Brocade Communications Systems IPMC5000PEF Manual De Usuario

Configuring PMRI

PMRI is enabled by default. To disable PMRI, enter commands such as the following.

device(config)# router pim

device(config-pim-router)# hardware-drop-disable

Syntax: [no] hardware-drop-disable

Displaying hardware-drop

Use the show ip pim sparse command to display if the hardware-drop feature has been enabled or
disabled.

device(config)#show ip pim sparse

Global PIM Sparse Mode Settings

  Maximum Mcache         : 12992       Current Count              : 0

  Hello interval         : 30          Neighbor timeout           : 105

  Join/Prune interval    : 60          Inactivity interval        : 180

  Hardware Drop Enabled  : Yes         Prune Wait Interval        : 3

  Bootstrap Msg interval : 60          Candidate-RP Msg interval  : 60

  Register Suppress Time : 60          Register Probe Time        : 10

  Register Stop Delay    : 10          Register Suppress interval : 60

  SSM Enabled            : Yes         SPT Threshold              : 1

  SSM Group Range        : 232.0.0.0/8

  Route Precedence       : mc-non-default mc-default uc-non-default uc-default

IP multicast boundaries

The IP multicast boundary feature is designed to selectively allow or disallow multicast flows to
configured interfaces.

The ip multicast-boundary command allows you to configure a boundary on a PIM enabled interface
by defining which multicast groups may not forward packets over a specified interface. This includes
incoming and outgoing packets. By default, all interfaces that are enabled for multicast are eligible to
participate in a multicast flow provided they meet the multicast routing protocol’s criteria for participating
in a flow.

Configuration considerations

•

Only one ACL can be bound to any interface.

•

Normal ACL restrictions apply as to how many software ACLs can be created, but there is no
hardware restrictions on ACLs with this feature.

•

Creation of a static IGMP client is allowed for a group on a port that may be prevented from
participation in the group on account of an ACL bound to the port’s interface. In such a situation,
the ACL would prevail and the port will not be added to the relevant entries.

•

Either standard or extended ACLs can be used with the multicast boundary feature. When a
standard ACL is used, the address specified is treated as a group address and NOT a source
address.

Configuring PMRI