The following are helpful tools used to gather information about your 5BRI
ports.
As you can see, this may help in answering your question about the
"NO-SERVICE". Sounds like the telco is dropping your SPID/circuit out of
the switch, maybe maintanence.
Note: Any switch provisioning changes in the global settings of the
Portmaster will need to be saved, and a power cycle will need to follow.
The ISDN module is loaded at boot time and will not take effect
dynamically.
Show Port
Command> show <port>
Here is a table for what show port displays according to port status:
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 ISDN
Command> show ISDN
This command will show us a status of what is on the D channel. The frame
counter helps us see if our circuit is live or not, no D channel frames no
ISDN line.
Command> show isdn
D Ports State Change Start Up Down Time Sess In Out
Err
-- ------- --------- ------ ----- ----- ----- ----- ------ ------- -------
----
5 S10/S11 Active 0 2 2 0 0 0 23 19
0
6 S12/S13 Active 0 2 2 0 0 0 23 19
0
7 S14/S15 Active 0 2 2 0 0 0 24 20
0
Here are the meanings of the "show isdn" fields:
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
ERRa = number of CRC, abort, overrun, bbc (bad byte count) and
lost
frame errors.
----------
> From: McClure Doug <closer@scescape.net>
> To: portmaster-users@livingston.com
> Subject: PM 2E ISDN
> Date: Sunday, December 29, 1996 9:10 AM
>
> Has anyone else had a problem with ports going NO-SERVICE DCD- CTS+
> TELCO+ NT1+ periodically?
>
> -doug