DELL S50V User Manual

|

PIM Sparse-Mode

www.dell.com | support.dell.com

To prevent these delivery errors you must statically map the potential incoming interfaces for the (*,G) 
entries via the CLI. When you create this mapping, (*,G) entries are programmed in hardware. Packets are 
then fast forwarded starting with the first packet, and the potential for these delivery errors is avoided.

The PIM MIB is supported only on platform 

e

FTOS fully supports the PIM MIB as specified in RFC 5060 with some exceptions.

•

The following tables are not supported:

•

pimBidirDFElectionTable

•

pimAnycastRPSetTable

•

The OIDs related to InvalidRegisterMsgs reflect the last received invalid register message. Similarly, 
the OIDs related to InvalidJoinPruneMsgs reflect the last received invalid Join or Prune message.

•

OIDs which refer to any timer show the time that the timer started; it is 0 otherwise.

multicast traffic when you enable different combinations of PIM-SM DR flooding and IGMP snooping 
flooding on a switch/router.

When you enable PIM-SM and IGMP snooping at the same time:

•

The IGMP report is forwarded on the port that connects to the PIM DR.

•

The port that connects to the PIM DR port and ports on which IGMP queries are received are chosen as 
IGMP router ports. It is recommended that you configure the both the IGMP querier and the PIM DR 
in the same router to avoid unnecessary flooding.

1

Create a standard access-list that 
permits one or more IGMP groups.

ip access-list standard name

CONFIGURATION

FTOS(config-std-nacl)#show config

!

ip access-list standard map1

 seq 5 permit 224.0.0.0/24

2

Apply the ACL to an interface on 
which there might be a source for a 
group specified in the ACL. This 
command maps the incoming 
interface to the (*,G) entry so that the 
entry can be programmed into 
hardware.

 

t

INTERFACE