Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

AWAITING_ESTABLISHMENT...

I keep getting this when I do 'sh isdn status' on my AS5300. The only thing that fixes it that I've found is a reload of the entire system. What are some debugs that I can run to see what's going on?

11 REPLIES
Cisco Employee

Re: AWAITING_ESTABLISHMENT...

sh controllers T1

debug isdn q921

HTH

java

if this helps, please rate

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

Re: AWAITING_ESTABLISHMENT...

They went down again and I get this:

%CONTROLLER-5-LOOPSTATUS: Controller T1 3, PAYLOAD loopback request from external network

'show controller T1 3' gives me:

T1 3 is up. (Payload Loop by Remote)

Applique type is Channelized T1

Cablelength is long gain36 0db

Description:

Receiver has no alarms.

alarm-trigger is not set

Soaking time: 3, Clearance time: 10

AIS State:Clear LOS State:Clear LOF State:Clear

Version info of slot 0: HW: 4, PLD Rev: 0

Manufacture Cookie Info:

EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x42,

Board Hardware Version 1.32, Item Number 73-2217-05,

Board Revision B16, Serial Number 09354209,

PLD/ISP Version 0.0, Manufacture Date 19-Jun-1998.

Framing is ESF, Line Code is B8ZS, Clock Source is Internal.

Data in current interval (256 seconds elapsed):

0 Line Code Violations, 0 Path Code Violations

23 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

23 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Data in Interval 1:

83 Line Code Violations, 551 Path Code Violations

41 Slip Secs, 18 Fr Loss Secs, 2 Line Err Secs, 1 Degraded Mins

43 Errored Secs, 0 Bursty Err Secs, 10 Severely Err Secs, 18 Unavail Secs

Data in Interval 2:

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 Interval 3:

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 Interval 4:

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 Interval 5:

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 Interval 6:

6 Line Code Violations, 0 Path Code Violations

0 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 0 Degraded Mins

0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Total Data (last 6 15 minute intervals):

89 Line Code Violations, 551 Path Code Violations,

41 Slip Secs, 18 Fr Loss Secs, 3 Line Err Secs, 1 Degraded Mins,

43 Errored Secs, 0 Bursty Err Secs, 10 Severely Err Secs, 18 Unavail Secs

I can't find much on google about my situation :(

Hall of Fame Super Gold

Re: AWAITING_ESTABLISHMENT...

Does "shut / no shut" and controller T3 fixes it ?

After how long it happens ?

Which exact IOS are you running ?

New Member

Re: AWAITING_ESTABLISHMENT...

I can't seem to recreate it yet so I can't really put a time to it. Right now it's been up for a couple hours. But earlier it happened about 10 minutes after I 'reload'. My IOS version is:

IOS (tm) 5300 Software (C5300-JK9S-M), Version 12.3(26), RELEASE SOFTWARE (fc2)

Another thing I'd like to point out is that the particular controllers that go down are connected to a proprietary conference bridge. A shut/no shut doesn't bring it up either.

interface Serial3:23

no ip address

encapsulation ppp

trunk-group BRIDGE 1

isdn switch-type primary-ni

isdn protocol-emulate network

isdn incoming-voice modem

no fair-queue

no cdp enable

end

controller T1 3

framing esf

linecode b8zs

pri-group timeslots 1-24

Those are the configurations I have.

Hall of Fame Super Gold

Re: AWAITING_ESTABLISHMENT...

Problem seems to be somewhat with the DS3 circuit, of course it's an anomaly that reloading fixes it. You can try upgrading IOS, latest 12.3 for example.

New Member

Re: AWAITING_ESTABLISHMENT...

I am connected to the bridge with a T1 xover cable... no DS3 here. Also, AFAIK I'm on the latest IOS supported by the AS5300... 12.3(26).

Here's something interesting:

Apr 13 16:38:43 CDT: ISDN Se2:23 Q921: Net TX -> SABMEp sapi=0 tei=0

Apr 13 16:38:44 CDT: ISDN Se2:23 Q921: Net TX -> SABMEp sapi=0 tei=0

Apr 13 16:38:45 CDT: ISDN Se2:23 Q921: Net TX -> SABMEp sapi=0 tei=0

Apr 13 16:38:46 CDT: ISDN Se2:23 Q921: Net TX -> SABMEp sapi=0 tei=0

from http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801509d7.shtml it says that if the router receives these messages it will Tx a UAf. Does that hold true for the opposite? If the router Tx a SABMEp should it Rx a UAf from my conference bridge?

Hall of Fame Super Gold

Re: AWAITING_ESTABLISHMENT...

Yes, a sabme elicits uaf. Is the bridge is providing clock ? Probably it is not, from the show controller something is wrong with that.

New Member

Re: AWAITING_ESTABLISHMENT...

my guess is that the bridge doesn't provide the clock. That's why it's set to 'clock source internal'. It looks like this is the problem... I don't Rx a UAf and just keep Tx'ing SABMEp messages over and over.

I have tried to change it to 'clock source line primary' with no joy. How do I reset layer 2? When I do a shut/no shut on the interface it looks like it takes down layer 3 only.

Hall of Fame Super Gold

Re: AWAITING_ESTABLISHMENT...

What could be happening, is that the bridge sees too many errors and shuts down his port temporarily.

Shut under interface should bring layer 2 and 3 down. Shut under controller sets RAI bit, that is a clean way to bring down layer 1.

New Member

Re: AWAITING_ESTABLISHMENT...

I can tell that the conference bridge hasn't shutdown the port. It even tries to use it but can't because "Requested circuit/channel not available". I'm going to investigate why the conference bridge doesn't reply to my SABME messages... that has to be the reason it won't get to MULTIPLE_FRAME_ESTABLISHED.

If you have any other suggestions it would be greatly appreciated.

New Member

Re: AWAITING_ESTABLISHMENT...

I also receive this:

Apr 13 18:11:11 CDT: ISDN Se2:23 Q921: Net RX <- RRp sapi=0 tei=0 nr=4

from the conference bridge. So, it seems that it's sending something... just not the UAf. Does this indicate anything that you know of?

952
Views
0
Helpful
11
Replies
CreatePlease to create content