|
|
Table 14-1 lists the troubleshooting commands.
| Command | Full Name | Page |
|---|---|---|
addalmslot | Add alarm slot | |
addextlp | Add external loopback | |
addloclp | Add local loopback | |
addlocrmtlp | Add local-remote loopback | |
addrmtlp | Add remote loopback | |
clrchstats | Clear channel statistics | |
clrclkalm | Clear clock alarm | |
clrclnalm | Clear circuit line alarm | |
clrclnerrs | Clear circuit line errors | |
clreventq | Clear the events queues | |
clrlnalm | Clear line alarm | |
clrlnerrs | Clear line errors | |
clrlog | Clear log | |
clrmsgalm | Clear message alarm | |
clrportstats | Clear port statistics | |
clrslotalms | Clear slot alarms | |
clrsloterrs | Clear slot errors | |
clrtrkalm | Clear trunk alarm | |
clrtrkerrs | Clear trunk errors | |
clrtrkstats | Clear trunk statistics | |
cnfbus | Configure Bus | |
cnflnalm | Configure line alarm | |
cnfslotalm | Configure slot alarm | |
cnftrkalm | Configure trunk alarm | |
dellp | Delete loopback | |
dncd | Down card | |
dspalms | Display alarms | |
dspbob | Display Breakout Box | |
dspbuses | Display Buses | |
dspclnerrs | Display circuit line errors | |
dspeventq | Display the event queue names and the data in each. | |
dspfrcbob | Display FRC-2/FRM-2 breakout box | |
dsplog | Display event log | |
dsplnalmcnf | Display line alarm configuration | |
dsplnerrs | Display line errors | |
dsppwr | Display power | |
dspslotalms | Display slot alarms | |
dspsloterrs | Display slot errors | |
dspslotstatcnf | Display slot statistics configuration | |
dsptrkerrs | Display individual or all trunk errors. | |
prtclnerrs | Print circuit line errors | |
prtlnerrs | Print line errors | |
prtlog | Print log | |
prttrkerrs | Print trunk errors | |
resetcd | Reset card | |
resetpc | Reset Port Concentrator | |
switchcc | Switch controller card | |
tstcon | Test connection | |
tstconseg | Test connection segment | |
tstdelay | Test delay | |
tstpcs | Test Port Concentrator Shelf | |
tstport | Test port |
Enables the MAJOR and MINOR alarm indicators on an Alarm Relay Card (ARC) or Alarm Relay Module (ARM). It also configures the slot to support external alarms from the Alarm Relay Interface (ARI) back card. You can use this command at any node that can provide external alarm indications to an alarm reporting system. The ARC or ARM can reside in any front slot but usually resides in the right-most slot.
Add alarm slot
addalmslot <slot number>
delalmslot, dspalms
Privilege | 1-4 |
Jobs | No |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
addalmslot 16
Enable alarm reporting from slot 16 in a node.
beta TRM YourID:1 IPX 32 8.5 Aug. 3 1997 14:27 MST
Alarm summary (Configured alarm slots: 16)
Connections Failed: None
Groups Failed: None
PLN Alarms: 1 Major
CLN Alarms: None
Cards Failed: 1
Missing Cards: None
Remote Node Alarms: 1 Major
Last Command: addalmslot 16
Next Command:
Places an external device in loopback mode. The addextlp command applies to existing connections on an SDP, HDM, LDP, or LDM. A "near" loopback causes the NEAR EIA template to be applied. A `far' loopback causes the FAR EIA template to be applied to the data port. The loopback remains in place until removed by the dellp command.
The dspcons command shows which connections are in loopback mode. Specifying an "n" after the channel indicates a near loopback, and an "f" indicates a far loopback. Because addextlp takes the specified connections out of service, use it only when a service disruption is tolerable.
Add External Loop to Connection
addextlp <channel> < n | f >
dellp, dspcons
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
addextlp 5.1 n
Place the device connected to channel 5.1 in near loopback.
alpha TRM YourID:1 IPX 16 8.5 Aug. 16 1997 12:53 PST
Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
N5.1 beta 25.1 Ok 256 7/8 0 L
9.1.100 gamma 8.1.200 Ok fr 0 L
9.2.400 beta 19.2.302 Ok fr 0 L
14.1 gamma 15.1 Ok v 0 L
Last Command: addextlp 5.1 n
Next Command:
| Parameter | Description |
|---|---|
channel | Specifies the channel to loopback in the format slot.port. |
n /f | Specifies whether the loopback is near or far. An "n" specifies near; an "f" specifies far. For a non-DDS port, the near or far modem is placed in loopback, if it supports this function. For a DDS port, the external DDS device is placed in CSU loopback. Local channels must be configured as OCU in order to place them in external loopback. |
The addloclp command places the following types of channels in local loopback mode:
For voice connections, addloclp creates a signal path from a channel or group of channels on an incoming line then back out to the line. External test equipment can test the integrity of the path at the T1 DS0 level. Figure 14-1 shows a local loopback on a voice channel.
For data connections, addloclp creates a signal path from the incoming data port or set of ports back to these same port(s) through the local CDP/CVM, SDP/HDM, or LDP/LDM. External test equipment can then test the integrity of the path. Figure 14-2 illustrates a local loopback on a data connection.
A local loopback can simultaneously exist at both ends of a connection. However, a local loopback and a remote loopback cannot co-exist on a connection. (See the addrmtlp description for more information.)
Prior to executing a loopback, the IPX or IGX node performs signal and code conditioning to remove the connection from service. The loopback remains in place until removed by the dellp command. Only existing connections can be looped back. Use the dspcons command to see which connections are looped back. A flashing right parenthesis ")" or left parenthesis "(" is used in the connections display to indicate a loopback. The direction and location of the parenthesis depends on whether the loopback is local or remote and which end of the connection was used to establish the loopback. A local loopback initiated from the local end of the connection looks like this in the connections display:
Local Channel | Remote Node | Remote Channel |
12.1 | alpha | 15.1 |
A local loopback initiated from the remote end of the connection looks like this:
Local Channel | Remote Node | Remote Channel |
12.1 | alpha | 15.1 |
In frame relay connection loopback mode (DLCI included in command), all packets from the far-end of the connection are dropped. The far-end system software is informed of the loopback. In port loopback mode (port specified without a DLCI), all packets for this port are dropped and each opposite end is informed of the loopback mode. The format slot.port is used in port mode to loop just the port. The data is looped directly in the FRI back card, so no data reaches the MUXBUS or CELLBUS. The format slot.port.DLCI is used in connection (channel) mode to loop a specific channel. Note that this can affect up to 252 connections (channels) in port loopback mode.
Because the addloclp command causes the connection(s) to be removed from service, loopbacks should be used only when a service disruption can be tolerated. Remote loopbacks are established with the addrmtlp command. Both local and remote loopbacks are removed by the dellp command. Loopbacks for data channels can also be initiated by pressing a button on the front of the associated data card.
When a frame relay port or connection is located on a Port Concentrator instead of directly on an FRP or FRM card, the data test path is different. When just the <port> parameter is used, incoming data is looped back out on the Port Concentrator port:
This loop disrupts all frame relay connections on the port that is under test.
When a connection is specified by <port.dlci> parameters, the connection is looped back at the FRM-2 or FRP-2 interface with the IGX or IPX card bus:
As shown, this test verifies the operation of all components from the Port Concentrator to IPX/IGX interface with the FRP-2 or FRM-2 card.
This tests interrupts only the specified connection on the Port Concentrator port.
Add local loopback to connections on a port
addloclp channel
addrmtlp, dellp, dspcons, dspfrport
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
addloclp 14.1
The connections screen appears with connection 14.1 highlighted. The system prompts to confirm the loopback. To confirm it, enter y.
Next Command:
alpha TRM YourID:1 IPX 16 8.5 Aug. 23 1997 11:03 PST
Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
5.1 beta )25.1 Ok 256 7/8 0 L
9.1.100 gamma 8.1.200 Ok fr 0 L
9.1.200 gamma 8.1.300 Ok fr 0 L
9.2.400 beta 19.2.302 Ok fr(Grp) 0 L
14.1 )gamma 15.1 Ok v 0 L
Last Command: addloclp 14.1
Next Command:
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the card containing the port to loop at the local node. |
channel (s) | Specifies the channel or set of channels to loop at the local node. |
port | Where applicable for the connection type, specifies the port. |
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the card containing the port to loop at the local node. |
port | Specifies the local port to loop at the local node. |
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the FRP card containing the port to be looped at the local node. |
port | Specifies the local port to loop at the local node. |
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the FRP card containing the port to loop at the local node |
port | Specifies the local port to loop at the local node. |
DLCI | Specifies the Data Link Connection Identifier (DLCI) number of the channel to loop at the local node. |
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the ATM card containing the port to loop at the local node |
port | Specifies the local port to loop at the local node. |
vpi.vci | The vpi range is 0-7, and the vci range is 1-255. An asterisk (*) indicates a virtual path |
Adds support of a local-remote loopback for testing multi-segment connections in a tiered network. The effect is to instruct the remote node to set up a remote loopback. The addlocrmtlp command must be executed prior to using tstcon and tstdelay for multi-segment connections. For interface shelves, you can execute addlocrmtlp on either the interface shelf (after telnetting to it). After testing is complete, remove the local-remote loop by executing dellp. A parenthesis on the screen shows the loop's endpoint.
Add local-remote loopback in a tiered network
addlocrmtlp <channel(s)>
tstcon, tstdelay, dellp, dspcons, dspfrport
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | BPX, IPX/AF, IPX, IGX |
Lock | Yes |
addlocrmtlp 5.1.3.100
The connections screen appears with the connection highlighted and a prompt for confirmation.
pubsbpx1 TN SuperUser BPX 8.5 July 13 1997 14:41 PDT Local Remote Remote Channel NodeName Channel State Type Compress Code COS 5.1.3.100 ( pubsbpx3 7.1.2.49 Ok aftr 0 This Command: addlocrmtlp 5.1.3.100 Loopback these connections (y/n)?
| Parameter | Description |
|---|---|
channels(s) | The connection endpoint on the local node. |
The addrmtlp command places the following types of channels in remote loopback mode:
For voice connections, addrmtlp loops the information stream from the designated channel or group of channels on an incoming circuit line across the network and loops it back to the circuit line by way of the remote CDP or CVM. External test equipment can then test the integrity of the path at the T1 DS0 level. The following illustrates a remote loopback on a voice channel.
l
For data connections, addrmtlp transfers the information stream from the designated channels through the network and loops it back to the data port(s) through a remote SDP, HDM, LDM, or LDP. External test equipment can then test the integrity of the path. The following illustrates a data connection remote loopback.
Prior to executing the loopback, the IPX or IGX node applies signalling template bit patterns to the A, B, C, and D signalling bits at the remote end to remove the connection from service. The loopback remains in place until removed by the dellp command. Only existing connections (those that have been entered with the add-on command) can be looped back. You cannot establish a remote loopback on a connection that is already looped back, either locally or remotely. (See the addloclp command for more information on local loopbacks.)
Use the dspcons command to see which connections are looped back. A flashing left parenthesis "(" or right parenthesis ")" is used in the connections display to indicate a loopback. The direction and location of the parenthesis depends on whether the loopback is local or remote and which end of the connection was used to establish the loopback. A remote loopback initiated from the local end of the connection looks like this:
Local Channel | Remote Channel | Remote Node |
3.2 | alpha | 12.1 |
A remote loopback initiated from the remote end of the connection looks like this:
Local Channel | Remote Node | Remote Channel |
3.2 | alpha | 12.1 |
For remote loopback of frame relay connections, note that in remote loopback mode, if the transmit minimum bandwidth exceeds the receive minimum bandwidth, then loopback data may be dropped. For this reason, the connection speeds will be checked and the user will receive the following message if there is a problem:
Because the addrmtlp command causes the connection to be removed from service, loopbacks should be used only when a service disruption can be tolerated. Local loopbacks are established with the addloclp command. Both local and remote loopbacks are removed by the dellp command. Loopbacks for data channels can also be initiated by pressing a push-button on the front of the associated data card.
For frame relay remote loops, DLCI MUST be specified; entering only port number only generates an error message.
Unlike local loopbacks, remote loopbacks are not supported for frame relay ports; connections must be specified. Data incoming on the frame relay port is looped at the remote end FRM-2 or FRP-2 card.
As shown, this test verifies the operation of IPX/IGX network components up to the interface with the remote-end FRM-2 or FRP-2. This test interrupts data traffic for only the connection specified by DLCI.
If a port concentrator is attached to the FRM-2 or FRP-2, the only difference in the loop is that the port specified to loop data is on the Port Concentrator:
Add remote loopback to connections
addrmtlp (see parameter tables)
addloclp, dellp, dspcons
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
addrmtlp 5.1
The connections screen appears with connection 5.1 highlighted. The system prompts to confirm the loopback. To confirm it, enter y. A flashing parenthesis ")" appears in the "Remote Channel" column of the connection to indicate that the connection is looped back.
alpha TRM YourID:1 IPX 16 8.5 Aug. 16 1997 12:57 PST
Local Remote Remote Route
Channel NodeName Channel State Type Compression Code Avoid COS O
5.1 beta )25.1 Ok 256 7/8 0 L
9.1.100 gamma 8.1.200 Ok fr 0 L
9.2.400 beta 19.2.302 Ok fr 0 L
14.1 gamma 15.1 Ok v 0 L
Last Command: addrmtlp 5.1
Next Command:
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the card containing the port to loop at the local node. |
channel (s) | Specifies the channel or set of channels to loop at the local node. |
port | Where applicable for the connection type, specifies the port. |
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the card containing the port to loop at the local node. |
port | Specifies the local port to loop at the local node. |
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the FRP card containing the port to loop at the local node |
port | Specifies the local port to loop at the local node. |
DLCI | Specifies the Data Link Connection Identifier (DLCI) number of the channel to loop at the local node. |
| Parameter | Description |
|---|---|
slot | Specifies the slot number of the card containing the port to loop at the local node. |
channel (s) | Specifies the channel or set of channels to loop at the local node. |
port | Where applicable for the connection type, specifies the port. |
vpi.vci | Specifies vpi/vci. |
Clears the channel utilization statistics for either all frame relay channels or a specified frame relay channel. Statistics generated within the last one minute are not cleared.
Clear channel statistics
clrchstats <channel | *>
dspchstats
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
clrchstats 9.2.400
Clear the statistics of channel 9.2.40.
alpha TRM YourID:1 IPX 16 8.5 Aug. 16 1997 13:24 PST
Channel Statistics for 9.2.400 Cleared: Aug. 16 1997 13:23
MIR: 9.6 kbps Collection Time: 0 day(s) 00:02:42 Corrupted: NO
Frames Avg Size Avg Util Packets Avg
(bytes) (fps) (%) (pps)
From Port: 0 0 0 0
To Network: 0 0 0 0 0 0
Discarded: 0 0 0 0
From Network: 0 0 0 0 0 0
To Port: 0 0 0 0
Discarded: 0 0 0 0 0 0
ECN Stats: Avg Rx VC Q: 0 ForeSight RTD --
Min-Pk bytes rcvd: 0 FECN Frames: 0 FECN Ratio (%) 0
Minutes Congested: 0 BECN Frames: 0 BECN Ratio (%) 0
This Command: clrchstats 9.2.400
OK to clear (y/n)?
| Parameter | Description |
|---|---|
channel | Specifies the frame relay channel in the format slot.port.DLCI. A "*" specifies all channels. |
Clears the alarm condition attached to a clock source, either circuit line or trunk. The clock test runs continuously in a node, comparing the frequency of the node's clock source to a reference on the NPC/BCC/CC/control card. If a clock source is found to be outside preset frequency limits, it is declared defective and another clock source is selected. In order for the node to return to the original clock source, the alarm must be cleared using the clrclkalm command. The alarm may be either a "Bad Clock Source" or "Bad Clock Path" alarm.
Clear clock alarm
clrclkalm <line type> <line number>
cnfclksrc, dspclksrcs, dspclns, dspcurclk, dsptrks
Privilege | 1-5 |
Jobs | No |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
clrclkalm c 12
Clear a clock alarm on circuit line 12
clrclkalm p 12
Clear a clock alarm on packet line 12
| Parameter | Description |
|---|---|
c/p | Specifies the type of line. A "c" is entered for a circuit line, and a "p" is entered for a trunk. |
line number | Specifies the number of the circuit or trunk. |
Clears the alarms associated with a circuit line. Since the statistical alarms associated with a circuit line have associated integration times, they can keep a major or minor alarm active for some time after the cause has been rectified. This command allows these alarms to be cleared, allowing any new alarms to be quickly identified. The clrclnalm command can only clear alarms caused by the collection of statistical data. Alarms caused by a network failure cannot be cleared. For example, an alarm caused by a collection of bipolar errors can be cleared, but an alarm caused by a card failure cannot.
Clear circuit line alarm
clrclnalm <line_number> <fail_type>
dspclns, dspclnerrs
Privilege | 1-5 |
Jobs | No |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
clrclnalm 14 2
Clear the minor alarm caused by frame slips on circuit line 14.
alpha TRM YourID:1 IPX 16 8.5 Aug. 16 1997 13:10 PST
Line Alarm Configuration
Minor Major
Violation Rate Alarm Time Clear Rate Alarm Time Clear
1) Bpv 10E-7 10 min 3 min 10E-3 10 sec 10 sec
2) Fs .01% 10 min 3 min .1% 10 sec 10 sec
3) Oof .0001% 10 min 3 min .01% 10 sec 10 sec
4) Vpd 2% 5 min 3 min 5% 60 sec 10 sec
5) Tsdp .01% 5 min 3 min .1% 60 sec 10 sec
6) Ntsdp .01% 5 min 3 min .1% 60 sec 10 sec
7) Pkterr .01% 10 min 3 min .1% 125 sec 10 sec
8) Los .0001% 10 min 3 min .01% 10 sec 10 sec
This Command: clrclnalm 14 2
Continue?
| Parameter | Description |
|---|---|
line number | Specifies the number of the line. |
failure type | Specifies the type of alarm to clear. |
Clears the errors associated with a circuit line. Since the statistical alarms associated with a circuit line have associated integration times, they can keep a major or minor alarm active for some time after the cause has been rectified. This command allows these alarms to be cleared, allowing any new alarms to be quickly identified. The clrclnerrs command can clear only those alarms that the collection of statistical data has caused. Alarms caused by a network failure cannot be cleared by clrclnerrs.
Clear circuit line errors
clrclnerrs [<line_number>]
dspclnerrs, prtclnerrs
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
clrclnerrs
Clear circuit line error counts. In response to the prompt, enter "y" to reset all circuit line error counts to "0."
alpha TRM YourID:1 IPX 16 8.5 Aug. 16 1997 13:12 PST
Total Errors
From Code Frame Out of Loss of Frame CRC Out of
CLN Errors Slips Frames Signal BitErrs Errors MFrames AIS-16
14 0 0 0 - 0 - - -
Last Command: clrclnerrs
Next Command:
Clears the alarms associated with a circuit line. Since the statistical alarms associated with a line have associated integration times, they can keep a major or minor alarm active for some time after the cause has been rectified. This command allows these alarms to be cleared, allowing any new alarms to be quickly identified.
The clrclnalm command can only clear alarms caused by the collection of statistical data. Alarms caused by a network failure cannot be cleared. For example, an alarm caused by a collection of bipolar errors can be cleared, but an alarm caused by a card failure cannot.
Clear circuit line alarm
clrclnalm <line_number> <fail_type>
dsplns, dsplnerrs
Privilege | 1-5 |
Jobs | No |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
clrlnalm 14 2
Clear the minor alarm caused by frame slips on 14. The 2 indicates frame slips.
alpha TRM YourID:1 IPX 16 8.5 Aug. 16 1997 13:10 PST
Line Alarm Configuration
Minor Major
Violation Rate Alarm Time Clear Rate Alarm Time Clear
1) Bpv 10E-7 10 min 3 min 10E-3 10 sec 10 sec
2) Fs .01% 10 min 3 min .1% 10 sec 10 sec
3) Oof .0001% 10 min 3 min .01% 10 sec 10 sec
4) Vpd 2% 5 min 3 min 5% 60 sec 10 sec
5) Tsdp .01% 5 min 3 min .1% 60 sec 10 sec
6) Ntsdp .01% 5 min 3 min .1% 60 sec 10 sec
7) Pkterr .01% 10 min 3 min .1% 125 sec 10 sec
8) Los .0001% 10 min 3 min .01% 10 sec 10 sec
This Command: clrclnalm 14 2
Continue?
| Parameter | Description |
|---|---|
line number | Specifies the number of the line. |
failure type | Specifies the type of alarm to clear. |
Clears high water marks for fail handler event queues.
Clear event queues from the fail handler
clreventq
dspeventq
Privilege | 1-6 |
Jobs | No |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
clreventq
Clear the fail handler event queue.
sw151 TN SuperUser IGX 16 8.5 Sep. 12 1997 19:18 GMT QUEUE LENGTH THROTTLING NUM NAMES MAX HIGH CURRENT POINT 1 Fail_Xid 26 1 7000 2 Fail_ Q 25 0 3 Mt_Sv_Q[0] 300 9 0 270 4 sv_mt_bufq 9 0 This Command: clreventq OK to clear HIGH counts(y/n)?
Clears accumulated line error counts for all lines on a node.
Clear line errors
clrlnerrs [<line_number>]
dsplnerrs, prtlnerrs
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
clrlnerrs
Clear the line error counts. In response to the prompt enter "y" to reset all line error counts to "0."
alpha TRM YourID:1 IPX 16 8.5 Aug. 16 1997 13:12 PST
Total Errors
From Code Frame Out of Loss of Frame CRC Out of
CLN Errors Slips Frames Signal BitErrs Errors MFrames AIS-16
14 0 0 0 - 0 - - -
Last Command: clrclnerrs
Next Command:
Clears the event log. When the log is cleared, one entry remains, "Info Log Cleared". Before the event log is cleared, a prompts you to confirm. See the dsplog command for more information on the event log.
Clear event log
clrlog
dsplog
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
clrlog
Clear the event log. When the log is cleared, one entry remains, "Info Log Cleared." Enter "y" to confirm.
sw151 TN SuperUser IGX 16 8.5 Sep. 12 1997 19:19 GMT Most recent log entries (most recent at top) Class Description Date Time Info User SuperUser logged out (Local) 09/12/96 18:18:57 Major LN 5.6 Loss of Sig (RED) 09/12/96 18:12:22 Info User SuperUser logged out (Local) 09/12/96 18:11:17 Info Clock switch to oscillator of SCC 09/12/96 18:10:46 Clear LN 5.6 OK 09/12/96 18:05:11 Minor LN 5.6 Out of Multi-Frames 09/12/96 18:03:27 Info Clock switch to LINE 5.6 09/12/96 18:03:12 Clear LN 5.6 OK 09/12/96 18:02:42 Info Clock switch to oscillator of SCC 09/12/96 17:59:24 Major LN 5.6 Loss of Sig (RED) 09/12/96 17:59:24 Info Clock switch to LINE 5.6 09/12/96 17:59:20 Clear LN 5.6 OK 09/12/96 17:59:20 Major LN 5.6 Loss of Sig (RED) 09/12/96 17:58:51 This Command: clrlog OK to clear (y/n)?
Clears the minor alarm due to an alarm message received at an alarm collection port.
Clear message alarm
clrmsgalm
dspalms, dsplog
Privilege | 1-5 |
Jobs | No |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
clrmsgalm
Clear a minor alarm due to an alarm message.
alpha TRM YourID:1 IPX 16 8.5 Aug. 23 1997 10:59 PST
Last Command: clrmsgalm
No message alarm set
Next Command:
Clears the statistics for any port on an FRP. This includes the data byte count in the transmit and receive directions and error counts associated with the port. Statistical accumulation then resumes for that port.
Statistics collecting takes place once per minute, so clrportstats may not clear statistics that are less than one minute old.
Clear port statistics
clrportstats <port | *>
dspportstats
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
clrportstats 9.1
Clear the port statistics for port 1 on an FRP card in slot 9. Type "y" to confirm.
alpha TRM YourID:1 IPX 16 8.5 Aug. 23 1997 10:57 PST
Port Statistics for 9.1 Cleared: Aug. 11 1997 15:32
Port Speed: 256 kbps Collection Time: 11 day(s) 19:22:09 Corrupted: YES
Bytes Average (kbps) Util (%) Frames
From Port: 0 0 0 0
To Port: 0 0 0 0
Frame Errors LMI Receive Protocol Stats Misc Statistics
Invalid CRC 0 Status Enq Rcvd 0 Avg Tx Port Q 0
Invalid Alignment 0 Status Xmit 0 FECN Frames 0
Invalid Frm Length 0 Asynch Xmit 0 Ratio (%) 0
Invalid Frm Format 0 Seq # Mismatches 0 BECN Frames 0
Unknown DLCIs 0 Timeouts 0 Ratio (%) 0
Last Unknown DLCI 0 Invalid Req 0 Rsrc Overflow 0
Sig Protocol: None DE Frms Dropd 0
This Command: clrportstats 9.1
OK to clear port statistics (y/n)?
Clears the alarm messages associated with the alarms displayed for the Display Slot Alarms command. Alarm messages are cleared for the specified slot only. These counters should be cleared before beginning any monitoring session. This command prompts the user with a "OK to Clear?" message before actually clearing the counters. Use dspslotalms to observe the slot alarms. Refer to the dspslotalms command for a description of the counters cleared by the clrslotalms command.
Clear slot alarms
clrslotalms parameters
dspslotalms
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | BPX |
Lock | Yes |
clrslotalms 3
Clear alarm on slot 3.
| Parameter | Description |
|---|---|
slot number | Specifies shelf slot in the BPX node. |
Clears the counters for the error counts displayed for the Display Slot Errors command. Counters are cleared for the specified slot only. These counters should be cleared before beginning any monitoring session. This command prompts the user with a "OK to Clear?" message before actually clearing the counters. Use dspsloterrs to observe the slot errors. Refer to the dspsloterrs command for a description of the counters cleared by the clrsloterrs command.
Clear slot errors
clrsloterrs <slot number | *>
dspsloterrs
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
clrsloterrs 3
Clear the slot errors in slot 3.
| Parameter | Description |
|---|---|
slot number | Specifies the shelf slot in the node. |
Clears statistical alarms associated with either a physical or virtual trunk. Since the statistical alarms associated with a trunk have associated integration times, they can keep a major or minor alarm active for some time after the cause has been rectified. The clrtrkalm allows these alarms to be cleared, allowing any new alarms to be quickly identified.
The clrtrkalm command can only clear alarms caused by the collection of statistical data. Alarms caused by a network failure cannot be cleared. For example, an alarm caused by a collection of bipolar errors can be cleared, but an alarm caused by a card failure cannot.
Clear trunk alarm
clrtrkalm <trunk number> <failure type>
dsptrks, dsptrkerrs
Privilege | 1-5 |
Jobs | No |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
clrtrkalm
Statistical trunk alarms are cleared.
beta TRM YourID:1 IPX 32 8.5 Aug. 15 1997 15:15 MST
PLN Type Current Line Alarm Status Other End
7 E1/32 Clear - Line OK alpha.10
9 T1/24 Clear - Line OK gamma.10
13 T1/24 Clear - Line OK alpha.14
15 T1/24 Clear - Line OK gamma.15
20 T3/3 Clear - ATM Missing -
Last Command: clrtrkalm
Next Command:
clrtrkalm 7 4
Clear the minor alarm type 4 caused by dropped voice packets on trunk 7. Respond to the "Continue?" prompt with "y" (for yes) to clear and display the remaining alarms.
beta TRM YourID:1 IPX 32 8.5 Aug. 15 1997 15:15 MST
PLN Type Current Line Alarm Status Other End
7 E1/32 Clear - Line OK alpha.10
9 T1/24 Clear - Line OK gamma.10
13 T1/24 Clear - Line OK alpha.14
15 T1/24 Clear - Line OK gamma.15
20 T3/3 Clear - ATM Missing -
Last Command: clrtrkalm 7 4
Next Command:
| Parameter | Description |
|---|---|
trunk number | Specifies the trunk. Note that, for virtual trunks, no virtual trunk parameter is required—just slot.port. The format is either slot (for a single-trunk card) or slot.port. |
failure type | Specifies the type of alarm to clear. |
Clears the statistical error counters at the node for the specified physical or virtual trunk. You should do this before you begin any monitoring session and periodically thereafter to determine exactly when a trunk problem begins. Use dsptrkerrs to observe errors without clearing counters.
Clear trunk errors
clrtrkerrs <trunk_number | *>
dsptrkerrs, prttrkerrs
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
clrtkerrs *
Clear all trunk errors.
pubsbpx1 TN SuperUser BPX 15 8.5 Sep. 12 1997 19:37 PST
Total Errors
Code Rx Cell Out of Loss of Frame HCS Tx Cell Cell Cell
TRK Errors Dropped Frames Signal BitErrs Errors Dropped Errors Oofs
1.1 0 0 0 0 - 0 0 - -
1.2 0 0 0 0 - 0 0 - -
This Command: clrtrkerrs *
Clears errors on all trunks. Continue (y/n)?
| Parameter | Description |
|---|---|
trunk number | Specifies the trunk counter to clear. |
Clears the node counters used for the Display Trunk Statistics. Counters are cleared for a physical or virtual trunk. These counters should be cleared before beginning any monitoring session. This is similar to the clrtrkerrs command for errors. This command prompts the user with a "OK to Clear?" message before actually clearing the counters. Use dsptrkstats to observe the trunk statistics. See the dsptrkstats command for a description of the counters cleared by the clrtrkstats command.
Clear trunk statistics
clrtrkstats <trunk number>
dsptrkstats
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | BPX |
Lock | Yes |
clrtrkstats
Clear the statistics on trunk 3.
Parameter | Description |
|---|---|
trunk number | Specifies the trunk. Note that, for virtual trunks, no virtual trunk parameter is required—just slot.port. The format is either slot (for a single-trunk card) or slot.port. |
Selects the active System Bus. It should only be necessary to use this command when a problem is suspected with the currently active System Bus. As a safeguard against bus failure, each IPX node is equipped with redundant System Buses, Bus A and Bus B. Either bus can be configured as the active bus and the remaining bus is reserved as standby. Use the dspbuses command to display the current bus configuration when configuring the buses with the cnfbus command.
Configure active bus
cnfbus <a/b/t>
dspbuses
Privilege | 1-3 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX |
Lock |
|
cnfbus t
Configure the system bus to toggle.
pubsigx1 TN SuperUser IGX 32 8.5 Sep. 12 1997 19:42 GMT
Bus Info
Bus Bandwidth usage in Fastpackets/second (Snapshot)
Allocated = 20000 ( 2%)
Available = 1148000 (98%)
-----------
Bus A: Standby - OK
Bus B: Active - OK
Last Command: cnfbus t
Next Command:
| Parameter | Description |
|---|---|
a | Select Bus A as the active bus. |
b | Select Bus B as the active bus. |
t | Toggles between buses. It changes the standby bus to the active bus and the active bus to the standby bus |
Sets the trunk and line alarm values for failures that are statistical in nature. Statistical alarms are declared by the switch software when a cards supporting these trunks or lines report too many errors. The switch declares an alarm if the detected error rate equals the cnflnalm parameter error rate for the period of time designated by the alarm time parameter. Error rates that exceed the specified error rate cause an alarm in a proportionately shorter period of time. An alarm is cleared when the error rate remains below the rate specified by error rate for a period of time designated by the clear time.
You can configure the thresholds for alarms caused by the collection of statistics but not for the alarms caused by a network failure. For example, you can configure the threshold for an alarm caused by a collection of bipolar errors, but you cannot configure an alarm caused by a card failure.
Six parameters exist for each failure type—three for minor alarms and three for major alarms. When configuring any item for a minor or major alarm, you must enter a value. You can enter a new value or enter the current value.
Table 14-23 describes the parameters for cnflnalm. For each failure type listed in Table 14-23, the alarm classes, the possible error rate options, and default alarm times and clear times are listed in Table 14-24. Table 14-25 describes the error rate options listed in Table 14-24.
Configure line alarms
cnflnalm <fail_type> <alarm_class> <rate> <alarm_time> <clear_time>
clrclnalm, clrtrkalm, dspclnerrs, dsplnalmcnf, dsptrkerrs
Privilege | 1-3 |
Jobs | No |
Log | Yes |
Node | IPX, IGX |
Lock | Yes |
cnflnalm 27 1 4 4 3
Set Alarm Type 27, the Minor alarm time threshold, to 4 minutes. In this example, the cnflnalm command is followed by the alarm type (27), the alarm minor or major (1 for minor, 2 for major), the current rate (which is the default of 0.001%, (which is a 4), the new value for Alarm Time of 4 minutes (which is a "4" entry), and the existing Alarm Clear time of "3."
pubsigx1 TN SuperUser IGX 32 8.5 Aug. 20 1997 17:19 GMT
Line Alarm Configuration
Minor Major
Violation Rate Alarm Time Clear Rate Alarm Time Clear
25) Rxbdapd .001% 5 min 3 min .1% 60 sec 10 sec
26) Rxbdbpd .001% 5 min 3 min .1% 60 sec 10 sec
27) Rxhppd .001% 4 min 3 min .1% 60 sec 10 sec
28) Atmhec .1% 10 min 3 min 1% 120 sec 10 sec
29) FSyncErr .01% 10 min 3 min .1% 200 sec 10 sec
30) Rxspdm .01% 4 min 2 min .001% 30 sec 5 sec
Last Command: cnflnalm 27 1 4 4 3
Next Command:
| Parameter | Description |
|---|---|
Failure type | Specifies the failure type. The list that follows gives the number for each failure type. (Items with an asterisk pertain to ATM only.) 1. Bpv—Bipolar violations 2. Fs —Frame slip 3. oof—Out of frame 4. Vpd -Voice packets dropped (TX) 5. Tspd—Time stamped packets dropped (TX) 6. Ntspd—Non-time stamped packets dropped 7. Pkterr—Packet error 8. Los—Loss of signal 9. Fer—Frame error 10. CRC—Cyclic Redundancy Check 11. Pkoof—Packet out of frame 12. Oom—Out of multi-frame 13. Ais16—Alarm information signal—E1/E3 Only 14. Bdapd—Bursty data A packets dropped 15. Bdbpd—Bursty data B packets dropped 16. Badclk—Bad clock 17. Pccpd—PCC packets dropped 18. * Lcv—Line code violations 19. * Pcv1—P-bit parity code violations 20. * Pcvp—C-bit parity code violations 21. * Bcv—PLCP BIP-8 code violations 22. * Rxvpd—Receive voice packets dropped 23. * Rxtspd—Receive time stamped packets dropped 24. * Rxntspd—Receive non-time stamped packets dropped 25. * Rxbdapd—Receive bursty data A packets dropped 26. * Rxbdbpd—Receive bursty data B packets dropped 27. * Rxhppd—Receive high priority packets dropped 28. * Atmhec—Cell header HEC errors 29. * Plcpoof—PLCP out of frame 30. * 30—Rxspdm: Receive spacer packets dropped |
alarm class | Specifies the class of alarm to be configured for the specified alarm type. Valid alarm classes are:
|
rates | Specifies the error rate at which the error must occur before an alarm is declared. The choices for error rates vary depending on the failure type and the alarm class. The choices are called out as Error Rate Options. The default error rates are indicated. With the exception of a Vpd (voice packets dropped) failure, you enter the number corresponding to the error rate. For Vpd (voice packets dropped) failures, you enter a percentage for the dropped packet rate in the range 1%-10%. See Table 14-24 for failure type and Table 14-25 for error rate options. |
alarm time | Specifies the time that a condition must exceed a threshold before an alarm is declared. For minor alarms, the alarm time has a range of 3-10 minutes. For major alarms, the alarm time has a range of 10-250 seconds. |
clear time | Specifies the time that the condition must exceed the selected threshold before the alarm is cleared. For minor alarms, the clear time has a range of 3-10 minutes. For major alarms, the clear time has a range of 10-250 seconds. |
| Failure Type | Alarm Class | Error Rate Options * | Alarm Time | Clear Time |
|---|---|---|---|---|
| | Option B | | |
| | Option A | | |
3-Oof | 1-minor | 1: 1% 2: 0.1% 3: 0.01% 4: 0.001% 5: 0.0001% (Def.) | 10 Minutes | 3 Minutes |
| 2-major | 1: 1% 4: 0.001% | 10 Seconds | 10 Seconds |
4- Vpd | 1-minor | Any dropped packet | 5 Minutes | 3 Minutes |
| | Option A | | |
| | Option A | | |
7- Pkterr | 1-minor | Any error count | 10 Minutes | 3 Minutes |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option B | | |
| | Option B | | |
| | Option B | | |
| | Option B | | |
| | 1-10% | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| | Option A | | |
| Error Rate Options | ||
|---|---|---|
| Option | Alarm Class | Error Rate |
A | 1 - minor | 1 - 1% 2 -.1% 3 -.01% 4 -.001% 5 -.0001% |
2 - major | 1 - 1% 2 -.1% 3 -.01% | |
B | 1 - minor | 1 - 10E-4 2 - 10E-5 3 - 10E-6 4 - 10E-7 5 - 10E-8 |
2 - major | 1 - 10E-2 2 - 10E-3 3 - 10E-4 4 - 10E-5 5 - 10E-6 | |
Configures the alarm parameters for the various card types. Upon command entry, the system displays a screen with a choice of 8 card-alarm types. It then displays "Enter Type" and waits for a number in the range 1-12. Upon entry of the alarm type, the system displays the error rates of the selected type.
Configure slot alarm parameters
cnfslotalm <fail_type> <alarm_class> <rate> <alarm_time> <clear_time>
dspslotalms
Privilege | 1 |
Jobs | Yes |
Log | Yes |
Node | BPX |
Lock | Yes |
cnfslotalm 10
Configure the alarm parameters.
pubsbpx1 TN SuperUser BPX 15 8.5 Sep. 12 1997 19:43 PST Slot Alarm Types 1) Standby PRBS Errors 11) Poll Clk Errors 2) Rx Invalid Port Errs 12) CK 192 Errors 3) PollA Parity Errors 4) PollB Parity Errors 5) Bad Grant Errors 6) Tx Bip 16 Errors 7) Rx Bip 16 Errors 8) Bframe parity Errors 9) SIU phase Errors 10) Rx FIFO Sync Errors This Command: cnfslotalm Enter Type:
The screen display after selecting alarm type 10:
pubsbpx1 TN SuperUser BPX 15 8.5 Sep. 12 1997 19:47 PST
Slot Alarm Configuration
Minor Major
Violation Rate Alarm Time Clear Rate Alarm Time Clear
1) SPRBS .1% 10 min 3 min 1% 100 sec 100 sec
2) InvP .1% 10 min 3 min 1% 100 sec 100 sec
3) PollA .1% 10 min 3 min 1% 100 sec 100 sec
4) PollB .1% 10 min 3 min 1% 100 sec 100 sec
5) BGE .1% 10 min 3 min 1% 100 sec 100 sec
6) TBip .1% 10 min 3 min 1% 100 sec 100 sec
7) RBip .1% 10 min 3 min 1% 100 sec 100 sec
8) Bfrm .1% 10 min 3 min 1% 100 sec 100 sec
9) SIU .1% 10 min 3 min 1% 100 sec 100 sec
10) RFifo .1% 10 min 3 min 1% 100 sec 100 sec
Last Command: cnfslotalm 10
Next Command:
Configures trunk alarm reporting. When trunks are upped and added to the network, alarm reporting automatically is enabled. The cnftrkalm command lets you disable alarms on a trunk. Disabling alarms may be useful, for example, for trunks that are connected to the node but not yet in service or if the node is experiencing occasional bursts of errors but is still operational. (When the alarms are enabled, they cause an alarm output from the DTI Group Alarm Connector (if present) and an alarm indication on the StrataView Plus terminal.)
Configure trunk alarms
cnftrkalm <trunk number> <e | d>
dspalms, dsptrks
Privilege | 1-5 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
cnftrkalm 14 d
Disable trunk alarms on trunk 14, which has a major alarm. After using this command to disable the alarms, the only indication that the alarms have been disabled is to observe the dspalms screen while a trunk alarm exists. The dspalms screen displays the word "disabled" after "PLN Alarms." Therefore, when you disable trunk alarms, be sure to note this action so you remember to enable alarms after the cause of the trunk failure has been corrected.
alpha TRM YourID:1 IPX 16 8.5 Aug. 16 1997 13:04 PST
From Type Current Line Alarm Status Other End
14 T1/24 Major - Tx NTS Packets Dropped beta.13
Last Command: cnftrkalm 14 d
Next Command:
cnftrkalm 14 e
Enable the alarms after they have been disabled.
| Parameter | Description |
|---|---|
e | d | Enable or disable trunk alarms. |
Deletes an external, local, remote, or local-remote (tiered nets) loopback form the designated channel, set of channels, or port. After the loopback is deleted, any conditioning applied during the loopback process is removed and service is restored. Local loopbacks are added with the addloclp command, and remote loopbacks are added with the addrmtlp command. External loopbacks are added with the addextlp command. A local loop can be deleted only from the node that added it. However, a remote loop can be deleted from the node at either end of the connection. Local-remote loopbacks are added with the addlocrmtlp command. Note that with local-remote loopbacks, execution of dellp is mandatory after testing is complete, otherwise continuity errors will follow.
Delete loopback from connections or a port
dellp <channel(s)>
addextlp, addloclp, addlocrmtlp, addrmtlp
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
dellp 5.1.121
Delete the loopback on channel 5.1.121. The connections screen appears with connection 5.1.121 highlighted. (The highlighting is not visible in the screen example, but the loop symbols indicates loopback.) The display prompts you to confirm deletion of the loopback. To confirm, enter "y."
pubsipx1 TN SuperUser IPX 16 8.5.00 May 29 1997 19:16 PDT
Local Remote Remote
Channel NodeName Channel State Type Compress Code COS
5.1.121 )pubsipx1 8.33.133 Ok atfr
5.1.122 pubsipx1 8.34.134 Ok atfr
5.2.111 pubsipx1 8.45.155 Ok atfr
5.2.112 pubsipx1 8.45.156 Ok atfr
8.33.133 pubsipx1 (5.1.121 Ok atfr
8.34.134 pubsipx1 5.1.122 Ok atfr
8.45.155 pubsipx1 5.2.111 Ok atfr
8.45.156 pubsipx1 5.2.112 Ok atfr
This Command: dellp 5.1.121
Delete these loopbacks (y/n)?
| Parameter | Description |
|---|---|
channels | Specifies the channel or set of channels whose loopback is to be deleted. The format for channel depends on the type of connection, as follows: Voice connection: slot.channel |
Downs (or deactivates) a card. When you down a card, it is no longer available as a node resource. You should down a card before you remove it from a card cage. Before it actually downs an active card, the node determines if a standby card is available. If no standby card is present, the node gives you an opportunity to abort the command. If a standby card of the same type is available and you execute dncd, the standby card is activated. If no standby card is available and you execute the command, a major alarm results. To activate a downed card, use the upcd command.
You cannot down a control card (NPC, NPM, or BCC). Use switchcc for control cards.
Down card
dncd <slot number>
dspcds, resetcd, upcd
Privilege | 1-3 |
Jobs | Yes |
Log | Yes |
Node | IPX, IGX, BPX |
Lock | Yes |
dncd 9
Down card 9.
| Parameter | Description |
|---|---|
slot number | Specifies the slot number of the card to be downed. |
Displays major and minor alarms throughout the network and more specific alarms at the local node. The dspalms command displays the following information:
Trunk alarms are differentiated between those trunks that are disabled and trunks that are not disabled. For more details on each type of alarm, use the "display" command associated with each failed item. Table 14-29 shows the display commands that shows error information.
| Command | Description |
|---|---|
dspcds | Displays cards in the node, with "F" for failures. |
dspclns | Displays circuit lines. |
dspcons | Displays connections. |
dsplog | Displays events affecting the node. |
dspnds | Displays unreachable nodes within a network. |
dspnw | Displays the network topology and includes alarm status of each node in the network. |
dsptrks | Displays trunks. |
dsppwr | Displays power supply status and internal temperature. |
Display current node alarms
dspalms
dspcds, dspclns, dspcons, dsplog, dspnw, dsptrks, dsppwr
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | IPX, IGX, BPX |
Lock | No |
dspalms
See a summary of all alarms affecting the node.
sw181 TN SuperUser BPX 15 8.5 Oct. 2 1997 12:26 GMT
Alarm summary (Configured alarm slots: None)
Connections Failed: None
Groups Failed: None
TRK Alarms: None
Line Alarms: None
Cards Failed: None
Slots Alarmed: None
Missing Cards: 1
Remote Node Alarms: 2 Minors
Interface Shelf Alarms: None
ASM Alarms: None
Last Command: dspalms
Next Command:
dspalms
The current alarms on a BPX.
sw53 TN SuperUser BPX 15 8.5 July 21 1997 15:18 GMT
Alarm summary (Configured alarm slots: None)
Connections Failed: 100
Groups Failed: None
TRK Alarms: None
Line Alarms: None
Cards Failed: None
Slots Alarmed: None
Missing Cards: None
Remote Node Alarms: 1 Unreachable, 5 Majors, 5 Minors
Interface Shelf Alarms: 2 Unreachables, 2 Minors
ASM Alarms: None
Last Command: dspalms
Next Command:
SW MAJOR ALARM
Shows the current state of all inputs from user equipment to the node the state of all outputs from the node to the user equipment. The display is real-time and updated at a user-specified interval. The display refreshes at the designated interval until the Delete key is pressed or until it times out. See the cnfict description for information on configuring data interfaces. When used with Frame Relay T1/E1 applications, dspbob displays the message "This FRP does not support V.35 ports."
If an FRM-2 or FRP-2 card connects to a Port Concentrator Shelf (PCS), up to 44 ports can be specified with the port parameter. In this case, dspbob displays the signal status for ports on the PCS. The PCS relays any changes in signal states to the FRM-2 or FRP-2, so a slight delay occurs when signals are updated.
When used for PCS ports, dspbob has an optional parameter of measuring port clock speed. Selection of this parameter temporarily interrupts all traffic on the logical port. The events that take place upon input of this parameter are:
1. The port is disabled.
2. Two invalid frames are timed as they go out the port.
3. The port is reactivated.
Display breakout box
dspbob <port> [interval] [(measure clock speed) y | n ]
cnfict, dspcon, dspict
Privilege | 1-6 |
Jo |