Cisco Newbie - Ping problem to T1 WIC

[tester125]

Hi, Am new to the Cisco World. I can't ping to the T1 WIC ip address from the router (Cisco2621XM). Does anyone know what the problem might be. Any help will be greatly appreciated.

VIRCIS20.2#show interface fastethernet0/0
FastEthernet0/0 is up, line protocol is up
Hardware is AmdFE, address is 000c.31eb.e5c0 (bia 000c.31eb.e5c0)
Internet address is 10.5.20.2/16
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 14:51:32
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 3000 bits/sec, 5 packets/sec
5 minute output rate 1000 bits/sec, 3 packets/sec
100130 packets input, 11498890 bytes
Received 88510 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog
0 input packets with dribble condition detected
14620 packets output, 1574266 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
66 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
VIRCIS20.2#
VIRCIS20.2#show interface serial0/0
Serial0/0 is up, line protocol is up
Hardware is PQUICC with Fractional T1 CSU/DSU
Internet address is 10.1.11.1/24
MTU 1524 bytes, BW 1536 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set
Keepalive not set
Last input 00:00:02, output 00:00:56, output hang never
Last clearing of "show interface" counters 14:52:34
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
12136 packets input, 497484 bytes, 0 no buffer
Received 12136 broadcasts, 0 runts, 2 giants, 0 throttles
940 input errors, 234 CRC, 481 frame, 0 overrun, 0 ignored, 223 abort
1118 packets output, 320577 bytes, 0 underruns
0 output errors, 0 collisions, 5 interface resets
0 output buffer failures, 0 output buffers swapped out
4 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up

 

[Andyleates]

can you post your running configuration?

Andy Leates MCSE CCNA MCP+I

 

[tester125]

Thanks for the respose, here it is:
Note: I could ping to the remote router: 10.1.11.2, but I still can't ping to my router(10.1.11.1) from the router itself. Also I can ping to the router 10.1.11.1 from my workstation.
Thanks


Building configuration...

Current configuration : 937 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname VIRCIS20.2
!
boot system flash c2600-i-mz.122-8.T10.bin
enable secret 5 $1$.F0l$ViEPBxrkT6tzhsKdLtLh4.
enable password
!
ip subnet-zero
!
!
!
!
!
!
interface FastEthernet0/0
ip address 10.5.20.2 255.255.0.0
ip ospf authentication
no ip mroute-cache
speed auto
half-duplex
!
interface Serial0/0
mtu 1524
ip address 10.1.11.1 255.255.255.0
encapsulation ppp
no ip mroute-cache
delay 10
autodetect encapsulation ppp
roles
role default
no fair-queue
service-module t1 clock source internal
!
interface FastEthernet0/1
no ip address
no ip mroute-cache
shutdown
duplex auto
speed auto
!
ip classless
ip route profile
ip route 192.168.0.0 255.255.255.192 10.1.11.2
ip http server
ip ospf name-lookup
ip pim bidir-enable
!
!
!
line con 0
line aux 0
line vty 0 4
password login
!
!
end

 

[MztrNyceGuy]

Have you tried specifying the interface in which you ping from?

Ping <-enter
<-
10.1.11.1 (Ip to ping)
<-
<-
<-
y
10.5.20.2 (interface to ping from)
<- all defaults unless you want to change

results.


Another question is; are you using OSPF for this network? Are there multiple networks on either side of this or is it just a test to see if OSPF works? the OSPF part seems to be lacking in some areas (e.g. Router OSPF NAME, and areas) that could be part of the problem you are running into, since its trying to figure out the route to itself however it doesn’t know it since its not part of a real OSPF area.

http://www.cisco.com/warp/public/104/25.shtml

for some info.


How come you are using autodetect encapsulation statement I’m wondering why this is here? Why not just state encap PPP? I’ve seen the autodetect encapsulation hdlc etc for BRI or ISDN connections but not PPP Wan T1 connections.

In my opinion it looks like you were given a config from somewhere else and told to put it here. If this is a regular wan T1 why isn’t the default MTU used? Is it a 3com or Nortel router on the other side? Basically the keep it simple methodology works best and I think if this is just a test site or even one site connecting to another site there could be an easier way of doing it, which may also be the answer to your question on why this T1 WIC interface doesn’t talk to itself but passes traffic just fine.


IMHO
Kevin

 

[jimmyzz]

tester125,
As I stated in your earlier post, the router may not be able to ping its own serial interface if you have configured the IP on the main-interface Serial0/0

The work-around is to configure the IP/T1 config using sub-interfaces. The sub-interface in your case would be interface Serial0/0.1

The router is able to successfully send and recieve the ICMP packet under the sub-interface config. Another work-around is if you try doing a extended ping on the router and specifying the source interface as the IP of your ethernet (haven't tested this one, but should work in theory).

JimmyZ

 

[MztrNyceGuy]

Jimmyzz,

Is there something you know that I dont? I have not had trouble with point to point T1's with a single main interface IP address pinging each other. You said soemthing about an earlier post? hmm.. Im probabbly not in the loop.

Kevin

 

[jimmyzz]

MztrNyceGuy
Pinging each other is not a problem. As tester125 stated he can do this from the remote router and his PC. Pinging the router's own main-serial interface from the router itself is the problem.

I was referring to a seperate thread that Tester submitted just the other day - seems to be submitting the problem twice, hence twice the solution.

Your extended ping work-around seems to have got post about 10secs before mine ;-). Looks like we're the same track and in the same time-zone

JimmyZ

 

[MztrNyceGuy]

Jimmyzz,

have you had problems on Router A pinging Router A's Serial0:0 ip address? in a ppp network? If so I would have to say thats a first for me since I have it set up and works fine for me... however it could be a different version of IOS that is out that I have used.... dunno

Im still wondering what's up with his config, it looks more convoluted then necessary? but who knows.

o yeah is there a setting I need to see the time for posts? I only see the date...

Kevin