26.10.2013 Views

8.3.17.0 - Force10 Networks

8.3.17.0 - Force10 Networks

8.3.17.0 - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Auto-configured VLANs do not exist on a stacked Aggregator<br />

Symptom: When an Aggregator is configured and used in a stack, traffic does not flow and the VLAN<br />

auto-configuration on all ports is lost. This behavior happens because an Aggregator in stacking mode does<br />

not support auto-configured VLANs. Only VLANs that were previously manually configured are retained<br />

on the master stack unit.<br />

Resolution: You must manually configure VLAN membership on each stack-unit port.<br />

Steps to Take:<br />

1. Configure VLAN membership on individual ports (vlan tagged command).<br />

FTOS(conf)# interface tengigabitethernet 0/1<br />

FTOS(conf-if-te-0/1)#vlan tagged 2-5,100,4010<br />

FTOS(conf-if-te-0/1)#<br />

2. Verify the manually configured VLAN membership (show interfaces switchport interface command).<br />

FTOS#show interfaces switchport tengigabitethernet 0/1<br />

Codes: U - Untagged, T - Tagged<br />

x - Dot1x untagged, X - Dot1x tagged<br />

G - GVRP tagged, M - Trunk, H - VSN tagged<br />

i - Internal untagged, I - Internal tagged, v - VLT untagged, V - VLT tagged<br />

Name: TenGigabitEthernet 0/1<br />

802.1QTagged: Hybrid<br />

SMUX port mode: Admin VLANs enabled<br />

Vlan membership:<br />

Q Vlans<br />

U 1<br />

T 2-5,100,4010<br />

Native VlanId: 1<br />

Debugging and Diagnostics | 243

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!