asr9k multicast troubleshooting external
DESCRIPTION
Asr9k Multicast Troubleshooting ExternalTRANSCRIPT
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 1
ASR9000 Multicast troubleshooting Document Cisco Systems
ASR9000 Deployment team
2 ASR9000 Multicast troubleshooting document, Cisco Systems Inc
Table of Contents
1 Introduction: ............................................................................................................................... 3 1.1 Fabric Replication: ....................................................................................................................................................................... 3 1.2 FIA and Bridge replication: ...................................................................................................................................................... 4 1.3 NP Replication: .............................................................................................................................................................................. 5
2 Multicast software Architecture: ................................................................................................. 6
3 Packet flow and debugging commands at high level: ................................................................... 8
4 Testbed topology: ....................................................................................................................... 9
5 Verifying the mrib, mfib and IGMP info ..................................................................................... 10 5.1 Explanation of the mfib and mrib flags ........................................................................................................................... 13 5.2 MGID and FGID programming: ............................................................................................................................................ 13 5.3 Checking multicast programming in MFIB: ................................................................................................................... 15 6 Verifying hardware mroute/mfib Table ..................................................................................... 17
7 Tracing the packet through Fabric and ASICs: ............................................................................ 19 7.1 Ingress NP counters: ................................................................................................................................................................ 19 7.2 Ingress FIA counters ................................................................................................................................................................ 19 7.3 Egress LC FIA counters: .......................................................................................................................................................... 20 7.4 Egress NP counters ................................................................................................................................................................... 20 8 Debugging multicast Process Memory: ...................................................................................... 21
9 Debugging Multicast and related processes: .............................................................................. 21
10 Additional Commands: .............................................................................................................. 23
11 Multicast drops counters in NP: ................................................................................................ 23
12 Checking multicast resource Allocation in hardware/software: ................................................. 24
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 3
1 Introduction: Purpose of this document is to outline multicast forwarding packet path as well to provide deep dive on troubleshooting procedures which can be handy to troubleshoot multicast related issues. ASR9k is highly distributed system, which utilizes simplified but very sophisticated replication technologies. As described below, replication is performed at various points to ensure bandwidth is utilized effectively. Unlike 7600, there is no concept of ingress replication in ASR9K. Hence ingress LC doesn’t take part in replication of multicast traffic. Figure 1: Following diagram outlines various replication points.
1.1 Fabric Replication: Fabric is responsible for replicating packet to egress LCs interested in receiving multicast traffic. When ingress LC receives multicast packet, NP performs a lookup on (S,G) and forwards the packet to fabric along with fabric header that has MGID and FGID. Fabric performs the replication based on the FGID value in fabric header of the packet.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public Presentation_ID 14
IGMP joins
NP0
NP2
NP3
NP1 FIA
B0
B1
CPU PHY
PHY
PHY
PHY
Typhoon LC
Multicast Source Switch
Fabric
1
FGID/ FPOE
Fabric Replication ! replicate single copy to
LCs which receive IGMP join, based on FGID table
in switch fabric
FIA Replication ! replicate single copy to Bridge which has
IGMP join, based on MGID table in FIA
NP Replication ! replicate copy per receiver based on
multicast FIB table
1
2
4
Multicast Packet Replication Switch Fabric and Egress LC Replication
FGID – Fabric Group ID MGID – Multicast Group ID
MFIB – Multicast Forwarding Information Base
IGMP joins
Bridge Replication ! similar as FIA replication, single copy
to NP
3
23
NP0 PHY
NP2 PHY
NP3 PHY
NP1 PHY FIA
CPU
Trident LC
IGMP joins
B0
B1
23
4
MGID MGID
MFIB
3x10GE SFP +
3x10GE SFP +
3x10GE SFP +
3x10GE SFP +
3x10GE SFP +
3x10GE SFP +
3x10GE SFP +
3x10GE SFP +
Sw
itch Fabric A
SIC
2
MGID/
FPOE
FIA
FIA
FIA
FIA NP1
NP2
NP3
NP4
NP5
NP6
NP7
NP8
3x 10G
3x 10G
3x 10G
3x 10G
3x 10G
3x 10G
3x 10G
3x 10G
Trident LC
IGMP joins
4 ASR9000 Multicast troubleshooting document, Cisco Systems Inc
• FGID (Fabric Group Identifier) is globally significant and is 12 bits wide. • Slotmask used by switch fabric to determine replication to line card/RSP slots • FGID Values for Megatron (ASR 9022) chassis are assigned as follows
FGID Bit 0 1 2 3 4 5 6 7 8 9 10 11 Slot RP0 RP1 LC0 LC1 LC2 LC3 LC4 LC5 LC6 LC7 LC8 LC9 Slot N/A N/A LC10 LC11 LC12 LC13 LC14 LC15 LC16 LC17 LC18 LC19
• On the 9022 chassis, due to overlapping slots mapped to same bit, fabric will replicate
packets to 2 slots. For example, if receiver is on slot 6, fabric will replicate the packets to slot 6 and 16.
1.2 FIA and Bridge replication:
• FIA and Bridge uses MGID (multicast Group ID) information in fabric headers for replicating packets to bridge and NP’s.
• MGID is locally significant to LC. This means content of the same MGID in LC2 can be different from LC3.
© 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential EDCS:xxxx 5
LC 7
LC
6
LC 5
LC 4
RS
P 0
RS
P 1
LC 3
LC 2
LC 1
LC 0
Logical Slot
9 8 7 6 5 4 3 2 1 0
Slot Slot Mask
Logical Physical Binary Hex
LC7 9 1000000000 0x0200
LC6 8 0100000000 0x0100
LC5 7 0010000000 0x0080
LC4 6 0001000000 0x0040
RSP0 5 0000100000 0x0020
RSP1 4 0000010000 0x0010
LC3 3 0000001000 0x0008
LC2 2 0000000100 0x0004
LC1 1 0000000010 0x0002
LC0 0 0000000001 0x0001
Target Linecards FGID Value (10 Slot Chassis)
LC6 0x0100
LC1 + LC5 0x0002 | 0x0080 = 0x0082
LC0 + LC3 + LC7 0x0001 | 0x0008 | 0x0200 = 0x0209
FGID Calculation Examples
FGIDs: 10 Slot Chassis
LC 3
LC 2
LC 1
LC 0
RSP 1
RSP 0
Logical Slot
Phy Slot
Number
5
4
3
2
1
0
Slot Slot Mask
Logical Physical Binary Hex
LC3 5 0000100000 0x0020
LC2 4 0000010000 0x0010
LC1 3 0000001000 0x0008
LC0 2 0000000100 0x0004
RSP1 1 0000000010 0x0002
RSP0 0 0000000001 0x0001
FGIDs: 6 Slot Chassis
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 5
• MGID’s are programmed both in FIA and bridge. MGID in FIA is used to replicate the packet to Bridge asic and MGID in Bridge asic is used to perform replication to interested NPU’s. NOTE: Only tridents LCs have Bridge asic. In typhoon LC’s, NP is directly connected to FIA.
1.3 NP Replication: NP replicates the packets to one or more directly connected interfaces from which it receives IGMP joins. • If given NP has more than one outgoing ports, packet will be replicated in TM
loopback in the NP. In the second pass all the egress features will be applied.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public Presentation_ID 32
MGID Tables MGID Bitmasks
MGID Bit 1 Bit 0
MGID Bit 1 Bit 0
MGID Bit 1 Bit 0
FIA
Bridge1
NP3
Bridge0
NP2 NP1 NP0
6 ASR9000 Multicast troubleshooting document, Cisco Systems Inc
2 Multicast software Architecture: As described below LC will punt PIM, IGMP control packets to RP CPU. The MRIB process uses route, outgoing interface list information from PIM, IGMP to build mroute table. MRIB is also responsible to send this information to each of the LC CPU’s. If LC receives a packet to a new (S,G), NPU will punt the packet to LC CPU. LC CPU will punt packet to RSP CPU if transit entry for new (S,G) doesn’t exist in LC CPU (entry is also called pre-‐fib)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public Presentation_ID 13
Initial lookup
TM
Second lookup
From Fabric
To egress port
NP
! Initial Lookup – Original packet is lookup in the MFIB/L2FIB returning the number of copies to be replicated on the given NPU, each copy per output logical interface
– Packet is sent to a TM (traffic manager). TM replicates the packets and send the copy to the processing engine
! Second Lookup – Each copy is processed and sent out of interface. Egress feature like QoS, ACL is applied at this pass
Multicast Packet Replication Inside NP
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 7
Multicast control packets destined to LC/RP CPU will undergo CoPP (LPTS : Local Packet Transport System) to protect RP/LC CPU from excessive control packets. Following diagram shows policing rate for PIM/IGMP packets.
1. Incoming*IGMP*and*PIM*packets*are*punted*to*RP*CPU*
2. Protocols*(PIM/IGMP)*send*their*Route/OLIST*InformaEon*to*MRIB*process*to*build*mulEcast*route/olist*table*
3. MRIB*sends*the*mulEcast*state*informaEon*to*MFIB*process*on*all*LCs*
4. MFIB*program*HW*forwarding*tables*in*NP,*Bridge*FPGA*and*Fabric*interface*ASIC*
5. SoRware*switched*mulEcast*packet*or*data*packet*for*protocol*signaling*is*sent*to*local*line*card*CPU*
Switch*Fabric*
NP0$PHY$
NP2$
NP3$
NP1$
FIA*B0
B1
PIM* IGMP*
MRIB*
MFIB*
2*
1*
3*
4*
CPU$
CPU$5*
PHY$
PHY$
PHY$Switch*Fabric*
Crossbar$Fabric$ASIC$
Crossbar$Fabric$ASIC$
8 ASR9000 Multicast troubleshooting document, Cisco Systems Inc
3 Packet flow and debugging commands at high level: Below diagram shows commands, which can be executed to trace the packet from ingress NPU to egress NPU.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public Presentation_ID 35
Typhoon LC
RSP
FABRIC
Trident LC NP3
NP2
NP1
NP0
Br1
Br0
FIA
show controller fabric fia bridge stats
show controller fabric fia stats
controller np ports all loc <> Show controller np counters <np> loc <
Ingress NP: ENET RX ! From Port FAB TX ! To fabric IPv4MC_DO_ALL_BUT_FRD " Punt only IPv4MC_DO_ALL ! punt to LC CPU IFIB ! IGMP, PIM Control packets
3x10GE
SFP +
3x10GE
SFP +
3x10GE
SFP +
3x10GE
SFP +
3x10GE
SFP +
3x10GE
SFP +
3x10GE
SFP +
3x10GE
SFP +
Switch Fabric A
SIC
FIA
FIA
FIA
FIA NP1
NP2
NP3
NP4
NP5
NP6
NP7
NP8
3x 10G
3x 10G
3x 10G
3x 10G
3x 10G
3x 10G
3x 10G
controller np ports all loc <>
Show controller np counters <np> loc < Egress NP: ENET FAB RX ! From Fabric FAB TX ! to TM LOOPBACK RX ! from TM ENET TX ! to port
RP/0/RSP0/CPU0:asr9k-‐3#show lpts pifib hardware police loc 0/4/CPU0 | in “IGMP|PIM” -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Node 0/4/CPU0: -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Burst = 100ms for all flow types -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ FlowType Policer Type Cur. Rate Def. Rate Accepted Dropped -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐ PIM-‐mcast-‐default 109 Static 2000 2000 0 0 PIM-‐mcast-‐known 176 Static 2000 2000 0 0 PIM-‐ucast 110 Static 1500 1500 0 0 IGMP 111 Static 3000 3000 369376 0 RP/0/RSP0/CPU0:asr9k-‐3# RP/0/RSP0/CPU0:asr9k-‐3#show lpts pifib hardware entry statistics location 0/5/CPU0 12 IPV4 * IGMP Te0/5/0/1 LU(30) 251/0 224.0.0.1,any any,any 14 IPV4 * PIM Te0/5/0/1 LU(30) 501/0 224.0.0.13,any any,any 236 IPV4 * IGMP any LU(30) 6967/0 any,any any,any 237 IPV4 * PIM any LU(30) 0/0 any,any any,any 261 IPV4 * IGMP Optimized LU(30) 0/0 224.0.0.22,any any,any
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 9
Following diagram outlines set of show commands, which can be executed to trace the packet and to debug if multicast stream is programmed correctly at software and hardware level.
4 Testbed topology: Following testbed topology used for demonstrating troubleshooting section as well to explain packet path.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public Presentation_ID 36
L3 Multicast Show CLIs
10
ASR9000 Multicast troubleshooting document, Cisco Systems Inc
5 Verifying the mrib, mfib and IGMP info This section walks you through verification of programming of control plane in RP using mrib (Multicast Routing Information base), which is used by MFIB to program the hardware. NOTE: Role of the routers in the above setup: asr9k-‐3 is the last hop router for the group 225.0.0.1 and 225.0.0.2 Asr9k-‐2 is the first hop router for the group 225.0.0.1 and 225.0.0.2 • Step 1: Check if there are receivers for the groups on asr9k-‐3
o Following output shows that 2 receivers are joining group 225.0.0.1 and one receiver is interested in group 225.0.0.2
RP/0/RSP0/CPU0:ASR9K-‐3#show igmp group | include 225. 225.0.0.1 GigabitEthernet0/4/0/3.102 00:28:52 00:01:34 42.0.1.1 225.0.0.1 GigabitEthernet0/4/0/10.101 2d07h 00:01:29 33.0.2.2 225.0.0.2 GigabitEthernet0/4/0/10.101 2d07h 00:01:29 33.0.2.2 RP/0/RSP0/CPU0:ASR9K-‐3# RP/0/RSP0/CPU0:ASR9K-‐3#show igmp groups 225.0.0.1 IGMP Connected Group Membership Group Address Interface Uptime Expires Last Reporter 225.0.0.1 GigabitEthernet0/4/0/3.102 00:29:10 00:01:15 42.0.1.1 225.0.0.1 GigabitEthernet0/4/0/10.101 2d07h 00:01:11 33.0.2.2
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public Presentation_ID 39
Receiver Gig0/4/0/10.101 Join 225.0.0.1,
225.0.0.2
Source Gig0/4/0/10.100
(142.0.0.2, 225.0.0.1/225.0.0.2)
Gig0/4/0/2
(142.0.0.2, 225.0.0.1/225.0.0.2)
(142.0.0.2, 225.0.0.1/225.0.0.2)
interface)GigabitEthernet0/4/0/10.101)!ipv4!address!33.0.2.1!255.255.255.0!!encapsulation!dot1q!101!interface)GigabitEthernet0/4/0/3.102)!ipv4!address!42.0.1.2!255.255.255.0!!encapsulation!dot1q!102!interface)TenGigE0/5/0/1)!ipv4!address!40.0.75.2!255.255.255.0!!!multicast;routing!!address;family!ipv4!interface!all!enable!router!pim!!address;family!ipv4!!!rp;address!110.0.0.24!interface)TenGigE0/5/0/1))))enable)))interface)GigabitEthernet0/4/0/3.102))))enable)interface)GigabitEthernet0/4/0/10.101))))enable)RP/0/RSP0/CPU0:ASR9K;3#!
Receiver Gig0/4/0/3.102 Join 225.0.0.1
igmp v2
Ten0/5/0/1
multicast;routing!!address;family!ipv4!interface!all!enable!router!pim!!address;family!ipv4!!)rp:address)110.0.0.24)interface)GigabitEthernet0/4/0/2)!!!enable!interface)GigabitEthernet0/4/0/10.100)!!!enable!RP/0/RSP0/CPU0:ASR9K;2#!
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 11
RP/0/RSP0/CPU0:ASR9K-‐3# RP/0/RSP0/CPU0:ASR9K-‐3#show igmp groups 225.0.0.1 detail Interface: GigabitEthernet0/4/0/3.102 Group: 225.0.0.1 Uptime: 00:29:16 Router mode: EXCLUDE (Expires: 00:02:09) Host mode: INCLUDE Last reporter: 42.0.1.1 Source list is empty Interface: GigabitEthernet0/4/0/10.101 Group: 225.0.0.1 Uptime: 2d07h Router mode: EXCLUDE (Expires: 00:02:05) Host mode: INCLUDE Last reporter: 33.0.2.2 Source list is empty RP/0/RSP0/CPU0:ASR9K-‐3#
• Step 2: Verify mrib table is programmed properly in control-‐plane (RSP). The MRIB table
is similar to mroute table in IOS. Output from last and first hop router is below: RP/0/RSP1/CPU0:asr9k-‐2#show mrib route 225.0.0.1 IP Multicast Routing Information Base Entry flags: L -‐ Domain-‐Local Source, E -‐ External Source to the Domain, C -‐ Directly-‐Connected Check, S -‐ Signal, IA -‐ Inherit Accept, IF -‐ Inherit From, D -‐ Drop, MA -‐ MDT Address, ME -‐ MDT Encap, MD -‐ MDT Decap, MT -‐ MDT Threshold Crossed, MH -‐ MDT interface handle CD -‐ Conditional Decap, MPLS -‐ MPLS Decap, MF -‐ MPLS Encap, EX -‐ Extranet MoFE -‐ MoFRR Enabled, MoFS -‐ MoFRR State, MoFP -‐ MoFRR Primary MoFB -‐ MoFRR Backup Interface flags: F -‐ Forward, A -‐ Accept, IC -‐ Internal Copy, NS -‐ Negate Signal, DP -‐ Don't Preserve, SP -‐ Signal Present, II -‐ Internal Interest, ID -‐ Internal Disinterest, LI -‐ Local Interest, LD -‐ Local Disinterest, DI -‐ Decapsulation Interface EI -‐ Encapsulation Interface, MI -‐ MDT Interface, LVIF -‐ MPLS Encap, EX -‐ Extranet, A2 -‐ Secondary Accept (*,225.0.0.1) RPF nbr: 110.0.0.24 Flags: C Up: 2d22h Incoming Interface List Decapstunnel0 Flags: A, Up: 2d22h Outgoing Interface List GigabitEthernet0/4/0/2 Flags: F NS, Up: 2d22h (142.0.0.2,225.0.0.1) RPF nbr: 142.0.0.2 Flags: L Up: 4d05h Incoming Interface List GigabitEthernet0/4/0/10.100 Flags: A, Up: 4d03h Outgoing Interface List GigabitEthernet0/4/0/2 Flags: F NS, Up: 2d22h ç LI flag is not RP/0/RSP1/CPU0:asr9k-‐2#
• Detail output:
RP/0/RSP0/CPU0:asr9k-‐3#show mrib route 225.0.0.1 detail
12
ASR9000 Multicast troubleshooting document, Cisco Systems Inc
(*,225.0.0.1) Ver: 0x429a RPF nbr: 40.0.75.1 Flags: C, PD: Slotmask: 0x40 MGID: 19919 Up: 2d21h Incoming Interface List TenGigE0/5/0/1 Flags: A NS, Up: 2d21h Outgoing Interface List GigabitEthernet0/4/0/3.102 Flags: F NS LI, Up: 14:20:00 GigabitEthernet0/4/0/10.101 Flags: F NS LI, Up: 2d21h (142.0.0.2,225.0.0.1) Ver: 0x7163 RPF nbr: 40.0.75.1 Flags:, PD: Slotmask: 0x40 ç Used for Fabric Replication 0x40 == 0 0 0 1 0 0 0 0 0 0 (slot 4) MGID: 19918 ç Used by egress LC’s FIA and Bridge ASIC to replicate the packet. Up: 3d00h Incoming Interface List TenGigE0/5/0/1 Flags: A, Up: 3d00h ç Interface towards source (RPF to source) Outgoing Interface List GigabitEthernet0/4/0/3.102 Flags: F NS, Up: 14:20:00 ç interface towards receivers GigabitEthernet0/4/0/10.101 Flags: F NS, Up: 2d21h ç interface towards receivers RP/0/RSP0/CPU0:asr9k-‐3#
• For the group 225.0.0.2
RP/0/RSP0/CPU0:asr9k-‐3#show mrib route 225.0.0.2 detail -‐-‐-‐ snip -‐-‐-‐-‐ (*,225.0.0.2) Ver: 0x7c9b RPF nbr: 40.0.75.1 Flags: C, PD: Slotmask: 0x40 MGID: 19920 Up: 2d23h Incoming Interface List TenGigE0/5/0/1 Flags: A NS, Up: 2d23h Outgoing Interface List GigabitEthernet0/4/0/10.101 Flags: F NS LI, Up: 2d23h (142.0.0.2,225.0.0.2) Ver: 0x2fba RPF nbr: 40.0.75.1 Flags:, PD: Slotmask: 0x40 ç Same slot mask as 225.0.0.1. Because egress LC is same. MGID: 19921 ç Different MGID. Packets replicated to only one NP. Up: 2d23h Incoming Interface List TenGigE0/5/0/1 Flags: A, Up: 2d23h Outgoing Interface List GigabitEthernet0/4/0/10.101 Flags: F NS, Up: 2d23h RP/0/RSP0/CPU0:asr9k-‐3#
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 13
5.1 Explanation of the mfib and mrib flags Description of the most common flags you see in mfib/mrib commands. • Flag A:
o Accept flag is set by control plane to indicate traffic from this interface can be accepted.
• Flag F: o Forward – set by the control plane to indicate that data is allowed to be forwarded
out this interface • Flag NS:
o Negate Signal* – set by the control plane to indicate whether or not a signal should be sent to the control plane when traffic is received on this interface.
• Flag L: o Local Source. Set on an S,G if Router is the PIM RP for that Group and its receiving
PIM Registers • Flag LI:
o Local Interest. Set when joins are directly connected to this router. See LI flag is not set on asr9k-‐2 router, which is directly connected to source but not to receivers.
o IGMP is interested in this route. Received a Report indicating interest for the group (and source) on that interface
5.2 MGID and FGID programming: The “show mrib …” command shows MGID and FGID values used by FIA and Fabric for multicast replication. Let us verify if values programmed are correct.
FGID: In the above show command output (show mrib route 225.0.0.1 detail) FGID value programmed is 0x40, which is for slot 4 as per below decode. 0 0 0 1 0 0 0 0 0 0 Slot 7 Slot 6 Slot 5 Slot 4 RSP1 RSP 0 Slot 3 Slot 2 Slot 1 Slot 0 Hence fabric will replicate traffic to LC 4, which is correct because both the receivers are on Slot 4 (0/4/0/10.101 and 0/4/0/3.102) MGID (Multicast Group ID) MGID programmed for the stream 225.0.0.1 is 19918. Content of this ID is can be different on each LC. Lets verify whether MGID values programmed correctly. Since our fabric is replicating packets to LC 4, we need to check content of MGID in LC 4. RP/0/RSP0/CPU0:asr9k-‐3#show controllers np ports all location 0/4/CPU0 Node: 0/4/CPU0: -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP Bridge Fia Ports
14
ASR9000 Multicast troubleshooting document, Cisco Systems Inc
-‐-‐ -‐-‐-‐-‐-‐-‐ -‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 0 0 0 GigabitEthernet0/4/0/30 -‐ GigabitEthernet0/4/0/39 1 0 0 GigabitEthernet0/4/0/20 -‐ GigabitEthernet0/4/0/29 2 1 0 GigabitEthernet0/4/0/10 -‐ GigabitEthernet0/4/0/19 çIGMP Join on 0/4/0/10 3 1 0 GigabitEthernet0/4/0/0 -‐ GigabitEthernet0/4/0/9 çIGMP Join on 0/4/0/3 RP/0/RSP0/CPU0:asr9k-‐3# RP/0/RSP0/CPU0:asr9k-‐3#show controllers mgidprgm mgidindex 19918 location 0/4/CPU0 Device MGID-‐Bits Client-‐Last-‐Modified ======================================================= FIA 10 MFIBV4 ß Replicated to Bridge-‐1 [Bridge-‐1 | Bridge-‐0] Bridge-‐0 0 MFIBV4 ß Not replicated here [NP 1 | NP 0] Bridge-‐1 11 MFIBV4 ß Replicated to NP 2 and 3 [NP 3|NP 2] RP/0/RSP0/CPU0:asr9k-‐3# RP/0/RSP0/CPU0:asr9k-‐3#show controllers mgidprgm mgidindex 19921 location 0/4/CPU0 Device MGID-‐Bits Client-‐Last-‐Modified ======================================================= FIA 10 MFIBV4 ß Replicated to Bridge-‐1 Bridge-‐0 0 MFIBV4 Bridge-‐1 1 MFIBV4 ç Replicated to NP 2 [NP-‐3| NP-‐2 ] RP/0/RSP0/CPU0:asr9k-‐3#
Another way to check MGID and FGID programming: You also see that content of the MGID for 225.0.0.1 and 225.0.0.2 are different. Below command gives great deal of information about replication taking place, MGID, FGID info as well as number of ports in each NP interested in the traffic.
RP/0/RSP0/CPU0:asr9k-‐3#show mfib hardware route olist 225.0.0.2 location 0/4/CPU0 LC Type: Trident A9K-‐40GE-‐E -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Legend: Route Information B: BACL check S: RPF Interface signal DC: Directly connected PL: Punt to LC CPU PR: Punt to RP PF: Punt if forwarded DR: Drop all RI: RPF interface FS: Fabric slotmask G: Multicast group ID M: Multicast leaf index NI: Not Installed Interface Information Intf: Interface OT: OLE Type U: uIDB index T: Table ID IC: HW IC flag B: HW BACL flag -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Source: 142.0.0.2 Group: 225.0.0.2 Mask: 64 RPF Int: Te0/5/0/1 Route Information -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ B S DC PL PR PF DR RI FS G M
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 15
-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ F F F F F F F 0xe000100 0x40 19921 3801 ç FGID and MGID values -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Interface Information -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP Intf OT U T IC B -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 2 Gi0/4/0/10.101 REG 85 1 F F -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ OLIST counts -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP: 0 1 2 3 Count: 0 0 1 0 ç Shows 1 port from NP 2 interested in traffic. -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ RP/0/RSP0/CPU0:asr9k-‐3#show mfib hardware route olist 225.0.0.1 location 0/4/CPU0 -‐-‐-‐-‐-‐-‐ SNIP-‐-‐-‐-‐ Source: 142.0.0.2 Group: 225.0.0.1 Mask: 64 RPF Int: Te0/5/0/1 Route Information -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ B S DC PL PR PF DR RI FS G M -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ F F F F F F F 0xe000100 0x40 19918 3797 çFGID and MGID values -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Interface Information -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP Intf OT U T IC B -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 2 Gi0/4/0/10.101 REG 85 1 F F ç NP and Outgoing port info 3 Gi0/4/0/3.102 REG 109 1 F F ç NP and Outgoing port info -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ OLIST counts -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP: 0 1 2 3 Count: 0 0 1 1 ç Shows 1 port from NP 2 and 3 interested in traffic. -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ RP/0/RSP0/CPU0:asr9k-‐3#
5.3 Checking multicast programming in MFIB: MFIB is a key component in multicast architecture. MFIB receives updates from MRIB and updates the platform control plane. MFIB in LC will store routes only relevant to the LC using selective route downloads. First we build software mfib table based on mrib routing table. This is used incase packets needs to be software switched.
• Verifying mfib programming:
RP/0/RSP0/CPU0:asr9k-‐3#show mfib route 225.0.0.1 IP Multicast Forwarding Information Base Entry flags: C -‐ Directly-‐Connected Check, S -‐ Signal, D -‐ Drop, IA -‐ Inherit Accept, IF -‐ Inherit From, MA -‐ MDT Address, ME -‐ MDT Encap, MD -‐ MDT Decap, MT -‐ MDT Threshold Crossed, MH -‐ MDT interface handle, CD -‐ Conditional Decap,
16
ASR9000 Multicast troubleshooting document, Cisco Systems Inc
DT -‐ MDT Decap True, EX -‐ Extranet MoFE -‐ MoFRR Enabled, MoFS -‐ MoFRR State Interface flags: F -‐ Forward, A -‐ Accept, IC -‐ Internal Copy, NS -‐ Negate Signal, DP -‐ Don't Preserve, SP -‐ Signal Present, EG -‐ Egress, EI -‐ Encapsulation Interface, MI -‐ MDT Interface, EX -‐ Extranet, A2 -‐ Secondary Accept Forwarding/Replication Counts: Packets in/Packets out/Bytes out Failure Counts: RPF / TTL / Empty Olist / Encap RL / Other (*,225.0.0.1), Flags: C Up: 00:00:21 Last Used: never SW Forwarding Counts: 0/0/0 SW Replication Counts: 0/0/0 SW Failure Counts: 0/0/0/0/0 TenGigE0/5/0/1 Flags: A NS, Up:00:00:21 GigabitEthernet0/4/0/3.102 Flags: NS, Up:00:00:21 GigabitEthernet0/4/0/10.101 Flags: NS, Up:00:00:21 (142.0.0.2,225.0.0.1), Flags: Up: 00:00:21 Last Used: never SW Forwarding Counts: 0/0/0 SW Replication Counts: 0/0/0 SW Failure Counts: 0/0/0/0/0 TenGigE0/5/0/1 Flags: A, Up:00:00:21 GigabitEthernet0/4/0/3.102 Flags: NS, Up:00:00:21 GigabitEthernet0/4/0/10.101 Flags: NS, Up:00:00:21 RP/0/RSP0/CPU0:asr9k-‐3# RP/0/RSP0/CPU0:asr9k-‐3#show mfib route 225.0.0.1 location 0/4/CPU0 -‐-‐-‐ snip -‐-‐-‐ (142.0.0.2,225.0.0.1), Flags: Up: 3d09h Last Used: never SW Forwarding Counts: 0/0/0 SW Replication Counts: 0/0/0 SW Failure Counts: 0/0/0/0/0 TenGigE0/5/0/1 Flags: A, Up:3d09h GigabitEthernet0/4/0/3.102 Flags: NS EG, Up:23:19:39 ç Traffic will be forwarded GigabitEthernet0/4/0/10.101 Flags: NS EG, Up:3d06h RP/0/RSP0/CPU0:asr9k-‐3#
• Now check if packets are getting forwarded in hardware using mfib commands:
RP/0/RSP0/CPU0:asr9k-‐3#show mfib route statistics 225.0.0.1 142.0.0.2 detail IP Multicast Forwarding Information Base Entry flags: C -‐ Directly-‐Connected Check, S -‐ Signal, D -‐ Drop, IA -‐ Inherit Accept, IF -‐ Inherit From, MA -‐ MDT Address, ME -‐ MDT Encap, MD -‐ MDT Decap, MT -‐ MDT Threshold Crossed, MH -‐ MDT interface handle, CD -‐ Conditional Decap, DT -‐ MDT Decap True Interface flags: F -‐ Forward, A -‐ Accept, IC -‐ Internal Copy, NS -‐ Negate Signal, DP -‐ Don't Preserve, SP -‐ Signal Present, EG -‐ Egress, EI -‐ Encapsulation Interface, MI -‐ MDT Interface SW/HW Forwarding/Replication Counts: Packets in/Packets out/Bytes out SW Failure Counts: RPF / TTL / Empty Olist / Encap RL / Other
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 17
HW Drop Counts: Ingress / Egress HW Forwarding Rates: bps In/pps In/bps Out/pps Out (142.0.0.2,225.0.0.1), Flags: Up: 00:12:57 Last Used: never SW Forwarding Counts: 0/0/0 SW Replication Counts: 0/0/0 SW Failure Counts: 0/0/0/0 HW Forwarding Counts: N/A /N/A /N/A HW Replication Counts: N/A /N/A /N/A HW Drop Counts: N/A /N/A HW Forwarding Rates: N/A /N/A /N/A /N/A TenGigE0/5/0/1 Flags: A, Up:00:12:57 GigabitEthernet0/4/0/3.102 Flags: NS, Up:00:12:57 GigabitEthernet0/4/0/10.101 Flags: NS, Up:00:12:57 RP/0/RSP0/CPU0:asr9k-‐3# RP/0/RSP0/CPU0:asr9k-‐3#show mfib route statist 225.0.0.1 142.0.0.2 detail loc 0/4/CPU0 -‐-‐ SNIP -‐-‐ (142.0.0.2,225.0.0.1), Flags: Up: 3d09h Last Used: never SW Forwarding Counts: 0/0/0 SW Replication Counts: 0/0/0 SW Failure Counts: 0/0/0/0 HW Forwarding Counts: 0/169493467/7796699482 HW Replication Counts: 0/736054494/33858506724 HW Drop Counts: 0/0 HW Forwarding Rates: N/A /N/A /725395/1970 TenGigE0/5/0/1 Flags: A, Up:3d09h GigabitEthernet0/4/0/3.102 Flags: NS EG, Up:23:32:24 GigabitEthernet0/4/0/10.101 Flags: NS EG, Up:3d06h RP/0/RSP0/CPU0:asr9k-‐3#
6 Verifying hardware mroute/mfib Table Following command output shows the whether packets forwarded in hardware for a given (S,G):
18
ASR9000 Multicast troubleshooting document, Cisco Systems Inc
RP/0/RSP0/CPU0:asr9k-‐3#show mfib hardware route stati 225.0.0.1 142.0.0.2 loc 0/5/CPU0 LC Type: Typhoon A9K-‐MOD160-‐SE -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Legend: N: NP ID R: Received F: Forwarded P: Punted to CPU ID: Ingress Drop ED: Egress Drop Source: 142.0.0.2 Group: 225.0.0.1 Mask:64 -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP R(packets:bytes)/F(packets:bytes)/P(packets)/ID(packets)/ED(packets) -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 0 406759:18710914 / 0:0 / 0 / 0 / 0 ç THIS NP is receiving traffic from wire 1 0:0 / 0:0 / 0 / 0 / 0 2 0:0 / 0:0 / 0 / 0 / 0 3 0:0 / 0:0 / 0 / 0 / 0 -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ No OLIST interfaces found for this route RP/0/RSP0/CPU0:asr9k-‐3# RP/0/RSP0/CPU0:asr9k-‐3#show mfib hardware route stati 225.0.0.1 142.0.0.2 loc 0/4/CPU0 LC Type: Trident A9K-‐40GE-‐E -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Legend: N: NP ID R: Received F: Forwarded P: Punted to CPU ID: Ingress Drop ED: Egress Drop Source: 142.0.0.2 Group: 225.0.0.1 Mask:64 -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP R(packets:bytes)/F(packets:bytes)/P(packets)/ID(packets)/ED(packets) -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 0 0:0 / 0:0 / 0 / 0 / 0 1 0:0 / 0:0 / 0 / 0 / 0 2 0:0 / 434208:19973568 / 0 / 0 / 0 ç This NP is sending traffic out on wire 3 0:0 / 443309:20392214 / 0 / 0 / 0 ç This NP is sending traffic out on wire -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Interface Statistics: -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ C Interface F/P/D (packets:bytes) -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 2 Gi0/4/0/10.101 434208:19973568 / 0:0 / 0:0 ç Outgoing interface on the NP2 3 Gi0/4/0/3.102 443309:20392214 / 0:0 / 0:0 ç Outgoing interface on the NP3 -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ RP/0/RSP0/CPU0:asr9k-‐3#
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 19
7 Tracing the packet through Fabric and ASICs: At very high-‐level path taken by a packet is as follows. Only Trident LC has bridge asic. PHY è ingress NP è Bridge è FIA è Fabric è FIA è Bridge è Egress NP è PHY
Lets check the counters in each asic using show commands to trace the packet getting forwarded.
7.1 Ingress NP counters: RP/0/RSP0/CPU0:asr9k-‐3#show controllers np counters np0 location 0/5/CPU0 Node: 0/5/CPU0: -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Show global stats counters for NP0, revision v2 Read 23 non-‐zero NP counters: Offset Counter FrameValue Rate (pps) -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 21 MDF_TX_FABRIC 23279 4001 29 PARSE_FAB_RECEIVE_CNT 7 1 33 PARSE_INTR_RECEIVE_CNT 43 7 41 PARSE_ENET_RECEIVE_CNT 23278 4001 RP/0/RSP0/CPU0:asr9k-‐3#
7.2 Ingress FIA counters RP/0/RSP0/CPU0:asr9k-‐3#show controllers fabric fia stats location 0/5/CPU0 ********** FIA-‐0 ********** Category: count-‐0 From Unicast Xbar[0] 6 From Unicast Xbar[1] 4 From Unicast Xbar[2] 0 From Unicast Xbar[3] 0 From MultiCast Xbar[0] 0 From MultiCast Xbar[1] 0 From MultiCast Xbar[2] 0 From MultiCast Xbar[3] 0 To Unicast Xbar[0] 3 To Unicast Xbar[1] 3 To Unicast Xbar[2] 0 To Unicast Xbar[3] 0 To MultiCast Xbar[0] 17829 ç To MultiCast Xbar[1] 17829 ç To MultiCast Xbar[2] 0 To MultiCast Xbar[3] 0 To Line Interface[0] 0 To Line Interface[1] 10 From Line Interface[0] 0 From Line Interface[1] 35664 Ingress drop: 0 Egress drop: 0
20
ASR9000 Multicast troubleshooting document, Cisco Systems Inc
Total drop: 0 ********** FIA-‐1 ********** RP/0/RSP0/CPU0:asr9k-‐3#
7.3 Egress LC FIA counters: RP/0/RSP0/CPU0:asr9k-‐3#show controllers fabric fia stats location 0/4/CPU0 ********** FIA-‐0 ********** Category: count-‐0 From Line Interface[0] 6 From Line Interface[1] 24 To Line Interface[0] 6 To Line Interface[1] 663542 To Unicast Xbar[0] 30 To Unicast Xbar[1] 0 To Unicast Xbar[2] 0 To Unicast Xbar[3] 0 To MultiCast Xbar[0] 0 To MultiCast Xbar[1] 0 To MultiCast Xbar[2] 0 To MultiCast Xbar[3] 0 From Unicast Xbar[0] 43 From Unicast Xbar[1] 0 From Unicast Xbar[2] 0 From Unicast Xbar[3] 0 From MultiCast Xbar[0] 331753 ç From Fabric From MultiCast Xbar[1] 331752 ç From Fabric From MultiCast Xbar[2] 0 From MultiCast Xbar[3] 0 Ingress drop: 0 Egress drop: 0 Total drop: 0
7.4 Egress NP counters RP/0/RSP0/CPU0:asr9k-‐3#show controllers np ports all location 0/4/CPU0 Node: 0/4/CPU0: -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP Bridge Fia Ports -‐-‐ -‐-‐-‐-‐-‐-‐ -‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 0 0 0 GigabitEthernet0/4/0/30 -‐ GigabitEthernet0/4/0/39 1 0 0 GigabitEthernet0/4/0/20 -‐ GigabitEthernet0/4/0/29 2 1 0 GigabitEthernet0/4/0/10 -‐ GigabitEthernet0/4/0/19 3 1 0 GigabitEthernet0/4/0/0 -‐ GigabitEthernet0/4/0/9 RP/0/RSP0/CPU0:asr9k-‐3# RP/0/RSP0/CPU0:asr9k-‐3#show controllers np counters np2 location 0/4/CPU0 Node: 0/4/CPU0: -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Show global stats counters for NP2, revision v3 Read 16 non-‐zero NP counters: Offset Counter FrameValue Rate (pps) -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 23 PARSE_FABRIC_RECEIVE_CNT 11349830 4000 24 PARSE_LOOPBACK_RECEIVE_CNT 5674751 2000 30 MODIFY_ENET_TRANSMIT_CNT 11349784 4000 38 MODIFY_MCAST_FLD_LOOPBACK_CNT 5674751 2000 RP/0/RSP0/CPU0:asr9k-‐3#show controllers np counters np3 location 0/4/CPU0 Node: 0/4/CPU0:
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 21
-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Show global stats counters for NP3, revision v3 Read 19 non-‐zero NP counters: Offset Counter FrameValue Rate (pps) -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 23 PARSE_FABRIC_RECEIVE_CNT 5684472 2000 24 PARSE_LOOPBACK_RECEIVE_CNT 47 0 30 MODIFY_ENET_TRANSMIT_CNT 5684425 2000 RP/0/RSP0/CPU0:asr9k-‐3#
8 Debugging multicast Process Memory: This section outlines some basic commands, which can help to troubleshoot whether system is running with low memory, memory leak and or process crashes. • Collect the output of “show process memory location <>” and check if memory in
dynamic column increasing. If so, this might be sign of one or more process holding up memory and not releasing it. Please take few snap shot of the output. Output shows memory utilization for only multicast process.
RP/0/RSP0/CPU0:asr9k-‐3#show processes memory location 0/5/CPU0 | in ipv4_mfwd ID Text Data Stack Dynamic Process -‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ -‐-‐-‐-‐-‐-‐-‐ 237 475136 192512 126976 12337152 ipv4_mfwd_partner RP/0/RSP0/CPU0:asr9k-‐3#
9 Debugging Multicast and related processes: • Following outputs were taken from one of the Service request for the explanation
purpose. This output shows one of the multicast process blocked • Check if multicast process is blocked:
RP/0/RSP0/CPU0:on-‐bari-‐vbr1#sh processes blocked location 0/rsp0/cpu0 Jid Pid Tid Name State TimeInState Blocked-‐on 65549 16397 1 ksh Reply 6572:57:32:0613 16396 devc-‐conaux 65554 57362 2 devb-‐umass Reply 0:00:07:0644 45096 io-‐usb 96 40996 2 umass-‐enum Reply 6572:57:36:0954 1 kernel 96 40996 6 umass-‐enum Reply 6572:57:31:0685 45096 io-‐usb 52 69677 2 attachd Reply 6572:57:33:0322 49196 eth_server 52 69677 3 attachd Reply 6572:57:33:0321 24595 mqueue 65582 57390 2 devb-‐umass Reply 0:00:37:0655 45096 io-‐usb 87 69680 6 qnet Reply 0:00:00:0010 49196 eth_server 51 69684 2 attach_server Reply 6572:57:33:0215 24595 mqueue 65594 69690 2 devb-‐umass Reply 0:00:05:0158 45096 io-‐usb 334 221279 1 tftp_server Reply 2066:33:24:0177 24595 mqueue 241 258252 2 lpts_fm Reply 0:04:50:0486 245891 lpts_pa 65741 59502797 1 exec Reply 0:01:13:0410 258244 devc-‐vty 353 1835278 6 ipv4_mfwd_partner Mutex 16:33:20:0238 69684-‐56184 #0 attach_server 65844 60350772 1 exec Reply 0:00:00:0114 1 kernel 65845 61145397 1 more Reply 0:00:00:0065 24593 pipe
22
ASR9000 Multicast troubleshooting document, Cisco Systems Inc
65846 61145398 1 show_processes Reply 0:00:00:0000 1 kernel RP/0/RSP0/CPU0:on-‐bari-‐vbr1#
• Above output shows that ipv4_mfwd_partner process blocked on attach_server. Lets check
status of the attach_server process • Check state of the attach_server process and ipv4_mfwd_partner
RP/0/RSP0/CPU0:on-‐bari-‐vbr1#sh processes attach_server Thu May 10 15:42:24.745 EDT Job Id: 51 ç=== Job ID PID: 69684 ç=== PID Executable path: /asr9k-‐os-‐4.0.1/bin/attach_server Instance #: 1 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Wed Aug 10 15:02:46 2011 Process state: Run Package state: Normal core: MAINMEM Max. core: 0 Level: 39 MaintModeProc: ON Placement: None startup_path: /pkg/init.d/attach_server.init Process cpu time: 0.012 user, 0.000 kernel, 0.012 total JID TID CPU Stack pri state TimeInState HR:MM:SS:MSEC NAME 51 1 0 20K 10 Receive 6576:39:04:0327 0:00:00:0012 attach_server 51 2 1 20K 55 Reply 6576:39:31:0128 0:00:00:0000 attach_server -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ RP/0/RSP0/CPU0:on-‐bari-‐vbr1#show processes ipv4_mfwd_partner Thu May 10 15:44:38.446 EDT Job Id: 353 PID: 1835278 Executable path: /disk0/iosxr-‐mcast-‐4.0.1/bin/ipv4_mfwd_partner Instance #: 1 Version ID: 00.00.0000 Respawn: ON Respawn count: 1 Max. spawns per minute: 12 Last started: Fri Aug 19 21:38:29 2011 Process state: Run Package state: Normal core: MAINMEM Max. core: 0 Level: 99 Placement: None startup_path: /install/iosxr-‐mcast-‐4.0.1/startup/ipv4_mfwd.startup Ready: 0.423s Process cpu time: 222829.394 user, 60507.334 kernel, 283336.728 total JID TID CPU Stack pri state TimeInState HR:MM:SS:MSEC NAME 353 1 0 76K 10 Receive 0:00:00:0040 48:58:31:0650 ipv4_mfwd_partner 353 6 1 76K 10 Mutex 20:17:31:0794 28:39:32:0556 ipv4_mfwd_partner
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 23
Collect output of “show follow process <pid>” if the process is in blocked state.
10 Additional Commands: Some additional useful commands: • Show mfib interface loca <ingress/egress LC> • Show pim topology • Show drops ç Take this output 2-‐3 times with some gap • Show controller fabric fia q-‐depth loc <ingress/egress LC> ç 2-‐3 times • Show controller pm location <ingress/Egress LC> • Show controller fabric fia stat loc <ingress/egress LC> ç 2-‐3 times • Show log • Show tech-‐support multicast hardware <group> loc <ingress/egress LC> • Show controllers np tm counter loc <ingress/egress LC> ç 2-‐3 times • Show tech-‐support fabric • Show mfib hardware <route/connection/interface> loc • Show mfib hardware ltrace <init/error/warning/event> • Show controllers np struct 22 all location [egress] • Show mfib hardware route summary loc <> • Show mfib hardware trace location <>
11 Multicast drops counters in NP: • IPV4MC_DO_ALL_EXCD
§ Punt policier rate limited packet drops • IPV4MC_DO_ALL_BUT_FWD_EXCD
§ Punt policier rate limited packet drops • MODIFY_RPF_FAIL_DROP_CNT
§ Ingress on RPF interface • RESOLVE_IPM4_ING_RTE_DROP_CNT
§ No multicast route found on ingress • RESOLVE_IPM4_EGR_RTE_DROP_CNT
§ No multicast route found on ingress • RESOLVE_IPM4_NO_OLIST_DROP_CNT
§ No multicast output interfaces found on egress route • RESOLVE_IPM4_FILTER_DROP_CNT
§ Ingress interface = egress interface • RESOLVE_IPM4_TTL_DROP_CNT
§ TTL exceeded on packet • PUNT_IFIB (L3 PUNT)
§ PIM/IGMP control plane packets punted to RP • IPV4MC_DO_ALL
24
ASR9000 Multicast troubleshooting document, Cisco Systems Inc
§ Multicast traffic punted to LC CPU and not forwarded • IPV4MC_DO _ALL_BUT_FWD
§ Multicast traffic punted to LC CPU and forwarded
• For further explanation on drop counters: o Google for “asr9000 NP counters”:
§ https://supportforums.cisco.com/docs/DOC-‐26566
12 Checking multicast resource Allocation in hardware/software: RP/0/RSP0/CPU0:asr9k-‐3#show mfib hardware resource-‐counters location 0/5/CPU0 LC Type: Typhoon A9K-‐MOD160-‐SE Memory alloc stats -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Type Allocated Freed Delta -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ global 0 0 0 table extension 1 0 1 route extension 11 2 9 interface extension 12 2 10 idb extension 7 0 7 srh 0 0 0 uidb data 3 3 0 EDM bag data 2 0 2 encap extension 0 0 0 regdb extension 0 0 0 encap leaf extension 0 0 0 -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP Structure Resource Usage -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP rte leaf rte node punt sw ole hw ole mofrr mvpn encap ole -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 0 9 9 2 0 0 0 0 0 1 9 9 0 0 0 0 0 0 2 9 9 0 0 0 0 0 0 3 9 9 0 0 0 0 0 0 Max 131072 131072 131072 65536 65536 4096 131072 98304 -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP Structure Shared IPv4/IPv6 Resource Usage -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP rte node rte node punt punt ole ole ipv4 total ipv4 total ipv4 total -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ 0 9 9 2 2 0 0 1 9 9 0 0 0 0 2 9 9 0 0 0 0 3 9 9 0 0 0 0 Max 131072 131072 131072 131072 65536 65536 -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ RP/0/RSP0/CPU0:asr9k-‐3#
ASR9000 Multicast troubleshooting document, Cisco Systems Inc 25
RP/0/RSP0/CPU0:asr9k-‐3#show mfib hardware connection location 0/5/CPU0 LC Type: Typhoon A9K-‐MOD160-‐SE -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ Server Status Connect Disconnect -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ UIDB connected 1 0 PRM connected 1 0 MGID FABRIC LIB connected 1 0 MGID REFCOUNT LIB connected 1 0 -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NP State: Running; Last Event: Running -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ RP/0/RSP0/CPU0:asr9k-‐3# RP/0/RSP0/CPU0:asr9k-‐3#show mfib hardware route summary location 0/5/CPU0 LC Type: Typhoon A9K-‐MOD160-‐SE H/W IP Multicast Forwarding Information Base Summary No. of (*,G) routes = 7 No. of (S,G) routes = 2 No. of (S,G) MoFRR routes = 0, Maximum supported MoFRR routes = 2048 RP/0/RSP0/CPU0:asr9k-‐3#