interface serial down line protocol down

Failed router was a Cisco 3640, the replacement is a Cisco 1800 series

Also, AL light on CSU/DSU is amber and CD light is green

Call up the ISP, and have them clear their arp cache of the old router

Will this happen over time without my calling?  The reason I ask is I have stepped into the position that has been vacant for months.  There seem to be two circuits from AT&T.  I have numerous bills but not one listing this circuit.  I currently have the phone stuck in my ear regarding the other and they can hardly identify us, although we are paying $1500/mo.  So don't even know where to start to get a contact for the other circuit.

I haven't come across an ISP who'll take the initiative unless it's to squeeze more out of you. Good luck in your new position.

USE EE regularly for all your needs. Most of us do :)

>Call up the ISP, and have them clear their arp cache of the old router

There is no arp cache in frame-relay.

I would double check the previous router config. Since it "failed", I assume you're using a backup of the config. Is it possible the config of the original router was changed since the backup of the config was made?

Things to check.

timeslots (is it a full T1?)
linecoding (usually B8ZS)
framing (usually ESF)

Do understand that Frame Relay, i.e. WAN protocol, uses (inARP) inverse-arp, which has the same protocol structure and purpose as, ARPA(Ethernet) ARP, but is used to map the L2, Frame Relay DLCI, to an L3 IP address.

The config is absolutely identical.  I have access to the old router and was able to verify.  The old router suffered a power surge about a month ago, it was plugged into a wall outlet.  At that time I reconfigured from a file I found, however, it seemed the ethernet interface kept dropping.  I switched the ethernet interface to the second one, and all worked well for the last month.  I started getting drops in the new ethernet interface, so I swapped out the entire router today.  All is working well, most traffic is sent back out to a PIX firewall, or out to metro E routers in remote offices, except for those dlcis, which then go out this circuit.

I believe it is a full t-1.

I was able to get someone at AT&T to suggest they were passing the issue on to the appropriate techs to clear the arp cache.  Holding my breath is not an option.  But I will keep you updated.

In the 3640 it says WIC 1DSU T1  and in the 1800 WIC 1DSU T1 V2

Would I get any indicator lights if the card wasn't set properly in the 1800?

When you issue a "show version", does the card show up at the bottom of the output?

I just noticed you stated earlier that the AL LED is amber. This indicates a provider issue.

http://www.cisco.com/en/US/products/hw/routers/ps214/products_tech_note09186a00801f5d89.shtml#led

Contact the T1 provider and let them know what's going on. It's possible that when you swapped out routers, they disabled the circuit.

yes, 2 fastethernet
1 serial
WIC 1DSU t1

If I unplug the cable the light stays on amber

>If I unplug the cable the light stays on amber

Right. That's because circuit is down. Contact the T1 provider.

OK, here is the latest.  At the end of the day I made a second call to AT&T with the info regarding the amber light.  They said they hadn't addressed it, but would do so shortly.  I walked down the hall to the router, unplugged the cat5 from the dsu/csu for the tenth time on both ends.  Plugged it back in, still same lights.  I was there for about 5 more minutes and noticed amber had disappeared.  Tested from a client and everything was fine, wen home.  This morning, back to amber and a down down state.  I had a call from AT&T on the messages that said they had tested and the problem, if there was one, was on customer equipment.  Go figure.

Can I swap out the card without downing the router?

OIR (Online Insertion and Removal) is not supported on the 1800.

The alarm light means you're not connected. When AT&T "did something" it started working.

Call 'em again.

OK, just got off the phone with them.  They said they tested clean to the Dmark, could connect to the CSU but with errors, as I was on the phone with them.  How do I add the line coding to the config   just get into config of the interface, and use the command linecoding B8ZS ??

I tried swapping the cat5 out ...no change.   I could down the router tomorrow morning and swap the card.  Can't believe it would be bad out of the box.

OK, I added the linecode and framing by using the service module t1 commands.  It seemed to accept them but did not show on the running config under the interface configs.

They're default so they won't necessarily show up in the config.

It should show up with a "show controller t1..." command.

OK, I have swapped out the DSU/CSU, and the entire router with an identical router, with no success.  Below is the enitre config.  I had taken a router right out of the box, and added the config from the previous router, so some of the upper parts may have been pre-existing on the router.  Anyone think there is anything blocking the interface?  Funny thing is, it worked fine for a bit two days ago.

Current configuration : 3965 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname yourname
!
boot-start-marker
boot-end-marker
!
logging buffered 51200 warnings
!
no aaa new-model
!
resource policy
!
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
ip subnet-zero
ip cef
!
!
no ip dhcp use vrf connected
!
!
ip domain name yourdomain.com
!
username cisco privilege 15 secret 5 $1$yO.d$rHpQk9k.vkuiG08YOa5D/.
!
!
!
interface FastEthernet0/0
 description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-FE 0$
 ip address 192.168.35.1 255.255.255.0
 no ip redirects
 ip nat inside
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0/0
 description Frame Relay to Bellsouth ckt ID 70QGDA500669
 no ip address
 encapsulation frame-relay IETF
 no fair-queue
 service-module t1 timeslots 1-24
 frame-relay lmi-type cisco
!
interface Serial0/0/0.102 point-to-point
 description PVC to Plantation PKRouter
 ip address 192.168.196.1 255.255.255.0
 ip nat inside
 frame-relay interface-dlci 102
!
interface Serial0/0/0.103 point-to-point
 description PVC to  PDRouter
 ip address 192.168.198.1 255.255.255.0
 ip nat inside
 frame-relay interface-dlci 103
!
interface Serial0/0/0.104 point-to-point
 description PVC to Marathon MRRouter
 ip address 192.168.195.1 255.255.255.0
 ip nat inside
 frame-relay interface-dlci 104
!
interface Serial0/0/0.117 point-to-point
 description PVC to MCSO
 ip address 192.168.192.1 255.255.255.248
 ip nat inside
 frame-relay interface-dlci 117
!
interface Serial0/0/0.201 point-to-point
 description PVC to CFRouter
 ip address 160.131.26.138 255.255.255.252
 ip nat outside
 frame-relay interface-dlci 201
!
router rip
 version 2
 network 160.131.0.0
 network 192.168.192.0
 network 192.168.195.0
 network 192.168.196.0
 network 192.168.198.0
 no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.35.253
ip route 10.0.0.0 255.0.0.0 192.168.192.2
ip route 162.143.0.0 255.255.0.0 192.168.35.2
ip route 192.168.33.0 255.255.255.0 192.168.192.2
ip route 192.168.37.0 255.255.255.0 192.168.198.2
ip route 192.168.45.0 255.255.255.0 192.168.35.5
ip route 192.168.65.0 255.255.255.0 192.168.35.5
ip route 192.168.99.0 255.255.255.0 192.168.192.2
!
no ip http server
ip http access-class 23
ip http authentication local
ip http timeout-policy idle 60 life 86400 requests 10000
!
access-list 10 permit 192.168.0.0 0.0.255.255
access-list 23 permit 10.10.10.0 0.0.0.7
snmp-server engineID local 00000009020000B0C289C5B1
snmp-server community public RO
snmp-server community public$ RO
snmp-server community private# RW
snmp-server location Key West
snmp-server enable traps tty
!
control-plane
!
banner login ^C
-----------------------------------------------------------------------
Cisco Router and Security Device Manager (SDM) is installed on this device.
This feature requires the one-time use of the username "cisco"
with the password "cisco". The default username and password have a privilege le
vel of 15.

Please change these publicly known initial credentials using SDM or the IOS CLI.

Here are the Cisco IOS commands.

username <myuser>  privilege 15 secret 0 <mypassword>
no username cisco

Replace <myuser> and <mypassword> with the username and password you want to use
.

For more information about SDM please follow the instructions in the QUICK START

GUIDE for your router or go to http://www.cisco.com/go/sdm
-----------------------------------------------------------------------
^C
banner motd ^CCC
       ,,,,,
      /'^C
!
line con 0
 exec-timeout 0 0
 logging synchronous
 login local
line aux 0
line vty 0 4
 access-class 23 in
 privilege level 15
 login local
 transport input telnet
line vty 5 15
 access-class 23 in
 privilege level 15
 login local
 transport input telnet
!
end

Also, just as a test, I plugged in the circuit into the old original router's DSU/CSU and got just the green light.

>and got just the green light.

What grenn light? I thought the old router failed?

Old router ethernet interfaces were failing, dropping tow three times a day, from a power surge about a month ago.  I don't know what else may have been fried so I thought having new routers on hand, may as well swap out the entire router.  It's been nice having everything else stable, it's just this one circuit out for occasional use.

I just noticed that there was one line that did not copy over because I must not have changed the interface name from the interface of the old router. It is...


ip nat inside source list 10 interface Serial3/0.201 overload

I'm going to go add that, with the appropriate serial int name.  

That will get your IP traffic moving but it won't have any effect on the interface being down.

>and got just the green light.

What green light?

The CD light on the dsu/csu

On the new router I have the green light along with an amber AL light.  The one time the new router was functioning, the AL light was off and only the green CD light was on.

I plugged the circuit into the old router dsu/csu and it connected with only the green CD light.

You're right, why is the interface just down?  I thought I'd see something different this AM when I tried both a new DSU/CSU and then an entire router.  I have a 1700 too, I'm not sure if it is worth swapping it out and trying that.

What does this line do?  
ip nat inside source list 10 interface Serial3/0.201 overload

You say get my IP traffic moving, but it already was, I'm a little suspect of the .201 overload

That particular .201 does not connect anymore, (I only included it so as to have the complete configuration from the old router)  Does overload try and throw traffic out to that connection?  If so, that could have been the ethernet problem with the old router

Please post a "show service-module"

The router will bring up the interface as soon as the line is inserted into the DSU/CSU NT1 jack and the interface is configured. There are a couple of things to look for when determining if the interface is properly functioning.

The AL (Alarm) light on the DSU/CSU should be off and the CD (Carrier Detect) light should be green.

If the AL light on CSU/DSU is amber and CD light is green

Create a loopback cable to test the WIC-1DSU-T1. RJ-45 pins 1-4, 2-5 connection.

You've already set the framing to esf and linecode to b8zs, right? wri mem, plug the loopback cable and see the status of the LEDs.

Here is the service mod

(See above -It is a WIC-T1-V2 , already swapped out DSU and full router for testing equipement, router is right out of the box)


Module type is T1/fractional
    Hardware revision is 0.50, Software revision is 20051025,
    Image checksum is 0x3EFB7B, Protocol revision is 0.1
Transmitter is sending remote alarm.
Receiver has no alarms.
Framing is ESF, Line Code is B8ZS, Current clock source is line,
Fraction has 24 timeslots (64 Kbits/sec each), Net bandwidth is 1536 Kbits/sec.
Last module self-test (done at startup): Passed
Last clearing of alarm counters 01:34:49
    loss of signal        :    1, last occurred 01:34:42
    loss of frame         :    1, last occurred 01:34:42
    AIS alarm             :    0,
    Remote alarm          :    0,
    Module access errors  :    0,
Total Data (last 6 15 minute intervals):
    168329 Line Code Violations, 6138 Path Code Violations
    0 Slip Secs, 954 Fr Loss Secs, 5131 Line Err Secs, 49 Degraded Mins
    3003 Errored Secs, 2999 Bursty Err Secs, 455 Severely Err Secs, 1940 Unavail
 Secs
Data in current interval (286 seconds elapsed):
    65492 Line Code Violations, 1023 Path Code Violations
    0 Slip Secs, 36 Fr Loss Secs, 286 Line Err Secs, 4 Degraded Mins
    250 Errored Secs, 250 Bursty Err Secs, 36 Severely Err Secs, 0 Unavail Secs
yourname#

This is most likely a provider issue. If the alarm LED is on, it means there is no connectivity to the service. Which means that either the WIC is bad (it worked for a while and you swapped that out), the cable between the WIC and the smartjack is bad (it worked before) or there is a problem with the service.

Since the problem went away after AT&T got involved (with no change in your config or equipment), that is further evidence of a provider issue.

I agree, and the loopback cable test would help strengthen your case

don -
Could be provider except for the fact I got what looked like a good connection(Only a green CD light) with the old router this morning using same Cat5 and same line to dmark, etc.

As much as I would like to say it is the provider, the only thing that changed to cause a problem on this circuit was when I pulled the old router out of service.  The anomaly is the fact the new router worked briefly at one point.

Yes, that is a fly in the ointment.

Can you post the config of the old router?

Old Router config

version 12.2
service config
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
!
hostname SA_3640_frame
!
boot system flash c3640-i-mz.122-12.bin
logging buffered 4096 warnings
aaa new-model
enable secret 5 $1$R3zj$ig/kIYUXMQuTb9APooiEz/
!
username solarcom password 7 105D0615040511040140
clock timezone eastern -5
clock summer-time est recurring
ip subnet-zero
!
!
ip name-server 205.152.0.5
!
!
!
!
interface FastEthernet3/0
 ip address 192.168.35.1 255.255.255.0
 no ip redirects
 ip nat inside
 shutdown
 duplex auto
 speed auto
!
interface Serial3/0
 description Frame Relay to Bellsouth ckt ID 70QGDA500669
 no ip address
 encapsulation frame-relay IETF
 no fair-queue
 service-module t1 timeslots 1-24
 frame-relay lmi-type cisco
!
interface Serial3/0.102 point-to-point
 description PVC to Plantation PKRouter
 ip address 192.168.196.1 255.255.255.0
 ip nat inside
 frame-relay interface-dlci 102
!
interface Serial3/0.103 point-to-point
 description PVC to  PDRouter
 ip address 192.168.198.1 255.255.255.0
 ip nat inside
 frame-relay interface-dlci 103
!
interface Serial3/0.104 point-to-point
 description PVC to Marathon MRRouter
 ip address 192.168.195.1 255.255.255.0
 ip nat inside
 frame-relay interface-dlci 104
!
interface Serial3/0.117 point-to-point
 description PVC to MCSO
 ip address 192.168.192.1 255.255.255.248
 ip nat inside
 frame-relay interface-dlci 117
!
interface Serial3/0.201 point-to-point
 description PVC to CFRouter
 ip address 160.131.26.138 255.255.255.252
 ip nat outside
 frame-relay interface-dlci 201
!
interface FastEthernet3/1
 ip address 192.168.35.1 255.255.255.0
 no ip redirects
 ip nat inside
 duplex auto
 speed auto
!
router rip
 version 2
 network 160.131.0.0
 network 192.168.192.0
 network 192.168.195.0
 network 192.168.196.0
 network 192.168.198.0
 no auto-summary
!
ip nat inside source list 10 interface Serial3/0.201 overload
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.35.253
ip route 10.0.0.0 255.0.0.0 192.168.192.2
ip route 162.143.0.0 255.255.0.0 192.168.35.2
ip route 192.168.33.0 255.255.255.0 192.168.192.2
ip route 192.168.37.0 255.255.255.0 192.168.198.2
ip route 192.168.45.0 255.255.255.0 192.168.35.5
ip route 192.168.65.0 255.255.255.0 192.168.35.5
ip route 192.168.99.0 255.255.255.0 192.168.192.2
ip route 199.250.0.0 255.255.0.0 Serial3/0.201
no ip http server
ip pim bidir-enable
!
access-list 10 permit 192.168.0.0 0.0.255.255
snmp-server engineID local 00000009020000B0C289C5B1
snmp-server community public RO
snmp-server community public$ RO
snmp-server community private# RW
snmp-server location Key West
snmp-server enable traps tty
banner motd ^CC
       ,,,,,
      /'^C
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
end

Resolved!!!  I will Split the points for all your assistance.

I don't think that V2 card is compatible with the 1800 router, even though it came packaged with it.  I had a 1700 lying around with the standard DSU/CSU.  So I configured just the serial on it and it linked up fine.  I gave it's ethernet an IP, and routed the the traffic for the circuit on the 1800 to that IP (not wanting to take down the whole shooting match) and everything works.  I'll just completely swap out the 1800 with the 1700 off hours.

At some point in all of this I saw on the cisco site the approved routers for the V2, and noticed the 1800 was not on the list.  Go figure, these 1800s I had were purchased before my arrival, you would think they would come with a compatible DSU/CSU but then again my predecessor did some strange things....like plug routers into wall outlets.