Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos Fusion] Satellite Device (SD) - FAQs for how to login, identify, monitor, and troubleshoot

0

0

Article ID: KB31479 KB Last Updated: 16 Mar 2018Version: 3.0
Summary:

The Junos Fusion solution is composed of an Aggregation device (AD) and multiple Satellite devices (SD). Each satellite device has at least one connection to the aggregation device. The satellite devices provide interfaces that send and receive network traffic. Network traffic can be forwarded to the aggregation device within the Junos Fusion.

This document covers an extensive list of debugging commands that can be run on the Satellite Device for data collection.

Solution:

Frequently Asked Questions (FAQ):

  1. How to login to Satellite Device Host OS Shell
  2. How to identify the current version of Linux Host OS running on Satellite Device
  3. How to Identify the SNOS version running on Satellite Device from Satellite Shell
  4. How to run any Linux Shell Command on SD by staying on AD Junos CLI
  5. What are the key processes running on Satellite Device w.r.t Junos Fusion?
  6. What log files to check on Host OS to understand the reason for failed SNOS upgrade fails?
  7. What data needs to be collected from Host OS to determine the cause of last reboot of Satellite Device?
  8. What log files are required to investigate the cause of last SD reboot?
  9. What are the satellite daemon specific log files available on the Host OS?
  10. How to restart a particular satellite process daemon on multiple Satellite Devices at once
  11. How to check the IP assigned to the Satellite Loopback and Uplink Ports for In-Band Management
  12. How to check the reachability of Aggregation Device from the Satellite Host OS Shell
  13. How to determine the Mgmt. IP Configured on the Aggregate device Cascaded and Loopback interface for in-band communication
  14. How to login into the Aggregation Device Junos CLI from Satellite Host Shell
  15. How to login to SD PFE from Host OS Shell prompt
  16. How to check the core dump files on SD Host OS
  17. How to copy files from SD Host OS to Aggregate Device
  18. How to monitor traffic statistics along with error and drop counts on all the uplink ports of Satellite device
  19. How to verify the CPU utilization in real time on Satellite Host OS
  20. How to identify the Satellite BIOS version from the satellite host shell
  21. How to determine the current time and uptime of SD from Host OS Shell
  22. How to determine the serial number of Satellite device from Host OS Shell
  23. How to list the users that have logged on to Satellite Device from Host OS Shell
  24. How to get the last login history of a particular user on a satellite device
  25. How to determine the last reboot and historic reboot date & time on the Satellite Host OS
  26. How to list the Linux command line history along with timestamp for investigation/auditing purposes
  27. How to perform the real-time operating temperature of Satellite Device
  28. How to view the Virtual Memory Statistics on Satellite Host OS
  29. How to Determine the Model, Serial Number and Size of Connected hard drives on Satellite Devices
  30. How to check hard disk partitions, partition size, file system type and mount point.
  31. How to check the total size, current use and use % for hard disk partitions from Satellite Host OS
  32. How to test the readable speed of HDD from Satellite Host OS Shell
  33. How to perform health Check on the Hard Disk Drive connected on Satellite Device
  34. How to monitor the hard disk drive device I/O statistics
  35. How to see the hardware specification of installed RAM on the Satellite Host
  36. How to view the network/system statistics on a Satellite Device
  37. How to view PSU locally from a Satellite Device
  38. How to capture LLDP initial Discovery history from Satellite Device
  39. How to capture LLDP statistics from Satellite Device
  40. List of Satellite Commands available in RSI
  41. Shell Command on SD to TCPDump LLDP Packet
  42. How to check Routing table on Satellite Device
===========================================================================================

1. How to Login to Satellite Device Host OS Shell

Procedure 1: Using root/satellite credentials this can be done below Junos CLI from Aggregation Device
 
labroot@Aggregation-Device> request chassis satellite login fpc-slot 101
Warning: Permanently added '172.16.0.101' (ECDSA) to the list of known hosts.
sd101:~$

Procedure 2:  Using root/satellite credentials this can be done below Junos CLI from Aggregation Device
 
labroot@Aggregation-Device> request chassis satellite login interface-name xe-1/2/1
Warning:P manently added '10.0.144.6' (ECDSA) to the list of known hosts.
Last login: Tue Mar 1 08:17:03 2016 from 172.16.255.1
sd101:~$

Procedure 3  Using root/satellite credentials this can be done below Junos CLI from Aggregation Device
 
labroot@Aggregation-Device> ssh routing-instance __juniper_private4__ labroot@10.0.144.2
The authenticity of host '10.0.144.2 (10.0.144.2)' can't be established.
ECDSA key fingerprint is 01:1c:2b:8c:4c:29:3b:d8:b9:16:ef:df:02:ec:1c:6d.
Are you sure you want to continue connecting (yes/no)? yes
Last login: Tue Mar 1 08:22:55 2016 from 10.0.144.5
sd101:~

Procedure 4: Using root credentials we can directly log into the Satellite device through console por

2. How to identify the current version of Linux Host OS running on Satellite Device
 
sd101:~$ cat /etc/issue
Wind River Linux 6.0.0.21 \n \l
(Back to List)

3. How to Identify the SNOS version running on Satellite Device from Satellite Shell
 
sd101:~$ cat /etc/app-version
Version: 1.0R3
Installed: Sat Dec 5 18:42:30 2015
sd101:~$ cat /etc/host-version
HOST_VERSION=3.0.1
sd101:~$
sd101:~$ cat /etc/version
201602121523
sd101:~$
(Back to List)

4. How to run any Linux Shell Command on SD by staying on AD Junos CLI
 
It is possible from the Junos CLI on AD – We can run any Linux command on a particular SD or a group of SD’s.

labroot@Aggregation-Device> request chassis satellite shell-command ?
Possible completions:
<remote-command> Remote fpc shell command
fpc-slot Satellite slot number (100..254)
range Slot range as <start-end> slot number (e.g. 100-110)
labroot@Aggregation-Device> request chassis satellite shell-command fpc-slot 101 ?
Possible completions:
<remote-command> Remote fpc shell command
(Back to List)

5. What are the key processes running on Satellite Device w.r.t Junos Fusion?
 
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 2464 0.0 0.0 4184 2284 ? S 2015 6:00 /usr/local/bin/dpd
root 2478 20.3 0.7 539212 61172 ? Sl 2015 23932:21 /usr/local/bin/spfe
root 2510 0.1 0.1 91256 10264 ? S 2015 147:15 python2.7 /usr/local/bin/amd
root 2521 0.0 0.0 13164 2540 ? Sl 2015 0:07 /usr/local/bin/ppman
root 2535 0.0 0.0 13164 2548 ? Sl 2015 0:25 /usr/local/bin/ppman-lite
labroot 12706 0.0 0.0 4396 516 pts/0 S+ 09:48 0:00 grep /usr/local/bin/
root 19493 0.0 0.0 287956 3396 ? SLsl 2015 85:26 /usr/local/bin/lcmd
(Back to List)

6. What log files to check on Host OS to understand the reason for failed SNOS upgrade?

The following files in the /var/log directory can be inspected to determine the root cause for a failed upgrade.
 
sd101:~$ ls -ltr /var/log/
-rw-rw-rw- 1 root root 0 Sep 17 17:01 amd.log
-rw-rw-rw- 1 root root 954974 Feb 26 09:40 amd_jrpc.log
-rw-r----- 1 root root 118661 Mar 1 09:40 messages
-rw-r--r-- 1 root root 20257 Dec 5 18:43 postinstall.log
-rw-rw-rw- 1 root root 3457 Dec 5 18:42 sw_update.log
-rw-r--r-- 1 root root 1002478 Dec 5 18:42 v44_installer.log
(Back to List)

7. What data needs to be collected from Host OS to determine the cause of last reboot of Satellite Device?
 
There could be several reasons for a Satellite Device failure such as:
a) Power Failures.
b) Accidental/Intentional Hard Reset.
c) Manual Reboot.
d) Memory /CPU Errors.
e) Unrecoverable Hardware errors.
a) High CPU.
b) Kernel/Application Malfunction.
c) Low Disk Space

We can collect the following output from the Host OS Shell to start the investigation along with inspecting the files in /var/log/ directory :
Commands Descriptions

dmesg - Will print kernel ring buffer. Captures boot time messages helpful for debugging
last reboot  - List reboot history along with the time stamp.
sensors -  Displays Device temp.
history -  List Command History ran on Linux Shell
who -b  - List the last reboot time of the device
df -h | grep ^/dev - List used and available disk space.
Vmstat -s - Dumps Memory Statistiscs.
top - List cpu and memory utilization in real time.

sd202:~$ dmesg
[340169.570236] lcmd[27702]: segfault at f0 ip 0000000045b9eb52 sp 00000000f72f3cb4 error 4 in libc-2.18.so[45b1d000+1a3000]
[340229.626729] lcmd[28253]: segfault at f0 ip 0000000045b9eb52 sp 00000000f7336cb4 error 4 in libc-2.18.so[45b1d000+1a3000]
[4774840.470425] dmar: DRHD: handling fault status reg 2
[4774840.513021] dmar: DMAR:[DMA Read] Request device [09:00.0] fault addr a7a7a000
DMAR:[fault reason 06] PTE Read access is not set
[5761130.848350] spfe[1916]: segfault at 5 ip 00000000f471e762 sp 00000000d71feee0 error 4 in libtoolkits.so[f4714000+12000]
[5766741.744330] Netfilter messages via NETLINK v0.30.
[5766741.761558] device eth0 entered promiscuous mode
[5766741.767262] device eth0 left promiscuous mode
[5766748.813989] device eth0 entered promiscuous mode
[5766748.819805] device eth0 left promiscuous mode
[5766756.275607] device eth0 entered promiscuous mode
[5766756.281348] device eth0 left promiscuous mode
[5766768.312514] device eth0 entered promiscuous mode
[5766768.318282] device eth0 left promiscuous mode
[5766773.087819] device eth0 entered promiscuous mode
[5766773.093605] device eth0 left promiscuous mode
[5768152.160991] device xe-0-0-0 entered promiscuous mode
[5768191.603258] device xe-0-0-0 left promiscuous mode
[5768206.488442] device ge-0-0-49 entered promiscuous mode
[5768214.523687] device ge-0-0-49 left promiscuous mode


sd202:~$ last reboot
reboot system boot 3.10.62-ltsi-WR6 Tue Jun 21 13:12 - 16:58 (75+03:46)
reboot system boot 3.10.62-ltsi-WR6 Sun Jun 5 20:12 - 13:11 (15+16:58)
reboot system boot 3.10.62-ltsi-WR6 Tue May 31 23:28 - 20:11 (4+20:42)
reboot system boot 3.10.62-ltsi-WR6 Tue May 31 23:28 - 20:11 (4+20:43)
reboot system boot 3.10.55-ltsi-WR6 Sat May 28 16:50 - 23:25 (3+06:35)
reboot system boot 3.10.55-ltsi-WR6 Sat May 28 16:49 - 23:25 (3+06:36)
reboot system boot 3.10.62-ltsi-WR6 Sat May 28 16:39 - 16:47 (00:08)
reboot system boot 3.10.62-ltsi-WR6 Sat May 28 16:39 - 16:47 (00:08)
reboot system boot 3.10.55-ltsi-WR6 Thu May 19 21:19 - 16:36 (8+19:16)
reboot system boot 3.10.55-ltsi-WR6 Thu May 19 21:19 - 16:36 (8+19:16)
reboot system boot 3.10.62-ltsi-WR6 Thu May 19 21:09 - 21:17 (00:07)
reboot system boot 3.10.62-ltsi-WR6 Thu May 19 21:09 - 21:17 (00:07)
reboot system boot 3.10.62-ltsi-WR6 Sun May 15 21:49 - 21:07 (3+23:17)
reboot system boot 3.10.62-ltsi-WR6 Sun May 15 21:49 - 21:07 (3+23:17)


sd202:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +29.8 C (crit = +100.0 C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +51.0 C (high = +86.0 C, crit = +100.0 C)
Core 0: +51.0 C (high = +86.0 C, crit = +100.0 C)
Core 1: +47.0 C (high = +86.0 C, crit = +100.0 C)


sd202:~$ top
top - 17:02:04 up 75 days, 3:50, 1 user, load average: 0.07, 0.14, 0.15
Tasks: 100 total, 1 running, 94 sleeping, 0 stopped, 5 zombie
Cpu(s): 3.5%us, 0.9%sy, 0.0%ni, 95.5%id, 0.1%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 7900528k total, 631808k used, 7268720k free, 169836k buffers
Swap: 583980k total, 0k used, 583980k free, 239992k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
17165 root 20 0 529m 70m 15m S 20 0.9 2283:35 spfe
2447 root 20 0 99.8m 1876 1424 S 0 0.0 251:35.64 monit
28382 labroot 20 0 15204 1096 840 R 0 0.0 0:00.01 top
1 root 20 0 4208 680 596 S 0 0.0 1:38.57 init
2 root 20 0 0 0 0 S 0 0.0 0:00.31 kthreadd
3 root 20 0 0 0 0 S 0 0.0 4:02.40 ksoftirqd/0
5 root 0 -20 0 0 0 S 0 0.0 0:00.00 kworker/0:0H
7 root RT 0 0 0 0 S 0 0.0 0:13.48 migration/0
8 root 20 0 0 0 0 S 0 0.0 18:00.42 rcu_preempt
9 root 20 0 0 0 0 S 0 0.0 0:00.00 rcu_bh
10 root 20 0 0 0 0 S 0 0.0 0:00.00 rcu_sched
11 root RT 0 0 0 0 S 0 0.0 0:24.50 migration/1
12 root 20 0 0 0 0 S 0 0.0 2:20.81 ksoftirqd/1
14 root 0 -20 0 0 0 S 0 0.0 0:00.00 kworker/1:0H
15 root RT 0 0 0 0 S 0 0.0 0:13.26 migration/2
16 root 20 0 0 0 0 S 0 0.0 3:46.75 ksoftirqd/2
18 root 0 -20 0 0 0 S 0 0.0 0:00.00 kworker/2:0H
19 root RT 0 0 0 0 S 0 0.0 0:24.67 migration/3
20 root 20 0 0 0 0 S 0 0.0 2:24.80 ksoftirqd/3
22 root 0 -20 0 0 0 S 0 0.0 0:00.00 kworker/3:0H
(Back to List)

8. What log files are required to investigate the cause of last SD reboot?
 
The following files in the /var/log directory can be inspected to determine the last reboot reason.
-rw-r----- 1 root root 1608 Sep 3 02:39 boot
-rw-r----- 1 root root 259570 Sep 3 02:39 debug
-rw-r--r-- 1 root root 6047 Sep 3 02:40 lcmd.log
-rw-r--r-- 1 root root 231 Aug 25 04:46 mcelog
-rw-r----- 1 root root 782346 Sep 3 02:59 messages
-rw-r--r-- 1 root root 0 Aug 27 02:08 reboots.log
-rw-r----- 1 root root 4316082 Sep 3 02:59 syslog
-rw-r----- 1 root root 13436 Sep 3 02:39 user.log
-rw-r----- 1 root root 1010968 Sep 3 02:59 kern.log
(Back to List)

9. What are the satellite daemon specific log files available on the Host OS?
 
file name location Info

dpd.log /var/log Records Device Discovery and provsioning logs.
ppman.log /var/log Records PPMan events. PPMan prcoess is reposible for periodic packet management of LACP & STP protocol.
ppman-lite.log /var/log Records PPM-Lite evetns. PPMLite prcoess is reposible for periodic packet management of LLDP protocol.
lcmd.log /var/log Records Evironmental & FRU's events.
spfe.log /var/log Records Satellite PFE logs.
amd_jrpc.log /var/log Records communication logs with SDPD and SPMD.
mcelog /var/log Records Hardware Errors / fault information
(Back to List)

10. How to restart a particular satellite process daemon on multiple Satellite device at once?
 
Satellite specific daemons like DPD, SPFE, LCMD & AMD can be restarted directly from the Aggregation Device using the following JUNOS CLI command :

“request chassis satellite restart <process-name>”

Importantly from the Aggregate device is it possible to restart same process of multiple satellite device at once.

labroot@Aggregation-Device> request chassis satellite restart ?
Possible completions:
api-management-daemon AMD process
chassis-management-daemon LCMD process
discovery-and-provisioning-daemon DPD process
fpc-slot Satellite slot number (100..254)
packet-forwarding-engine SPFE process
ppman PPMAN process
ppman-lite PPMAN-lite process
range Slot range as <start-end> slot number (e.g. 100-110)
Alternatively we could manually the kill the PID of the desired process from the Host OS shell of a satellite device using our favorite “kill” command.
root@sd201:~# ps -aux | grep lcmd
root 2790 0.0 0.0 278172 3152 ? SLsl 02:39 0:23 /usr/local/bin/lcmd
root@sd201:~# kill -9 2790
(Back to List)

11. How to check the IP assigned to the Satellite Loopback and Uplink Ports for In-Band Management?
 
sd202:~# ifconfig | grep "inet addr:" -C 2
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
lo:0 Link encap:Local Loopback
inet addr:172.16.0.202 Mask:255.255.255.255
UP LOOPBACK RUNNING MTU:65536 Metric:1
xe-0-0-0c Link encap:Ethernet HWaddr 40:a6:77:d9:08:c5
inet addr:10.0.128.10 Bcast:0.0.0.0 Mask:255.255.255.252
inet6 addr: fe80::42a6:77ff:fed9:8c5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9192 Metric:1
xe-0-0-1c Link encap:Ethernet HWaddr 40:a6:77:d9:08:c6
inet addr:10.0.136.10 Bcast:0.0.0.0 Mask:255.255.255.252
inet6 addr: fe80::42a6:77ff:fed9:8c6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9192 Metric:1
(Back to List)

12. How to check the reachability of Aggregation Device from the Satellite Host OS Shell?
 
sd202:~# ip -s neighbor list
10.0.128.9 dev xe-0-0-0c lladdr a8:d0:e5:f3:02:97 ref 1 used 41610/0/734 probes 0 REACHABLE
10.0.136.9 dev xe-0-0-1c lladdr a8:d0:e5:f3:03:3c ref 1 used 40452/0/51 probes 1 REACHABLE
sd202:~# arp -e
Address HWtype HWaddress Flags Mask Iface
10.0.128.9 ether a8:d0:e5:f3:02:97 C xe-0-0-0c
10.0.136.9 ether a8:d0:e5:f3:03:3c C xe-0-0-1c
(Back to List)

13. How to determine the Mgmt. IP Configured on the Aggregate device Cascaded and Loopback interface for in-band communication?
 
Note: The route table on Host OS contains prefixes which is used for Internal ( In-Band Communication) between Aggregate and Satellite device.

sd202:~# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.0.128.8 0.0.0.0 255.255.255.252 U 0 0 0 xe-0-0-0c
10.0.136.8 0.0.0.0 255.255.255.252 U 0 0 0 xe-0-0-1c
172.16.0.0 10.0.128.9 255.255.0.0 UG 0 0 0 xe-0-0-0c
172.16.255.1 10.0.128.9 255.255.255.255 UGH 0 0 0 xe-0-0-0c
sd202:~# ip route
10.0.128.8/30 dev xe-0-0-0c proto kernel scope link src 10.0.128.10
10.0.136.8/30 dev xe-0-0-1c proto kernel scope link src 10.0.136.10
172.16.0.0/16 proto 5
nexthop via 10.0.128.9 dev xe-0-0-0c weight 1
nexthop via 10.0.136.9 dev xe-0-0-1c weight 1
172.16.255.1 proto 5
nexthop via 10.0.128.9 dev xe-0-0-0c weight 1
nexthop via 10.0.136.9 dev xe-0-0-1c weight 1
From the “ip route” command we could ascertain that 172.16.255.1 is management IP assigned to the loopback interface of aggregate device and 10.0.0.1 and 10.1.152.9 are the IP’s assigned to the cascaded interfaces of the aggregate device.
Also the following netstat command further suggest that the TCP connection between SD & Ad loopback interfaces are in established state for internal communication purposes.
sd202:~# netstat -tn
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 172.16.0.202:56870 172.16.255.1:65105 ESTABLISHED
tcp 0 200 172.16.0.202:22 172.16.255.1:50600 ESTABLISHED
tcp 0 0 172.16.0.202:38173 172.16.255.1:33127 ESTABLISHED
tcp 0 0 127.0.0.1:53886 127.0.0.1:56791 ESTABLISHED
tcp 0 0 172.16.0.202:5591 172.16.255.1:60705 ESTABLISHED
tcp 0 0 127.0.0.1:56791 127.0.0.1:47658 ESTABLISHED
tcp 0 0 172.16.0.202:5591 172.16.255.1:49976 ESTABLISHED
tcp 0 0 172.16.0.202:5591 172.16.255.1:63387 ESTABLISHED
tcp 0 0 172.16.0.202:39280 172.16.255.1:6011 ESTABLISHED
tcp 0 0 172.16.0.202:46481 172.16.255.1:6012 ESTABLISHED
tcp 0 0 127.0.0.1:48635 127.0.0.1:5591 ESTABLISHED
tcp 0 0 127.0.0.1:5591 127.0.0.1:48635 ESTABLISHED
tcp 0 0 127.0.0.1:56791 127.0.0.1:53886 ESTABLISHED
tcp 0 0 127.0.0.1:47658 127.0.0.1:56791 ESTABLISHED
sd202:~#
(Back to List)

14. How to Login into the Aggregation Device Junos CLI from Satellite Host Shell?
 
Note: Based on earlier examples we could determine the IP configured on Aggregate Device Cascaded Port and loopback interfaces used for internal management communication between Aggregate and Satellite devices.
To Login from Host OS Shell to Aggregate Device Junos CLI we can use the IP’s assigned to the Loopback/cascaded ports of Aggregate Device for telnet/ssh. We require root/super-user credentials to login to the aggregate device.

root@sd202:~# ssh root@172.16.255.1 --------------- Mgmt IP configured on the Loopback interface of Aggregate Device.
Password:
Last login: Tue Sep 1 00:36:46 2015 from 10.0.0.2
--- JUNOS 14.2X2 built 2015-07-15 03:38:52 UTC
labroot@AD>
root@sd202:~# telnet 10.0.0.1 ---------------- IP assigned to one of the cascaded port on AD.
Trying 10.0.0.1...
Connected to 10.0.0.1.
Escape character is '^]'.
MX480-15-WTR-RE0 (ttyp0)
login: lab
Password:
--- JUNOS 14.2X2 built 2015-07-15 03:38:52 UTC
labroot@AD>
root@sd202:~# ssh lab@10.1.152.9 ---------------- IP assigned to the second cascaded port on AD.
Password:
Last login: Wed Sep 2 05:13:29 2015 from 10.0.0.2
--- JUNOS 14.2X2 built 2015-07-15 03:38:52 UTC
(Back to List)

15. How to login to SD PFE from Host OS Shell prompt?
 
root@sd202:~# vty
connect to 127.0.0.1:33000
spfe#
root@sd202:~# telnet 127.0.0.1 33000
Trying 127.0.0.1...
Connected to 127.0.0.1.
spfe#
sd202:~$ vty -s spfe
connect to 127.0.0.1:33000
spfe#
(Back to List)

16. How to check the core dump files on SD Host OS?
 
All Crash Files are located in following location on SD Host OS : /var/tmp/corefiles
We can view the corefiles info from AD Junos CLI using the following command “show system core-dumps satellite”

sd202:~$ ls -l /var/tmp/corefiles/
total 10136
-rw-r--r-- 1 root root 258888 Jun 21 13:39 sd202.lcmd.2554.1466516365.core.tgz
-rw-r--r-- 1 root root 255551 Jun 25 11:39 sd202.lcmd.28246.1466854759.core.tgz
-rw-r--r-- 1 root root 3405254 Aug 27 04:43 sd202.spfe.17403.1472273018.core.tgz
(Back to List)

17. How to copy files from SD Host OS to Aggregate Device?
 
Note: FTP does not seem to work on Host OS but SCP works seamlessly as long as SSH is enabled on Aggregate Device.
scp <source-file-location-on-SD> user@x.x.x.x:/<destination-directory-on-Aggregate-device>
scp –r <source-directory-location-on-SD> user@x.x.x.x:/<destination-directory-on-Aggregate-device>
sd202:~# scp -r /var/tmp/corefiles/ root@172.16.255.1:/var/tmp/
sd202.spfe.2959.1440834396.core.tgz 100% 3022KB 3.0MB/s 00:00
sd202.spfe.3135.1440834474.core.tgz 100% 2955KB 2.9MB/s 00:00
sd202.spfe.3528.1440844114.core.tgz 100% 2978KB 2.9MB/s 00:01
sd202.spfe.2622.1440829820.core 100% 164MB 9.6MB/s 00:17
(Back to List)

18. How to monitor traffic statistics along with error and drop counts on all the uplink ports of Satellite device
 
Note: From the Satellite Host OS Shell Prompt we can only monitor the statistics of uplink and loopback ports. The extended ports can be monitored from Aggregate device or from Satellite Device PFE. We can use the following three command to monitor the interface statistics such as Rx/Tx count, errors & drops count on uplink ports :
i. Ifconfig
ii. netstat –i.
iii. ip -s link

sd202:~# ifconfig xe-0-0-1c
xe-0-0-1c Link encap:Ethernet HWaddr 40:a6:77:d9:08:c6
inet addr:10.0.136.10 Bcast:0.0.0.0 Mask:255.255.255.252
inet6 addr: fe80::42a6:77ff:fed9:8c6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9192 Metric:1
RX packets:18180720 errors:0 dropped:0 overruns:0 frame:0
TX packets:14717695 errors:0 dropped:4 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:3772348240 (3.5 GiB) TX bytes:4666416647 (4.3 GiB)
sd202:~# ifconfig xe-0-0-0c
xe-0-0-0c Link encap:Ethernet HWaddr 40:a6:77:d9:08:c5
inet addr:10.0.128.10 Bcast:0.0.0.0 Mask:255.255.255.252
inet6 addr: fe80::42a6:77ff:fed9:8c5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9192 Metric:1
RX packets:1345545 errors:0 dropped:0 overruns:0 frame:0
TX packets:1337641 errors:0 dropped:12 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:320491807 (305.6 MiB) TX bytes:407798608 (388.9 MiB)
sd202:~$ netstat -i
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 4625096 0 0 0 6 0 0 0 BMRU
ge-0-0-49 1518 0 0 0 0 0 16 0 0 0 BMRU
ge-0-0-49c 1518 0 0 0 0 0 16 0 0 0 BMRU
lo 65536 0 2109474 0 0 0 2109474 0 0 0 LRU
lo:0 65536 0 - no statistics available - LRU
lo-prv 1514 0 0 0 0 0 24 0 0 0 BMRU
lo-pub 1514 0 0 0 0 0 24 0 0 0 BMRU
xe-0-0-0 9192 0 0 0 0 0 70 0 0 0 BMRU
xe-0-0-1 9192 0 0 0 0 0 77 0 0 0 BMRU
xe-0-0-0c 9192 0 1345189 0 0 0 1337329 0 12 0 BMRU
xe-0-0-1c 9192 0 18180395 0 0 0 14717460 0 4 0 BMRU
sd202:~# ip -s link
8: xe-0-0-0c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9192 qdisc pfifo_fast state UP mode DEFAULT qlen 500
link/ether 40:a6:77:d9:08:c5 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
320560025 1345901 0 0 0 0
TX: bytes packets errors dropped carrier collsns
407869548 1338045 0 12 0 0
10: xe-0-0-1c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9192 qdisc pfifo_fast state UP mode DEFAULT qlen 500
link/ether 40:a6:77:d9:08:c6 brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
3772420322 18181080 0 0 0 0
TX: bytes packets errors dropped carrier collsns
4666643322 14717959 0 4 0 0
(Back to List)

19. How to verify the CPU utilization in real time on Satellite Host OS?
 
There exist several linux command to get this information:

top : This command will provide real time cpu & memory utilization per ~3 seconds.
sar -u 2 : This command wil ldiplay average CPU utilization every seconds till the time command is aborted.
sar -u 2 5 : This command will display average cpu utilization every 2 sounds for 5 such occurrence.
mpstat –P All : This command will display cpu utilization of individual physical CPU’s and average of all CPU.
mpstat -P ALL 2 5 : This command will display same output every 2 seconds for 5 times.

sd202:~# sar -u 2 5
Linux 3.10.62-ltsi-WR6.0.0.21_standard (sd202) 08/28/16 _x86_64_ (4 CPU)
05:47:41 CPU %user %nice %system %iowait %steal %idle
05:47:43 all 3.69 0.00 0.89 0.00 0.00 95.42
05:47:45 all 3.16 0.00 1.14 0.00 0.00 95.70
05:47:47 all 3.92 0.00 0.63 0.13 0.00 95.32
sd202:~# mpstat -P ALL
Linux 3.10.62-ltsi-WR6.0.0.21_standard (sd202) 08/28/16 _x86_64_ (4 CPU)
05:48:34 CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle
05:48:34 all 3.44 0.00 0.87 0.06 0.00 0.00 0.00 0.00 0.00 95.62
05:48:34 0 4.76 0.00 0.99 0.13 0.00 0.00 0.00 0.00 0.00 94.12
05:48:34 1 1.26 0.00 0.81 0.01 0.00 0.00 0.00 0.00 0.00 97.92
(Back to List)

20. How to identify the Satellite BIOS version from the satellite host shell?
 
sd202:~# dmidecode -s bios-version
V0018.1
From Aggregation Device :-
labroot@AD> show chassis routing-engine bios satellite
Routing Engine BIOS Version: FPC 101: V0018.1
Routing Engine BIOS Version: FPC 202: V0018.1
(Back to List)

21. How to determine the serial number of Satellite device from Host OS Shell ?
 
sd202:~# dmidecode -t 1
# dmidecode 2.12
SMBIOS 2.7 present.
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Juniper Networks
Product Name: 0BDD
Version: 02 09 REV 09
Serial Number: VB3715060116
UUID: 12345678-1234-5678-90AB-CDDEEFAABBCC
Wake-up Type: Power Switch
SKU Number: Type1Sku0
Family: Type1Family
(Back to List)

22. How to determine the current time and uptime of SD from Host OS Shell?
 
sd202:~# date
Sun Aug 28 06:00:53 UTC 2016
sd202:~# uptime
06:00:55 up 67 days, 16:49, 1 user, load average: 0.26, 0.18, 0.16


Explanation:
- The current time (06:00:55)
- How long the system has been running (up 67 days, 16 hours and 49 minutes )
- How many users are currently logged on (1 user)
- The system load averages for the past 1, 5, and 15 minutes (0.26, 0.18, 0.16)
(Back to List)

23. How to list the users that have logged on to Satellite Device from Host OS Shell?
 
sd202:~# w
06:08:51 up 67 days, 16:57, 1 user, load average: 0.05, 0.09, 0.12
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
labroot pts/0 05:56 3.00s 0.00s 0.00s sshd: labroot [priv]
sd202:~# who am i
labroot pts/0 Aug 28 05:56 (172.16.255.1)
(Back to List)

24. How to get the last login history of a particular user on a satellite device?
 
sd202:~# last <----------- prints out the login/out history of all users
labroot pts/0 172.16.255.1 Sun Aug 28 05:56 still logged in
labroot pts/0 172.16.255.1 Sun Aug 28 05:21 - 05:51 (00:29)
labroot pts/0 172.16.255.1 Sun Aug 28 05:20 - 05:21 (00:00)
labroot pts/0 172.16.255.1 Sun Aug 28 05:05 - 05:20 (00:14)
sd202:~# last <user-name> <----------- prints out the login/out history of the specified user
sd202:~# last labroot
labroot pts/0 172.16.255.1 Sun Aug 28 05:56 still logged in
labroot pts/0 172.16.255.1 Sun Aug 28 05:21 - 05:51 (00:29)
labroot pts/0 172.16.255.1 Sun Aug 28 05:20 - 05:21 (00:00)
labroot pts/0 172.16.255.1 Sun Aug 28 05:05 - 05:20 (00:14)
(Back to List)

25. How to determine the last reboot and historic reboot date & time on the Satellite Host OS?
 
sd202:~# who -b
system boot Jun 21 13:12
sd202:~# last reboot
reboot system boot 3.10.62-ltsi-WR6 Tue Jun 21 13:12 - 06:15 (67+17:03)
reboot system boot 3.10.62-ltsi-WR6 Sun Jun 5 20:12 - 13:11 (15+16:58)
reboot system boot 3.10.62-ltsi-WR6 Tue May 31 23:28 - 20:11 (4+20:42)
(Back to List)

26. How to list the linux command line history along with timestamp for investigation/auditing purposes?
 
sd202:~# export HISTTIMEFORMAT='%F %T '
sd202:~# history | more
1 2016-08-28 05:56:28 ls -l /var/tmp/
2 2016-08-28 05:56:28 ls -l /dev/sd*
3 2016-08-28 05:56:28 mount /dev/sdc1 /mnt
4 2016-08-28 05:56:28 mount /dev/sdb1 /mnt
5 2016-08-28 05:56:28 ls /mnt
6 2016-08-28 05:56:28 cp /var/tmp/amd_root.log /mnt
(Back to List)

27. How to perform the real-time operating temperature of Satellite Device?
 
sd202:~# watch -n 1 sensors <--------------- This command will perform real time monitoring ( per second) of operating SD & CPU temperature.
Every 1.0s: sensors Sun Aug 28 06:20:33 2016
acpitz-virtual-0
Adapter: Virtual device
temp1: +29.8 C (crit = +100.0 C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +49.0 C (high = +86.0 C, crit = +100.0 C)
Core 0: +48.0 C (high = +86.0 C, crit = +100.0 C)
Core 1: +45.0 C (high = +86.0 C, crit = +100.0 C)
sd202:~# sensors –A <---------------- This command will show the current device & cpu temperature.
acpitz-virtual-0
temp1: +29.8 C (crit = +100.0 C)
coretemp-isa-0000
Physical id 0: +50.0 C (high = +86.0 C, crit = +100.0 C)
Core 0: +47.0 C (high = +86.0 C, crit = +100.0 C)
Core 1: +46.0 C (high = +86.0 C, crit = +100.0 C)
(Back to List)

28. How to view the Virtual Memory Statistics on Satellite Host OS?
 
§ vmstat (virtual memory statistics) is a system monitoring tool that collects and displays summary information about operating system memory, processes, interrupts, paging and block I/O.
§ /proc/meminfo is another commonly used files in the /proc/ directory that contains large amount of valuable information about the systems RAM usage.
sd202:~# cat /proc/meminfo
MemTotal: 7900528 kB
MemFree: 7271772 kB
Buffers: 170204 kB
Cached: 235020 kB
SwapCached: 0 kB
Active: 359772 kB
Inactive: 128020 kB
Active(anon): 84988 kB
Inactive(anon): 464 kB
Active(file): 274784 kB
VmallocChunk: 34359385156 kB
HardwareCorrupted: 0 kB
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 11008 kB
DirectMap2M: 8298496 kB
sd202:~# vmstat -s
7900528 total memory
628888 used memory
359776 active memory
128040 inactive memory
7271640 free memory
170204 buffer memory
235044 swap cache
583980 total swap
583980 free swap
79348778 non-nice user cpu ticks
20159849 system cpu ticks
2204063931 idle cpu ticks
1486480 IO-wait cpu ticks
404066 pages paged in
77980043 pages paged out
522463564 interrupts
(Back to List)

29. How to Determine the Model, Serial Number and Size of Connected hardrives on Satellite Devices?
 
sd202:~# lsscsi --size
[4:0:0:0] disk ATA TS16GHSD310 2011 /dev/sda 16.0GB
[5:0:0:0] disk ATA TS16GHSD310 2011 /dev/sdb 16.0GB
sd202:~# sudo smartctl -i /dev/sda
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.10.62-ltsi-WR6.0.0.21_standard] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: TS16GHSD310
Serial Number: 20140522B42278025818
Firmware Version: 20111220
User Capacity: 16,013,852,672 bytes [16.0 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ACS-2 (revision not indicated)
Local Time is: Sun Aug 28 06:45:52 2016 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
sd202:~# sudo smartctl -i /dev/sdb
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.10.62-ltsi-WR6.0.0.21_standard] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: TS16GHSD310
Serial Number: 20140523B42278052047
Firmware Version: 20111220
User Capacity: 16,013,852,672 bytes [16.0 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ACS-2 (revision not indicated)
Local Time is: Sun Aug 28 06:46:58 2016 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
(Back to List)

30. How to check hard disk partitions, partition size, file system type and mount point.
 
sd202:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 14.9G 0 disk
|-sda1 8:1 0 1.2G 0 part /boot
|-sda2 8:2 0 1.1G 0 part /app_disk
|-sda3 8:3 0 1.9G 0 part /
|-sda4 8:4 0 1K 0 part
|-sda5 8:5 0 9.5G 0 part /var
`-sda6 8:6 0 570.3M 0 part
sdb 8:16 0 14.9G 0 disk
|-sdb1 8:17 0 976.6M 0 part
`-sdb2 8:18 0 13.3G 0 part
sd202:~# sudo parted –l <------ its “l” as in “Liberty”
Model: ATA TS16GHSD310 (scsi)
Disk /dev/sda: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 8000kB 1280MB 1272MB primary fat16 boot
2 1280MB 2474MB 1194MB primary ext4
3 2474MB 4522MB 2048MB primary ext4
4 4522MB 15.3GB 10.8GB extended lba
5 4522MB 14.7GB 10.2GB logical ext4
6 14.7GB 15.3GB 598MB logical linux-swap(v1)
Model: ATA TS16GHSD310 (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 512B 1024MB 1024MB primary ext4 boot
2 1024MB 15.3GB 14.2GB primary
(Back to List)

31. How to check the total size, current use and use % for hard disk partitions from Satellite Host OS?
 
The list generated by “df –h | grep ^/dev” includes only the file systems that are real disk partitions. Importantly it displays the total size, used and use%.

sd202:~# df -h | grep ^/dev
/dev/sda3 1.9G 471M 1.3G 27% /
/dev/sda5 9.2G 181M 8.6G 3% /var
/dev/sda1 1.2G 404M 810M 34% /boot
/dev/sda2 1.1G 1.5M 1015M 1% /app_disk
(Back to List)

32. How to test the readable speed of HDD from Satellite Host OS Shell?
 
sd202:~# hdparm -Tt /dev/sda
/dev/sda:
Timing cached reads: 6632 MB in 2.00 seconds = 3317.80 MB/sec
Timing buffered disk reads: 284 MB in 3.00 seconds = 94.63 MB/sec
sd202:~# hdparm -Tt /dev/sdb
/dev/sdb:
Timing cached reads: 6684 MB in 2.00 seconds = 3344.12 MB/sec
Timing buffered disk reads: 382 MB in 3.02 seconds = 126.62 MB/sec
(Back to List)

33. How to perform health Check on the Hard Disk Drive connected on Satellite Device.
 
sd202:~# smartctl --health /dev/sda
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.10.62-ltsi-WR6.0.0.21_standard] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Please note the following marginal Attributes:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
167 Unknown_Attribute 0x0000 100 100 100 Old_age Offline FAILING_NOW 49
sd202:~# smartctl --health /dev/sdb
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.10.62-ltsi-WR6.0.0.21_standard] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Please note the following marginal Attributes:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
167 Unknown_Attribute 0x0000 100 100 100 Old_age Offline FAILING_NOW 11
(Back to List)

34. How to monitor the hard disk drive device I/O statistics?
 
sd202:~# iostat
Linux 3.10.62-ltsi-WR6.0.0.21_standard (sd202) 08/28/16 _x86_64_ (4 CPU)
avg-cpu: %user %nice %system %iowait %steal %idle
3.44 0.00 0.88 0.06 0.00 95.62
Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn
sda 1.16 0.12 15.38 690088 89998175
sdb 0.00 0.07 0.00 399738 0
(Back to List)

35. How to see the hardware specification of installed RAM on the Satellite Host?
 
sd202:~# sudo dmidecode -t 17
# dmidecode 2.12
SMBIOS 2.7 present.
Handle 0x0028, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Set: None
Locator: ChannelA-DIMM 0
Bank Locator: BANK 0
Type: Unknown
Type Detail: Unknown
Speed: Unknown
Manufacturer: Empty
Serial Number: Empty
Asset Tag: Unknown
Part Number: Empty
Rank: Unknown
Configured Clock Speed: Unknown
Handle 0x0029, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: 0x002C
Total Width: 72 bits
Data Width: 64 bits
Size: 8192 MB
Form Factor: DIMM
Set: None
Locator: ChannelA-DIMM 1
Bank Locator: BANK 1
Type: DDR3
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 1333 MHz
Manufacturer: Transcend Information
Serial Number: 000A2C0F
Asset Tag: Unknown
Part Number: TS1GLK72V3H
Rank: 2
Configured Clock Speed: 1333 MHz
(Back to List)

36. How to view the network/system statistics on a Satellite Device ?
 
sd202:~# netstat -s
Ip:
21806190 total packets received
0 forwarded
0 incoming packets discarded
21805923 incoming packets delivered
17487974 requests sent out
235286 dropped because of missing route
Icmp:
5561 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
destination unreachable: 5561
0 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
IcmpMsg:
InType3: 5561
Tcp:
5774 active connections openings
5849 passive connection openings
7 failed connection attempts
23 connection resets received
14 connections established
19112245 segments received
15679620 segments send out
110 segments retransmited
0 bad segments received.
49 resets sent
Udp:
1802675 packets received
0 packets to unknown port received.
0 packet receive errors
1813886 packets sent
UdpLite:
TcpExt:
5 invalid SYN cookies received
1 packets pruned from receive queue because of socket buffer overrun
5734 TCP sockets finished time wait in fast timer
1334846 delayed acks sent
216 delayed acks further delayed because of locked socket
Quick ack mode was activated 1 times
16652 packets directly queued to recvmsg prequeue.
136567 bytes directly in process context from backlog
22223 bytes directly received in process context from prequeue
622002 packet headers predicted
26543 packets header predicted and directly queued to user
890565 acknowledgments not containing data payload received
8244147 predicted acknowledgments
53 other TCP timeouts
TCPLossProbes: 73
TCPLossProbeRecovery: 17
57 packets collapsed in receive queue due to low socket buffer
3 DSACKs sent for old packets
10 times unabled to send RST due to no memory
TCPSackShiftFallback: 2
IPReversePathFilter: 267
TCPRcvCoalesce: 21627
TCPSpuriousRtxHostQueues: 5
(Back to List)

37. How to view FRUs locally from a Satellite Device ?
 
labroot@AD> request chassis satellite login fpc-slot 202
sd202:~$ cli
> d localhost
localhost>
localhost# show lcmd ?
Possible Completions:
fan_info
ts_stat
fan_stat
async_msg
chassis_info
psu_stat
pic
chassis_alarm
sys_stat
led_info
xcvr
led_stat
ts_info
sys_info
psu_info
port_led
chassis_stat
localhost# show lcmd psu_stat
{
"psu_stat": {
"psu0": {
"psu_s_psu_fan_rpm": [
0,
0
],
"psu_s_curt": 0,
"psu_s_psu_no": 0,
"psu_s_psu_te": [
0,
0,
0
],
"psu_s_psu_ld": 0,
"psu_s_psu_ns": 3,
"psu_s_pwr_i": 0,
"psu_s_vt_i": 0,
"psu_s_status": "NOPOWER",
"psu_s_psu_nfan": 2,
"psu_s_psu_ip_st": "Out Of Range",
"psu_s_pwr": 0,
"psu_s_curt_i": 0,
"psu_s_vt": 0,
"psu_s_psu_te_st": [
"OK",
"OK",
"OK"
],
"psu_s_psu_ext": 0,
"psu_s_state": "Present"
},

localhost# show lcmd fan_stat
{
"fan_stat": {
"fan1": {
"fan_s_fan_tno": 1,
"fan_s_fan_st": "OK",
"fan_s_fan_sp_st": "Spinning at normal speed",
"fan_s_no_of_fan": 1,
"fan_s_fan_r": 5325
},
"fan0": {
"fan_s_fan_tno": 0,
"fan_s_fan_st": "OK",
"fan_s_fan_sp_st": "Spinning at normal speed",
"fan_s_no_of_fan": 1,
"fan_s_fan_r": 5278
},
"fan2": {
"fan_s_fan_tno": 2,
"fan_s_fan_st": "OK",
"fan_s_fan_sp_st": "Spinning at normal speed",
"fan_s_no_of_fan": 1,
"fan_s_fan_r": 5601
}
},
"nfan": 3
}
localhost# show lcmd xcvr
{
"xcvr": {
"xcvr_0_71": {
"xv_vn": "FINISAR CORP. ",
"xv_pt_no": 71,
"xv_rev": "REV 01",
"xv_v_fw_vr": "",
"xv_sno": "PM752HE ",
"xv_cb_ty": "SFP-SX",
"xv_md": 2,
"xv_pno": "740-031851",
"xv_v_pno": "FTLF8519P2BNL-J4",
"xv_wv": 850
},
"xcvr_0_70": {
"xv_vn": "FINISAR CORP. ",
"xv_pt_no": 70,
"xv_rev": "REV 01",
"xv_v_fw_vr": "",
"xv_sno": "PC31B9Q ",
"xv_cb_ty": "SFP-SX",
"xv_md": 2,
"xv_pno": "740-011782",
"xv_v_pno": "FTRJ8519P1BNL-J2",
"xv_wv": 850
localhost# show lcmd sys_stat
{
"sys_s": {
"krn_ut": "0.80",
"up_t": "6314391",
"id_ut": "96.40",
"bkg_ut": "0.00",
"bt_t": "1466514695",
"re_te": 29,
"usr_ut": "2.80",
"buf_ut": "8.08",
"in_te": 29,
"av_rn": [
"0.08",
"0.10",
"0.13"
],
"int_ut": "0.00"
}
}
(Back to List)

38. How to capture LLDP history from Satellite Device?
 
localhost# show lldp history
{
"xe-0-0-0c": {
"Adjacency Down Cause": {
"Cause": [
"Interface Down",
"Interface Down",
"Hold timer expire",
"Interface Down"
]
},
"Protocol State": "Two-Way",
"Adjacency hold timer (second)": 60,
"Peer Information": {
"Adjacency UP/Dn transition": 13,
"Peer Device Serial Number": "a8:d0:e5:f3:07:c0"
},
"Peer Address": "10.0.128.9/30",
"Tx hello timer (seconds)": 10,
"Peer Name": "Aggregation-Device",
"Local assigned address": {
"Local-end IP address": "10.0.128.10/30",
"Remote-end IP address": "10.0.128.9/30"
},
"Local Address": "10.0.128.10/30",
"Event History": {
"Event": [
{
"Timerstamp": " 5d: 22h: 28m: 16s .357",
"Action List": {
"Action": "Received Message same as the last one"
(Back to List)

39. How to capture LLDP statistics from Satellite Device?
 
localhost# show lldp statistics
{
"xe-0-0-0c": {
"General Statistics": {
"Adjacenct Established": 7,
"Adjacenct Expire": 6
},
"Messages": {
"Rcvd Error Count": 0
},
"Discovery": {
"Rcvd Count": 130152,
"Sent Count": 125216,
"Rcvd Error Count": 0,
"LLDP Msg (with no PE TLV)": 0
}
},
"xe-0-0-1c": {
"General Statistics": {
"Adjacenct Established": 8,
"Adjacenct Expire": 7
},
"Messages": {
"Rcvd Error Count": 0
},
"Discovery": {
"Rcvd Count": 682867,
"Sent Count": 649102,
"Rcvd Error Count": 0,
"LLDP Msg (with no PE TLV)": 0
}
}
}
(Back to List)

40. Following Commands are already included in RSI-
 
show chassis satellite
show chassis satellite extensive
show chassis satellite detail
show chassis satellite neighbor
show chassis satellite interface extensive
show chassis satellite extended-port extensive
show chassis satellite upgrade-group
show chassis satellite software detail
show chassis satellite statistics
show chassis satellite unprovision
show chassis satellite unprovision detail
show chassis hardware satellite
show chassis hardware satellite extensive
show chassis environment satellite
show chassis environment pem satellite
show chassis environment routing-engine satellite
show chassis environment fpc satellite
show chassis fan satellite
show chassis temperature-thresholds satellite
show chassis routing-engine satellite
show chassis routing-engine bios satellite
show chassis firmware satellite
show chassis alarms satellite
show chassis led satellite
show chassis satellite task summary
show chassis satellite task memory detail
show chassis satellite platform task summary
show chassis satellite platform task memory detail
show chassis satellite platform interface queue
show chassis satellite platform interface statistics
show chassis satellite platform fpc detail
show chassis satellite platform fpc interfaces detail
show chassis satellite environment-monitoring
show chassis satellite environment-monitoring detail
show chassis services satellite
show interfaces terse satellite-device all
show interfaces extensive satellite-device all
show system core-dumps satellite
(Back to List)

41. Shell Command on SD to TCPDump LLDP Packet.
 
sd202:~# tcpdump -w test.pcap -i xe-0-0-0c
tcpdump: listening on xe-0-0-0c, link-type EN10MB (Ethernet), capture size 65535 bytes
^C20 packets captured
21 packets received by filter
0 packets dropped by kernel
sd202:~# ls -tl
total 8
-rw-r--r-- 1 root root 3225 Sep 4 17:14 test.pcap
sd202:~# tcpdump -r test.pcap -i xe-0-2-0c
reading from file test.pcap, link-type EN10MB (Ethernet)
17:14:09.035544 IP 172.16.0.202.ssh > 172.16.255.1.54825: Flags [P.], seq 4180563435:4180563567, ack 1810589215, win 270, options [nop,nop,TS val 2199286109 ecr 2788579298], length 132
17:14:09.036214 IP 172.16.255.1.54825 > 172.16.0.202.ssh: Flags [.], ack 132, win 32702, options [nop,nop,TS val 2788579323 ecr 2199286086], length 0
17:14:09.849520 IP 172.16.255.1.51666 > 172.16.0.202.56870: Flags [P.], seq 261794989:261795369, ack 1235070311, win 4096, options [nop,nop,TS val 2788580136 ecr 2199285925], length 380
17:14:09.851801 IP 172.16.0.202.56870 > 172.16.255.1.51666: Flags [P.], seq 1:82, ack 380, win 64, options [nop,nop,TS val 2199286925 ecr 2788580136], length 81
17:14:09.900652 IP 172.16.255.1.33127 > 172.16.0.202.41527: Flags [P.], seq 2040190055:2040190090, ack 2444696709, win 4096, options [nop,nop,TS val 2788580187 ecr 2199283269], length 35
17:14:09.900677 IP 172.16.0.202.41527 > 172.16.255.1.33127: Flags [.], ack 35, win 64, options [nop,nop,TS val 2199286974 ecr 2788580187], length 0
17:14:09.951854 IP 172.16.255.1.51666 > 172.16.0.202.56870: Flags [.], ack 82, win 4096, options [nop,nop,TS val 2788580239 ecr 2199286925], length 0
17:14:10.851869 IP 172.16.0.202.56870 > 172.16.255.1.51666: Flags [P.], seq 82:153, ack 760, win 64, options [nop,nop,TS val 2199287925 ecr 2788581137], length 71
17:14:10.952812 IP 172.16.255.1.51666 > 172.16.0.202.56870: Flags [.], ack 153, win 4096, options [nop,nop,TS val 2788581239 ecr 2199287925], length 0
17:14:11.852865 IP 172.16.0.202.56870 > 172.16.255.1.51666: Flags [P.], seq 153:162, ack 1140, win 64, options [nop,nop,TS val 2199288926 ecr 2788582139], length 9
17:14:12.000942 LLDP, name Aggregation-Device, length 312
17:14:12.897002 IP 172.16.0.202.56870 > 172.16.255.1.51666: Flags [.], ack 1520, win 64, options [nop,nop,TS val 2199289971 ecr 2788583143], length 0
17:14:13.242684 IP 172.16.0.202.56870 > 172.16.255.1.51666: Flags [P.], seq 162:229, ack 1520, win 64, options [nop,nop,TS val 2199290316 ecr 2788583143], length 67
17:14:13.677367 IP 172.16.255.1.6011 > 172.16.0.202.38792: Flags [.], ack 3887113203, win 65535, length 0
17:14:13.857329 IP 172.16.255.1.51666 > 172.16.0.202.56870: Flags [P.], seq 1520:1900, ack 229, win 4096, options [nop,nop,TS val 2788584145 ecr 2199290316], length 380
17:14:13.857356 IP 172.16.0.202.56870 > 172.16.255.1.51666: Flags [.], ack 1900, win 62, options [nop,nop,TS val 2199290931 ecr 2788584145], length 0
17:14:13.858694 IP 172.16.0.202.56870 > 172.16.255.1.51666: Flags [P.], seq 229:309, ack 1900, win 64, options [nop,nop,TS val 2199290932 ecr 2788584145], length 80
17:14:13.961148 IP 172.16.255.1.51666 > 172.16.0.202.56870: Flags [.], ack 309, win 4096, options [nop,nop,TS val 2788584247 ecr 2199290932], length 0
17:14:14.860146 IP 172.16.0.202.56870 > 172.16.255.1.51666: Flags [P.], seq 309:387, ack 2280, win 64, options [nop,nop,TS val 2199291934 ecr 2788585146], length 78
17:14:14.960981 IP 172.16.255.1.51666 > 172.16.0.202.56870: Flags [.], ack 387, win 4096, options [nop,nop,TS val 2788585248 ecr 2199291934], length 0
sd202:~#
sd202:~# tcpdump -i xe-0-0-0c -s 1500 -XX -c 1 'ether proto 0x88cc'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on xe-0-0-0c, link-type EN10MB (Ethernet), capture size 1500 bytes
17:20:42.011837 LLDP, name Aggregation-Device, length 312
0x0000: 0180 c200 000e a8d0 e5f3 0297 88cc 0207 ................
0x0010: 04a8 d0e5 f307 c004 0207 3006 0200 3c08 ..........0...<.
0x0020: 0878 652d 312f 302f 320a 1241 6767 7265 .xe-1/0/2..Aggre
0x0030: 6761 7469 6f6e 2d44 6576 6963 650c 554a gation-Device.UJ
0x0040: 756e 6970 6572 204e 6574 776f 726b 732c uniper.Networks,
0x0050: 2049 6e63 2e20 6d78 3234 3020 2c20 7665 .Inc..mx240.,.ve
0x0060: 7273 696f 6e20 3134 2e32 5235 2d53 3320 rsion.14.2R5-S3.
0x0070: 4275 696c 6420 6461 7465 3a20 3230 3136 Build.date:.2016
0x0080: 2d30 332d 3034 2031 313a 3431 3a31 3720 -03-04.11:41:17.
0x0090: 5554 4320 0e04 0010 0000 fe11 0080 c20f UTC.............
0x00a0: 00a8 d0e5 f302 97a8 d0e5 f302 97fe 3100 ..............1.
0x00b0: 9069 2e53 6174 656c 6c69 7465 2073 6c6f .i.Satellite.slo
0x00c0: 7420 3120 736e 2061 383a 6430 3a65 353a t.1.sn.a8:d0:e5:
0x00d0: 6633 3a30 373a 6330 2064 7020 3232 3935 f3:07:c0.dp.2295
0x00e0: fe0a 0090 6921 da3a b271 7712 fe0d 0090 ....i!.:.qw.....
0x00f0: 6922 0a00 8009 0a00 800a 1efe 0900 9069 i".............i
0x0100: 23ac 1000 0010 fe0e 0090 6924 0002 0000 #.........i$....
0x0110: 8167 ac10 ff01 fe0e 0090 6926 00ca ac10 .g........i&....
0x0120: ff01 ac10 00ca fe08 0090 692a 0000 ea60 ..........i*...`
0x0130: fe08 0090 692b 0000 7530 fe08 0090 692d ....i+..u0....i-
0x0140: 0000 0001 0000 ......
1 packets captured
1 packets received by filter
0 packets dropped by kernel
42. How to check Routing table on Satellite Device.
sd202:~# ip route show table local
broadcast 10.0.128.8 dev xe-0-0-0c proto kernel scope link src 10.0.128.10
local 10.0.128.10 dev xe-0-0-0c proto kernel scope host src 10.0.128.10
broadcast 10.0.128.11 dev xe-0-0-0c proto kernel scope link src 10.0.128.10
broadcast 10.0.136.8 dev xe-0-0-1c proto kernel scope link src 10.0.136.10
local 10.0.136.10 dev xe-0-0-1c proto kernel scope host src 10.0.136.10
broadcast 10.0.136.11 dev xe-0-0-1c proto kernel scope link src 10.0.136.10
broadcast 127.0.0.0 dev lo proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo proto kernel scope link src 127.0.0.1
local 172.16.0.202 dev lo proto kernel scope host src 172.16.0.202
(Back to List)

42. How to check Addresses on Satellite Device interfaces.
 
sd202:~# ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet 172.16.0.202/32 scope global lo:0
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
7: xe-0-0-0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9192 qdisc pfifo_fast state UP qlen 500
link/ether 40:a6:77:d9:08:c5 brd ff:ff:ff:ff:ff:ff
inet6 fe80::42a6:77ff:fed9:8c5/64 scope link
valid_lft forever preferred_lft forever
8: xe-0-0-0c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9192 qdisc pfifo_fast state UP qlen 500
link/ether 40:a6:77:d9:08:c5 brd ff:ff:ff:ff:ff:ff
inet 10.0.128.10/30 scope global xe-0-0-0c
valid_lft forever preferred_lft forever
inet6 fe80::42a6:77ff:fed9:8c5/64 scope link
valid_lft forever preferred_lft forever
9: xe-0-0-1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9192 qdisc pfifo_fast state UP qlen 500
link/ether 40:a6:77:d9:08:c6 brd ff:ff:ff:ff:ff:ff
inet6 fe80::42a6:77ff:fed9:8c6/64 scope link
valid_lft forever preferred_lft forever
10: xe-0-0-1c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9192 qdisc pfifo_fast state UP qlen 500
link/ether 40:a6:77:d9:08:c6 brd ff:ff:ff:ff:ff:ff
inet 10.0.136.10/30 scope global xe-0-0-1c
valid_lft forever preferred_lft forever
inet6 fe80::42a6:77ff:fed9:8c6/64 scope link
valid_lft forever preferred_lft forever
(Back to List)



 
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search