No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Troubleshooting Procedure

Troubleshooting Procedure

NOTE:

Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.

Procedure

  1. Check that a link is set up successfully.

    Run the display isdn call-info command to check the call status.

    • If no information is displayed, no PRI interface is configured as a dialer interface. Create a dialer interface.
    • If the value of State in the command output is TEI_ASSIGNED or AWAITING_ESTABLISHMENT, the link is not set up. Rectify the fault according to Link Failed to Be Established on ISDN Interfaces.
    • If the value of State in the command output is MULTIPLE_FRAME_ESTABLISHED, the link has been set up. Go to step 2.

  2. Check whether the AR receives the call.

    Run the debugging dialer all, debugging isdn cc, debugging isdn q931, terminal debugging, and terminal monitor commands to check whether the AR sends and receives packets.

    • If the command outputs do not contain N->U, the AR does not receive calls. Check the configurations on the call initiator.
    • If the following information is displayed, the AR has received the call. Go to step 3.

      <Huawei>
      Oct 14 2007 10:30:19.160.1+08:00 AR2220 Q931/7/Q931_Debug: Serial1/0/0:15                                     
          N->U   DL_I_Data_Ind  CES = 1                                                                                cr= 02 00 e7 SETUP  *send_comp=a1 *bearer=04 02 88 90 *chan_id=18 03 a1 83 9a *called_n=70 05 80 30 31 32 33
      
      <Huawei>
      Oct 14 2007 10:30:19.160.1+08:00 AR2220-S Q931/7/Q931_Debug: Serial1/0/0:15                                     
          N->U   DL_I_Data_Ind  CES = 1                                                                                cr= 02 00 e7 SETUP  *send_comp=a1 *bearer=04 02 88 90 *chan_id=18 03 a1 83 9a *called_n=70 05 80 30 31 32 33
      
  3. Check whether the AR rejects the call.

    Various interaction packets are sent during the setup of an ISDN call. If the AR receives a packet of a wrong type, the AR rejects the call.

    Run the debugging dialer all, debugging isdn cc, debugging isdn q931, terminal debugging, and terminal monitor commands to check whether the AR rejects the call.

    • If the following information is displayed, the AR has rejected the call. Restart the AR.

      <Huawei> Oct 14 2007 08:56:10.30.1+08:00 AR2220 CC/7/CC_Debug: 
      CC <-DDR : ISDN_DISC_REQ 
      CallID=0x0 UserID=0x0 PortID=0x9 ServiceType=0x8 Channel=0x2 IsCompleted=0x0 Cause=0x00
      Oct 14 2007 08:56:10.30.2+08:00 AR2220 CC/7/CC_Debug: 
      CC->Q931: PRIM_DISCONNECT_REQ 
       CCIndex=0x0 L3Index=0x1 PortID=0x9 CES=0x1 *cause=08 02 80 90
      Oct 14 2007 08:56:10.40.1+08:00 AR2220 Q931/7/Q931_Debug: Serial1/0/0:15 
          U->N   DL_I_Data_Req  CES = 1  
          cr= 01 01 DISCONNECT  *cause=08 02 80 90
      
      <Huawei> Oct 14 2007 08:56:10.30.1+08:00 AR2220-S CC/7/CC_Debug: 
      CC <-DDR : ISDN_DISC_REQ 
      CallID=0x0 UserID=0x0 PortID=0x9 ServiceType=0x8 Channel=0x2 IsCompleted=0x0 Cause=0x00
      Oct 14 2007 08:56:10.30.2+08:00 AR2220-S CC/7/CC_Debug: 
      CC->Q931: PRIM_DISCONNECT_REQ 
       CCIndex=0x0 L3Index=0x1 PortID=0x9 CES=0x1 *cause=08 02 80 90
      Oct 14 2007 08:56:10.40.1+08:00 AR2220-S Q931/7/Q931_Debug: Serial1/0/0:15 
          U->N   DL_I_Data_Req  CES = 1  
          cr= 01 01 DISCONNECT  *cause=08 02 80 90
      
    • If the command outputs do not contain the preceding information, the AR has accepted the call. Go to step 4.

  4. Check whether the network-side device rejects the call.

    Various interaction packets are sent during the setup of an ISDN call. If the network-side device receives a packet of a wrong type, it rejects the call.

    Run the debugging dialer all, debugging isdn cc, debugging isdn q931, terminal debugging, and terminal monitor commands to check whether the network-side device rejects the call.

    • If the following information is displayed, the network-side device has rejected the call. Restart the network-side device.

      <Huawei> Oct 14 2007 09:40:38.10.1+08:00 AR2220 Q931/7/Q931_Debug: Serial1/0/0:15
          N->U   DL_I_Data_Ind  CES = 1                                                                        
          cr= 01 84 DISCONNECT  *cause=08 02 80 90  
      Oct 14 2007 09:40:38.10.2+08:00 AR2220 Q931/7/Q931_Debug:                                                                           
       [FUN: ProcMsgDisconnect, LINE: 545] ISDN Layer 3 call state change:-> CS_DISCONNECT_INDICATION 
      Oct 14 2007 09:40:38.10.3+08:00 AR2220 CC/7/CC_Debug:                                                                               
      CC<-Q931: PRIM_DISCONNECT_IND                                                                           
       CCIndex=0x3 L3Index=0x4 PortID=0x9 CES=0x1 *cause=08 02 80 90
      
      <Huawei> Oct 14 2007 09:40:38.10.1+08:00 AR2220-S Q931/7/Q931_Debug: Serial1/0/0:15
          N->U   DL_I_Data_Ind  CES = 1                                                                        
          cr= 01 84 DISCONNECT  *cause=08 02 80 90  
      Oct 14 2007 09:40:38.10.2+08:00 AR2220-S Q931/7/Q931_Debug:                                                                           
       [FUN: ProcMsgDisconnect, LINE: 545] ISDN Layer 3 call state change:-> CS_DISCONNECT_INDICATION 
      Oct 14 2007 09:40:38.10.3+08:00 AR2220-S CC/7/CC_Debug:                                                                               
      CC<-Q931: PRIM_DISCONNECT_IND                                                                           
       CCIndex=0x3 L3Index=0x4 PortID=0x9 CES=0x1 *cause=08 02 80 90
      
    • If the command outputs do not contain the preceding information, the network-side device has accepted the call. Go to step 5.

  5. Check that the protocol status of the data channel is Up.

    Run the display isdn active-channel command to check the activated data channel.

    <Huawei> display isdn active-channel                                                                                                             
    Serial1/0/0:15                                                                                                                      
    -------------------------------------------------------------------------------                                                     
    Channel  Call     Call     Calling        Calling     Called         Called                                                         
    Info     Property Type     Number         Subaddress Number         Subaddress                                                     
    -------------------------------------------------------------------------------                                                     
    B26      Digital  Out      88888204           -        88888206           -
    

    Run the display interface serial 1/0/0:15 command to check the data channel corresponding to the call. If the protocol status is Line protocol current state : Up, the protocol status of the data channel is Up. Go to step 6.

    If the protocol status is Line protocol current state : DOWN, the protocol status of the data channel is Down.

  6. Collect the following information and contact technical support personnel.

    • Results of the preceding troubleshooting procedure
    • Configuration files, log files, and alarm files of the AR

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000079719

Views: 492735

Downloads: 4523

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next