Introduction to the Junos Operating System

Instructor Notes

Author's Name Pradeep Gadde

Gadde, Hari Reddy K

Training Group Education Services

Date 26 April 2021

Revision Number 21.a

Course Title Introduction to the Junos Operating System

Product Name All Junos Platforms

Par t Number EDU-JUN-IJOS

Sof tware Release Code 21.1R1.11

Introduction to the Junos Operating System Instructor Notes

Introduction
Lab Device Summary
Instructor-Led Online Delivery (ILO)
Chapter Suggestions For ILO Delivery
Instructor Preparation
Classroom Resources
Room Arrangement
Suggested Schedule
Homework
Lab Setup
Lab Infrastructure Information
Lab Notes
Introduction
IJOS is a three-day course that discusses the Junos software. This course includes a brief overview of Junos
devices and discusses the key architectural components of the Junos software. Additional key topics include
user interface options with a heavy focus on the command-line interface (CLI), the J-Web interface,
configuration tasks typically associated with the initial setup of Junos devices, interface configuration basics
with configuration examples, secondary system configuration, and the basics of operational monitoring and
maintenance of Junos devices.
The course then delves into foundational routing knowledge and configuration examples including general
routing concepts, routing policy, firewall filters, Class of service, and IPv6.
This instructor’s guide is recommended for anyone preparing to teach this course. The guide highlights a
number of caveats between Junos platforms, existing issues found in the Junos software version used in this
course, and various suggestions that may come in handy when teaching this course.
Lab Device Summary
vSRX-1

Version 21.1R1.11

Credentials

Username: root Password: training1

Username: lab Password: lab123

Licenses No License required

Universal License Not Applicable

Management IP: [Link] Web Interface: Same

vSRX-2

Version 21.1R1.11

Credentials

Username: root Password: training1

Username: lab Password: lab123

Licenses No License required

Universal License Not Applicable

Management IP: [Link] Web Interface: Same

Student Desktop - CentOS

Version CentOS Stream release 8.0

Credentials

Username: root Password: training1

Username: lab Password: lab123

Licenses No licenses Needed

Management IP: [Link] Web Interface: None

Instructor-Led Online Delivery (ILO)
Over the past several years the move toward ILO training has increased significantly; this has accelerated
largely in part due to the 2020 pandemic and organization’s realization that at-home workers are equally
productive. This trend is likely to continue and presents opportunities and challenges for organizations
responsible for delivering meaningful and timely online content. Typically, the online experience has simply
been to deliver existing course material through virtual sessions (Adobe Connect, Blue Jeans, etc.). While this
method has its advantages, student responsiveness and enthusiasm have declined when relying primarily on
this platform. The ability to deliver the right content in the right form provides our organization the prospect of
delivering an exciting new training medium.
Student engagement while attending online classes requires more interactive events than traditional
classroom environments. Considering some students view online training a background task, the Instructor
ought to be aware that more frequent Q & A sessions, demonstrations, and general engaging techniques
should be employed to keep the students not only interested, but focused on the content. Consider
developing scenarios relevant to the content and have the class propose solutions, or in the case of a
troubleshooting topic, recommended solutions.
Generally, af ter 10 or 12 slides it is recommended to provide students with a par ticipator y
activity. IJOS folder on the CDS site has the IJOS_Activity_Slides.pptx for the interactive
questions.
Student impressions of the Online training environment and Instructor tend to differ from a classroom setting.
Students will focus on the reliability of the meeting software, lab sessions, pacing and timing of delivery, and
the Instructor’s willingness to actively engage and draw conversations from the group. This set of
circumstances require a more concentrated effort in order to keep the student’s attention and motivation
constant throughout the training session. To effectively mitigate this set of concerns, please refer to the
Juniper ILO Best Practices document located on the Juniper Networks Learning Portal:
ILO_BestPractices.pdf ([Link])
Below are some chapter by chapter suggestions for facilitating online delivery. The suggestions are meant to
assist with student engagement and reinforce chapter content.
Chapter Suggestions For ILO Delivery
Below are some chapter by chapter suggestions for facilitating online delivery. The suggestions are meant to
assist with student engagement and reinforce chapter content.

Module 2 — Junos Operating System Fundamentals

Throughout the chapter: Chapter 2 introduces students to the architecture of the Junos OS and its
unique features. As time permits and depending upon the experience level of students with other
networking OSs, you might occasionally ask how the Junos OS compares to other vendor OSs.
topics could include the following:
— Modular OS
— Single Software Train, single code base
— Separation of control and forwarding plane
— Disaggregated Junos, Junos Evolved
At the end of the chapter: If there are students that have used another vendor OS and The Junos
OS, ask to get their feelings about how Junos compares. Most prefer Junos.
Juniper product portfolio is updated with the latest offerings; All major products, including
automation, are briefly introduced. Redirect students to Juniper Networks TechLibrary (https://
[Link]/documentation/) for specific details on any platform.

Module 3 — Junos CLI Operational Mode

Page 3-4: To showcase the Junos Automation capabilities, this slide is introduced; Redirect
students to Junos Automation track for indepth coverage of these topics.
Page 3-5: You might point to the difference in the root login prompt from shell mode (in certain
platforms)
Page 3-12: You might identify the EMAC commands you most often use.
Page 3-13: Possibly identify some of the pipe “|” commands you use.
Page 3-17: Possibly explain some of the commands you use most commonly in operational mode.

Module 4 — Junos CLI Configuration Mode

Page 4-3: When discussing the Active and Candidate configuration model Junos uses, you might
ask students who have multi vendor experience, if they prefer the Junos batch model commits or
the method of other vendors and why.
Page 4-5: When discussing entering configuration mode, you might ask students if they are
familiar with other modes of entering configuration mode other than the configure command. This
is assuming that some students will have prior
Junos experience. Alternatives to configure are the edit and conf commands.
Page 4-14: This slide is the last slide in the sequence of slides explaining how tomove around in
the Junos configuration hierarchy. Students might benefit from a review by identifying a current
location in the Junos hierarchy shown on the slide and a destination location on the slide and ask
students to identify which commands would most efficiently achieve the task. You could gameify it
by having students raise their virtual hands when they have an answer and see how quickly each
student can figure the answer out. You could do this several times to give practice as time permits.
 Page 4-21: Showing the configuration in set command format is discussed in the notes section of
this page. Ask students why viewing parts of the configuration in set format could be useful.
Possible answers include:
— To see the series of commands needed to add a Junos configuration feature.
— To retrieve a list of commands that can then be used in Junos automation to add a
Junos configuration feature.
Page 4-24: This is a new slide on two step commit process; Ask students when this might be
useful.
Page 4-26: Rollback rescue (will be covered in detail in another module) and revision are
introduced; Ask students when these options might be useful.
Page 4-28: Expanding on the topic introduced in Page 3-4 (Junos Automation Interfaces), a new
slide on ephemeral configuration database is introduced here.

Module 5 — J-Web Interface

Page 5-28: A good discussion either at the end or throughout the chapter is to discuss with
students whether they prefer to a CLI or Web interface. Or, possibly a more useful discussion would
be to talk about when the J-Web would be a better option than the CLI and when the CLI is
preferred.

Lab ILO Suggestions

At the beginning of the lab, take a few minutes to explain what the students will be doing.
At the end of the lab, check to see if there were any questions or concepts that need clarification.

Module 6 — Initial System Configuration

Page 6-4: You might explain the difference between loading a factory default configuration and
zeroing a device. Discuss when each is appropriate.
Page 6-18: If time permits, you might get feedback from students on how Juniper interface naming
compares to that of other vendors.
Page 6-19: The concept of logical interfaces can be difficult to new learners, especially if they have
never assigned more than one IP address to a single interface. You may want take a little extra
time on this page.
Page 6-23: Check the student's understanding of Primary and Preferred concept
Page 6-24: Discuss how to interpret the show interfaces terse command output and how this can
be useful while troubleshooting

Lab ILO Suggestions

At the beginning of the lab, take a few minutes to explain what the students will be doing.
At the end of the lab, check to see if there were any questions or concepts related to Initial System
Configuration that need clarification.

Module 7 — User Authentication Archiving

Module 7 — User Authentication Archiving
Page 7-7: If students have experience with other vendor equipment, ask how Junos user classes
compare with that of other vendors.
Page 7-13: Ask students how they would go about archiving the configuration of many Junos
devices? Explain that Juniper offers many automation solutions such as PyEZ and Ansible to
efficiently perform archiving and automation tasks.

Lab ILO Suggestions

At the end of the lab, verify that students were able to complete all the User Authentication and
Archival configuration steps.

Module 8 — System Logging, Tracing, NTP, and SNMP

Page 8-12: After discussing about setting NTP, this would be a good time to also show the show
system uptime command as a way to verify that NTP is configured and working.
Page 8-17: Ask students they think would be the best course of action if a particular piece of
information they wanted was not retrievable via SNMP?
– Ask Juniper to add it. (May take a while)
– Write an SNMP script using Junos automation to retrieve the information. Take the JAUT course
for more details.

Lab ILO Suggestions

At the beginning of the lab, take a few minutes to explain what the students will be doing.
At the end of the lab, check to see if there were any questions or concepts related to Syslog, NTP,
Traceoptions, and SNMP that need clarification.

Module 9 — Operational Monitoring and Maintenance

Page 9-10: The monitor interface traffic has a new slide of its own, do highlight this
command to view real-time statistics for all interfaces
Page 9-15: Check with students if any of them still using the Telnet, FTP options.
Page 9-17: Demonstrate password recovery (recording available)
Page 9-18: If time permits, demonstrate password recovery for platforms with upgraded FreeBSD
as well ( recording available)

Lab ILO Suggestions

At the end of the lab, verify that students were able to complete all the taks successfully. Note,
there is no lab on password recovery.

Module 10 — Upgrading the Junos OS

Page 10-7: If students have experience with other vendor equipment, ask how Junos package
naming convention and release cycle compare with that of other vendors.
Page 10-9: When talking about adding software you might also introduce the show system
software command or the show version command to show what software is currently installed.

Lab ILO Suggestions

Lab ILO Suggestions
At the beginning of the lab, take a few minutes to explain what the students will be doing
(especially, the point that we are upgrading to the same [current running] version)
At the end of the lab, verify that students were able to complete the Junos upgrade successfully.

Module 11 — Interface Configuration Examples

Page 11-6: Ask students what types of interfaces they most often configure and try to address
those interfaces in the examples.

Module 12 — Routing Fundamentals

Page 12-8: Correlate route preference with Administrative distance on other vendors.
Page 12-9: Spend some time discussing the difference between Local and Direct routes as this
can be confusing to beginners.
Page 12-9 & 12-11: Explain the best route selection process for the route [Link]/24.
Page 12-18: After talking about routing instances, see if the class can identify where routing
instances would be useful.
Page 12-22: Ask students what if you omit routing-instance options for the commands shown on
the slide.

Lab ILO Suggestions

Verify students were able to get IPv6 connectivity working properly.

Module 13 — Static and Dynamic Routing

Page 13-11: Ask students who have used other vendor devices, why isn’t IGRP, or EIGRP listed as
an IGP protocol. IGRP and EIGRP are proprietary Cisco protocols.
Page 13-13: Spend some time discussing the Link state protocol, SPF algorithm and backbone
area.
Page 13-15: Stress on using the correct unit number for interfaces in OSPF configuration.
Page 13-20: IPv6 introduces to students the concept of link local addresses. Even though the
concept exists in IPv4, you may want to spend extra time making sure students understand the
concept as the term is not widely used in IPv4.

Lab ILO Suggestions

Verify students were able to get OSPF working properly.

Module 14 — Routing Policy

Page 14-2: Spend little extra time to explain the default export policy for protocols as this can be
confusing to beginners.
Page 14-13: On the Route Filter Match Type summary page consider giving students several
different ranges of IP addresses and see if they can come up with the appropriate match filter.
Page 14-23: Though the sample capture is taken on R4, Please inform students that R2 and R3
also receives the exported route from R1.

Lab ILO Suggestions

Lab ILO Suggestions
Verify that students are clear on what they will be doing in the lab and then follow up at the end to
make sure all went well.

Module 15 — Firewall Filters

Page 15-2: Correlate Firewall filters to Stateless ACLs/Packet-Filters for better understanding if
they have different vendors experience.
Page 15-4: Compare the operations of routing policy and firewall filters, as the building blocks are
similar sometimes participants gets confused.
Page 15-16: Spend some time discussing the except options in firewall filters match condition.
Page 15-26 & 15-28: Compare the difference between feasible path and loose mode.
At some point: It might be a good place to talk about the difference between firewall filters and
security policies and that security policies are covered in the security classes.

Lab ILO Suggestions

Take a moment to set this lab up for students so that they have an understanding of what they
need to do.

Module 16 — Class of Service

Page 16-5: CoS processing is dependent on Junos platform. The slide shows processing on SRX
device, and inform participants to consult Juniper documentation for specific platform.
Page 16-11: Spend some time discussing how rewrite works on R1 and based on markings how
classification works on R2.
Page 16-16: It is good time to discuss the importance of forwarding class again, as forwarding
classes are used in other CoS components rather than queues.
Page 16-24: Ask students about when does classification, scheduling and rewriting happens in the
CoS processing.
Page 16-31: Spend some time discussing the default classifier and rewrite-rule, if possible
correlate with slide 12 in the module.

Lab ILO Suggestions

This lab is probably the most complex in the course. It might be a good idea to talk about each lab
part and what students will be doing.

Module 17 — JTAC Procedures

Page 17-3: Ask students about what Juniper online tools have they used ?
Page 17-9: Inform students that Juniper will be launching a new Customer support platform in 2H
2021.
Page 17-18: Spend some time discussing the additional online tools.
If time permits: See if students have ever dealt with JTAC, how did it go?

Module 18 — Junos Security Concepts

Module 18 — Junos Security Concepts
Throughout: Ask students about their organization’s most difficult security challenges and how
they are addressing them. Suggest possible Juniper solutions and courses that they may want to
take to learn more.
Instructor Preparation
In preparation for teaching the class, you should be very familiar with the material and the labs. You should
complete and understand all labs to better serve those you teach. You should download and read current
copies of the following documents (the most current copies of which are available from the Course
Distribution System): the Instructor Notes (this document), the Errata, and Change Log. As you prepare to
teach this course, you may run across errors or have suggestions. Please forward all errata items and course
suggestions to es-dev@[Link].
Classroom Resources
Each student should have the following materials:
Student Guide
Lab Guide including lab diagrams
A pen to take notes

Each classroom should provide the following:

Method for displaying slides
Adequate seating
Access to the virtual lab environment
A computer for each student
Room Arrangement
Each student will work on their own lab environment, so the only requirement for room arrangement is that
each student have adequate space to work on their own.
Suggested Schedule
Day 1
Module 1: Course Introduction
Module 2: Junos Operating System Fundamentals
Module 3: Junos CLI Operational Mode
Module 4: Junos CLI Configuration Mode
Module 5: J-Web Interface
Lab 1: User Interface Options
Module 6: Initial System Configuration
Lab 2: Initial Configuration

Day 2
Module 7: User Authentication Archiving
Lab 3: User Authentication Archiving
Module 8: System Logging, Tracing, NTP, and SNMP
Lab 4: System Logging, Tracing, NTP, and SNMP
Module 9: Operational Monitoring and Maintenance
Lab 5: Operational Monitoring and Maintenance
Module 10: Upgrading the Junos OS
Lab 6: Upgrading the Junos OS
Module 11: Interface Configuration Examples
Module 12: Routing Fundamentals
Lab 7: Routing Fundamentals
Module 13: Static and Dynamic Routing
Lab 8: Static and Dynamic Routing

Day 3
Module 14: Routing Policy
Lab 9: Routing Policy
Module 15: Firewall Filters
Lab 10: Firewall Filters
Module 16: Class of Service
Lab 11: Class of Service
Module 17: JTAC Procedures
Module 18: Juniper Security Concepts
Appendix AA: IPv6 Fundamentals
This course will consume a full three days. Be prepared to stay a full day and set the student’s expectation
accordingly. We suggest that lunch be no more than an hour (less if possible) and that you combine breaks
with the labs.
Homework
Assign your students homework. Your students have high expectations from taking this class and there are
some things best learned through individual study of detailed case studies presented in the Student Guide.
Assigning study of this information as homework provides both the most efficient use of class time as well as
the most effective student experience.
Lab Setup
For detailed lab setup instruction, see the .
For details about the physical topology and course setup, review the IJOS Setup Guide. This document can be
retrieved through the Course Distribution System (CDS) and is found in the \GeneralInfo\Lab Setup\IJOS
directory.
Each student will have their own virtual environment, consisting of two vSRX devices (vSRX-1 and vSRX-2) and
a student desktop/server. This course requires Junos Software Release [21.1R1.11] for the vSRX.
The student desktop/server, as well as providing a graphical desktop from which the students can access
their vSRX, is also used for RADIUS, NTP synchronization, configuration archival, and as the primary storage
location for the software image and the configuration files used with in the labs. The server requirements
include:
User account ftp with password of ftp used for file transfers
Directory /var/ftp/archive used for configuration archival
Directory /Documents/IJOS used as storage location for config files.
Verify that you have the [Link] Junos install package on your
server under /home/lab directory.
Directory /home/lab used as storage location for [Link] and [Link] files.
Services and protocols enabled (ftp, NTP, RADIUS).

Note: There is no special configuration required for the

RADIUS server requirement. The server is simply
required to listen for authentication requests and
respond with a failed response.
Lab Infrastructure Information
IP Addressing
The addresses used throughout the labs are private addresses and may vary depending on the device’s
interface and lab. For addressing details, please refer to the management topology diagram and the topology
diagrams for the individual labs.

Lab Infrastructure
All students use the same lab topology and network topology diagrams. Before class begins, you should
ensure that the reset configuration files have been loaded and committed on the student and instructor
devices in the /var/home/lab/ijos directory.
Lab Notes
In general, the labs are quite complex and, as such, will require fairly regular instructor monitoring. Students
will probably also benefit from post-lab debriefing and discussion.
Before class begins you should ensure the student devices and the instructor’s device are running the correct
version of software and that each device has its respective reset configuration loaded and committed. You
should also ensure that the reset configurations for each student device is saved in the /var/home/lab/ijos
directory.
Every lab has been re-engineered to fit a modularized format, in which prescriptive trainings can be created
from putting various labs together. To this end, most labs have a step at the beginning in which a starting
configuration is loaded. The lab starting configurations should be in the /var/home/lab/ijos directory and be
in the format of [Link], where X is the lab number.

Note: The configuration files provided by Juniper, have

the root password on the student devices set to
training1. The student devices should all have a student
user account named lab with a password of lab123.

Please note! The J-Web interface was recently redesigned and we have included both a CLI and a J-Web
version of each lab. However, there are some lab steps that can only be performed using the CLI. Take care to
explain this to students before the labs begin.
Before beginning the first lab, you need to make the student device assignments and provide the access
details for the lab equipment. A sample management network diagram is provided on the first page in the lab
diagrams booklet. You’ll simply need to provide the students with the access and login details for your
designated delivery environment.

Lab 1
CLI
This lab introduces the students to the Junos software command-line interface (CLI). In this lab, students
become familiar with various CLI operational-mode and configuration-mode features. Some common
problems encountered:
Initial access to student environment. We recommend writing the access details on the board and
leaving them there. As noted above, we use the traditional lab/lab123 credentials for access to the
student devices.

J-Web
This lab introduces students the J-Web graphical user interface (GUI). In this lab, students will familiarize
themselves with the various J-Web features and capabilities.
For this lab and all remaining labs, students must first connect to the CLI to load and commit the current
configuration for the lab. Although students can upload configs from a desktop using the J-Web interface,
students can not access /var/home/lab/ijos using the J-Web interface.
Likewise, there might be other moments, such as step 2.5, where students will need to switch to the CLI to
perform the step. For this reason, we suggest making sure students have access to both the CLI and the J-
Web interface for each lab.

Lab 2
Lab 2
CLI
In this lab, students use the CLI to perform configuration steps typically associated with initial installation of
Junos platforms. Some common problems encountered:
Students are asked to load the contents of the reset configuration over the top of the configuration
they’ve built at the start of part 2. This file is located in the /var/home/lab/ijos directory and has
to be loaded, even if a lab is taught from start to finish.
When using vSRX 3.0, students might no longer receive the warning to reboot the device when
switching to packet mode. Accordingly, the lab step to reboot the device has been removed;
however, the student might still need to reboot the device if prompted, or if the device is not
operating in the correct mode.

J-Web
Part 1 uses the CLI exclusively. You switch over to the J-Web for Part 2, after you have loaded the part2-start
config.

Lab 3
CLI
In this lab, students use the CLI to perform configuration steps typically associated with secondary system
configuration (Authentication and Archival). Some common problems encountered:
Students are directed to maintain an active console connection to their assigned device. If they do
not follow this direction, they will likely be locked out due to the defined authentication order. If a
student team cannot login to their assigned device, you or the student may be required to login to
the server and halt the RADIUS service momentarily while they regain access.
It is recommended to execute step 1.16 via an SSH session from the student desktop. When
logging in as Nancy at step 1.16 using cloudshell, open another terminal session on the student
desktop and ssh using this command: ssh nancy@[Link]. If students ssh directly to the srx
from cloudshell they will be denied and in the next step they only need to use 1 password.

Note: In Juniper environments, the lab user on the

student desktop/server is allowed to use the sudo
command. The commands to perform this operation are:
sudo systemctl stop [Link]
sudo systemctl start [Link]

Step 2.1 make sure that permissions are properly set on the student desktop so that the ftp
account functions properly. If the FTP file transfer fails, try issuing the following commands from
the shell on the student desktop:

Note: In case FTP service gets stuck on student desktop,

use the following commands on the student desktop to
restart the FTP service
sudo systemctl stop [Link]
sudo systemctl start [Link]
 Try the following using root:
cd /var/ftp
chown –R ftp archive
chmod 777 archive

J-Web
Watch for the same issues that might occur in the CLI version of the lab. Note that the passwords are different
in the J-Web labs vs. the CLI labs for Walter and Nancy. This is because the J-Web interface will not allow you
to create such simple passwords as walter123 or nancy123. This should only be a problem if students switch
between using the CLI and J-Web lab guides.

Lab 4
CLI
In this lab, students use the CLI to perform configuration steps typically associated with secondary system
configuration (Syslog, NTP, and SNMP). Some common problems encountered:
In some cases, the NTP server connection will fail. Check that the service is running on the
desktop by issuing the command systemctl status ntpd on the linux desktop. Start the service by
issuing the systectl start ntpd and systemctl enable ntpd commands, in that order. It appears that,
in some instances, the service must be running for several minutes before successful connections
are made to the server.

J-Web
Watch for the same issues that exist in the CLI lab guide. Also, the same issue with Walter and Nancy’s
passwords from Lab 3 exist in this lab as well. In this case, if you load the starting configuration at the
beginning of the lab, as instructed, you will find that your walter and Nancy accounts have the same simple
passwords, as defined in the CLI lab.

Lab 5
CLI
This lab covers common operational monitoring and platform maintenance activities. In this lab students
monitor system and chassis operation, use network utilities, and perform system maintenance tasks. Some
common problems encountered:
Questions may arise regarding the truncated messages in the monitored output during Step 2.4.
These messages are caused by the default capture size of 96 bytes and can be eliminated by
specifying a larger size (e.g. 1520).

J-Web
Watch for the same issues that exist in the CLI lab guide. Also, the same issue with Walter and Nancy’s
passwords from Lab 3 exist in this lab as well. In this case, if you load the starting configuration at the
beginning of the lab, as instructed, you will find that your walter and Nancy accounts have the same simple
passwords, as defined in the CLI lab.

Lab 6
Lab 6
CLI
This lab covers storage cleanup and upgrade activities. Though start configuraiton (and reset at the end) is
not needed, these steps included for consistency.
If any student issues, the zeoise command, might need to rebuild the VM (incase of any issues)
As mentioned above, please verify that you have the following Junos install package on your server:
[Link]

Note: In case FTP service gets stuck on student desktop,

use the following commands on the student desktop to
restart the FTP service
sudo systemctl stop [Link]
sudo systemctl start [Link]

J-Web
Watch for the same issues that exist in the CLI lab guide. Also, the same issue with Walter and Nancy’s
passwords from Lab 3 exist in this lab as well. In this case, if you load the starting configuration at the
beginning of the lab, as instructed, you will find that your walter and Nancy accounts have the same simple
passwords, as defined in the CLI lab.

Lab 7
CLI
This lab demonstrates configuration and monitoring of Layer 3 routing on Junos platforms. In this lab students
use the CLI to configure and monitor interfaces. Throughout these configuration tasks, the students will
become familiar with and describe the contents of the routing and forwarding tables. Make sure that IPv6
connectivity is established and packet-mode is set for family IPv6.
Students were given a choice to choose manual method or Junos automation in order to load the lab-start
config to the vSRX-1 in the lab.

J-Web
There are still some elements that must be configured or monitored using the CLI but not from J-Web
interface. In this lab to display the routing table, switch to CLI.
While testing IPv6 connectivity, it may take 10-15 seconds to display the ping packet failures.

Lab 8
CLI
This lab demonstrates configuration and monitoring of static routing and dynamic routing using OSPF on
Junos platforms. In this lab students use the CLI to configure and monitor static routing, and basic OSPF. Note
that there should no longer be issues with OSPFv3 adjacencies forming. We have corrected the networking
assignments in vSphere for the vSRX-1 and vSRX-2 devices. If you are still seeing issues, verify that the
network interfaces are correctly configured in vSphere in your lab environment.
Students were given a choice to choose manual method or Junos automation in order to load the lab-start
config to the vSRX-1 in the lab.

J-Web
J-Web
There are still some elements that must be configured or monitored using the CLI but not from J-Web
interface. In this lab, to configure qualified next hop option, switch to CLI.

Lab 9
CLI
This lab demonstrates configuration and monitoring of routing policy on Junos platforms. In this lab students
use the command-line interface (CLI) to define, apply, and monitor basic routing policy.
Note that sometimes students may miss the step to apply the routing policy to OSPF protocol in the lab.

J-Web
In this lab, students will use the CLI editor to adjust the configuration in certain steps. It’s important that the
student adds the configuration exactly as it is written in the lab guide, otherwise the student will not be able
to commit the configuration. If this is too frustrating for the student, you can always suggest that they switch
to the CLI for lab steps that include using the CLI Editor.

Note: Students will certainly ask why some steps are not
supported in the J-Web interface. The best explanation
you can offer is that this is a brand new version of J-Web
and that these configuration elements that currently
don’t work in the J-Web will improve over time.

Lab 10
CLI
This lab demonstrates configuration and monitoring of firewall filters on Junos platforms. In this lab you use
the command-line interface (CLI) to define, apply, and monitor firewall filters.

J-Web
Sometimes the linux desktop does not display drop-down menus correctly within the J-Web Interface.
Sometimes restarting the browser or switching to another browser will resolve the issue, but restarting the
desktop will always resolve the issue. This appears to be an issue with the Linux browsers, not with the J-Web
Interface.

Lab 11
CLI
This lab explores basic class of service (CoS) configuration for devices running Junos [Link] this lab you
use the command-line interface (CLI) to define, apply, and monitor CoS components.

J-Web
No specific issues are known for this lab, but keep in mind some of the issues and comments from previous
labs when using the J-Web Interface.