The following example shows the steps to configure a VMAN (PBN) on the BlackDiamond 8810 switch shown in the following figure.
The VMAN is configured from the building to port 1, slot 3 on the BlackDiamond 8810 switch and from port 2, slot 3 on the BlackDiamond 8810 switch to the BlackDiamond® 6808 switch:
enable jumbo frames create vman vman_tunnel_1 configure vman vman_tunnel_1 tag 100 configure vman vman_tunnel_1 add port 3:1 untagged configure vman vman_tunnel_1 add port 3:2 tagged disable dot1p examination port 3:2 enable dot1p examination inner-tag port 3:2
The following example configuration demonstrates configuring IP multicast routing between VMANs and VLANs (when VMAN traffic is not double-tagged) on the BlackDiamond 8800 series switch and the Summit family of switches.
Using this configuration you can use a common uplink to carry both VLAN and VMAN traffic and to provide multicast services from a VMAN through a separate VLAN (notice that port 1:1 is in both a VLAN and a VMAN):
enable jumbo-frame ports all configure vman ethertype 0x8100 create vlan mc_vlan configure vlan mc_vlan tag 77 create vman vman1 configure vman vman1 tag 88 configure vlan vman1 ipaddress 10.0.0.1/24 configure vlan mc_vlan ipaddress 11.0.0.1/24 enable ipforwarding vman1 enable ipforwarding mc_vlan enable ipmcforwarding vman1 enable ipmcforwarding mc_vlan configure vlan mc_vlan add port 1:1 tag configure vman vman1 add port 1:1 tag configure vman vman1 add port 2:1, 2:2, 2:3
Note
IGMP reports can be received untagged on ports 2:1, 2:2, and 2:3. Tagged IP multicast data is received on mc_vlan port 1:1 and is routed using IP multicasting to vman1 ports that subscribe to the IGMP group.
IGMP snooping (Layer 2 IP multicasting forwarding) does not work on the VMAN ports because there is no double-tagged IP multicast cache lookup capability from port 1:1.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB