Troubleshooting Wan Protocols in Cisco Ios Software: Session Acc-3000

TROUBLESHOOTING WAN PROTOCOLS IN CISCO IOS SOFTWARE
SESSION ACC-3000
ACC-3000 9743_05_2004_c2
2004 Cisco Systems, Inc. All rights reserved.
Skill Level Assumptions

Have protocol level knowledge of:
Frame Relay, PPP, and/or ATM
Familiar with Cisco IOS WAN configuration of:

T1, T3, and SONET controllers HDLC, PPP, Frame Relay, and WAN ATM
ACC-3000 9743_05_2004_c2
2004 Cisco Systems, Inc. All rights reserved. Printed in USA. Presentation_ID.scr
WAN Troubleshooting Maxim
IF THE LOWER LAYER DOESNT WORK, THE UPPER LAYER CANT WORK.
ANCIENT WAN TROUBLESHOOTING PROVERB
ACC-3000 9743_05_2004_c2
Session Topics
T1 and T3 Transmission Lines Point-to-Point SONET HDLC PPP Frame Relay WAN ATM
ACC-3000 9743_05_2004_c2
T1 AND T3 TRANSMISSION LINES
ACC-3000 9743_05_2004_c2
Troubleshooting T1 or Digital Leased Lines

DCE
Router (Serial Int.)
DCE Telco
DSU/CSU Router (Serial Int.)
DTE
DSU/CSU
DTE
Verify CSU/DSU settings

Framing, line code, clocking, timeslots, speed, interface type SCTE used to compensate for clock phase shift
Loopbacks are your friends Service Timestamps Debug Date MSEC Service Timestamps Log Date MSEC
ACC-3000 9743_05_2004_c2
Breakdown of T1 Controller Counters

Defect counters
Line code violations Path code violations
Performance counters
Degraded mins Errored secs Bursty err secs Severely err secs Unavail secs
Format may vary contingent upon module type and revision
ACC-3000 9743_05_2004_c2
T1: Meaning of Controller Counters

Data in current interval (359 seconds elapsed): 9 Line Code Violations, 55 Path Code Violations 21 Slip Secs, 0 Fr Loss Secs, 9 Line Err Secs, 0 Degraded Mins 31 Errored Secs, 5 Bursty Err Secs, 1 Severely Err Secs 0 Unavail Secs, 0 Stuffed Secs
Line Code Violations (LCV)number of bipolar violations or excessive zeros Path Code Violations (PCV)number of frame synchronization bit errors in SF frame format or CRC errors in ESF frames Slip Secsnumber of seconds containing one or more controlled slips Fr Loss Secsnumber of seconds with at least one Out Of Frame (OOF) error Line Err Secsnumber of seconds with at least one line code violation Degraded Minsminutes since controller has been up and available that the error rate per minute exceeded 0.000001 but was less than 0.001
ACC-3000 9743_05_2004_c2

Errored Secstotal seconds containing one or more PCVs, OOF conditions, AIS alarms, or controlled slips for ESF format; SF also count seconds containing one or more LCVs Bursty Err Secsnumber of seconds containing one to 320 PCVs Severely Err Secsfor ESF format, the total number of seconds containing more than 320 PCVs, at least one OOF condition, or an AIS detection; for SF/D4 format, the total number of seconds with more than 1544 LCVs or at least one OOF condition
ACC-3000 9743_05_2004_c2

Unavail Secstotal seconds that the T1 controller cannot pass traffic; unavailable seconds begin when ten consecutive severely errored seconds occur; the unavailable seconds end when ten contiguous seconds elapse with no severely errored seconds; during an unavailable second none of the other T1 controller counters increment Stuffed Secstotal seconds where non-data bit patterns must be transmitted due to TX buffer under runs
ACC-3000 9743_05_2004_c2
10
T1/T3: Alarm Scenario

Red Alarm
Upstream
TX RX TX RX TX RX RX TX
Blue Alarm Sent

TX RX RX TX
Yellow Alarm Sent
Yellow Alarm Sent
Yellow Alarm Sent
ACC-3000 9743_05_2004_c2
11
T1: Red Alarm

Occurs when T1 receiver has Loss of Signal (LOS) LOS defined in RFC 1406 as:
For T1, the Loss of Signal failure is declared upon observing 175 +/- 75 contiguous pulse positions with no pulses of either positive or negative polarity
ACC-3000 9743_05_2004_c2
12
T1/T3: Yellow Alarm

Yellow alarm is the common expression for a Remote Alarm Indication (RAI) A yellow alarm is transmitted when the receiver has loss of signal; in this case, the receiver is in red alarm and the transmitter sends a yellow alarm If the receiver is in yellow alarm, this indicates a problem exists in the far end
ACC-3000 9743_05_2004_c2
13
T1: Declaring a Yellow Alarm

For SF links, the yellow (a.k.a. far end) alarm failure is declared when bit 6 of all of the channels has been zero for at least 335 ms; the failure is cleared when bit 6 of at least one channel is not zero for a period usually less than one second and always less than 5 seconds; the far end alarm failure is not declared for SF links when a Loss of Signal is detected For ESF links, the far end alarm failure is declared if the yellow alarm signal pattern occurs in at least seven out of ten contiguous 16-bit pattern intervals; the failure is cleared if the yellow alarm signal pattern does not occur in ten contiguous 16-bit signal pattern intervals
ACC-3000 9743_05_2004_c2
14
T1: ESF Yellow Alarm Pattern

ESF yellow alarm is transmitted as a repeating 16 bit pattern of 8 one bits followed by 8 zero bits This pattern is transmitted in the FDL overhead bits Pattern must be transmitted for a minimum of 1 second
ACC-3000 9743_05_2004_c2
15
T1/T3: AIS and Blue Alarms

An unframed all ones bit stream is called an Alarm Indication Signal (AIS); reception of an AIS causes a blue alarm state on the receiving device T1 transport device sends AIS when the signal to transmit downstream is lost; i.e. there is a problem upstream
ACC-3000 9743_05_2004_c2
16
T1/T3: Alarm States

A T1 devices current alarm state is based on the signal pattern or lack of signal present at the T1 devices receiver The transmitted signal pattern sent by the T1 devices transmitter does not determine the alarm state of the device
ACC-3000 9743_05_2004_c2
17
T1: Show Controller with Alarms

show controller t1 T1 2/1 is down Transmitter is sending remote alarm (Yellow alarm) Receiver has loss of signal Framing is ESF, Line Code is B8ZS, Clock Source is Line Data in current interval (160 seconds elapsed): 0 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 160 Unavail Secs
ACC-3000 9743_05_2004_c2
18
T1/T3: Troubleshooting Tools

Extended ping tests Loopbacks
Controller loops Serial loops Hard wire loops
BERT generators
ACC-3000 9743_05_2004_c2
19
Using extended Ping Command to Test a T1

You can use the Cisco IOS exec command ping to test T1 circuits for line code mismatches, T1 repeater problems and timing issues The ping command has an extended commands section that allows you to enter the 2 byte data pattern that is repeated in the payload of the ping packet
ACC-3000 9743_05_2004_c2
20
Using extended Ping Command to Test a T1 (Cont.)

Three useful ping data patterns that expose line problems:
0x0000 (line code mismatches) 0xFFFF (repeater power problems) 0x4040 (timing problems)
ACC-3000 9743_05_2004_c2
21
Using extended Ping Command to Test a T1 (Cont.)

Example:
Router#ping Protocol [ip]: Target IP address: 13.200.2.5 Repeat count [5]: 100 Datagram size [100]: 1500 Timeout in seconds [2]: Extended commands [n]: y Source address or interface: Type of service [0]: Set DF bit in IP header? [no]: Validate reply data? [no]: Data pattern [0xABCD]: 0x4040 Loose, Strict, Record, Timestamp, Verbose[none]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 5, 1500-byte ICMP Echos to 13.200.2.5, timeout is 2 seconds: Packet has data pattern 0x4040 !!!!!!!..!!!!!!!!!!!!!..!!!.!!!!..!!!!!..!!!...!!!!!!!!!...!!!!!! !!!!!
ACC-3000 9743_05_2004_c2
22
Loopback Tests
DCE DTE
DSU CSU DACS
DCE Telco
DACS CSU DSU
DTE
Local Loopbacks
(Also Called Line and DTE Loopback)
(Also Called Network Loopback)
Remote Loopbacks
Use pings to test connectivity, while in loopback mode Remember, success of pings, depends on correct configuration
HDLC: if keep alive is enable, sh int => up, up (looped) You can then ping yourself Frame Relay: If LMI is exchanged with switch, then you see up, up if PVCto-IP mapping exists, you can ping yourself
ACC-3000 9743_05_2004_c2
23
Troubleshooting Tools Loopbacks

T1 CSU/DSU Loopback Line
Router (config-if) # loopback line
CSU/DSU Module
Cisco Router
DTE Interface
DSU
CSU
ACC-3000 9743_05_2004_c2
24
Troubleshooting Tools Loopbacks (Cont.)

T1 CSU/DSU Loopback Line Payload
Router (config-if) # loopback line payload
CSU/DSU Module
Cisco Router
DTE Interface
DSU
CSU
ACC-3000 9743_05_2004_c2
25

T1 CSU/DSU Module DTE Loop
Router (config-if) # loopback dte
CSU/DSU Module
Cisco Router
DTE Interface
DSU
CSU
Send Blue Alarm
ACC-3000 9743_05_2004_c2
26

Far End Remote Loop
Router (config-if) # loopback remote full other type loopspayload, smart-jack
Cisco Router
CSU/DSU Module DTE Interface

DSU CSU
CSU
DSU
May Require Service-Module T1 Remote-Loopback Set at Remote
ACC-3000 9743_05_2004_c2
27

Loopback Remote Payload V.54
Router (config-if) # service-module t1 Remote-loopback payload v54
CSU/DSU Module
Cisco Router
DTE Interface
DSU
CSU
v54industry standard loopback code using v54 pseudorandom loopup and loopdown codes Applies to WIC-1DSU-T1 V2 only
ACC-3000 9743_05_2004_c2
28
T1: Loopback Types

Linea loopback that cross connects the RX signal to the TX signal without correcting any LCVs or framing errors in the RX signal Line payloada loopback that reframes the received T1 data before transmitting it to the source; not applicable to T1 SF links
ACC-3000 9743_05_2004_c2
29
T1: ANSI T1.403 SF Loopback Codes

For SF framing:
Loopback codes are sent in-band; i.e. in the timeslots, and T1 framing is maintained
Action
Loopback Code
Loop Activate Code Loop Deactivate Code
00001 and Repeat for at Least Five Seconds 001 and Repeat for at Least Five Seconds
ACC-3000 9743_05_2004_c2
30
T1: ANSI T1.403 ESF Loopback Codes

For ESF framing:
Loopback codes are sent in the DL a.k.a. FDL bits of the framing overhead and T1 framing is maintained
Action
Line Loop
Payload Loop
Loop Up Code Loop Down Code
0000111011111111 0011100011111111
0001010011111111 0011001011111111
Note: The Right-Most Bit Is Sent First

ACC-3000 9743_05_2004_c2
31
T1: DB-15 and RJ-45 Loopback Plugs

DB 15 Pin Signal Name RJ 45 PIN
1 3 9 11
TX Tip (T1) RX Tip (T1) TX Ring (R1) RX Ring (R)
5 2 4 1
To loopback a DB-15 interface, connect pin 1 to pin 3 and connect pin 9 to pin 11 To loopback a RJ-45 interface, connect pin 1 to pin 4 and connect pin 2 to pin 5
ACC-3000 9743_05_2004_c2
32
T3: show controllers serial

Router#show controllers serial 1/1/0 Serial1/1/0 Mx T3+(1) HW Revision 0x3, FW Revision 3.9 Framing is c-bit, Clock Source is Line Bandwidth limit is 44210, DSU mode 0, Cable length is 10 rx FEBE since last clear counter 16094, since reset 0 Data in current interval (565 seconds elapsed): 0 Line Code Violations, 0 P-bit Coding Violation 17850 C-bit Coding Violation 0 P-bit Err Secs, 0 P-bit Sev Err Secs 0 Sev Err Framing Secs, 7 Unavailable Secs 70 Line Errored Secs, 70 C-bit Errored Secs, 70 C-bit Sev Err Secs No alarms detected
ACC-3000 9743_05_2004_c2
33
T3: show controller Field Explanations

Line Code Violationstotal count of BPVs and excessive zeros conditions P-Bit Coding Violationtotal count of P-bit parity errors where locally calculated parity does not equal P-bit parity code in received M-frame C-Bit Coding Violationfor C-bit framing, total count of Cbit parity errors P-Bit Err Secstotal seconds in which one or more P-bit coding violations, OOF conditions, or received AIS occurred P-Bit Sev Err Secstotal seconds in which 44 or more Pbit coding violations, one or more OOF conditions, or a received AIS occurred Sev Err Framing Secstotal seconds with one or more OOF conditions or received AIS
ACC-3000 9743_05_2004_c2
34
More T3 show controller Field Explanations

Unavailable Secstotal number of seconds the interface has been unusable; unavailable seconds are those between the time the interface experiences 10 P-bit severely errored seconds and time it experiences 10 seconds with no P-bit severely errored seconds; when the interface is unavailable no other interface error counters increment Line Errored Secstotal seconds in which one or more coding violations or LOS defects occurred C-Bit Errored Secstotal seconds in which one or more Cbit coding violations, OOF conditions, or received AIS occurred C-Bit Sev Err Secstotal seconds in which 44 or more C-bit coding violations, one or more OOF conditions, or a received AIS occurred
ACC-3000 9743_05_2004_c2
35
POINT-TO-POINT SONET
ACC-3000 9743_05_2004_c2
36
SONET: Overview
Path Line
Section Section Section
Line
Section
Line
Section
Repeater
ADM
SONET
ADM
Path layerresponsible for the end-to-end communication of the payload data Line layerresponsible for the reliable transmission of the path layer signals Section layertransports the framed electrical signals over an optic fiber
ACC-3000 9743_05_2004_c2
37
SONET: Alarm Indicator Example

RDI-P Downstream
ADM
RDI-L
ADM
SONET
AIS-P
ACC-3000 9743_05_2004_c2
38
SONET: Overview
Router1# show controller pos [snip] POS6/0 SECTION LOF = LINE AIS = PATH AIS = PLM = LOP =
0 0 0 0 0
LOS = 0 RDI = 0 RDI = 0 UNEQ = 0 NEWPTR = 0 FEBE = 0 FEBE = 0 PSE = 0
BIP(B1) = 0 BIP(B2) = 0 BIP(B3) = 0 NSE = 0
Active Defects: None Active Alarms: None Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA
ACC-3000 9743_05_2004_c2
39
SONET: Overview
LOF-S
Out of frame, occurs when four consecutive frames are received with invalid framing patterns (A1, A2); correct pattern is 0xF628
LOS
Loss of Signal, occurs when the signal level drops below the threshold at which a BER of 1 in 1000 is predicted
AIS
Alarm Indication Signal (all ones) sent downstream to indicate an error condition; also defined as AIS-L indicates Line AIS; AIS-P indicates Path AIS
RDI
Remote Defect Indicator, sent to the transmitting terminating equipment when detecting AIS, LOF, or LOS; RDI-L Line Remote Defect Indication; RDI-P Path Remote Defect Indicator (sent in bits 5, 6, and 7 of G1 byte); similar functionality as yellow alarm in DS1/DS3
REI
(FEBE) Remote Error Indication, sent to the transmitting source indicating that a block has been received in error; REI-L Line Remote Error Indication (M0 or M1 byte); REI-P Path Remote Error Indication (sent in bits 14 of G1 byte)
ACC-3000 9743_05_2004_c2
40
SONET: Overview
BIP (B1)
Section parity check of the previous frame
BIP (B2)
Line parity check of the previous frame, includes section
BIP (B3)
Path parity check of the previous frame includes section and line
LOP
Loss Of Pointer, occurs when consecutive invalid pointers are received
NEWPTR
New Pointer, indicates when the pointer is incremented or decremented based on H1 and H2
PSE
Positive Stuff Event, occurs when the incoming interface clock is lagging behind the outgoing interface clock (underflow); results in stuffing the first byte after H3
NSE
Negative Stuff Event, occurs when the incoming interface clock is faster than the outgoing interface (overflow); results in payload byte insertion into H3
ACC-3000 9743_05_2004_c2
41
SONET: Timing
Router1# show controller pos [snip] POS6/0 SECTION LOF = LINE AIS = PATH AIS = PLM = LOP =
0 0 0 5 6
LOS = 0 RDI = 4 RDI = 4 UNEQ = 0 NEWPTR = 3260
BIP(B1) = 8501 FEBE = 1225584230 BIP(B2) = 25748 FEBE = 1890201 PSE = 1101 BIP(B3) = 8947 NSE = 11
Active Defects: SD B1-TCA LRDI B2-TCA PRDI PLOP PPLM B3-TCA RDOOL Active Alarms: B1-TCA B2-TCA B3-TCA Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA
A DS1 transported via SONET VT1.5 can serve as timing reference if SONET transport ring has a single timing source
ACC-3000 9743_05_2004_c2
42
SONET: Troubleshooting Tips

Error Condition Check For
S-LOS, S-LOF, or B1 L-AIS L-RDI B2 P-AIS P-RDI B3 LOP. NEWPTR, PSE, NSE
Link Problems LOS, LOF on Upstream STE AIS on Downstream LTE B1 on Upstream LTE L-AIS Upstream P-AIS on Downstream PTE B1, B2 on Upstream STE/LTE Telco Timing Problems
ACC-3000 9743_05_2004_c2
43
SONET: Alarm Hierarchy

LOS-S LOF-S AIS-L SF RDI-L AIS-P LOP-P RDI-P
Priority 1 (Highest) Priority 2 Priority 3 Priority 4 Priority 5 Priority 6 Priority 7 Priority 8
ACC-3000 9743_05_2004_c2
44
Session Goal
Troubleshooting Process
Check your physical layer first Use your show commands Use your debugs
ACC-3000 9743_05_2004_c2
45
HDLC
ACC-3000 9743_05_2004_c2
46
Ciscos HDLC
Its proprietary because:
It does not perform windowing or retransmission Higher layer protocol identification method is not standardized
Its frame format and bit stuffing technique are per the ANSI T1.618 standard
ACC-3000 9743_05_2004_c2
47
Ciscos HDLC: Frame Format

1 1 1 2 variable 2 1 +----+----+----+--------+---------------------------------------+--------+----+ |flag|addr|ctrl|protocol| data | FCS |flag| |0x7E| |0x00| | | |0x7E| +----+----+----+--------+---------------------------------------+--------+----+ flag = start/end of frame = 0x7E (Other special characters: Idle = 0xFF, Abort = 0x7F) address = this 0x0F 0x80 0x40 0x20 is really a frame type field = Unicast Frame = Broadcast Frame (used if upper layer packet is a broadcast) = Padded Frame = Compressed Frame
Protocol = the Ethernet type of the encapsulated data: 0x0800 IP 0x4242 DSAP/SSAP for IEEE bridge spanning protocol 0x6003 DECnet phase IV 0x6558 Bridged Ethernet/802.3 packet 0x8035 cisco SLARP 0x8038 DEC bridge spanning tree protocol 0x809b Apple EtherTalk 0x80f3 Appletalk ARP 0x8137 Novell IPX 0xFEFE ISO CLNP/ISO ES-IS DSAP/SSAP
ACC-3000 9743_05_2004_c2 48
Ciscos HDLC: Bit Stuffing Technique

Possible Data Pattern: Flag:
01111110 01111110
So They Are Not Confused, We Will Bit Stuff after Five 1s New Data Pattern:
011111010
Stuffed Bit
Stuffed 0 Removed at the Receiver

ACC-3000 9743_05_2004_c2 49
Ciscos HDLC: Why Is Line Protocol Down?

Router A Circuit-Switched Network
Myseq = 2, Yourseen = 101
10 Seconds Mineseen = 2
Router B
Myseq = 2
Myseq = 101
Mineseen = 101
Myseq = 102, Yourseen = 2 Myseq = 3, Yourseen = 102 10 Seconds

Mineseen = 102
Mineseen = 3
Myseq = 103, Yourseen = 3 Myseq = 4, Yourseen = 103
Mineseen = 3 Mineseen = 3 Mineseen = 3

ACC-3000 9743_05_2004_c2
Myseq = 5, Yourseen = 103 Myseq = 6, Yourseen = 103
Line Protocol Down

50
Ciscos HDLC: Debug Serial Interface

From Router A 1 Missed Keepalive
Serial1: HDLC myseq 0, mineseen 0, yourseen 100, line up Serial1: HDLC myseq 1, mineseen 1, yourseen 101, line up Serial1: HDLC myseq 2, mineseen 2, yourseen 102, line up Serial1: HDLC myseq 3, mineseen 3, yourseen 103, line up Serial1: HDLC myseq 4, mineseen 3, yourseen 103, line up Serial1: HDLC myseq 5, mineseen 3, yourseen 103, line up Serial1: HDLC myseq 6, mineseen 3, yourseen 103, line down
3 Missed Keepalives so Line Goes Down and Interface Is Reset

ACC-3000 9743_05_2004_c2
51
Link Testing with HDLC

HDLC has no such protection or addressing, so line protocol will come up PPP not good for link tests due to loopback testing (magic number) Due to DLCI addressing, Frame Relay also not good for loopback testing Once up/up, you can test with PING
ACC-3000 9743_05_2004_c2
52
PPP
ACC-3000 9743_05_2004_c2
53
PPP: Frame Format

Address* Control* Protocol** Payload + Padding Checksum Flag Flag (FCS) 01111110 01111110 11111111 00000011 (12 bytes) (MRU=1500 Default)
Always 0x7E
UI Frame W/p/f (Bit 5) Set to 0 Unique to PPP 24 Bytes
Always 0x7E
Always 0xFF
Standard method for transporting multiprotocol datagrams over point-to-point links Modeled after HDLC frame with addition of protocol field PPP frame size ranges from 10 bytes to 4 bytes (when PFC and ACFC compression are enabled, and without ending flag) Ending flag only needed on single frame or final frame of a sequence
*Omitted when Address and Control Field Compression (ACFC) Is Used **Only 1 Byte when Protocol Field Compression (PFC) Is Used
ACC-3000 9743_05_2004_c2
54
PPP: Protocols (Protocol Field)

Value (in Hex): Protocol Name:
0001 0003 to 001f 007d 00cf 00ff 8001 to 801f 8031 80fd c021 c023 c025 c029 c02b c02d c223
ACC-3000 9743_05_2004_c2
Padding Protocol Reserved (Transparency Inefficient) Reserved (Control Escape) Reserved (PPP NLPID) Reserved (Compression Inefficient) Unused [RFC1661] Bridging NCP Compression Control Protocol (CCP) [RFC1962] Link Control Protocol Password Authentication Protocol Link Quality Report CallBack Control Protocol (CBCP) BACP Bandwidth Allocation Control Protocol [RFC2125] BAP [RFC2125] Challenge Handshake Authentication Protocol
55
PPP: Simplified Phase Diagram
Dead
Up
Establish
Opened
Authenticate
Success or None (No Authentication Used)
Fail
Fail Closing
Down
Terminate
Network
ACC-3000 9743_05_2004_c2
56
Open
Dead
Est. Term.
Auth. Netw.
PPP: LCP (Link Control Protocol)

Circuit-Switched Network
LCP: Negotiate link-specific options:

Callback Multilink (MRRU) or non-multilink (MRU) Authentication method: PAP/CHAP (optional) Magic number (loopback detection) PFC (Protocol Field Compression) ACFC (Address and Control Field Compression) ACCM (Async Control Character Map)
ACC-3000 9743_05_2004_c2
57
Open
Dead
Est. Term.
Auth. Netw.
PPP: LCP Configuration Options
Used to modify the default link characteristics

Common LCP options:
0x00 0x02 0x02 0x03 0x04 0x05 0x07 0x08 0x0D 0x11 0x12 0x13
ACC-3000 9743_05_2004_c2
RESERVED [RFC2153] Maximum-Receive-Unit (a.k.a., non-multilink) ACCM Authentication-Protocol Quality-Protocol Magic-Number Protocol-Field-Compression Address-and-Control-Field-Compression Callback [RFC1570] Multilink-MRRU [RFC1717] Multilink-Short-Sequence-Number-Header [RFC1717] Multilink-Endpoint-Discriminator [RFC1717]
58
Open
Dead
Est. Term.
Auth. Netw.
PPP: LCP Negotiation

In reality all PPP negotiations are double negotiations Configure-Req Configure-ACK Configure-Req Configure-ACK
ACC-3000 9743_05_2004_c2
59
PPP: Simplified Phase Diagram
Dead
Up
Establish
Opened
Authenticate
Fail
Fail Closing
Down
Terminate
Network
ACC-3000 9743_05_2004_c2
60
Open
Dead
Est. Term.
Auth. Netw.
PPP: Authentication
Circuit-Switched Network
Authentication follows LCP phase Authentication protocols (LCP option 3)

PAP (0xC023)* CHAP (0xC223, Algorithm 0x05)*
*Prior to Cisco IOS V11.2, These Values Were Not Decoded in PPP Debugs
ACC-3000 9743_05_2004_c2
61
PPP: PAP Authentication Protocol

Remote Router (Santa Cruz)
Open
Dead
Est. Term.
Auth. Netw.
2-Way Handshake
Santa Cruz, Boardwalk
Central-Site Router (HQ)
Accept/Reject IOS Configuration: Hostname: Santacruz Password: Boardwalk Local Database: Username Santacruz Password Boardwalk
Passwords sent in clear text Peer (client) in control of attempts Performed only once per session
ACC-3000 9743_05_2004_c2
62
PPP: CHAP Authentication Protocol

Remote Router (Santa Cruz)
Open
Dead
Est. Term.
Auth. Netw.
3-Way Handshake
Challenge W/key
Central-Site Router (HQ)
IOS Configuration: Hostname: Santacruz Local Database Username Santacruz Password: Boardwalk
Response W/MD5 Hash Accept/Reject Local Database: Username Santacruz Password Boardwalk
Password never sent across wire Challenger in control of attempts Authenticate multiple times per connection
ACC-3000 9743_05_2004_c2
63
Simplified PPP Phase Diagram
Dead
Up
Establish
Opened
Authenticate
Fail
Fail Closing
Down
Terminate
Network
ACC-3000 9743_05_2004_c2
64
Dead
Est. Term.
Auth. Netw.
PPP: Network Control Protocol

Dial-Up or Circuit-Switched Network
Negotiate which Layer 3 protocol(s) to use:

For IP: IPCP For IPX: IPXCP For AppleTalk: ATCP For Bridging: BridgeCP
Each of the above have protocol-specific options that must be negotiated (protocol address, etc.)
ACC-3000 9743_05_2004_c2
65
PPP Verification
2621#show interface serial0/0 Serial0/0 is up, line protocol is up PPP Is Hardware is PQUICC with Fractional T1 CSU/DSU Internet address is 10.1.3.1/29 Configured MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, loopback not set Shows the Configured Keepalive set (10 sec) Network Protocols LCP Open Open: IPCP, CDPCP Last input 00:00:21, output 00:00:01, output hang never Last clearing of "show interface" counters 20:36:48 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queuing strategy: weighted fair Output queue: 0/1000/64/0 (size/max total/threshold/drops) Conversations 0/1/256 (active/max active/max total) Reserved Conversations 0/0 (allocated/max allocated) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 32146 packets input, 1616707 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 302 input errors, 44 CRC, 258 frame, 0 overrun, 0 ignored, 0 abort 32173 packets output, 1616197 bytes, 0 underruns 0 output errors, 0 collisions, 4 interface resets 0 output buffer failures, 0 output buffers swapped out 2 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up
ACC-3000 9743_05_2004_c2
66
PPP: Troubleshooting
Debug ppp negotiation Debug ppp authentication Debug ppp multilink events Service timestamps debug date msec Service timestamps log date msec
ACC-3000 9743_05_2004_c2
67
PPP: Things to Look for in PPP Debugs

LCP: State is open
LCP negotiation was successful If not, then look for options that failed during LCP negotiation by observing the CONFREQ, CONFREJ, CONFACK, and CONFNACK activity
Dead Open Auth. Est. Term. Netw. Success (or None)
Authentication: PAP or CHAP

Check for username, passwords, etc.
Dead
Est. Term.
Auth. Netw.
NCP: IPCP, IPXCP, ATCP state is open

Means NCP negotiation was successful If not, then monitor NCP negotiation by observing the CONFREQ, CONFREJ, CONFACK, and CONFNACK activity
Dead Est. Term. Auth. Netw. (Open)
ACC-3000 9743_05_2004_c2
68
Open
Dead
Est. Term.
Auth. Netw.
Debug PPP Negotiation

Notice the two-way hand shaking
May May May May May May May May May May May May May 1 1 1 1 1 1 1 1 1 1 1 1 1 15:02:57.763: 15:02:57.763: 15:02:57.763: 15:02:57.783: 15:02:57.783: 15:02:57.783: 15:02:57.783: 15:02:57.783: 15:02:57.783: 15:02:57.783: 15:02:57.783: 15:02:57.783: 15:02:57.783: Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 LCP: LCP: LCP: LCP: LCP: LCP: LCP: LCP: LCP: LCP: LCP: LCP: LCP:
O CONFREQ [REQsent] id 135 len 14 AuthProto PAP (0x0304C023) MagicNumber 0x1F7A2545 (0x05061F7A2545) I CONFREQ [REQsent] id 108 len 14 AuthProto PAP (0x0304C023) MagicNumber 0x1F7A2A52 (0x05061F7A2A52) O CONFACK [REQsent] id 108 len 14 AuthProto PAP (0x0304C023) MagicNumber 0x1F7A2A52 (0x05061F7A2A52) I CONFACK [ACKsent] id 135 len 14 AuthProto PAP (0x0304C023) MagicNumber 0x1F7A2545 (0x05061F7A2545) State is Open
0x0304C023 ^ ^ ^ | | | | | Value = C023 = PAP | Length = 4 Octets Type = Authentication Method (RFC 1172)
ACC-3000 9743_05_2004_c2
0x05061F7A2545 ^ ^ ^ | | | | | Value = 0x1F7A2545 | Length = 6 Octets Type = Magic Number

69
Open
Dead
Est. Term.
Auth. Netw.

Notice the two-way hand shaking
May May May May May May May 1 1 1 1 1 1 1 15:02:57.783: 15:02:57.803: 15:02:57.835: 15:02:57.847: 15:02:57.847: 15:02:57.863: 15:02:57.863: Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 PPP: PAP: PAP: PAP: PAP: PAP: PPP:
Phase is AUTHENTICATING, by both [0 sess, 1 load] O AUTH-REQ id 11 len 18 from "router1" I AUTH-REQ id 11 len 18 from "router2" Authenticating peer router2 O AUTH-ACK id 11 len 5 I AUTH-ACK id 11 len 5 Phase is UP [0 sess, 2 load]
ACC-3000 9743_05_2004_c2
70
Dead
Est. Term.
Auth. Netw.

May May May May May May May May May May May May May May May 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 15:02:57.863: 15:02:57.863: 15:02:57.863: 15:02:57.863: 15:02:57.863: 15:02:57.863: 15:02:57.863: 15:02:57.863: 15:02:57.863: 15:02:57.875: 15:02:57.875: 15:02:57.875: 15:02:57.875: 15:02:57.875: 15:02:57.983: Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0 Se8/0
IPCP: O CONFREQ [Closed] id 17 len 10 IPCP: Address 10.1.1.1 (0x03060A010101) CDPCP: O CONFREQ [Closed] id 17 len 4 IPCP: I CONFREQ [REQsent] id 17 len 10 IPCP: Address 10.1.1.2 (0x03060A010102) IPCP: O CONFACK [REQsent] id 17 len 10 IPCP: Address 10.1.1.2 (0x03060A010102) CDPCP: I CONFREQ [REQsent] id 18 len 4 CDPCP: O CONFACK [REQsent] id 18 len 4 IPCP: I CONFACK [ACKsent] id 17 len 10 IPCP: Address 10.1.1.1 (0x03060A010101) IPCP: State is Open CDPCP: I CONFACK [ACKsent] id 17 len 4 CDPCP: State is Open IPCP: Install route to 10.1.1.2 !^^^^^^^^^^^^^^^^^^^^^^^^^ ! /32 Route
0x03060A010101 ^ ^ ^ | | | | | Value = 0x0A010101 = 10.1.1.1 | Length = 6 Octets Type = IP Address (RFC 1332)
ACC-3000 9743_05_2004_c2
Notice the two-way handshaking

71
FRAME RELAY
ACC-3000 9743_05_2004_c2
72
Frame Relay Overview

Data Frame Relay Cloud
Uni User-Side
LMI Uni Network-Side Status Enquiry Status

10 Seconds
Uni Network-Side
LMI Uni User-Side Status Enquiry Status

10 Seconds
Status Enquiry Status

Every Sixth Status Enquiry
Status Enquiry Status

Every Sixth Status Enquiry
Full Status Enquiry Full Status
Full Status Enquiry Full Status
Cisco LMI DLCI = 1023, ANSI and ITU-T (q933a) LMI DLCI = 0
ACC-3000 9743_05_2004_c2
73
Frame Relay Packet

Bits Q.922 Header 1 2 4 5 Flag (0x7E) DLCI (High Order) Control (0x03) NLPID (1 Byte) Data (Variable Length) FCS (2 Bytes) SNAP Format3 Byte OUI and 2 Byte PID OUI PID 0x00 00 00 routed Ethertype 0x00 80 C2 bridged With Preserved FCS 0x00 01 0x00 02 0x00 03 0x00 04 3 6 7 8 NLPID 0x08 0x80 0x81 0xCC 0xB1 Protocol Q.933 SNAP ISO CLNP Internet IP FRF.12 C/R EA = 0
DLCI (Low Order)
FECN BECN DE EA = 1
W/O FCS 0x00 07 0x00 08 0x00 09 0x00 0A 0x00 0D 0x00 0E 0x00 0F
Media 802.3/Ethernet 802.4 802.5 FDDI Fragments BPDUs Source-Routing BPDUs
Note: Cisco Encap Uses 2 Byte Ethertype Instead of the Control and NLPID Bytes
ACC-3000 9743_05_2004_c2
74
Frame Relay: Terms

DLCIData Link Connection Identifier
10 bit address for a frame relay connection; it only has local significance; DLCIs 16-1007 are definable on Cisco routers
FECNForward Explicit Congestion Notification

This bit may be flipped by nodes in the cloud when it experiences congestion in its path to the destination remote FRAD
BECNBackward Explicit Congestion Notification

This bit may be flipped by nodes in the cloud when packets in the opposite direction of this packet experience congestion
DEDiscard Eligible
This bit may be flipped by nodes in the cloud to indicate that packet exceeded the rate the carrier has committed to transport; packets with the DE bit set may be intentionally dropped by frame relay nodes in the face of congestion
ACC-3000 9743_05_2004_c2
75
Frame Relay: LMI

Supported on both UNI and NNI interfaces UNI LMI is defined in three different standards:
Consortium LMI (Frame Relay lmi-type cisco) ANSI T1.617 Annex D LMI (Frame Relay lmi-type ansi) ITU-T Q.933 Annex A LMI (Frame Relay lmi-type q933a)
LMI has a Q.931 header directly after the 2 byte header and 1 byte control (0x03) Full status update includes all the DLCIs and their status (i.e. ACTIVE, INACTIVE, DELETED, etc.)
ACC-3000 9743_05_2004_c2
76
Frame Relay: Interface Types

Multipoint
Default Require DLCI to IP mapping Static = frame relay map Dynamic = inverse arp (default) Can configure multiple DLCIs
e0 s0 Frame Relay Cloud s1 e0
s1
e0
Point to point
Only one DLCI per interface No map or inverse arp needed
e0 s0 Frame Relay Cloud s1 e0
Multipoint can be point to

point with sub-interfaces
s0.1 s0.2
ACC-3000 9743_05_2004_c2
Frame Relay Cloud
s1.1
s1
77
Frame Relay: Debugging

Router#debug frame-relay packet Router#ping 10.5.5.5 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.5.5.5, timeout is 2 seconds: *Mar 6 15:33:17.294: Serial0/0.102:Encaps failed--no map entry link 7(IP) *Mar 6 15:33:17.858: Serial0/0.102(o): dlci 102(0x1861), pkt encaps 0x0300 0x8000 0x0000 0x806 (ARP), datagramsize 34 *Mar 6 15:33:17.858: FR: Sending INARP Request on interface Serial0/0.102 dlci 102 for link 7(IP) *Mar 6 15:33:17.950: broadcast dequeue *Mar 6 15:33:17.950: Serial0/0.102(o):Pkt sent on dlci 102(0x1861), pkt encaps 0x300 0x8000 0x0 0x806 (ARP), datagramsize 34 *Mar 6 15:33:17.962: Serial0/0.102: frame relay INARP received. Router#show frame map Serial0/0.102 (up): ip 10.5.5.4 dlci broadcast, CISCO, status defined, Serial0/0.102 (up): ip 10.5.5.5 dlci broadcast, CISCO, status defined, 102(0x66,0x1860), static, active 102(0x66,0x1860), dynamic, active
Make sure broadcast keyword is on end of map statement so routing updates (and other broadcast packets) will pass
ACC-3000 9743_05_2004_c2
78
Frame Relay: Debugging LMI

Router# *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 *Mar 6 debug frame-relay lmi 17:46:50.797: Serial0/0(in): Status, myseq 137 17:46:50.797: RT IE 1, length 1, type 1 17:46:50.797: KA IE 3, length 2, yourseq 137, myseq 137 17:47:00.789: Serial0/0(out): StEnq, myseq 138, yourseen 137, DTE 17:47:00.789: datagramstart = 0x1BE69F4, datagramsize = 13 17:47:00.789: FR encap = 0xFCF10309 17:47:00.789: 00 75 01 01 00 03 02 8A 89 17:47:00.789: 17:47:00.801: Serial0/0(in): Status, myseq 138 17:47:00.801: RT IE 1, length 1, type 0 17:47:00.801: KA IE 3, length 2, yourseq 138, myseq 138 17:47:00.801: PVC IE 0x7 , length 0x6 , dlci 100, status 0x2 , bw 17:47:00.801: PVC IE 0x7 , length 0x6 , dlci 101, status 0x2 , bw 17:47:00.801: PVC IE 0x7 , length 0x6 , dlci 102, status 0x2 , bw
up
0 0 0
0x0 is added/inactive 0x4 is deleted 0x2 is added/active 0x8 is new/inactive
0xa is new/active
ACC-3000 9743_05_2004_c2
79
Frame Relay: Show Frame Relay PVC

Router#show Frame-Relay pvc 100 PVC Statistics for interface Serial0/0 (Frame Relay DTE) DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0.100 input pkts 19962 output pkts 25727 in bytes 297929 out bytes 2120032 dropped pkts 42 in FECN pkts 0 in BECN pkts 0 out FECN pkts 0 out BECN pkts 0 in DE pkts 0 out DE pkts 0 out bcast pkts 5775 out bcast bytes 1778682 pvc create time 4d00h, last time pvc status changed 20:02:22
If DLCI is configured on the router then USAGE = LOCAL If DLCI is not configured on the router but switch is reporting the DLCI, then USAGE = UNUSED If keepalives are disabled, then STATUS = STATIC If DLCI is defined on the router but not switch, then STATUS = DELETED If DLCI is defined on switch but the pvc is not up (i.e. network failure), then STATUS = INACTIVE If DLCI is defined on the switch and is enabled, then STATUS = ACTIVE
ACC-3000 9743_05_2004_c2
80
Why Use Frame Relay Traffic Shaping?
Max Be Bc Kilobytes Sent

ne Li ( e) at R
R CI
DE Domain
IR
Time (Seconds)
ACC-3000 9743_05_2004_c2
1
81
What Were Trying to Avoid

Router A
Frame Relay Cloud BECNs
Data with Congestion
Router B
Congestion
FECNs (in Congested Frames)
Router#show Frame-Relay pvc 401 PVC Statistics for interface Serial1/0:0 (Frame Relay DTE) DLCI = 401, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0:0.401 input pkts 3420 output pkts 50150 in bytes 4974630 out bytes 75255200 dropped pkts 0 in FECN pkts 737 in BECN pkts 275 out FECN pkts 0 out BECN pkts 0 in DE pkts 91 out DE pkts 0 out bcast pkts 150 out bcast bytes 55200 pvc create time 02:28:23, last time pvc status changed 02:26:45
ACC-3000 9743_05_2004_c2
82
Frame Relay Traffic Shaping Facts

Frame Relay Traffic Shaping (FRTS) takes the frame relay header and encapsulation into account The default value for mincir is CIR/2 FRTS will activate without input BECNs if the instantaneous bit rate exceeds configured CIR
ACC-3000 9743_05_2004_c2
83
More FRTS Facts

FRTS works on a token-bucket algorithm Excess burst bits (Be) above committed burst bits (Bc) are only sent in the 1st FRTS interval (Tc) after a quiet period Terms:
CIR = this is rate you want to normally send at when there is no congestion; often line rate; measured in bits/second MinCIR = this is what you will slow down to during congestion; usually the purchased CIR; measured in bits/second Bc = this is amount you will send per interval Tc; rule of thumb is to make it 1/8 CIR; measured in bits Be = this is extra amount to send in the first interval; usually set to 0 because with CIR set to line rate, you are already transmitting at the highest possible rate; measured in bits
ACC-3000 9743_05_2004_c2
84
Configuring FRTS
Example configuration:
interface Serial1/0:0 encapsulation Frame-Relay Frame-Relay traffic-shaping ! interface Serial1/0:0.401 point-to-point Frame-Relay class 64k Frame-Relay interface-dlci 401 ! map-class Frame Relay 64k Frame-Relay cir 64000 ! CIR = 64k Frame-Relay bc 8000 ! BC = CIR / 8 Frame-Relay be 0 Frame-Relay mincir 48000 ! Purchased CIR Frame-Relay adaptive-shaping becn
ACC-3000 9743_05_2004_c2
85
Frame: ATM Interworking FRF.5

The Frame Relay (FR) to ATM network interworking function allows FR traffic to be transported through an ATM network; FRF.5 enables two FR end stations to communicate with each other through an ATM network
Serial 5/0:1 Serial 4/0/0:1 ATM 0/1/1 ATM 0/1/1 Serial 4/1/0.1 Serial 4/1/0.1
E1
OC-3
OC-3
E1
ATM
Router 1 ATM Switch 1 ATM Switch 2 Router 2
ACC-3000 9743_05_2004_c2
86
Frame: ATM Interworking FRF.8

The Frame Relay to ATM service interworking function allows communication between a FR end user and an ATM end user; it is based on the Frame Relay Forum (FRF.8) implementation agreement
Serial 5/0:30 T1 Router 1 (Frame Relay) DS-3 ATM 2/0.123 DS-3
ATM
ATM Switch Router 2 (ATM)
FR Router
IW Switch
ATM Router
FR IETF FR IETF
ACC-3000 9743_05_2004_c2
SIW-X (Translational) SIW-T (Transparent)
Aal5snap RFC2684/1483 Aal5nlpid RFC2427/1490

87
Frame: ATM Interworking Troubleshooting

Use the same debug tools with ATM-FR interworking as you would use with a frame relay connection or an ATM connection When in doubt, always use IETF encapsulation on the frame relay side FRF.8 allows for OAM cells to be translated to LMI status updates; therefore, the following sections on OAM management should be considered for managing ATM-FR connections as well
ACC-3000 9743_05_2004_c2
88
WAN ATM
ACC-3000 9743_05_2004_c2
89
ATM Topics
Understand ATM Encapsulation Traffic Shaping vs. Policing OAM IMA
ACC-3000 9743_05_2004_c2
90
Understanding ATM Encapsulation

ATM Adaptation Layers: AAL5 (RFC1483/RFC2684)
AAL5 Is the Primary AAL for Data and Supports Both Connection-Oriented and Connectionless Data
Data
First Step (Convergence Sublayer )
Important!
PAD Trailer CRC
Data
Second Step (SAR)
48 Byte Fragment 48 Byte Fragment
48 Byte Fragment
Third Step (Adding Header)

5 Byte Header
ACC-3000 9743_05_2004_c2
48 Byte Fragment
91
ATM: Whats an ATM CRC Error? Its the CRC from the AAL5 Frame!!!
Data
PAD Trailer
HERE!
CRC
48 Byte Fragment
48 Byte Fragment
48 Byte Fragment
AAL5 CRC is calculated over entire frame AAL5 frame consists of multiple cells Reasons for CRC errors
Cell losscommonly due to cloud policing Cell corruptionLayer 1 issues Faulty ATM interfacehardware problem
ACC-3000 9743_05_2004_c2
92
ATM: Finding CRC Errors

Use the command:
show interfaces atm slot/port To identify the presence of CRC errors on an ATM interface
ACC-3000 9743_05_2004_c2
93
ATM: CRC Example

Router#show interfaces atm 4/0 ATM4/0 is up, line protocol is up Hardware is cxBus ATM Internet address is 131.108.97.165, subnet mask is 255.255.255.0 MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255 ATM E164 Auto Conversion Interface Encapsulation ATM, loopback not set, keepalive set (10 sec) Encapsulation(s): AAL5, PVC mode 256 TX buffers, 256 RX buffers, 1024 Maximum VCs, 1 Current VCs Signaling vc = 1, vpi = 0, vci = 5 ATM NSAP address: BC.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.13 Last input 0:00:05, output 0:00:05, output hang never Last clearing of "show interface" counters never Output queue 0/40, 0 drops; input queue 0/75, 0 drops Five minute input rate 0 bits/sec, 0 packets/sec Five minute output rate 0 bits/sec, 0 packets/sec 144 packets input, 31480 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants 13 input errors, 12 CRC, 0 frame, 0 overrun, 1 ignored, 0 abort 154 packets output, 4228 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets, 0 restarts
ACC-3000 9743_05_2004_c2
94
ATM Traffic Shaping and Policing
RX TX
Router Traffic Shaping Takes Place
TX RX
ATM Switch
ATM Cloud
RX TX
Router
TX RX
Policing Takes Place ATM Switch
ATM Cloud
ACC-3000 9743_05_2004_c2
95
ATM: Are We Exceeding PCR/SCR? Pinging with Large Packets

Router#ping Protocol [ip]: Target IP address: 10.2.1.2 Repeat count [5]: 100 Datagram size [100]: 1500 Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 100, 1500-byte ICMP Echos to 10.2.1.2, timeout is 2 seconds: !!!.!!.!!!.!!.!!!.!!.!!!.!!.!!!.!!.!!!.!!.!!!.!!.!!!.!!.!!!.!!.!!!.!!.!!!.!!.!!! .!!.!!!.!!.!!!.!!.!
Work with ATM provider to compare VC settings (PCR, SCR, CDVT)
ACC-3000 9743_05_2004_c2
96
ATM: Are We Exceeding PCR/SCR?

Router#show interfaces atm 4/0 ATM4/0 is up, line protocol is up [snip] Last input 0:00:05, output 0:00:05, output hang never Last clearing of "show interface" counters 00:00:05 Output queue 0/40, 727 drops; input queue 0/75, 0 drops Five minute input rate 0 bits/sec, 0 packets/sec Five minute output rate 5025 bits/sec, 1105 packets/sec 144 packets input, 31480 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants 13 input errors, 12 CRC, 0 frame, 0 overrun, 1 ignored, 0 abort 154 packets output, 4228 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets, 0 restarts
show interface atm command; the traffic shaper should start dropping packets when the average traffic volume reaches SCR
ACC-3000 9743_05_2004_c2
97
ATM: Are We Exceeding PCR/SCR?

Router#show atm pvc test ATM2/IMA0.294: VCD: 5, VPI: 7, VCI: 192, Connection Name: test VBR-NRT, PeakRate: 500, Average Rate: 500, Burst Cells: 100 AAL5-LLC/SNAP, etype:0x0, Flags: 0x20, VCmode: 0x0 *****snipped OAM***** InARP frequency: 15 minutes(s) Transmit priority 2 InPkts: 0, OutPkts: 5, InBytes: 0, OutBytes: 500 InPRoc: 0, OutPRoc: 6 InFast: 0, OutFast: 0, InAS: 0, OutAS: 0 InPktDrops: 0, OutPktDrops: 727 CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0 *****snipped OAM***** Status: UP
Only available, per VC, on the PA-A3 and on Cisco 2600 and 3600 routers (DS3, E3, OC3, and IMA interfaces)
ACC-3000 9743_05_2004_c2
98
ATM: Router vs. Switch Implementation

RX TX TX RX
ATM Cloud
Router
Rates counted in bits per second (bps) The PCR and SCR bps values count the bits of the entire cell
Cisco ATM Switch

Rate counted in cells per second (cps) PCR and SCR assigned in CPS
Example: Want SCR [in bps] Rate of Data

Configure the Router to: SCR [in bps] * 53 / 48 bps
ACC-3000 9743_05_2004_c2
Configure the Switch to: roundup[SCR [in bps] / (8 * 48)] CPS

99
ATM: Verifying the Local Interface

Place a physical loopback on the interface and ping your own IP address Create a soft loopback with the loopback diagnostic and atm clock internal commands on the main ATM interface If loopbacks fail, try other ports on the same card If card looks suspect, move it to another slot in the chassis and retest
ACC-3000 9743_05_2004_c2
100
ATM: OAM Cells

In order to detect a failure along the PVC path on an end-device, OAM uses specific cells:
Loopback cells Continuity Check (CC) cells Alarm Indication Signal (AIS) cells RDI cells (Remote Detection Indication)
ACC-3000 9743_05_2004_c2
101
ATM: Loopback Cells

Two types (for both PVP and PVC)
Segment End-to-end End-to-End
Segment
Segment
Without OAM management, a PVC would remain up upon communication problems, and routing entries pointing to that PVC would remain in the RT
ACC-3000 9743_05_2004_c2
102
ATM: OAM F4 and F5 Flows

F4 OAM Cells Are Used for Monitoring VPCs: Preassigned VCI: VPI: VCI = 3 for Segment OAM VCI = 4 for End-to-End OAM VPI = Same as the One Being Checked
F5 OAM Cells Are Used for Monitoring VCCs; the F5 OAM Cell Provides a VC-Level Loopback: PTI = 100 PTI = 101 Segment OAM F5 Cell End-to-End OAM F5 Cell
ACC-3000 9743_05_2004_c2
103
ATM: OAM Cell Format (F4-VPC)

ATM Cell Header
G F C VPI VCI PT C L HEC P OAM Type
ATM Cell Payload

Function Function Specific CRC 10 Fields Type
VCI = 3 (Segment) VCI = 4 (End-to-End) Same as 0001 User Cell 0010 1000
0000 0001 0010
AIS FERF Loopback
Fault Management Performance Management Activation/Deactivation
ACC-3000 9743_05_2004_c2
104
ATM: OAM Cell Format (F5-VCC)

ATM Cell Header
G F C VPI VCI PT C L HEC P OAM Type
ATM Cell Payload

Function Function Specific CRC 10 Fields Type
PT = 100 (Segment) PT = 101 (End-to-End) Same as 0001 User Cell 0010 1000
0000 0001 0010
AIS FERF Loopback
Fault Management Performance Management Activation/Deactivation
ACC-3000 9743_05_2004_c2
105
ATM: AIS/RDI Cells (Diagram)

Upon detection of a failure, a device configured for OAM sends AIS frames downstream and sends RDI frames upstream
Tx
Rx
OAM AIS
Rx Tx OAM RDI
ACC-3000 9743_05_2004_c2
106
ATM: Detecting Failures

There Are Three Conditions to Declare a PVC UP
1. The router receives a configured number of successive end-to-end F5 OAM loopback cell replies 2. The router does not receive F5-AIS cells for 3 seconds 3. The router does not receive F5-RDI cells for 3 seconds
ACC-3000 9743_05_2004_c2
107
ATM: Sample Network Diagram
Command LB cell (LoopInd = 1) 1/116
Router1 Response LB cell Switch1 Response LB cell Switch2 LoopInd = 0 LoopInd = 0
Response LB cell LoopInd = 0
Router2
ACC-3000 9743_05_2004_c2
108
ATM: debug atm oam (Showing Only One Side)

Mar 30 14:22:39.050: ATM OAM(ATM2/0/0.116): Timer: VCD#4 VC 1/116 Status:2 CTag:17128 Tries:0 Mar 30 14:22:39.050: ATM OAM LOOP(ATM2/0/0.116) O: VCD#4 VC 1/116 CTag:42E9 Mar 30 14:22:39.050: ATM OAM LOOP(ATM2/0/0) I: VCD#4 VC 1/116 LoopInd:0 CTag:42E9 Mar 30 14:22:48.958: ATM OAM(ATM2/0/0.116): Timer: VCD#4 VC 1/116 Status:2 CTag:17129 Tries:0 Mar 30 14:22:48.958: ATM OAM LOOP(ATM2/0/0.116) O: VCD#4 VC 1/116 CTag:42EA Mar 30 14:22:48.958: ATM OAM LOOP(ATM2/0/0) I: VCD#4 VC 1/116 LoopInd:0 CTag:42EA
Successfully acknowledged OAM cells 0x42E9 From 12.3(7.2), the CTag is displayed always in hexadecimal form
*Dec 9 19:48:50.463: ATM OAM LOOP(ATM2/0/0.1) O: VCD#10 VC 121/50 CTag:0x242
= 17129
*Dec 9 19:48:50.531: ATM OAM LOOP(ATM2/0/0) I: VCD#10 VC 121/50 LoopInd:0 CTag:0x242 OAM Cell Type 5 *Dec 9 19:49:00.427: ATM OAM(ATM2/0/0.1): Timer: VCD#10 VC 121/50 Status:2 CTag:0x242 Tries:0
ACC-3000 9743_05_2004_c2
109
ATM: debug atm oam (Cell Loss)

Mar 30 14:48:41.684: ATM OAM(ATM2/0/0.116): Timer: VCD#4 VC 1/116 Status:1 Tag:17285 Tries:0 Mar 30 14:48:41.684: atm_oam_setstate - VCD#4, VC 1/116: newstate = Down Retry Mar 30 14:48:41.684: ATM OAM LOOP(ATM2/0/0.116) O: VCD#4 VC 1/116 CTag:4386 Mar 30 14:48:42.680: ATM OAM(ATM2/0/0.116): Timer: VCD#4 VC 1/116 Status:1 CTag:17286 Tries:1 <- timer expires after 1 second, and sends another OAM cell Mar 30 14:48:42.680: Mar 30 14:48:43.680: Tries:2 Mar 30 14:48:43.680: Mar 30 14:48:44.680: Tries:3 Mar 30 14:48:44.680: Mar 30 14:48:45.676: Tries:4 Mar 30 14:48:45.676: ATM OAM LOOP(ATM2/0/0.116) O: VCD#4 VC 1/116 CTag:4387 ATM OAM(ATM2/0/0.116): Timer: VCD#4 VC 1/116 Status:1 CTag:17287 ATM OAM LOOP(ATM2/0/0.116) O: VCD#4 VC 1/116 CTag:4388 ATM OAM(ATM2/0/0.116): Timer: VCD#4 VC 1/116 Status:1 CTag:17288 ATM OAM LOOP(ATM2/0/0.116) O: VCD#4 VC 1/116 CTag:4389 ATM OAM(ATM2/0/0.116): Timer: VCD#4 VC 1/116 Status:1 CTag:17289 ATM OAM LOOP(ATM2/0/0.116) O: VCD#4 VC 1/116 CTag:438A
Mar 30 14:48:46.676: ATM OAM(ATM2/0/0.116): Timer: VCD#4 VC 1/116 Status:1 CTag:17290 Tries:5 <- the router makes 5 retries before declaring the PVC Mar 30 14:48:46.676: atm_oam_setstate - VCD#4, VC 1/116: newstate = Not Verified
down
Mar 30 14:48:46.676: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM2/0/0.116,changed state to down Mar 30 14:48:46.676: ATM OAM LOOP(ATM2/0/0.116) O: VCD#4 VC 1/116 CTag:438B
ACC-3000 9743_05_2004_c2
110
ATM: sh atm pvc (OAM)

Router1# sh atm pvc 1/116 *snip* AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0 OAM frequency: 10 second(s), OAM retry frequency: 1 second(s) OAM up retry count: 3, OAM down retry count: 5 OAM Loopback status: OAM Sent *snip* OAM cells received: 9 F5 InEndloop: 9, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0 F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0 OAM cells sent: 18 F5 OutEndloop: 18, F5 OutSegloop: 0, F5 OutRDI: 0 F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0 OAM cell drops: 0 Status: DOWN, State: NOT_VERIFIED
ACC-3000 9743_05_2004_c2
111
ATM: Inverse Multiplex over ATM

IMA Link IMA Group
nxT1/E1 Links
IMA uses IMA Control Protocol (ICP) Cells Transmitted periodically To transmit information to reconstruct the ATM cell stream
ICP cells are served in round robin fashion ICP cells provide order of links in the group
ACC-3000 9743_05_2004_c2
112
ATM: Troubleshooting IMA

The show ima interface Command
Router#show ima interface atm2/IMA2 Interface atm2/IMA2 is up Group index is 2 Ne state is operational, failure status is noFailure State active links bitmap 0x30 IMA Group Current Configuration: TX/Rx configured links bitmap 0x30/0x30 TX/Rx minimum required links 1/1 Config Maximum allowed diff delay is 25ms, TX frame length 128 NE TX clock mode CTC, configured timing reference link atm2/4 Test pattern procedure is disabled atm2/5 IMA Group Current Counters (time elapsed 12 seconds): 3 NE Failures, 3 Fe Failures, 4 Unavail Secs IMA Group Total Counters (last 0 15 minute intervals): 0 NE Failures, 0 Fe Failures, 0 Unavail Secs IMA link Information: Link Physical Status NearEnd Rx Status Test Status ------------------ --------------------------Links atm2/4 down unusableFailed disabled atm2/5 up active disabled
ACC-3000 9743_05_2004_c2
113

The show controllers atm Command for Physical Interfaces
ATM#show controllers atm 2/4 !Part of IMA group 2 <snip> Link 2 IMA Info: group index is 2 Tx link id is 2, TX link state is unusableFault Rx link id is 99, Rx link state is unusableFailed Rx link failure status is lodsFailure, 1 TX failures, 3 rx failures <snip>
LINK FAILURE CONDITIONS: Loss of IMA Frame (LIF)Interface is experiencing an out of IMA frame (OIF) or loss of synchronization state for at least two IMA frames; when this fault condition is active, the IMA sublayer replaces all received data cells with filler cells Loss of Delay Synchronization (LODS)Interface has detected the timing delay between this link and other links in the IMA group has exceeded the configured maximum value
ACC-3000 9743_05_2004_c2
114
ATM: IMA Main States in Link State Machine

State Description
Not in Group Link Is Not Configured to Be an IMA Group Member Unusable Usable Active Blocking Link Is Configured to Be an IMA Group Member, But Is Not in Use Due to Fault or Inhibition; Link Error Conditions Can Lead to an Unusable State Link Is Ready to Operate, But Is Waiting for the Other End to Be Usable or Active Link Is Capable of Passing ATM Layer Cells from and to the ATM Layer (Receive State Only) Link Is Transitioning to the Unusable State; Allows Graceful Transition into the Unusable State without Loss of ATM Cells
ACC-3000 9743_05_2004_c2
115

The show controllers atm Command for IMA Virtual Interfaces
ATM#show controllers atm1/ima0 Interface ATM1/IMA0 is down Hardware is ATM IMA [snip] atm channel number is 2 link members are 0x4, active links are 0x0 Group status is blockedNe, 1 links configured, Group Info: Configured links bitmap 0x4, Active links bitmap 0x0, TX/Rx IMA_id 0x11/0x63, NE Group status is startUp, frame length 0x80, Max Diff Delay 477, 1 min links, clock mode ctc, symmetry symmetricOperation, trl 2, Group Failure status is startUpNe. Test pattern procedure is disabled SAR counter totals across all links and groups: 0 cells output, 0 cells stripped 0 cells input, 0 cells discarded, 0 AAL5 frames discarded 0 pci bus err, 0 DMA FIFO full err, 0 rsm parity err 0 rsm syn err, 0 rsm/seg q full err, 0 rsm overflow err 0 Hs q full err, 0 no free buff q err, 0 seg underflow err 0 host seg stat q full err ACC-3000
9743_05_2004_c2
116
ATM: IMA States in Group State Machine

State Description
Not Configured The IMA Group Does Not Exist Start-Up Start-Up-Ack Config-Aborted InsufficientLinks Blocked Operational
ACC-3000 9743_05_2004_c2
This End (NE) Is Waiting for Indication that the Far End Is in Startup; It Moves to the Next State after Recording IMA ID and Other IMA Parameters When Both Sides Are Enabled The FE Is Using Unacceptable Configuration Parameters (Including IMA Version) NE Accepted FE Parameters, but FE Has Insufficient Links The Group Is Blocked The Group Is Not Inhibited and Has Sufficient Links; ATM Cells Are Passed from IMA Sublayer to ATM Layer
117
ATM: Bouncing IMA Links

Decoding the Active Link Bitmap
Apr now APR now APR now APR now 13 20:45:47.196 CDT: %IMA-5-ACTIVE_LINK_CHANGE: has 5 active links, active link bitmap is 0x37. 13 20:45:47.964 CDT: %IMA-5-ACTIVE_LINK_CHANGE: has 6 active links, active link bitmap is 0x3F. 13 20:45:51.184 CDT: %IMA-5-ACTIVE_LINK_CHANGE: has 5 active links, active link bitmap is 0x37. 13 20:45:51.440 CDT: %IMA-5-ACTIVE_LINK_CHANGE: has 6 active links, active link bitmap is 0x3F. IMA Group ATM2/IMA0 IMA Group ATM2/IMA0 IMA Group ATM2/IMA0 IMA Group ATM2/IMA0
Decode for 0x37 Binary Decode T1 Port Value Port Status
0 7
0 6
1 5 Up 1 5 Up
1 4 Up 1 4 Up
0 3 Down 1 3 Up
1 2 Up 1 2 Up
1 1 Up 1 1 Up
1 0 Up 1 0 Up
118
Down Down 0 7 0 6
Decode for 0x3F Binary Decode T1 Port Value Port Status

ACC-3000 9743_05_2004_c2
Down Down
References:
T1
http://www.cisco.com/warp/public/116/t1_flchrt_main.html http://www.cisco.com/warp/public/116/t1_flchrt_alarm_1.html http://www.cisco.com/cgi-bin/Support/PSP/psp_view.pl?p=Internetworking:T1T3E1E3
SONET
http://www.cisco.com/cgibin/Support/browse/psp_view.pl?p=Technologies:Optical_General
Frame Relay Technical Tips

http://www.cisco.com/cgibin/Support/browse/psp_view.pl?p=Internetworking:Frame_Relay
Point-to-Point Protocol
http://www.cisco.com/en/US/tech/tk713/tk507/tech_protocol_family_home.html
ATM Technical Tips

http://www.cisco.com/cgi-bin/Support/browse/index.pl?i=Technologies&f=379
General WAN
http://www.cisco.com/cgi-bin/Support/browse/index.pl?i=Technologies&f=776 http://www.cisco.com/en/US/tech/tk713/tech_protocol_families.html
ACC-3000 9743_05_2004_c2
119
Recommended Reading
Cisco ATM Solutions
ISBN: 1-57870-213-5
Cisco IOS 12.0 Wide Area Networking Solutions

ISBN: 1-57870-158-9
Available Onsite at the Cisco Company Store

ACC-3000 9743_05_2004_c2
120
Recommended Reading
Cisco WAN Quick Start
ISBN: 1-57870-104-X
Cisco IOS Wide Area Networking Solutions

ISBN: 1-57870-054-X
Available Onsite at the Cisco Company Store

ACC-3000 9743_05_2004_c2
121
Complete Your Online Session Evaluation!

WHAT: Complete an online session evaluation and your name will be entered into a daily drawing Win fabulous prizes! Give us your feedback!
WHY:
WHERE: Go to the Internet stations located throughout the Convention Center HOW: Winners will be posted on the onsite Networkers Website; four winners per day
ACC-3000 9743_05_2004_c2
122
ACC-3000 9743_05_2004_c2
123

Troubleshooting Wan Protocols in Cisco Ios Software: Session Acc-3000

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Troubleshooting Wan Protocols in Cisco Ios Software: Session Acc-3000

Uploaded by

Copyright:

Available Formats

TROUBLESHOOTING WAN PROTOCOLS IN CISCO IOS SOFTWARE

2004 Cisco Systems, Inc. All rights reserved.

Skill Level Assumptions

Familiar with Cisco IOS WAN configuration of:

2004 Cisco Systems, Inc. All rights reserved.

WAN Troubleshooting Maxim

ANCIENT WAN TROUBLESHOOTING PROVERB

2004 Cisco Systems, Inc. All rights reserved.

2004 Cisco Systems, Inc. All rights reserved.

T1 AND T3 TRANSMISSION LINES

2004 Cisco Systems, Inc. All rights reserved.

Troubleshooting T1 or Digital Leased Lines

Verify CSU/DSU settings

Breakdown of T1 Controller Counters

Format may vary contingent upon module type and revision

2004 Cisco Systems, Inc. All rights reserved.

T1: Meaning of Controller Counters

T1: Meaning of Controller Counters

2004 Cisco Systems, Inc. All rights reserved.

T1: Meaning of Controller Counters

2004 Cisco Systems, Inc. All rights reserved.

T1/T3: Alarm Scenario

Blue Alarm Sent

Yellow Alarm Sent

Yellow Alarm Sent

Yellow Alarm Sent

2004 Cisco Systems, Inc. All rights reserved.

T1: Red Alarm

2004 Cisco Systems, Inc. All rights reserved.

T1/T3: Yellow Alarm

2004 Cisco Systems, Inc. All rights reserved.

T1: Declaring a Yellow Alarm

2004 Cisco Systems, Inc. All rights reserved.

T1: ESF Yellow Alarm Pattern

2004 Cisco Systems, Inc. All rights reserved.

T1/T3: AIS and Blue Alarms

2004 Cisco Systems, Inc. All rights reserved.

T1/T3: Alarm States

2004 Cisco Systems, Inc. All rights reserved.

T1: Show Controller with Alarms

2004 Cisco Systems, Inc. All rights reserved.

T1/T3: Troubleshooting Tools

2004 Cisco Systems, Inc. All rights reserved.

Using extended Ping Command to Test a T1

2004 Cisco Systems, Inc. All rights reserved.

Using extended Ping Command to Test a T1 (Cont.)

2004 Cisco Systems, Inc. All rights reserved.

Using extended Ping Command to Test a T1 (Cont.)

(Also Called Network Loopback)

Troubleshooting Tools Loopbacks

2004 Cisco Systems, Inc. All rights reserved.

Troubleshooting Tools Loopbacks (Cont.)

2004 Cisco Systems, Inc. All rights reserved.

Troubleshooting Tools Loopbacks (Cont.)

Send Blue Alarm

2004 Cisco Systems, Inc. All rights reserved.

Troubleshooting Tools Loopbacks (Cont.)

CSU/DSU Module DTE Interface

May Require Service-Module T1 Remote-Loopback Set at Remote

2004 Cisco Systems, Inc. All rights reserved.

Troubleshooting Tools Loopbacks (Cont.)

T1: Loopback Types