Saturday 14 July 2012

multicasting troubleshooting with commands list

1)      Check traffic on provider CE LAN interface using following command.

CErouter#sh int fa0/0 | in rate
 Queueing strategy: fifo
 30 second input rate 992000 bits/sec, 307 packets/sec
 30 second output rate 2000 bits/sec, 4 packets/sec

2)        Check multicast traffic on CE  router using following commands

    CErouter#sh ip mroute active
 Active IP Multicast Sources - sending >= 4 kbps
 a negative (-) Rate counts pps being fast-dropped

    Group: 233.77.100.4, (?)
     Source: 100.10.10.1 (?)
     Rate: 2 pps/8 kbps(1sec), 8 kbps(last 0 secs), 0 kbps(life avg)

     Group: 233.64.195.81, (?)
      Source: 160.1.1.17 (?)
      Rate: 20 pps/65 kbps(1sec), 65 kbps(last 0 secs), 1 kbps(life avg)


router#sh ip mroute count

IP Multicast Statistics
91 routes using 43784 bytes of memory
46 groups, 0.97 average sources per group
Forwarding Counts: Pkt Count/Pkts(neg(-) = Drops) per second/Avg Pkt Size/Kilobits per second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)

Group: 233.77.100.4, Source count: 1, Packets forwarded: 3231252, Packets received: 3231984
  Source: 100.10.10.1/32, Forwarding: 3231252/6/400/19, Other: 3231984/732/0

Group: 233.77.100.58, Source count: 1, Packets forwarded: 1821875, Packets received: 2639381
  RP-tree: Forwarding: 0/0/0/0, Other: 0/0/0
  Source: 140.1.1.17/32, Forwarding: 1821875/17/400/54, Other: 2639381/0/817506


3)      If you don’t see any multicast traffic check whether tunnel (from the remote PE) is     up or not on PE router using following command.   


PEROUTER#sh ip pim vrf <VRF NAME>neighbor

PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
      S - State Refresh Capable
Neighbor          Interface                Uptime/Expires     
Ver     DR
Address                                                                                           Prio/Mode
212.60.60.66      Tunnel2                  3d21h/00:01:42    v2    1 / DR S P






PEROUTER#sh int Tunnel2
Tunnel2 is up, line protocol is up
  Hardware is Tunnel
  Interface is unnumbered. Using address of Loopback60 (212.60.60.36)
  MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation TUNNEL, loopback not set
  Keepalive not set
  Tunnel source 212.60.60.36 (Loopback60), destination 239.232.63.61, fastswitch TTL 255
  Tunnel protocol/transport GRE/IP Multicast, key disabled, sequencing disabled


If tunnel is down,

Check transport vrf configuration on both PE routers (Provider and Member)

a)       MDT should be same on both vrfs.
b)       Enable pim on all core interfaces.
c)       Also check if there are any ACLs which are denying the PIM neighborship to establish.
d)       Use following command to trace.

     Mtrace < Source add (management address) >  < Destination add >  < group add>

 Tunnel source and destination add  will be Loopback 100 for white OSPF, Loopback 60 for RED OSPF and Loopback 70 for BLUE OSPF of PE routers.


5) Use following command to check multicast traffic on PE router.

PEROUTER#sh ip mroute vrf <vrf name> active

Active IP Multicast Sources - sending >= 4 kbps

Group: 233.64.195.84, (?)
   Source: 100.10.10.1 (?)
     Rate: 28 pps/89 kbps(1sec), 91 kbps(last 40 secs), 90 kbps(life avg)

6) Use following command  to display IP multicast routing table.

Router#sh ip mroute

IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(100.10.10.1, 233.77.100.4), 1w1d/00:02:51, flags: sTI
  Incoming interface: Serial0/0/0:0.101, RPF nbr 62.2.68.29
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 1w1d/00:02:58

(*, 233.77.100.58), 1d22h/stopped, RP 145.1.1.2, flags: SP
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null

(140.1.1.17, 233.77.100.58), 1d19h/00:03:20, flags: TA
  Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0
  Outgoing interface list:
    Serial0/0/0:0.101, Forward/Sparse, 01:11:14/00:03:23



Show Commands

1)      Show  ip pim neighbor
2)      Show  ip pim Interfaces
3)      Show ip pim rp mappings
4)      Show ip igmp groups
5)      Show ip  mroute active
6)      Show ip mroute count


Debug commands

1)      #debug ip pim
Use the debug ip pim command to display PIM packets received and transmitted, as well as PIM related events.

2)       # debug ip igmp
Use the debug ip igmp command to display IGMP packets received and transmitted, as well as IGMP-host related events



No comments:

Post a Comment