Dell Brocade DCX, Configuration Manual, Page: 660 / 1436

588 BigIron RX Series Configuration Guide
53-1001810-01
PIM dense
23
Next hop validation check
Beginning with release 02.6.00, you can configure the device to perform multicast validation
checks on the destination MAC address, the sender and target IP addresses, and the source MAC
address.
You can enable ARP validation check on the global basis. When feature is enabled, the multicast
route will only be installed when the next hop ARP has been resolved.
Configuring an ARP validation check
To enable the ARP validation check globally, enter a command such as the following.
BigIron RX(config)#ip mroute validate-nexthop-arp
Syntax: [no] ip mroute validate-nexthop-arp
Use the no form of the command to disable the ARP validation feature. When ARP validation is
disabled, The static mroute will be installed without checking the validity of the next hop.
Enabling the next hop validate ARP timer
The ip arp validate-nexthop-timer command has been introduced which replaces the ip route
validate-nexthop-arp-timer and the ip mroute validate-nexthop-arp-timer commands. The next hop
validate ARP timer works only on the ARP entries created when the ARP validation check feature
has been enabled. The timer is used to age out the ARP entries when the next hop goes down. All
other ARP entries in the system, which are NOT created due to static routes, follow the normal ARP
age timer with default value of 3 minutes.
Use the validation timer to reduce the response time where the static route with the next hop down
can be replaced quickly with a route with active next hop.
To set the validation timer to 30 seconds, enter commodes such as the following.
BigIron RX(config)#ip arp validate-nexthop-timer 30
Syntax: [no] ip arp validate-nexthop-timer <value>
The default is 200 seconds.
The value parameter specifies the amount of time before a nexthop down is replaced by an active
nexthop. Possible values are10-200 seconds.
Use the no form of the command to disable the validation timer.
PIM dense
NOTE
This section describes the “dense” mode of PIM, described in RFC 1075. Refer to “PIM Sparse” on
page 596 for information about PIM Sparse.
NOTE
Multicast protocols can only be applied to 1 physical interface. You must create multiple VLANs with
individual untagged ports and ve’s under which you configure PIM.