Tuesday, September 22, 2020

Switch not passing PVID tagged VLAN to other ports?

I hope this is OK to ask here, its been driving me mad for a few days now and I can't think where else to get help!

I'm working on a small portion of a very large corporate network. Our IT department has given us access for our needs but won't provide any support!

I have 8 H3C managed switched around my part of the building that are connected though the resorts main guests network core (the core is outside of what we are allowed to configure). We have been allocated 6 VLANs for our use and I am setting up an Aruba WIFI network using a 7030 controller and large number of APs.

The APs connected to ports on the switch that are configured as:

Link Type: Access Untagged Membership: 601 Tagged Membership: None PVID: 601 

The controller is connected to a port setup the same (it also has 2 other connections to ports for the VLANs the WIFI users get assigned to but I believe that's not relevant to the issue here)

The uplink from the switches to the core switches are setup as:

Link Type: Trunk Untagged Membership: None Tagged Membership: 601 (plus others) PVID: 1 

Everything works except 1 thing.

APs on the same switch as the controller can't see it.

APs on other switches have no problems. From my desktop I can ping all the APs and the Controller, including the APs on the same switch as the controller.

I assumed that with PVID set to the correct VLAN, the data from an AP gets tagged, and would then be passed back out of any ports on the same switch allocated to that VLAN?

With exactly the same port configuration, why after passing through the core does it work, but not within a single switch?

Any advice would be hugely appreciated.



No comments:

Post a Comment