Equipment Support > Hardware By Brand > Cisco > Cisco 1751 with t1 card

Cisco 1751 with t1 card

Before replacing your equipment, make sure the T1 gets tested by your provider from the farthest point away from your location with a battery of tests, including a stress test - this will check all 13 repeaters and smartjack. It should be done first to the smartjack, then to the CSU.
Could be a repeater, bad pairs, borderline smartjack, up to a bad connector/cable/wire from the smartjack to the CSU.

All t1 lines should be conditioned before service but some components have a tendency to die once they are placed in actual work conditions. Some memorable trouble include a particular cable pair segment that tested OK at first and took 20+ minutes of continuous testing before it started sputtering errors.

Hope your t1 trouble gets resolved soon!

reply to bbwithdrawls
I SWEAR circuit troubleshooting is the bane of any network engineer,
and I'd need a few supercomputers to keep track of the number of times
telco's told me "we can loop the smartjack but not the CSU, the
problem's on your end." *sighs*

Couple basic questions bbwithdrawls

- How's the T1 configured on the 1751? Is all the configs under the
serial 0/0 interface (clockrate, bandwidth, etc?) or are there additional
configs?

- next time it happens, can you grab the output of "sh controller T1"
and save it for reference?

- what's between the 1751 going to the smartjack and about how far is
the distance to the smartjack? Do you have any replacement cabling you
can use to rule out a cable issue?

Like rovernet suggested, I'd get them to run a stress test on the circuit
for a minimum 4 hours. Depending on your SLA, you could ask for a head
to head test which basically loops a signal between the CO back to your
smartjack with testers on either end to verify the circuit path. That part's
for the telco.

For yourself, I'd see about making a loopback cable to test the chunk
from the smartjack to the WIC card in the 1751. Here's a doc which
conceptually explains this

»www.cisco.com/en/US/tech/tk713/t···4b.shtml

I'd also get with the telco and make sure that framing / clocking / etc.
is verified between their device and your device.

If the WIC card is seeing a Yellow Alarm, then that usually means an
upstream issue, the trick is isolating where the problem is.

Here's a few more docs that may help you to troubleshoot this from the 1751,
or just do a search on Cisco for T1 troubleshooting.

»www.cisco.com/en/US/tech/tk713/t···52.shtml

»www.cisco.com/en/US/tech/tk713/t···8d.shtml

Best of luck!

Regards

my configs with a few things masked

xxxxxx#show run
Building configuration...

Current configuration : 1019 bytes
!
! Last configuration change at 05:49:11 UTC Wed Feb 4 2009
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname XXXXXXXX
!
boot-start-marker
boot-end-marker
!
logging buffered 4096 debugging
enable secret 5XXXXXXXXXXXXXXXXXXXXXX
enable password XXXXXXXXXXXXXXXX
!
memory-size iomem 25
no aaa new-model
ip subnet-zero
!
!
!
ip cef
!
!
!
!
!
interface FastEthernet0/0
ip address XXXXXXXXXXXXXXXXXXXXXX
no ip redirects
no ip unreachables
no ip proxy-arp
speed auto
full-duplex
no cdp enable
!
interface Serial0/0
bandwidth 1536
ip address xxxxxxxxxxxxxxxxxxxxxxxx
no ip redirects
no ip unreachables
no ip proxy-arp
encapsulation ppp
no fair-queue
service-module t1 timeslots 1-24
service-module t1 remote-alarm-enable
service-module t1 fdl both
no cdp enable
!
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0/0
no ip http server
!
no cdp run
!
line con 0
line aux 0
line vty 0 4
password XXXXXXXXXXXXXXXXXXXX
login
!
end

XXXXXXXXXXX#

yes i plan on grabbing the show controller and sh int for s0/0 just to document

between my router and the smart jack about 8 ft tops , i had to rewire the stuff they did on this side as it was all wrong , the day of my turnup , ( worked with excellent engineer kevin collins from the company , he had me make a looback and test

I had a head to head scheduled last night a t 6 but when i called in they had already closed the ticket , it was my equipment , ( yeah right ) because whe it happenned the did a test and couoldnt loop the csu , NO KIDDING I had to reset everything

any way i plan on taking that back up Monday morning

reply to bbwithdrawls
So it goes : 1751 -> WIC -> 8' cable -> smartjack -> telco cloud?

Depending on your SLA, I'd get your account manager involved and document
this stuff on your end, along with any "tickets" they may have closed with
the comment "customer-end problem" and start beating them over the head
about it.

The config looks pretty bogstandard, but I'd still verify it with what
they have on their end for the encapsulation and the T1 config.

Just for chuckles, I'd test the cable again (if you can) and loop your
connection for a couple hours as well and pull the pre/post output, just
so you have something to back your router / WIC / cable up.

Regards

1751 -> WIC -> 8' cable -> smartjack -> 13 repeaters to CO in Vanleer, then from there to CO in Dickson , then CO in Nashville

it happened again Sunday morning , I noticed the power flicker , sure enough , all electronic clocks blinking , Look at the T1 , yellow alarm light , wait 10 minutes to see if it will reset itself, it doesn't , i had to rest the card to bring it back up

if the power goes out shouldn't it come back up with out having to reset card???

reply to bbwithdrawls
I wonder if the power has anything to do with it? What I'm thinking is
it could be a sag, not enough to force the thing to reload but enough
to damage the electronics.

You able to UPS the router and smartjack to rule that out?

Regards

definitely gonna ups the router , the smart jack , unless I'm mistaken mine is powered remotely , they had a heck of a time installing it and keep blowing fuses in the card at the CO , the techs fix was " turned up the voltage to the card " he said if that didn't work they would have to redo my smartjack and power it here at the house and put it inside , they never did ,

everything I'm reading says the yellow alarm light is the remote system , blue and red are for the local system unless i read it wrong , Ill try the UPS and see if that works out

Do a "sh service-module serial 0" and see how that looks -- specifically, is the carrier providing clocking? There's also some more interesting info here than the "sh int s0" stuff.

(This is from an older 1721 we have, if you're running a newer IOS things may have changed. I don't mess with the 17xx much these days -- the ones we have just work till they die, then we chunk in a replacement.)

show service-module

Module type is T1/fractional
Hardware revision is 1.3, Software revision is 20050811-0.3,
Image checksum is 0x80ACD1B3, Protocol revision is 0.1
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 3d22h
loss of signal : 0,
loss of frame : 0,
AIS alarm : 0,
Remote alarm : 0,
Module access errors : 0,
Total Data (last 96 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in current interval (498 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

framing line code and clocking came from the provider ,

Yep that looks normal to me... I was curious about the clock source especially, we ran into issues with who was providing clocking when our T1s first came up.

Seems clean otherwise though.... I'm out of ideas. Good luck though...

reply to bbwithdrawls
I think I should pay my bill the way they handled my ticket , tell them its their problem and ignore them

LOL..... I like that.... it is only fair, pay for the service you get

Rule # 1 for telco, it is ALWAYS the customer's CPE at fault

Since you have to bounce your side for the circuit to come back up, it will be very hard to get telco to admit anything is 'wrong' on their end. UPS in your case is a must. The 2nd router/card should help rule things out also.

If worst come to the worst, get your provider to manage the equipment on your premises. It will cost you extra, but the onus of maintaining the integrety of the circuit will lay with your ISP & they will have to maintain pre-defined SLAs.

reply to bbwithdrawls
@ladino
Preachng to the choir here. I can't count the number of times I've simply
had to tell their frontline staff that power to site and equipment had
already been verified and to begin testing the line just to get them to
open a ticket.

Honestly, the next time it breaks, tell them to escalate to a manager and get
their L2s on the line. Frontline for alot of telcos I've found are simply
ticket monkeys -- good at picking up the phone but not much else and more often
than not never even given access to the equipment they're supposed to be
monitoring. Try and figure that one out.

As for managed router services, yes it's alittle less of a headache sometimes,
but I've had problems or two where most of the conversation revolved around
eactly where on the managed router the ISP's responsibility ended and
the customer's began. Ugh!

@bbwithdrawls
Keep all this output gathered so far... I think it should let you build a pretty
good picture of what the environment's supposed to look like when its functioning,
so if it happens next time you can compare and at least shove it back in their
faces and tell them they're full of it to say the problem's on your side.

Regards

I'm going to go ahead and get a backup anyway and just copy the con fig out this one to it , and keep this one as a back up ( if i wasn't already planning on doing it for i backup i would refuse on principle , Im 99% sure its not the equipment but if it happens again i replaced the equipment now its their turn , they wont have that to fall back on ,

I put it on a ups today so we;ll see what happens , thanks for all the advice

reply to bbwithdrawls
One last suggestion is to keep a detailed log, or get a folder for
youserlf holding all your documentation, output, what actions
taken and when, along with previous ticket #s from their side.

Again, speaking as someone who's been on the fronlines, the collective
memory of what may and maynot have been done tends to get easily lost
in the shuffle of dealing with so many other tickets, and it helps
to have all that information within easy reach.

Regards

reply to bbwithdrawls
Well , Well, Well, Vindicated at a cost

My T1 went down Friday at 8pm , called into the #they gave me all weekend and got the same sad story , someone was dispatched and checking

late Sunday night I gave them an earful and a scathing email this morning ,

they at first blamed my equipment , I got past that with check the circuit its dropping 50-75% of the packets , oh yeah that's our problem , then i got its not a hard down down because my router showed the int up/,?? i explained it real clear to them them with ,"" I don't care what you call it but its useless right now , it doesn't work"
so I was down all weekend and it wasn't my equipment but a bad pair of lines ???

I'm confident that was the issue early on but I learned a while back take the excuses away you get to the problem , so I bought me a backup today and will switch them out , next time I'm waiting for them to say its my equipment , my equipment showed up /UP but on a ping to the edge router on the other side of mine it was dropping 50-75% of the packets

anyway that's where that is , its off to a rocky start but I'm hoping it will be better in the near future

reply to bbwithdrawls
Sounds like you're making some inroads in their BS there bbwithdrawls.
Look forward to hear what their next round of excuses are with the
backup in place. BTW, did the power go down again this outage, and
how'd the UPS handle it?

Regards

no no power issue this time , i was actually sitting here on it went it went down , no alarms lights nothing but no browser, ping all my equipment all good , ping the edge router , dns and this is what it looked like
Reply from 12.127.16.67: bytes=32 time=33ms TTL=243
Request timed out.
Request timed out.
Reply from 12.127.16.67: bytes=32 time=34ms TTL=243
Request timed out.
Reply from 12.127.16.67: bytes=32 time=33ms TTL=243
Reply from 12.127.16.67: bytes=32 time=33ms TTL=243
Reply from 12.127.16.67: bytes=32 time=33ms TTL=243
Request timed out.
Reply from 12.127.16.67: bytes=32 time=33ms TTL=243
Request timed out.
Reply from 12.127.16.67: bytes=32 time=33ms TTL=243
Reply from 12.127.16.67: bytes=32 time=34ms TTL=243
Reply from 12.127.16.67: bytes=32 time=33ms TTL=243
Reply from 12.127.16.67: bytes=32 time=34ms TTL=243
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 12.127.16.67: bytes=32 time=33ms TTL=243
Reply from 12.127.16.67: bytes=32 time=33ms TTL=243
Reply from 12.127.16.67: bytes=32 time=34ms TTL=243
Request timed out.

wasn't working real good