Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Troubleshooting Serial interface

Hi,

I have a wide area point to point connection via frame relay. The interface on my backbone router is UP/UP. My frame relay PVC is also active. The Serial interface at the router at the other end is also UP / UP. But the Sub interface is Down/ Down.

I have checked the IP addressess ; Encapsulation ; DLCI's and it seems to have been configured correctly

Anyone got any ideas what the problem could be.

Thanks in advance.

Jay

17 REPLIES
Gold

Re: Troubleshooting Serial interface

Can you post your config pls.

Thanks -

New Member

Re: Troubleshooting Serial interface

interface Serial0

description 1024Kb/s Frame Relay to xxxxxxxxx

no ip address

encapsulation frame-relay IETF

no ip mroute-cache

no fair-queue

frame-relay lmi-type ansi

!

interface Serial0.1 point-to-point

description PVC to xxxxxxxxxxx

bandwidth 1024

ip address xxxxxxxxx

no cdp enable

frame-relay interface-dlci 106

xxxxxxxxxx#sh ip int brie

Interface IP-Address OK? Method Status Protocol

FastEthernet0

Serial0 unassigned YES NVRAM up up

Serial0.1 xxxxxxxxxxxxxxx YES NVRAM down down

Other end.

!

interface Serial4/1/3

description Connection to xxxxxxxxx

no ip address

no ip directed-broadcast

encapsulation frame-relay IETF

ip route-cache distributed

frame-relay lmi-type ansi

!

interface Serial4/1/3.1 point-to-point

description xxxxxxx

bandwidth 1024

ip address xxxxxx

ip access-group xxxx in

no ip directed-broadcast

traffic-shape rate 1024000 25600 25600 1000

no cdp enable

frame-relay interface-dlci xxx

Gold

Re: Troubleshooting Serial interface

Hi -

I presume you've tried no shutdown cmd on se0.1 ?

I.e. router(config) int se0.1

> router(config-subif) no shutdown

thanks -

New Member

Re: Troubleshooting Serial interface

Yes tried that and reloaded router as well

New Member

Re: Troubleshooting Serial interface

Can you please post the output from the command show frame-relay PVC? and the output from the command show controllers serial X from both routers?

New Member

Re: Troubleshooting Serial interface

xxxxxx#sh frame-relay pvc

PVC Statistics for interface Serial0 (Frame Relay DTE)

Active Inactive Deleted Static

Local 0 0 1 0

Switched 0 0 0 0

Unused 0 0 0 0

DLCI = 106, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE = Serial0.1

input pkts 0 output pkts 1 in bytes 0

out bytes 80 dropped pkts 0 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 0 out bcast bytes 0

xxxxxxxx#sh controllers serial 0

Interface Serial0

Hardware is PowerQUICC MPC860

DTE V.11 (X.21) TX and RX clocks detected.

idb at 0x80BA5D28, driver data structure at 0x80BAD634

SCC Registers:

General [GSMR]=0x2:0x00000030, Protocol-specific [PSMR]=0x8

Events [SCCE]=0x0000, Mask [SCCM]=0x001F, Status [SCCS]=0x06

Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E

Interrupt Registers:

Config [CICR]=0x00365F80, Pending [CIPR]=0x00008000

Mask [CIMR]=0x40204000, In-srv [CISR]=0x00000000

Command register [CR]=0x5C0

Port A [PADIR]=0x1000, [PAPAR]=0xFFFF

[PAODR]=0x0000, [PADAT]=0xE6FF

Port B [PBDIR]=0x09C0F, [PBPAR]=0x0E00E

[PBODR]=0x00000, [PBDAT]=0x0847C

Port C [PCDIR]=0x000, [PCPAR]=0x000

[PCSO]=0xC20, [PCDAT]=0xFCC, [PCINT]=0x000

Receive Ring

rmd(FF002230): status 9000 length 10 address 196B604

rmd(FF002238): status 9000 length 10 address 196AF84

rmd(FF002240): status 9000 length 10 address 196A904

rmd(FF002248): status 9000 length 10 address 196A284

rmd(FF002250): status 9000 length 10 address 1970404

rmd(FF002258): status 9000 length 10 address 1970A84

rmd(FF002260): status 9000 length 10 address 196FD84

rmd(FF002268): status 9000 length 10 address 196F704

rmd(FF002270): status 9000 length 10 address 196EA04

rmd(FF002278): status 9000 length 10 address 196E384

rmd(FF002280): status 9000 length 10 address 196DD04

rmd(FF002288): status 9000 length 10 address 196D684

rmd(FF002290): status 9000 length 10 address 196D004

rmd(FF002298): status 9000 length 10 address 196C984

rmd(FF0022A0): status 9000 length 10 address 196C304

rmd(FF0022A8): status B000 length 10 address 196BC84

Transmit Ring

tmd(FF0022B0): status 5C00 length E address 197FF94

tmd(FF0022B8): status 5C00 length E address 197FF94

tmd(FF0022C0): status 5C00 length E address 197FF94

tmd(FF0022C8): status 5C00 length E address 197FF94

tmd(FF0022D0): status 5C00 length E address 197FF94

tmd(FF0022D8): status 5C00 length E address 197FF94

tmd(FF0022E0): status 5C00 length E address 197FF94

tmd(FF0022E8): status 5C00 length E address 197FF94

tmd(FF0022F0): status 5C00 length E address 197FF94

tmd(FF0022F8): status 5C00 length E address 197FF94

tmd(FF002300): status 5C00 length E address 197FF94

tmd(FF002308): status 5C00 length E address 197FF94

tmd(FF002310): status 5C00 length E address 197FF94

tmd(FF002318): status 5C00 length E address 197FF94

tmd(FF002320): status 5C00 length E address 197FF94

tmd(FF002328): status 7C00 length E address 197FF94

SCC GENERAL PARAMETER RAM (at 0xFF003C00)

Rx BD Base [RBASE]=0x2230, Fn Code [RFCR]=0x18

Tx BD Base [TBASE]=0x22B0, Fn Code [TFCR]=0x18

Max Rx Buff Len [MRBLR]=1548

Rx State [RSTATE]=0x18008440, BD Ptr [RBPTR]=0x2270

Tx State [TSTATE]=0x18000548, BD Ptr [TBPTR]=0x2328

SCC HDLC PARAMETER RAM (at 0xFF003C38)

CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8

Errors: CRC [CRCEC]=0, Aborts [ABTSC]=0, Discards [DISFC]=0

Nonmatch Addr Cntr [NMARC]=0

Retry Count [RETRC]=0

Max Frame Length [MFLR]=1608

Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=65464

User-defined Address 0000/0000/0000/0000

User-defined Address Mask 0x0000

buffer size 1524

PowerQUICC SCC specific errors:

0 input aborts on receiving flag sequence

0 throttles, 0 enables

0 overruns

0 transmitter underruns

0 transmitter CTS losts

==============================

PVC Statistics for interface Serial4/1/3 (Frame Relay DTE)

DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial4/1/3.1

input pkts 0 output pkts 210 in bytes 0

out bytes 19060 dropped pkts 0 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 0 out bcast bytes 0

pvc create time 04:22:15, last time pvc status changed 04:21:15

I could not do the show controller on the other router.

WARW1BR2#sh int s4/1/3

Serial4/1/3 is up, line protocol is up

Hardware is cyBus Serial

Description: Connection to *********

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation FRAME-RELAY IETF, crc 16, loopback not set

Keepalive set (10 sec)

LMI enq sent 70366, LMI stat recvd 70366,LMI upd recvd 0, DTE LMI up

LMI enq recvd 0, LMI stat sent 0,LMI upd sent 0

LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE

Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0

Last input 00:00:05, output 00:00:05, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0 (size/max/drops); Total output drops: 0

Queueing 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

81113 packets input, 1961924 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

70601 packets output, 1005548 bytes, 0 underruns

0 output errors, 0 collisions, 3 interface resets

0 output buffer failures, 0 output buffers swapped out

1 carrier transitions

RTS up, CTS up, DTR up, DCD up, DSR up

Gold

Re: Troubleshooting Serial interface

Q. Why is your PVC on se0.1 showing deleted ?

New Member

Re: Troubleshooting Serial interface

I think because the sub interface S0.1 is not receiving any lmi's. This is only my assumption. Thanks

Gold

Re: Troubleshooting Serial interface

Hi -

I think you've answered your own question, if you have no LMI then you have no PVC so as the other post suggested please check with service provider of on this issue.

thanks -

New Member

Re: Troubleshooting Serial interface

Is this a new circuit or an old one?

If this is a new circuit verify with the service provider that the PVC has been provisioned correctly.

New Member

Re: Troubleshooting Serial interface

It is a new circuit. The provider has verified and confirmed that the PVC is correctly provisioned. Thanks

Gold

Re: Troubleshooting Serial interface

Hi again -

Do a "sh fr lmi" and post the result please -

Thanks -

New Member

Re: Troubleshooting Serial interface

LMI Statistics for interface Serial4/1/3 (Frame Relay DTE) LMI TYPE = ANSI

Invalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0

Invalid Status Message 0 Invalid Lock Shift 0

Invalid Information ID 0 Invalid Report IE Len 0

Invalid Report Request 0 Invalid Keep IE Len 0

Num Status Enq. Sent 70548 Num Status msgs Rcvd 70548

Num Update Status Rcvd 0 Num Status Timeouts 0

=========

*******#SH FRame-relay LMI

LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = ANSI

Invalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0

Invalid Status Message 0 Invalid Lock Shift 0

Invalid Information ID 0 Invalid Report IE Len 0

Invalid Report Request 0 Invalid Keep IE Len 0

Num Status Enq. Sent 319 Num Status msgs Rcvd 319

Num Update Status Rcvd 0 Num Status Timeouts 0

New Member

Re: Troubleshooting Serial interface

Can you post the output for the command debug frame-relay lmi?

thanks

Gold

Re: Troubleshooting Serial interface

Just a thought -

Take out the sub interface se0.1 and re-create another sub-interface as se0/0.1 and do the usual no shutdown + add all the other information and se what happens.

Thanks -

New Member

Re: Troubleshooting Serial interface

Okay Folks the issue has been resolved. The Service provider messed the PVC definitions. Sorry to have troubled you.

Thanks for all your quick response.

New Member

Re: Troubleshooting Serial interface

01:16:17: Serial0(out): StEnq, myseq 202, yourseen 201, DTE up

01:16:17: datagramstart = 0x197FF94, datagramsize = 14

01:16:17: FR encap = 0x00010308

01:16:17: 00 75 95 01 01 00 03 02 CA C9

01:16:17:

01:16:17: Serial0(in): Status, myseq 202

01:16:17: RT IE 1, length 1, type 0

01:16:17: KA IE 3, length 2, yourseq 202, myseq 202

01:16:27: Serial0(out): StEnq, myseq 203, yourseen 202, DTE up

01:16:27: datagramstart = 0x197FF94, datagramsize = 14

01:16:27: FR encap = 0x00010308

01:16:27: 00 75 95 01 01 01 03 02 CB CA

01:16:27:

01:16:27: Serial0(in): Status, myseq 203

01:16:27: RT IE 1, length 1, type 1

01:16:27: KA IE 3, length 2, yourseq 203, myseq 203

01:16:37: Serial0(out): StEnq, myseq 204, yourseen 203, DTE up

01:16:37: datagramstart = 0x197FF94, datagramsize = 14

01:16:37: FR encap = 0x00010308

01:16:37: 00 75 95 01 01 01 03 02 CC CB

01:16:37:

01:16:37: Serial0(in): Status, myseq 204

01:16:37: RT IE 1, length 1, type 1

01:16:37: KA IE 3, length 2, yourseq 204, myseq 204

01:16:47: Serial0(out): StEnq, myseq 205, yourseen 204, DTE up

01:16:47: datagramstart = 0x197FF94, datagramsize = 14

01:16:47: FR encap = 0x00010308

01:16:47: 00 75 95 01 01 01 03 02 CD CC

01:16:47:

01:16:47: Serial0(in): Status, myseq 205

01:16:47: RT IE 1, length 1, type 1

01:16:47: KA IE 3, length 2, yourseq 205, myseq 205

01:16:57: Serial0(out): StEnq, myseq 206, yourseen 205, DTE up

01:16:57: datagramstart = 0x197FF94, datagramsize = 14

01:16:57: FR encap = 0x00010308

01:16:57: 00 75 95 01 01 01 03 02 CE CD

01:16:57:

01:16:57: Serial0(in): Status, myseq 206

01:16:57: RT IE 1, length 1, type 1

01:16:57: KA IE 3, length 2, yourseq 206, myseq 206

01:17:07: Serial0(out): StEnq, myseq 207, yourseen 206, DTE up

01:17:07: datagramstart = 0x197FF94, datagramsize = 14

01:17:07: FR encap = 0x00010308

01:17:07: 00 75 95 01 01 01 03 02 CF CE

01:17:07:

01:17:07: Serial0(in): Status, myseq 207

01:17:07: RT IE 1, length 1, type 1

01:17:07: KA IE 3, length 2, yourseq 207, myseq 207

01:17:17: Serial0(out): StEnq, myseq 208, yourseen 207, DTE up

01:17:17: datagramstart = 0x197FF94, datagramsize = 14

01:17:17: FR encap = 0x00010308

01:17:17: 00 75 95 01 01 00 03 02 D0 CF

01:17:17:

01:17:17: Serial0(in): Status, myseq 208

01:17:17: RT IE 1, length 1, type 0

01:17:17: KA IE 3, length 2, yourseq 208, myseq 208

01:17:27: Serial0(out): StEnq, myseq 209, yourseen 208, DTE up

01:17:27: datagramstart = 0x197FF94, datagramsize = 14

01:17:27: FR encap = 0x00010308

01:17:27: 00 75 95 01 01 01 03 02 D1 D0

01:17:27:

01:17:27: Serial0(in): Status, myseq 209

01:17:27: RT IE 1, length 1, type 1

01:17:27: KA IE 3, length 2, yourseq 209, myseq 209undebug all

01:17:37: Serial0(out): StEnq, myseq 210, yourseen 209, DTE up

01:17:37: datagramstart = 0x197FF94, datagramsize = 14

01:17:37: FR encap = 0x00010308

01:17:37: 00 75 95 01 01 01 03 02 D2 D1

01:17:37:

01:17:37: Serial0(in): Status, myseq 210

01:17:37: RT IE 1, length 1, type 1

01:17:37: KA IE 3, length 2, yourseq 210, myseq 210

#

288
Views
0
Helpful
17
Replies
CreatePlease login to create content