Unable to ping or telnet to remote router, line up/up

[Scott Fella]

I can't ping or telnet to the remote router. The interface on the

local router is s1/0:0.102 and shows the line up. The router has been

power cycled many times and still the issue persists. I do not have

access to the remote router. Is there anything I can do, or is there

a problem with the router on the remote side.

#sh int s1/0:0.102

Serial1/0:0.102 is up, line protocol is up

Hardware is DSX1

Description: FR to Middletown

Internet address is 10.50.0.1/16

MTU 1500 bytes, BW 256 Kbit, DLY 20000 usec,

reliability 255/255, txload 66/255, rxload 20/255

Encapsulation FRAME-RELAY

#sh cdp nei

Capability Codes: R - Router, T - Trans Bridge, B - Source Route

Bridge

S - Switch, H - Host, I - IGMP, r - Repeater

Device ID Local Intrfce Holdtme Capability Platform

Port ID

capw Ser 1/0:0.104 127 R 1000

Ser 0.100

PRIMM_NEVADA Ser 1/0:0.106 141 R Cisco

C805Ser 0.1

2900XL Fas 0/0 161 T S

WS-C2924M-Fas 0/18

Graycore1751-MexiSer 1/0:0.119 156 R 1751

Ser 0/0.100

Indianapolis Ser 1/0:0.101 148 R 1000

Ser 0.100

Middletown Ser 1/0:0.102 175 R 1000

Ser 0.1

Avenue_O Ser 1/0:1 168 R Cisco

C805Ser 0

Lafarge_Chicago Ser 1/0:5 179 R Cisco

C805Ser 0

Hoffman_Estates Ser 1/0:9 161 R Cisco

C805Ser 0

graycor_2620#ping 10.50.0.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.50.0.2, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

#sh frame pvc

DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =

Serial1/0:0.102

input pkts 11327 output pkts 28466 in bytes 1465085

out bytes 6877676 dropped pkts 34 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 19641 out bcast bytes 6083819

pvc create time 2d11h, last time pvc status changed 05:34:58

#config t

Enter configuration commands, one per line. End with CNTL/Z.

graycor_2620(config)#int s1/0:0.102

graycor_2620(config-subif)#fram

graycor_2620(config-subif)#frame-relay int

graycor_2620(config-subif)#frame-relay interface-dlci ?

<16-1007> Define a locally terminated DLCI

(config-subif)#frame-relay interface-dlci 102

%PVC is already defined

graycor_2620(config-fr-dlci)#end

graycor_2620#debug frame-relay lmi

Frame Relay LMI debugging is on

Displaying all Frame Relay LMI data

#config t

Enter configuration commands, one per line. End with CNTL/Z.

(config)#int s1/0:0.102

(config-subif)#shut

(config-subif)#no shut

(config-subif)#end

#sh log

Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)

Console logging: disabled

Monitor logging: level debugging, 0 messages logged

Buffer logging: level debugging, 156 messages logged

Trap logging: level informational, 75 message lines logged

Log Buffer (4096 bytes):

ol on Interface FastEthernet0/0, changed state to down

*Mar 1 00:11:56.447: %LINEPROTO-5-UPDOWN: Line protocol on Interface

FastEthernet0/0, changed state to up

*Mar 1 00:28:15.547: %LINEPROTO-5-UPDOWN: Line protocol on Interface

FastEthernet0/0, changed state to down

*Mar 1 00:28:25.547: %LINEPROTO-5-UPDOWN: Line protocol on Interface

FastEthernet0/0, changed state to up

*Mar 1 00:32:48.935: %SYS-5-CONFIG_I: Configured from console by

console

*Mar 1 00:33:25.547: %LINEPROTO-5-UPDOWN: Line protocol on Interface

FastEthernet0/0, changed state to down

*Mar 1 00:33:59.991: %LINEPROTO-5-UPDOWN: Line protocol on Interface

FastEthernet0/0, changed state to up

*Mar 1 00:34:59.323: %SYS-5-CONFIG_I: Configured from console by

console

*Mar 3 01:12:56.699: %LINEPROTO-5-UPDOWN: Line protocol on Interface

Serial1/0:1, changed state to down

*Mar 3 01:13:17.895: %LINEPROTO-5-UPDOWN: Line protocol on Interface

Serial1/0:1, changed state to up

*Mar 3 05:06:53.394: %SYS-5-CONFIG_I: Configured from console by vty0

(10.0.4.17)

*Mar 3 10:13:23.765: %SYS-5-CONFIG_I: Configured from console by vty0

(10.0.0.22)

*Mar 3 10:14:22.661: %SYS-5-CONFIG_I: Configured from console by vty0

(10.0.0.22)

*Mar 3 10:14:51.357: %SYS-5-CONFIG_I: Configured from console by vty0

(10.0.0.22)

*Mar 3 11:25:26.509: %SYS-5-CONFIG_I: Configured from console by vty0

(10.0.0.22)

*Mar 3 11:25:32.589: Serial1/0:0(out): StEnq, myseq 189, yourseen

252, DTE up

*Mar 3 11:25:32.589: datagramstart = 0x1355598, datagramsize = 14

*Mar 3 11:25:32.589: FR encap = 0x00010308

*Mar 3 11:25:32.589: 00 75 95 01 01 01 03 02 BD FC

*Mar 3 11:25:32.589:

*Mar 3 11:25:32.601: Serial1/0:0(in): Status, myseq 189

*Mar 3 11:25:32.601: RT IE 1, length 1, type 1

*Mar 3 11:25:32.601: KA IE 3, length 2, yourseq 253, myseq 189

*Mar 3 11:25:42.589: Serial1/0:0(out): StEnq, myseq 190, yourseen

253, DTE up

*Mar 3 11:25:42.589: datagramstart = 0x13547D8, datagramsize = 14

*Mar 3 11:25:42.589: FR encap = 0x00010308

*Mar 3 11:25:42.589: 00 75 95 01 01 01 03 02 BE FD

*Mar 3 11:25:42.589:

*Mar 3 11:25:42.601: Serial1/0:0(in): Status, myseq 190

*Mar 3 11:25:42.601: RT IE 1, length 1, type 1

*Mar 3 11:25:42.601: KA IE 3, length 2, yourseq 254, myseq 190

*Mar 3 11:25:52.589: Serial1/0:0(out): StEnq, myseq 191, yourseen

254, DTE up

*Mar 3 11:25:52.589: datagramstart = 0x13556D8, datagramsize = 14

*Mar 3 11:25:52.589: FR encap = 0x00010308

*Mar 3 11:25:52.589: 00 75 95 01 01 00 03 02 BF FE

*Mar 3 11:25:52.589:

*Mar 3 11:25:52.601: Serial1/0:0(in): Status, myseq 191

*Mar 3 11:25:52.601: RT IE 1, length 1, type 0

*Mar 3 11:25:52.601: KA IE 3, length 2, yourseq 255, myseq 191

*Mar 3 11:25:52.601: PVC IE 0x7 , length 0x3 , dlci 101, status 0x2

*Mar 3 11:25:52.601: PVC IE 0x7 , length 0x3 , dlci 102, status 0x2

*Mar 3 11:25:52.601: PVC IE 0x7 , length 0x3 , dlci 105, status 0x2

*Mar 3 11:25:52.601: PVC IE 0x7 , length 0x3 , dlci 108, status 0x2

*Mar 3 11:25:52.605: PVC IE 0x7 , length 0x3 , dlci 113, status 0x2

*Mar 3 11:25:52.605: PVC IE 0x7 , length 0x3 , dlci 114, status 0x2

*Mar 3 11:25:52.605: PVC IE 0x7 , length 0x3 , dlci 115, status 0x2

*Mar 3 11:25:52.605: PVC IE 0x7 , length 0x3 , dlci 116, status 0x2

*Mar 3 11:25:52.605: PVC IE 0x7 , length 0x3 , dlci 117, status 0x2

*Mar 3 11:25:52.605: PVC IE 0x7 , length 0x3 , dlci 118, status 0x2

*Mar 3 11:25:52.605: PVC IE 0x7 , length 0x3 , dlci 119, status 0x2

*Mar 3 11:25:52.605: PVC IE 0x7 , length 0x3 , dlci 120, status 0x0

*Mar 3 11:25:52.605: PVC IE 0x7 , length 0x3 , dlci 121, status 0x2

*Mar 3 11:26:02.589: Serial1/0:0(out): StEnq, myseq 192, yourseen

255, DTE up

*Mar 3 11:26:02.589: datagramstart = 0x1200E98, datagramsize = 14

*Mar 3 11:26:02.589: FR encap = 0x00010308

*Mar 3 11:26:02.589: 00 75 95 01 01 01 03 02 C0 FF

*Mar 3 11:26:02.589:

*Mar 3 11:26:02.601: Serial1/0:0(in): Status, myseq 192

*Mar 3 11:26:02.601: RT IE 1, length 1, type 1

*Mar 3 11:26:02.601: KA IE 3, length 2, yourseq 1 , myseq 192

*Mar 3 11:26:08.193: %SYS-5-CONFIG_I: Configured from console by vty0

(10.0.0.22)

graycor_2620#no debug frame-relay lmi

Frame Relay LMI debugging is off

Displaying all Frame Relay LMI data

Every thing looks okay... I got a status of 0x2 on dlci 102

[oj88]

I presume that user traffic is coming through without any problems. If so, I can think of two reasons why ping and telnet doesn't work:

1. There might be an ACL somewhere, blocking ICMP and telnet.

2. If you have configured traffic-shaping, fragmentation might've been incorrectly set. These could cause the symptoms you described.

These problems may reside on either the local or remote router.

Have you tried ping/telnet using other interfaces on the remote router?

Please post the results of the following show commands on the local router if you can:

sh fram map

sh ip int s1/0:0.102

[Scott Fella]

I am able to ping and telnet to other remote routers from the local router. I noticed that I was not able to ping the actual interface IP. I can ping that interface from another router though. The remote router only has one WAN port and an ethernet port. I have no way to get to that router besides a user out there.

internet#ping 10.50.0.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.50.0.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

#ping 10.50.0.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.50.0.1, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

#sh fram map

Serial1/0:0.106 (up): point-to-point dlci, dlci 113(0x71,0x1C10), broadcast

status defined, active

Serial1/0:0.107 (up): point-to-point dlci, dlci 116(0x74,0x1C40), broadcast

status defined, active

Serial1/0:0.109 (down): point-to-point dlci, dlci 120(0x78,0x1C80), broadcast

status defined, inactive

Serial1/0:0.108 (up): point-to-point dlci, dlci 108(0x6C,0x18C0), broadcast

status defined, active

Serial1/0:0.110 (up): point-to-point dlci, dlci 118(0x76,0x1C60), broadcast

status defined, active

Serial1/0:0.104 (up): point-to-point dlci, dlci 117(0x75,0x1C50), broadcast

status defined, active

Serial1/0:0.111 (up): point-to-point dlci, dlci 115(0x73,0x1C30), broadcast

status defined, active

Serial1/0:0.114 (up): point-to-point dlci, dlci 114(0x72,0x1C20), broadcast

status defined, active

Serial1/0:0.119 (up): point-to-point dlci, dlci 119(0x77,0x1C70), broadcast

status defined, active

Serial1/0:0.105 (up): point-to-point dlci, dlci 105(0x69,0x1890), broadcast

status defined, active

Serial1/0:0.160 (up): point-to-point dlci, dlci 121(0x79,0x1C90), broadcast

status defined, active

Serial1/0:0.101 (up): point-to-point dlci, dlci 101(0x65,0x1850), broadcast

status defined, active

Serial1/0:0.102 (up): point-to-point dlci, dlci 102(0x66,0x1860), broadcast

status defined, active

Serial1/0:0.103 (down): point-to-point dlci, dlci 103(0x67,0x1870), broadcast

status deleted

#sh ip int s1/0:0.102

Serial1/0:0.102 is up, line protocol is up

Internet address is 10.50.0.1/16

Broadcast address is 255.255.255.255

Address determined by non-volatile memory

MTU is 1500 bytes

Helper address is not set

Directed broadcast forwarding is disabled

Multicast reserved groups joined: 224.0.0.9

Outgoing access list is not set

Inbound access list is not set

Proxy ARP is enabled

Security level is default

Split horizon is enabled

ICMP redirects are always sent

ICMP unreachables are always sent

ICMP mask replies are never sent

IP fast switching is enabled

IP fast switching on the same interface is enabled

IP Flow switching is disabled

IP Fast switching turbo vector

IP multicast fast switching is disabled

IP multicast distributed fast switching is disabled

Router Discovery is disabled

IP output packet accounting is disabled

IP access violation accounting is disabled

TCP/IP header compression is disabled

RTP/IP header compression is disabled

Probe proxy name replies are disabled

Policy routing is disabled

Network address translation is disabled

WCCP Redirect outbound is disabled

WCCP Redirect exclude is disabled

BGP Policy Mapping is disabled

[rjackson]

are you really using a 16 bit mask on a point to point connection or could that be the problem? What is the address/mask on the other end? When you talk about pinging the actual interface IP what does that mean, serial or ethernet? What other router can ping it, where is it in the topology?

[Scott Fella]

This network was configured using a 16-bit mask. The other end is configured as 10.50.0.2/16. When I mean I can't ping, I mean from within the router, I can't ping the serial 1/0:0.102 interface (10.50.0.1). I can not ping the serial interface from the other router anymore. I was able to yesterday. Maybe I was pinging the wrong IP.

Users on the other end can not access the network.

[deilert]

I do see you have an entry in CDP for this device . When you do a sh ip route to the remote end what does it show ?

try doing an extended ping using the record option and see if your pings are successful.

[rjackson]

Your cdp display shows that the other end is middletown I assume thats correct. If so if shows that the pvc is up and you have a problem in the IP configuration. If not then the carrier has screwed up your frame relay mapping. Since you can see the config on this end it sounds like the other end is the problem. Although I'd think the ping to yourself would work since the physical circuit is up.

[Scott Fella]

The line is up now, I just have to find out what the local telco did. What happened, is I deleted the sub-interface and recreated a new sub-interface. When I brought up the interface, the line showed down/down. I thought it was wierd so I went over the config and the changes I did. So when the line stayed down, I decided to delete the new sub-interface and recreate the old. The line still stayed down. I told my client to have the telco provder look at the pvc. The line is up now and I'm just waiting to find out what the issue was. By the way, I can ping the local interface now.

Thanks for all the input.