Serial0/0 is up, line protocol is up
Hardware is PowerQUICC Serial
Description: VPNtranet
Internet address is 64.89.111.130/30
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC,
loopback not set loopback is NOT set.. good things
Keepalive set (10 sec)
Last input 00:00:01, output 00:00:02, output hang never
Last clearing of "show interface" counters 00:02:45
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 1000 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
55 packets input, 4734 bytes, 0 no buffer
Received 20 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
26 packets output, 2466 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
You have packets coming across.. more then likly it's the keep alive.. thats good, no CRC errors which tells the framing is probably good.
0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
tells us the circuit is up correctly
I would dump the access lists on the interface for now.. keept things simple for troubleshooting. Do an extended ping out of the serial interface and see if you can ping the other end. It may or may not work depending on security at the other end. Traceroute is another good test.. pick a point beyond the next hop.
Extended PING is had by typing in PING and press return.
This takes you to a query session. When you get to the command asking if you want extended commands, say yes. It was ask among other items, what interface IP you want the ping to leave from .. give it the S0/0 interface. If you can ping or traceroute, the problem is with either the access-list or the NAT config.. I need to review the NAT on paper before I say anything about that. Same for the access lists.. it's hard on these little columms to read it at times.
I will ask about the default gatway.. why? Cisco's own docs say not to use it unless routing is disabled (
"The ip default-gateway command differs from the other two commands, in that it should only be used when ip routing is disabled on the Cisco router.")
use IP ROUTE 0.0.0.0 0.0.0.0 (nexthop or interface)
Additional notes from Cisco "Note: IGRP doesn't understand a route to 0.0.0.0, therefore it can't propagate default routes created using the ip route 0.0.0.0 0.0.0.0 command. Use the ip default-network command to have IGRP propagate a default route. "
Complete article for your pleasure
Mike S
PS- dump the public and private SNMP community strings.. big security hole.
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
