Sie sind auf Seite 1von 101
LAB MANUAL FOR JNCIA Version 1.0 CONTENTS: 1. About Juniper Routers 2. Classification of Juniper

LAB MANUAL FOR JNCIA

Version 1.0

CONTENTS:

1. About Juniper Routers

2. Classification of Juniper Routers

2.1. Difference between J, M, T, E and MX series of juniper routers

3. Juniper Router Architecture

3.1. Routing Engine

3.2. Packet Forwarding Engine

3.2.1. Switching Control Board

3.2.2. FPC

3.2.3. PIC

3.3. Routing Engine Hardware Components

3.4. Router Boot Methods

4. J-Series Router Overview

4.1. J2320 Router Front Panel and its components

4.2. Rear Panel of J2320 router

4.3. J-Series Router Configuration

4.4. PIM Modules for J-Series

4.5. PIM and VOIP Module Overview

4.5.1. Gigabit Ethernet uPIMs

4.5.2. Dual-Port Serial PIM

4.5.3. Dual-Port T1 or E1 PIM

4.6. Brief Overview of J2320, J2350, J4350, J6350 Routers

5. M-Series Router Overview

5.1. M7i Front Panel and its Components

5.2. M7i Rear Panel

5.3. Brief Overview of M7i, M10i, M40e, M120 and M320 Routers

6. JUNOS Command Line Interface

7.

Router Interfaces

7.1. Permanent Interfaces

7.2. Transient Interfaces

8. Interface Representation

8.1. On J-Series Routers

8.2. On M-Series and T-Series Routers

8.3. On MX-Series Routers

9. Routing Fundamental Labs

9.1. Lab Exercise 1 : Entering configuration mode on a router and exit

9.2. Lab Exercise 2 : Setting host name

9.3. Lab Exercise 3 : Setting routers domain name

9.4. Lab Exercise 4 : Configure the root password (Encrypted Password)

9.5. Lab Exercise 5 : Configure a DNS name server

9.6. Lab Exercise 6 : Configure a backup router

9.7. Lab Exercise 7 : Router interface address configuration

9.8. Lab Exercise 8 : Shut down an interface

9.9. Lab Exercise 9 : Set interface description

9.10. Lab Exercise 10 : Configuring encapsulation on a physical interface

9.11. Lab Exercise 11 : Configuring keepalives

9.12. Lab Exercise 12 : Set keepalive timers

9.13. Lab Exercise 13 : Configuring management ethernet interface(fxp0)

9.14. Lab Exercise 14 : Setting bandwidth on an interface

9.15. Lab Exercise 15 : Setting the hold-time value on a physical interface

9.16. Lab Exercise 16 : Setting the DTE clock rate

9.17. Lab Exercise 17 : Basic gigabit ethernet configuration on a J-series router

9.18. Lab Exercise 18 : Configuring speed on sonet interface

9.19. Lab Exercise 19 : Show chassis commands on J and M series routers

9.20. Objective Test 1

10. Static Routing Labs

10.1. Lab Exercise 1 : Configuring static routes

10.2. Lab Exercise 2 : Ping Test

10.3. Lab Exercise 3 : Telnet

10.4. Lab Exercise 4 : Traceroute

10.5. Objective Test 2

11. Policies Configuration Labs

11.1. Lab Exercise 1 : Routing policy lab 1

11.2. Lab Exercise 2 : Routing policy lab 2

11.3. Objective Test 3

12.

RIP Configuration Labs

12.1. Lab Exercise 1 : RIP configuration

12.2. Objective Test 4

13. Dynamic Routing Labs

13.1. Lab Exercise 1 : Ping test by configuring RIP

13.2. Lab Exercise 2 : Ping test by configuring OSPF with multiple areas

14. Show Commands Labs

14.1. Lab Exercise 1 : Show commands lab

15. OSPF Labs

15.1. Lab Exercise 1 : OSPF configuration

15.2. Lab Exercise 2 : OSPF configuration and verification

15.3. Objective Test 5

16. Juniper Switch Models

17. EX Series Switches Overview

17.1. EX2200 Switch

17.1.1. EX2200 Front Panel

17.1.2. Chassis LEDs

17.1.3. EX2200 Rear Panel

17.2. EX2500 Switch

17.3. EX3200 Switch

17.4. EX4200 Switch

17.5. EX4500 Switch

17.6. EX8200 Switch

18. QFX Series Switch - QFX3500 Switch Overview

19. QFX Series Switch - QFX3500 Switch Overview

20. Basic Switch Labs

20.1. Lab Exercise 1 : Entering configuration mode on a switch and exit

20.2. Lab Exercise 2 : Setting Hostname

20.3. Lab Exercise 3 : Set interface description

20.4. Lab Exercise 4 : Shutdown an interface

20.5. Lab Exercise 5 : Basic CLI commands

20.6. Lab Exercise 6 : Configure bandwidth on an interface

20.7. Lab Exercise 7 : Configuring ether-options on the gigabit ethernet switch

interface

20.8. Lab Exercise 8 : Configuring the management IP address on EX series switch

21. Lab Exercises on VLAN

21.1. Lab Exercise 1 : Define VLANs

21.2. Lab Exercise 2 : Configure a port for membership in that VLAN

21.3. Lab Exercise 3 : Configuring an interface as a trunk port

21.4. Lab Exercise 4 : Configuring VLANs on EX series switch

21.5. Lab Exercise 5 : Configuring Routed VLAN interface (Inter-VLAN routing) on

a switch

21.6. Objective Test 6

22. Lab Exercises on Spanning tree protocol and VSTP

22.1. Lab Exercise 1 : Configuring STP Timers

22.2. Lab Exercise 2 : Setting bridge priority on switch

22.3. Lab Exercise 3 : Configuring port priority

22.4. Lab Exercise 4 : Verifying STP

22.5. Lab Exercise 5 : Enabling VSTP on all VLANs

22.6. Lab Exercise 6 : Enabling VSTP on a VLAN using a single VLAN-ID / VLAN-

Name

22.7. Objective Test 7

23. Lab Exercises on PoE

23.1. Lab Exercise 1 : Configuring guard-band and maximum power on PoE enabled

interface

23.2. Lab Exercise 2 : Configuring power management mode on PoE enabled

interface

23.3. Lab Exercise 3 : Disabling a PoE interface

23.4. Lab Exercise 4 : Setting power priority on all PoE enabled interfaces

24. Final Exam

24.1. Objective Test Final Exam

25. Appendix

25.1. Answer keys for objective test 1

25.2. Answer keys for objective test 2

25.3. Answer keys for objective test 3

25.4. Answer keys for objective test 4

25.5. Answer keys for objective test 5

25.6. Answer keys for objective test 6

25.7. Answer keys for objective test 7

25.8. Answer keys for objective test final exam

1.

About Juniper Routers

Main products offered by Juniper include T-Series, M-Series, E-Series, MX-Series, J-Series routers, EX-Series Ethernet switches and SRX-Series Security products. JUNOS is the operating system that runs on most of the juniper's networking equipment.

2. Classification of Juniper Routers:

The routers are classified in to M-series, J-series, T-series, E-series, and MX-series based on the functionality. Some frequently used models are given below:

M-Series: M7i, M10i, M40e, M120, M320 J-Series: J2320, J2350, J4350, J6350 T-Series: T320, T640, T1600, TX Matrix, TX Matrix Plus E-Series: E120, E320, ERX310, ERX705, ERX710, ERX1410, ERX1440 MX-Series: MX80, MX240, MX480, MX960

2.1 Differences between different series of juniper routers are

1. Juniper J-Series routers are a series of enterprise routers called as modular

routers for enterprises running desktops, servers, VoIP etc applications and

these kind of routers are typically deployed at remote offices or branch locations.

2. Juniper M-Series routers are called Multiservice Edge routers designed for

enterprise and service provider networks.

3. Juniper T-Series routers are a series of core routers designed for high-end

and core networks with throughput from 320 Gbit/s to 25.6 Tbit/s with a max

forwarding rate of 30.7 billion pps.

4. Juniper E-Series routers are a series of broadband services routers or edge

routers which provides multiple services including broadband remote access

server, broadband video services, security services, NAT etc on a single platform.

5. Juniper MX-Series routers are a family of high-performance Ethernet

Services routers with powerful switching features and are designed for high- performance service providers and enterprises.

Note: However, please note that we will be discussing only the J-series and some M-series routers in this manual. Other products are beyond the scope of this manual.

3. Juniper Routers Architecture

The central principle of the Juniper Networks platform centers on a separation of the control and forwarding planes within the router. These are Routing Engine and Packet Forwarding Engine as shown below.

Routing Engine and Packet Forwarding Engine as shown below. 3.1. Routing Engine The Routing Engine is

3.1. Routing Engine

The Routing Engine is the central location for control of the system in a juniper networks router and it consists of an Intel-based PCI platform running JUNOS software. The Routing Engine constructs and maintains one or more routing tables. From the routing tables, the Routing Engine derives a table of active routes, called the forwarding table, which is then copied into the Packet Forwarding Engine.

Functions of the routing engine include the following

Handling of routing protocol packets

Management Interface

Configuration Management

Accounting and alarms

Modular Software

Scalability

3.2. Packet Forwarding Engine

The Packet Forwarding Engine is the central location for data packet forwarding through the router. The main portions of the Packet Forwarding Engine are the following:

Switching control board.

Flexible PIC Concentrator, and

Physical Interface Card

3.2.1 Switching Control Board

The switching control board contains a PowerPC CPU and 64MB of RAM that

operates the components of the circuit board itself, but doesn't participate in packet forwarding. The Internet Processor ASIC is located on the control board and accesses the forwarding table for route lookups.

3.2.2. Flexible PIC Concentrator (FPC)

The Flexible PIC Concentrators on a router house the PICs which connect the router to network media and its main function is to connect the PICs installed in it to the other router components.

The Flexible PIC Concentrator (FPC) connects to both the switching control board and the router's interfaces within the Packet Forwarding Engine.

3.2.3. Physical Interface Card (PIC)

PIC is an interface card through which network cables carry data transmissions to and from the network plug. A PIC installs into a FPC.

3.3. Routing Engine Hardware Components

The Routing Engine consists of various components like Processor, DRAM, EPROM, Crypto Accelerator Module, Compact Flash.

i. Processor

The processor runs JUNOS software to maintain the router's routing tables and routing protocols and creates the packet forwarding switch fabric for the router.

ii. DRAM

DRAM buffers incoming packets and provides storage for the routing and forwarding tables and for other Routing Engine processes

iii. EPROM

EPROM stores the serial number of the Routing Engine.

iv. Crypto Accelerator Module

Crypto Accelerator Module is a processor card that enhances performance of cryptographic algorithms used in IP security (IPSec) services.

The cryptographic algorithms supported include Advanced Encryption Standard (AES), Data Encryption Standard (DES), triple DES (3DES), Hashed Message Authentication Code-Message Digest 5 (HMAC-MD5), and HMAC-Secure Hash Algorithm 1 (SHA-1).

v. Compact Flash

Compact Flash component provides primary storage for software images, configuration files, and microcode. J-series routers have a primary or internal compact flash located on the system board.

3.4. Router Boot Methods

J2320 and J2350 router can boot from the following given three devices.

i. Internal Compact Flash

ii. External Compact Flash

iii. USB Storage Device

J4350 and J6350 can boot from two devices namely

i. Compact Flash disk

ii. USB Storage Device

4. J-Series Router Overview

J Series Services Routers running JUNOS Software provide stable, reliable, and efficient IP routing, WAN and LAN connectivity, and management services for small to medium-sized enterprise networks. The J-series juniper router runs Junos with MPLS, IP4/6, QOS, multicast, firewall and IPsec VPN.

J-series Services Routers support network interfaces for E1, E3, T1, T3, Fast Ethernet, serial, Point-to- Point Protocol over Ethernet (PPPoE), and ISDN media.

Slot numbering for J2320 router

(PPPoE), and ISDN media. Slot numbering for J2320 router Slot numbering for J2350 router Version 1.0

Slot numbering for J2350 router

Slot numbering for J2320 router Slot numbering for J2350 router Version 1.0 Copyright © 2002 -

4.1. J2320 Router Front Panel and its Components

The front panel of the J2320 router is as shown below

The front panel of the J2320 router is as shown below The cross section as indicated

The cross section as indicated by AA is provided in an enlarged scale below:

The components are explained below: Physical Interface Module (PIM) PIMs provide the physical connection to

The components are explained below:

Physical Interface Module (PIM)

PIMs provide the physical connection to various network media types. The PIM receives incoming packets from the network and transmits outgoing packets to the network.

Power Button and Power LED

The power button can be used to power the service router on and off. The power LED located at the upper left of the LED dashboard is green color when on and it can be in two states. i. On steadily state which means power is functioning correctly ii. Blinking state which means power button has been pressed and quickly released and the router is shutting down.

Status LED

Status LED changes from off to blinking green when the system is powered on. It can be in the following states

Color

State

Description

Green

Blinking

Router is starting up or performing diagnostics

On steadily

Router is operating normal

Red

Blinking

Error has been detected

Alarm LED

The alarm LED lights can be either yellow or red. If yellow, indicates a minor condition that requires monitoring or maintenance. If red, indicates major condition that can result in a system shutdown.

HA LED

The High availability (HA) LED lights when the router starts but otherwise remains unlit and this is mostly for future use.

Reset Config Button

This button is used to return the router to either the rescue configuration or the factory default configuration.

Console Port

Through the console port, a RJ-45 serial cable can be used to connect to the routing engine and the router can be configured using CLI from the chassis console port.

USB Port

The USB ports on the front panel of the router accept a USB storage device or USB storage device adapter with a compact flash installed and can act as a secondary boot device if the internal compact flash fails on startup.

ESD Point

The electrostatic discharge point located at the front of the chassis minimizes the risk of electrical discharge in potentially hazardous environments.

4.2. Rear Panel of J2320 router

4.2. Rear Panel of J2320 router 4.3. J-Series Router Configuration There are two user interfaces to

4.3. J-Series Router Configuration

There are two user interfaces to monitor, configure, troubleshoot and manage a service router. They are JUNOS CLI and J-web Interface.

5.3.1 JUNOS Command Line Interface

JUNOS CLI is a Juniper Networks Command Shell that runs on top of a UNIX- Based OS Kernel. The CLI provides command help and command completion and commands are executed when Enter key is pressed.

The CLI has two modes Operational mode and Configuration mode. The CLI commands are organized hierarchically with commands that perform a similar function grouped together under the same level.

Steps for starting the CLI

1. Establish a connection with the services router 2. Log in using username and password. After log in, enter a UNIX shell 3. Start the CLI

%cli

user@host>

The prompt ">" indicates that the CLI has started.

5.3.2. J-Web Interface

J-Web is a web-based GUI that allows operating a router without commands. It allows to monitor, configure, troubleshoot, and manage the router on a client by means of a web browser with HTTP (Hyper Test Transfer Protocol) or HTTPS (HTTP over Secure Sockets Layer) enabled. Quick configuration wizards simplify basic configuration and minimizes the risk of error.

4.4. PIM Modules for J-Series

PIMs supported for J-Series are categorized into uPIM, ePIM.

5.4.1 PIM

PIM (Physical Interface Module) is a network interface card that is installed on a J-series Services Router, to provide physical connections to a LAN or a WAN

5.4.2 uPIM (Universal Switching PIM)

uPIM is a particular type of PIM, such as the Gigabit Ethernet uPIM, which can be universally inserted in any slot on a J2320, J2350, J4350, or J6350 Services Router.

The difference is ePIM slots has PCI and PCI-X bus connection whereas PIM slots only has PCI bus connection. A uPIM either uses the PCI or the PCI-X bus depending on what slot the uPIM is installed in. Naturally better performance is expected with ePIM slots.

5.4.3 ePIM (Enhanced PIM)

ePIM is a particular type of high-speed PIM, such as the Gigabit Ethernet ePIM or 4-port Fast Ethernet ePIM, which can be inserted only in high-speed slots (slots 3 and 6 on a J4350 Services Router, or slots 2, 3, 5, and 6 on a J6350 Services Router).

4.5. PIM and VoIP Module Overview

J-Series routers accept PIMs and Avaya VoIP modules in the slots on the front of the chassis.

Some of the supported PIMs include the following and are explained below

1-Port, 6-Port, 8-Port and 16-Port Gigabit Ethernet uPIMs

Dual-Port Serial PIM

Dual-Port T1 or E1 PIM

Avaya VoIP modules are controlled by the Avaya Communication Manager (CM) software

rather than the JUNOS software and are installed in the router chassis like PIMs.

5.5.1. Gigabit Ethernet uPIMs

Gigabit Ethernet uPIMs are available in four versions i.e, 1-Port, 4-Port, 8-Port, 16-Port and are supported on J2320, J2350, J4350 and J6350 service routers.

1-Port Gigabit Ethernet uPIM

These have small form-factor pluggable (SFP) transceivers which allows different connectors. SFP is as shown in the figure below

different connectors. SFP is as shown in the figure below A 1-port Gigabit Ethernet uPIM is

A 1-port Gigabit Ethernet uPIM is as shown

the figure below A 1-port Gigabit Ethernet uPIM is as shown Gigabit Ethernet uPIM can be

Gigabit Ethernet uPIM can be inserted in any slot on J2320, J2350, J4350 and J6350 service routers. High-speed slots are slots 3 and 6 on the J4350 router, and slots 2, 3, 5, and 6 on the J6350 router.

Gigabit Ethernet uPIMs features are

The multiport uPIMs can be used as switches in the access layer

Link speed for 8-port and 16-port Gigabit Ethernet uPIMs is

configurable to 10, 100, or 1000 Mbps, and transmission mode is configurable to half or full duplex. The 1-port and 6-port SFP Gigabit Ethernet uPIMs cannot be manually configured-they are set at 1000 Mbps and full duplex.

1-port and 6-port Gigabit Ethernet uPIMs use SFP transceivers to allow different connectors to be used on uPIM ports. These SFP Gigabit Ethernet uPIMs support 1000Base-SX, 1000Base-LX, and 1000Base-T SFPs. They do not support 1000Base-LH SFPs.

8-port and 16-port Gigabit Ethernet uPIMs-and SFPs on the 1-port and 6-port uPIMs-support 1000Base-T RJ-45 connectors. The limitations are that Gigabit Ethernet uPIMs do not support SNMP and the interfaces can be configured up to a max MTU size of 9014 bytes.

5.5.2.

Dual-Port Serial PIM

The Dual-Port Serial PIM provides a physical connection to serial network media types through two serial interface ports.

network media types through two serial interface ports. The key features of dual-port serial PIM are

The key features of dual-port serial PIM are

Onboard network processor

Auto selection of operation modes based on data terminal equipment (DTE) or data communication equipment (DCE) cables

Local and remote loopback diagnostics

Configurable clock rate for the transmit (Tx) clock and receive (Rx) clock

5.5.3.

Dual-Port T1 or E1 PIM

The Dual-Port T1 PIM and Dual-Port E1 PIM provide a physical connection to T1 or E1 network media types. Each PIM has two physical T1 or E1 ports with an integrated channel service unit (CSU) or data service unit (DSU).

Dual-port T1 PIM is shown below

Dual-port E1 PIM is shown below Their key features include • Onboard network processor •

Dual-port E1 PIM is shown below

Their key features include

Onboard network processor

Integrated CSU/DSU-Eliminates the need for a separate external device

56-Kbps and 64-Kbps modes

ANSI T1.102, T1.107, and T1.403 standards compliance

G.703, G.704, and G.706 E1 standards compliance

Independent internal and external clocking system

Loopback, bit error rate test (BERT), T1 facilities data link (FDL), and long buildout diagnostics

4.6. Brief Overview of J2320, J2350, J4350, J6350 Routers

1. J2320

The J2320 Services Router is primarily designed for remote and branch offices. The J2320 routers are entry level service routers which gives up to 600 Mbps throughput performance, has four built-in Gigabit Ethernet ports. It has three PIM slots for additional LAN/WAN connectivity, Avaya VoIP Gateway, and WAN acceleration. They are used for one or two broadband, T1, or E1 interfaces with integrated services.

Fixed Interfaces: 4 Gigabit Ethernet ports No of pim slots: 3

2. J2350

The J2350 Services Router is primarily designed for branch offices. The J2350 router which has 4built-in Gigabit Ethernet ports gives up to 700 Mbps performance. It gives five PIM slots. They are usually used for multiple broadband, T1, or E1 interfaces with multiple integrated services

Fixed Interfaces: 4 Gigabit Ethernet ports No of pim slots: 5

3. J4350

The J4350 Services Router is designed primarily for regional and branch offices. The J4350 enterprise router gives up to 1Gbps in performance. They are usually used for DS3, E3, and Metro Ethernet interfaces with integrated services. It has six PIM slots. Two of these slots are enhanced-performance slots that provide additional performance to multiple Gigabit Ethernet configurations.

performance to multiple Gigabit Ethernet configurations. Fixed Interfaces: 4 Gigabit Ethernet ports No of pim slots:

Fixed Interfaces: 4 Gigabit Ethernet ports No of pim slots: 6

4. J6350

The J6350 Services Router is designed primarily for regional and central offices. The J6350 gives up to 2 Gbps in performance. It has six PIM slots for additional LAN/WAN connectivity, Avaya VoIP Gateway, and WAN acceleration. These routers have optional redundant power supplies for high system availability. The J6350 Services Router is a higher-performance system than the J4350 Services Router.

a higher-performance system than the J4350 Services Router. Fixed Interfaces: 4 Gigabit Ethernet ports No of

Fixed Interfaces: 4 Gigabit Ethernet ports No of pim slots: 6

5. M-Series Routers Overview

The Juniper Networks M Series is a family of high-performance, multiservice edge routers, with advanced routing features that delivers exceptional flexibility and reliability over a wide range of connectivity options without compromise.

Designed for high-performance service providers and enterprises, the M7i, M10i, M120, and M320 can be deployed in the small and medium core, multiservice edge, collapsed POP routing, peering, route reflector, campus or WAN gateway applications. Speeds range from DS0 up to OC192/STM-64 and 10 GbE.

Advanced routing features supported include MPLS, multicast, QoS, and high availability. Services

supported include a broad array of VPNs, network-based security, real-time voice and video, bandwidth on demand, rich multicast of premium content, IPv6 services, granular accounting and much more.

5.1 M7i Front Panel and its Components

and much more. 5.1 M7i Front Panel and its Components The components are explained below PIC

The components are explained below

PIC

A PIC (Physical Interface Card) is an interface card through which network cables carry

data transmissions to and from the network plug. A PIC installs into a FPC (Flexible PIC Concentrator). M7i router accommodates four PICs.

FIC

In addition to four PICs, M7i router includes a built-in FIC (Fixed Interface Card) that

provides two fast Ethernet ports or one gigabit Ethernet port depending on which FIC was ordered. FPC 0 holds PIC slots (0 to 3) and FPC 1 holds fixed interfaces (Two Fast

Ethernet or One Gigabit Ethernet).

FIC Receives incoming packets and transmits outgoing packets to the network, displays alarm status, and takes PICs online and offline.

ESD Point

The ESD Point (Electrostatic discharge point) located at the front of the chassis minimizes the risk of electrical discharge in potentially hazardous environments.

Routing Engine

Routing Engine maintains the routing tables, manages the routing protocols, controls the interfaces, controls some chassis components, and provides the interface for system management and user access.

5.2 M7i Rear Panel

for system management and user access. 5.2 M7i Rear Panel Some of the components are explained

Some of the components are explained below

CFEB

CFEB (Compact Forwarding Engine Board) provides route lookup, management of shared memory, transfer of outgoing data packets, and transfer of exception and control packets; includes built-in tunnel interface and optional Adaptive Services PIC.

Power Supplies

Power Supplies distributes needed voltages to components.

5.3 Brief overview of M7i, M10i, M40e, M120 and M320 Routers

1. M7i

The M7i Multiservice Edge Router is 3.5 inches (8.9 cm) in height and supports 7+ Gbps throughput. The M7i is ideal as an IP/MPLS provider edge router in small PoPs or as an enterprise routing solution for Internet gateway or branch aggregation.

The M7i router supports various PICs, including ATM, channelized, Ethernet, IP services, and SONET/SDH interfaces.

The router accommodates up to four Physical Interface Cards (PICs). In addition to the PICs, the Fixed Interface Card (FIC) provides two Fast Ethernet ports or one Gigabit Ethernet port, depending on your configuration.

PICs are interchangeable between the M7i and M10i routers.

2. M10i

The M10i Multiservice Edge Router is cost-effective fully redundant M Series edge router, combined with Junos OS reliability features, the M10i router is the product of choice for enabling reliable and secure services in small and medium PoPs.

The router supports up to eight PICs, including ATM, Channelized, Gigabit Ethernet, IP Services, and SONET/SDH interfaces

The M10i router supports up to eight Physical Interface Cards (PICs). PICs are interchangeable between the M7i and M10i routers.

3. M40e

The M40e Multiservice Edge Router provides a dense, highly redundant platform primarily targeted for dense dedicated access aggregation and provider edge services in medium and large PoPs.

PICs are available in supported media types, including Asynchronous Transfer Mode (ATM), Channelized DS3, E1, E3, T1, Ethernet, SONET/SDH, and IP services.

The router accommodates up to eight Flexible PIC Concentrators (FPCs) (FPC 0 to FPC 7), which can each be configured with a variety of network media types, altogether providing up to 32 OC12/STM4, 32 Gigabit Ethernet, or eight OC48/STM16 ports per system. FPCs supported by M40e router are FPC, Enhanced Plus FPC1, Enhanced Plus FPC2

PICs are compatible with the M120 and Juniper Networks T320 and T640 Core Routers.

4. M120

M120 router is the newest addition to M-Series, capable of supporting MPLS services at Layers 2 and 3, including Layer 3 VPNs, the M120 is designed to deliver superior redundancy and facilitate the transport of legacy Frame Relay and ATM traffic over high-bandwidth Ethernet links.

The router supports various PICs, including ATM, Channelized, Gigabit Ethernet, IP services, and SONET/SDH interfaces.

The M120 delivers support for 128 GE subscriber ports, with 10 GB Ethernet or OC 192 uplink capability in an affordable, compact form factor

The router is a quarter-rack chassis that supports up to six FPCs. Four slots accept FPCs of Types 1, 2, and 3 and two slots accept Compact FPCs (CFPCs). Each FPC can be configured with a variety of network media types, altogether providing up to 130 physical interface ports per system. The CFPC slots are identical to the Type 1, 2, and 3 FPC slots, but feature a smaller form factor to provide higher density 10-Gigabit interfaces.

FPCs supported by M120 router are FPC1, FPC2 and FPC3. PICs are compatible with M40e, T320, and T640 routers.

5. M320

The M320 Multiservice Edge Router is a high performance, 10 Gbps-capable, distributed architecture edge router ideal for medium-size backbone cores requiring predictable performance for feature-rich infrastructures.

The router supports up to eight FPCs providing SONET/SDH OC-48/STM16, SONET/SDH OC192/STM64, and 160-Gigabit Ethernet media.

The router is a half-rack chassis that supports up to eight Flexible PIC Concentrators (FPCs) providing up to 64 SONET/SDH OC48/STM16, 16 SONET/SDH OC192/STM64, or 160 Gigabit Ethernet ports for the router.

FPCs supported by M320 router are Enhanced II FPC 1, Enhanced III FPC 1, Enhanced II FPC 2, Enhanced II FPC 3, Enhanced III FPC 2, Enhanced III FPC 3. PICs are compatible with M40e, M120, T320, and T640 routers

6. JUNOS Command Line Interface

The operating system software that powers the Juniper routers is called JUNOS. The software is modular and standards based. Another important feature of JUNOS is that the software is platform independent (within Juniper hardware systems, not to be confused with other vendor hardware), thus delivering the same scalability and security across several hardware platforms.

JUNOS CLI is a simple to use, text-based command interface. We give various commands on CLI for

configuring, troubleshooting and monitoring the software.

JUNOS primarily supports two types of command modes.

a) Operational Mode

b) Configuration Mode

a) Operational Mode:

When we log in to the router and the CLI starts, we are at the top level of the CLI operational mode. In this mode, we enter the commands for

1. Controlling the CLI environment, and

2. Monitor and troubleshoot network connectivity, and

3. Initiating the Configuration Mode.

Frequently used commands in this mode include ping, show, traceroute, configure, etc.

b) Configuration Mode:

We use the Configuration mode for configuring the JUNOS software by creating a hierarchy of configuration statements. We enter the configuration mo9+de by using the command "configure" as shown below:

user@host>configure Entering configuration mode [edit] user@host#

Issuing the commands one at a time using CLI can configure a JUNOS™ router or alternately, we can configure by creating a text (ASCII) file that contains the statement hierarchy. Remember to activate the configuration by using the command "commit" on the router.

As shown in the above example, the generic configuration prompt is user@host#. Ofcourse, we can change the prompt by using appropriate command.

Statement Hierarchy:

We use the above configuration mode commands to create a statement hierarchy, and then configure the JUNOS software. The term "statement hierarchy" is used to define the sequence of commands used for configuring a particular feature (or features) of the router. An example statement hierarchy is given below:

user@host>configure Entering configuration mode [edit] ----Top level user@host#edit protocols ospf [edit protocols ospf] ----protocols ospf hierarchy level user@host#

"set" commands are used to configure specific leaf statements.

Ex: user@host#set hello-interval 14

7. Router Interfaces

Juniper Networks platform has primarily two types of interface. These are:

Permanent interfaces, these are always present in the router and Transient interfaces, these can be inserted or removed from the router by user.

7.1. Permanent Interfaces:

Each router has two permanent interfaces. These are:

a. Management Ethernet interface: This interface enables us to access the router using ssh, and telnet. The interface uses out-of-band connectivity, and does not provide packet forwarding capabilities for the transit data packets.

b. Internal Ethernet interface: Connects the Routing Engine (running the JUNOS Internet software) to the Packet Forwarding Engine. The router uses this interface as the main communications link between the JUNOS software and the components of the Packet Forwarding Engine. The Internal Ethernet interface is configured automatically when the JUNOS software boots.

7.2. Transient Interfaces:

Transient Interfaces are the interfaces that receive user's data packets from the network and transmit the packets to the network. These interfaces are physically located on a Physical Interface Card. They can be inserted and removed at any time.

These interface need to be configured before using it. We can also configure the interfaces that are not in the chassis. When the JUNOS software activates the router's configuration it finds out the interfaces that are present and activates only those interfaces.

In addition, each router has two serial ports, labeled console and auxiliary. Console port can be used to connect tty-type terminals to the router. The auxiliary port can connect to a modem.

8. Interface Representation

8.1. On J-Series routers

On the J-series routing platform, when information about an interface is displayed, the interface type, the slot in which the Physical Interface Module (PIM) is installed, 0, and the configured port number is specified.

In the physical part of the interface name, a hyphen (-) separates the media type from the PIM number, and a slash (/) separates the PIM, 0, and port numbers. And the syntax is:

type-pim/0/port

Each of the terms are explained below:

type: is the one that uniquely identifies the type of physical interface. It is a two-character word and can be one of the following:

ae-Aggregated Ethernet interface at-ATM interface e1-E1 interface (including channelized STM-1 interfaces) e3-E3 interface fe-Fast Ethernet interface fxp-Management and internal Ethernet interfaces ge-Gigabit Ethernet interface gr-Generic Route Encapsulation tunnel interface ip-IP-over-IP encapsulation tunnel interface lo-Loopback interface ml-Multilink interface so-SONET/SDH interface t1-T1 interface (including channelized DS-3 and OC-3 interfaces) t3-T3 interface (including channelized OC-12 interfaces se-Serial interface

pim: Physical Interface Module (PIM) provides the physical connection to various network media types. It is the slot in which the PIM is installed. 0: it is the pim module number port: it is the port number to be configured

For example, on a J-series router J2320, assuming that slot 1 is populated with single port gigabit ethernet card, the interface is uniquely identified as below:

ge-1/0/0

8.2. On M-Series routers and T-Series routers

Using JUNOS™ software, a typical interface configuration will have the following syntax:

type-fpc/pic/port

Each of the terms are explained below:

type: is the one that uniquely identifies the type of physical interface. It is a two-character word as stated above. fpc: is the physical slot number in the chassis where the interface is located. pic: is the slot number on the FPC where the interface is located. port: is the location on the PIC where the interface port (to which the interface is

connected) is located.

For example, M7i router will have one fixed FPC (FPC1) that contains internal ports, and FPC 0 for external PIC cards. Assuming that FPC0, PIC1 is populated with dual port fast ethernet card, the ports are uniquely addressed as below:

fe-0/1/0 for the first fast ethernet port, and fe-0/1/1 for the second fast ethernet port.

Note:Some physical interfaces use channel numbers instead if unit numbers. These numbers are represented using colon instead of period like media_type-fpc/pic/port:channel Number

8.3. On MX-Series routers

On the MX-series routers when information about an interface is displayed, the interface type, the slot in which the Dense Port Concentrator (DPC) is installed, the slot on the DPC in which the Physical Interface Card (PIC) is located, and the configured port number are specified.

In the physical part of the interface name, a hyphen (-) separates the media type from the DPC number, and a slash (/) separates the DPC, PIC, and port numbers. And the syntax is:

type-dpc/pic/port

type: is the one that uniquely identifies the type of physical interface. It is a two-character word as stated above. dpc: is the slot number in which the Dense Port Concentrator (dpc) is installed pic: is the slot number on the dpc port: it is the port number to be configured

9. ROUTING FUNDAMENTAL LABS

The following labs can be performed using CertExams.com Juniper network simulator. The software may be downloaded from the Juniper Junos Simulator product page. Further, please note that the Demo version will support limited commands. All labs are supported only in the full version of the software.

9.1 : Lab Exercise 1 : Entering configuration mode on a Router, and exit

Description: A basic exercise, that shows how to enter configuration mode, and exit from the same. Choose R1 from the network diagram, and exit.

Instructions:

1. Enter into configuration mode 2. Get back to the operational mode

user@R1>configure

[edit]

user@R1#exit

user@R1>

 

Back

9.2

:Lab Exercise 2 : Setting Host Name

Description:Set the router host name. Go to N/W diagram and choose device R1.

 

Instructions:

1. Enter into configuration mode

2. Set hostname as juniper1

user@R1>configure

[edit] user@R1#edit system [edit system] user@R1#set host-name juniper1 [edit system]

user@juniper1#exit

[edit]

user@juniper1#exit

 

Back

9.3

: Lab Exercise 3 : Setting Routers Domain Name

Description:Set the router domain name. Go to N/W diagram and choose device R1.

 

Instructions:

1. Enter into configuration mode

2. Set domain name as mydomain.net.

user@R1>configure

[edit] user@R1#edit system [edit system] user@R1#set domain-name mydomain.net [edit system]

user@R1#exit

[edit]

 

user@R1#

 

Back

9.4 : Lab Exercise 4 : Configure the Root Password (Encrypted

Password)

Description: This lab demonstrates configuring encrypted password on the router.

Instructions:

1. Enter into configuration mode

2. Move to the root-authentication hierarchy

3. Set the encrypted password as 24adr3e

user@R1>configure

[edit] user@R1#edit system root-authentication [edit system root-authentication] user@R1#set encrypted-password 24adr3e [edit system root-authentication]

user@R1#exit

[edit]

user@R1#

 

Back

9.5

: Lab Exercise 5 : Configure a DNS Name Server

Description:For the Router to resolve hostnames into addresses, one or more DNS name servers have to be configured.

 

Instructions:

1. Enter into configuration mode

2. Set the DNS name server as 196.20.32.15

user@R1>configure

[edit] user@R1#edit system [edit system] user@R1#set name-server 196.20.32.15 [edit system]

user@R1#exit

[edit]

 

user@R1#

 

Back

9.6 : Lab Exercise 6 : Configure a Backup Router

Description: This exercise demonstrates configuring a backup router.

Instructions:

1. Enter into configuration mode

2. Configure the backup router with an address of 196.20.32.15/24

user@R1>configure

[edit] user@R1#edit system [edit system] user@R1#set backup-router 196.20.32.15/24 [edit system]

user@R1#exit

[edit]

user@R1#

 

Back

9.7 : Lab Exercise 7 : Router Interface Address Configuration

Description: In this lab, you configure so-0/0/1 interface under unit 0 and family inet on a router with specified ip address and subnet mask. Choose R1 in the network diagram and exit.

Instructions:

1. Enter into configuration mode

2. Set ip address of so-0/0/1 as 196.20.32.15 and subnet mask as 24

3. Issue show interfaces command to verify the configuration

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/1 [edit interfaces so-0/0/1] user@R1#edit unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R1#set address 196.20.32.15/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R1#exit

[edit interfaces so-0/0/1]

user@R1#exit

[edit]

user@R1#commit

commit complete [edit]

user@R1#exit

user@R1>show interfaces so-0/0/1

 

Back

9.8 : Lab Exercise 8 : Shut down an Interface

Description: By default, an interface will be in up state. We need to issue disable command to bring-down the interface.

Instructions:

1. View the information about interface serial 0

2. Bring serial 0 to no shutdown state

3. Now view the state of the interface serial 0

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R1#set disable [edit interfaces so-0/0/0]

user@R1#exit

[edit]

user@R1#

 

Back

9.9

: Lab Exercise 9 : Set Interface Description

Description: In this exercise, description to an interface is set by using set description command.

 

Instructions:

1. Enter into configuration mode.

2. Set the description of interface so-0/0/0 as "interface-so-0/0/0" .

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R1#set description "interface-so-0/0/0" [edit interfaces so-0/0/0]

user@R1#exit

[edit]

 

user@R1#

 

Back

9.10 : Lab Exercise 10 : Configuring the Encapsulation on a Physical Interface

Description: The following lab configures the PPP encapsulation on the physical interface

so-0/0/0

Instructions:

1. Enter into configuration mode.

2. Set the encapsulation of interface so-0/0/0 as ppp.

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R1#set encapsulation ppp [edit interfaces so-0/0/0]

user@R1#exit

[edit]

user@R1#

Back

9.11 : Lab Exercise 11 : Configuring Keepalives

Description: By default, physical interfaces configured with Cisco HDLC or PPP encapsulation send keepalive packets at 10-second intervals, use this lab to disable the sending of keepalives and then enable it back on interface so-0/0/0.

Instructions:

1. Enter into configuration mode.

2.Disable the sending of keepalives on so-0/0/0.

3. Enable the sending of keepalives on so-0/0/0 with an interval of 40 seconds, down-count

as 30 and up-count as 20 seconds.

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R1#set no-keepalives [edit interfaces so-0/0/0] user@R1#set keepalives 40 30 20 [edit interfaces so-0/0/0]

user@R1#exit

[edit]

user@R1#

Back

9.12 : Lab Exercise 12 : Set Keepalive Timers

Description: This exercise demonstrates setting keepalive timers on the router.

Instructions:

1. Enter into configuration mode.

2. Set keepalive interval as 1000, down count as 12 and up count as 12 of interface so-

0/0/0.

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R1#set keepalives 1000 12 12 [edit interfaces so-0/0/0]

user@R1#exit

[edit]

user@R1#

Back

9.13 : Lab Exercise 13 : Configuring the Management Ethernet interface

(fxp0)

Description: By default, the management Ethernet interface (fxp0) autonegotiates whether to operate at 10 megabits per second (Mbps) or 100 Mbps. All other interfaces automatically choose the correct speed based on the PIC type and whether the PIC is configured to operate in multiplexed mode. This lab is used to configure the management Ethernet interface speed.This statement applies only to the management Ethernet interface (fxp0) and to the Fast Ethernet 12-port and 48-port PICs.

Instructions:

1. Enter into configuration mode

2. Set the management Ethernet interface (fxp0) speed to 10 Mbps

user@R1>configure

[edit] user@R1#edit interfaces fxp0 [edit interfaces fxp0] user@R1#set speed 10m [edit interfaces fxp0]

user@R1#exit

[edit]

user@R1#

Back

9.14 : Lab Exercise 14 : Setting Bandwidth on an interface

Description: This exercise demonstrates setting bandwidth on an interface.

Instructions:

1. Enter into configuration mode

2. Set bandwidth of so-0/0/0 unit 0 as 1000k

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R1#edit unit 0 [edit interfaces so-0/0/0 unit 0] user@R1#set bandwidth 1000k [edit interfaces so-0/0/0 unit 0]

user@R1#exit

[edit interfaces so-0/0/0]

user@R1#exit

[edit]

user@R1#

Back

9.15 :Lab Exercise 15 : Configuring the hold-time value on a physical interface to damp interface transitions

Description: Hold-time value is used to damp interface transitions. When an interface goes from up to down, it is not advertised to the rest of the system as being down until it has remained down for the hold-time period. Similarly, an interface is not advertised as being up until it has remained up for the hold-time period.

Instructions:

1. Enter into configuration mode.

2. Set the holdtime value of 200 milliseconds to use when an interface transitions from

down to up and holdtime value of 200 milliseconds to use when an interface transitions from up to down .

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R1#set hold-time up 200 down 200 [edit interfaces so-0/0/0]

user@R1#exit

[edit]

user@R1#

Back

9.16 : Lab Exercise 16 : Configuring the DTE Clock Rate

Description: This lab is used to configure the DTE clock-rate in serial clocking mode.

Instructions:

1. Enter into configuration mode.

2. Configure the clock rate of 2.048mhz on so-0/0/0.

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 serial-options [edit interfaces so-0/0/0 serial-options] user@R1#set clock-rate 2.048mhz [edit interfaces so-0/0/0 serial-options]

user@R1#exit

[edit]

user@R1#

Back

9.17 : Lab Exercise 17 : Basic gigabit ethernet configuration on a J-series

router

Description : This lab exercise demonstrates configuring the gigabit ethernet interface on a J- series router and also setting other basic parameters like hostname, domain-name, name-server, backup router etc. Show command is issued to verify the configuration set on the router.

is issued to verify the configuration set on the router. Instructions 1. Enter into system hierarchy

Instructions

1. Enter into system hierarchy on R1

2. Set the router hostname as Router1, domain-name as router.net, root-authentication as vhvc#!,

name-server as 10.148.2.32, backup-router as 192.168.2.34/24

3. Exit from system hierarchy and enter into interfaces hierarchy

4. Set the IP address on all the four fixed Gigabit Ethernet ports of J-Series router

5. Commit the configuration

6. Issue show configuration to verify the configuration set on the router.

7. Issue show interfaces brief command to display brief information about all interfaces configured on

the router.

8. Issue show interfaces terse command to display summary information about interfaces.

user@R1>configure

[edit] user@R1#edit system [edit system] user@R1#set host-name Router1 [edit system] user@Router1#set domain-name router.net [edit system] user@Router1#set root-authentication encrypted-password vhvc#! [edit system] user@Router1#set name-server 10.148.2.32 [edit system] user@Router1#set backup-router 192.168.2.34/24 [edit system]

user@Router1#exit

[edit] user@Router1#edit interfaces [edit interfaces] user@Router1#set ge-0/0/0 unit 0 family inet address 192.168.1.1/24 [edit interfaces] user@Router1#set ge-0/0/1 unit 0 family inet address 192.168.2.1/24 [edit interfaces] user@Router1#set ge-0/0/2 unit 0 family inet address 192.168.3.1/24 [edit interfaces] user@Router1#set ge-0/0/3 unit 0 family inet address 192.168.4.1/24 [edit interfaces]

user@Router1#exit

[edit]

user@Router1#commit

commit complete [edit]

user@Router1#exit

user@Router1>show configuration user@Router1>show interfaces brief user@Router1>show interfaces terse

Back

9.18 : Lab Exercise 18 : Configuring speed on sonet interface

Description : This lab exercise demonstrates configuring sonet interface speed.

Instructions

1. Enter into interfaces hierarchy on R1

2. Set the sonet interface speed to OC48

user@R1>configure

[edit] user@R1#edit interfaces [edit interfaces] user@R1#set so-0/0/0 speed OC48

[edit interfaces]

Back

9.19 : Lab Exercise 19 : Show chassis commands on J and M-series routers

Description: This lab demonstrates the show chassis commands.

This lab demonstrates the show chassis commands. Instructions 1. Display environmental information about the

Instructions

1. Display environmental information about the routing platform chassis, including the

temperature and information about the fans, power supplies, and Routing Engine

2. Displays a list of all Flexible Physical Interface Card Concentrators (FPCs) and PICs installed

in the router chassis, including the hardware version level and serial number.

3. Displays the FIC information, such as the FIC type, ASIC type, operating status, PIC version,

and the amount of time the FIC has been online. The command output also displays port cable information.

user@R1>show chassis environment user@R2>show chassis hardware user@R3>show chassis pic pic-slot 3 fpc-slot 1

Back

9.20 : Objective Test 1 : Answer the following questions

1. For which two functions is the Routing Engine responsible? (Choose two.)

A. packet forwarding

B. queuing functions

C. routing protocol control

D. JUNOS software operation

2. Which command would correctly define a router's host-name?

A. # set ip host-name

B. > set ip host-name

C. # set system host-name

D. > set system host-name

3. The interface ge-0/2/3 is located in which flexible PIC concentrator slot?

A. 0

B. 2

C. 3

D. 4

4. How many FPC slots are there on M40 router?

A. 2

B. 4

C. 6

D. 8

5. Which command configures an address of 192.168.1.1 with a mask of 255.255.255.0 on

interface ge-0/0/0?

A. set ip interface ge-0/0/0 address 192.168.1.1 255.255.255.0

B. set ip interface ge-0/0/0 address 192.168.1.1/24

C. set interface ge-0/0/0 ip4 address 192.168.1.1 mask 255.255.255.0

D. set interfaces ge-0/0/0 unit 0 family inet address 192.168.1.1/24

6. Which protocol family is required prior to assigning an IP address to an interface?

A. family ip

B. family ip6

C. family inet

D. family inet4

7. Which operational command allows a user to view the exhaust temperatures of a Juniper

device?

A. show chassis state

B. file list alarm

C. show chassis alarms

D. show chassis environment

8.

In which mode are users allowed to configure the device, including interfaces, protocols,

user access, and system hardware properties?

A. priviledged mode

B. configuration mode

C. monitoring mode

D. operational mode

9. Which command is used to retrieve the serial numbers of a Juniper device?

A. show version

B. show chassis hardware

C. show hardware detail

D. view hardware database

10. What are the primary responsibilities of the RE?

A. Control routing protocol traffic, perform route look-ups

B. Forward data traffic, perform route filtering

C. Maintain routing protocols, control software processes

D. Manage interfaces, reassemble packets from shared memory

10. STATIC ROUTING LABS

10.1 : Lab Exercise 1 : Configuring Static Routes

Description: Configure static route 172.16.1.0 mask 255.255.255.0 with next hop address of 192.16.2.1.

syntax: ip route prefix mask {address|interface} [distance]

prefix mask: is the ip route prefix and mask for the destination. address|interface: Use either the next hop router ip or the local router outbound interface used to reach the destination. distance: is the administrative distance and an optional parameter.

Instructions:

1. Enter into Global Configuration Mode

2. Configure a static route to a destination sub-network (172.16.1.0) with 24-bit subnet

mask and next hop IP address of 172.16.2.1.

user@R1>configure

[edit] user@R1#edit routing-options [edit routing-options] user@R1#edit static route 172.16.1.0/24

[edit routing-options static route 172.16.1.0/24] user@R1#set next-hop 172.16.2.1 [edit routing-options static route 172.16.1.0/24]

user@R1#exit

[edit routing-options]

user@R1#exit

[edit]

user@R1#

Back

10.2 : Lab Exercise 2 : Ping test

Description: The purpose of this lab is to configure IP Address on all the devices and test for connectivity using ping command. Applicable network diagram is given below

ping command. Applicable network diagram is given below Instructions: 1. Assign the IP address of all

Instructions:

1. Assign the IP address of all the devices as given below and commit the configurations

Device

Interface

IP Address

Mask

 

So-0/0/0

192.168.1.1

255.255.255.0

R1

So-0/0/1

192.168.3.2

255.255.255.0

 

So-0/0/0

192.168.3.1

255.255.255.0

R2

So-0/0/1

192.168.2.1

255.255.255.0

So-0/0/0

So-0/0/1

192.168.1.2

192.168.2.2

255.255.255.0

255.255.255.0

R3

2. From R1 issue a ping command to R2 and R3

3. Commands to be executed:

On R1:

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R1#edit unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R1#set address 192.168.1.1/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R1#exit

[edit interfaces so-0/0/0]

user@R1#exit

[edit] user@R1#edit interfaces so-0/0/1 [edit interfaces so-0/0/1] user@R1#edit unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R1#set address 192.168.3.2/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R1#exit

[edit interfaces so-0/0/1]

user@R1#exit

[edit]

user@R1#commit

commit complete [edit]

user@R1#

On R2:

user@R2>configure

[edit] user@R2#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R2#edit unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R2#set address 192.168.3.1/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R2#exit

[edit interfaces so-0/0/0]

user@R2#exit

[edit] user@R2#edit interfaces so-0/0/1 [edit interfaces so-0/0/1] user@R2#edit unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R2#set address 192.168.2.1/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R2#exit

[edit interfaces so-0/0/1]

user@R2#exit

[edit]

user@R2#commit

commit complete [edit]

user@R2#

On R3:

user@R3>configure

[edit] user@R3#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R3#edit unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R3#set address 192.168.1.2/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R3#exit

[edit interfaces so-0/0/0]

user@R3#exit

[edit] user@R3#edit interfaces so-0/0/1 [edit interfaces so-0/0/1 user@R3#edit unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R3#set address 192.168.2.2/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R3#exit

[edit interfaces so-0/0/1]

user@R3#exit

[edit]

user@R3#commit

commit complete [edit]

user@R3#

On R1:

user@R1>ping 192.168.2.2 user@R1>ping 192.168.2.1

Back

10.3 : Lab Exercise 3 : Telnet

Description: The purpose of this lab is to configure IP Address on all the devices and test for telnet command. Applicable network diagram is shown below:

telnet command. Applicable network diagram is shown below: Instructions: 1.Assign the IP address of all the

Instructions:

1.Assign the IP address of all the devices as given below and commit the configurations

Device

Interface

IP Address

Mask

 

So-0/0/0

192.168.1.1

255.255.255.0

R1

So-0/0/1

192.168.3.2

255.255.255.0

 

So-0/0/0

192.168.3.1

255.255.255.0

R2

So-0/0/1

192.168.2.1

255.255.255.0

 

So-0/0/0

192.168.1.2

255.255.255.0

R3

So-0/0/1

192.168.2.2

255.255.255.0

2. From R1 issue a telnet command to R2 and R3 and use quit command to close the telnet

connection

3. Issue show system users command on R2 to view the logged in users on the router

4. Commands to be executed:

On R1:

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R1#edit unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R1#set address 192.168.1.1/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R1#exit

[edit interfaces so-0/0/0]

user@R1#exit

[edit] user@R1#edit interfaces so-0/0/1 [edit interfaces so-0/0/1] user@R1#edit unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R1#set address 192.168.3.2/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R1#exit

[edit interfaces so-0/0/1]

user@R1#exit

[edit]

user@R1#commit

commit complete [edit]

user@R1#

On R2:

user@R2>configure

[edit] user@R2#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R2#edit unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R2#set address 192.168.3.1/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R2#exit

[edit interfaces so-0/0/0]

user@R2#exit

[edit] user@R2#edit interfaces so-0/0/1 [edit interfaces so-0/0/1] user@R2#edit unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R2#set address 192.168.2.1/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R2#exit

[edit interfaces so-0/0/1]

user@R2#exit

[edit]

user@R2#commit

commit complete [edit]

user@R2#

On R3:

user@R3>configure

[edit] user@R3#edit interfaces so-0/0/0 [edit interfaces so-0/0/0] user@R3#edit unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R3#set address 192.168.1.2/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R3#exit

[edit interfaces so-0/0/0]

user@R3#exit

[edit] user@R3#edit interfaces so-0/0/1 [edit interfaces so-0/0/1] user@R3#edit unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R3#set address 192.168.2.2/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R3#exit

[edit interfaces so-0/0/1]

user@R3#exit

[edit]

user@R3#commit

commit complete [edit]

user@R3#

On R1:

user@R1>telnet 192.168.2.2 user@R1>telnet 192.168.2.1 user@R2>show system users

10.4 : Lab Exercise 4 : Traceroute

Back

Description: The purpose of this lab is to configure the routers and test for traceroute command.

Instructions: 1. Assign the IP address of all the devices as given below Device Interface

Instructions:

1. Assign the IP address of all the devices as given below

Device

Interface

IP Address

Mask

R1

se-0/0/0

192.168.3.1

255.255.255.0

se-0/0/1

192.168.1.1

255.255.255.0

R2

se-0/0/0

192.168.1.2

255.255.255.0

se-0/0/1

192.168.2.1

255.255.255.0

R3

se-0/0/0

192.168.3.2

255.255.255.0

se-0/0/1

192.168.2.2

255.255.255.0

2. From R1 issue a traceroute command to R3

Commands to be executed:

On R1:

user@R1>configure

[edit] user@R1#edit interfaces se-0/0/0 [edit interfaces se-0/0/0]

user@R1#edit unit 0 family inet [edit interfaces se-0/0/0 unit 0 family inet] user@R1#set address 192.168.3.1/24 [edit interfaces se-0/0/0 unit 0 family inet]

user@R1#exit

[edit interfaces se-0/0/0]

user@R1#exit

[edit] user@R1#edit interfaces se-0/0/1 [edit interfaces se-0/0/1] user@R1#edit unit 0 family inet [edit interfaces se-0/0/1 unit 0 family inet] user@R1#set address 192.168.1.1/24 [edit interfaces se-0/0/1 unit 0 family inet]

user@R1#exit

[edit interfaces se-0/0/1]

user@R1#exit

[edit]

user@R1#commit

commit complete [edit]

user@R1#

On R2:

user@R2>configure

[edit] user@R2#edit interfaces se-0/0/0 [edit interfaces se-0/0/0] user@R2#edit unit 0 family inet [edit interfaces se-0/0/0 unit 0 family inet] user@R2#set address 192.168.1.2/24 [edit interfaces se-0/0/0 unit 0 family inet]

user@R2#exit

[edit interfaces se-0/0/0]

user@R2#exit

[edit] user@R2#edit interfaces se-0/0/1 [edit interfaces se-0/0/1] user@R2#edit unit 0 family inet [edit interfaces se-0/0/1 unit 0 family inet] user@R2#set address 192.168.2.1/24 [edit interfaces se-0/0/1 unit 0 family inet]

user@R2#exit

[edit interfaces se-0/0/1]

user@R2#exit

[edit]

user@R2#commit

commit complete [edit]

user@R2#

On R3:

user@R3>configure

[edit] user@R3#edit interfaces se-0/0/0 [edit interfaces se-0/0/0] user@R3#edit unit 0 family inet [edit interfaces se-0/0/0 unit 0 family inet] user@R3#set address 192.168.3.2/24 [edit interfaces se-0/0/0 unit 0 family inet]

user@R3#exit

[edit interfaces se-0/0/0]

user@R3#exit

[edit] user@R3#edit interfaces se-0/0/1 [edit interfaces se-0/0/1] user@R3#edit unit 0 family inet [edit interfaces se-0/0/1 unit 0 family inet] user@R3#set address 192.168.2.2/24 [edit interfaces se-0/0/1 unit 0 family inet]

user@R3#exit

[edit interfaces se-0/0/1]

user@R3#exit

[edit]

user@R3#commit

commit complete [edit]

user@R3#

On R1:

user@R1>traceroute 192.168.2.2

Back

10.5 : Objective Test 2 : Answer the following questions

1. What is the route preference of a static route?

A. 1

B. 5

C. 15

D. 20

2. You want to configure a static default route to the gateway 10.1.1.1. Which set command will

accomplish this task?

A. Set routes static route 0.0.0.0/0 gateway 10.1.1.1

B. Set protocols static route 0.0.0.0/0 next-hop 10.1.1.1

C. Set family inet static route 0.0.0.0/0 next-hop 10.1.1.1

D. Set routing-options static route 0.0.0.0/0 next-hop 10.1.1.1

3. When you display the routing table by entering the show route command, what does the *

indicate?

 

A.

The route is a direct route.

B.

The route was selected as active.

C.

The route is a default route.

D.

The route was learned using a dynamic routing protocol.

4. In which table are static routes installed?

A. inet.0

B. inet.1

C. inet.2

D. inet.3

5. What is correct regarding the configuration shown below?

static route 0.0.0.0/0 qualified-next-hop 172.30.25.1 preference 7 next-hop 172.30.25.5

A. The next-hop 172.30.25.1 is selected because the address has the lowest value.

B. The next-hop 172.30.25.1 is selected because it is listed first.

C. The next-hop 172.30.25.1 is selected because it is the lowest protocol preference.

D. The next-hop 172.30.25.5 is selected because it is the lowest protocol preference.

11. POLICIES CONFIGURATION LABS

11.1 : Lab Exercise 1 : Routing Policy Lab 1

Description: Use this lab to configure the routing policy on router, by specifying the match condition to accept all rip routes, that is checked against the source address of the route advertised.

Instructions:

1. Enter into configuration mode.

2. Create a policy statement by name as same as riproutes.

3. Create a term under the policy created above by the name as AdvRip.

4. Create a match condition and specify to accept rip routes under the above term.

user@R1>configure

[edit] user@R1#edit policy-options policy-statement riproutes [edit policy-options policy-statement riproutes] user@R1#edit term AdvRip [edit policy-options policy-statement riproutes term AdvRip] user@R1#edit from [edit policy-options policy-statement riproutes term AdvRip from] user@R1#set protocol rip [edit policy-options policy-statement riproutes term AdvRip from]

user@R1#exit

[edit policy-options policy-statement riproutes term AdvRip] user@R1#edit then [edit policy-options policy-statement riproutes term AdvRip then] user@R1#set accept [edit policy-options policy-statement riproutes term AdvRip then]

user@R1#exit

[edit policy-options policy-statement riproutes term AdvRip]

user@R1#exit

[edit policy-options policy-statement riproutes]

user@R1#exit

[edit]

user@R1#

Back

11.2 : Lab Exercise 2 : Routing Policy Lab 2

Description: Use this lab to configure the routing policy on router, by specifying the match condition to reject all rip routes, that is checked against the source address of the route advertised.

Instructions:

1. Enter into configuration mode.

2. Create a policy statement by name as same as riproutes.

3. Create a term under the policy created above by the name as AdvRip.

4. Create a match condition and specify to reject rip routes under the above term.

user@R1>configure

[edit] user@R1#edit policy-options policy-statement riproutes [edit policy-options policy-statement riproutes] user@R1#edit term AdvRip [edit policy-options policy-statement riproutes term AdvRip] user@R1#edit from [edit policy-options policy-statement riproutes term AdvRip from] user@R1#set protocol rip [edit policy-options policy-statement riproutes term AdvRip from]

user@R1#exit

[edit policy-options policy-statement riproutes term AdvRip]

user@R1#edit then [edit policy-options policy-statement riproutes term AdvRip then] user@R1#set reject [edit policy-options policy-statement riproutes term AdvRip then]

user@R1#exit

[edit policy-options policy-statement riproutes term AdvRip]

user@R1#exit

[edit policy-options policy-statement riproutes]

user@R1#exit

[edit]

user@R1#

Back

11.3 : Objective Test 3 : Answer the following questions

1 What happens when a route does not match any user configured policies?

A. The route is rejected.

B. The route is accepted.

C. The route is given a lower priority.

D. The route is sent to the default policy.

2. A routing policy has three terms and the first term of the policy does not contain a

terminating action. What will become of the routes after they have been evaluated by the

first term?

A. In the absence of a terminating action, all routes are accepted.

B. The route will be evaluated by the second term in the policy.

C. The default action will be applied.

D. In the absence of a termination action, all routes are rejected.

3. Which statement is true about import and export routing policies?

A. Import policies concern routes received and determine which routes get put

into the routing table.

B. Export policies concern routes received and determine which routes get put

into the routing table.

C. Export policies are applied before the routing table.

D. Import polices are applied after the routing table.

4. Which two policy actions are considered flow control actions? (Choose two.)

A. reject

B. community add

C. next term

D. next policy

5. Which statement is correct about a Routing Policy term?

A. A term must contain a "from" statement.

B. A term acts like "if" and "then" statements.

C. The most specific term has precedence.

D. Terms can be written in any order to achieve the same behavior.

12. RIP CONFIGURATION LAB

12.1 : Lab Exercise 1 : RIP Configuration

Description: Use this lab to configure the RIP on router, by applying an export and import policies at their respective hierarchical levels.

Instructions:

1. Enter into configuration mode.

2. Enable RIP routing on the router.

3. Create a group called neighborRouters apply an export policy riproutes to this group.

4. Specify the neighbor interface as so-0/0/0 under the above created group and apply an

import policy riproutes to this neighbor.

user@R1>configure

[edit] user@R1#edit protocols rip [edit protocols rip] user@R1#edit group neighborRouters [edit protocols rip group neighborRouters] user@R1#set export riproutes [edit protocols rip group neighborRouters] user@R1#edit neighbor so-0/0/0 [edit protocols rip group neighborRouters neighbor so-0/0/0] user@R1#set import riproutes [edit protocols rip group neighborRouters neighbor so-0/0/0]

user@R1#exit

[edit protocols rip group neighborRouters]

user@R1#exit

[edit protocols rip]

user@R1#exit

[edit]

user@R1#

Back

12.2 : Objective Test 4 : Answer the following questions

1. What is the max hop count for a reachable RIP route?

A. 15

B. 16

C. 10

D. 255

2. How do you send static routes to a RIP neighbor?

A. By default, RIP automatically sends static routes.

B. Configure the static route with a next hop of the RIP neighbor.

C. Configure redistribute static under [edit protocols rip].

D. Apply an export policy within RIP that matches on the routes, and accepts it.

3. What two mechanisms does RIP use to prevent routing loops (select 2)?

A. Split-Horizon

B. Link-state database

C. Random routing database checks

D. Poison-reverse

4. Which two statements are correct regarding default protocol preference values? (Choose

two.)

A. OSPF has a single preference value for both internal and external routes.

B. RIP is preferred over OSPF external routes.

C. Direct, local, and static routes have the same preference value.

D. OSPF's preference value is lower than BGP (both IBGP and EBGP).

5. RIP is a distance vector routing protocol that depends on which of the following for

routing distance measurement?

A. Bandwidth

B. Delay

C. Number of Hops

D. Reliability

13. DYNAMIC ROUTING LABS

13.1 : Lab Exercise 1 : Ping test by configuring RIP

Description: The purpose of this lab is to configure RIP Routing and other required commands to advertise these rip routes on all the devices and test for ping command. Applicable network diagram is given below:

Note: .1 on router 1 So refers to 192.168.1.1. Similarly other IP addresses to be

Note: .1 on router 1 So refers to 192.168.1.1. Similarly other IP addresses to be interpreted.

Instructions:

1. Assign the IP address of all the devices as given below

Device

Interface

IP Address

Mask

 

So-0/0/0

192.168.3.1

255.255.255.0

R1

So-0/0/1

192.168.1.1

255.255.255.0

 

So-0/0/0

192.168.1.2

255.255.255.0

R2

So-0/0/1

192.168.2.1

255.255.255.0

 

So-0/0/0

192.168.3.2

255.255.255.0

R3

So-0/0/1

192.168.2.2

255.255.255.0

2. Enable RIP routing on all the devices

3. Specify the policy to accept the rip routes on all the devices

4. Apply an import policy and an export policy (policy created above) on all the devices.

5. Issue show rip neighbor command on all the devices to view its neighbor information

6. From R1 issue a ping command to R2 and R3

On R1:

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R1#set address 192.168.3.1/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R1#exit

[edit] user@R1#edit interfaces so-0/0/1 unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R1#set address 192.168.1.1/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R1#exit

[edit] user@R1#edit policy-options policy-statement R1pol term R1term [edit policy-options policy-statement R1pol term R1term] user@R1#edit from [edit policy-options policy-statement R1pol term R1term from] user@R1#set protocol rip [edit policy-options policy-statement R1pol term R1term from]

user@R1#exit

[edit policy-options policy-statement R1pol term R1term] user@R1#edit then [edit policy-options policy-statement R1pol term R1term then] user@R1#set accept [edit policy-options policy-statement R1pol term R1term then]

user@R1#exit

[edit policy-options policy-statement R1pol term R1term]

user@R1#exit

[edit] user@R1#edit protocols rip group R1grp [edit protocols rip group R1grp] user@R1#set export R1pol [edit protocols rip group R1grp] user@R1#edit neighbor so-0/0/0 [edit protocols rip group R1grp neighbor so-0/0/0] user@R1#set import R1pol [edit protocols rip group R1grp neighbor so-0/0/0]

user@R1#exit

[edit protocols rip group R1grp] user@R1#edit neighbor so-0/0/1 [edit protocols rip group R1grp neighbor so-0/0/1] user@R1#set import R1pol [edit protocols rip group R1grp neighbor so-0/0/1]

user@R1#exit

[edit protocols rip group R1grp]

user@R1#exit

[edit]

user@R1#commit

commit complete [edit]

user@R1#exit

user@R1>show rip neighbor

On R2:

user@R2>configure

[edit] user@R2#edit interfaces so-0/0/0 unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R2#set address 192.168.1.2/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R2#exit

[edit] user@R2#edit interfaces so-0/0/1 unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R2#set address 192.168.2.1/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R2#exit

[edit] user@R2#edit policy-options policy-statement R2pol term R2term [edit policy-options policy-statement R2pol term R2term] user@R2#edit from [edit policy-options policy-statement R2pol term R2term from] user@R2#set protocol rip [edit policy-options policy-statement R2pol term R2term from]

user@R2#exit

[edit policy-options policy-statement R2pol term R2term] user@R2#edit then [edit policy-options policy-statement R2pol term R2term then] user@R2#set accept [edit policy-options policy-statement R2pol term R2term then]

user@R2#exit

[edit policy-options policy-statement R2pol term R2term]

user@R2#exit

[edit] user@R2#edit protocols rip group R2grp [edit protocols rip group R2grp] user@R2#set export R2pol [edit protocols rip group R2grp] user@R2#edit neighbor so-0/0/0 [edit protocols rip group R2grp neighbor so-0/0/0] user@R2#set import R2pol [edit protocols rip group R2grp neighbor so-0/0/0]

user@R2#exit

[edit protocols rip group R2grp] user@R2#edit neighbor so-0/0/1 [edit protocols rip group R2grp neighbor so-0/0/1] user@R2#set import R2pol [edit protocols rip group R2grp neighbor so-0/0/1]

user@R2#exit

[edit protocols rip group R2grp]

user@R2#exit

[edit]

user@R2#commit

commit complete [edit]

user@R2#exit

user@R2>show rip neighbor

On R3:

user@R3>configure

[edit] user@R3#edit interfaces so-0/0/0 unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R3#set address 192.168.3.2/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R3#exit

[edit] user@R3#edit interfaces so-0/0/1 unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R3#set address 192.168.2.2/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R3#exit

[edit] user@R3#edit policy-options policy-statement R3pol term R3term [edit policy-options policy-statement R3pol term R3term] user@R3#edit from [edit policy-options policy-statement R3pol term R3term from] user@R3#set protocol rip [edit policy-options policy-statement R3pol term R3term from]

user@R3#exit

[edit policy-options policy-statement R3pol term R3term] user@R3#edit then [edit policy-options policy-statement R3pol term R3term then] user@R3#set accept [edit policy-options policy-statement R3pol term R3term then]

user@R3#exit

[edit policy-options policy-statement R3pol term R3term]

user@R3#exit

[edit] user@R3#edit protocols rip group R3grp [edit protocols rip group R3grp] user@R3#set export R3pol [edit protocols rip group R3grp] user@R3#edit neighbor so-0/0/0 [edit protocols rip group R3grp neighbor so-0/0/0] user@R3#set import R3pol [edit protocols rip group R3grp neighbor so-0/0/0]

user@R3#exit

[edit protocols rip group R3grp] user@R3#edit neighbor so-0/0/1 [edit protocols rip group R3grp neighbor so-0/0/1] user@R3#set import R3pol [edit protocols rip group R3grp neighbor so-0/0/1]

user@R3#exit

[edit protocols rip group R3grp]

user@R3#exit

[edit]

user@R3#commit

commit complete [edit]

user@R3#exit

user@R3>show rip neighbor

On R1:

user@R1>ping 192.168.2.2 user@R1>ping 192.168.2.1

Back

13.2 : Lab Exercise 2 : Ping test by configuring OSPF with multiple areas

Description: The purpose of this lab is to configure OSPF on all the devices with multiple areas including backbone (area 0) area and test for ping command. Applicable network diagram is as given below:

for ping command. Applicable network diagram is as given below: Version 1.0 Copyright © 2002 -

Note: .1 on router 1 So refers to 192.168.1.1. Similarly other IP addresses to be interpreted.

Instructions:

1. Assign the IP address of all the devices as given below

Device

Interface

IP Address

Mask

 

So-0/0/0

192.168.3.1

255.255.255.0

R1

So-0/0/1

192.168.1.1

255.255.255.0

 

So-0/0/0

192.168.1.2

255.255.255.0

R2

So-0/0/1

192.168.2.1

255.255.255.0

 

So-0/0/0

192.168.3.2

255.255.255.0

R3

So-0/0/1

192.168.2.2

255.255.255.0

2. Enable OSPF on R1 with So-0/0/0 under area 0 and So-0/0/1 under area 10

3. Enable OSPF on R2 with So-0/0/0 under area 10 and So-0/0/1 under area 20

4. Enable OSPF on R3 with So-0/0/0 under area 0 and So-0/0/1 under area 20

5. From R1 issue a ping command to R2 and R3.

On R1:

user@R1>configure

[edit] user@R1#edit interfaces so-0/0/0 unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R1#set address 192.168.3.1/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R1#exit

[edit] user@R1#edit interfaces so-0/0/1 unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R1#set address 192.168.1.1/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R1#exit

[edit] user@R1#edit protocols ospf area 0 interface so-0/0/0 [edit protocols ospf area 0 interface so-0/0/0]

user@R1#exit

[edit] user@R1#edit protocols ospf area 10 interface so-0/0/1 [edit protocols ospf area 10 interface so-0/0/1]

user@R1#exit

[edit]

user@R1#commit

commit complete [edit]

user@R1#

On R2:

user@R2>configure

[edit] user@R2#edit interfaces so-0/0/0 unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R2#set address 192.168.1.2/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R2#exit

[edit] user@R2#edit interfaces so-0/0/1 unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R2#set address 192.168.2.1/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R2#exit

[edit] user@R2#edit protocols ospf area 10 interface so-0/0/0 [edit protocols ospf area 10 interface so-0/0/0]

user@R2#exit

[edit] user@R2#edit protocols ospf area 20 interface so-0/0/1 [edit protocols ospf area 20 interface so-0/0/1]

user@R2#exit

[edit]

user@R2#commit

commit complete [edit]

user@R2#

On R3:

user@R3>configure

[edit] user@R3#edit interfaces so-0/0/0 unit 0 family inet [edit interfaces so-0/0/0 unit 0 family inet] user@R3#set address 192.168.3.2/24 [edit interfaces so-0/0/0 unit 0 family inet]

user@R3#exit

[edit] user@R3#edit interfaces so-0/0/1 unit 0 family inet [edit interfaces so-0/0/1 unit 0 family inet] user@R3#set address 192.168.2.2/24 [edit interfaces so-0/0/1 unit 0 family inet]

user@R3#exit

[edit]

user@R3#edit protocols ospf area 0 interface so-0/0/0 [edit protocols ospf area 0 interface so-0/0/0]

user@R3#exit

[edit] user@R3#edit protocols ospf area 20 interface so-0/0/1 [edit protocols ospf area 20 interface so-0/0/1]

user@R3#exit

[edit]

user@R3#commit

commit complete [edit]

user@R3#

On R1:

user@R1>ping 192.168.2.2 user@R1>ping 192.168.2.1

 

Back

14. SHOW COMMAND LAB