Brocade Communications Systems IPMC5000PEF manual PIM Passive, Syntax no ip pim passive

PIM Passive

-------------------------------------------		25.0.0.25
1	225.1.1.1
2	225.1.1.2	25.0.0.25
3	225.1.1.3	25.0.0.25
4	225.1.1.4	25.0.0.25
5	225.1.1.5	25.0.0.25

PIM Passive

PIM Passive is used to reduce and minimize unnecessary PIM Hello and other PIM control messages.

PIM Passive allows you to specify that the interface is "passive" in regards to PIM. No PIM control packets are sent or processed (if received), but hosts can still send and receive multicast traffic and IGMP control traffic on that interface. Also, PIM Passive prevents any malicious router from taking over as the designated router (DR), which can prevent all hosts on the LAN from joining multicast traffic outside the LAN.

The following guidelines apply to PIM Passive:

1.This is a Layer 3 interface [Ethernet/Ve] level feature.

2.Since the loopback interfaces are never used to form PIM neighbors, this feature is not supported on loopback interface.

3.Both PIM SM and PIM DM modes support this feature.

4.Applying the PIM Passive on an interface requires PIM to be enabled on that interface.

5.The sent and received statistics of a PIM Hello message are not changed for an interface, while it is configured as PIM passive.

To enable PIM Passive on an interface, enter the following commands:

device# config term device(config)#router pim device(config-pim-router)#exit device(config)#interface ethernet 2 device(config-if-e1000-2)#ip pim device(config-if-e1000-2)#ip pim passive device(config-if-e1000-2)#exit device(config)#interface ve 2 device(config-vif-2)#ip pim-sparse device(config-vif-2)#ip pim passive device(config-vif-2)#exit

Syntax: [no] ip pim passive

Multicast Outgoing Interface (OIF) list optimization

Each multicast route entry maintains a list of outgoing interfaces (OIF List) to which an incoming multicast data packet matching the route is replicated. In hardware-forwarded route entries, these OIF lists are stored inside the hardware in replication tables which are limited in size. In many deployment scenarios, more than one multicast route can have identical OIF lists and can optimize usage of the replication table entries by sharing them across multiple multicast routes.

Multicast OIF list optimization keeps track of all the OIF lists in the system. It manages the hardware replication resources optimally, in real time, by dynamically assigning or re-assigning resources to multicast route entries to suit their current OIF list requirements, while maximizing resource sharing.

102	FastIron Ethernet Switch IP Multicast Configuration Guide
	53-1003085-02