Brocade Multi-Service IronWare Multicast Configuration Guide (Supporting R05.6.00) - Manual (Page 63)

Multi-Service IronWare Multicast Configuration Guide 51
53-1003032-02
Multicast Outgoing Interface (OIF) list optimization
1
The num parameter specifies the number of seconds and can from 10 – 65535. The default is 60.
PIM multinet
Brocade devices support PIM over secondary addresses in IPv4.
Whenever a secondary address is configured on a interface, all the secondary addresses
configured on the interface are sent out on the PIM Hello using the secondary address option.
Whenever a receiver uses a secondary address as its source and sends a IGMP group report, the
PIM join and prunes are propagated up the network.
Whenever a secondary address is configured as a RP, the packets are processed appropriately
Displaying the seconadary address
In this example the PIM neighbor on e 1/11 has multiple IP addresses configured on the interface.
Brocade#show ip pim neighbor
--------+--------+---------------+--------+---+---------+---------+-----+--------
--------+-----------+----+
Port |PhyPort |Neighbor |Holdtime|T |PropDelay|Override |Age |UpTime
|VRF |Prio
| | |sec |Bit|msec |msec |sec |
| |
--------+--------+---------------+--------+---+---------+---------+-----+--------
--------+-----------+----+
e1/11 e1/11 20.1.1.1 105 1 500 3000 18 00:00:50
default 1
+ 30.1.1.1
e1/12 e1/12 192.168.2.1 105 1 500 3000 18 2d 02:34:19
default 1
e1/15 e1/15 192.168.7.3 105 1 500 3000 7 2d 23:53:07
default 1
On the PIM interface when multiple IP addresses are configured, the lowest IP
address is chosen as the primary address
That’s the reason that ethernet 1/11 has 20.1.1.1 as the address of the neighbor
address.
Syntax: show ip pim neighbor
Refer to “Displaying multicast neighbor information” for output descriptions.
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.