Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Monitoring Channelized DS3 Interfaces

 

Checklist for Monitoring Channelized DS3 Interfaces

Purpose

To monitor Channelized DS3 interfaces and begin the process of isolating Channelized DS3 interface problems when they occur.

Action

Table 1 provides the links and commands for monitoring Channelized DS3 interfaces.

Table 1: Checklist for Monitoring Channelized DS3 Interfaces

Tasks

Command or Action

Monitor Channelized DS3 Interfaces 
  1. Display the Status of Channelized DS3 Interfaces

show interfaces terse t1*

  1. Display the Status of a Specific Channelized DS3 Interface

show interfaces t1-fpc/pic/port:channel

  1. Display Extensive Status Information for a Specific Channelized DS3 Interface

show interfaces t1-fpc/pic/port:channel extensive

  1. Monitor Statistics for a Channelized DS3 Interface

monitor interfaces t1-fpc/pic/port:channel

Monitor Channelized DS3 Interfaces

By monitoring Channelized DS3 interfaces, you begin the process of isolating Channelized DS3 interface problems when they occur.

To monitor your Channelized DS3 interfaces, follow these steps:

  1. Display the Status of Channelized DS3 Interfaces

  2. Display the Status of a Specific Channelized DS3 Interface

  3. Display Extensive Status Information for a Specific Channelized DS3 Interface

  4. Monitor Statistics for a Channelized DS3 Interface



Display the Status of Channelized DS3 Interfaces

Purpose

To display the status of Channelized DS3 interfaces, use the following Junos OS command-line interface (CLI) operational mode command:

Action

Sample Output 1

user@host> show interfaces t1* terse

Sample Output 2

user@host> show interfaces t1* terse

Meaning

The sample output shows the status of both the physical and logical interfaces. Sample output 1 shows that 12 of the possible 28 channels have IP addresses and are connected. Of the 12 connected channels, the last channel (t1-1/2/0:19.0) is currently down.

Sample output 2 shows that all links are up except for interface t1-0/3/3:0, which has both the physical and logical links down.



Display the Status of a Specific Channelized DS3 Interface

Purpose

To display the status of a specific Channelized DS3 interface, use the following Junos OS CLI operational mode command:

Action

Sample Output 1

user@host> show interfaces t1-1/2/0:5

Sample Output 2

user@host> show interfaces t1-0/3/3:2

Sample Output 3

user@host> show interfaces t1-1/2/0:1

Sample Output 4

user@host> show interfaces t1-1/2/0:19

Meaning

The first line of the output shows the status of the channel. If this line shows that the physical link is up, the physical link is healthy and can pass packets. If this line shows that the physical link is down, the physical link is unhealthy and cannot pass packets.

Sample output 1 shows a channel that is connected and operating correctly. You can verify the following information to check that the interface is functioning correctly:

  • Encapsulation used on the physical interface, Link-level type: PPP

  • Reference clock source, Clocking: Internal

  • Frame checksum sequence, FCS: 16

  • Physical layer framing format used on the link, Framing: ESF

Because the link-level type is Point-to-Point Protocol (PPP), the link control protocol (LCP) state is Opened, and the network control protocol (NCP) state has one protocol, NCP::inet:Opened, indicating that the link is healthy. There are no DS1 alarms or defects.

Sample output 2 shows a channel that is connected and operating correctly. However, this channel has Cisco HDLC configured as the link-level type and a logical interface (t1-0/3/3:2.0) configured.

Sample output 3 shows a channel that is not connected, Physical link is Down. Loopback is not configured, Loopback: None, and the input and output counters are zero. In addition, there are alarm indication signal (AIS) and loss of frame (LOF) alarms and defects.

Sample output 4 shows a channel that is assigned but down, Physical link is Down. Information about the physical interfaces shows the device flags are Present Running Down, and one of the interface flags is Hardware-Down. In addition, interface protocol initialization failed to complete successfully on logical interface t1-1/2/0:19.0, Flags: Hardware-Down Device-Down.



Display Extensive Status Information for a Specific Channelized DS3 Interface

Purpose

To display the status of Channelized DS3 interfaces, use the following Junos OS CLI operational mode command:

Action

Sample Output 1

user@host> show interfaces t1-1/2/0:5 extensive

Sample Output 2

user@host> show interfaces t1-0/3/3:2 extensive

Sample Output 3

user@host> show interfaces t1-1/2/0:19 extensive

Meaning

The sample output shows very detailed interface information which includes where any errors might be occurring. The first line of the output indicates if the link is up. Sample output 1 and 2 show that both links are up. Sample output 3 shows that the link is down. The main sections of the output to examine are:

  • DS1 alarms

  • DS1 defects

  • T1 media

Both sample output 1 and 2 show no DS1 alarms or defects. Sample output 3 shows AIS and LOF alarms and defects. For more information about AIS and LOF alarms and defects, see List of Common SONET Alarms and Errors.

Even though there are counts in the T1 media section of the output in sample output 1 and 2, the State column indicates that the media are OK. However, sample output 3, in which the link is down, shows that the AIS and LOF defects are active.



Monitor Statistics for a Channelized DS3 Interface

Purpose

To display the status of Channelized DS3 interfaces, use the following Junos OS CLI operational mode command:

Action

Sample Output

user@host> monitor interfaces t1-1/2/0:5

Sample Output 2

user@host> monitor interface t1-0/3/3:2

Sample Output 3

user@host> monitor t1-1/2/0:19

Meaning

The sample output shows common interface failures, indicates whether loopback is detected, and shows increases in framing errors. Use information from this command to help narrow down possible causes of an interface problem.

The output in the examples is static, however, the counters in real time change as they are updated every second. The counters in sample output 3 show that there is no traffic for the interface that is down, and that it has active alarms, defects, and there are interface warnings.

Note

If you are accessing the router from the console connection, make sure you set the CLI terminal type using the set cli terminal command.

Caution

We recommend that you use this command only for diagnostic purposes. Do not leave it on during normal router operations because real-time monitoring of traffic consumes additional CPU and memory resources.