At JUNOS Health Check v1.0

JUNOS Monitoring & Health Check Document
2 Syslog
This Syslog feature causes the Juniper router to store all log messages to a
revolving buffer called the logging buffer. The messages logged are those from
all facilities such as authorization, severities (info) and from all facilities
(any).
<file-name> Description
messages
Log file messages have all the login attempts and authorization
information.
All severity levels. The severity hierarchy in the Junos OS is:
Severity Severity Severity Description

Name Number
Debug 7 Information to be used for debugging
info 6 Informational events about normal
operations
notice 5 Conditions that aren’t errors but are of
more interest than normal operations
warning 4 General warnings for significant events
error 3 General errors
critical 2 Critical errors, including hardware
failures
alert 1 Errors that require immediate intervention
emergency 0 Conditions that stop router function
interactive- Logs any interactive commands issued by users on the router.

commands
audit Logs a message when users issue any command at the CLI operational
or configuration mode prompt.
Table 1: Log files

2.1 Managing the log files
Multiple system logging files are configured to track messages from different
sources and of different severities. Instead of sifting through the messages file
to find out what users and processes have been logging in to the Juniper router,
the system logging file in table 3 for only those activities.
2.2 Viewing the log files

To review the system log messages, use the command "show log <file-name>". In all
system log message files, the messages are listed in order, from oldest to newest.
It is also possible to review the system log messages for today's date and time.
> show log messages | match "Mar 9 11:5"
3 Checking who’s on the Router

Displays the names of users who are logged in.
More than one person can log in to a Juniper router at any given time, logging in
either with an individual user account name or with a group name that is shared by
many users. (An example of a group account is root.) Each person who is on the
router can perform whatever operations they’re allowed, depending on their
privileges and it’s possible that another person’s work may interfere with what
you’re doing.
> show system users
3.1 Forced log out

Forced log out users from the router configuration database.
> request system logout <login name>
© Nokia 2014
2015-09– 05/ 66
3.2 Send message to all users

Display a message on the screens of all users who are logged in to the router on
specific screens. The message goes to everyone currently logged in to the router.
> request message all message "End router session now!"
3.3 Send message to particular user
Display a message on the screens of particular user-name logged in to the router.
> request message user <login name> message "End router session now!"
4 Simple Network Management Protocol (SNMP)

Display SNMP is up and running, that requests are being properly transmitted, and
that the number of requests is incrementing over time.
> show snmp statistics
The output shows the number and types of packets the router has received from and
sent to the NMS. If you see any bad (invalid) community names, or if the number of
names increases, this can indicate that one or more community names are configured
incorrectly, or that an unauthorized manager, possibly a malicious user, is trying
to access the agent
5 Figuring out who’s configuring
Displays who is changing the configuration.
Junos OS also allows multiple people to be in configuration mode at the same time.
When entering configuration mode, the CLI displays a message letting know whether
anyone else is also editing the configuration. However, if new user enters
configuration mode, the current won’t receive any kind of message.
# status
6 Traceoptions
Display trace log file which is viewed similar to the syslog files
In addition to logging system events, Junos OS software allows you to monitor

events through trace logging. That is, system logging (as the name implies) is
systemwide, whereas tracing is a more localized function of specific protocol and
processes.
Because trace logging is used to monitor and troubleshoot protocols, tracing isn’t
enabled at the [edit system syslog] level in the configuration hierarchy. Instead,
the tracing options (or traceoptions) are configured at the various protocol
levels in the configuration hierarchy.
> show log log-ddos
For example on Juniper routers, traceoptions is enabled to monitor the routing

protocol OSPF activities, using traceoptions under the [edit protocols ospf]
hierarchy in the configuration. The trace log file is viewed similar to the syslog
files.
> show log ospf-errors
7 Checking Host-to-Host with the ping command

The ping command, keeps an eye on the round-trip times to identify latency issues
within the network.
8 Tracerouting the Network

Ping is useful for figuring out whether we can reach one host from another host;
however, to find out the path that packets take through intermediate hops from
source to destination, we use the traceroute command.
The traceroute command shows the round-trip time for each of the three traceroute
packets, which gives an idea not only of which hops are being reached, but also how
long it’s taking to send traffic back and forth between those routers.
The traceroute command works by sending an ICMP packet from the source to the
destination node with an initial hop count of one. At each hop, the packet is
processed, the hop count decremented.
So as a traceroute process makes its way hop by hop from router to router, we
start to see responses showing how that packet is traversing the network. The
first hop along the way is next-hop router. As part of the traceroute process,
origin router sends three separate ICMP packets. Next-hop responds to each of
these three ICMP packets.
Figure 1: Traceroute demonstration
In this demonstration example, this information forms the first line of the output
(from router2 in this case). Then an ICMP packet with a hop count of 2 is sent
out, and makes its way to the second device similarly the output shows that
responses are being received from router3, but beyond that, nothing is received.
Looking at the topology, the next hop in the path is router5. Because the
traceroute isn’t receiving a response from router5, we know that the problem is
somewhere between router3 and router5. We still don’t know what the issue is, but
at least now we know where to look.
From the traceroute output that the packets are making their way just fine from
router1 to router3 and back.
9 Monitoring the Interfaces
9.1 Interface Statistic
Display static interface statistics, such as errors, traffic load (Input and
output rates for the connection.)
We often want to look at how the interfaces are behaving to figure out what is
happening to the traffic within the device. As such, we need to know the
parameters in the show interfaces command.
> show interfaces (no modifier)

> show interfaces brief
> show interfaces detail
9.2 Monitoring Interface Counters

Display real time, updating its display of an interface’s statistics, warnings,
errors and attributes.
> monitor interface <interface-ID>
9.3 Clearing Interface Counters
We can clear the stats with clear interface statistics or specify an interface to
clear if we are troubleshooting & health check and we want to watch how fast these
counters are increasing.
10 Monitoring the Routing Information

Display information regarding protocol adjacencies, neighbors, protocol status
> show ospf neighbor
> show ospf neighbor instance <instance-name>
> show bgp neighbor
11 Real-time Performance Monitoring

Real-Time Performance Monitoring (RPM) enables to configure active probes to track
and monitor traffic. Probes collect packets per destination and per application,
including PING Internet Control Message Protocol (ICMP) packets, User Datagram
Protocol and Transmission Control Protocol (UDP/TCP) packets with user-

configured ports, user-configured Differentiated Services code point (DSCP)
type-of-service (ToS) packets, and Hypertext Transfer Protocol (HTTP) packets.
RPM provides Management Information Base (MIB) support with extensions for RFC.
If required, please read on the below link.
http://www.juniper.net/documentation/en_US/junos14.2/topics/concept/real-time-
performance-monitoring-overview.html
12 Monitoring the Router Hardware

12.1 Environmental Information
Display all the current environmental data for the device.
This usually indicates the temperature and information about the fans,
power supplies, and Routing Engine (RE).
Table 2 lists the output fields for the "show chassis environment" command.
Field name Description

Temp Temperature of air flowing through the chassis in degrees Celsius
(C) and Fahrenheit (F).
Fan Fan status: OK, Testing (during initial power-on), Failed, or
Absent.
12.2 Chassis Alarm Status
Display if there were any fan failures, power supply failures, and so forth, they
should show up in the "show chassis alarms" command.
This usually indicates a power source problem.
12.3 Craft Display
It provides a console/remote session display of the current alarms and control

values. The commands output allows the device operator to see the status of router
alarm LEDs and controls without being physically present.
V
o
l
t
a V
o
g
le
t(
a
V
g
)
)
C
C
u
u
r
r
re
e
n
n
t
t(
(A
O
A
) n
) l K
P i O
nK
P
o e
o
w
w
e
e
r
r( 5
4
(W 5
W
) O 0
) n 0O
L l K
i Om
L
o n KV
o
a e
a
d
d
(
(%
%
) 4
) 5
5 0O
n 0
5
4 l K
4 i mO
6 n V
K
4 e
3
2
4
1
6
1
3
8
To view status and troubleshooting information at a glance and to perform many

system control functions.
Figure 1 demonstrate craft interface of the Juniper Networks MX960 router.
user@Router> show chassis craft-interface

Front Panel System LEDs:
Routing Engine 0 1
--------------------------
OK * *
Fail . .
Master * .
Front Panel Alarm Indicators:

-----------------------------
Red LED .
Yellow LED .
Major relay .
Minor relay .
Front Panel FPC LEDs:

FPC 0 1 2 3 4 5
------------------------------
Red . . . . . .
Green . * * * * .
CB LEDs:
CB 0 1
--------------
Amber . .
Green * *
PS LEDs:
PS 0 1 2 3
--------------------
Red . . . .
Green * * * *
Fan Tray LEDs:
© Nokia 2014
FT 0
----------
Red .
Green *
{master}
user@ROUTER>
12.4 Hardware Inventory
Displays the hardware components installed in Juniper MX 960 router, along with
serial numbers.
This information gives clue to failed hardware & its details such as serial number
and part number to Juniper Networks
Hardware inventory information also shows the slots that are available for a
device and provides information about power supplies, chassis cards, fans, part
numbers, and so on
Table describes the device’s hardware inventory field respect to the output of
the "show chassis hardware" command
Fields Description
Item The first column of the output lists each hardware component
installed in the router, starting with the chassis, which is the
router itself. These are chassis component depending on the device
type, can include the midplane, backplane, power supplies, fan
trays, Routing Engine (RE), front panel module board, PDM, CIP, PEM,
SCG, CB, FPCs, and PICs.
Version Revision level of the component.
Part number Part number of the component.
Serial Serial number of the component.
number
Hardware Description of the component. This last column has a brief
component description of each hardware component. This is especially useful
description for finding out which PICs are installed on which FPC and in which
location on the FPC. This information is required when configuring
the router's interfaces because it must specify the FPC number and
the PIC location to identify the interface.
The following output all the hardware components installed in the Juniper MX 960
router.
{master}
user@Router> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis JN122C100AFB MX960
Midplane REV 05 710-017414 ACRB1965 MX960 Midplane
FPM Board REV 02 710-017254 CABZ0440 Front Panel Display
PEM 0 Rev 05 740-027736 QCS1336T0JW DC 2.4kW Power Entry Module
PEM 1 Rev 05 740-027736 QCS1336T0LN DC 2.4kW Power Entry Module
PEM 2 Rev 05 740-027736 QCS1336T0M7 DC 2.4kW Power Entry Module
PEM 3 Rev 05 740-027736 QCS1336T0XE DC 2.4kW Power Entry Module
Routing Engine 0 REV 09 740-031116 9013052155 RE-S-1800x4
Routing Engine 1 REV 09 740-031116 9013052369 RE-S-1800x4
CB 0 REV 18 750-031391 CABW6518 Enhanced MX SCB
CB 1 REV 19 750-031391 CACF9151 Enhanced MX SCB
FPC 1 REV 15 750-038489 CABZ5895 MPCE Type 1 3D
CPU REV 06 711-038484 CACA5250 MPCE PMB 2G
MIC 0 REV 17 750-028390 CABY1351 3D 40x 1GE(LAN) RJ45
PIC 0 BUILTIN BUILTIN 10x 1GE(LAN) RJ45
FPC 2 REV 15 750-038489 CABZ5962 MPCE Type 1 3D
CPU REV 06 711-038484 CACA5178 MPCE PMB 2G
MIC 0 REV 27 750-028392 CACD9201 3D 20x 1GE(LAN) SFP
PIC 0 BUILTIN BUILTIN 10x 1GE(LAN) SFP
Xcvr 0 REV 01 740-031851 PQG6VFJ SFP-SX
Xcvr 1 REV 01 740-011782 PBA3LE0 SFP-SX
Xcvr 2 NON-JNPR P4B07V0 SFP-SX
PIC 1 BUILTIN BUILTIN 10x 1GE(LAN) SFP
Xcvr 7 REV 01 740-031851 PQJ2D9U SFP-SX
Xcvr 8 REV 01 740-031851 PQH2CFR SFP-SX
Xcvr 9 REV 01 740-031851 PQH10BH SFP-SX
FPC 3 REV 39 750-028467 CACC6336 MPC 3D 16x 10GE
CPU REV 13 711-029089 CACC6103 AMPC PMB
PIC 0 BUILTIN BUILTIN 4x 10GE(LAN) SFP+
Xcvr 0 REV 01 740-031980 AQA3U7M SFP+-10G-SR
Xcvr 1 REV 01 740-031981 AQH07G4 SFP+-10G-LR
Xcvr 2 fRt NON-JNPR AVD1726A79V SFP+-10G-SR
Xcvr 3 REV 01 740-031980 AQB0GKZ SFP+-10G-SR
Xcvr 0 REV 01 740-031980 AS819T4 SFP+-10G-SR
Xcvr 1 REV 01 740-031980 AQB1SSM SFP+-10G-SR
Xcvr 2 REV 01 740-031980 AQA3U4Z SFP+-10G-SR
Xcvr 3 REV 01 740-031980 AQA3TYR SFP+-10G-SR
© Nokia 2014
Xcvr 0 REV 01 740-031980 AQA3TYJ SFP+-10G-SR

Xcvr 1 REV 01 740-031980 AQA3UDQ SFP+-10G-SR
Xcvr 2 REV 01 740-031980 AQB1T7U SFP+-10G-SR
Xcvr 3 REV 01 740-031980 AQA3UBL SFP+-10G-SR
Xcvr 0 REV 01 740-031980 AQA3UEL SFP+-10G-SR
Xcvr 1 REV 01 740-031980 AQA3UFE SFP+-10G-SR
Xcvr 2 REV 01 740-031981 AQG0FCQ SFP+-10G-LR
Xcvr 3 REV 01 740-031980 AQA3UDY SFP+-10G-SR
FPC 4 REV 41 750-028467 CACA7203 MPC 3D 16x 10GE
CPU REV 13 711-029089 CACA8685 AMPC PMB
Xcvr 1 REV 01 740-031980 AS81815 SFP+-10G-SR
Xcvr 2 REV 01 740-031980 AS80RMN SFP+-10G-SR
Xcvr 3 REV 01 740-031980 AS80RJT SFP+-10G-SR
Xcvr 0 REV 01 740-031980 AS80RJU SFP+-10G-SR
Xcvr 1 REV 01 740-031980 AS80R5M SFP+-10G-SR
Xcvr 2 REV 01 740-031980 AS812TX SFP+-10G-SR
Xcvr 3 REV 01 740-031980 AS817L8 SFP+-10G-SR
Xcvr 0 REV 01 740-031980 AS80R6Y SFP+-10G-SR
Xcvr 1 REV 01 740-031980 AS812A4 SFP+-10G-SR
Xcvr 2 REV 01 740-031980 AS8194B SFP+-10G-SR
Xcvr 3 REV 01 740-031980 AS812AF SFP+-10G-SR
Xcvr 0 REV 01 740-031980 AS8181Q SFP+-10G-SR
Xcvr 1 REV 01 740-031980 AS814K6 SFP+-10G-SR
Xcvr 2 REV 01 740-031980 AS812HV SFP+-10G-SR
Xcvr 3 REV 01 740-031980 AS812DH SFP+-10G-SR
Fan Tray Enhanced Left Fan Tray
12.5 Routing Engine (RE) Status
Displays the general condition of the REs, the status of both the primary and the
backup REs. The Routing Engine (RE) in slot 0 is the master & Routing Engine (RE)
in slot 1 is the backup.
{master}
user@ROUTER> show chassis routing-engine
Routing Engine status:
Slot 0:
Current state Master
Election priority Master
Temperature 31 degrees C / 87 degrees F
CPU temperature 27 degrees C / 80 degrees F
DRAM 16349 MB (16384 MB installed)
Memory utilization 10 percent
CPU utilization:
User 1 percent
Background 0 percent
Kernel 6 percent
Interrupt 1 percent
Idle 92 percent
Model RE-S-1800x4
Serial ID 9013052155
Start time 2015-08-04 03:10:29 CET
Uptime 42 days, 10 hours, 42 minutes, 50 seconds
Last reboot reason Router rebooted after a normal shutdown.
Load averages: 1 minute 5 minute 15 minute
0.23 0.13 0.09
Routing Engine status:
Slot 1:
Current state Backup
Election priority Backup
Temperature 30 degrees C / 86 degrees F
CPU temperature 27 degrees C / 80 degrees F
DRAM 16349 MB (16384 MB installed)
Memory utilization 9 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 99 percent
Model RE-S-1800x4
Serial ID 9013052369
Start time 2015-08-04 02:41:05 CET
Last reboot reason Router rebooted after a normal shutdown.
Load averages: 1 minute 5 minute 15 minute
0.04 0.01 0.00
12.6 System Uptime Status
Displays how long a device has been up and running.
Table describes the field respect to the output of the "show system uptime"
command
Fields Description
Current time Current system time in UTC.
System booted Date and time when the switch was last booted and how long
it has been running.
Protocols started Date and time when the routing protocols were last started
and how long they have been running.
Last configured Date and time when a configuration was last committed. Also
shows the name of the user who issued the last commit
command.
Time and up Current time, in the local time zone, and how long the
switch has been operational.
Users Number of users logged into the switch.
Load averages Load averages for the last 1 minute, 5 minutes, and 15
minutes.
{master}
user@ROUTER> show system uptime Current
time: 2015-09-15 13:54:42 CET
System booted: 2015-08-04 03:10:29 CET (6w0d 10:44 ago)
Protocols started: 2015-08-04 03:17:07 CET (6w0d 10:37 ago)
Last configured: 2015-09-14 16:07:22 CET (21:47:20 ago) by user
1:54PM up 42 days, 10:44, 2 users, load averages: 0.14, 0.12, 0.09
The first line of output shows the current time on the router. The second line
shows when the router was last booted and how long it has been up. The last line
also shows how long the router has been up. The third line shows when the protocol
software started, and the last line tells when the configuration was last changed
and by whom.
12.7 System Reboot Status
Displays last time that the device was powered on, restarted, or rebooted
{master}
user@ROUTER> show system uptime
Current time: 2015-09-15 13:54:42
CET
System booted: 2015-08-04 03:10:29 CET (6w0d 10:44 ago)
Protocols started: 2015-08-04 03:17:07 CET (6w0d 10:37
ago)
Last configured: 2015-09-14 16:07:22 CET (21:47:20 ago) by
korichikh 1:54PM up 42 days, 10:44, 2 users, load averages:
0.14, 0.12, 0.09
12.8 Last Commit Status
Displays the system commit history and any pending commit operation.
Table describes the field respect to the output of the "show system
commit" command
Fields Description
Revision Display the revision number of the active configuration of
Routing Engine(s) .
User User who executed the commit operation.
Client Display the Client server name.
Time Date and time of the commit operation.
This command also lists the history of all the commit operations that have
occurred on the router and who activated them, and provides you with a history of
configuration changes at what time.
12.9 Usage of Junos OS Kernel Memory
12.10 Usage of Task Memory
Display standard information about memory utilization for routing protocol tasks
on the routing engine on all logical systems.
Displaying memory utilization status on the system: ROUTER
{master}
user@ROUTER> show task memory
Memory Size (kB) Percentage When
Currently In Use: 17334 0% now
Maximum Ever Used: 17482 0% 15/09/08 15:10:48
Available: 3221225 100% now
{master}
user@ROUTER>
12.11 System Process
Display information about software processes that are running on the router.
{master}
user@ROUTER> show system processes extensive
last pid: 53862; load averages: 0.06, 0.06, 0.06 up 42+11:03:18 14:13:17
153 processes: 2 running, 136 sleeping, 15 waiting
Mem: 583M Active, 241M Inact, 305M Wired, 6216M Cache, 214M Buf, 8448M Free
Swap: 8192M Total, 8192M Free
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
10 root 1 171 52 0K 16K RUN 940.3H 90.28% idle
1700 root 2 8 -88 125M 18548K nanslp 40.2H 3.61% chassisd
3110 root 1 4 0 118M 30272K kqread 198:56 0.10% rpd

19 root 1 -68 -187 0K 16K WAIT 618:49 0.00% irq11: em0 em1 em2*
1710 root 1 96 0 10892K 7436K select 588:46 0.00% ppmd
3148 root 1 96 0 69924K 34724K select 152:19 0.00% mib2d
13 root 1 -40 -159 0K 16K WAIT 138:08 0.00% swi2: netisr 0
3155 root 1 96 0 65712K 56360K select 111:21 0.00% snmpd
1717 root 1 96 0 8004K 3504K select 104:42 0.00% clksyncd
11 root 1 -20 -139 0K 16K WAIT 64:39 0.00% swi7: clock sio
3116 root 1 96 0 71100K 11728K select 54:01 0.00% cosd
14 root 1 -16 0 0K 16K - 34:29 0.00% yarrow
3153 root 1 96 0 67784K 20128K select 32:44 0.00% pfed
3112 root 1 96 0 22552K 10308K select 21:46 0.00% l2ald
1730 root 1 96 0 7760K 1768K select 17:40 0.00% license-check
8 root 1 0 0 0K 16K client 13:47 0.00% ifstate notify
3161 root 1 96 0 52496K 33868K select 10:35 0.00% smid
3137 root 3 20 0 10024K 3588K sigwai 10:24 0.00% jddosd
3157 root 1 96 0 33596K 12620K select 9:54 0.00% bdbrepd
1722 root 1 96 0 12352K 3028K select 9:22 0.00% shm-rtsdbd
1532 root 1 16 0 0K 16K bcmsem 8:40 0.00% bcmLINK.0
3076 root 1 96 0 0K 16K select 5:05 0.00% peerproxy13000080
3149 root 1 96 0 98M 1868K select 4:58 0.00% alarm-mgmtd
1697 root 1 96 0 1844K 760K select 4:27 0.00% bslockd
33 root 1 20 0 0K 16K syncer 4:26 0.00% syncer
3160 root 1 96 0 112M 5016K select 4:19 0.00% transportd
3158 root 1 96 0 8084K 2156K select 2:35 0.00% alarmd
1297 root 1 8 0 764K 424K nanslp 1:54 0.00% gstatd
51 root 1 0 0 0K 16K - 1:49 0.00% schedcpu
3 root 1 -8 0 0K 16K - 1:47 0.00% g_up
3125 root 1 4 0 21068K 12800K kqread 1:46 0.00% l2cpd
3151 root 1 96 0 5108K 1792K select 1:36 0.00% irsd
3128 root 1 96 0 39892K 7504K select 1:34 0.00% cfmd
3156 root 1 96 0 77080K 15696K select 1:21 0.00% dcd
1718 root 1 96 0 10048K 4232K select 1:16 0.00% lacpd
4 root 1 -8 0 0K 16K - 1:13 0.00% g_down
1716 root 1 96 0 9252K 4272K select 1:05 0.00% bfdd
31 root 1 20 0 0K 16K vnlrum 1:05 0.00% vnlru_mem
3146 root 1 96 0 8996K 1764K select 1:01 0.00% pkid
3127 root 1 96 0 5456K 2112K select 0:54 0.00% lfmd
2 root 1 -8 0 0K 16K - 0:54 0.00% g_event
29 root 1 171 52 0K 16K pgzero 0:52 0.00% pagezero
3114 root 1 111 15 10388K 6408K select 0:49 0.00% sampled
1711 root 1 96 0 8560K 5364K select 0:48 0.00% vrrpd
42 root 1 -16 0 0K 16K psleep 0:47 0.00% vmkmemdaemon
3115 root 1 96 0 11172K 5276K select 0:46 0.00% rmopd
1726 root 1 96 0 42992K 2556K select 0:38 0.00% idpd
1702 root 1 96 0 7324K 1540K select 0:27 0.00% craftd
3122 root 1 96 0 70768K 10212K select 0:26 0.00% dfcd
46 root 1 0 0 0K 16K . 0:26 0.00% ddostasks
222 root 1 -8 0 0K 16K mdwait 0:24 0.00% md8
3113 root 1 81 -15 8064K 3120K select 0:23 0.00% apsd
5 root 1 8 0 0K 16K - 0:22 0.00% kqueue taskq
3144 root 1 96 0 36028K 2660K select 0:20 0.00% smihelperd

22 root 1 -64 -183 0K 16K WAIT 0:15 0.00% irq14: ata0
3060 root 1 8 0 2140K 668K wait 0:14 0.00% sh
3059 root 1 8 0 2140K 668K wait 0:14 0.00% sh
3061 root 1 8 0 2140K 668K wait 0:14 0.00% sh
3133 root 1 96 0 4752K 1452K select 0:12 0.00% iccpd
146 root 1 -8 0 0K 16K mdwait 0:08 0.00% md4
3142 root 1 96 0 1864K 472K select 0:08 0.00% mountd
3130 root 1 96 0 5068K 1168K select 0:08 0.00% mplsoamd
1712 root 1 96 0 1836K 880K select 0:08 0.00% smartd
34 root 1 -16 0 0K 16K sdflus 0:07 0.00% softdepflush
3154 root 1 96 0 1832K 700K select 0:07 0.00% tnp.sntpd
1530 root 1 16 0 0K 16K bcmsem 0:07 0.00% bcmXGS3AsyncTX
1529 root 1 16 0 0K 16K bcmsem 0:07 0.00% bcmTX
1329 root 1 96 0 5400K 3212K select 0:06 0.00% eventd
30 root 1 -16 0 0K 16K psleep 0:06 0.00% bufdaemon
1703 root 1 96 0 40832K 7292K select 0:05 0.00% mgd
3159 root 1 96 0 4908K 972K select 0:05 0.00% relayd
1538 root 1 8 0 1812K 1012K nanslp 0:05 0.00% cron
3152 root 1 96 0 79956K 16236K select 0:05 0.00% dfwd
32 root 1 -4 0 0K 16K vlruwt 0:05 0.00% vnlru
36 root 1 -16 0 0K 16K psleep 0:04 0.00% vmuncachedaemon
110 root 1 -8 0 0K 16K mdwait 0:04 0.00% md2
52 root 1 0 0 0K 16K no_rs 0:03 0.00% rtimeshare_thr
320 root 1 -8 0 0K 16K mdwait 0:03 0.00% md12
1696 root 1 96 0 1632K 404K select 0:03 0.00% watchdog
1731 root 1 8 0 1804K 572K nanslp 0:02 0.00% getty
53 root 1 -8 0 0K 16K mdwait 0:02 0.00% md0
9 root 1 -16 0 0K 16K psleep 0:02 0.00% pagedaemon
166 root 1 -8 0 0K 16K mdwait 0:02 0.00% md5
1310 root 1 96 0 1824K 452K select 0:02 0.00% usbd
1 root 1 8 0 1432K 988K wait 0:01 0.00% init
43708 remote 1 96 0 26716K 21812K select 0:01 0.00% cli
90 root 1 -8 0 0K 16K mdwait 0:01 0.00% md1
3120 root 1 96 0 6280K 2684K select 0:01 0.00% rdd
242 root 1 -8 0 0K 16K mdwait 0:01 0.00% md9
186 root 1 -8 0 0K 16K mdwait 0:00 0.00% md6
20 root 1 8 0 0K 16K usbevt 0:00 0.00% usb0
53635 remote 1 96 0 26716K 21772K select 0:00 0.00% cli
15 root 1 -28 -147 0K 16K WAIT 0:00 0.00% swi5: cambio
262 root 1 -8 0 0K 16K mdwait 0:00 0.00% md10
126 root 1 -8 0 0K 16K mdwait 0:00 0.00% md3
3121 root 1 96 0 5288K 1608K select 0:00 0.00% pppd
1706 root 1 96 0 3516K 1068K select 0:00 0.00% inetd
3117 root 1 96 0 5212K 1724K select 0:00 0.00% lmpd
3119 root 1 96 0 4960K 2988K select 0:00 0.00% fsad
3141 root 1 96 0 4920K 1376K select 0:00 0.00% mspd
302 root 1 -8 0 0K 16K mdwait 0:00 0.00% md11
53632 root 1 96 0 6768K 3560K select 0:00 0.00% sshd
83350 root 1 96 0 3192K 2536K select 0:00 0.00% auditd
24 root 1 -48 -167 0K 16K WAIT 0:00 0.00% swi0: sio
27 root 1 -44 -163 0K 16K WAIT 0:00 0.00% swi1: ipfwd
1725 root 1 96 0 10100K 1220K select 0:00 0.00% appidd
3145 root 1 96 0 5156K 2680K select 0:00 0.00% kod

3143 root 1 4 0 1672K 304K accept 0:00 0.00% nfsd
1698 root 1 96 0 1920K 668K select 0:00 0.00% tnetd
7843 root 1 8 0 2300K 1920K wait 0:00 0.00% login
3132 root 1 96 0 6764K 776K select 0:00 0.00% sendd
38 root 1 20 0 0K 16K condsl 0:00 0.00% delayedexecd
202 root 1 -8 0 0K 16K mdwait 0:00 0.00% md7
18 root 1 -12 -131 0K 16K WAIT 0:00 0.00% swi9: task queue
3126 root 1 96 0 5032K 632K select 0:00 0.00% oamd
3150 root 1 96 0 7560K 528K select 0:00 0.00% stats-agentd
3118 root 1 96 0 3640K 408K select 0:00 0.00% rtspd
53862 root 1 96 0 22544K 1944K RUN 0:00 0.00% top
53859 root 1 8 0 1632K 704K nanslp 0:00 0.00% sleep
0 root 1 0 0 0K 0K WAIT 0:00 0.00% swapper
25 root 1 -36 -155 0K 16K WAIT 0:00 0.00% swi3: ip6opt ipopt
7 root 1 8 0 0K 16K - 0:00 0.00% thread taskq
37 root 1 4 0 0K 16K select 0:00 0.00% if_pic_listen0
3147 root 1 4 0 1668K 296K - 0:00 0.00% nfsd
45 root 1 4 0 0K 16K purge_ 0:00 0.00% kern_pir_proc
41 root 1 0 0 0K 16K select 0:00 0.00% if_pfe_listen
6 root 1 8 0 0K 16K - 0:00 0.00% mastership taskq
35 root 1 96 0 0K 16K sleep 0:00 0.00% netdaemon
28 root 1 20 0 0K 16K psleep 0:00 0.00% vmdaemon
49 root 1 8 0 0K 16K - 0:00 0.00% nfsiod 2
47 root 1 8 0 0K 16K - 0:00 0.00% nfsiod 0
48 root 1 8 0 0K 16K - 0:00 0.00% nfsiod 1
43 root 1 4 0 0K 16K cb-pol 0:00 0.00% cb_poll
40 root 1 4 0 0K 16K dump_r 0:00 0.00% kern_dump_proc
21 root 1 8 0 0K 16K usbtsk 0:00 0.00% usbtask
50 root 1 8 0 0K 16K - 0:00 0.00% nfsiod 3
39 root 1 4 0 0K 16K scs_ho 0:00 0.00% scs_housekeeping
17 root 1 -12 -131 0K 16K WAIT 0:00 0.00% swi9: Giant taskq
16 root 1 -16 -135 0K 16K WAIT 0:00 0.00% swi8: +
12 root 1 -24 -143 0K 16K WAIT 0:00 0.00% swi6: vm
26 root 1 -32 -151 0K 16K WAIT 0:00 0.00% swi4: ip6mismatch+
23 root 1 -64 -183 0K 16K WAIT 0:00 0.00% irq15: ata1
12.12 System Storage
Displays statistics about the amount of free disk space in the routers file systems.
Juniper systems may sometimes run out of system storage capacity, commonly while
performing a software upgrade of the device. This article lists the files that can be safely
removed from the device in order to increase the storage capacity of the file system.
Table describes the output fields for the "show system storage" command
Field Name Field Description

Filesystem Name of the filesystem.
Size Size of the filesystem.
Used Amount of space used in the filesystem.
Avail Amount of space available in the filesystem.
Capacity Percentage of the filesystem space that is being used.
Mounted on Directory in which the filesystem is mounted.
{master}
user@ROUTER> show system storage
Filesystem Size Used Avail Capacity Mounted on
/dev/ad0s1a 3.5G 473M 2.7G 15% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/md0 77M 77M 0B 100% /packages/mnt/jbase
/dev/md1 42M 42M 0B 100% /packages/mnt/jkernel64-14.1R4.10
/dev/md2 285M 285M 0B 100% /packages/mnt/jpfe-X960-14.1R4.10
/dev/md3 5.4M 5.4M 0B 100% /packages/mnt/jdocs-14.1R4.10
/dev/md4 117M 117M 0B 100% /packages/mnt/jroute-14.1R4.10
/dev/md5 44M 44M 0B 100% /packages/mnt/jcrypto64-14.1R4.10
/dev/md6 70M 70M 0B 100% /packages/mnt/jpfe-common-14.1R4.10
/dev/md7 190K 190K 0B 100% /packages/mnt/jplatform-14.1R4.10
/dev/md8 508M 508M 0B 100% /packages/mnt/jruntime-14.1R4.10
/dev/md9 41M 41M 0B 100% /packages/mnt/jruntime64-14.1R4.10
/dev/md10 12M 12M 0B 100% /packages/mnt/py-base-i386-14.1R4.10
/dev/md11 7.9G 16K 7.2G 0% /tmp
/dev/md12 7.9G 16M 7.2G 0% /mfs
/dev/ad0s1e 393M 62K 362M 0% /config
procfs 4.0K 4.0K 0B 100% /proc
/dev/ad1s1f 16G 4.8G 9.6G 33% /var
12.13 FPC and PIC status
Display the online state/status of the individual components such as Flexible PIC Concentrator
(FPC) installed.
 For all active boards, the state field must be online.
{master}
user@ROUTER> show chassis fpc
Temp CPU Utilization (%) Memory Utilization (%)
Slot State (C) Total Interrupt DRAM (MB) Heap Buffer
0 Empty
1 Online 27 6 0 2048 10 13
2 Online 27 7 0 2048 9 13
3 Online 35 16 5 2048 13 13
4 Online 37 7 0 2048 13 13
5 Empty
12.14 FPC Health
Display the CPU utilization
{master}
0 Empty
1 Online 27 6 0 2048 10 13
2 Online 27 7 0 2048 9 13
3 Online 35 16 5 2048 13 13
4 Online 37 7 0 2048 13 13
5 Empty
12.15 FPC Temp
Display the temp utilization.
{master}
0 Empty
1 Online 27 6 0 2048 10 13
2 Online 27 7 0 2048 9 13
3 Online 35 16 5 2048 13 13
4 Online 37 7 0 2048 13 13
5 Empty
12.16 Knowing the Optics
{master}
user@ROUTER> show chassis fpc pic-status
Slot 1 Online MPCE Type 1 3D
PIC 0 Online 10x 1GE(LAN) RJ45
Slot 2 Online MPCE Type 1 3D
PIC 0 Online 10x 1GE(LAN) SFP
PIC 1 Online 10x 1GE(LAN) SFP
Slot 3 Online MPC 3D 16x 10GE
PIC 0 Online 4x 10GE(LAN) SFP+

Slot 4 Online MPC 3D 16x 10GE
{master}
user@ROUTER> show chassis pic fpc-slot 3 pic-slot 0
FPC slot 3, PIC slot 0 information:
Type 4x 10GE(LAN) SFP+
State Online
PIC version 0.0
PIC port information:

Fiber Xcvr vendor Wave- Xcvr
Port Cable type type Xcvr vendor part number length Firmware
0 10GBASE SR MM FINISAR CORP. FTLX8571D3BNL-J1 850 nm 0.0
1 10GBASE LR SM FINISAR CORP. FTLX1471D3BNL-J1 1310 nm 0.0
2 10GBASE SR MM CISCO-AVAGO SFBR-709SMZ-CS1 850 nm 0.0
3 10GBASE SR MM FINISAR CORP. FTLX8571D3BNL-J1 850 nm 0.0

At JUNOS Health Check v1.0

Hochgeladen von

Dokumentinformationen

Copyright

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

At JUNOS Health Check v1.0

Hochgeladen von

Copyright:

JUNOS Monitoring & Health Check Document

Severity Severity Severity Description

interactive- Logs any interactive commands issued by users on the router.

Table 1: Log files

2.1 Managing the log files

2.2 Viewing the log files

3 Checking who’s on the Router

> show system users

3.1 Forced log out

> request system logout <login name>

JUNOS Monitoring & Health Check Document

3.2 Send message to all users

> request message all message "End router session now!"

3.3 Send message to particular user

Display a message on the screens of particular user-name logged in to the router.

4 Simple Network Management Protocol (SNMP)

> show snmp statistics

In addition to logging system events, Junos OS software allows you to monitor

> show log log-ddos

For example on Juniper routers, traceoptions is enabled to monitor the routing

> show log ospf-errors

7 Checking Host-to-Host with the ping command

8 Tracerouting the Network

Figure 1: Traceroute demonstration

> show interfaces (no modifier)

9.2 Monitoring Interface Counters

> monitor interface <interface-ID>

9.3 Clearing Interface Counters

10 Monitoring the Routing Information

> show ospf neighbor

> show ospf neighbor instance <instance-name>

> show bgp neighbor

11 Real-time Performance Monitoring

Protocol and Transmission Control Protocol (UDP/TCP) packets with user-

If required, please read on the below link.

12 Monitoring the Router Hardware

Display all the current environmental data for the device.

Field name Description

12.2 Chassis Alarm Status

This usually indicates a power source problem.

12.3 Craft Display

It provides a console/remote session display of the current alarms and control

To view status and troubleshooting information at a glance and to perform many

Figure 1 demonstrate craft interface of the Juniper Networks MX960 router.

user@Router> show chassis craft-interface

Front Panel Alarm Indicators:

Front Panel FPC LEDs:

Fan Tray LEDs:

12.4 Hardware Inventory

Xcvr 0 REV 01 740-031980 AQA3TYJ SFP+-10G-SR

12.5 Routing Engine (RE) Status

12.6 System Uptime Status

Displays how long a device has been up and running.

12.7 System Reboot Status

12.8 Last Commit Status

12.9 Usage of Junos OS Kernel Memory

12.10 Usage of Task Memory

Displaying memory utilization status on the system: ROUTER

12.11 System Process

3110 root 1 4 0 118M 30272K kqread 198:56 0.10% rpd

3144 root 1 96 0 36028K 2660K select 0:20 0.00% smihelperd

3145 root 1 96 0 5156K 2680K select 0:00 0.00% kod

12.12 System Storage

Field Name Field Description

12.13 FPC and PIC status

 For all active boards, the state field must be online.

12.14 FPC Health