ISDN Debugging ToolsThe following are helpful tools used to gather information about the Lucent PortMaster (TM) 5BRI ports. Note: Changes to the global settings of the PortMaster will need to be saved, followed by a reboot of the unit as shown in the example below. The ISDN module is loaded at boot time and will not take effect dynamically. Example: Command> set isdn-switch type dms100 Show PortCommand> show sx <port> The table below gives an explanation of the field values of the "show port" command: Port Status Modem Status Description NO-SERVICE DCD- CTS- TELCO- NT1- No SPID set NO-SERVICE DCD- CTS- TELCO- NT1+ No cable or no circuit to Telephone Company NO-SERVICE DCD- CTS+ TELCO+ NT1+ Cable and ISDN circuit OK but SPID not registered IDLE DCD- CTS+ TELCO+ NT1+ SPID registered and ready to use. ESTABLISHED DCD- CTS+ TELCO+ NT1+ Connecting or providing device service but no carrier sensed ESTABLISHED DCD+ CTS+ TELCO+ NT1+ Connected ESTABLISHED DCD+ CTS- TELCO+ NT1+ Connected with V.120 async but flow controlled by other end Show ISDNCommand> show ISDN This command will show the state of the D channel and related S-ports.
Conditions of the D channel may be seen in the STATE column as ACTIVE, INACTIVE or
'STARTING'. The 'STARTING' condition may indicate a loop or a wiring
error on the telco side of the circuit. The table below gives an explanation of the field values of the "show isdn" command: Change = Minutes since last change in status Start = # of times NT1 has attempted to bring up link Up = # of times its gone to UP status Down = # of times its gone to DOWN status Time = # of times D channel has timed out attempting to bring up the link Sessions = # of times PortMaster has received a connect message from the switch In = # of input ISDN frames on B channel Out = # of output ISDN frames on B channel ERR = number of CRC, abort, overrun, bbc (bad byte count) and lost frame errors. |