Troubleshooting Tips for Cisco e1 pri

Table of Contents

Updated

1. Download ASR Pro

2. Run the program

3. Click "Scan Now" to find and remove any viruses on your computer

Speed up your computer today with this simple download.

Hope if you have any problems with Cisco e1 pri on your PC this guide can help you.

Presentation

When troubleshooting the Primary Rate Interface (PRI), make sure the E1 is working properly at both ends. When the tier 1 issues are resolved, check for tier 2 and tier 3 issues. Use the show controller e1 command to verify that the line configuration matches the remote end configuration. Make sure cropping, channel coding and time source are set correctly. For more information, see Some e1 alarm troubleshooting and E1 fault event troubleshooting documents. Contact your current service provider for correct settings.

Before You Start

How do you troubleshoot a PRI issue?

Check the PRI line configuration and make sure it matches the physical configuration.Make sure you are using an efficient T1 cable. Most PBXs use a T1 crossover cable.If PRI still does not improve after steps 9 and 3, check if ewua (PRI / NET) or possibly ewsipgw (PRI / USER) is running.

Conventions

For more information on document conventions, see the “Cisco Technical Agreement Tips” section.

Requirements

Components Used

The information in this document is based entirely on the software and release tools listed below.

How do you troubleshoot a T1 line?

Make sure the portion of the cable between the interface connector and the T1 service provider device or critical T1 device is securely connected. Make sure the link is of the correct type. Correct the cable connections if necessary. Check the integrity of the cable by looking for matches or other physical abnormalities in the cable.

Cisco IOS® Software Release 12.0

Information

The document presented in this qualification document was created by devices in concrereal laboratory environment. A different approved (standard) configuration was triggered for all items used in this document. When training online, make sure people understand the potential impact of real-time selling before you start using it.

Use Current ISDN Status Command

Updated

Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!

The Establish isdn status command displays a summary of all ISDN interfaces. It also shows the most important status of levels 1, 2 and c. To check the basic state of the layers, do the following:

Make sure level 1 is in the ACTIVE state. Shell state 1 should always be ACTIVE, unless E1 fails.

If the output of the isdn show command shows that Layer 1 is definitely OFF, then there is a problem with the physical connectivity of the E1 queue. If the line is administratively inactive, use the no shutdown command to restart the interface.
Make sure level 2 is in the MULTIPLE_FRAME_ESTABLISHED state. This is an important state for indicating Layer 2 that Layer 2 frames are exchanged and initiated Level 2ization completed.

If layer 2 is not in the MULTIPLE_FRAME_ESTABLISHED state, use the show controller e1 EXEC command to diagnose the problem. See Troubleshooting E1 Alarms for more information.

Since the show isdn status command displays a blur of the current state, level 2 should jump up and down despite displaying a MULTIPLE_FRAME_ESTABLISHED status. Use isdn q921 debug to analyze Layer 2 stability.

The following is definitely an example of ISDN position output:
```
 bru-nas-03 # Show Isdn statusISDN global switch type = Primary-net5ISDN series 0: 15 interfaces        dsl 0, ISDN switch type GUI = Primary-net5    Level 1 status:        ACTIVE    Level 2 status:       TEI = 0, Ces = 1, SAPI = 0, state implies MULTIPLE_FRAME_ESTABLISHED    Level 3 status:        Ideas Active Challenge Level 3    DSL 0 CCB enabled corresponds to 5        CCB: callid = 7D5, sapi = 0, ces = 0, B-chan = 9, calltype = DATA        CCB: callid = 7D6, sapi = 0, ces = 0, B-chan = 10, calltype = DATA        CCB: callid = 7DA, sapi = 0, ces = 0, B-chan = 11, calltype = DATA        CCB: callid = 7DE, sapi = 0, ces = 0, B-chan = 1, calltype = DATA        CCB: callid = 7DF, sapi = 0,ces = 0, B-chan = 2, calltype = DATA    Free channel mask: 0xFFFF78FC1:15 ISDN Serial Interface        dsl 1, ISDN interface switch type is the same as main network 5    Level 1 status:        ACTIVE    Level 2 status:       TEI = 0, Ces = 1, SAPI = 0, State = TEI _ASSIGNED    Level 3 status:        0 active level 3 calls    DSL activated 1 CCB = 0    Free channel mask: 0xFFFF7FFF    The total number of allocated CCB ISDN is 5 
```
Note if E1 has 0 (whose D-channel serial number is 0:15) Layer 1 as ACTIVE and Layer 2 as MULTIPLE_FRAME_ESTABLISHED, which indicates that the entire signaling channel is functioning correctly and traditional Layer 2 frames are s Telco levers work. The D-channel for (serial1: 15) E1 1 was recently Tier 1 ACTIVE, but Tier 2 may be TEI_ASSIGNED. This indicates that the PRI is no longer exchanging Layer 2 frames with this switch. Use the show controller e1 command to troubleshoot errors. Refer to the current E1 troubleshooting flowchart for more information.

Using Our Debug Command

q921

The debug isdn q921 command displaysThere are procedures for accessing data (layer 2) that are presented on the router on the D-channel.

Make sure you are configured to display debug messages using the visit command from the console or terminal monitor.

Note. In a production check state, console logging is disabled only with the show logging command. If logging was enabled, the access server could temporarily stop working if the console port was full of log messages. Enter the no hauling console command to disable logging.

Note: if

Debug isdn q921 is enabled, but you are not getting any debug output, calling or resetting the controller for debug output.

Consider the following considerations to ensure that the upper layer data link access procedures on the primary router are done on the D-channel:

Make sure level 2 is stable next to message lookups during debugging. If the line bounces up and / or down, a result similar to the following appears:

 women   Years March 10: 06: 07.% ISDN-6-LAYER2DOWN: 882: Layer 2 for interface Se0: 15, TEI 0 disabledMarch 25, 10:06: 09.882:% LINK-3-UPDOWN: Interface Serial0: 15, status changed to DownMarch 20, 10:06: 21,274:% DSX1-6-CLOCK_CHANGE: Controller 0 is now selected as alarm clock source.28.03. 10: 06: 21.702:% ISDN-6-LAYER2UP: Layer 2 for Se0: 15, TEI 0 went upMarch 20, 10:06: 22.494:% CONTROLLER-5-UPDOWN: E1 controller 0, status changed, you can now startMarch 20, 10.06: 24.494: Interface% link-3-updown: Serial0: 15, change right

If Layer 2 generally does not seem stable, see the Troubleshooting E1 Errors section.

Make sure that only SAPI (Service Access Level Identifier) messages are displayed on the sending (TX) and receiving (RX) side. For example:

 20.March 10: 06: 52.505: ISDN Se0: 15: TX -> RRf sapi 0 corresponds to part 0 = nr 0 =Mar something 10: 06: 52.505: ISDN Se0: 15: RX <- RRf equals sapi 0 tei = 0 NR equals 0March 20 10: 07: 22.505: ISDN TX se0: 15: -> RRp sapi = 0 tei = nothing NR = 0March 20 10: 07: 22.509: ISDN Se0: 15: RX <- Sapi rrp = null tei = 0 NR = 0March 23 10: 07: 22.509: ISDN Se0: 15: TX -> RRf corresponds to sapi 0 tei = 0 NR means 0March 20 10: 07: 22.509: ISDN Se0: 15: <- rx RRf sapi = 0 tei = 0 NR = 0

Make sure you are not viewing the newsletters p Asynchronous Balanced Enhanced Mode (SABME). These messages indicate that this level 2 is trying to reset itself. Messages usually appear when poll requests (rrp) are sent and there is no response from the switch (RRf), or vice versa. The following examples are SABME messages:
```
 20.March 10: 06: 21.702: ISDN Se0: 15: RX <- Sapi sabmep = tei = 0March 20 10: 06: 22.494: ISDN Se0: 15: TX -> SABMEp sapi = 0 game implies 0
```
If SABME messages appear, complete the following path:
1. Use the show running-config command to verify that the ISDN switch and PRI group timeslots can be configured correctly. Check with your service provider for the correct values.
2. Enter the following commands to exchange ISDN switch type and Pri group settings:
```
 bru-nas-03 # configure the terminalbru-nas-03 (config) # isdn-switch-type-primary-net5bru-nas-03 (config) # controller e1 0bru-nas-03 (config-control) # pri-group time window 1-31
```
How do you check if PRI is down?

Check out the line log.Wiring.Check if the ISDN line is active.Start with the default settings for your country.Check the yellow status LED.Check the connection mode setting.Check the XLOG trace.Check if your PRI line is Fraxel line.

Verify channel D is active using the show Interfaces Sequence Number: 15 command, where number is the interface number.

If channel D doesn't actually useXia, the no shutdown command calls it directly. For example:
```
 bru-nas-03 (config) # serial interface 0:15bru-nas-03 (config-if) # without stopping
```
Make sure you are using PPP encapsulation. Otherwise, use the ppp encapsulation control to set encapsulation. For example:

PPP
```
 bru-nas-03 (config-if) # encapsulation      
```
Make sure the interface is in loopback mode. Loopback should only be installed for testing purposes. Use the No Loopback command to remove loops. For example:
Loopback
```
 bru-nas-03 (config-if) # no
```
In general, turn your router off and on again.