From: Matthew Seppeler (Matt.Seppeler@InetX.com)
Date: Sun Oct 17 2004 - 23:13:47 GMT-3
Thanks!
I'll add the "clear interface bri0/0" prior to shutting down the
interface. Perhaps abruptly shutting down the interface may have caused
the issue on the ISDN switch. I also tested these procedures without
the IP address and works fine so I'll take off assigning the IP address
to the interface in these steps.
To summarize for those not wanting to read the following novel below,
follow these steps in configuring basic layer 2 connectivity for ISDN:
1) Do a "clear interface bri0/0"
2) Shut down the BRI interface.
3) Assign the ISDN switch-type
4) Assign spids if required
5) Do a "no shut" on the BRI interface
6) Confirm Layer 2 connectivity with the "show isdn status" command
7) Make a test call with the "isdn test call int b0/0 string" command
8) Run the previous command again to confirm the 2nd BRI channel comes
up
This should take about 2-3 minutes which could save you a lot of
troubleshooting with ISDN. Believe me, I know this from experience.
Matt Seppeler
Email: mseppeler@inetx.com
-----Original Message-----
From: Brian McGahan [mailto:bmcgahan@internetworkexpert.com]
Sent: Sunday, October 17, 2004 8:13 PM
To: Matthew Seppeler; ccielab@groupstudy.com
Subject: RE: "ESTABLISH_AWAITING_TEI" ISDN error message
Matt,
Before you shut/no shut or reload, try a "clear interface bri0".
Like I mentioned in class, the method that you used led you to the
conclusion that it was in fact a problem with the ISDN switch. Using
this type of method gives you more firepower when presenting the problem
to the proctor, as you can say I tried a,b,c and d, and it still doesn't
work. The lack of a layer 3 configuration (you don't need an IP address
BTW) is indicative that the problem relies at layer 2.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Matthew Seppeler
> Sent: Sunday, October 17, 2004 11:58 AM
> To: ccielab@groupstudy.com
> Subject: "ESTABLISH_AWAITING_TEI" ISDN error message
>
> ISDN is probably one of the most quirky things I had the pleasure of
> dealing with in preparing for the R&S exam. However, thanks to the
help
> of the Brian McGahan with Internetwork Experts and the Mock Lab class
I
> took the other week, I've settled into an almost foolproof way of
> minimizing the headaches of configuring ISDN. If you are in the final
> stretch in preparing for the lab, it's a class well worth the money.
>
>
>
> The basis for this email is to point out a case where it was required
to
> reload the ISDN switch in getting ISDN layer 2 working. Below are the
> steps I followed in configuring ISDN with the minimal configuration
> needed to get to this point of configuration:
>
>
>
> 1) Shut down the BRI interface.
>
> 2) Assigned an IP address to the interface.
>
> 3) Assigned the ISDN switch type to the interface.
>
> 4) Assigned the spids if required. In this case, yes as we are
> using basic-ni.
>
> 5) No shut on the BRI interface.
>
> 6) Verified Layer 2 connectivity with the show ISDN status. You
> should see "multiple frame stabled" with "valid" spids.
>
> 7) Run the command "isdn test call int b0/0 string" to test that
> the circuit comes up.
>
>
>
> If after running all these steps, this will verify that the ISDN
switch
> is indeed ok. Any further issues with ISDN will be a result of the
> config as extra stuff is added.
>
>
>
> Well, it looks like I found one of those rare cases that the ISDN
switch
> is to blame. Nope, it was not due to wrong spids or switch type.
Even
> after I did a reload on the router, I was still not able to get ISDN
> layer 2 connectivity up and working with the basic step followed
above.
>
>
>
>
> The error message when doing a "show isdn status" shows that the Layer
2
> status shows as "ESTABLISH_AWAITING_TEI" or "await establishment"
along
> with invalid spids. I kid you not, all I had to do to resolve this
> issue was to reload the ISDN switch. Fortunately, the rack I was on
> gives you access to reload the ISDN switch. This is not my own rack
to
> add. It was rented from RackTimeRentals and is one of the reasons why
I
> like using their racks. Great job Bill with providing this feature
for
> our use!
>
>
>
> Being that I've run into this problem before, I was quick enough to
log
> my config for my configuration steps as well as steps taken to resolve
> this issue. Below is input if you wish to review in further detail:
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:49 GMT-3