12.07.2015 Views

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4Super Aggregated VLANs.4/1 PHYSICAL UNTAGGED NONE FORWARDING4/2 PHYSICAL UNTAGGED NONE FORWARDING4/3 PHYSICAL UNTAGGED NONE FORWARDING4/4 PHYSICAL UNTAGGED NONE DISABLEDPORT-VLAN 100, Name [None], Priority Level0----------------------------------------------------------Port Type Tag-Mode Protocol State4/1 PHYSICAL TAGGED STP FORWARDINGThis comm<strong>and</strong> displays detailed information for a specific VLAN ID, as shown in the followingexample.<strong>Brocade</strong>(config-vlan-10)# show vlan detail 10PORT-VLAN 10, Name [None], Priority Level0----------------------------------------------------------Port Type Tag-Mode Protocol State1/1 PHYSICAL TAGGED STP DISABLED1/2 PHYSICAL TAGGED STP DISABLEDSAV debug comm<strong>and</strong>sThere are no debug comm<strong>and</strong>s specific to SAV.Configuration notes• A maximum of 1544 bytes is supported on ports where SAVs are configured. An additional 8bytes over the untagged port maximum allows for support of two VLAN tags.• For core devices, you must configure a VLAN tag-type (tag ID) that is different than the tag-typeused on edge devices. If you use the default tag-type (8100) on the edge devices, set thetag-type on the core devices to another value, such as 9100.Common diagnostic scenariosIn an environment that includes a <strong>Brocade</strong> <strong>NetIron</strong> <strong>XMR</strong> <strong>and</strong> <strong>Brocade</strong> <strong>MLX</strong> series device with bothVPLS <strong>and</strong> SAV configured, one VPLS endpoint port is connected to a carrier <strong>and</strong> will be receivingdual tags, with both tags using tag-type 8100. The outer tag is the carrier's VLAN <strong>and</strong> the inner tagis from the end user.The frame structure is DA | SA | 8100 tag=1000 | 8100 tag=100 | Data from the carrier side. Theport must support multiple VLANs coming in from the carrier.The other VPLS endpoint goes to the end user with a single tag, <strong>and</strong> the frame structure is DA | SA| 8100 tag=100 | Data.Use the following configuration on the two endpoints to support dual tags on one side of the VPLS<strong>and</strong> a single tag on the other side:Carrier side endpoint configurationRouter MPLSvpls vpls1000 1000vpls-peer 2.2.2.282 <strong>Brocade</strong> <strong>MLX</strong> <strong>Series</strong> <strong>and</strong> <strong>Brocade</strong> <strong>NetIron</strong> <strong>XMR</strong> <strong>Diagnostic</strong> <strong>Guide</strong>53-1002426-02

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

Saved successfully!

Ooh no, something went wrong!