Switching

I'm going through the Marvis alerts and it indicated that 3 ports on a given switch , which are connected to Mist APs have a missing VLAN. Yet, the VLAN is assigned to those ports by one of our templates and the VLAN shows assigned to those ports on the switch. 

What did Marvis think indicated that the VLANs were missing?  Do I dig deeper or ignore Marvis alerts on this type of issue? 

Hi John,

Is the switch port configured with all VLANs used by the AP's SSIDs?

For example, if the AP broadcasts two SSIDs, each mapped to a VLAN, the trunk port should include the native VLAN (for AP management) plus VLANs for SSID1 and SSID2. If more than one VLAN is mapped to the SSID in the WLAN configuration, more VLANs may be required on the switch port.

Regards

I'm going through the Marvis alerts and it indicated that 3 ports on a given switch , which are connected to Mist APs have a missing VLAN. Yet, the VLAN is assigned to those ports by one of our templates and the VLAN shows assigned to those ports on the switch. 

What did Marvis think indicated that the VLANs were missing?  Do I dig deeper or ignore Marvis alerts on this type of issue? 

Mist tells me it's missing VLAN2, which the port is a member of by our template.  With a "show vlans" command I see vlan2 has the port listed with an asterisk. 

Hi John,

Is the switch port configured with all VLANs used by the AP's SSIDs?

For example, if the AP broadcasts two SSIDs, each mapped to a VLAN, the trunk port should include the native VLAN (for AP management) plus VLANs for SSID1 and SSID2. If more than one VLAN is mapped to the SSID in the WLAN configuration, more VLANs may be required on the switch port.

Regards

I'm going through the Marvis alerts and it indicated that 3 ports on a given switch , which are connected to Mist APs have a missing VLAN. Yet, the VLAN is assigned to those ports by one of our templates and the VLAN shows assigned to those ports on the switch. 

What did Marvis think indicated that the VLANs were missing?  Do I dig deeper or ignore Marvis alerts on this type of issue? 

Mist should detect the absence of traffic and also if LLDP fails to tell the AP the VLAN is there and possibly other criteria and compile that info to a decision that the VLAN is missing on  the port. It could be that the VLAN is missing on the uplink to the switch so it doesn't have connectivity to the router for that VLAN. That would result in no ARP packets from the GW/FW.

Does VLAN 2 actually work on the switch and the AP?

Mist tells me it's missing VLAN2, which the port is a member of by our template.  With a "show vlans" command I see vlan2 has the port listed with an asterisk. 

Hi John,

Is the switch port configured with all VLANs used by the AP's SSIDs?

For example, if the AP broadcasts two SSIDs, each mapped to a VLAN, the trunk port should include the native VLAN (for AP management) plus VLANs for SSID1 and SSID2. If more than one VLAN is mapped to the SSID in the WLAN configuration, more VLANs may be required on the switch port.

Regards

I'm going through the Marvis alerts and it indicated that 3 ports on a given switch , which are connected to Mist APs have a missing VLAN. Yet, the VLAN is assigned to those ports by one of our templates and the VLAN shows assigned to those ports on the switch. 

What did Marvis think indicated that the VLANs were missing?  Do I dig deeper or ignore Marvis alerts on this type of issue?