The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how multicasting interoperates in a chassis that contains both M Series and N7K-F132-15 modules.
Beginning with Cisco NX-OS Release 5.1, you can add an N7K-F132-15 module, which is a Layer 2-only module, into the Cisco Nexus 7000 Series chassis. You can add this module to a chassis that already contains M Series modules to provide multicasting in a chassis that contains both N7K-F132-15 and M Series modules.
This section includes the following topics:
Note You must install an N7K-M series module in the Cisco Nexus 7000 Series chassis to run Layer 3 routing and multicasting with the N7K-F132-15 module because you must have interfaces from both the M Series and the N7K-F132-15 modules in the same virtual device context (VDC). See the Cisco Nexus 7000 Series Virtual Device Context Configuration Guide, Release 5.x, for more information on VDCs.
Layer 3 routing and multicasting come up automatically when you have an N7K-M series module installed in the chassis with the N7K-F132-15 module. You can position a chassis with both N7K-F132-15 and M Series modules at the boundary between the Layer 2 and Layer 3 networks.
You must configure a VLAN interface for each VLAN on the N7K-F132-15 module that you want to use the proxy-routing functionality in a chassis that contains both N7K-F132-15 and M series modules. See the Cisco Nexus 7000 Series Interfaces Configuration Guide,Release 5.x, for information on configuring VLAN interfaces.
By default, all of the physical interfaces on the N7K-M series modules in the VDC become proxy routing ports for the VLANs that are configured with VLAN interfaces on the Layer 2-only N7K-F132-15 module in the same VDC. The physical interfaces on the M Series module can be administratively down and they still pass traffic as proxy routers.
Packets that enter an interface on the N7K-F132-15 module are automatically forwarded to one of the interfaces on the M Series modules in the same VDC to be routed. The interface on the M Series module also performs egress replication for Layer 3 multicast packets that enter an interface on the N7K-F132-15 module in the same VDC. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for additional information about the routing interoperation with the N7K-F132-15 module.
You can specify which interfaces on the M Series modules in the VDC where you want to perform the egress replication of VLAN interfaces for Layer 3 multicast packets. For multicast egress replication, the system automatically rebalances all the VLAN interfaces among all the available M Series proxy routing interfaces. You can specify automatic or manual rebalancing among the proxy multicast replicators. If you specify manual rebalancing, you trigger a rebalance by entering a command. This command is useful when you are inserting or removing modules.
Note When you configure manual egress multicast replication load balancing and enter the rebalancing command, that command is not part of the configuration. It is not included in the commands that are copied when you enter the copy running-config startup-config command.
You must have interfaces from both the M Series and the N7K-F132-15 modules in the same VDC.
See the Cisco Nexus 7000 Series Virtual Device Context Configuration Guide, Release 5.x, for more information about VDCs.
For information about high availability, see the Cisco Nexus 7000 Series NX-OS High Availability and Redundancy Guide, Release 5.x.
The following table shows the licensing requirements for this feature:
For multicast interoperation, you must have at least one module of the following series in the Cisco Nexus 7000 Series chassis, as well as a valid license installed:
Multicasting has the following configuration guidelines and limitations:
You can configure a Layer 3 gateway in a chassis with N7K-F132-15 and M series modules, by using the proxy routing functionality. You enable routing on a specific VLAN by configuring a VLAN interface. See the Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x, for more information about Layer 3 routing and VLAN interfaces.
By default, Layer 3 routing and multicasting come up automatically when you have an N7K-M Series module installed in the chassis with the N7K-F132-15 module. Layer 3 routing, multicasting, and load balancing among the available N7K-M Series works by default using proxy routing on the N7K-M Series modules.
Optionally, you can specify which physical interfaces on the N7K-M Series modules that you want to use for egress multicast replication, as well as forcing rebalancing.
You must configure a VLAN interface for each VLAN on the N7K-F132-15 module where you want to use the proxy-routing functionality in a mixed chassis.
You must have interfaces from both the M Series and the N7K-F132-15 modules in the same VDC.
If you remove an interface from the VDC and then enter this command, the removed interface only display when you reload the VDC.
2. hardware proxy layer-3 replication {use | exclude} { module mod-number | interface slot/port} [ module-type f1 ]
3. hardware proxy layer-3 replication rebalance-mode {auto | manual}
4. hardware proxy layer-3 replication trigger rebalance
This example shows how to specify certain physical interfaces on the N7K-M Series modules to perform egress multicast replication for VLANs on the N7K-F132-15 module in a mixed chassis and to trigger a rebalance:
To display multicast configuration information, perform one of the following tasks:
Table 1-1 lists the release history for this feature.