Filter
Top Products
Application Example for Configuring Multicast Address Boundaries Configuring Multicast Address Boundaries
page 5-10 OmniSwitch 6800/6850/9000 Advanced Routing Configuration Guide December 2007
7 Create an IP interface on VLAN 3. For example:
-> ip interface vlan-3 address 178.20.1.1 vlan 3
Note. The ip interface command is not supported in Release 5.3.1. For this release use the vlan router ip
command instead. See the OmniSwitch CLI Reference Guide for more information.
8 Assign a boundary on the switch’s router interface. For this example, the interface is given the bound-
ary 239.188.0.0/16. This boundary will keep all traffic addressed to multicast addresses 239.188.0.0
through 239.188.255.255 from being forwarded on the interface:
-> ip mroute-boundary vlan-3 239.188.0.0 255.255.0.0
The command syntax includes the interface IP address (178.20.1.1), along with the multicast address
boundary (239.188.0.0) and the corresponding subnet mask (255.255.0.0).
9 Create a VLAN on the separate wiring closet switch used for Training. For example:
-> vlan 4
VLAN 4 is now used to define the Training network domain.
10 Create an IP interface on VLAN 4. For example:
-> ip interface vlan-4 address 178.30.1.1 vlan 4
Note. The ip interface command is not supported in Release 5.3.1. For this release use the vlan router ip
command instead. See the OmniSwitch CLI Reference Guide for more information.
11 Assign a boundary on the Training router interface. The interface is given the same boundary as
Human Resources (i.e., 239.188.0.0/16).
-> ip mroute-boundary vlan-4 239.188.0.0 255.255.0.0
Because there is a boundary configured at each domain, multicast users in Human Resources can forward
239.188.x.x multicast traffic without conflicting with users in Training who are forwarding traffic with the
same addresses. By allowing addresses to be used concurrently in more than one department, network
administrators can conserve limited scoped multicast address space.