Introduction to the Junos Operating System

Part 1: Monitoring System and Chassis Operation

In this lab part, each team will use key commands within the CLI to monitor system and chassis operation.

Step 1.1

Ensure that you know to which student device you have been assigned. Check with your instructor if you are not certain. Consult the management network diagram to determine the management address of your student device

Question: What is the management address assigned to your station?

Answer: The answer varies; in the example used throughout this lab, the user belongs to the srxA-1 station, which uses an IP address of 10.210.14.131. Your answer will depend on the rack of equipment your class is using.

Step 1.2

Access the CLI at your station using either the console, Telnet, or SSH as directed by your instructor. Refer to the management network diagram for the IP address associated with your team’s station. The following example uses a simple Telnet access to srxA-1 with the Secure CRT program as a basis:

Step 1.3

Log in to the student device with the username lab using a password of lab123. Note that both the name and password are case-sensitive. Enter configuration mode and load the reset configuration file using the load override /var/home/ lab/ijos/lab4-start.config command. After the configuration has been loaded, commit the changes and return to operational mode.

srxA-1 (ttyp0)

login: lab Password:

Introduction to the Junos Operating System

--- JUNOS 12.1R1.9 built 2012-03-24 12:12:49 UTC lab@srxA-1> configure

Entering configuration mode

[edit]

lab@srxA-1# load override ijos/lab4-start.config load complete

[edit]

lab@srxA-1# commit and-quit commit complete

Exiting configuration mode

lab@srxA-1>

Step 1.4

Issue the show system processes extensive command to check the status of the routing protocol daemon (rpd). Alternatively, issue the show system processes extensive | match "pid | rpd" command to parse the output. The use of two pipes (|) in this command allows you to make multiple matches. In this case it matches rpd for the routing protocol process as well as PID to view the column headers.

Mem: 143M Active, 98M Inact, 535M Wired, 159M Cache, 112M Buf, 34M Free Swap:

...TRIMMED...

Question: What is the weighted CPU usage of rpd?

Answer: The answer can vary. In the sample output taken from srxA-1, the weighted CPU usage is 0%. The weighted CPU column represents the CPU usage over a period of time.

Step 1.5

Issue the show system statistics command to view protocol statistics related to your team’s device.

lab@srxA-1> show system statistics tcp:

466 packets sent

340 data packets (16474 bytes)

0 data packets (0 bytes) retransmitted

0 resends initiated by MTU discovery

116 ack-only packets (91 delayed)

0 URG only packets

2 window probe packets

0 window update packets

10 control packets

...TRIMMED...

Question: How many TCP packets did your assigned device send since the last clearing of the system statistics?

Answer: The answer can vary. In the previous example taken from srxA-1, the device sent 466 TCP packets.

Step 1.6

Issue the show system storage command to view information regarding the device storage space.

Question: How much free space is available on your device?

Answer: The answer can vary. In the sample output taken from srxA-1, 330 Megabytes are available.

Step 1.7

Issue the show system uptime command to view the current system time.

lab@srxA-1> show system uptime

Current time: 2012-04-20 08:01:50 PDT

System booted: 2012-04-18 10:24:42 PDT (1d 21:37 ago) Protocols started: 2012-04-18 12:27:26 PDT (1d 19:34 ago)

Last configured: 2012-04-20 07:52:13 PDT (00:09:37 ago) by lab 8:01AM up 1 day, 21:37, 2 users, load averages: 0.07, 0.05, 0.03

Question: When was your team’s device last booted?

Answer: The answer will vary. In the example taken from srxA-1, you can see that the system booted close to two days ago.

Step 1.8

Open another terminal window and use Telnet to access your system’s management IP address. If needed, refer to the management network diagram. Log in with the username walter and the password walter123.