Technical data

52 Known limitations and considerations in this release

217316-A Rev 00

DVMRP

• Scaling with 500 DVMRP interfaces and 1980 VLANs with 512 neighbors or

more results in a high CPU utilization that could reach 100%. If you need to

configure a large number of interfaces with DVMRP neighbors, the interfaces

cannot be attached to LANs without routers running DVMRP. (Q00646615)

• Before configuring DVMRP on an interface using Device Manager, please be

sure that DVMRP has been globally and successfully configured.

(Q00912792)

PIM

• A non-DR switch receives double traffic when a receiver is connected to a

non-DR switch and the unicast route (shortest path) towards the source is not

through a DR switch. Both non-DR and DR switches create (*,G) and (S,G)

records. (Q0086744)

• On a VLAN spanning more than two switches, SPT path joins are received on

one port of the spanning VLAN. The messages on the VLAN port on which

RP-to-source prune messages are received are not properly pruned and stay in

a prune pending state (because of overriding joins received on the port in the

SPT path). (Q00421566)

• The PIM MRtable incorrectly shows incoming traffic port when there is an

SMLT failover. (Q00664751)

• R1 and R2 are running PIM, as shown below:

If the BPS is at the edge, then the BPS always forwards traffic on the lowest

link of the MLT. Rebooting the DR switch when traffic is flowing

through 1/1, forces traffic to recover through 1/2.

BPS

R2 (DR)(non-DR) R1

1/11/2