- play_arrow Overview
- play_arrow Operation, Administration, and Management Features
- play_arrow Ethernet OAM and Connectivity Fault Management for Routers
- Introduction to OAM Connectivity Fault Management (CFM)
- Configure Connectivity Fault Management (CFM)
- CFM Action Profile
- Ethernet Local Management Interface
- CFM Support for CCC Encapsulated Packets
- Configure Unified ISSU for 802.1ag CFM
- CFM Monitoring between CE and PE Devices
- Configure Continuity Check Messages
- Example: Configure Ethernet CFM on Physical Interfaces
- Example: Configure Ethernet CFM on Bridge Connections
- Example: Configure Ethernet CFM over VPLS
- play_arrow Link Fault Management for Routers
- play_arrow Ethernet OAM Link Fault Management for Switches
- play_arrow Ethernet OAM Connectivity Fault Management for Switches
- play_arrow Ethernet Frame Delay
- Ethernet Frame Delay Measurements on Switches
- Configure MEP Interfaces on Switches to Support Ethernet Frame Delay Measurements (CLI Procedure)
- Configure One-Way Ethernet Frame Delay Measurements on Switches (CLI Procedure)
- Configure an Iterator Profile on a Switch (CLI Procedure)
- Trigger an Ethernet Frame Delay Measurement Session on a Switch
- Configure Two-Way Ethernet Frame Delay Measurements on Switches (CLI Procedure)
- play_arrow Ethernet Service OAM (ITU-TY.1731) for Routers
- ITU-T Y.1731 Ethernet Service OAM Overview
- Configure Ethernet Frame Delay Measurement Sessions
- Configuring MEP Interfaces to Support Ethernet Frame Delay Measurements
- Configure Ethernet Frame Loss Measurement
- Configure an Iterator Profile
- Configure Ethernet Synthetic Loss Measurements
- Ethernet Alarm Indication
- Inline Transmission Mode
-
- play_arrow Network Monitoring by using SNMP
- SNMP Architecture and SNMP MIBs Overview
- Understand SNMP Implementation in Junos OS
- Configure SNMP in Junos OS
- Configure Options on Managed Devices for Better SNMP Response Time
- Enterprise Specific Utility MIB to Enhance SNMP Coverage
- Optimize the Network Management System Configuration for the Best Results
- Interfaces to Accept SNMP Requests
- Configure SNMP for Routing Instances
- Configure SNMP Remote Operations
- SNMP Traps
- SNMP Traps Supported by Junos OS
- Trace SNMP Activity
- Access Privileges for an SNMP Group
- Configure Local Engine ID on SNMPv3
- Configure SNMPv3
- Configure SNMPv3 Authentication Type and Encryption Type
- SNMPv3 Traps
- SNMPv3 Informs
- SNMP Communities
- MIB Views
- SNMP MIBs Supported by Junos OS and Junos OS Evolved
- Junos OS SNMP FAQs
- play_arrow Remote Network Monitoring (RMON) with SNMP Alarms and Events
- play_arrow Accounting Options
- play_arrow Monitoring Options
- play_arrow Interface Alarms
- play_arrow IP Monitoring
- play_arrow sFlow Monitoring Technology
- play_arrow Adaptive Sampling for Routers and Switches
- play_arrow Packet Flow Accelerator Diagnostics Software
-
- play_arrow Performance Management
- play_arrow Port Mirroring
- play_arrow Port Mirroring and Analyzers
- Port Mirroring and Analyzers
- Configuring Port Mirroring and Analyzers
- Configuring Port Mirroring Instances
- Configuring Port Mirroring on Physical Interfaces
- Configuring Port Mirroring on Logical Interfaces
- Configuring Port Mirroring for Multiple Destinations
- Configuring Port Mirroring for Remote Destinations
- Configuring Port Mirroring Local and Remote Analysis
- 1:N Port Mirroring to Multiple Destinations on Switches
- Example: Configure Port Mirroring with Family any and a Firewall Filter
- Monitoring Port Mirroring
- Configure Packet Mirroring with Layer 2 Headers for Layer 3 Forwarded Traffic
- Troubleshooting Port Mirroring
-
- play_arrow System Log Messages
- play_arrow Network Management and Troubleshooting
- Compressing Troubleshooting Logs from /var/logs to Send to Juniper Networks Technical Support
- Monitoring and Troubleshooting
- Troubleshooting System Performance with Resource Monitoring Methodology
- Configuring Data Path Debugging and Trace Options
- Using MPLS to Diagnose LSPs, VPNs, and Layer 2 Circuits
- Using Packet Capture to Analyze Network Traffic
- On-Box Packet Sniffer Overview
- Troubleshooting Security Devices
- play_arrow Configuration Statements and Operational Commands
Display Real-Time Information from Device to Host
This section describes how to display real-time monitoring information about each device between the device and a destination host.
Display Real-Time Monitoring Information
To display real-time monitoring information about each device
between the device and a specified destination host, enter the traceroute monitor
command with the following syntax:
user@host> traceroute monitor host <count number> <inet | inet6> <interval seconds> <no-resolve> <size bytes><source source-address> <summary>
Table 1 describes
the traceroute monitor
command options.
Option | Description |
---|---|
| Sends traceroute packets to the hostname or IP address you specify. |
| (Optional) Limits the number of ping requests, in packets, to send in summary mode. If you do not specify a count, ping requests are continuously sent until you press Q. |
| (Optional) Forces the traceroute packets to an IPv4 destination. |
| (Optional) Forces the traceroute packets to an IPv6 destination. |
| (Optional) Sets the interval between ping
requests, in seconds. The default value is |
| (Optional) Suppresses the display of the hostnames of the hops along the path. |
| (Optional) Sets the size of the ping request
packet. The size can be from |
| (Optional) Uses the source address that you specify, in the traceroute packet. |
| (Optional) Displays the summary traceroute information. |
To quit the traceroute monitor
command, press Q.
The following is sample output from a traceroute monitor
command:
user@host> traceroute monitor host2
My traceroute [v0.69] host (0.0.0.0)(tos=0x0 psize=64 bitpattern=0x00) Wed Mar 14 23:14:11 2007 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 173.24.232.66 0.0% 5 9.4 8.6 4.8 9.9 2.1 2. 173.24.232.66 0.0% 5 7.9 17.2 7.9 29.4 11.0 3. 173.24.232.66 0.0% 5 9.9 9.3 8.7 9.9 0.5 4. 173.24.232.66 0.0% 5 9.9 9.8 9.5 10.0 0.2
Table 2 summarizes the output fields of the display.
Field | Description |
---|---|
| Hostname or IP address of the device issuing
the |
| Size of ping request packet, in bytes. |
Keys | |
| Displays the Help for the CLI commands. Press H to display the Help. |
| Toggles the display mode. Press D to toggle the display mode |
| Restarts the Press R to restart the |
| Sets the order of the displayed fields. Press O to set the order of the displayed fields. |
| Quits the Press Q to quit the |
Packets | |
number | Number of the hop (device) along the route to the final destination host. |
| Hostname or IP address of the device at each hop. |
| Percent of packet loss. The number of ping responses divided by the number of ping requests, specified as a percentage. |
Pings | |
| Number of ping requests sent to the device at this hop. |
| Most recent round-trip time, in milliseconds, to the device at this hop. |
| Average round-trip time, in milliseconds, to the device at this hop. |
| Shortest round-trip time, in milliseconds, to the device at this hop. |
| Longest round-trip time, in milliseconds, to the device at this hop. |
| Standard deviation of round-trip times, in milliseconds, to the device at this hop. |
Display Multicast Path Information
To display information about a multicast path from a source
to the device, enter the mtrace from-source
command with
the following syntax:
user@host> mtrace from-source source host <extra-hops number> <group address> <interval seconds> <max-hops number> <max-queries number> <response host> <routing-instance routing-instance-name> <ttl number> <wait-time seconds> <loop> <multicast-response | unicast-response> <no-resolve> <no-router-alert> <brief | detail>
Table 3 describes
the mtrace from-source
command options.
Option | Description |
---|---|
| Traces the path to the specified hostname or IP address. |
| (Optional) Sets the number of extra hops to
trace past nonresponsive devices. Specify a value from |
| (Optional) Traces the path for the specified
group address. The default value is |
| (Optional) Sets the interval between statistics
gathering. The default value is |
| (Optional) Sets the maximum number of hops
to trace toward the source. Specify a value from |
| (Optional) Sets the maximum number of query
attempts for any hop. Specify a value from |
| (Optional) Sends the response packets to the specified hostname or IP address. By default, the response packets are sent to the device. |
| (Optional) Traces the routing instance you specify. |
| (Optional) Sets the time-to-live (TTL) value
in the IP header of the query packets. Specify a hop count from |
| (Optional) Sets the time to wait for a response
packet. The default value is |
| (Optional) Loops indefinitely, displaying
rate and loss statistics. To quit the |
| (Optional) Forces the responses to use multicast. |
| (Optional) Forces the response packets to use unicast. |
| (Optional) Does not display hostnames. |
| (Optional) Does not use the device alert IP option in the IP header. |
| (Optional) Does not display packet rates and losses. |
| (Optional) Displays packet rates and losses if a group address is specified. |
The following is sample output from the mtrace from-source
command:
user@host> mtrace from-source source 192.1.4.1 group 224.1.1.1
Mtrace from 192.1.4.1 to 192.1.30.2 via group 224.1.1.1 Querying full reverse path... * * 0 ? (192.1.30.2) -1 ? (192.1.30.1) PIM thresh^ 1 -2 routerC.mycompany.net (192.1.40.2) PIM thresh^ 1 -3 hostA.mycompany.net (192.1.4.1) Round trip time 22 ms; total ttl of 2 required. Waiting to accumulate statistics...Results after 10 seconds: Source Response Dest Overall Packet Statistics For Traffic From 192.1.4.1 192.1.30.2 Packet 192.1.4.1 To 224.1.1.1 v __/ rtt 16 ms Rate Lost/Sent = Pct Rate 192.168.195.37 192.1.40.2 routerC.mycompany.net v ^ ttl 2 0/0 = -- 0 pps 192.1.40.1 192.1.30.1 ? v \__ ttl 3 ?/0 0 pps 192.1.30.2 192.1.30.2 Receiver Query Source
Each line of the trace display is usually in the following format (depending on the options selected and the responses from the devices along the path):
hop-number host (ip-address) protocolttl
Table 4 summarizes the output fields of the display.
The packet statistics gathered from Juniper Networks devices
and routing nodes always display as 0
.
Field | Description |
---|---|
| Number of the hop (device) along the path. |
| Hostname, if available, or IP address of the
device. If the |
| IP address of the device. |
| Protocol used. |
| TTL threshold. |
| Total time between the sending of the query packet and the receiving of the response packet. |
| Total number of hops required to reach the source. |
| Source IP address of the response packet. |
| Response destination IP address. |
| Average packet rate for all traffic at each hop. |
| Number of packets lost, number of packets sent, percentage of packets lost, and average packet rate at each hop. |
| IP address receiving the multicast packets. |
| IP address of the host sending the query packets. |