Download complete user manual (PDF). - Brocade
Download complete user manual (PDF). - Brocade
Download complete user manual (PDF). - Brocade
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
3<br />
Multicast non-stop routing<br />
The ethernet slot/portnum parameter specifies the port number. Use this parameter if the port is a<br />
member of a virtual routing interface, and you are entering this command at the configuration level<br />
for the virtual routing interface.<br />
Manually added groups are included in the group information displayed by the following<br />
commands:<br />
• show ip igmp group<br />
• show ip pim group<br />
To display static multicast groups in default VRF, enter the following command.<br />
<strong>Brocade</strong>#show ip igmp static<br />
Group Address Interface Port List<br />
----------------------------------<br />
224.2.2.2 v1 ethe 5/2<br />
Syntax: show ip igmp [vrf vrf_name] static<br />
The vrf parameter allows you to display static IGMP groups for the VRF instance specified by the<br />
vrf_name variable.<br />
Multicast non-stop routing<br />
Multicast non-stop routing (NSR) provides hitless-failover support on all platforms for IPv4<br />
multicast features (default and non-default VRFs): PIM-DM, PIM-SM, and PIM-SSM.<br />
If multicast NSR is enabled, the software state is kept in sync between the active and standby<br />
modules. The standby module is NSR ready when the software state of the standby and active<br />
modules are in sync. When the standby module is NSR ready, a hitless-failover does not result in a<br />
disruption to the multicast forwarding state or traffic<br />
If Multicast NSR is not enabled, or if the standby module is not NSR ready, the software state of the<br />
standby and active modules are not in sync. In this case, after a switchover or failover occurs, the<br />
new active module enters protocol learning phase for a duration of 55 seconds. During this phase,<br />
it learns the protocol state information from its PIM neighbors and local clients. During this period,<br />
new multicast flows will not be forwarded, but the existing mutlicast flows (which existed prior to<br />
switchover or failover) are forwarded in hardware without any disruption. At the end of the period,<br />
all the existing flows are deleted from hardware and they are reprogrammed as per the newly<br />
learned state information. Multicast traffic will incur a slight disturbance until the new active<br />
module reprograms the hardware with new forwarding state information.<br />
The following message is displayed on the console of the active and standby modules to indicate<br />
that the standby module is NSR ready:<br />
Mcastv4 is NSR ready<br />
NOTE<br />
During a hitless-upgrade on SX platforms, the new active module will always perform the 55 second<br />
deferred hardware cleanup even if the NSR is enabled.<br />
66 FastIron Ethernet Switch IP Multicast Configuration Guide<br />
53-1002638-02
Change language