Brocade Multi-Service IronWare Multicast Configuration Gui Manual de usuario Pagina 28

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 216
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 27
16 Multi-Service IronWare Multicast Configuration Guide
53-1003032-02
IP multicast boundaries
1
Configuring PMRI
PMRI is enabled by default. To disable PMRI, enter commands such as the following.
Brocade(config)# router pim
Brocade(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.
Brocade(config)#show ip pim sparse
Global PIM Sparse Mode Settings
Hello interval : 30 Neighbor timeout : 105
Bootstrap Msg interval: 60 Candidate-RP Advertisement interval: 60
Join/Prune interval : 60 SPT Threshold : 1
Inactivity interval : 180 SSM Enabled : No
Hardware Drop Enabled : Yes
show ip pim sparse
IP multicast boundaries
The 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 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
The configuration considerations are as follows:
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.
When a boundary is applied to an ingress interface, all packets destined to a multicast group
that is filtered out will be dropped by software. Currently, there is no support to drop such
packets in hardware.
The ip multicast-boundary command may not stop clients from receiving multicast traffic if the
filter is applied on the egress interface up-stream from RP.
Vista de pagina 27
1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 215 216

Comentarios a estos manuales

Sin comentarios