Monitoring Interfaces
The below topics discuss the monitoring of the status and traffic, system process information, system properties, statistics for a fast Ethernet and the tracing operations of the interface process.
Monitoring Interface Status and Traffic
Purpose
View interface status to monitor interface bandwidth utilization and traffic statistics.
Action
To view interface status for all the interfaces, enter show interfaces xe.
To view status and statistics for a specific interface, enter show interfaces xe interface-name.
To view status and traffic statistics for all interfaces, enter either show interfaces xe detail or show interfaces xe extensive.
Meaning
For details about output from the CLI commands, see show interfaces xe.
Monitoring System Process Information
Purpose
View the processes running on the device.
Action
To view the software processes running on the device:
user@switch> show system processes
Meaning
Table 1 summarizes the output fields in the system process information display.
The display includes the total CPU load and total memory utilization.
Table 1: Summary of System Process Information Output Fields
Field | Values |
|---|---|
PID | Identifier of the process. |
Name | Owner of the process. |
State | Current state of the process. |
CPU Load | Percentage of the CPU that is being used by the process. |
Memory Utilization | Amount of memory that is being used by the process. |
Start Time | Time of day when the process started. |
See also
Monitoring System Properties
Purpose
View system properties such as the name, IP address, and resource usage.
Action
To monitor system properties in the CLI, enter the following commands:
Meaning
Table 2 summarizes key output fields in the system properties display.
Table 2: Summary of Key System Properties Output Fields
Field | Values | Additional Information |
|---|---|---|
| General Information | ||
Serial Number | Serial number of device. | |
Junos OS Version | Version of Junos OS active on the switch, including whether the software is for domestic or export use. | Export software is for use outside the USA and Canada. |
Hostname | Name of the device. | |
IP Address | IP address of the device. | |
Loopback Address | Loopback address. | |
Domain Name Server | Address of the domain name server. | |
Time Zone | Time zone on the device. | |
| Time | ||
Current Time | Current system time, in Coordinated Universal Time (UTC). | |
System Booted Time | Date and time when the device was last booted and how long it has been running. | |
Protocol Started Time | Date and time when the protocols were last started and how long they have been running. | |
Last Configured Time | Date and time when a configuration was last committed. This field also shows the name of the user who issued the last commit command. | |
Load Average | CPU load average for 1, 5, and 15 minutes. | |
| Storage Media | ||
Internal Flash Memory | Usage details of internal flash memory. | |
External Flash Memory | Usage details of external USB flash memory. | |
| Logged in Users Details | ||
User | Username of any user logged in to the switch. | |
Terminal | Terminal through which the user is logged in. | |
From | System from which the user has logged in. A hyphen indicates that the user is logged in through the console. | |
Login Time | Time when the user logged in. | This is the user@switch field in show system users command output. |
Idle Time | How long the user has been idle. | |
See also
Monitor Statistics for a Fast Ethernet or Gigabit Ethernet Interface
Purpose
To monitor statistics for a Fast Ethernet or Gigabit Ethernet interface, use the following Junos OS CLI operational mode command:
Action
We recommend that you use the monitor interface fe-fpc/pic/port or monitor interface ge-fpc/pic/port command only for diagnostic purposes. Do not leave these commands on during normal router operations because real-time monitoring of traffic consumes additional CPU and memory resources.
Sample Output
The following sample output is for a Fast Ethernet interface:
user@host> monitor interface fe-2/1/0 Interface: fe-2/1/0, Enabled, Link is Up Encapsulation: Ethernet, Speed: 100mbps Traffic statistics: Current Delta Input bytes: 282556864218 (14208 bps) [40815] Output bytes: 42320313078 (384 bps) [890] Input packets: 739373897 (11 pps) [145] Output packets: 124798688 (1 pps) [14] Error statistics: Input errors: 0 [0] Input drops: 0 [0] Input framing errors: 0 [0] Policed discards: 6625892 [6] L3 incompletes: 75 [0] L2 channel errors: 0 [0] L2 mismatch timeouts: 0 [0] Carrier transitions: 1 [0] Output errors: 0 [0] Output drops: 0 [0] Aged packets: 0 [0] Active alarms : None Active defects: None Input MAC/Filter statistics: Unicast packets 464751787 [154] Packet error count 0 [0]
Meaning
Use the information from this command to help narrow down possible causes of an interface problem.
If you are accessing the router from the console connection, make sure you set the CLI terminal type using the set cli terminal command.
The statistics in the second column are the cumulative statistics since the last time they were cleared using the clear interfaces statistics interface-name command. The statistics in the third column are the cumulative statistics since the monitor interface interface-name command was executed.
If the input errors are increasing, verify the following:
Check the cabling to the router and have the carrier verify the integrity of the line. To verify the integrity of the cabling, make sure that you have the correct cables for the interface port. Make sure you have single-mode fiber cable for a single-mode interface and multimode fiber cable for a multimode interface.
For a fiber-optic connection, measure the received light level at the receiver end and make sure that it is within the receiver specification of the Ethernet interface. See Fiber-Optic Ethernet Interface Specifications for the fiber-optic Ethernet interface specifications.
Measure the transmit light level on the Tx port to verify that it is within specification. See Fiber-Optic Ethernet Interface Specificationsfor the optical specifications.
Tracing Operations of the Interface Process
To trace the operations of the router or switch interface process, dcd, perform the following steps:
- In configuration mode, go to the [edit interfaces] hierarchy level:[edit]user@host# edit interfaces
- Configure the traceoptions statement.[edit interfaces]user@host# edit traceoptions
- Configure the no-remote-trace option to disable
remote tracing.[edit interfaces traceoptions]user@host# set no-remote-trace
- Configure the file filename option.[edit interfaces traceoptions]user@host# edit file
- Configure the files number option, match regular-expression option, size size option, and world-readable | no-world-readable option.[edit interfaces traceoptions file]user@host# set files numberuser@host# set match regular-expressionuser@host# set size sizeuser@host# set word-readable | no-world-readable
- Configure the tracing flag. [edit interfaces traceoptions]user@host# set flag flag-option
- Configure the disable option in flag flag-option statement to disable the tracing operation.
You can use this option to disable a single operation when you have
defined a broad group of tracing operations, such as all.[edit interfaces traceoptions]user@host# set flag flag-option disable
You can specify the following flags in the interfaces traceoptions statement:
all—Enable all configuration logging.
change-events—Log changes that produce configuration events.
gres-events—Log the events related to GRES.
resource-usage—Log the resource usage for different states.
config-states—Log the configuration state machine changes.
kernel—Log configuration IPC messages to kernel.
kernel-detail—Log details of configuration messages to kernel.
select-events—Log the events on select state machine.
By default, interface process operations are placed in the file named dcd and three 1-MB files of tracing information are maintained.
For general information about tracing, see the tracing and logging information in the Junos OS Administration Library.