Junos Operating System Highlights(SSFJUN01Ia_LabGuide)

Junos Operating System Highlights

Lab Guide

Worldwide Education Services 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000 www.juniper.net

Course Number: SSFJUN01 SSFJUN01

This document is produced by Juniper Networks, Inc. This document or any part thereof may not be reproduced or transmitted in any form under penalty of law, without the prior written permission of Juniper Networks Education Services. Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks o f Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Junos Operating System Highlights Lab Guide Copyright © 2012 Juniper Networks, Inc. All rights reserved. Revision History: July, 2010 November, 2011 April, 2012 July 2012 The information in this document is current as of the date listed above. The information in this document has been carefully verified and is believed to be accurate for software Release 11.4R1.6. Juniper Networks assumes no responsibilities for any inaccuracies that may appear in this document. In no event will Juniper Networks be liable for direct, indirect, special, exemplary, incidental, or consequential damages resulting from any defect or omission in this document, even if advised of the possibility of such damages.

Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. YEAR 2000 NOTICE Juniper Networks hardware and software products do not suffer from Year 2000 problems and hence are Year 2000 compliant. The Junos operating system has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036. SOFTWARE LICENSE The terms and conditions for using Juniper Networks software are described in the software license provided with the software, or to the extent applicable, in an agreement executed between you and Juniper Networks, or Juniper Networks agent. By using Juniper Networks software, you indicate that you understand and agree to be bound by its license terms and conditions. Generally speaking, the software license restricts the manner i n which you are permitted to use the Juniper Networks software, may contain prohibitions against certain uses, and may state conditions under which the license is automatically terminated. You should consult the software license for further details.

Contents Lab 0: 0: Lab

Introduction Intr Introd oduc ucti tion on to to the the Juniper Juni Junipe perr Networks Netw Networ orks ks Virtual Vir Virtu tual al Lab Lab Lab . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .0 ..0-1 0-1 Part Part Part Part Part Part Part Part

Lab 1: 1: Lab

1: 2: 3: 4: 5: 6: 7: 8:

Accessing the Virtual Lab Homepage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-2 Accepting the EULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-2 Logging in to the TrueLab Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-2 Selecting Your Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-3 Creating an On-Demand Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-4 Creating a Dynamic Session (If the On-Demand Session Is Unavailable) . . . . . . . . . . . . . . . . . . . . . . 0-5 Starting the Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-6 Additional Information and Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-9

Junos Jun Junos Operating Oper Operat atin ing g System Sy System stem Highlights Hig Highlig hligh hts . . . . .. .. .. .. .. . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .....1 ..1-1 1-1 Part 1: Logging In Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Part 2: Experimenting with the CLI’s Operational Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Part 3: Entering Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Lab 2: 2: Lab

Configuring Conf Config igur urin ing g Junos Jun Junos os OS OS Using Us Using ing the the the CLI CLI . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .2 ..2-1 2-1 Part 1: Exploring Configuration Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Part 2: Using a Rescue Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Lab 3: 3: Lab

Configuring Conf Config igur urin ing g OSPF OSP OSPF F on on Junos Jun Junos os OS OS Devices Dev Devices ices . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .3 ..3-1 3-1 Part 1: Configuring and Monitoring Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Part 2: Configuring and Monitoring Static Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Part 3: Configuring and Monitoring OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Appendix A: Lab Diagrams . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .A-1 .. A-1

www.juniper.net

Contents • iii

iv • Contents

www.juniper.net

Document Conventions CLI and GUI Text Frequently throughout this course, we refer to text that appears in a command-line interface (CLI) or a graphical user interface (GUI). To make the language of these documents easier to read, we distinguish GUI and CLI text from chapter text according to the following table. Style

Description

Usage Example

Franklin Gothic

Normal text.

Most of what you read in the Lab Guide and Student Guide.

Courier New

Console text:

commit complete

•

Screen reen captures

•

Nonc Noncom omma mand nd-r -rel elat ated ed synta syntaxx

Select File > Open, and then click Configuration.conf in the Filename text box.

GUI text elements: •

Menu names

•

Text fiel field d entry try

Exiting configuration mode

Input Text Versus Output Text You You will also frequently see cases cases where you must enter input text text yourself. Often this will be shown in the context of where you must enter it. We use bold style to distinguish text that is input versus text that is simply disp layed. Style

Description

Usage Example

Normal CLI

No distinguishing variant.

Physical interface:fxp0, Enabled

Normal GUI

View configuration history by clicking Configuration > History.

CLI Input

Text that you must enter.

lab@San_Jose> show route Select File > Save, and enter config.ini in the Filename field.

GUI Input

Defined and Undefined Syntax Variables Finally, this course distinguishes between regular text and syntax variables, and it also distinguishes between syntax variables where the value is already assigned (defined variables) and syntax variables where you must assign the value (undefined variables). Note that these styles can be combined with the input style as well. Style

Description

Usage Example

CLI Variable

Text Text where variable value is already assigned.

policy

GUI variable

my-peers

Click my-peers in the dialog.

Type set policy is the user’s discretion and text policy-name. GUI Undefined where the variable’s value as ping 10.0.x.y 10.0.x.y shown in the lab guide might differ from the value the user Select File > Save, and enter must input. filename in the Filename field. CLI Undefined Text Text where the variable’s value

www.juniper.net

Document Conventions • v

vi • Document Conventions

www.juniper.net

Lab 0 Introduction to the Juniper Networks Virtual Lab

Overview This lab shows the basic procedures for how to access the Juniper Networks Virtual Lab (vLab) using a standard Web browser.

The Purpose of the Virtual Labs

The vLabs help partners receive hands-on training through a virtual portal which is available 24 hours a day, 7 days a week. This is not a simulator, but live equipment to promote learning and development for interested partners to the Juniper Networks Partner Learning Academy. The vLab exercises assist a student to become proficient at installing, configuring, and troubleshooting Juniper products. Each JNSS track takes approximately 8 hours to complete. Once connected to the vLab site, you will nee d to register (with a valid e-mail address) and then log in. Access is granted on a first come, first serve basis through the training section of the Partner Center. The vLabs are also available for dedicated instructor-led courses on an as needed basis. The system will check to see if one of the selected labs is available. If a vLab is available, access is granted. I f no lab is available, you will be asked to try again later. Each of the vLabs is duplicated multiple times. In the case of the Router/Firewall lab there are extra cross connects between the labs so that in a classroom environment they can be connected in interesting network topologies. Note

We recommend that you download and read the course lab guide prior to star ting your lab. The guide provides important information to access the lab environment and the labs themselves.

Introduction to the Juniper Networks Virtual Lab • Lab 0–1

Part 1: Accessing the Virtual Lab Homepage The first step in accessing the Virtual Lab is to login to the vLab homepage. To access the Virtual Lab home page, copy and paste the below URL into a browser window: https://virtuallabs.juniper.net

Part 2: Accepting the EULA You will need to accept the End User License Agreement to log in and begin your work in the Virtual Lab.

Part 3: Logging in to the TrueLab Manager If you are already logged in to the Partner Lear ning Academy on the Juniper Partner Center, you will not need to log in to TrueLab Manager. However, if you are not logged in to the Partner Center, you can log in on this sc reen.

Lab 0–2 • Introduction to the Juniper Networks Virtual Lab

Part 4: Selecting Your Time Zone Next, you must specify a time zone. Once your correct time zone has been specified, click Update in the bottom left corner of the screen.

Step 4.1 You can modify your user name, password, and time zone if necessary by clicking on the Profile tab. Once you have made the updates, you must click Update to save these changes.


Part 5: Creating an On-Demand Session You will then create a session under the Sessions tab and select the lab that you want to use. First, identify the correct row for your course under the Event heading. Next, select the course title from the Purpose drop down menu under the Session Information column and click Open.

Note Click the View Event Details link under each Event description to access the course lab guide and credentials.


Part 6: Creating a Dynamic Session (If the On-Demand Session Is Unavailable) To reserve a dynamic session, first identify the correct row for your course under the Event heading. Next, select the course title from the Purpose drop down menu under the Session Information column and the lab you want to schedule under the Lab Option drop down menu. Click Reserve to schedule a session.


Step 6.1 Click Start Session Now.

Step 6.2 Click Finish to return to the Sessions tab.

Note The system will send you a reminder e-mail prior to your session start time.

Part 7: Starting the Session Once the Start Session Now link has been clicked (under the session link), you will be prompted to click OK to continue and log in.


Note Each session can be a maximum of 3 hours.

Step 7.1 Click OK to see the following screen.

Note Do not close the browser window. Closing your browser window will disconnect your Virtual Lab session connected.


Step 7.2 Once you have an active session, you will see the following virtual desktop screen. On this virtual desktop, you must double-click on the Secure CRT icon to begin your lab.

Note The Help tab also has links to the related course lab guide and vLab environment help guides.


Step 7.3 Choose the device you will be working with in the Secure CRT session and click Connect.

Note Make sure that you consult your lab guide before opening any of the VT100 terminal sessions.

Part 8: Additional Information and Feedback Connection Test You can test your ability to connect by navigating to https://truelab.hatsize.com/syscheck/sunnyvale/. Virtual Lab Support For support, please call 1-866-933-5487 (207-319-1142 if outside North America) Go to: https://support.hatsize.com/ Or send an e-mail to [email protected] Feedback If you would like to provide feedback on ways we can improve your vLab experience, please an e-mail to [email protected].

STOP



Lab 1 Junos Operating System Highlights

Overview This lab introduces you to the Junos OS command-line interface (CLI). In this lab, you will familiarize yourself with various CLI operational mode features. By completing this lab, you will perform the following tasks:

www.juniper.net

•

Log in to the CLI.

•

Explore the Junos OS CLI operational mode.

Junos Operating System Highlights • Lab 1–1 11.4R1.6


Part 1: Logging In Using the CLI The goal of this lab part is for you to become familiar with the access details used to connect to the lab equipment. Once you are familiar with the access details, you will use the CLI to log in to your designated device. Step 1.1 Access the CLI using SecureCRT. Double click on the SecureCRT 5.0 icon located on the desktop to open the connection manager. Highlight SRX1 and click Connect.

Step 1.2 Log in as user lab with the password lab123.

login: lab Password: --- JUNOS 11.4R1.6 built 2011-11-15 12:44:14 UTC lab@srxB-1>

Part 2: Experimenting with the CLI’s Operational Mode In this part, you will use the CLI to become familiar with operational mode. You will also gain experience with some of the tools and functionality available within operational mode. Step 2.1 Determine what system information you can clear from the operational mode command prompt.

lab@srxB-1> clear ? Possible completions: amt arp auto-configuration

Show AMT Protocol information Clear address resolution information Clear auto-configuration action

Lab 1–2 • Junos Operating System Highlights

www.juniper.net


bfd bgp bridge chassis database-replication dhcpv6 dot1x esis ethernet-switching firewall gvrp helper igmp igmp-snooping interfaces ipv6 isdn isis information l2-learning lacp ldp lldp log mld mpls msdp multicast network-access ospf ospf3 passive-monitoring pfe pgm pim ppp pppoe r2cp rip ripng rsvp security services snmp spanning-tree system vpls vrrp wlan

www.juniper.net

Clear Bidirectional Forwarding Detection information Clear Border Gateway Protocol information Clear learned Layer 2 MAC address information Clear chassis information Clear database replication information Clear DHCPv6 information Clear 802.1X session Clear end system-to-intermediate system information Clear ethernet switching information Clear firewall counters Clears Generic VLAN Registration Protocol information Clear port-forwarding helper information Clear Internet Group Management Protocol information Clear IGMP snooping information Clear interface information Clear IP version 6 information Clear Integrated Services Digital Network information Clear Intermediate System-to-Intermediate System Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear Clear

learned Layer 2 MAC address information Link Aggregation Control Protocol information Label Distribution Protocol information Link Layer Discovery Protocol information contents of log file multicast listener discovery information mpls information Multicast Source Discovery Protocol information multicast information network-access related information Open Shortest Path First information Open Shortest Path First version 3 information passive monitoring statistics Packet Forwarding Engine information Pragmatic Generalized Multicast information Protocol Independent Multicast information PPP information PPP over Ethernet information Radio-to-Router Protocol information Routing Information Protocol information Routing Information Protocol for IPv6 information Resource Reservation Protocol information security information services Simple Network Management Protocol information Spanning Tree Protocol information system information learned Layer 2 MAC address information Virtual Router Redundancy Protocol statistics Wireless LAN information

Junos Operating System Highlights • Lab 1–3


Question: Which command do you use to clear the contents of a system log (syslog) file?

Answer: Use the clear log log-filename command to clear the contents of a particular syslog file. Step 2.2 Experiment with command completion by entering show i.

lab@srxB-1> show i ^ 'i' is ambiguous. Possible completions: iccp Show igmp Show igmp-snooping Show ingress-replication Show interfaces Show ipv6 Show isdn Show isis Show information

Inter Chassis Control Protocol information Internet Group Management Protocol information IGMP snooping information Ingress-Replication tunnel information interface information IP version 6 information Integrated Services Digital Network information Intermediate System-to-Intermediate System

Step 2.3 Add characters to disambiguate your command so that you can display interface-related information; use the Spacebar or Tab key for automatic command completion. Note

You can return to the command prompt without scrolling through all of the generated output from a command. Enter ‘q’ to abort the operation and return to the command prompt.

lab@srxB-1> show interfaces Physical interface: ge-0/0/0, Enabled, Physical link is Up Interface index: 134, SNMP ifIndex: 509 Description: MGMT Interface - DO NOT DELETE Link-level type: Ethernet, MTU: 1514, Link-mode: Full-duplex, Speed: 1000mbps, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled, Remote fault: Online Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x0 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Current address: b0:c6:9a:7a:88:00, Hardware address: b0:c6:9a:7a:88:00 Last flapped : 2012-07-11 23:10:36 UTC (14:46:41 ago) Input rate : 472 bps (0 pps) Lab 1–4 • Junos Operating System Highlights

www.juniper.net


Output rate : 0 bps (0 pps) Active alarms : None Active defects : None Interface transmit statistics: Disabled Logical interface ge-0/0/0.0 (Index 69) (SNMP ifIndex 510) Flags: SNMP-Traps 0x0 Encapsulation: ENET2 Input packets : 32141 Output packets: 173 Security: Zone: Null Protocol inet, MTU: 1500 Flags: Sendbcast-pkt-to-re, Is-Primary Addresses, Flags: Is-Default Is-Preferred Is-Primary Destination: 10.210.14.128/27, Local: 10.210.14.133, Broadcast: 10.210.14.159 ...TRIMMED... Step 2.4 Try to clear SNMP statistics by entering the clear snmp command.

lab@srxB-1> clear snmp ^ syntax error, expecting . Question: What do you think the resulting display means?

Answer: The display indicates that the command was incomplete as entered. The carrot symbol (^) indicates the area of the problem, and the error message tells you that the system expects additional command input. Step 2.5 Verify that the CLI will not let you complete invalid commands by trying to enter the command show ip interface brief.

lab@srxB-1> show ip lab@srxB-1> show ipv6 lab@srxB-1> show ipinterfacebrief ^ syntax error, expecting .

www.juniper.net



Question: What happens when you try to enter this command?

Answer: The system’s command completion feature completes a show ipv6 command in this case because ipv6 is the only valid completion. If you attempt to continue with invalid syntax, the system informs you of your error. Unlike some CLI implementations, Junos OS will not let you waste time typing in an illegitimate command! Step 2.6 Enter a show route command followed by a show system users command. You are entering these commands to demonstrate command history recall. When finished, enter the keyboard sequences indicated to answer the related questions.

lab@srxB-1> show route inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.210.14.128/27 10.210.14.133/32

*[Direct/0] 14:48:08 > via ge-0/0/0.0 *[Local/0] 14:48:17 Local via ge-0/0/0.0

lab@srxB-1> show system users 1:58PM up 14:51, 1 user, load averages: 0.06, 0.09, 0.08 USER TTY FROM LOGIN@ lab u0 Wed11PM

IDLE WHAT - -cli (cli)

Question: What happens when you press the up-arrow key twice?

Answer: The system recalls the show route command and displays it at the prompt. Question: What happens when you press the down-arrow key once?

Answer: The system recalls the next command in the buffer, which is a show system users command in this example.


www.juniper.net


Step 2.7 A large portion of the Junos OS documentation is available directly from the CLI. You can retrieve high-level topics using the help topic command, whereas you can obtain detailed configuration-related information with the help reference command. Use the help reference command along with the CLI question-mark operator (?) to find detailed information about configuring a system hostname. Question: Which CLI command displays reference information about configuration of the system’s hostname?

Answer: The help reference system host-name command displays information regarding system hostnames.

lab@srxB-1> help reference system host-name host-name

Syntax host-name hostname; Hierarchy Level [edit system] Release Information Statement introduced before JUNOS Release 7.4. Statement introduced in JUNOS Release 9.0 for EX Series switches.

Description Set the hostname of the router or switch.

Options hostname--Name of the router or switch. Required Privilege Level system--To view this statement in the configuration. system-control--To add this statement to the configuration. Related Topics * Configuring the Hostname of the Router

www.juniper.net



Part 3: Entering Configuration Mode In this part, you will enter and explore configuration mode. Step 3.1 Enter configuration mode.

lab@srxB-1> configure Entering configuration mode [edit] lab@srxB-1# Question: What happens to your prompt?

Answer: A pound sign (#) replaces the angle bracket (>), and a configuration hierarchy banner displays. Question: According to the prompt, what is your position in the configuration hierarchy?

Answer: The display indicates that you are now at the [edit] hierarchy, which is the root of the configuration tree. Step 3.2 Display the interfaces portion of the candidate configuration.

[edit] lab@srxB-1# show interfaces ge-0/0/0 { description "MGMT Interface - DO NOT DELETE"; unit 0 { family inet { address 10.210.14.133/27; } } }

STOP

You have completed Lab 1. Please return to the course and complete the next section.


www.juniper.net

Lab 2 Configuring Junos OS Using the CLI

Overview This lab continues to explore the functionality of the Junos OS command-line interface (CLI). In this lab, you will familiarize yourself with various CLI configuration mode features. By completing this lab, you will perform the following tasks:

www.juniper.net

•

Explore the Junos OS CLI using configuration mode.

•

Save, view, and use a rescue configuration.

Configuring Junos OS Using the CLI • Lab 2–1 11.4R1.6


Part 1: Exploring Configuration Mode In this part, you will use the CLI to explore configuration mode. Step 1.1 Access the CLI using SecureCRT. Double click on the SecureCRT 5.0 icon located on the desktop to open the connection manager. Highlight SRX1 and click Connect.


login: lab Password: --- JUNOS 11.4R1.6 built 2011-11-15 12:44:14 UTC lab@srxB-1> Step 1.3 Issue the configure command to enter configuration mode.

lab@srxB-1> configure Entering configuration mode Step 1.4 Move to the [edit protocols ospf] portion of the hierarchy. This step requires that you first visit the root of the hierarchy, as you cannot jump directly between branches. You can perform this step with a single command in the form of top edit protocols ospf, however.

[edit interfaces] lab@srxB-1# top edit protocols ospf [edit protocols ospf]

Lab 2–2 • Configuring Junos OS Using the CLI

www.juniper.net


Question: Which commands can you now enter to reposition yourself at the [edit] portion of the hierarchy? Return to the [edit] hierarchy level now.

Answer: You can issue an up command twice, or an up 2 command. You can also issue an exit command or a top command.

[edit protocols ospf] lab@srxB-1# top [edit] lab@srxB-1# Note

If you have not already done so, return to the [edit] hierarchy level using one of the available methods. Step 1.5 Try to display the status of chassis hardware with a show chassis hardware operational command while in configuration mode.

[edit] lab@srxB-1# show chassis hardware ^ syntax error. Question: Why do you think you received an error? What can you do to execute operational mode commands while in configuration mode? Try that now.

Answer: The command issued is not valid in configuration mode. Precede operational mode commands with the keyword run to execute them while in configuration mode:

www.juniper.net

Configuring Junos OS Using the CLI • Lab 2–3


[edit] lab@srxB-1# run show chassis hardware Hardware inventory: Item Version Part number Chassis Routing Engine REV 37 750-024366 FPC 0 PIC 0 Power Supply 0

Serial number BD5009AA0022 AABA9253

Description SRX240H-POE RE-SRX240H-POE FPC 16x GE Base PIC

Step 1.6 Try to return to operational mode by entering an exit command.

[edit] lab@srxB-1# exit The configuration has been changed but not committed Exit with uncommitted changes? [yes,no] (yes) Question: What happens when you execute the exit command?

Answer: You should see a message indicating that uncommitted changes exist. This message results from the creation of an empty [edit protocols ospf] stanza. This empty stanza causes the configuration database to believe that the configuration actually changed. Question: Which CLI command can you use to display differences between the candidate and active configuration file? Enter no at the current prompt and issue the required command to view the differences between the candidate and active configurations.

Answer: Use the show command with the results piped to compare rollback number . In this example, you should not see any actual configuration changes, as shown in the following sample capture:


www.juniper.net


The configuration has been changed but not committed Exit with uncommitted changes? [yes,no] (yes) no Exit aborted [edit] lab@srxB-1# show | compare rollback 0 [edit] lab@srxB-1# Question: Considering that nothing changed, which command can you enter in order to exit from configuration mode without being warned of uncommitted changes? Issue that command now.

Answer: Issue a rollback 0 command to replace the candidate configuration with a new copy of the active configuration. You can now exit configuration mode without any being warned of uncommitted changes:

[edit] lab@srxB-1# rollback 0 load complete [edit] lab@srxB-1# exit Exiting configuration mode lab@srxB-1>

Part 2: Using a Rescue Configuration In this part, you will save, display, load, and delete a rescue configuration using the Junos OS CLI. Step 2.1 Save the active configuration as the rescue configuration.

lab@srxB-1> request system configuration rescue save lab@srxB-1 Step 2.2 Display the contents of the recently saved rescue configuration.

www.juniper.net



lab@srxB-1> file show /config/rescue.conf.gz ## Last changed: 2012-07-12 13:52:08 UTC version 11.4R1.6; system { host-name srxB-1; root-authentication { encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/ O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/ gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/ Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/ zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBH x9elwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF 2KHBSIxL51lmIDW8Gql9hJfD/Dr/ NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu 2C8UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/ g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= [email protected]"; } login { user lab { uid 2000; class super-user; authentication { encrypted-password "$1$84J5Maes$cni5Hrazbd/IEHr/50oY30"; } } } services { ssh; telnet; } syslog { user * { any emergency; } file messages { any any; authorization info; } file interactive-commands { interactive-commands any; } } } interfaces { ge-0/0/0 { description "MGMT Interface - DO NOT DELETE"; unit 0 { family inet { address 10.210.14.133/27; } } } } Lab 2–6 • Configuring Junos OS Using the CLI

www.juniper.net


security { forwarding-options { family { mpls { mode packet-based; } } } } Question: Does the rescue configuration match the recently created active configuration?

Answer: Yes, the rescue configuration should match the recently created active configuration. Step 2.3 Return to configuration mode and delete either ssh or telnet access to the device (whichever one you are NOT using), under the [edit system services] hierarchy level. Activate the change.

lab@srxB-1> configure Entering configuration mode [edit] lab@srxB-1# delete system services telnet [edit] lab@srxB-1# commit commit complete Step 2.4 Verify that the appropriate service has been deleted under the [edit system services] hierarchy level and then load the rescue configuration.

[edit] lab@srxB-1# show system services ssh; [edit] lab@srxB-1# rollback rescue load complete Step 2.5 Verify that both the ssh and telnet services are once again enabled.

[edit] lab@srxB-1# show system services ssh; telnet; Step 2.6 Activate the rescue configuration and return to operational mode. www.juniper.net



[edit] lab@srxB-1# commit and-quit commit complete Exiting configuration mode lab@srxB-1> Step 2.7 Delete the rescue configuration and attempt to display the rescue.conf.gz file to confirm the deletion.

lab@srxB-1> request system configuration rescue delete lab@srxB-1> file show /config/rescue.conf.gz error: could not resolve file: /config/rescue.conf.gz Question: Did you successfully delete the rescue configuration?

Answer: Yes, based on the CLI’s feedback, the deletion of the rescue configuration was successful.

STOP

You have completed Lab 2. Please return to the course and complete the next section.


www.juniper.net

Lab 3 Configuring OSPF on Junos OS Devices

In this lab, you will use the Junos OS command-line interface (CLI) to configure and monitor static routing and basic OSPF. Throughout these configuration tasks, you will become familiar with and describe the contents of the routing and forwarding tables. By completing this lab, you will perform the following tasks:

www.juniper.net

•

Configure and monitor static routing.

•

Configure and monitor OSPF.

Configuring OSPF on Junos OS Devices • Lab 3–1 11.4R1.6


Part 1: Configuring and Monitoring Interfaces In this lab part, you will load a basic configuration from flash memory, then configure a new network interface on your assigned device. You will then verify that the interface is operational and that the system adds the corresponding route table entries for all the configured interfaces on your device. Step 1.1 Access the CLI using SecureCRT. Double click on the SecureCRT 5.0 icon located on the desktop to open the connection manager. Highlight SRX1 and click Connect.


login: lab Password: --- JUNOS 11.4R1.6 built 2011-11-15 12:44:14 UTC lab@srxB-1> Step 1.3 Enter Configuration mode using the configure command.

lab@srxB-1> configure Entering configuration mode Step 1.4 Using the load override command, load the file lab3p1s4.config from the /var/home/lab/ssfjun01/ directory. This will load the basic configuration needed to complete the lab. Issue the commit command to apply the changes and exit configuration mode.

Lab 3–2 • Configuring OSPF on Junos OS Devices

www.juniper.net


[edit] lab@srxB-1# load override /var/home/lab/ssfjun01/lab3p1s4.config [edit] lab@srxB-1# commit commit complete [edit] lab@srxB-1# Step 1.5 Open a new SecureCRT tab and connect to the SRX2 device. Enter configuration mode and load the lab3p1s9.config file from the /var/home/lab/ssfjun01/ directory. Commit the changes and exit when complete. Click File > Connect in Tab from the SecureCRT window.

www.juniper.net

Configuring OSPF on Junos OS Devices • Lab 3–3


Step 1.6 Select SRX2 from the available devices and click Connect.


srxB-2 (ttyp0) login: lab Password: --- JUNOS 11.4R1.6 built 2011-11-15 12:44:14 UTC lab@srxB-2> Step 1.8 Enter configuration mode.

lab@srxB-2> configure Entering configuration mode [edit] lab@srxB-2# Step 1.9 Load the configuration file and then exit. Exit the device and close the tab and return to the SRX1 device.

[edit] lab@srxB-2# load override /var/home/lab/ssfjun01/lab3p1s9.config [edit] lab@srxB-2# commit and-quit commit complete Exiting configuration mode


www.juniper.net


lab@srxB-2> exit srxB-2 (ttyu0) login: Step 1.10 Return back to the SRX1 device. Navigate to the [edit interfaces] hierarchy level.

[edit] lab@srxB-1# edit interfaces [edit interfaces] lab@srxB-1# Step 1.11 Refer to the following diagram and configure the new interface, ge-0/0/4, for your assigned device. Use the VLAN-ID as the logical unit value for the tagged interface. VLAN Assignments Hostname

VLAN-ID

srxA-1

101

srxB-1

103

srxC-1

105

srxD-1

107

[edit interfaces] lab@srxB-1# set ge-0/0/4 vlan-tagging [edit interfaces] vlan-id 10v lab@srxB-1# set ge-0/0/4 unit 10v [edit interfaces] lab@srxB-1# set ge-0/0/4 unit 10v family inet address 172.20.10v.1/24 Note

VLAN tagging is used on the ge-0/0/4 interface to support the underlying lab architecture for this course. The use of a VLAN ID serves no other specific purpose in this lab.

www.juniper.net



Step 1.12 Display the interface configuration and ensure it matches the details outlined on the network diagram for this lab. When you are comfortable with the interface configuration, issue the commit-and-quit command to activate the configuration and return to operational mode.

[edit interfaces] lab@srxB-1# show ge-0/0/0 { description "MGMT Interface - DO NOT DELETE"; unit 0 { family inet { address 10.210.14.133/27; } } } ge-0/0/1 { unit 0 { family inet { address 172.20.77.1/30; } } } ge-0/0/2 { unit 0 { family inet { address 172.20.66.1/30; } } } ge-0/0/3 { unit 0 { family inet { address 172.18.1.2/30; } } } ge-0/0/4 { vlan-tagging; unit 103 { vlan-id 103; family inet { address 172.20.103.1/24; } } } lo0 { unit 0 { family inet { address 192.168.1.1/32; } } }


www.juniper.net


[edit interfaces] lab@srxB-1# commit and-quit commit complete Exiting configuration mode Step 1.13 Issue the show interfaces terse command to verify the current state of the interface you just configured.

lab@srxB-1> show interfaces terse Interface Admin Link ge-0/0/0 up up ge-0/0/0.0 up up ...TRIMMED.. ge-0/0/1 up up ge-0/0/1.0 up up ge-0/0/2 up up ge-0/0/2.0 up up ge-0/0/3 up up ge-0/0/3.0 up up ge-0/0/4 up up ge-0/0/4.103 up up ...TRIMMED.. lo0 up up lo0.0 up up ...TRIMMED..

Proto

Local

inet

10.210.14.133/27

inet

172.20.77.1/30

inet

172.20.66.1/30

inet

172.18.1.2/30

inet

172.20.103.1/24

inet

192.168.1.1

Remote

--> 0/0

Question: What is the Admin and Link state for the ge-0/0/4 interface?

Answer: The new interface should all show an Admin and Link state of up. Step 1.14 Issue the show route command to view the current route entries.

lab@srxB-1> show route inet.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 10.210.14.128/27 10.210.14.133/32 172.18.1.0/30 172.18.1.2/32 172.20.66.0/30

www.juniper.net

*[Direct/0] 15:47:37 > via ge-0/0/0.0 *[Local/0] 15:47:46 Local via ge-0/0/0.0 *[Direct/0] 00:36:20 > via ge-0/0/3.0 *[Local/0] 00:36:20 Local via ge-0/0/3.0 *[Direct/0] 00:36:20 > via ge-0/0/2.0 Configuring OSPF on Junos OS Devices • Lab 3–7


172.20.66.1/32 172.20.77.0/30 172.20.77.1/32 172.20.103.0/24 172.20.103.1/32 192.168.1.1/32

*[Local/0] 00:36:20 Local via ge-0/0/2.0 *[Direct/0] 00:36:20 > via ge-0/0/1.0 *[Local/0] 00:36:20 Local via ge-0/0/1.0 *[Direct/0] 00:02:10 > via ge-0/0/4.103 *[Local/0] 00:02:10 Local via ge-0/0/4.103 *[Direct/0] 00:36:20 > via lo0.0 Question: Does the route table display an entry for all local interface addresses and directly connected networks?

Answer: The answer should be yes. If needed, you can refer back to the network diagram and compare it with the displayed route entries. Question: What is the route preference for the Local and Direct route entries?

Answer: The Local and Direct route entries both have a route preference of 0. Step 1.15 Use the ping utility to verify reachability to the neighboring devices c onnected to your device. The following sample capture shows ping tests from srxB-1 to the Internet gateway, srxB-2-a, and vr103, which are all directly connected: Note

Use Ctrl+C to stop a continuous ping operation.

lab@srxB-1> ping 172.18.1.1 rapid count 25 PING 172.18.1.1 (172.18.1.1): 56 data bytes !!!!!!!!!!!!!!!!!!!!!!!!! --- 172.18.1.1 ping statistics --25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 3.560/5.276/26.080/4.364 ms lab@srxB-1> ping 172.20.66.2 rapid count 25 PING 172.20.66.2 (172.20.66.2): 56 data bytes !!!!!!!!!!!!!!!!!!!!!!!!! --- 172.20.66.2 ping statistics --Lab 3–8 • Configuring OSPF on Junos OS Devices

www.juniper.net


25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 4.776/6.841/29.045/4.672 ms lab@srxB-1> ping 172.20.77.2 rapid count 25 PING 172.20.77.2 (172.20.77.2): 56 data bytes !!!!!!!!!!!!!!!!!!!!!!!!! --- 172.20.77.2 ping statistics --25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 4.817/7.077/27.688/4.360 ms lab@srxB-1> ping 172.20.10v.10 rapid count 25 PING 172.20.103.10 (172.20.103.10): 56 data bytes !!!!!!!!!!!!!!!!!!!!!!!!! --- 172.20.103.10 ping statistics --25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 3.499/4.644/6.253/0.871 ms Question: Are the ping tests successful?

Answer: Yes, the ping tests should be successful at this time.

Part 2: Configuring and Monitoring Static Routing In this part, you will configure and monitor static routing. Step 2.1 Attempt to ping the loopback address of the directly attached vir tual router referenced on the network diagram for this lab. Note

Use Ctrl+C to stop a continuous ping operation.

lab@srxB-1> ping 192.168.1.2/32 ping: cannot resolve 192.168.1.2/32: Host name lookup failure Question: What does the result from the ping operation indicate?

Answer: The results from the ping operation indicate that no route to the specified host currently exists.

www.juniper.net



Step 2.2 Enter configuration mode, navigate to the [edit routing-options] hierarchy level, and add a static route to the loopback address of the directly attached virtual router.

lab@srxB-1> configure Entering configuration mode [edit] lab@srxB-1# edit routing-options [edit routing-options] lab@srxB-1# set static route 192.168.1.2/32 next-hop 172.20.10v.10 Step 2.3 Define additional static routes to allow end-to-end connectivity to the re mote subnet and loopback addresses within your assigned pod. Use the IP address assigned on the 172.20.66.0/30 subnet as the next hop for these static routes.

[edit routing-options] lab@srxB-1# set static route 192.168.2.1/32 next-hop 172.20.66.2 [edit routing-options] lab@srxB-1# set static route 192.168.2.2/32 next-hop 172.20.66.2 [edit routing-options] lab@srxB-1# set static route 172.20.104.0/24 next-hop 172.20.66.2 Step 2.4 Display the resulting configuration to review your work. Once satisfied, activate the configuration changes and return to operational mode.

[edit routing-options] lab@srxB-1# show static { route 192.168.1.2/32 next-hop 172.20.103.10; route 192.168.2.1/32 next-hop 172.20.66.2; route 192.168.2.2/32 next-hop 172.20.66.2; route 172.20.104.0/24 next-hop 172.20.66.2; } [edit routing-options] lab@srxB-1# commit and-quit commit complete Exiting configuration mode Step 2.5 Issue the show route protocol static command to view the current static routes in your device’s route table.

lab@srxB-1> show route protocol static inet.0: 15 destinations, 15 routes (15 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both


www.juniper.net


172.20.104.0/24 192.168.1.2/32 192.168.2.1/32 192.168.2.2/32

*[Static/5] 00:00:22 > to 172.20.66.2 via ge-0/0/2.0 *[Static/5] 00:00:22 > to 172.20.103.10 via ge-0/0/4.103 *[Static/5] 00:00:22 > to 172.20.66.2 via ge-0/0/2.0 *[Static/5] 00:00:22 > to 172.20.66.2 via ge-0/0/2.0 Question: How many static routes display?

Answer: Each device should show four static routes. Step 2.6 Ping the loopback address of all internal devices to verify reachability. Note

The virtual routers have a preconfigured default static route using their directly connected device as the next hop.

lab@srxB-1> ping 192.168.2.1 rapid count 25 PING 192.168.2.1 (192.168.2.1): 56 data bytes !!!!!!!!!!!!!!!!!!!!!!!!! --- 192.168.2.1 ping statistics --25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 4.714/6.018/13.400/1.758 ms lab@srxB-1> ping 192.168.1.2 rapid count 25 PING 192.168.1.2 (192.168.1.2): 56 data bytes !!!!!!!!!!!!!!!!!!!!!!!!! --- 192.168.1.2 ping statistics --25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 3.598/5.839/35.017/6.038 ms lab@srxB-1> ping 192.168.2.2 rapid count 25 PING 192.168.2.2 (192.168.2.2): 56 data bytes !!!!!!!!!!!!!!!!!!!!!!!!! --- 192.168.2.2 ping statistics --25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 4.241/5.953/27.162/4.406 ms

www.juniper.net



Question: Did the ping tests succeed?

Answer: The ping tests should succeed.

Part 3: Configuring and Monitoring OSPF In this part, you will configure and monitor OSPF. You will configure a single OSPF area based on the network diagram for this lab. Then you will per form some verification tasks to ensure that OSPF works properly. Step 3.1 Enter configuration mode and navigate to the [edit protocols ospf] hierarchy level.

lab@srxB-1> configure Entering configuration mode [edit] lab@srxB-1# edit protocols ospf [edit protocols ospf] lab@srxB-1# Step 3.2 Define OSPF Area 0 and include all internal interfaces that connect to host device and the directly connected virtual router. Ensure that you also include the lo0 interface. Issue the show command to view the resulting configuration. Note

Remember to specify the appropriate logical interface! If the logical unit is not specified, Junos OS assumes a logical unit of zero (0).

[edit protocols ospf] lab@srxB-1# set area 0 interface ge-0/0/1.0 [edit protocols ospf] lab@srxB-1# set area 0 interface ge-0/0/2.0 [edit protocols ospf] lab@srxB-1# set area 0 interface ge-0/0/4.10v [edit protocols ospf] lab@srxB-1# set area 0 interface lo0.0 [edit protocols ospf] lab@srxB-1# show area 0.0.0.0 { interface ge-0/0/1.0; Lab 3–12 • Configuring OSPF on Junos OS Devices

www.juniper.net


interface ge-0/0/2.0; interface ge-0/0/4.103; interface lo0.0; } Step 3.3 Activate the candidate configuration using the commit command. Issue the run show ospf neighbor command to verify OSPF neighbor adjacency state information. Note

The OSPF adjacency state for each neighbor is dependent on that neighbor’s configuration.

[edit protocols ospf] lab@srxB-1# commit commit complete [edit protocols ospf] lab@srxB-1# run show ospf neighbor Address Interface 172.20.77.2 ge-0/0/1.0 172.20.66.2 ge-0/0/2.0 172.20.103.10 ge-0/0/4.103

State Full Full Full

ID 192.168.2.1 192.168.2.1 192.168.1.2

Pri 128 128 128

Dead 38 32 39

Question: What state do the OSPF neighbor adjacencies show?

Answer: Although you might see some transitional states, the state for all three OSPF neighbors should eventually show Full. Step 3.4 Issue the run show route protocol ospf to view the active OSPF routes in your device’s route table.

[edit protocols ospf] lab@srxB-1# run show route protocol ospf inet.0: 16 destinations, 20 routes (16 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 172.20.104.0/24 192.168.1.2/32 192.168.2.1/32 192.168.2.2/32 www.juniper.net

[OSPF/10] 00:01:33, metric 2 to 172.20.77.2 via ge-0/0/1.0 > to 172.20.66.2 via ge-0/0/2.0 [OSPF/10] 00:02:14, metric 1 > to 172.20.103.10 via ge-0/0/4.103 [OSPF/10] 00:01:33, metric 1 to 172.20.77.2 via ge-0/0/1.0 > to 172.20.66.2 via ge-0/0/2.0 [OSPF/10] 00:01:33, metric 2 Configuring OSPF on Junos OS Devices • Lab 3–13


224.0.0.5/32

to 172.20.77.2 via ge-0/0/1.0 > to 172.20.66.2 via ge-0/0/2.0 *[OSPF/10] 00:02:24, metric 1 MultiRecv Question: Are all of the OSPF routes for the remote subnet and loopback destinations active? Why?

Answer: No, the OSPF routes for the remote subnet and loopback destinations should not be active (Note the lack of a * in front of most of the OSPF routes). We still have the static routes in place, which have a route preference of 5, making them more preferred than OSPF routes. (Internal OSPF routes use a route preference of 10, by default.) Step 3.5 Delete all static routes used for internal connectivity.

[edit protocols ospf] lab@srxB-1# top edit routing-options [edit routing-options] lab@srxB-1# show static { route 192.168.1.2/32 next-hop 172.20.103.10; route 192.168.2.1/32 next-hop 172.20.66.2; route 192.168.2.2/32 next-hop 172.20.66.2; route 172.22.104.0/24 next-hop 172.20.66.2; [edit routing-options] lab@srxB-1# delete static route 192.168.1.2/32 [edit routing-options] lab@srxB-1# delete static route 192.168.2.1/32 [edit routing-options] lab@srxB-1# delete static route 192.168.2.2/32 [edit routing-options] lab@srxB-1# delete static route 172.20.10v.0/24 [edit routing-options] lab@srxB-1# show [edit routing-options] lab@srxB-1# Step 3.6 Activate the configuration and return to operational mode. Issue the show route protocol ospf command to verify that the OSPF routes are now active.


www.juniper.net


[edit routing-options] lab@srxB-1# commit and-quit commit complete Exiting configuration mode lab@srxB-1> show route protocol ospf inet.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 172.20.104.0/24 192.168.1.2/32 192.168.2.1/32 192.168.2.2/32 224.0.0.5/32

*[OSPF/10] 00:07:13, metric 2 to 172.20.77.2 via ge-0/0/1.0 > to 172.20.66.2 via ge-0/0/2.0 *[OSPF/10] 00:07:54, metric 1 > to 172.20.103.10 via ge-0/0/4.103 *[OSPF/10] 00:07:13, metric 1 to 172.20.77.2 via ge-0/0/1.0 > to 172.20.66.2 via ge-0/0/2.0 *[OSPF/10] 00:07:13, metric 2 to 172.20.77.2 via ge-0/0/1.0 > to 172.20.66.2 via ge-0/0/2.0 *[OSPF/10] 00:08:04, metric 1 MultiRecv

lab@srxB-1> Question: Are all of the OSPF routes for the remote subnet and loopback destinations active now?

Answer: Yes, all OSPF routes should now be active. (Notice that the * is now present for all of the OSPF routes.) Step 3.7 Ping the loopback address of all internal devices to verify reachability through the OSPF routes.

lab@srxB-1> ping 192.168.1.2 rapid count 25 PING 192.168.1.2 (192.168.1.2): 56 data bytes !!!!!!!!!!!!!!!!!!!!!!!!! --- 192.168.1.2 ping statistics --25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 3.445/4.646/9.481/1.217 ms lab@srxB-1> ping 192.168.2.1 rapid count 25 PING 192.168.2.1 (192.168.2.1): 56 data bytes !!!!!!!!!!!!!!!!!!!!!!!!! --- 192.168.2.1 ping statistics --25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 4.736/5.888/11.097/1.327 ms lab@srxB-1> ping 192.168.2.2 rapid count 25 PING 192.168.2.2 (192.168.2.2): 56 data bytes www.juniper.net



!!!!!!!!!!!!!!!!!!!!!!!!! --- 192.168.2.2 ping statistics --25 packets transmitted, 25 packets received, 0% packet loss round-trip min/avg/max/stddev = 4.069/7.120/54.837/9.810 ms lab@srxB-1> Question: Do the ping tests succeed?

Answer: Yes, the ping tests should succeed, due to the OSPF routes in your device’s route table.

STOP

You have completed Lab 3. Congratulations! You have completed the lab portion of this course.


www.juniper.net

Junos Operating System Highlights Appendix A: Lab Diagrams

Junos Operating System Highlights(SSFJUN01Ia_LabGuide)

Recommend Documents