
- •Contents
- •Course Overview
- •Course Agenda
- •Document Conventions
- •Additional Information
- •The Junos CLI (Detailed)
- •Overview
- •Part 1: Logging In and Exploring the CLI
- •Step 1.1
- •Step 1.2
- •Step 1.3
- •Step 1.4
- •Step 1.5
- •Step 1.6
- •Step 1.7
- •Step 1.8
- •Step 1.9
- •Step 1.10
- •Step 1.11
- •Step 1.12
- •Step 1.13
- •Step 1.14
- •Step 1.15
- •Step 1.16
- •Step 1.17
- •Step 1.18
- •Step 1.19
- •Initial System Configuration (Detailed)
- •Overview
- •Part 1: Loading a Factory-Default Configuration and Performing Initial Configuration
- •Step 1.1
- •Step 1.2
- •Step 1.3
- •Step 1.4
- •Step 1.5
- •Step 1.6
- •Step 1.7
- •Step 1.8
- •Step 1.9
- •Step 1.10
- •Step 1.11
- •Step 1.12
- •Step 1.13
- •Step 1.14
- •Step 1.15
- •Step 1.16
- •Part 2: Saving, Displaying, Loading, and Deleting a Rescue Configuration
- •Step 2.1
- •Step 2.2
- •Step 2.3
- •Step 2.4
- •Step 2.5
- •Step 2.6
- •Step 2.7
- •Step 2.8
- •Step 2.9
- •Part 3: Configuring Interfaces and Verifying Operational State
- •Step 3.1
- •Step 3.2
- •Step 3.3
- •Step 3.4
- •Secondary System Configuration (Detailed)
- •Overview
- •Part 1: Configuring User Authentication
- •Step 1.1
- •Step 1.2
- •Step 1.3
- •Step 1.4
- •Step 1.5
- •Step 1.6
- •Step 1.7
- •Step 1.8
- •Step 1.9
- •Step 1.10
- •Step 1.11
- •Step 1.12
- •Step 1.13
- •Step 1.14
- •Step 1.15
- •Step 1.16
- •Step 1.17
- •Step 1.18
- •Step 1.19
- •Part 2: Performing System Management Options
- •Step 2.1
- •Step 2.2
- •Step 2.3
- •Step 2.4
- •Step 2.5
- •Step 2.6
- •Step 2.7
- •Step 2.8
- •Step 2.9
- •Step 2.10
- •Step 2.11
- •Step 2.12
- •Step 2.13
- •Step 2.14
- •Step 2.15
- •Step 2.16
- •Step 2.17
- •Step 2.18
- •Operational Monitoring and Maintenance (Detailed)
- •Overview
- •Part 1: Monitoring System and Chassis Operation
- •Step 1.1
- •Step 1.2
- •Step 1.3
- •Step 1.4
- •Step 1.5
- •Step 1.6
- •Step 1.7
- •Step 1.8
- •Step 1.9
- •Step 1.10
- •Step 1.11
- •Step 1.12
- •Step 1.13
- •Step 1.14
- •Step 1.15
- •Step 1.16
- •Part 2: Using Network Utilities and Monitoring Traffic
- •Step 2.1
- •Step 2.2
- •Step 2.3
- •Step 2.4
- •Step 2.5
- •Step 2.6
- •Part 3: Upgrading the Junos OS
- •Step 3.1
- •Step 3.2
- •Step 3.3
- •Step 3.4
- •Step 3.5
- •Part 4: Recovering the Root Password
- •Step 4.1
- •Step 4.2
- •Step 4.3
- •Step 4.4
- •Step 4.5
- •Step 4.6
- •Step 4.7
- •Step 4.8
- •Lab 5 (Optional)
- •The J-Web Interface (Detailed)
- •Overview
- •Part 1: Logging In to and Exploring the J-Web Interface
- •Step 1.1
- •Step 1.2
- •Step 1.3
- •Step 1.4
- •Step 1.5
- •Step 1.6
- •Step 1.7
- •Step 1.8
- •Step 1.9
- •Part 2: Exploring J-Web Configuration and Diagnostic Capabilities
- •Step 2.1
- •Step 2.2
- •Step 2.3
- •Step 2.4
- •Step 2.5
- •Step 2.6
- •Step 2.7
- •Step 2.8
- •Step 2.9
- •Appendix A: Lab Diagrams

Introduction to the Junos Operating System
srxA-1 (ttyp0)
login: walter Password:
--- JUNOS 12.1R1.9 built 2012-03-24 12:12:49 UTC walter@srxA-1>
Step 1.9
Return to the original session opened to your device.
Return to the original session logged in as lab and issue the show system users command to view information about users logged in to your team’s device.
lab@srxA-1> |
show system users |
|
|
|
12:41PM |
up |
46 mins, 2 users, load averages: 0.03, 0.08, 0.12 |
||
USER |
TTY |
FROM |
LOGIN@ |
IDLE WHAT |
lab |
u0 |
- |
2:33PM |
- -cli (cli) |
walter |
p0 |
10.210.14.129 |
3:07PM |
1 -cli (cli) |
Question: What is the source IP address of the
Telnet session established by the user walter?
Answer: The answer will vary. In the following example taken from srxA-1, the source IP address of the telnet session established by the user walter is 10.210.14.129.
Step 1.10
Issue the request system logout user walter command to force a log out for the user walter. Next, issue the show system users command to verify that the user session for walter was terminated.
lab@srxA-1> |
request system logout user walter |
|
||
logout-user: done |
|
|
||
lab@srxA-1> |
show system users |
|
||
12:46PM |
up |
51 mins, 1 |
user, load averages: 0.06, 0.12, 0.12 |
|
USER |
TTY |
FROM |
LOGIN@ |
IDLE WHAT |
lab |
u0 |
- |
12:29PM |
- -cli (cli) |
Question: Was the user Telnet session for walter properly closed?
Answer: As shown in the sample output, the Telnet session for the user walter should now be closed.
Lab 4–6 • Operational Monitoring and Maintenance (Detailed) |
www.juniper.net |

Introduction to the Junos Operating System
Step 1.11
Check the environmental status of your team’s device by issuing the show chassis environment command.
lab@srxA-1> show |
chassis environment |
|
|
|
Class Item |
|
Status |
Measurement |
|
Temp |
Routing Engine |
OK |
37 degrees C / 98 degrees F |
|
|
Routing Engine CPU |
OK |
36 degrees C / 96 degrees F |
|
Fans |
SRX240 PowerSupply fan 1 |
OK |
Spinning at high speed |
|
|
SRX240 PowerSupply fan 2 |
OK |
Spinning at high speed |
|
|
SRX240 CPU |
fan 1 |
OK |
Spinning at high speed |
|
SRX240 CPU |
fan 2 |
OK |
Spinning at high speed |
|
SRX240 IO |
fan 1 |
OK |
Spinning at high speed |
|
SRX240 IO |
fan 2 |
OK |
Spinning at high speed |
Power Power Supply 0 |
OK |
|
Question: What is the temperature and status of the
Routing Engine (RE)?
Answer: Your details might vary. The sample capture shows a temperature of 37 degrees Celsius and a status of OK.
Question: Name another show chassis command that displays the RE temperature. (Hint: Use the ?.)
Answer: As the following capture shows, the show chassis routing-engine command displays the RE temperature as well as other RE-specific details.
lab@srxA-1> show chassis routing-engine |
|
||
Routing Engine status: |
|
|
|
Temperature |
37 |
degrees C / 98 degrees F |
|
CPU temperature |
36 |
degrees C / 96 degrees F |
|
Total memory |
1024 |
MB Max |
635 MB used ( 62 percent) |
Control plane memory |
560 |
MB Max |
330 MB used ( 59 percent) |
Data plane memory |
464 |
MB Max |
306 MB used ( 66 percent) |
CPU utilization: |
|
|
|
User |
5 |
percent |
|
Background |
0 |
percent |
|
Kernel |
4 |
percent |
|
Interrupt |
0 |
percent |
|
Idle |
92 |
percent |
|
Model |
|
RE-SRX240H-POE |
|
Serial ID |
|
AAAD8406 |
|
Start time |
|
2010-10-20 11:56:01 PDT |
|
Uptime |
|
58 minutes, 49 seconds |
|
Last reboot reason |
|
0x200:chassis control reset |
www.juniper.net |
Operational Monitoring and Maintenance (Detailed) • Lab 4–7 |

Introduction to the Junos Operating System |
|
|
|
Load averages: |
1 minute |
5 minute |
15 minute |
|
0.11 |
0.11 |
0.11 |
Step 1.12
Issue the show chassis temperature-thresholds command.
lab@srxA-1> show chassis temperature-thresholds |
|
|
|
|
|||
|
Fan speed |
Yellow alarm |
Red alarm |
Fire |
|||
|
(degrees C) |
(degrees C) |
(degrees C) (degrees C) |
||||
Item |
Normal |
High |
Normal |
Bad fan |
Normal |
Bad fan |
|
Normal |
|
|
|
|
|
|
|
Chassis default |
35 |
45 |
50 |
40 |
75 |
65 |
100 |
Routing Engine |
35 |
45 |
50 |
40 |
75 |
65 |
100 |
Question: At what temperature is a red alarm generated for the RE?
Answer: Assuming the fans are operational, the system raises a red alarm when the RE reaches 75 degrees Celsius. These threshold values can vary between different Junos devices.
Step 1.13
View details about your system’s hardware components using the show chassis hardware command.
lab@srxA-1> show |
chassis hardware |
|
|
||
Hardware inventory: |
|
|
|
||
Item |
|
Version |
Part number |
Serial number |
Description |
Chassis |
|
|
AH2909AA0041 |
SRX240-poe |
|
Routing Engine |
REV 31 |
750-021794 |
AAAK4071 |
RE-SRX240-POE |
|
FPC 0 |
|
|
|
|
FPC |
PIC |
0 |
|
|
|
16x GE Base PIC |
Power |
Supply 0 |
|
|
|
|
Question: What is the chassis serial number for your team’s device?
Answer: The answer will vary depending on your assigned device. In the example, the chassis serial number is AH2909AA0041.
Step 1.14
Issue the show interface terse command to quickly verify the administrative and link state for your device’s interfaces.
lab@srxA-1> show interfaces terse |
|
|
|||
Interface |
Admin |
Link Proto |
Local |
Remote |
|
ge-0/0/0 |
up |
up |
|
|
|
ge-0/0/0.0 |
up |
up |
inet |
10.210.14.131/27 |
|
Lab 4–8 • Operational Monitoring and Maintenance (Detailed) |
www.juniper.net |

|
|
|
|
Introduction to the Junos Operating System |
|
gr-0/0/0 |
up |
up |
|
|
|
ip-0/0/0 |
up |
up |
|
|
|
ls-0/0/0 |
up |
up |
|
|
|
lt-0/0/0 |
up |
up |
|
|
|
mt-0/0/0 |
up |
up |
|
|
|
pd-0/0/0 |
up |
up |
|
|
|
pe-0/0/0 |
up |
up |
|
|
|
ge-0/0/1 |
up |
up |
|
|
|
ge-0/0/1.0 |
up |
up |
inet |
172.20.77.1/30 |
|
ge-0/0/2 |
up |
up |
|
|
|
ge-0/0/2.0 |
up |
up |
inet |
172.20.66.1/30 |
|
ge-0/0/3 |
up |
up |
|
|
|
ge-0/0/3.0 |
up |
up |
inet |
172.18.1.2/30 |
|
ge-0/0/4 |
up |
up |
|
|
|
ge-0/0/5 |
up |
down |
|
|
|
ge-0/0/6 |
up |
down |
|
|
|
ge-0/0/7 |
up |
down |
|
|
|
ge-0/0/8 |
up |
down |
|
|
|
ge-0/0/9 |
up |
down |
|
|
|
ge-0/0/10 |
up |
down |
|
|
|
ge-0/0/11 |
up |
down |
|
|
|
ge-0/0/12 |
up |
down |
|
|
|
ge-0/0/13 |
up |
down |
|
|
|
ge-0/0/14 |
up |
down |
|
|
|
ge-0/0/15 |
up |
down |
|
|
|
gre |
up |
up |
|
|
|
ipip |
up |
up |
|
|
|
lo0 |
up |
up |
|
|
|
lo0.0 |
up |
up |
inet |
192.168.1.1 |
--> 0/0 |
lo0.16384 |
up |
up |
inet |
127.0.0.1 |
--> 0/0 |
lo0.16385 |
up |
up |
inet |
10.0.0.1 |
--> 0/0 |
|
|
|
|
10.0.0.16 |
--> 0/0 |
|
|
|
|
128.0.0.1 |
--> 0/0 |
|
|
|
|
128.0.1.16 |
--> 0/0 |
|
|
|
inet6 |
fe80::226:88ff:fe02:6700 |
|
lo0.32768 |
up |
up |
|
|
|
lsi |
up |
up |
|
|
|
mtun |
up |
up |
|
|
|
pimd |
up |
up |
|
|
|
pime |
up |
up |
|
|
|
pp0 |
up |
up |
|
|
|
st0 |
up |
up |
|
|
|
tap |
up |
up |
|
|
|
vlan |
up |
up |
|
|
|
Question: What are the Admin and Link states for all configured interfaces?
Answer: All configured interfaces should show Admin and Link states of up. If your output shows otherwise, please contact your instructor.
www.juniper.net |
Operational Monitoring and Maintenance (Detailed) • Lab 4–9 |