I have a remote site that still utilizes a single T1 connection to me. For multiple reasons we had to scrap the old T1 and have a new one put in. The old T1 resided on a T3 as channel 25. The new T1 is a standlone point to point. I removed the old config from my 7301 and programmed my 3725. I cannot figure out what is going on but the interface stays down/down. There is no loopback turned on, either manually or by the carrier. The AL LED stays amber regardless of whether or not I have a cable patched down. The CD LED remains green when I patch a cable down. LP is not light.
I am using a straight through ethernet cable to connect my 3725 to the smart jack. If you look at the show output below you will see DCD and CTS is down. Since the remote end was working and I just had the tech move the patch cable from one smartk jack to another I am assuming the problem is on my side or with the carrier. Can anyone please offer advice? I already tried changing the clock sourcd between internal and line. I also swapped out the WIC card for another one. Still no go. I don't usually program T1 connections. I am also listing my interface config minus the ip address info.
ip address x.x.x.x 255.255.255.252
ip flow ingress
ip flow egress
ip route-cache flow
serial restart-delay 0
Serial0/4 is down, line protocol is down
Hardware is GT96K with integrated T1 CSU/DSU
Description: T1 to Fire Island 18.104.22.168/30 [Circuit ID-32/HCGS/731924]
Internet address is 22.214.171.124/30
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Restart-Delay is 0 secs
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Because it's down/down, it's a physical issue. Did it work on the same smartjack before you replaced the card, or was the smartjack installed in parallel to the existing and you're just now moving over to it?
Something isn't right on the carrier's side then. The smartjack could be bad, the interface is down on the carrier's side (usually requires a test and turn up; did you schedule one?), or the cable is bad. I'm assuming that you're using the same cable, so that's probably not it. You should contact the carrier and have them look into it, because the way it stands now it looks like it's their fault.
John already pointed you in correct direction, but you can also try loopback tests from the router interface. Soft loopback test will also work to prove the hardware, but if you have a T1 hard loopback adapter (not hard to make one), you can prove upto demarc (that includes your cable as well). As this is new install, I hope you are not going to have any issue with the carrier, but just to share, last month I had an issue with one of our T1 (not new install) and carrier I had to prove everypoint in my infra to make them realise the issue in their colo.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...