The 'monitor interface interface-name' command displays per-second real-time statistics for a physical interface. We can also view common interface failures, such as alarms, errors, or loopback settings. The below fig shows the output of the monitor command
show route table inet.0 : We use 'show route table inet.0' command in the operational mode hierarchy to view the IPv4 unicast routes whereas, 'show route table inet.1' command displays the IPv4 multicast routes.
We use 'show route table inet.1' command to view the routing table that stores IPv4 multicast routes. In the below output, the multicast group 224.2.2.2/32 is being advertised by a source located at 10.10.200.200/32.
The monitor traffic command prints packet headers to your terminal screen for information sent or received by the Routing Engine. It is very similar in operation to the Unix tcpdumputility.
We can use a number network tools to help with troubleshooting and end-to-end connectivity. The ping, traceroute, ssh and telnet commands we use mostly. We would use ping to check end-to-end connectivity testing and we would use traceroute to check the path that we are using to get from one device to another, whether that is on our internal LAN or across the internet. With Junos if we are using a DNS name (i.e. google.co.uk), it will by default use IPv6 AAAA record to try and get find the host in question. If you don't have IPv6 configured on your network this is no help at all!
The ping destination command is a common troubleshooting tool used to check host reachability and network connectivity. It sends ICMP ECHO_REQUEST messages to elicit ICMP ECHO_ RESPONSE messages from the specified host.
We use 'set system services ping' command on our juniper devices to allow ping service. This command is written in configuration mode hierarchy.
Ping and traceroute are the network troubleshooting tools. We often use traceroute when the result of the ping command shows that end-to-end network connectivity is not established.
The 'deactivate system services telnet' command only deactivates the telnet service from our device. In order to remove the telnet service from our device, we use 'delete system services telnet'.
Traceroute command output is as shown below
After executing 'traceroute 192.168.5.1' command, the given output is obtained. We can determine the actual network path taken by the IP packets and also know where the problem might exist. The traceroute command lists all the routers that it passes through until the destination is reached, or fails to and is discarded.
