McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 20

↗ View in doc context
page
20
source
ip/multicast/multicast-guide/multicast-guide.md
chunk_id
ip::multicast::multicast-guide::multicast-guide::20

M - MSDP created entry, X - Proxy Join Timer Running A - Advertised via MSDP Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.1.1.1), 02:42:20/00:02:59, RP 0.0.0.0, flags: DJC Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Tunnel0, Forward/Sparse-Dense, 00:22:53/00:00:00 Ethernet1/4, Forward/Sparse-Dense, 02:42:20/00:00:00

(10.1.1.1, 224.1.1.1), 00:22:53/00:02:59, flags: CT Incoming interface: Tunnel0, RPF nbr 10.6.1.1, Mroute Outgoing interface list: Ethernet1/4, Forward/Sparse-Dense, 00:22:53/00:00:00

In order to check that the multicast data is load balanced equally across the three links, look at the interface data of Router 75a. The incoming interface is 9000 bits/sec:

<#root> ip22-75a# show interface e0/0

. . 5 minute input rate 9000 bits/sec, 20 packets/sec

The three outgoing interfaces each show 3000 bits/sec:

ip22-75a#show interface e0/1 . . 5 minute output rate 3000 bits/sec, 7 packets/sec

ip22-75a#show interface e0/2 . . 5 minute output rate 3000 bits/sec, 7 packets/sec

ip22-75a#show interface e0/3 . . 5 minute output rate 3000 bits/sec, 7 packets/sec

When You Receive the IP Multicast "INVALID_RP_JOIN" Error