Paladin Roaming

ATM circuits are up

A couple of days ago the Fiber People finished running the fiber connections. Yesterday the Fiber people turned up the OC3 and pronouced it 'hot to trot.'

This morning, on the Cisco Catalyst 8540's, I plugged in the fibers to the Avaya (drop side) and the coax cable to the fiber rack (line side.) Lit up some pretty green lights. (except for my transmit the line side.)

Ran into an interesting glitch....

The ethernet control channel is in and up, I can ping it, I can telenet into it. And I cannot, or rather should not, get past the password authentication.

On the A switch I telenet in, type in the default cisco/cisco, and get rejected. Which is as it should be. To verify that I am talking to the A switch I pull the ethernet connection and type cisco/cisco again, and get ignored -- no echo of my typing. Which is as it should be given that I have broken the connection. But.... I then plug the ethernet back in and hit return and I am into the router, past the log-in! This is wrong -- I am not supposed to be able to get in.

While I am there I verify that ATM 0,0,0 is administratively down -- which is why I have no light on the line transmit. I verify that ATM 1,0,0 is up and up and is passing data between the router and the Avaya on the drop side. There is also an ATM 0,0,100 which I am confused as to what it might be.

I log off, try getting back in, and I am rejected -- even after the pull the ethernet trick. Don't understand.

Posted by at June 16, 2004 11:14 AM