[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Monitoring Interfaces
To display statistics for channelized SONET and
SDH interfaces, use the show controllers sonet command. The following section describes
some of the options for the command and shows some sample displays.
From User Exec mode, use the following show commands to monitor and display the T3, T1/E1,
and HDLC serial data channel information:
- Display E1 or T1 statistics for E1 or T1 over a VT.
- host1#show controllers sonet 2/0 e1
- Display T3 statistics.
- host1#show controllers sonet 2/1 ds3
- Display statistics for the section, line, path, and tributary
layers.
- host1#show controllers sonet 2/1 section
- Display the configuration for channelized SONET and SDH
interfaces.
- host1#show controllers sonet 2/0 configuration
- Display statistics for serial interfaces.
- host1#show interfaces serial 2/0:1/1/1/1/1
Setting a Baseline
You can set statistics baselines for serial interfaces,
subinterfaces, and circuits using the baseline interface
serial command. You can also set statistics baselines
for the section, line, and path layers using the baseline
interface sonet command. Use the delta options with
the show commands to display statistics
with the baseline subtracted.
Output Filtering
You can use the output filtering feature of the show command to include or exclude lines of output
based on a text string you specify. See Command Line Interface in JUNOSe System Basics Configuration Guide, for details.
baseline interface serial
- Use to set a statistics baseline for serial interfaces.
- The router implements the baseline by reading and storing
the statistics at the time the baseline is set and then subtracting
this baseline whenever baseline-relative statistics are retrieved.
- Use the delta keyword with the show interfaces
serial command to view the baseline statistics.
- Example
- host1#baseline interface serial 2/0:1/1
- There is no no version.
- See baseline interface.
baseline line interface sonet
- Use to set a statistics baseline for the SONET/SDH line
layer.
- The router implements the baseline by reading and storing
the MIB statistics at the time the baseline is set and then subtracting
this baseline whenever baseline-relative statistics are retrieved.
- Use the total [ delta ] keywords with the show controllers
sonet line command to view the baseline statistics.
- Example
- host1#baseline line interface sonet 2/0
- There is no no version.
- See baseline line interface sonet.
baseline line path interface sonet
- Use to set a statistics baseline for the SONET/SDH path
layer.
- The router implements the baseline by reading and storing
the MIB statistics at the time the baseline is set and then subtracting
this baseline whenever baseline-relative statistics are retrieved.
- Use the total [ delta ] keywords with the show controllers
sonet path command to view the baseline statistics.
- Example
- host1#baseline path interface sonet 2/0:1
- There is no no version.
- See baseline path interface sonet.
baseline line section interface sonet
- Use to set a statistics baseline for the SONET/SDH section
layer.
- The router implements the baseline by reading and storing
the MIB statistics at the time the baseline is set and then subtracting
this baseline whenever baseline-relative statistics are retrieved.
- Use the total [ delta ] keywords with the show controllers
sonet section command to view the baseline statistics.
- Example
- host1#baseline section interface sonet 2/0
- There is no no version.
- See baseline section interface sonet.
show controllers sonet configuration
- Use to display the configuration for channelized SONET
and SDH interfaces.
- Specify an interface in slot/port format.
- To view information for a controller and all layers above
that controller, specify a controller. For example, to view all controllers
on interface 3/0, use show controllers sonet 3/0
configuration. To view information for path 1 only,
use show controllers sonet 3/0:1 configuration.
- Field descriptions
- Interface specifier in slot/port format
- channelized—Number of channels and speed for the
interface
- ifAdminStatus—Configured status of the interface:
up or down
- description—Configured description of the controller
- snmp trap link-status—State of SNMP link status
processing for the section and line layers of the interface: enabled
or disabled
- alarms used for operational status calculation—Types
of defects that the router uses to determine the operational status
of the interface at the section and line layers
- defect trigger soaking delay—Time that the router
waits to set an alarm when the router records a defect at the section
or line layer
- Operational Status—Physical state of the interface:
- up—Interface is operational
- down, failure alarm—Interface is not operational;
type of defect that caused failure is specified
- time since last status change—Time since the line
module was rebooted
- Loopback State—Type of loopback configured at this
layer in the interface, or none
- Last Remote Loopback Request Sent
- BERT test—Number of current test and total number
of tests
- Test interval—Length of the BERT test
- status—Sync (controller is synchronized with remote
device) or NoSync (controller is not synchronized with remote device
- Sync count—Number of times the pattern detector
synchronized with the incoming data pattern
- Received bit count—Number of bits received
- Error bit count—Number of bits with errors
- Mode—Type of interface: SONET or SDH
- Timing source—Type of clock source configured for
the channel:
- internal module—Internal clock is from the line
module itself
- chassis—Internal clock is from the configured router
clock
- Current section alarms—Number of suspect bit patterns
found in several consecutive frames in section layer, or none
- Current line alarms—Number of suspect bit patterns
found in several consecutive frames in line layer
- Channel configuration—Parameters for specific controllers;
the actual parameters depend on the controller.
- ifAdminStatus—State of the controller in the software
configuration: up or down
- ifOperStatus—Physical state of the controller: up
or down
- Time since last status change—Time the controller
has been up or down
- Alarms—Number of suspect bit patterns found in several
consecutive frames
- snmp trap link-status—State of SNMP link status
processing for the controller: enabled or disabled
- alarms used for operational status calculation—Types
of defects that the router uses to determine the operational status
of the interface at the path layer
- defect trigger soaking delay—Time that the router
waits to set an alarm when the router records a defect at the path
layer
- c2 byte—Setting of path signal byte: set by upper
interface type (automatic setting) or configured value
- Operational Status—Physical state of this layer:
up, down, or lowerLayerDown
- time since last status change—Time since the line
module was rebooted
- Framing—Type of framing configured for the controller:
- c-bit parity framing (for T3 interfaces)
- M23 multiplexer framing (for T3 interfaces)
- crc4—Cyclic redundancy check (for E1 interfaces)
- no-crc4—No cyclic redundancy check (for E1 interfaces)
- esf—Extended superframe (for T1 interfaces)
- sf—Superframe (for T1 interfaces)
- Line Code—Type of line coding the router assigned
to the controller: B8ZS or AMI
- Clock source—Type of clock source configured for
the channel:
- module—Internal clock is from the line module itself
- chassis—Internal clock is from the configured router
clock
- J1 transmit trace message—Trace message sent to
the remote device
- J1 expected trace message—Trace message expected
from the remote device
- J1 received trace message—Trace message received
from the remote device
- Example 1
host1#show controllers sonet 3/0 configuration
oc12 3/0
non channelized
ifAdminStatus: up
description: link1
snmp trap link-status: enabled
alarms used for operational status calculation: LOS LOF AIS RDI
defect trigger soaking delay: 2500 milliseconds
Operational Status: up
time since last status change: 00:03:30
Loopback State: none
Mode: sonet
Timing source: internal module
Receive FIFO Overruns: 0, Reconfigurations: 0
Current section defects: none
Current line defects: none
Channel configuration:
channel = 0, path = oc12, hierarchy = 1/1/0/0, current path defects: none
ifAdminStatus: up
snmp trap link-status: disabled
alarms used for operational status calculation: LOP AIS
defect trigger soaking delay: 2500 milliseconds
c2 byte override 20
Operational Status: up
time since last status change: 00:03:30
J1 transmit trace message: sonet3/0
J1 expected trace message: sonet4/0
J1 received trace message: sonet4/0
- Example 2—If you do not specify the layer in the
interface, the router shows the configuration for all layers, whether
or not you specify the keyword configuration.
host1#show controllers sonet 2/1
oc3 2/1
channelized (3 channels, oc1 minimum speed)
ifAdminStatus: up
description: link1
snmp trap link-status: enabled
alarms used for operational status calculation: LOS LOF AIS RDI
defect trigger soaking delay: 2500 milliseconds
Operational Status: up
time since last status change: 00:03:30
Operational Status: up
time since last status change: 00:06:49
Loopback State: none
Mode: sonet
Timing source: internal module
Current section alarms: none
Current line alarms : none
Channel configuration:
channel = 1, path = oc1, hierarchy = 1/1/1/1, current path alarms: none
ifAdminStatus: up
snmp trap link-status: disabled
alarms used for operational status calculation: LOP AIS
defect trigger soaking delay: 2500 milliseconds
c2 byte override 20
Operational Status: up
time since last status change: 00:06:49
Ds3 1, unchannelized
ifOperStatus = ifOperUp
snmp trap link-status = disabled
Framing is C-BIT, Line Code is B3ZS, Clock Source is Internal - Module
- Example 3—This example displays the configuration
for T3 1/1 on slot 2, port 1.
host1#show controllers sonet 2/1:1/1
oc3 2/1
channelized (3 channels, oc1 minimum speed)
ifAdminStatus: up
description: link1
snmp trap link-status: enabled
alarms used for operational status calculation: LOS LOF AIS RDI
defect trigger soaking delay: 2500 milliseconds
Operational Status: up
time since last status change: 00:03:30
Loopback State: none
Mode: sonet
Timing source: internal module
Current section alarms: none
Current line alarms : none
Channel configuration:
channel = 1, path = oc1, hierarchy = 1/1/1/1, current path alarms: none
ifAdminStatus: up
snmp trap link-status: disabled
alarms used for operational status calculation: LOP AIS
defect trigger soaking delay: 2500 milliseconds
c2 byte override 20
Operational Status: up
time since last status change: 00:05:37
Ds3 1, unchannelized
ifOperStatus = ifOperUp
snmp trap link-status = disabled
Framing is C-BIT, Line Code is B3ZS, Clock Source is Internal - Module
- See show controllers sonet.
show controllers sonet ds1|e1
- Use to display E1 or T1 (DS1) statistics for the different
layers in channelized SONET and SDH interfaces. Figure 8 shows the layers in the interface.
- For definitions of the MIB statistics, see RFC 2495—Definitions
of Managed Objects for the DS1, E1, DS2 and E2 Interface Types (January
1999).
- Specify an interface in slot/port format.
- To view information for a specific controller in a layer,
enter the specifier for the controller and the type for the controller.
For example, to view the E1 controller 1/1/1 on path 1 on the interface
4/0, enter show controllers sonet 4/0:1/1/1/1 e1.
- To view information for all controllers above a particular
layer, enter the specifier for the layer and the type for the controller.
For example, to view all E1 controllers on the interface 4/0 path
1, enter show controllers sonet 4/0:1 e1.
- To view E1 or T1 statistics for a layer, specify the controller
type, e1 or ds1.
- To view the configuration for a controller or all controllers
in a layer, omit the controller type.
- Field descriptions
- Description—Text description or alias if configured
for the interface
- BERT test—Number of current test and total number
of tests
- Test interval—Length of the BERT test
- status—Sync (controller is synchronized with remote
device) or NoSync (controller is not synchronized with remote device
- Sync count—Number of times the pattern detector
synchronized with the incoming data pattern
- Received bit count—Number of bits received
- Error bit count—Number of bits with errors
- Number of valid intervals—Number of 15-minute intervals
since the line module was last powered on or reset
- Time elapsed in current interval—Reported in 15-minute
intervals
- Errored seconds—Number of errored seconds encountered
by a T1 or an E1 in the current interval
- Severely errored seconds—Number of severely errored
seconds encountered by a T1 or an E1 in the current interval
- Severely errored frame seconds—Number of severely
errored framing seconds encountered by a T1 or an E1 in the current
interval
- Unavailable seconds—Number of unavailable seconds
encountered by a T1 or an E1 in the current interval
- Clock slip seconds—Number of clock slips encountered
by a T1 or an E1 in the current interval
- Path code violations—Number of coding violations
encountered by a T1 or an E1 in the current interval
- Line errored seconds—Number of line errored seconds
encountered by a T1 or an E1 in the current interval
- Bursty errored seconds—Number of bursty errored
seconds encountered by a T1 or an E1 in the current interval
- Degraded minutes—Number of minutes that a T1 or
an E1 line is degraded
- Line code violations—Number of line code violations
encountered by a T1 or an E1 in the current interval
- Example—This example displays statistics for all
the E1 lines on the interface 2/0.
host1#show controllers sonet 2/0 e1
E1 1/1/1
Description: boston111 e1
BERT test - 2 in 11
Test Interval 1 minute(s), Running - Status is Sync
0 minute(s), 33 second(s) left in test interval
Sync count = 1
Received bit count = 41472000
Error bit count = 0
Number of valid interval - 0
Time elapse in current interval - 0
Current Interval Counters
Errored seconds = 0
Severely errored second = 0
Severely errored frame seconds = 0
Unavailable seconds = 0
Clock slip seconds = 0
Path code violations = 0
Line errored seconds = 0
Bursty errored seconds = 0
Degraded minutes = 0
Line code violations = 0
24 Hour Total Counters
Errored seconds = 0
Severely errored second = 0
Severely errored frame seconds = 0
Unavailable seconds = 0
Clock slip seconds = 0
Path code violations = 0
Line errored seconds = 0
Bursty errored seconds = 0
Degraded minutes = 0
Line code violations = 0
- See show controllers sonet.
show controllers sonet ds3
- Use to display T3 statistics for the different layers
in channelized SONET and SDH interfaces. Figure 8 shows the layers in the interface.
- For definitions of the MIB statistics, see RFC 2496—Definitions
of Managed Objects for the DS3/E3 Interface Types (January 1999).
- Specify an interface in slot/port format.
- To view information for a specific controller in a layer,
enter the specifier for the controller and the type for the controller.
For example, to view T3 controller 1 on path 1 on the interface 4/0,
enter show controllers sonet 4/0:1/1 ds3.
- To view information for all controllers above a particular
layer, enter the specifier for the layer and the type for the controller.
For example, to view all DS3 controllers on the interface 4/0, enter show controllers sonet 4/0 ds3.
- To view T3 statistics for a layer, specify the controller
type, ds3.
- To view the configuration for a controller or all controllers
in a layer, omit the controller type.
- Field descriptions
- Description—Text description or alias if configured
for the interface
- BERT test—Number of current test and total number
of tests
- Test interval—Length of the BERT test
- status—Sync (controller is synchronized with remote
device) or NoSync (controller is not synchronized with remote device
- Sync count—Number of times the pattern detector
synchronized with the incoming data pattern
- Received bit count—Number of bits received
- Error bit count—Number of bits with errors
- Number of valid intervals—Number of 15-minute intervals
since the line module was last powered on or reset
- Time elapse in current interval—Time (seconds) passed
in current interval
- Current Interval Counters—Statistics for the current
15-minute interval
- P-bit errored seconds—Number of errored seconds
encountered by a T3
- P-bit severely errored seconds—Number of severely
errored seconds encountered by a T3
- Severely errored frame seconds—Number of severely
errored framing seconds encountered by a T3
- Unavailable seconds—Number of unavailable seconds
encountered by a T3
- Line code violations—Number of line code violations
encountered by a T3
- P-bit coding violations—Number of coding violations
encountered by a T3
- Line errored seconds—Number of line errored seconds
encountered by a T3
- C-bit coding violations—Number of C-bit coding violations
encountered by a T3
- C-bit errored seconds—Number of C-bit errored seconds
encountered by a T3
- C-bit severely errored seconds—Number of C-bit severely
errored seconds encountered by a T3
- 24 Hour Total counters—Statistics for last 24 hours
- Example 1—This example shows all T3 controllers
on the interface 2/1.
host1#show controllers sonet 2/1 ds3
Ds3 1
Description: ottawa211 ds3
Number of valid interval - 0
Time elapse in current interval - 696
Current Interval Counters
P-bit errored seconds = 0
P-bit severely errored seconds = 0
Severely errored frame seconds = 0
Unavailable seconds = 541
Line code violations = 0
P-bit coding violations = 0
Line errored seconds = 0
C-bit coding violations = 0
C-bit errored seconds = 0
C-bit severely errored seconds = 0
24 Hour Total Counters
P-bit errored seconds = 0
P-bit severely errored seconds = 0
Severely errored frame seconds = 0
Unavailable seconds = 0
Line code violations = 0
P-bit coding violations = 0
Line errored seconds = 0
C-bit coding violations = 0
C-bit errored seconds = 0
C-bit severely errored seconds = 0
- Example 2—This example shows statistics for the
T3 controller 1/1 on interface 2/0.
host1#show controllers sonet 2/0:1/1 ds3
Ds3 1
Description: ottawa2011 ds3
Number of valid interval - 0
Time elapse in current interval - 534
Current Interval Counters
P-bit errored seconds = 0
P-bit severely errored seconds = 0
Severely errored frame seconds = 0
Unavailable seconds = 117
Line code violations = 0
P-bit coding violations = 0
Line errored seconds = 0
C-bit coding violations = 0
C-bit errored seconds = 0
C-bit severely errored seconds = 0
24 Hour Total Counters
P-bit errored seconds = 0
P-bit severely errored seconds = 0
Severely errored frame seconds = 0
Unavailable seconds = 0
Line code violations = 0
P-bit coding violations = 0
Line errored seconds = 0
C-bit coding violations = 0
C-bit errored seconds = 0
C-bit severely errored seconds = 0
- See show controllers sonet.
show controllers sonet line | path | section | tributary
- Use to display statistics for the different layers in
channelized SONET and SDH interfaces. Figure 8 shows the layers in the interface.
- For definitions of the MIB statistics, see RFC 2558—Definitions
of Managed Objects for the SONET/SDH Interface Type (March 1999).
- Specify an interface in slot/port format.
- To view information for a specific controller in a layer,
enter the specifier for the controller and the type for the controller.
For example, to view tributary 1/1/1 on path 1 of interface 4/0, enter show controllers sonet 4/0:1/1/1/1 tributary.
- To view information for all controllers above a particular
layer, enter the specifier for the layer and the type for the controller.
For example, to view all tributaries on path 1 of interface 4/0, enter show controllers sonet 4/0:1 tributary.
- To view statistics for a layer, specify the type of layer.
- To view the configuration for a controller or all controllers
in a layer, omit the controller type.
- To view all statistics for all sessions, specify the total keyword.
- To view baselined statistics for all intervals, specify
the delta total keywords.
- Field descriptions
- Current Interval Counters—Statistics for the current
15-minute interval
- Errored seconds—Number of errored seconds encountered
by a T1 or an E1 in an interval
- Severly errored seconds—Number of severely errored
seconds encountered in an interval
- Severly errored framing seconds—Number of severely
errored framing seconds encountered in an interval
- Coding violations—Number of coding violations encountered
in an interval
- Unavailable seconds—Number of unavailable seconds
encountered in an interval
- Last Interval Counters—Statistics for the previous
15-minute interval
- Current Far End Interval Counters—Statistics for
the remote connection associated with the SONET/SDH path in the current
15-minute interval
- Last Far End Interval Counters—Statistics for the
remote connection associated with the SONET/SDH path in the previous
15-minute interval
- Total interval counters—Shows the statistics for
all intervals or baselined statistics
- Example 1—This example shows the MIB statistics
for the section layer on interface 2/1.
host1#show controllers sonet 2/1 section
Current Section Interval Counters
Current status = No Defect
Errored seconds = 0
Severly errored seconds = 0
Severely errored framing seconds = 0
Coding violations = 0
Last Section Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Severely errored framing seconds = 0
Coding violations = 0
- Example 2—This example illustrates the behavior
of the baseline section interface
sonet command. The examples show the MIB statistics
of the section layer before and after the command is issued.
host1#show controllers sonet 2/0 section total
Number of valid intervals - 0
Time elapsed in current interval - 192
Current Section Interval Counters
Current status = No Defect
Errored seconds = 68
Severly errored seconds = 68
Severely errored framing seconds = 2
Coding violations = 4018
Total Section Counters
Errored seconds = 68
Severly errored seconds = 68
Severely errored framing seconds = 2
Coding violations = 4018
host1#baseline section interface sonet 2/0
host1#show controllers sonet 2/0 section total delta
Number of valid intervals - 0
Time elapsed in current interval - 209
Current Section Interval Counters
Current status = No Defect
Errored seconds = 68
Severly errored seconds = 68
Severely errored framing seconds = 2
Coding violations = 4018
Total Section Counters
Errored seconds = 0
Severly errored seconds = 0
Severely errored framing seconds = 0
Coding violations = 0
- Example 3—This example shows the MIB statistics
for the line layer on interface 2/1.
host1#show controllers sonet 2/1 line
Current Line Interval Counters
Current status = No Defect
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 190
Last Line Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 900
Current Far End Line Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
Far End Last Line Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
- Example 4—This example shows the MIB statistics
for the path layer on interface 2/1.
host1#show controllers sonet 2/1 path
Channel number 1
Current Path Interval Counters
Current status = No Defect
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 248
Last Path Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
Current Far End Path Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 248
Far End Last Path Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
- Example 5—This example displays the tributary statistics
for all tributaries on interface 4/0, path 1.
host1#show controllers sonet 4/0:1 tributary
Tributary 1/1/1
Current Tributary Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
Last Tributary Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
Current Far End Path Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
Far End Last Tributary Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
- Example 6—This example displays the tributary statistics
for the tributary 1/1/1 on path 1 on slot 4, port 0.
host1#show controllers sonet 4/0:1/1/1/1 tributary
Tributary 1/1/1
Current Tributary Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
Last Tributary Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
Current Far End Path Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
Far End Last Tributary Interval Counters
Errored seconds = 0
Severly errored seconds = 0
Coding violations = 0
Unavailable seconds = 0
- See show controllers sonet.
show controllers sonet remote
- Use to display MIB statistics for the remote end of a
channelized T3 interface configured for MDL or for the remote end
of a T1 channel configured for FDL.
- Specify the all option to display detailed information
for all 15-minute intervals.
- For definitions of the MIB statistics for a T3 connections,
see RFC 2496—Definitions of Managed Objects for the DS3/E3 Interface
Types (January 1999).
- For definitions of the MIB statistics for a T1 connections,
see RFC 2495—Definitions of Managed Objects for the DS1, E1,
DS2 and E2 Interface Types (January 1999).
- Field descriptions for a T3 interface
- Far End MDL Carrier bit—Status of MDL configuration
on remote device connected to T3 interface
- set—MDL is configured for carrier mode
- not set—MDL is not configured for carrier mode
- Far End Equipment Identification Code—eic string
sent by remote device for MDL
- Far End Line Identification Code—lic string sent
by remote device for MDL
- Far End Frame Identification Code—fic string sent
by remote device for MDL
- Far End Unit Identification Code—unit string sent
by remote device for MDL
- Far End Facility Identification Code—pfi string
sent by remote device for MDL
- Far End Generator Number—generator string sent by
remote device for MDL
- Far End Port Number—port string sent by remote device
for MDL
- Number of valid intervals—Number of 15-minute intervals
since the line module was last powered on or reset
- Time elapse in current interval—Number of seconds
that have passed in the 15-minute (900-second) interval
- C-bit errored seconds—Number of C-bit errored seconds
encountered by a T3 in the current interval
- C-bit severely errored seconds—Number of C-bit severely
errored seconds encountered by a T3 in the current interval
- C-bit coding violations—Number of C-bit coding violations
encountered by a T3 in the current interval
- Unavailable seconds—Number of unavailable seconds
encountered by a T3 in the current interval
- Invalid seconds—Number of seconds when statistics
were not collected
- Field descriptions for a T1 channel
- DS1—Identifier of T1 channel
- Number of valid intervals—Number of 15-minute intervals
since the line module was last powered on or reset
- Time elapse in current interval—Number of seconds
that have passed in the 15-minute (900-second) interval
- Far End FDL Carrier bit—Status of FDL configuration
on remote device connected to T1 channel
- set—FDL is configured for carrier mode
- not set—FDL is not configured for carrier mode
- Far End Equipment Identification Code—eic string
sent by remote device for FDL
- Far End Line Identification Code—lic string sent
by remote device for FDL
- Far End Frame Identification Code—fic string sent
by remote device for FDL
- Far End Unit Identification Code—unit string sent
by remote device for FDL
- Far End Facility Identification Code—pfi string
sent by remote device for FDL
- Far End Generator Number—generator string sent by
remote device for FDL
- Far End Port Number—port string sent by remote device
for FDL
- Errored seconds—Number of errored seconds encountered
by a T1 in the current interval
- Severely errored seconds—Number of severely errored
seconds encountered by a T1 in the current interval
- Severely errored frame seconds—Number of severely
errored framing seconds encountered by a T1 in the current interval
- Unavailable seconds—Number of unavailable seconds
encountered by a T1 in the current interval
- Clock slip seconds—Number of clock slips encountered
by a T1 in the current interval
- Path code violations—Number of coding violations
encountered by a T1 in the current interval
- number of coding violations encountered by a T1 in the
current interval
- Line errored seconds—Number of line errored seconds
encountered by a T1 in the current interval
- Bursty errored seconds—Number of bursty errored
seconds encountered by a T1 in the current interval
- Degraded minutes—Number of minutes that a T1 line
is degraded
- Example 1—In this example, a T3 interface is specified.
host1#show controllers sonet 5/0:1/1 remote
Far End MDL Carrier bit is not set
Far End Equipment Identification Code is the null string
Far End Line Identification Code is the null string
Far End Frame Identification Code is the null string
Far End Unit Identification Code is the null string
Far End Facility Identification Code is the null string
Far End Generator Number is the null string
Far End Port Number is the null string
Number of valid interval - 3
Time elapse in current interval - 756
Ds3 Current Interval Counters
C-bit errored seconds = 0
C-bit severely errored seconds = 0
C-bit coding violations = 0
Unavailable seconds = 0
Invalid seconds = 0
Ds3 Last Interval Counters
C-bit errored seconds = 0
C-bit severely errored seconds = 0
C-bit coding violations = 0
Unavailable seconds = 0
Invalid seconds = 0
Ds3 24 Hour Total Counters
C-bit errored seconds = 1
C-bit severely errored seconds = 1
C-bit coding violations = 330
Unavailable seconds = 0
Invalid seconds = 0
- Example 2—In this example, a T1 channel on a T3
over channelized SONET interface is specified.
host1#show controllers sonet 5/0:1/1/1 remote
DS1 10/1:1
Number of valid interval - 0
Time elapse in current interval - 0
Far End FDL Carrier bit is not set
Far End Equipment Identification Code is the null string
Far End Line Identification Code is the null string
Far End Frame Identification Code is the null string
Far End Unit Identification Code is the null string
Far End Facility Identification Code is the null string
Far End Port Number is the null string
Far End Generator Number is the null string
DS1 Current Interval Counters
Errored seconds = 0
Severely errored second = 0
Severely errored frame seconds = 0
Unavailable seconds = 0
Clock slip seconds = 0
Path code violations = 0
Line errored seconds = 0
Bursty errored seconds = 0
Degraded minutes = 0
DS1 24 Hour Total Counters
Errored seconds = 0
Severely errored second = 0
Severely errored frame seconds = 0
Unavailable seconds = 0
Clock slip seconds = 0
Path code violations = 0
Line errored seconds = 0
Bursty errored seconds = 0
Degraded minutes = 0
- Example 3—In this example, a T1 over channelized
SONET interface is specified.
host1#show controllers sonet 5/0:1/1/1/2/2 remote
DS1 10/1:1
Number of valid interval - 0
Time elapse in current interval - 0
Far End FDL Carrier bit is not set
Far End Equipment Identification Code is the null string
Far End Line Identification Code is the null string
Far End Frame Identification Code is the null string
Far End Unit Identification Code is the null string
Far End Facility Identification Code is the null string
Far End Port Number is the null string
Far End Generator Number is the null string
DS1 Current Interval Counters
Errored seconds = 0
Severely errored second = 0
Severely errored frame seconds = 0
Unavailable seconds = 0
Clock slip seconds = 0
Path code violations = 0
Line errored seconds = 0
Bursty errored seconds = 0
Degraded minutes = 0
DS1 24 Hour Total Counters
Errored seconds = 0
Severely errored second = 0
Severely errored frame seconds = 0
Unavailable seconds = 0
Clock slip seconds = 0
Path code violations = 0
Line errored seconds = 0
Bursty errored seconds = 0
Degraded minutes = 0
- See show controllers sonet remote.
show interfaces serial
- Use to display information about the serial interfaces
you specify.
- Field descriptions
- Serial Interface—Location of the interface
- Description—Text description or alias if configured
for the interface
- ifOperStatus—Physical state of the interface
- ifOperDown—Interface is not functioning
- ifOperLowerLayerDown—Lower layer in the interface
stack is not functioning
- ifOperNotPresent—Module has been removed from the
chassis
- ifOperTesting—Interface is being tested
- ifOperUp—Interface is functioning
- snmp trap link-status—Enabled or disabled
- Encapsulation—Layer 2 encapsulation display; options:
ppp, frame-relay ietf, mlppp, mlframe-relay ietf, hdlc
- Crc type checking—Size of the CRC
- Hdlc mru—Current size of the MRU
- Hdlc mtu—Current size of the MTU
- Hdlc interface speed—Current line speed of the interface
- Hdlc idle-character—Current idle character
- Invert data disabled—Status of the data inversion
feature
- Ds0 mode—Nx56 or Nx64
- 5 minute input rate—Data rates based on the traffic
received in the last five minutes
- 5 minute output rate—Data rates based on the traffic
sent in the last five minutes
- Interface Statistics
- Packets received—Number of packets received on the
interface
- Bytes received—Number of bytes received on the interface
- Errored packets received—Number of packets with
errors received on the interface
- Packets sent—Number of packets sent on the interface
- Bytes sent—Number of bytes sent on the interface
- Errored packets sent—Number of packets with errors
sent from the interface
- Example
host1#show interfaces serial 2/0:1/1/1/1/1
Serial Interface at 2/0:1/1/1/1/1
Description: toronto20 hdlc channel
ifOperStatus = ifOperUp
snmp trap link-status = disabled
Encapsulation hdlc
Crc type checking - CRC16
Hdlc mru = 1600
Hdlc mtu = 1600
Hdlc interface speed = 1536000
Hdlc idle-character marks
Invert data disabled, Ds0 time slot map = 0xffffff
Ds0 mode = Nx64
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
Interface statistics
Packets received 100
Bytes received 1300
Errored packets received 1
Packets sent 100
Bytes send 1436
Errored packets sent 0
- See show interfaces.
Monitoring APS/MSP
For information about monitoring APS/MSP, see Monitoring APS/MSP in Configuring Unchannelized OCx/STMx Interfaces .
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]