RST-331 Troubleshooting ATM MPLS.pdf

7/23/2019 RST-331 Troubleshooting ATM MPLS.pdf

http://slidepdf.com/reader/full/rst-331-troubleshooting-atm-mplspdf 1/51

Copyright © 1998, Cisco Systems, Inc. All rights reserved. Printed in USA.Presentation_ID.scr 1

RST-3312901_05_2001_c1 © 2001, Cisco Systems, Inc. All rights reserved.

RST-3312901_05_2001_c1 © 2001, Cisco Systems, Inc. All rights reserved. 2 © 2001, Cisco Systems, Inc. All rights reserved. 2 © 2001, Cisco Systems, Inc. All rights reserved. 2




3RST-3312901_05_2001_c1 © 2001, Cisco Systems, Inc. All rights reserved. © 2001, Cisco Systems, Inc. All rights reserved. © 2001, Cisco Systems, Inc. All rights reserved.

TroubleshootingATM MPLS

Session RST-331


Table of Contents

• ATM MPLS Overview

• LSC-Switch Problems

• Bring-Up Problems

• LSR-LSR Troubleshooting

• LVC Problems and Network-Wide

Troubleshooting• Multiple Controller Problems

• Summary




5RST-3312901_05_2001_c1 © 2001, Cisco Systems, Inc. All rights reserved. © 2001, Cisco Systems, Inc. All rights reserved. © 2001, Cisco Systems, Inc. All rights reserved. 5

ATM MPLS Overview


ATM MPLS

• MPLS adds IP routingcontrol to an ATM

switch

• MPLS enables ATMswitches to also actlike routers

Fully support IP, alongwith frame relay and ATM,

on shared ATM backbone

Provides optimal IPforwarding capabilityon an ATM network





PPP Header

(Packet over SONET/SDH)

ATM Cell Header

LAN MAC Label Header

Label Header Label Header PPP Header PPP Header Layer 3 Header Layer 3 Header

HECHEC

LabelLabel

DATADATACL PCL PPTIPTIVCIVCIGFCGFC VPIVPI

Label Header Label Header MAC Header MAC Header Layer 3 Header Layer 3 Header

Encapsulations


ATM Switch Label Switch

Controller

ATM Label

Switch Router

++ ==

ATM Label Switch Router

• The Label Switch Controller is an MPLS router

with functionality to control an ATM switch usingVSI (Virtual Switch Interface)

• Separation of routing and forwarding





Firmware and DriversFirmware and Drivers

Virtual Switch SlavePlatform

Software

VSI

VSI Master

MPLS SoftwareMPLS Software Network-Layer

Software

ConnectionRequests

SwitchInfoUpdates

LSC

Controlled Switch

VSI

Virtual Switch Interface (VSI)

• VSI is an interface between network-layer

software and platform connection software

• VSI allows a cross-connect to be establishedat a switch


• Control of switch cross-connects

• Switch configuration discovery

• Monitoring of port and VC statistics

• Resynchronization

Virtual Switch Interface (VSI)





• Allows platform performance to be scaled using

distributed processing, i.e. across several cards

• Multiple paths into platform eliminates anycentral bottleneck

Master

Controller (e.g. MPLS, PNNI)Controller (e.g. MPLS, PNNI)Network Software

VSI

Platform Software

VSI VSI

Slave 1

Card 1Card 1

Slave 2

Card 2Card 2

Slave 3

Card 3Card 3

Multiple Slave Model


IP RoutingIP Routing

LDP SignalingLDP Signaling

L2 VCsL2 VCs

PNNI Routing

UNI/NNI SignalingUNI/NNI Signaling

MPLS

Stack

ATM Forum

Stack

MPLS Is an ATM Control Stack

• The MPLS protocol stack consists of IP routing and MPLS

signaling, together setting up connectivity at Layer 2

• Label VCs (LVCs) are not PVCs or SVCs

• LVCs, SVCs and PVCs can exist on same link: different VPIs





BXM 3BXM 3

Port

LDP/RoutingSignaling VCs

BXM 1BXM 1

ATM Link

Label Switch Controller on 7xxx Router

VSI Inter-SlaveControl x-conns

BXM 2BXM 2

VSI Master-SlaveControl VCs

Label-Controlled

VC x-connsConfig Control

BPX Switch

Switch, LSC, and VSI: More Details

VSI Master

LSC and Routing SoftwareLSC and Routing Software

BXM 1BXM 1BXM 1VSI Slave 1

VSI Slave 2 VSI Slave 3

BCCBCC


LSC-Switch Problems





LSC

Controlled Switch

VSI

• Symptom: No VSIsessions established

State shows UNKNOWN

• Scenario

wsw-7206 -3a#show controllers vsi session

Interface Session VCD VPI/VCI Switch/Slave Ids Session State ATM1/0 0 1 0/40 0/0 UNKNOWN

ATM1/0 1 2 0/41 0/0 UNKNOWN

ATM1/0 2 3 0/42 0/0 UNKNOWN

ATM1/0 3 4 0/43 0/0 UNKNOWN

ATM1/0 4 5 0/44 0/0 UNKNOWN

ATM1/0 5 6 0/45 0/0 UNKNOWN ATM1/0 6 7 0/46 0/0 UNKNOWN

ATM1/0 7 8 0/47 0/0 UNKNOWN

ATM1/0 8 9 0/48 0/0 UNKNOWN

ATM1/0 9 10 0/49 0/0 UNKNOWN

ATM1/0 10 11 0/50 0/0 UNKNOWN ATM1/0 11 12 0/51 0/0 UNKNOWN ATM1/0 12 13 0/52 0/0 UNKNOWN

ATM1/0 13 14 0/53 0/0 UNKNOWN

wsw-7206 -3a#

No Communicationbetween LSC and Controlled Switch


wsw-7206-3a#show controllers vsi session 0Interface: ATM1/0 Session number: 0 VCD: 1 VPI/VCI: 0/40Switch type: Switch id: 0Controller id: 1 Slave id: 0…

Possible Cause 1

• Different base-vc for VSI master-slave channels

• The base-vc in the controller in this case is 0/40(corresponding to slave 0)





b8620-3a TN Cisco BPX 8620 9.3.11 Apr. 10 2001 23:49 EST

BPX 8620 VSI controller information

Ctrl Id Part Id Control_VC Trunk Ctrlr Type Intfc VPI VCIRange

3 1 0 100-114 3.1 VSI VSI

Last Command: dspctrlrs

Next Command:

Possible Cause 1

• In BPX/IGX can be seen with dspctrlrs


wsw-7206-3a(config-if)#tag-control-protocol vsi ? base-vc VC to use for VSI protocolid Specify the controller id keepalive Timeout for VSI keepalive protocolretry VSI request timer and retry countslaves VSI slave count <cr> wsw-7206-3a(config-if)#


BPX 8620 Interface Shelf Information

Trunk Name Type Part Id Ctrl Id Control_VC Alarm

VPI VCIRange3.1 VSI VSI 1 3 0 40-54 OK

Last Command: addshelf 3.1 v 3 1 0 40

Shelf has been added Next Command:

Solution Problem 1• Modify the base-vc either in the master or the slave





Possible Cause 2

• Base-VCs are the same but still no luck…

• Different controller ID in master and slaves

wsw-7206-3a#show controllers vsi session 0Interface: ATM1/0 Session number: 0 VCD: 1 VPI/VCI: 0/40Switch type: Switch id: 0Controller id: 1 Slave id: 0…

wsw-7206-3a#debug vsi errors02:18:37: VSI Master: parse error (unexpected controller id) in IFC GET CNFGTRAP rcvd on ATM1/0:0/42 (slave 2)02:19:29: VSI Master: got NAK reason 105 (unknown ctrler id) in GEN ERROR RSP





3 1 0 40-54 3.1 VSI VSI


Next Command:

Possible Cause 2

• In BPX/IGX can be seen with dspctrlrs





Solution Problem 2

• Modify the controller ID in either master or slave wsw-7206-3a(config-if)#tag-control-protocol vsi ? base-vc VC to use for VSI protocolid Specify the controller id keepalive Timeout for VSI keepalive protocolretry VSI request timer and retry countslaves VSI slave count <cr> wsw-7206-3a(config-if)#


BPX 8620 Interface Shelf Information

Trunk Name Type Part Id Ctrl Id Control_VC Alarm VPI VCIRange

3.1 VSI VSI 1 1 0 40-54 OK

Last Command: addshelf 3.1 v 1 1 0 40

Shelf has been added Next Command:

Default base-vc = 0/40Default id = 1


wsw-7206-3a#show controllers vsi sessionInterface Session VCD VPI/VCI Switch/Slave Ids Session State ATM1/0 0 1 0/40 0/0 UNKNOWN ATM1/0 1 2 0/41 0/0 UNKNOWN ATM1/0 2 3 0/42 0/3 ESTABLISHED ATM1/0 3 4 0/43 0/0 UNKNOWN

• Check for KA

wsw-7206-3a#debug vsi packets interface atm 1/0 slave 2 VSI Master packet debugging is onDisplaying packets on interface ATM1/0, selected slave(s) only wsw-7206-3a#00:35:12: VSI Master (session 2 on ATM1/0): sent msg SW GET CNFG CMD on 0/4200:35:12: VSI Master (session 2 on ATM1/0): rcvd msg SW GET CNFG RSP on 0/4200:35:27: VSI Master (session 2 on ATM1/0): sent msg SW GET CNFG CMD on 0/4200:35:27: VSI Master (session 2 on ATM1/0): rcvd msg SW GET CNFG RSP on 0/42

Verification• Check that sessions are established

• Slave ID is BXM/UXM slot number

• Established on active cards





wsw-7206-3a#show controllers vsi session 2Interface: ATM1/0 Session number: 2 VCD: 3 VPI/VCI: 0/42Switch type: BPX Switch id: 0Controller id: 1 Slave id: 3Keepalive timer: 15 Powerup session id: 0x00000001Cfg/act retry timer: 8/8 Active session id: 0x00000001 Max retries: 10 Ctrl port log intf: 0x00030100Trap window: 50 Max/actual cmd wndw: 21/21Trap filter: all Max checksums: 79Current VSI version: 2 Min/max VSI version: 2/2 Messages sent: 17 Inter-slave timer: 0.004

Messages received: 14 Messages outstanding: 0 wsw-7206-3a#

Verification

• Check session details


wsw-7206-5a#show controllers vsi traffic session 10Sent Received

Sw Get Cnfg Cmd: 870 Sw Get Cnfg Rsp: 870Sw Cnfg Trap Rsp: 0 Sw Cnfg Trap: 0Sw Set Cnfg Cmd: 1 Sw Set Cnfg Rsp: 1Sw Start Resync Cmd: 1 Sw Start Resync Rsp: 1Sw End Resync Cmd: 1 Sw End Resync Rsp: 1Ifc Getmore Cnfg Cmd: 2 Ifc Getmore Cnfg Rsp: 2Ifc Cnfg Trap Rsp: 0 Ifc Cnfg Trap: 0Ifc Get Stats Cmd: 3 Ifc Get Stats Rsp: 3Conn Cmt Cmd: 14 Conn Cmt Rsp: 14Conn Del Cmd: 3 Conn Del Rsp: 3Conn Get Stats Cmd: 0 Conn Get Stats Rsp: 0

Conn Cnfg Trap Rsp: 0 Conn Cnfg Trap: 0Conn Bulk Clr Stats Cmd: 0 Conn Bulk Clr Stats Rsp: 0Gen Err Rsp: 0 Gen Err Rsp: 0unused: 0 unused: 0unknown: 3 unknown: 3TOTAL: 898 TOTAL: 115

wsw-7206-5a#

Verification

• Check VSI messages





Addshelf/Addcontroller

• ‘addshelf VSI’ triggers the creation ofmaster-slave and inter-slave cross-connects

• In an IGX, the command is ‘addctrlr’


VSI lcns for Slot 3

lcn type dest_slot dest_lcn vpi vci16364 control-port msvc local - 0 4216372 control-port msvc 11 16364 0 5016357 interslave 11 16349 - -

Last Command: dspvsich 3

Next Command:

• VSI slaves in slots 3 and 11


wsw-7206-2a#conf tEnter configuration commands, one per line. End with CNTL/Z.

wsw-7206-2a(config)#int at 2/0 wsw-7206-2a(config-if)#tag-control-protocol vsi id 3 slaves 31

IGX-8420 and IGX-8430

• By default, 14 master-slave VCs are createdin the controller

• Use slaves parameter to increase the number





VSI Terminating VCs

BXM

Slot 1

BXM

Slot 2BXM

Slot 14

VPI/VCI0/40

VPI/VCI0/41

VPI/VCI0/53

Controller IDController ID

Controller IDController ID


Bring-Up Problems





LSC

Controlled Switch

VSI wsw-7206-3a#show controllers vsi control-interfaceInterface: ATM1/0 Connections: 0 wsw-7206-3a#

wsw-7206-3a#show tag-switching interfacesInterface IP Tunnel OperationalXTagATM1101 Yes No No (ATM tagging) wsw-7206-3a#

Problem 1: No VCs Created

• Scenario • Symptom: Absence of PVCs and LVCs otherthan the VSI VCs


Problem Symptom

• Symptom: The LSC cannot create VCsusing VSI

wsw-7206 -3a#show atm vc interface atm 1/0

VCD / Pea k Avg/Min Burst

Interface Name VPI VCI Type Encaps SC Kbps Kbps Cells Sts

1/0 1 0 40 PVC SNAP UBR 40704 UP1/0 2 0 41 PVC SNAP UBR 40704 UP

1/0 3 0 42 PVC SNAP UBR 40704 UP

1/0 4 0 43 PVC SNAP UBR 40704 UP

1/0 5 0 44 PVC SNAP UBR 40704 UP

1/0 6 0 45 PVC SNAP UBR 40704 UP



1/0 11 0 50 PVC SNAP UBR 40704 UP

1/0 12 0 51 PVC SNAP UBR 40704 UP


wsw-7206 -3a#





wsw-7206-3a#show controllers vsi statusInterface Name IF Status IFC State Physical DescriptorXTagATM1101 down ACTIVE 0.11.1.0 wsw-7206-3a#

Possible Cause

• There’s no VSI partition in the control interface

• This does not prevent the controller from being added

• Use show controllers vsi status and check if there’san interface with the name “switch control port”


wsw-7206-3a#show controllers vsi descriptor

Phys desc: 0.11.1.0Log intf: 0x000B0100 (0.11.1.0)

Interface: XTagATM1101IF status: down IFC state: ACTIVE Min VPI: 2 Maximum cell rate: 100000 Max VPI: 15 Available channels: 7633 Min VCI: 32 Available cell rate (forward): 100000 Max VCI: 65535 Available cell rate (backward): 100000

wsw-7206-3a#

Possible Cause

• Session is active but there’s no descriptor for thecontrol interface






Trunk : 3.1Full Port Bandwidth: 96000

Maximum PVC LCNS: 0 Maximum PVC Bandwidth: 91000(Statistical Reserve: 5000)

PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1

Partition : 1 2 3Partition State : Disabled Disabled Disabled

VSI LCNS (min/max): 1000 /2000 0 /0 0 /0 VSI VPI (start/end): 1 /4095 0 /0 0 /0

VSI BW (min/max): 91000 /91000 0 /0 0 /0 VSI ILMI Config: CLR CLR CLR

Last Command: dsprsrc 3.1

Next Command:

Possible Cause

• Use dsprsrc in the BPX/IGX using thecontrol interface






Partition : 1 2 3Partition State : Enabled Disabled Disabled



Last Command: cnfrsrc 3.1 0 0 N y 1 E 1000 2000 1 4095 91000 91000

Next Command:

Solution

• Use cnfrsrc in the BPX/IGX





Verification

• The LSC should look like this

wsw-7206-3a#show controllers vsi statusInterface Name IF Status IFC State Physical Descriptorswitch control port n/a ACTIVE 0.3.1.0XTagATM1101 up ACTIVE 0.11.1.0

wsw-7206-3a#show controllers vsi control-interfaceInterface: ATM1/0 Connections: 3

wsw-7206-3a#


Last Command: cnfrsrc 11.3 256 50000 N y 1 d

Increase MAX VSI LCNs on another active partn in same port grp to 6500 Next Command:

• LCN: Logical Connection Number

• Port Group: Set of interfaces that shareLCN resources

Problem 2:

Cannot Disable Resource Partition

• Error message when trying to disable aresource partition





• Cannot ‘shrink’ resources

• This is one of the most common problems

Formulas for Resource Reservation

• Total number of channels reserved for VSI in aport group:

? ?)max(,)(max MaxLCN MinLCN ed_LCN VSI_reserv PortGroup_ ??



Detailed Card Display for BXM-155 in slot 11Status: ActiveRevision: FDL Backcard InstalledSerial Number: 687272 Type: LM-BXM Top Asm Number: 28215802 Revision: BBQueue Size: 228300 Serial Number: 706939Support: 8 Pts, OC3, FST, VcShp Supp: 8 Pts,OC3,MMF,RedSlot:NOSupp: VT,ChStLv 1,VSI(Lv 3,ITSM)Support: APS(FW)Support: LMIv 1,ILMIv 1,NbrDiscSupport: OAMLp, TrfcGen#Ch:16320,PG[1]:8160,PG[2]:8160PG[1]:1,2,3,4,PG[2]:5,6,7,8,#Sched_Ch:16384

Last Command: dspcd 11

Next Command:

Checking for PG Info• To check for PG information we use ‘dspcd’

Port Group 1: Intfs 1, 2, 3 and 4Port Group 2: Intfs 5, 6, 7 and 8






Channel Management Summary for Slot 11

max used avail netw pvc cnfg vsi mgmt vsi cnf

card 11: 16320 8067 8253 542 1024 1 6500

port grp 1: 8160 8066 94 542 1024 0 6500

port grp 2: 8160 0 8160 0 0 0 0

pvc cnfg pvc used nw used vsi mgmt vsi min vsi max phy if 1: 256 0 271 0

phy trk : 256 0

part 1: 1000 4000

part 2: 1000 4000

phy if 2: 256 0 271 0

phy trk : 256 0 part 1: 1000 4000

part 2: 1000 4000

phy if 3: 256 0 0 0

phy port: 256 0 0

part 1: 1000 6500

phy if 4: 256 0 0 0 phy port: 256 0 0

part 1: 500 1000

phy if 5: 0 0 0 0

This Command: dspchuse 11

Checking for Channel Use: ‘dspchuse’

• Sum(Mins) = 5500 Max(Maxs)=6500



Port : 11.4Full Port Bandwidth: 353208

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 100000(CAC Reserve: 0)



VSI LCNS (min/ max): 500 /6500 0 /0 0 /0

VSI VPI (start/end): 10 /20 0 /0 0 /0 VSI BW (min/max): 100000 /100000 0 /0 0 /0 VSI ILMI Config: CLR CLR CLR

Last Command: cnfrsrc 11.4 256 100000 N y 1 E 500 6500 10 20 100000 100000

Next Command:

Solution• The solution is to increase max LCN in another

partition in the same PG





LSR-LSR Troubleshooting


mpls label-protocol [tdp | ldp | both]

Tag-Switching or MPLS?

• From 12.1(3)T there are ‘mpls’ commands correspondingto most ‘tag-switching’ commands

(Example ‘mpls ip’ for ‘tag-switching ip’)

• In a ‘show running-config’ show as ‘tag-switching’ forbackward compatibility

• We are still configuring TDP

• LDP support from 12.2T





wsw-7206-3a#sh tag-switching tdp neighbor

wsw-7206-3a#

LSR LSR

Cannot Establish TDP Session

• Scenario • Symptom: TDP sessiondoesn’t come up


wsw-7206-3a#sh tag tdp discovery

Local TDP Identifier:

10.10.10.3:0TDP Discovery Sources:Interfaces:

XTagATM1101: xmitXTagATM1102: xmit/recv

TDP Id: 10.10.10.5:2

wsw-7206-3a#

wsw-7206-5a#sh tag-switching int xtagATM 1101 detailInterface XTagATM1101:

IP tagging enabled TSP Tunnel tagging not enabled Tag Frame Relay Transport tagging not enabled Tagging not operationalIP to Tag Fast Switching VectorTag Switching Turbo Vector

MTU = 4470 ATM tagging:

Tag VPI range = 10 - 30Tag VCI range = 33 - 65535Control VC = 15/32

wsw-7206-3a#sh tag-switching int xtagATM 1101 detailInterface XTagATM1101:

IP tagging enabled TSP Tunnel tagging not enabled

Tag Frame Relay Transport tagging not enabled Tagging not operationalIP to Tag Fast Switching VectorTag Switching Turbo Vector

MTU = 4470 ATM tagging:

Tag VPI range = 2 - 15Tag VCI range = 33 - 65535Control VC = 0/32

Possible Cause 1

• Different control-vcat both ends

• TDP discovery showstransmit only





wsw-7206-5a#show controllers xtagATM 1101Interface XTagATM1101 is up

Hardware is Tag-Controlled ATM Port (on BPX switch BPX-VSI2)Control interface ATM5/0 is upPhysical descriptor is 0.11.1.0Logical interface 0x000B0100 (0.11.1.0)Oper state ACTIVE, admin state UP

VPI range 10-30, VCI range 32-65535 VPI is not translated at end of linkTag control VC need not be strictly in VPI/VCI range

Available channels: ingress 2999, egress 2999 Maximum cell rate: ingress 100000, egress 100000 Available cell rate: ingress 100000, egress 100000Endpoints in use: ingress 0, egress 0, ingress/egress 1Rx cells 268

rx cells discarded 0, rx header errors 0rx invalid addresses: 754last invalid address 0/32

Tx cells 1008tx cells discarded: 0

wsw-7206-5a#


Hardware is Tag-Controlled ATM Port (on BPX switch BPX-VSI2)…

last invalid address 15/32

3a 5a

0;32

15;32

Possible Cause 1

• Check for unknownVPI/VCIsin LSC


• Check for unknownVPI/VCIsin switch

Possible Cause 1

3a 5a

0;32

15;32


Trunk Statistics for 11.1 Cleared: Apr. 10 2001 02:56 SnapshotTrunk Speed: 353208 cps Collection Time: 11 day(s) 23:32:14 Corrupted: NO

Cells CLP (EFCI)Rx Trunk: 886066 0 --Tx Trunk: 630272 0 --

Unkn Addr (UA): 2274 Rx OAM Cells : 0 Rx Clp 0 Cells: 886066Rx Clp 0 Dscd : 0 Rx Clp 1 Dscd : 0 Tx Clp 0 Cells: 630272Tx OAM Cells : 0 Rx RM Count : 0 Tx RM Count : 0Lst Unk VpiVci: 15.32 Percent load TX 0.0% Percent load RX 0.0%

UA sums across ports in port group.

Last Command: dsptrkstats 11.1

Next Command:





wsw-7206-3a#conf tEnter configuration commands, one per line. End with CNTL/Z.

wsw-7206-3a(config)#interface xtag 1101 wsw-7206-3a(config-if)#tag-switching atm control-vc 15 32 wsw-7206-3a(config-if)#^Z wsw-7206-3a#00:54:12: %SYS-5-CONFIG_I: Configured from console by console00:54:18: %OSPF-5-ADJCHG: Process 100, Nbr 10.10.10.2 on XTagATM1101 from LOADING toFULL, Loading Done

Solution Problem 1

• Configure the same control-vc in both ends…


wsw-7206-3a#show tag tdp discoveryLocal TDP Identifier:

10.10.10.3:0TDP Discovery Sources:

Interfaces:XTagATM1101: xmit/recv

TDP Id: 10.10.10.2:1XTagATM1102: xmit/recv

TDP Id: 10.10.10.5:2 wsw-7206-3a#

wsw-7206-3a#show tag tdp neighborPeer TDP Ident: 10.10.10.5:2; Local TDP Ident 10.10.10.3:2

TCP connection: 10.10.10.5.11138 - 10.10.10.3.711State: Oper; PIEs sent/rcvd: 70/70; ; Downstream on demand Up time: 00:53:57TDP discovery sources:XTagATM1102

Peer TDP Ident: 10.10.10.2:1; Local TDP Ident 10.10.10.3:1TCP connection: 10.10.10.2.711 - 10.10.10.3.11001

State: Oper; PIEs sent/rcvd: 5/5; ; Downstream on demand Up time: 00:00:48TDP discovery sources:XTagATM1101

wsw-7206-3a#

Solution Problem 1• …and verify TDP functionality

• TDP identifier (router ID: label space)

• Active and passive TDP peer





wsw-7206-3a#show tag-switching interface xTagATM 1131 detailInterface XTagATM1131:

IP tagging enabled TSP Tunnel tagging not enabled Tag Frame Relay Transport tagging not enabled

Tagging not operationalIP to Tag Fast Switching VectorTag Switching Turbo Vector MTU = 4470 ATM tagging:

Tag VPI = 3 (VP Tunnel)

Tag VCI range = 33 - 65535Control VC = 3/32


Hardware is Tag-Controlled ATM Port (on BPX switch BPX-VSI2)Control interface ATM1/0 is up

Physical descriptor is 0.11.3.1Logical interface 0x000B0301 (0.11.3.1)Oper state ACTIVE, admin state UP VPI range 3-3, VCI range 32-65535 VPI may be translated at end of linkTag control VC must be strictly in VPI/VCI range

Available channels: ingress 99, egress 99 Maximum cell rate: ingress 0, egress 0 Available cell rate: ingress 0, egress 0

Endpoints in use: ingress 0, egress 0, ingress/egress 1Rx cells 0rx cells discarded 0, rx header errors 19

rx invalid addresses: 5last invalid address 0/0

Tx cells 376tx cells discarded: 0

wsw-7206-3a#

mgx8250c_rpm_10(config-subif)#tag-sw atm vp-tunnel 10

Note

• For virtual trunks, thecontrol-vc uses the VT’sVPI; (interface is VP tunnel)

• Label is only VCI field

• In eLSR we need to specifythe VP tunnel


wsw-7206-5a#debug tag-switching atm-tdp api

00:35:31: TAGATM_API: Disjoint VPI local[20-30], peer[2-15]

00:37:28: %TDP-3-TAGATM_BAD_RANGE: Interface XTagATM1101, Bad VPIrange. Can't start a TDP session

Possible Cause 2

• There is no common VPI range between LSRs





wsw-7206 -5a#show controllers vsi descriptor 0.11.1.0

Phys desc: 0.11.1.0

Log intf: 0x000B0100 (0.11.1.0)

Interface: XTagATM1101

IF status: up IFC state: ACTIVE Min VPI: 20 Maximum cell rate: 100000

Max VPI: 30 Available channels: 2996

Min VCI: 32 Available cell rate (forward):

100000

Max VCI: 65535 Available cell rate (backward):

100000

wsw-7206 -5a#

wsw-7206 -3a#show controllers vsi descriptor 0.11.1.0

Phys desc: 0.11.1.0

Log intf: 0x000B0100 (0.11.1.0)Interface: XTagATM1101

IF status: up IFC state: ACTIVE Min VPI: 2 Maximum cell rate: 100000

Max VPI: 15 Available channels: 3496

Min VCI: 32 Available cell rate (forward):

50000 Max VCI: 65535 Available cell rate (backward):

50000

wsw-7206 -3a#

Possible Cause 2

• There is no common VPI range between LSRs









Last Command: cnfrsrc 11.1 256 248207 y 1 E 1000 7633 10 30 50000 100000

Next Command:

Note: This is because LDP currently negotiates label ranges (VPI,VCI ranges) only when the sessionis established; Shut/no shut the XmplsATMinterface will force the TDP session to be reestablished

Solution Problem 2• Configure an overlapping VPI Range with cnfrsrc

and shut/no shut the XmplsATM interface





wsw-7206-5a#sh tag atm-tdp capability

VPI VCI Alloc Odd/Even VC MergeXTagATM1101 Range Range Scheme Scheme IN OUT Negotiated [10 - 15] [33 - 65535] BIDIR - -Local [10 - 30] [33 - 65535] BIDIR EVEN NO NOPeer [2 - 15] [33 - 65535] BIDIR ODD - -

wsw-7206-5a#

Solution Problem 2

• Verify negotiated VPI range

EVEN for lower LDP ID


wsw-7206-5a#show tag-switching tdp discoveryLocal TDP Identifier:


Interfaces:XTagATM1101: xmit

wsw-7206-5a#show tag-switching tdp neighbor

wsw-7206-3a#show tag-switching tdp discoveryLocal TDP Identifier:


Interfaces:XTagATM1101: xmit/recv

TDP Id: 10.10.10.2:1; no route

wsw-7206-3a#

wsw-7206-3a#debug tag-switching tdp transport eventsTDP transport events debugging is on

00:18:44: tdp: Send hello; XTagATM1101, src/dst 10.10.10.3/255.255.255.255, inst_id 1, tcatm 00:18:46: tdp: Rcvd hello; XTagATM1101, from 10.10.10.2 (10.10.10.2:1), intf_id 1, opt 0x0, tcatm 00:18:46: tdp: Hello from 10.10.10.2 (10.10.10.2:1) to 255.255.255.255, opt 0x000:18:46: tdp: Opening conn; adj 0x631F2754, 10.10.10.3 <-> 10.10.10.200:18:46: tdp: No route to peer 10.10.10.2; set LDP_PROC_HANDLE_ROUTEUP

Only on Active TDP Side(Higher TDP ID)

Possible Cause 3• There is no route





Solution Problem 3

• Follow usual IGP troubleshooting

• Make sure CEF is enabled in theremote LSC


wsw-7206-3a#sh xtag cross-connect int xTagATM 1101 0 32Phys desc: 0.11.1.0Interface: XTagATM1101Intf type: extended tag ATM VPI/VCI: 0/32X-Phys desc: 0.3.1.0X-Interface: n/aX-Intf type: switch control portX-VPI/VCI: 1/32Conn-state: UPConn-type: input/outputCast-type: point-to-pointRx service type: Tag COS 7Rx cell rate: n/aRx peak cell rate: 91000

Tx service type: Tag COS 7Tx cell rate: n/aTx peak cell rate: 91000 wsw-7206-3a#

ATM Queues

MPLS Queues

ATMFPartition

MPLS Partition• Bandwidth

allocated by class

• Separate labelsper class

CBR

ABR

IP Class 1

IP Class 2

IP Class 3

UBR

Possible Cause 4

• QBINS not configured

• Use dspqbinstats in the BPX/IGX





Possible Cause 4

• First we check the SCT the partition uses

SCT = Service Class Template


Trunk: 11.1

Service Class Template ID: 1

VSI Partitions :channels bw vpi

Part E/D min max min max start end ilmi1 E 1000 7633 50000 100000 2 15 D2 D 0 0 0 0 0 0 D3 D 0 0 0 0 0 0 D

Last Command: dspvsiif 11.1

Next Command:



Service Class Map for MPLS1 Template

Service Class Qbin Service Class Qbin Service Class Qbin

Default 13Signaling 10Tag0 10Tag1 11Tag2 12Tag3 13Tag4 10Tag5 11

Tag6 12Tag7 13TagAbr 14

Last Command: dspsct 1

Next Command:

Possible Cause 4

• Second we identify the QBin for that COSthe control-vc uses






Qbin Database 11.1 on BXM qbin 13 (Configured by User)(EPD Enabled on this qbin)

Qbin State: Enabled Discard Threshold: 0 cellsEPD Threshold: 0%High CLP Threshold: 0%EFCI Threshold: 0%

Last Command: dspqbin 11.1 13

Next Command:

Possible Cause 4

• Last we check the QBin configuration


This Command: cnfqbin 11.1 13 E

Use default values from template?: y


Qbin Database 11.1 on BXM qbin 13 (Configured by MPLS1 Template)(EPD Enabled on this qbin)

Qbin State: Enabled Discard Threshold: 105920 cellsEPD Threshold: 95%High CLP Threshold: 100%EFCI Threshold: 100%

Last Command: cnfqbin 11.1 13 E y

Next Command:

Solution Problem 4

• Configure the QBin for default SCT values





Verification

wsw-7206-5a#show tag-switching tdp neighborPeer TDP Ident: 10.10.10.3:1; Local TDP Ident 10.10.10.2:1

TCP connection: 10.10.10.3.12241 - 10.10.10.2.711State: Oper; PIEs sent/rcvd: 4/4; ; Downstream on demand Up time: 00:00:11TDP discovery sources:XTagATM1101

wsw-7206-5a#


LVC and Network-Wide TS





VSI Slaves

End-to-End Connections

• Network layer handles end-to-end signaling

• Network layer uses VSI at each switch to set upcross-connects and VCs

VSI

VSI Master

MPLS, IP RoutingMPLS, IP Routing

PlatformPlatform

VSI

VSI Master


VSI Slaves

PlatformPlatform

VSI

VSI Master


VSI Slaves

PlatformPlatform

LDP LDP

VC VC

Cross-

Connect

Cross-

Connect

Cross-

Connect


wsw-7206-3a#show xtagatm vc AAL / Control Interface

Interface VCD VPI VCI Type Encapsulation VCD VPI VCI StatusXTagATM101 7 0 32 PVC AAL5-SNAP 48 1 36 ACTIVEXTagATM101 8 1 38 TVC AAL5-MUX 59 1 47 ACTIVEXTagATM101 10 1 49 TVC AAL5-MUX 71 1 59 ACTIVEXTagATM1101 11 0 32 PVC AAL5-SNAP 45 1 33 ACTIVEXTagATM1101 12 10 33 TVC AAL5-MUX 55 1 43 ACTIVEXTagATM1101 23 10 57 TVC AAL5-MUX 68 1 56 ACTIVEXTagATM1101 26 10 160 TVC AAL5-MUX 72 1 60 ACTIVEXTagATM1101 27 10 162 TVC AAL5-MUX 73 1 61 ACTIVEXTagATM1102 10 0 32 PVC AAL5-SNAP 46 1 34 ACTIVEXTagATM1102 11 244 34 TVC AAL5-MUX 49 1 37 ACTIVEXTagATM1102 17 244 45 TVC AAL5-MUX 74 1 62 ACTIVEXTagATM1131 3 3 32 PVC AAL5-SNAP 47 1 35 ACTIVEXTagATM1132 3 5 32 PVC AAL5-SNAP 44 1 32 ACTIVE

wsw-7206-3a#show xtagatm cross-connect descriptor 0.11.1.0Phys Desc VPI/VCI Type X-Phys Desc X-VPI/VCI State0.11.1.0 10/59 -> 0.1.1.0 1/47 UP0.11.1.0 10/57 -> 0.3.1.0 1/56 UP0.11.1.0 10/41 -> 0.1.1.0 1/37 UP

0.11.1.0 10/33 -> 0.3.1.0 1/43 UP0.11.1.0 10/162 <- 0.3.1.0 1/61 UP0.11.1.0 10/160 <- 0.3.1.0 1/60 UP0.11.1.0 10/156 <- 0.11.2.0 244/60 UP0.11.1.0 10/152 <- 0.1.1.0 1/46 UP0.11.1.0 10/148 <- 0.11.2.0 244/56 UP0.11.1.0 10/44 <- 0.1.1.0 1/36 UP0.11.1.0 10/40 <- 0.11.2.0 244/46 UP0.11.1.0 0/32 <-> 0.3.1.0 1/33 UP wsw-7206-3a#

VCs and Cross-Connects

• Note type andencapsulation





Label Distribution Mechanics:Downstream on Demand

• Distributes per-interface label space(e.g. label controlled ATM)

• Upstream LSR requests label for specificdestination from downstream LSR

• Builds label VC from head-end platform totail-end platform


Head

End

Tail

EndLabel VC

. . . D

Request (D) Request (D) Request (D)

S1 S2

S1 S2

Mapping(D, label )

S1

R2R2

R2R2

R1R1

R1R1

Mapping(D, label )

S2Mapping(D, label )

R2

Transit Transit

Label Distribution Mechanics

Downstream on Demand Example





wsw-7204-4a#show tag-switching atm-tdp bindingsDestination: 10.10.10.2/32

Headend Router ATM3/0.1 (1 hop) 1/33 Active, VCD=109Destination: 10.10.10.3/32

Headend Router ATM3/0.1 (2 hops) 1/35 Active, VCD=110Destination: 10.10.10.4/32



Tailend Router ATM3/0.1 1/34 Active, VCD=106Tailend Router ATM3/0.1 1/36 Active, VCD=107Tailend Router ATM3/0.1 1/38 Active, VCD=108

Tailend Router ATM3/0.1 1/40 Active, VCD=113

wsw-7204-4a#

How to Check Bindings—eLSR


wsw-7206-5a#show tag-switching atm-tdp bindingsDestination: 10.10.10.2/32

Tailend Switch XTagATM1101 10/36 Active -> Terminating Active, VCD=2Tailend Switch XTagATM1101 10/38 Active -> Terminating Active, VCD=4Tailend Switch XTagATM1103 1/33 Active -> Terminating Active, VCD=3Tailend Switch XTagATM1101 10/44 Active -> Terminating Active, VCD=6

Destination: 10.10.10.3/32Headend Switch XTagATM1101 (1 hop) 10/33 Active, VCD=3Transit XTagATM1103 1/35 Active -> XTagATM1101 10/37 Active

Destination: 10.10.10.4/32Headend Switch XTagATM1101 (2 hops) 10/35 Active, VCD=5Transit XTagATM1103 1/37 Active -> XTagATM1101 10/39 Active



Transit XTagATM1101 10/40 Active -> XTagATM1103 1/38 ActiveTransit XTagATM1101 10/42 Active -> XTagATM1103 1/40 Active

wsw-7206-5a#

How to Check Bindings—LSC

• Transit are LSC functionality





wsw-7206-3a#show tag-switching forwarding-table

Local Outgoing Prefix Bytes tag Outgoing Next Hoptag tag or VC or Tunnel Id switched interface16 10/34 10.10.10.1/32 0 XT1101 point2point17 10/36 10.10.10.2/32 0 XT1101 point2point18 1/49 10.10.10.4/32 0 XT101 point2point19 244/45 10.10.10.5/32 0 XT1102 point2point

21 Untagged 10.1.1.1/32 0 XT1101 point2point wsw-7206-3a#

Forwarding Table


wsw-7206-3a#show xtag cross-connect traffic interface xtag 1101 10 34

Phys desc: 0.11.1.0Interface: XTagATM1101 VPI/VCI: 10/34X-Phys desc: 0.3.1.0X-Interface: n/aX-VPI/VCI: 1/38

Conn-state: UPConn-type: output

Rx cells: n/a Rx cells discarded: n/aTx cells: 0 Tx cells discarded: 15 wsw-7206-3a#

Problem: LVCs Discarding Traffic

• Checking traffic discards from the LSC





wsw-7206-3a#show xtagatm cross-connect interface xtagATM 1101 10 34

Phys desc: 0.11.1.0Interface: XTagATM1101Intf type: extended tag ATM VPI/VCI: 10/34X-Phys desc: 0.3.1.0X-Interface: n/a

X-Intf type: switch control portX-VPI/VCI: 1/40Conn-state: UPConn-type: outputCast-type: point-to-pointRx service type: n/a

Rx cell rate: n/aRx peak cell rate: n/aTx service type: Tag COS 0Tx cell rate: n/aTx peak cell rate: 91000 wsw-7206-3a#

Discards—Things to Check

• Check the QBin configuration as before


wsw-7206-5a#show xtag cos-bandwidth-allocation xtag 1101

COS Bandwidth allocation

available 100 %standard 0 % premium 0 %

control 0 %

wsw-7206-5a# show xtag cos-bandwidth-allocation xtag 1102

COS Bandwidth allocation

available 100 %

standard 0 % premium 0 %control 0 %

wsw-7206-5a#sh xtag cos xtag 1103

LDP Uses Control

LDP CanTear DownLVCs

• Use dspqbinstats in the BPX/IGX

Discards—Things to Check• Check the COS allocation





Discards—Things to Check

i8430-2a TN Cisco IGX 8430 9.3.11 Apr. 15 2001 06:22 GMT

Bus Bandwidth Usage for UXM card in slot 31 Last Updated on 04/15/01 06:20:36

FPkts/sec Cells/sec UBUs Minimum Reqd Bandwidth: 0 0 0 Average Used Bandwidth: 0 0 0Peak Used Bandwidth: 615 19104 6

Maximum Port Bandwidth: - 706415 177

Allocated Bandwidth: 44(Cell Only): - 176000(Cell+Fpkt): 88000 132000(Fpkts / 2 + Cells) <= 176000

Reserved Bandwidth: - 4000 1

Last Command: dspbusbw 31

Next Command:

• On an IGX, also check UBU allocation

Cnfbusbw

to Fix


LCNLCN

LCNLCN

Setting Up an LVC Cross-Connect






LCN=16311: vpi=xa, vci=x24, port=0, phy=0, rp=0 ing_vi=x3, egr_vi=x0, state=x3ilmi_session_id=0,ingr_abit_status=1, egr_abit_status=1, conn_type=0Conn 3fb7 (16311 dec)cks_blk_idx= 0 cksm= 0 part_idx= 0 gi_gf= 2 gi_gf2=40:ei_gf_loc= 0 ei_gf2_loc= 0 ei_gf3_loc= 0:ei_gf_rem= 0 ei_gf2_rem= 0 ei_gf3_rem= 0:local_ep_type= 0 rsnc_flag= 1 state=VSI_Cmtted( 3):diag status= 0, diag_result= 0, diag_dir= 0:loc_lin=0xb0100 loc_vpi_vci=(10,36) rem_lin=0x30100 rem_vpi_vci=(1, 54):is_derouted=0 is_vpc=0 :alarm= 0 :alarm_ack_pending= 0:f_serv_type=0x200 b_serv_type=0x200 ING_ECR=0 EGR_ECR=0:next= 3f9c prev= 3fc0 tcb_addr=a0cd8f60

Last Command: rsh 11 vsi cm VsiDisplayLcn 0 10 36

Next Command:

• VsiDisplayLcn <Port 0-based> <VPI> <VCI>

Finding the LCN



VSI_CN_STATS_CELLS_FROM_PORT_IN 261 VSI_CN_STATS_CELLS_DISC_W_CLP0_IN 0 VSI_CN_STATS_CELLS_DISC_W_CLP1_IN 0 VSI_CN_STATS_CELLS_TO_PORT_EG 0 VSI_CN_STATS_CELLS_DISC_W_CLP0_EG 0 VSI_CN_STATS_CELLS_DISC_W_CLP1_EG 0

Last Command: rsh 11 vsi cm VsiCs 16311

Next Command:

• Be very careful with RSH commands

LVCs areunidirectional

Finding Statistics about LCN





Running out of LVCs

00:30:32: %TCATM-4-XCONNECT_FAILED: 10.10.10.3/32 Head end terminating on XTagATM310200:30:32: %TCATM-4-XCONNECT_FAILED: 10.10.10.5/32 Tail end terminating on XTagATM3102

• Immediate symptom is error messageson LSC: TCATM-XCONNECT_FAILED; thismeans that the switch has insufficient LCNs for LVCs on one of its interface’s partitions


A network that has run out of cross-connectsis basically non-functioning. There really isn’t

any way to control which [LVCs] get created

and which don’t. This may result in permanent

black holes and/or wildly overloaded control

processors. The network needs to be designed

from the start such that it won’t run out ofconnections.

Josh Gahm, LSC Developer

LVC Starvation





Network Behaviors

• An eLSR will deal with LVC setup failureby sending IP traffic on control-vc(switched then by LSC processor)

• For MPLS services (VPNs) packets arediscarded (black holes)



VSI Resources Status for trunk 31.2 Partition 3

Minimum Lcns : 100 Minimum BW (cps) : 100000 Maximum Lcns : 300 Maximum BW (cps) : 100000Used Lcns : 300 Used BW (cps) : 0

Available Lcns : 0 Available BW (cps) : 100000Start VPI : 2 End VPI : 2

This Command: dspvsipartinfo 31.2 3

Hit DEL key to quit:

Identifying the Problem• From the switch we use dspvsipartinfo and

several RSH commands






Phys desc: 0.31.2.0Log intf: 0x001F0200 (0.31.2.0)Interface: XTagATM3102IF status: up IFC state: ACTIVE

Min VPI: 2 Maximum cell rate: 100000 Max VPI: 2 Available channels: 0 Min VCI: 32 Available cell rate (forward): 100000 Max VCI: 65535 Available cell rate (backward): 100000

wsw-7206-5a#show controllers vsi descriptor 0.11.2.0

Phys desc: 0.11.2.0Log intf: 0x000B0200 (0.11.2.0)Interface: XTagATM1102IF status: up IFC state: ACTIVE


wsw-7206-2a#

Identifying the Problem

• From the LSC CLI or “VSI Master MIB”


wsw-7206-2a#show tag-switching atm-tdp summaryTotal number of destinations: 3

TC-ATM bindings summaryinterface total active local remote Bwait Rwait IFwaitXTagATM3102 3 2 1 1 1 0 0

wsw-7206-2a# wsw-7206-5a#show tag-switching atm-tdp bindwait

Waiting for bind on XTagATM110210.10.10.5/32

wsw-7206-5a#

IFwait The Number of Bindings That Are Waiting for Learned Labels to BeInstalled for Switching Use

The Number of Bindings That Are Waiting for Learned Labels to BeInstalled for Switching Use

Rwait The Number of Bindings That Are Waiting for Resources (VPI/VCISpace) to Be Available on the Downstream Device

The Number of Bindings That Are Waiting for Resources (VPI/VCISpace) to Be Available on the Downstream Device

Bwait The Number of Bindings That Are Waiting for aLabel Assignment From the Neighbor LSR

The Number of Bindings That Are Waiting for aLabel Assignment From the Neighbor LSR

Identifying the Problem

• From the LSC (i.e. LSR)





Possible Workaround 1

• Disable the eLSR functionality in the LSC,by disabling head-end VCs

• From 12.1(3)T

• Disable tail-end VCs: to stop other eLSRs

requesting LVCs to the LSCs, filter LSCloopback addresses in all eLSRs

wsw-7206-3a(config)#tag-switching atm disable-headend-vc


Possible Workaround 2• Use unnumbered links or use request-tags for command

in all LSCs and eLSRs (12.1(5)T)

• The effect on LVC setup is the same as usingunnumbered links

wsw-7206-5a#conf tEnter configuration commands, one per line. End with CNTL/Z. wsw-7206-5a(config)#ip access-list standard BlockThis wsw-7206-5a(config-std-nacl)#deny 10.1.1.0 0.0.0.255

wsw-7206-5a(config-std-nacl)#permit any wsw-7206-5a(config-std-nacl)#exit wsw-7206-5a(config)#tag-sw request-tags for BlockThis ?

<cr>

wsw-7206-5a(config)#tag-sw request-tags for BlockThis

wsw-7206-5a(config)#^Z wsw-7206-5a#

• tag-switching advertise-tags has no effect on an LC-ATMinterface.





Solution


Trunk : 31.2 Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 248207

(Statistical Reserve: 5000)

State MinLCN MaxLCN StartVPI EndVPI MinBW MaxBW Partition 1: DPartition 2: DPartition 3: E 500 2000 2 2 100000 100000

Last Command: cnfrsrc 31.2 256 y 3 E 500 2000 2 2 100000 100000

Cnfrsrc successful. Next Command:

• Dimension the Network correctly (minLCN toat least calculated LVC requirement)

• Increase LCN resources with cnfrsrc

• Enable VC-Merge with SwSW 9.3.30+


Verification

• Available LCN resources

• Bindings active

wsw-7206-2a#show tag-switching atm-tdp summaryTotal number of destinations: 3

TC-ATM bindings summaryinterface total active local remote Bwait Rwait IFwaitXTagATM3102 3 3 1 2 0 0 0

wsw-7206-2a#


Phys desc: 0.31.2.0Log intf: 0x001F0200 (0.31.2.0)Interface: XTagATM3102IF status: up IFC state: ACTIVE






Multiple Controller Problems


LSC Redundancy Not Working

• Scenario • Symptom: Only oneXmplsATM from aninterface with multiplepartitions comes up

LSC

Controlled Switch

VSI tagigx4 TN Cisco IGX 8430 9.3.1Z Aug. 3 2000 11:05 PDT

VSI Controller Information

CtrlrId PartId ControlVC Intfc Type CtrlrIP VPI VCIRange

1 1 0 40-70 3.3 MPLS 10.1.1.12 2 0 40-70 19.3 MPLS 11.1.1.1


The Slave Ids Correspond to the Slot Numbers in the Switch

VSI

LSC





Possible Cause 1

• Overlapping control-VCstagigx4 TN Cisco IGX 8430 9.3.1Z Aug. 3 2000 11:05 PDT

Trunk : 7.1


State MinLCN MaxLCN StartVPI EndVPI MinBW MaxBW

Partition 1: E 30 100 50 75 1000 10000

Partition 2: E 10 100 90 150 1000 10000

Partition 3: E 10 100 180 240 1000 5000

Last Command: dsprsrc 7.1

00:01:21: VSI Master: got NAK reason 12 ( sec VPI/VCI in use) in CONN CMT RSP rcvd on ATM1/0:0/42

connection 0x00030100/1/51 <-> 0x000B0100/0/32

00:01:21: Additional response data:

00.03.01.00 80.0b.01.00 13.99.00.8c 00.03.00.023f.b5.01.00 13.ab.00.1e 00.04.00.01 00.00.00.00

• Turn on debug vsi errors and see message‘VPI/VCI in use’

Info-Data


Solution Problem 1

• Modify control-vc in one of the partitions

!interface XTagATM71ip unnumbered Loopback1no ip directed-broadcastno ip route-cache cefextended-port ATM5/0 vsi 0x00070100tag-switching atm control-vc 90 32tag-switching ipend

!interface XTagATM71ip unnumbered Loopback0no ip mroute-cacheextended-port ATM2/0 vsi 0x00070100tag-switching ipend





Different Controllers Problem

• Scenario • Symptom: Only trafficfrom one controllerpasses (LVCs or SVCs)




1 1 0 40-54 3.1 VSI VSI2 2 0 40-54 12.1 VSI AAL/5


Next Command:

Service Expansion Shelf (SES) Is the PNNI Controller for BPX

LSC

Controlled Switch

VSI VSI

LSC


Possible Cause 1

• Incorrect SCT (Service Class Template) used


Service Class Templates

Template Name

1 MPLS1

2 ATMF1

3 ATMF2

4 ATMF_tagcos_1

5 ATMF_tagcos_26 ATMF_TAGABR_1

7 ATMF_TAGABR_2

8 atmf_TAGCoS _TAGABR_1

9 atmf_TAGCoS _TAGABR_2

Last Command: dspsct

Next Command:

• dspsct shows the available templates

Default template






Trunk: 11.1



Part E/D min max min max start end ilmi1 E 1000 6500 50000 100000 2 15 D2 E 1000 4000 50000 100000 50 50 D3 D 0 0 0 0 0 0 D

Last Command: dspvsiif 11.1

Next Command:

Possible Cause 1

• Verify the SCT used in trunks, portsand control ports

• SCT should also match on connected trunks



Trunk: 11.1



Part E/D min max min max start end ilmi1 E 1000 6500 50000 100000 2 15 D2 E 1000 4000 50000 100000 50 50 D3 D 0 0 0 0 0 0 D

This Command: cnfvsiif 11.1 4

Interface has active VSI partition(s): changing SCT will be service affectingContinue?

Solution Problem 1

• Modify the SCT assigned to interfaces





Summary

95


Summary

• Troubleshooting ATM MPLS is easy

• ATM MPLS has two components totroubleshoot:

Controller => networking protocol

Switch => resources

• Find the problem first; solve it second





References

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/

bpx8600/mpls/index.htm

http://www.cisco.com/kobayashi/support/tac/troubleshoot.shtml

http://www.cisco.com/support/Errordecoder/error-decoder.html

http://www.cisco.com/warp/customer/105/mpls_index.shtml

http://www.cisco.com/warp/public/74/wansw_index.shtml

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121s

up/121sems/emdtcp.htm#xtocid17663


Related Sessions

• PS-542 MPLS-Technology Optionsand Applications

• RST-130 Introduction to MPLS

• RST-230 Deploying Large Scale VPNwith MPLS

• RST-430 Advanced Developments andConcepts in MPLS





TroubleshootingATM MPLS

Session RST-331

99


Please Complete YourEvaluation Form

Session RST-331

100



101RST-3312901_05_2001 © 2001, Cisco Systems, Inc. All rights reserved.

Documents

RST-331 Troubleshooting ATM MPLS.pdf