Swapping out 3660 for a 3620

[redwolf52]

I have created the same config on the new 3620 but when I plug in the T1 link the interface dosent come up. Does my ISP have to clear some arp cache or some other cache for me to switch routers? Basic config, static route to my isp and same encapsulation as on the old router. When I plug the old router back in and power it up the link comes right up.

Thanks in advance

 

[nyy1023]

There could be a couple of problems with this, and non of which are the ISP issue.

The first one could be a simple activation of the interface. You can try a shutdown of the interface and then a no shutdown and see if that works.

The next thing to do is make sure you have IP Routing enabled, it should be default depending on your IOS, but you may want to check.

Also check ip subnet zero and ip classless are enabled in the global config. Again these are items that should be enabled by default, but you may want to check.

If this does not help, put a PC on the ethernet side of the router and run a traceroute to see where the connection dies.

Remember, or better yet a word of caution, if you are running BGP it will take some time to establish the connection. The first thing to make sure of is the serial IP at the ISP end, make sure you can ping it. After that you will need to just run through the config line by line to make sure everything is turned on, and set up the way you want.

If this still does not help, let me know.
I may need to get a little deeper in what you have to help.
Also, don't forget to leave my consult fee at paypal?!?!?!

he he he lol!!!

 

[redwolf52]

Here is the console output from a power on.

00:00:06: SERVICE_MODULE(Serial1/0): self test finished: Passed
00:00:09: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
00:00:10: %LINK-3-UPDOWN: Interface Ethernet1/0, changed state to up
00:00:10: %SYS-5-CONFIG_I: Configured from memory by console
00:00:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed sta
te to down
00:00:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/0, changed s
tate to down
00:00:12: %LINK-5-CHANGED: Interface Serial1/0, changed state to administrativel
y down
00:00:13: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3620-I-M), Version 12.2(5d), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Sat 02-Feb-02 01:51 by kellythw
00:00:13: %SNMP-5-COLDSTART: SNMP agent on host Dallas-Router is undergoing a co
ld start

I dont have access to the router right now. Had to ship it to our other office. I am trying to get the on site admin to plug the router into a switch so i can telnet into it.

Not sure if the output helps at all

thanks in advance

 

[nyy1023]

yeah, your interfaces are down.

When you get access to it do this:
When you log on to the router go into enable mode and enter in password.
then do a show ip int brief
This will show the status of all the interfaces on the router.
If they are showing you interface down line protocol down
you will need to bring these interfaces up in order to pass traffic.
do a no shut on all the interfaces and make sure they are plugged into the network, WAN and LAN to make sure the interface stays up unless you turn keepalive off.

let me know if this works, or if you need more help.

 

[redwolf52]

well bringing up the interface was correct as was removing the no ip routing command, but the tech still cant ping past the wan interface. Here is a copy of the running config. Let me know if you see anything


Building configuration...

Current configuration : 2164 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname Dallas-Router
!
enable secret 5 $1$YkRQ$b4dQQwOiDzHjW/vqrJqSa0
!
username techops privilege 15 password 7 072701414359170104
ip subnet-zero
!
!
!
!
!
!
interface Ethernet1/0
ip address 216.61.193.65 255.255.255.224
no ip mroute-cache
full-duplex
!
interface Serial1/0
no ip address
ip access-group 100 in
encapsulation frame-relay IETF
no ip mroute-cache
!
interface Serial1/0.1 point-to-point
description SBC Interface
bandwidth 1544
ip address 65.64.223.222 255.255.255.252
ip access-group 100 in
no ip mroute-cache
frame-relay interface-dlci 500
!
ip classless
ip route 0.0.0.0 0.0.0.0 65.64.223.221
no ip http server
no ip pim bidir-enable
!
!
map-class frame-relay ietf
no frame-relay adaptive-shaping
access-list 100 permit 22 0.0.0.10 255.255.255.0 any
access-list 100 deny tcp any any range 137 139 log
access-list 100 deny udp any any eq 5631 log
access-list 100 deny tcp host 127.0.0.1 any log
access-list 100 deny ip host 127.0.0.1 any log
access-list 100 deny tcp any any eq 5631 log
access-list 100 deny tcp any any eq 87 log
access-list 100 deny tcp any any eq sunrpc
access-list 100 deny udp any any eq sunrpc
access-list 100 deny udp any any eq 2049
access-list 100 deny tcp any any range exec cmd log
access-list 100 deny tcp any any eq lpd log
access-list 100 deny tcp any any eq uucp log
access-list 100 deny tcp any any eq 6000 log
access-list 100 deny udp any any eq 6000 log
access-list 100 deny ip 10.0.0.0 0.255.255.255 any
access-list 100 deny udp 10.0.0.0 0.255.255.255 any
access-list 100 deny tcp 10.0.0.0 0.255.255.255 any
access-list 100 deny icmp 10.0.0.0 0.255.255.255 any
access-list 100 deny ip 172.16.0.0 0.15.255.255 any
access-list 100 deny ip 192.168.0.0 0.0.255.255 any
access-list 100 deny tcp any any eq 135
access-list 100 deny udp any any eq 135
access-list 100 permit ip any any
!
line con 0
password 7 153A2B01097A25203B
login
line aux 0
password 7 09646E041455191618
login
line vty 0 4
password 7 09646E041455191618
login local
!
end

Dallas-Router#

 

[nyy1023]

I have a suggestion, and a question
First remove the access-group from your serial interface and the sub-interface.

You can add it once the connection is up and running, but for ease of troubleshooting take it out.

Next, try to ping the next hop address 65.64.223.221

Also, and FYI you do not need to specify the next-hop address in the static route.

ip route 0.0.0.0 0.0.0.0 serial0/0.1 will work just fine too.

Next do a sho ip route to see if you are directly connected.

Try these and see if they show where a problem may be at, also do a traceroute from a host to see where it fails.

Try all of these, if it works we will then need to look at the ACL.

 

[redwolf52]

This is hard not having the ability to lay hands on the router but the tech is copying down the configs and sending them to me.

He ran sh ip route and got



Gateway of last resort is not set

I am going to have him change the static route to the serial interface and try again.

thanks