Professional Documents
Culture Documents
At JUNOS Health Check v1.0
At JUNOS Health Check v1.0
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:
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.
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"
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.
© Nokia 2014
2015-09– 05/ 66
specific screens. The message goes to everyone currently logged in to the router.
> request message user <login name> message "End router session now!"
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
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.
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.
JUNOS Monitoring & Health Check Document
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.
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.
http://www.juniper.net/documentation/en_US/junos14.2/topics/concept/real-time-
performance-monitoring-overview.html
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.
Display if there were any fan failures, power supply failures, and so forth, they
should show up in the "show chassis alarms" command.
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
JUNOS Monitoring & Health Check Document
Routing Engine 0 1
--------------------------
OK * *
Fail . .
Master * .
CB LEDs:
CB 0 1
--------------
Amber . .
Green * *
PS LEDs:
PS 0 1 2 3
--------------------
Red . . . .
Green * * * *
© Nokia 2014
JUNOS Monitoring & Health Check Document
FT 0
----------
Red .
Green *
{master}
user@ROUTER>
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.
JUNOS Monitoring & Health Check Document
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
PIC 1 BUILTIN BUILTIN 10x 1GE(LAN) RJ45
PIC 2 BUILTIN BUILTIN 10x 1GE(LAN) RJ45
PIC 3 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
PIC 1 BUILTIN BUILTIN 4x 10GE(LAN) SFP+
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
PIC 2 BUILTIN BUILTIN 4x 10GE(LAN) SFP+
© Nokia 2014
JUNOS Monitoring & Health Check Document
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.
JUNOS Monitoring & Health Check Document
{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
Uptime 42 days, 11 hours, 11 minutes, 58 seconds
Last reboot reason Router rebooted after a normal shutdown.
Load averages: 1 minute 5 minute 15 minute
0.04 0.01 0.00
JUNOS Monitoring & Health Check Document
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.
JUNOS Monitoring & Health Check Document
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
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.
JUNOS Monitoring & Health Check Document
Display standard information about memory utilization for routing protocol tasks
on the routing engine on all logical systems.
{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>
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
JUNOS Monitoring & Health Check Document
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
{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
JUNOS Monitoring & Health Check Document
Display the online state/status of the individual components such as Flexible PIC Concentrator
(FPC) installed.
{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
{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
JUNOS Monitoring & Health Check Document
{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
{master}
user@ROUTER> show chassis fpc pic-status
Slot 1 Online MPCE Type 1 3D
PIC 0 Online 10x 1GE(LAN) RJ45
PIC 1 Online 10x 1GE(LAN) RJ45
PIC 2 Online 10x 1GE(LAN) RJ45
PIC 3 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+
JUNOS Monitoring & Health Check Document
{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
Uptime 42 days, 12 hours, 6 minutes, 43 seconds