Juniper Lab Manual

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
Version 1.0 Copyright 2002 - 2011 CertExams.com 1
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
Version 1.0
Copyright 2002 - 2011 CertExams.com
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 / VLANName 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
Version 1.0
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 highperformance 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.
Version 1.0
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.
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
Version 1.0
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-toPoint Protocol over Ethernet (PPPoE), and ISDN media. Slot numbering for J2320 router
Slot numbering for J2350 router
Version 1.0
4.1. J2320 Router Front Panel and its Components

The front panel of the J2320 router is as shown below
The cross section as indicated by AA is provided in an enlarged scale below:
Version 1.0
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
Version 1.0
10
Color State Blinking Green On steadily Red Blinking
Description Router is starting up or performing diagnostics Router is operating normal 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.
Version 1.0
11
4.2. Rear Panel of J2320 router
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 UNIXBased 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
A 1-port Gigabit Ethernet uPIM is as shown
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.
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
Version 1.0
15
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
Version 1.0
16
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.
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.
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
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
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
Version 1.0
26
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.
Version 1.0
27
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
Version 1.0
28
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 so0/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
Version 1.0
32
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 Jseries 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.
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.
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
Version 1.0
36
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
Instructions: 1. Assign the IP address of all the devices as given below and commit the configurations Device Interface IP Address R1 So-0/0/0 So-0/0/1 So-0/0/0 So-0/0/1 192.168.1.1 192.168.3.2 192.168.3.1 192.168.2.1 Mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
R2
Version 1.0
38
R3
So-0/0/0 So-0/0/1
192.168.1.2 192.168.2.2
255.255.255.0 255.255.255.0
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:
Instructions: 1.Assign the IP address of all the devices as given below and commit the configurations Device Interface R1 So-0/0/0 So-0/0/1 So-0/0/0 So-0/0/1 So-0/0/0 So-0/0/1 IP Address 192.168.1.1 192.168.3.2 192.168.3.1 192.168.2.1 192.168.1.2 192.168.2.2 Mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
R2
R3
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:
Version 1.0
41
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 Back
10.4 : Lab Exercise 4 : Traceroute

Description: The purpose of this lab is to configure the routers and test for traceroute command.
Version 1.0
43
Instructions: 1. Assign the IP address of all the devices as given below Device R1 Interface se-0/0/0 se-0/0/1 se-0/0/0 se-0/0/1 se-0/0/0 se-0/0/1 IP Address 192.168.3.1 192.168.1.1 192.168.1.2 192.168.2.1 192.168.3.2 192.168.2.2 Mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
R2
R3
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

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

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
Version 1.0
50

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:
Version 1.0
51
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 R1 Interface So-0/0/0 So-0/0/1 So-0/0/0 So-0/0/1 So-0/0/0 So-0/0/1 IP Address 192.168.3.1 192.168.1.1 192.168.1.2 192.168.2.1 192.168.3.2 192.168.2.2 Mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
R2
R3
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:
Version 1.0
56
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 R1 Interface So-0/0/0 So-0/0/1 So-0/0/0 So-0/0/1 So-0/0/0 So-0/0/1 IP Address 192.168.3.1 192.168.1.1 192.168.1.2 192.168.2.1 192.168.3.2 192.168.2.2 Mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
R2
R3
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 14.1 : Lab Exercise 1 : Show Commands

Description: This exercise demonstrates various basic show commands available. Instructions: 1. Issue show version brief command. 2. Issue show cli command. 3. Issue show cli historycommand. user@R1>show version brief user@R1>show cli user@R1>show cli history Back
15. OSPF LABS 15.1 : Lab Exercise 1 : OSPF Configuration

Description: Use this lab to configure the OSPF on router with an area 0. Instructions: 1. Enter into configuration mode. 2. Enable OSPF routing on the router. 3. Put the interfaces so-0/0/0 and so-0/0/1 under area 0.
user@R1>configure [edit] user@R1#edit protocols ospf [edit protocols ospf] user@R1#edit area 0 [edit protocols ospf area 0] user@R1#edit interface so-0/0/0 [edit protocols ospf area 0 interface so-0/0/0] user@R1#exit [edit protocols ospf area 0] user@R1#edit interface so-0/0/1 [edit protocols ospf area 0 interface so-0/0/1] user@R1#exit [edit protocols ospf area 0] user@R1#exit [edit protocols ospf] user@R1#exit [edit] user@R1# Back
15.2 : Lab Exercise 2 : OSPF configuration and verification

Description: The purpose of this lab is to configure OSPF on all the devices with an area of 100 and to verify the configuration using show commands of OSPF.Applicable network diagram is shown below:
Version 1.0
60
Instructions: 1. Assign the IP address of all the devices as given below Device R1 Interface So-0/0/0 So-0/0/1 So-0/0/0 So-0/0/1 So-0/0/0 So-0/0/1 IP Address 192.168.3.1 192.168.1.1 192.168.1.2 192.168.2.1 192.168.3.2 192.168.2.2 Mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
R2
R3
2. Enable OSPF (use area number as 100) on all the interfaces of all the devices 3. Issue show ospf interface on R1 4. Issue show ospf neighbor on R1. 5. Issue show ospf database on R1. 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 100 interface so-0/0/0 [edit protocols ospf area 100 interface so-0/0/0] user@R1#exit [edit] user@R1#edit protocols ospf area 100 interface so-0/0/1 [edit protocols ospf area 100 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 100 interface so-0/0/0 [edit protocols ospf area 100 interface so-0/0/0] user@R2#exit [edit] user@R2#edit protocols ospf area 100 interface so-0/0/1 [edit protocols ospf area 100 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 100 interface so-0/0/0 [edit protocols ospf area 100 interface so-0/0/0] user@R3#exit [edit] user@R3#edit protocols ospf area 100 interface so-0/0/1
[edit protocols ospf area 100 interface so-0/0/1] user@R3#exit [edit] user@R3#commit commit complete [edit] user@R3# On R1: user@R1>show ospf interface user@R1>show ospf neighbor user@R1>show ospf database Back

1. What is the default protocol preference for OSPF external routes? A. 10 B. 15 C. 150 D. 160 2. Which command allows viewing of only OSPF routes? A. show ip ospf route B. show ip route protocol ospf C. show route protocol ospf D. show ospf table 3. What is the default OSPF timer values? A. 20 sec hello-time and 20 sec dead-time B. 10 sec hello-time and 60 sec dead-time C. 10 sec hello-time and 40 sec dead-time D. 20 sec hello-time and 40 sec dead-time 4. Which CLI command will show the state of OSPF to other routers? A. show ospf interface B. show ospf adjacency C. show ospf neighbor D. show ospf detail
Version 1.0
63
5. Which CLI command will show the type of networks the router participates in (point-to-point, BMA etc)? A. show ospf interface B. show ospf adjacency C. show ospf neighbor D. show ospf detail
16. Juniper Switch Models

Juniper switches are available in two series a. EX Series Ethernet Switches : Deliver high performance, carrier-class solutions built to meet the needs of today's converged branch office, campus, and data center networks. b. QFX Series : High-performance devices deliver Juniper's unique QFabric architecture, supporting thousands of ports within a single-tier data center or cloud network with ultra-low latency, high resiliency, and the simplicity of a single switch.
17. EX Series Switches Overview 17.1. EX2200 Switch

Juniper Networks EX2200 Ethernet switches provide connectivity for low-density environments. EX2200 switches are available in models with either 24 or 48 built-in network ports and four uplink ports, with Power over Ethernet (PoE) either available in all built-in network ports or not available in any built-in network port. All models provide network ports that have 10/100/1000Base-T Gigabit Ethernet connectors and four uplink ports. These switches run under Junos OS for EX Series switches. Each EX2200 switch has four uplink ports that support 1gigabit small form-factor pluggable (SFP) transceivers for use with fiber connections and copper connections. PoE ports provide electrical current to devices through the network cables so that separate power cords for devices such as IP phones, wireless access points, and security cameras are unnecessary. Model Number EX2200-24T-4G EX2200-24P-4G EX2200-48T-4G Access Ports 24 Gigabit Ethernet 24 Gigabit Ethernet 48 Gigabit Ethernet PoE Enabled Ports All 24 ports -
Version 1.0
64
EX2200-48P-4G
48 Gigabit Ethernet
All 48 ports
17.1.1. EX2200 Front Panel The front panel of an EX2200 switch consists of the following components: Network portsdepending on the switch model, either of: 24 or 48 10/100/1000Base-T Gigabit Ethernet ports, with Power over Ethernet (PoE) not available in EX2200-24T and EX2200-48T 24 or 48 10/100/1000Base-T Gigabit Ethernet ports, with Power over Ethernet (PoE) available in EX2200-24P and EX2200-48P 4 built-in SFP uplink ports 2 chassis status LEDs 4 port status mode LEDs Mode button
17.1.2. Chassis LEDs The front panel of an EX2200 switch has two chassis status LEDs labeled SYS and ALM on the far right side of the panel, above the uplink ports.
Version 1.0
65
LED Label ALM
Color Unlit Amber Red
State and Decription There is no alarm There is a minor alarm There is a major alarm On steadily : The switch is functioning normally Blinking : The switch is booting Off : The switch is off
SYS
Green
17.1.3. EX2200 Rear Panel The rear panel of the EX2200 switch consists of the following components: Management Ethernet port USB port Console port Protective earthing terminal ESD point Air exhaust
Version 1.0
66
Serial number ID label AC power cord inlet
17.2. EX2500 Switch

The EX2500 line of ethernet switches delivers a compact, energy efficient ethernet solution for 10 gigabit Ethernet GbE top-of-rack data center access deployments where high performance, low latency and high availabilty are key requirements. The EX2500 switch has 24 SFP+ ports, 2 management ports, and 1 console port. (The EX2500 switch contains 24 10-gigabit Small Form-Factor Pluggable Plus (SFP+) ports and 2 1-gigabit management ports. The 10-gigabit SFP+ ports can accept 10-gigabit optical transceivers or Direct Attach Cables (DACs). This 1U switch is rack mountable in either the horizontal or vertical direction, depending on your application.) Model Number EX2500-24F-FB Description 24-port Gigabit Ethernet/10-Gigabit Ethernet SFP 24-port Gigabit Ethernet/10-Gigabit Ethernet SFP
EX2500-24F-BF
Note: SFP+ Ports: 24 Small Form-Factor Pluggable (SFP+) ports are located on the front panel. These ports accept approved optical SFP+ transceivers or direct access cables (DACs).
17.3. EX3200 Switch

The EX3200 line of Ethernet switches offers a simple, cost-effective solution for low-density branch and regional offices. EX3200 switches are available in models with either 24 or 48 ports and with either all ports equipped for Power over Ethernet (PoE) or only 8 ports equipped for PoE. EX3200 switches with a DC power supply installed do not provide PoE. All models provide ports that have 10/100/1000Base-T Gigabit Ethernet connectors and optional 1-gigabit small form-factor pluggable (SFP) transceivers, 10-gigabit small form-factor pluggable (SFP+) transceivers, or 10gigabit small form-factor pluggable (XFP) transceivers for use with fiber connections. Model EX3200-24T EX3200-48T EX3200-24P EX3200-48P EX3200-24T-DC EX3200-48T-DC Access Ports 24 Gigabit Ethernet 48 Gigabit Ethernet 24 Gigabit Ethernet 48 Gigabit Ethernet 24 Gigabit Ethernet 48 Gigabit Ethernet No of PoE enabled ports First 8 ports First 8 ports All 24 ports All 48 ports -
17.4. EX4200 Switch

Juniper Networks EX4200 Ethernet Switches provide connectivity for medium- and high-density environments and scalability for growing networks. EX4200 switches are available in models with 24 or 48 ports and with either all ports equipped for Power over Ethernet (PoE) or only 8 ports equipped for PoE. All models provide ports that have 10/100/1000Base-T Gigabit Ethernet connectors and optional 1-gigabit small form-factor pluggable (SFP) transceivers, 10-gigabit small form-factor pluggable (SFP+) transceivers, or 10gigabit small form-factor pluggable (XFP) transceivers for use with fiber connections. Additionally, a 24-port model provides 100Base-FX/1000Base-X SFP ports. This model is typically used as a small distribution switch.
Version 1.0
68
Model EX4200-24T EX4200-48T EX4200-24P EX4200-48P EX4200-24F EX4200-24T-DC EX4200-48T-DC EX4200-24F-DC
Ports 24 Gigabit Ethernet 48 Gigabit Ethernet 24 Gigabit Ethernet 48 Gigabit Ethernet 24 Gigabit Ethernet 24 Gigabit Ethernet 48 Gigabit Ethernet 24 Gigabit Ethernet
PoE enabled ports First 8 ports First 8 ports All 24 ports All 48 ports
17.5. EX4500 Switch

EX4500 switches provide connectivity for high-density 10-Gigabit Ethernet data center top-ofrack and aggregation deployments. Typically, EX4500 switches are used in data centers where they can be positioned as the top device in a rack to provide connectivity for all devices in the rack. Model EX4500-40F-FB EX4500-40F-BF EX4500-40F-FB-C EX4500-40F-BF-C EX4500-40F-DC-C Access Port Configuration 40-port GbE/10GbE SFP/SFP+ 40-port GbE/10GbE SFP/SFP+ 40-port GbE/10GbE SFP/SFP+ 40-port GbE/10GbE SFP/SFP+ 40-port GbE/10GbE SFP/SFP+
Version 1.0
69
EX4500-40F-VC1-FB EX4500-40F-VC1-BF EX4500-40F-VC1-DC
40-port GbE/10GbE SFP/SFP+ 40-port GbE/10GbE SFP/SFP+ 40-port GbE/10GbE SFP/SFP+
Note: The FB and BF in the model number indicate the direction of airflow of the chassis: FBFront-to-back airflow BFBack-to-front airflow
The C in the model number indicates the Converged Enhanced Ethernet (CEE) status of switch: CCEE capable NoneNot CEE capable
The DC in the model number indicates that the switch model supports DC power supply. The VC in the model number indicates that the switch model can be used in a Virtual Chassis configuration.
17.6. EX8200 Switch

The EX8200 line of modular Ethernet switches is a family of high-performance, highly available platforms for use in high-density 10GbE data centers, campus aggregations and core networks. Juniper Networks EX8200 Ethernet line cards offer a variety of interfaces for supporting highdensity 100 Mbps, Gigabit and 10 Gigabit Ethernet (GbE) deployments. Four versions of the EX8200 Ethernet line cards are available, each of which supports a consistent set of features and capabilities: the EX8200-48T, the EX8200-48F, the EX8200-8XS and the EX8200-40XS. Three of these cards are available in Extra Scale (ES) configurationsthe EX8200-48T-ES, the EX8200-48F-ES and the EX8200-8XS-ESwhich are optimized for large-scale deployments such as large campuses, global data centers, or cloud-based applications.
Version 1.0
70
Ethernet Line Card Specifications

EX820048T/EX820048T-ES Port 48 RJ-45 quantity and type PoE/PoE 0 + ports Port speed 10/100/1000 Mbps EX820048F/EX820048F-ES 48 SFP EX82008XS/EX82008XS-ES 8 SFP+ EX8200-40XS EX8200EX8200-2XS48PL/EX8200 4OP/EX8200-48TL 2XS-4OT 48 RJ-45 40 RJ-45 / 4 SFP /2 SFP+
40 SFP/SFP+
48/12 (48PL only) 10/100/1000 Mbps
40/12 (40P only)
100/1000 Mbps 10 Gbps
1 Gbps/10 Gbps
10/100/1000 Mbps; 100/1000 Mbps; 10 Gbps
18. Connecting and Configuring an EX Series Switch (CLI Procedure)

Set the following parameter values in the console server or PC: Baud Rate9600 Flow ControlNone Data8 ParityNone Stop Bits1 DCD StateDisregard
To connect and configure the switch from the console using the CLI: 1. Connect the console port to a laptop or PC using the RJ-45 to DB-9 serial port adapter. The RJ-45 cable and RJ-45 to DB-9 serial port adapter are supplied with the switch. EX2200, EX3200, or EX4200 switchThe console port is located on the rear panel of the switch. EX4500 switchThe console port is located on the front panel of the switch. EX8200 switchThe console port is located on the Switch Fabric and Routing Engine (SRE) module in slot SRE0 in an EX8208 switch or on the Routing Engine (RE) module in slot RE0 in an EX8216 switch. 2. At the Junos OS shell prompt root%, type ezsetup. 3. Enter the hostname. This is optional. 4. Enter the root password you plan to use for this device. You are prompted to re-enter the root password. Note: The initial login name and password on EX-series switches:
login: root password: <no password>
Version 1.0
71
The device is shipped with no password; simply press the enter key. Note: For security reasons, create a password for the Root ID. 5. Enter yes to enable services like Telnet and SSH. By default, Telnet is not enabled and SSH is enabled. 6. Use the Management Options page to select the management scenario: Configure in-band management. In this scenario you have the following two options: Use the default VLAN. Create a new VLANIf you select this option, you are prompted to specify the VLAN name, VLAN ID, management IP address, and default gateway. Select the ports that must be part of this VLAN. Configure out-of-band management. Specify the IP address and gateway of the management interface. Use this IP address to connect to the switch.
7. Specify the SNMP Read Community, Location, and Contact to configure SNMP parameters. These parameters are optional. 8. Specify the system date and time. Select the time zone from the list. These options are optional. 9. The configured parameters are displayed. Enter yes to commit the configuration. The configuration is committed as the active configuration for the switch. 10.(For EX4500 switches only) Enter the request chassis pic-mode intraconnect operational mode command to set the PIC mode to intraconnect. You can now log in with the CLI or the J-Web interface to continue configuring the switch.
19. QFX Series Switch - QFX3500 Switch Overview

The Juniper Networks QFX3500 Switch is a high-speed, multipurpose switch especially designed for nextgeneration data centers that provides a total switching capacity and throughput of 640 Gbps. 48 10-Gbps access ports in the switch use small form-factor pluggable plus transceivers (SFP+) and operate by default as 10-Gigabit Ethernet interfaces. Optionally, you can choose to configure up to 12 of the ports as 2-Gbps, 4-Gbps, or 8-Gbps Fibre Channel (FC) interfaces, and up to 36 of the ports as 1-Gigabit Ethernet interfaces. 4 40-Gbps uplink ports in the switch use quad, small form-factor pluggable plus (QSFP+) transceivers. SFP+ Access Ports The QFX3500 switch has 48 access ports (0-47) that support small form-factor pluggable plus (SFP+) and small form-factor pluggable (SFP) transceivers, as well as SFP+ direct attach copper cables, also known as Twinax cables. Up to 48 of the access ports can be used for SFP+ transceivers or SFP+ direct attach copper cables. 10-Gigabit Ethernet SFP+ transceivers and SFP+ direct attach copper cables can be used in any access port. 2-Gbps, 4-Gbps, or 8-Gbps Fibre Channel SFP+ transceivers can be used in ports 0
Copyright 2002 - 2011 CertExams.com 72
Version 1.0
through 5 and ports 42 through 47. Up to 36 of the access ports can be used for SFP transceivers. Gigabit Ethernet SFP transceivers can be used in ports 6 - 41.
QSFP+ Uplink Ports The QFX3500 switch has four uplink ports (Q0-Q3) that support up to four 40-Gbps quad small form-factor pluggable plus (QSFP+) transceivers.
Note: Please refer to the below network diagram for the switch exercises given in the next sections.
20. Basic Switch Labs 20.1 : Lab Exercise 1 : Entering configuration mode on a switch and exit
Description: A basic exercise that shows how to enter configuration mode and exit from the same. Choose SW1 from the network diagram and exit. Instructions 1. Enter into configuration mode
2. Get back to the operational mode user@SW1>configure [edit] user@SW1#exit user@SW1> Back
20.2 : Lab Exercise 2 : Setting Hostname

Description: Set the switch hostname as junipersw. Choose SW1 from the network diagram. Instructions 1. Enter into configuration mode 2. Set hostname as junipersw user@SW1>configure [edit] user@SW1#edit system [edit system] user@SW1#set host-name junipersw [edit system] user@junipersw#exit [edit] user@junipersw#exit Back
20.3 : Lab Exercise 3 : 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 ge-0/0/0 as "interface-ge-0/0/0" user@SW1>configure [edit] user@SW1#edit interfaces ge-0/0/0 [edit interfaces ge-0/0/0] user@SW1#set description "interface-ge-0/0/0"
[edit interfaces ge-0/0/0] user@SW1#exit [edit] user@SW1# Back
20.4 : Lab Exercise 4 : Shutdown 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. Enter into interfaces hierarchy mode 2. Shutdown the interface ge-0/0/0 using disable command user@SW1>configure [edit] user@SW1#edit interfaces ge-0/0/0 [edit interfaces ge-0/0/0] user@SW1#set disable [edit interfaces ge-0/0/0] user@SW1#exit [edit] user@SW1#
Back
20.5 : Lab Exercise 5 : Basic CLI commands

Description: This exercise demonstrates various basic show commands available. Instructions 1. Issue show cli command 2. Issue show cli history command 3. Issue show version command user@SW1>show cli user@SW1>show cli history user@SW1>show version Back
Version 1.0
75
20.6 : Lab Exercise 6 : Configure bandwidth on an interface

Description: This exercise demonstrates setting bandwidth on an interface. Instructions 1. Enter into interfaces hierarchy mode 2. Set bandwidth of ge-0/0/0 unit 0 as 100m user@SW1>configure [edit] user@SW1#edit interfaces [edit interfaces] user@SW1#set ge-0/0/0 unit 0 bandwidth 100m Note: 100m sets bandwidth as 100Mbps. Back
20.7 : Lab Exercise 7 : Configuring ether-options on the gigabit ethernet switch interface
Description: This lab exercise demonstrates configuring ether-options like link-mode, speed on a switch interface. Instructions 1. Enter into gigabit ethernet interface mode 2. Set the link-mode to full-duplex 3. Set the interface speed to 10m 4. Verify the configuration using show command user@SW1>configure [edit] user@SW1#edit interfaces ge-0/0/1 [edit interfaces ge-0/0/1] user@SW1#set ether-options link-mode full-duplex [edit interfaces ge-0/0/1] user@SW1#set ether-options speed 10m [edit interfaces ge-0/0/1] user@SW1#exit [edit] user@SW1#commit [edit] SW1#show Back
20.8 : Lab Exercise 8 : Configuring the management IP address on EX series switch

Description: This exercise demonstrates configuring management IP address on a EX-Series Switch. Instructions 1. Enter into interfaces hierarchy mode 2. Set the management interface i.e, me0 address as 10.93.15.246/21 3. Verify using show command user@SW1>configure [edit] user@SW1#edit interfaces [edit interfaces] user@SW1#set me0 unit 0 family inet address 10.93.15.246/21 [edit interfaces] user@SW1#exit [edit] user@SW1#commit [edit] user@SW1#show Note: The EX-series switch management interface is a physical or virtual port through which the switch can be configured and maintained. The JUNOS for EX-series software automatically creates the switch's management Ethernet interface, me0. The management Ethernet interface provides an out-of-band method for connecting to the switch. To use me0 as a management port, you must configure its logical port, me0.0, with a valid IP address. Back
21. Lab Exercises on VLAN 21.1 : Lab Exercise 1 : DefineVLANs

Description: This exercise demonstrates the commands required to create VLANs on the switch. Instructions 1. Create VLAN 10 and 20 by using the command syntax set vlans <vlan-name> vlan-id <vlanid-number> 2. Verify the same using show vlans command
Version 1.0
77
user@SW1>configure [edit] user@SW1#set vlans marketing vlan-id 10 [edit] user@SW1#set vlans support vlan-id 20 [edit] user@SW1#commit [edit] user@SW1#exit user@SW1>show vlans Back
21.2 : Lab Exercise 2 : Configure a port for membership in that VLAN

Description: This exercise demonstrates the commands required to configure a port as a member of the VLAN. Instructions 1. Create VLAN by configuring the VLAN 2. Configure the interface port to be a member of the created VLAN 3. Verify using show command user@SW1>configure [edit] user@SW1#set vlans marketing vlan-id 10 [edit] user@SW1#set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members marketing [edit] user@SW1#commit [edit] user@SW1#exit user@SW1>show vlans
Back
21.3 : Lab Exercise 3 : Configuring an interface as a trunk port

Description: This exercise demonstrates the commands required to configure a port as trunk.
Version 1.0
78
Instructions 1. Create VLAN by configuring the VLAN 2. Configure the interface to be a part of the created VLAN 3. Set the appropriate port as trunk port. Note that the port is access port by default. user@SW1>configure [edit] user@SW1#set vlans production vlan-id 20 [edit] user@SW1#set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members production [edit] user@SW1#set interface ge-0/0/1 unit 0 family ethernet-switching port-mode trunk [edit] Back
21.4 : Lab Exercise 4 : Configuring VLANs on EX series switch

Description: This exercise demonstrates VLAN configuration commands on EX-Series switches in general. EX-series switches use VLANs to make logical groupings of network nodes with their own broadcast domains. For each endpoint on the VLAN, configure the VLAN parameters on the corresponding interface. Instructions 1. Configure the VLAN tag ID with vlan-name as sales 2. Specify the maximum time that an entry can remain in the forwarding table before it ages out 3. Configure the port ge-0/0/0 to be a member of the VLAN sales 4. Create the subnet for the VLAN 5. Commit the configuration before verifying using show configuration command. user@SW1>configure [edit] user@SW1#edit vlans [edit vlans] user@SW1#set sales vlan-id 2 [edit vlans] user@SW1#set sales mac-table-aging-time 500 [edit vlans] user@SW1#exit [edit] user@SW1#edit interfaces ge-0/0/0 unit 0 [edit interfaces ge-0/0/0 unit 0] user@SW1#set family ethernet-switching vlan members sales [edit interfaces ge-0/0/0 unit 0] user@SW1#exit
[edit] user@SW1#set interfaces vlan unit 2 family inet address 192.168.2.1/24 [edit interfaces] user@SW1#commit [edit] user@SW1#exit user@SW1>show configuration Back
21.5 : Lab Exercise 5 : Configuring Routed VLAN interface (Inter-VLAN routing) on a switch
Description: This exercise explains the commands required to route traffic between two VLANs on the same switch.
Instructions 1. Create the management and finance department VLANs by configuring the VLAN IDs for them 2. Configure the interface for the management server in the management VLAN 3. Configure the interface for the management access point in the management VLAN 4. Configure the interface for the finance server in the finance VLAN 5. Configure the interface for the finance access point in the finance VLAN 6. Create the interface named vlan with a logical unit in the management broadcast domain (management VLAN) 7. Add a logical unit in the finance broadcast domain (finance VLAN) to the vlan interface
8. Complete the RVI configuration by binding the management and finance VLANs (Layer 2) with the appropriate logical units of the vlan interface (Layer 3) 9. Verify using show commands 1. Create the VLAN by assigning it a name and a VLAN ID: user@SW1>configure [edit] user@SW1#edit vlans [edit vlans] user@SW1#set management vlan-id 10 [edit vlans] user@SW1#set finance vlan-id 20 [edit vlans] user@SW1#exit [edit] 2. Assign an interface to the VLAN by specifying the logical interface (with the unit statement) and specifying the VLAN name as the member: user@SW1#edit interfaces ge-0/0/2 unit 0 [edit interfaces ge-0/0/2 unit 0] user@SW1#set description Managementdepartmentport [edit interfaces ge-0/0/2 unit 0] user@SW1#set family ethernet-switching vlan members management [edit interfaces ge-0/0/2 unit 0] user@SW1#exit user@SW1#edit interfaces ge-0/0/4 unit 0 [edit interfaces ge-0/0/4 unit 0] user@SW1#set description Managementaccesspointport [edit interfaces ge-0/0/4 unit 0] user@SW1#set family ethernet-switching vlan members management [edit interfaces ge-0/0/4 unit 0] user@SW1#exit user@SW1#edit interfaces ge-0/0/6 unit 0 [edit interfaces ge-0/0/6 unit 0] user@SW1#set description financedepartmentport [edit interfaces ge-0/0/6 unit 0] user@SW1#set family ethernet-switching vlan members finance [edit interfaces ge-0/0/6 unit 0] user@SW1#exit user@SW1#edit interfaces ge-0/0/8 unit 0 [edit interfaces ge-0/0/8 unit 0] user@SW1#set description financeaccesspointport [edit interfaces ge-0/0/8 unit 0] user@SW1#set family ethernet-switching vlan members finance [edit interfaces ge-0/0/8 unit 0]
user@SW1#exit 3. Create the subnet for the VLANs broadcast domain [edit] user@SW1#set interfaces vlan unit 10 family inet address 192.168.1.1/24 [edit] user@SW1#set interfaces vlan unit 20 family inet address 192.168.2.1/24 [edit] user@SW1#commit [edit]
4. Layer 3 interfaces on trunk ports allow the interface to transfer traffic between multiple VLANs. Within a VLAN, traffic is bridged, while across VLANs, traffic is routed. Bind a Layer 3 interface with the VLAN user@SW1#edit vlans [edit vlans] user@SW1#set management l3-interface vlan.10 [edit vlans] user@SW1#set finance l3-interface vlan.20 [edit vlans] user@SW1#exit [edit] user@SW1#commit [edit] user@SW1#exit user@SW1>show configuration user@SW1>show vlans Back

1. Which of the following is true of a Switch? A. Switches forward packets based on IP address. B. Switches forward packets based on MAC address. C. Switches forward packets based on IPX address. D. Switches forward packets based on Layer 3 protocol. 2. Which is true regarding VLANs? A. VLAN technology uses VLAN switches (layer 2) which is a substitute for
routing technology which uses routers. B. A VLAN has same collision domain C. A VLAN has same broadcast domain D. VLANs are less secure with respect to simple switch or Hub networks. 3. Refer to the figure below, hosts on the same VLAN can communicate with each other but are unable to communicate with hosts on different VLANs. What is needed to allow communication between VLANs?
A. a switch with a trunk link that is configured between the switches B. a router with an IP address on the physical interface that is connected to the switch C. a switch with an access link that is configured between the switches D. an l3 interface binding the vlans
Version 1.0
83
22. Lab Exercises on Spanning tree protocol and VSTP
22.1 : Lab Exercise 1 : Configuring STP Timers

Description: This lab exercise demonstrates configuring spanning-tree protocol timers. Instructions: 1. Enter into configuration mode on SW1 2. Use the command set stp hello-time/forward-time/max-age <value> to configure the various STP timers on the switch 3. Verify the configuration using show configuration command. user@SW1>configure [edit] user@SW1#edit protocols [edit protocols] user@SW1#set stp forward-delay 20 [edit protocols] user@SW1#set stp hello-time 5 [edit protocols] user@SW1#set stp max-age 30 [edit protocols]
user@SW1#exit [edit] user@SW1#commit [edit] user@SW1#exit user@SW1>show configuration Note: i. Hello-Time: Determines how often the switch broadcasts hello messages to other switches. ii. Forward-Time: Determines how long each of the listening and learning states last before the interface begins forwarding. iii. Max-Age: Determines the amount of time the switch stores protocol information received on an interface. Back
22.2 : Lab Exercise 2 : Setting bridge priority on switch

Description: This exercise demonstrates the command required to configure switch priority of a VLAN. Instructions: 1. Enter into configuration mode on SW1 2. Issue the command "bridge-priority <priority-value> to configure the switch priority of a VLAN. user@SW1>show spanning-tree interface user@SW1>configure [edit] user@SW1#edit protocols [edit protocols] user@SW1#set stp bridge-priority 12288 [edit protocols] user@SW1#exit [edit] user@SW1#exit Note: The switch priority can be configured thus making it more likely to be chosen as the root switch. Priority range is 0 to 61440 in increments of 4096, default is 32768. Back
22.3 : Lab Exercise 3 : Configuring port priority

Description: This lab exercise demonstrates configuring port-priority for an interface on a
switch. Instructions: 1. Enter into interface configuration mode on SW1 2. Issue the command "priority <priority-value> to configure port-priority on the specified interface and verify using show command. user@SW1>configure user@SW1#edit protocols stp interface ge-0/0/0 [edit protocols stp interface ge-0/0/0] user@SW1#set priority 160 [edit protocols stp interface ge-0/0/0] user@SW1#exit [edit] user@SW1#commit [edit] user@SW1#exit user@SW1>show configuration Note: Port-Priority can be between 0 and 240 in the increments of 16, default is 128, the lower the number, higher is the priority. Back
22.4 : Lab Exercise 4 : Verifying STP

Description: This lab exercise demonstrates the various show commands to verify spanning-tree protocol. Instructions: 1. Enter into configuration mode and commit on any one of the switch for the spanning tree protocol algorithm to be saved on the switches. 2. Issue show commands to verify spanning tree protocol: To display the configured or calculated interface-level STP parameters. show spanning-tree interfaceDisplay brief STP interface information. brief | detail Display the specified level of output. user@SW1>configure [edit] user@SW1#commit [edit] user@SW1#exit
Version 1.0
86
user@SW1>show spanning-tree interface user@SW1>show spanning-tree interface detail user@SW2>show spanning-tree interface user@SW2>show spanning-tree interface detail user@SW3>show spanning-tree interface user@SW3>show spanning-tree interface detail Back
22.5 : Lab Exercise 5 : Enabling VSTP on all VLANs

Description: This lab exercise demonstrates the command required to enable VSTP on all VLANs. Instructions 1. Enter into edit protocols hierarchy to enable VLAN Spanning Tree Protocol 2. Issue command set vstp <all> to enable VSTP on all VLANs user@SW1>configure user@SW1#edit protocols [edit protocols] user@SW1#set vstp vlan all hello-time 5 Note: Make sure that VLANs are created before VSTP is enabled on a switch. Back
22.6 : Lab Exercise 6 : Enabling VSTP on a VLAN using a single VLANID / VLAN-Name
Description: This lab exercise demonstrates the command required to enable VSTP on a VLAN using single VLAN-ID. Instructions 1. Enter into edit protocols hierarchy to enable VLAN Spanning Tree Protocol 2. Issue command set vstp vlan <vlan-id-number> to enable VSTP on the specified VLAN or set vstp vlan <vlan-name> user@SW1>configure user@SW1#edit protocols [edit protocols] user@SW1#set vstp vlan 4 bridge-priority 4096 OR
user@SW1#set vstp vlan support bridge-priority 4096 Note: Make sure that VLANs are created before VSTP is enabled on a switch. Back

1. Which is the default spanning-tree protocol that runs on juniper switches? A. VLAN Spanning Tree protocol B. Rapid Spanning Tree Protocol C. Multiple Spanning Tree protocol D. Spanning Tree Protocol 2. Which of the following switches becomes the Root Bridge, given the details in the below table Switch Name SW1 SW2 SW3 SW4 Bridge Priority 32768 32768 32768 32768 MAC Address 00d0-1034-26a0 00d0-1034-27a0 00d0-1034-26a1 00d0-1034-28a0 Port Costs All are 19 All are 4 All are 19 All are 19
A. SW4 B. SW2 C. SW3 D. SW1 3. What is the maximum number of Root ports that a bridge can have ? A. Unlimited B. 2 C. 1 D. Not necessary 4. What happens to a port that is neither a Root port nor a Designated port? A. It is disabled B. It can be used to send/receive frames C. It is put into blocking state D. It will be put into listening mode
Version 1.0
88
5. Which is the designated port on segment SW1-->SW2. Refer to the exhibit below
A. Port 1 on SW1 B. Port 2 on SW1 C. Port 1 on SW2 D. Port 2 on SW2 6. Which is the designated port on the segment SW2-->SW3. Refer to the exhibit below?
Version 1.0
89
A. Port 1 on SW2 B. Port 2 on SW2 C. Port 1 on SW3 D. Port 2 on SW3
23. Lab Exercises on PoE 23.1: Lab Exercise 1 : Configuring guard-band and maximum power on PoE enabled interface
Description: This exercise demonstrates the commands required to configure parameters like guard-band and max power on a PoE enabled interface. Instructions 1. Enter into PoE hierarchy mode on SW2 that has PoE enabled ports. 2. Guard-band syntax is Set guard-band <watts>. Range to be set is 0 through 19 where default value is 0 3. Maximum power syntax is Set interface (all | interface-name) maximum-power <watts>. Range to be set is 0.0 through 18.6 for EX3200 and EX4200 switches and 0.0 through 30.0 for EX2200 switches and Default is: 15.4 for EX3200 and EX4200 switches and 30.0 for EX2200 switches 4. Verify using show poe interface command that display status of all PoE ports on the switch. user@SW2>configure
[edit] user@SW2#edit poe [edit poe] user@SW2#set guard-band 12 [edit poe] user@SW2#set interface ge-0/0/0 maximum-power 18.6 [edit poe] user@SW2#exit [edit] user@SW2#commit [edit] user@SW2#show user@SW2#exit user@SW2>show poe interface Note: Guard-band: Reserve a specified amount of power out of the PoE power budget in case of a spike in PoE consumption. Maximum-Power: Set the maximum amount of power that the switch can supply to the PoE port. Back
23.2 : Lab Exercise 2 : Configuring power management mode on PoE enabled interface
Description: This exercise demonstrates the way that the switch's PoE controller allocates power to the PoE interfaces. Instructions 1. Enter into PoE hierarchy mode on SW2 that has PoE enabled ports. 2. The command syntax is: Set management (class | static) user@SW2>configure [edit] user@SW2#edit poe [edit poe] user@SW2#set management static [edit poe] user@SW2#exit user@SW2>show Note: Default: class
Version 1.0
91
Mode: classThe amount of power allocated to the interface is determined by the class of the connected powered device. If no powered device is connected, no power is allocated to the interface. Mode: staticThe amount of power allocated to the interface is determined by the value of the maximum-power (Interface) statement, not the class of the connected powered device. This amount is allocated even when a powered device is not connected to the interface, ensuring that power is available when needed. Back
23.3 : Lab Exercise 3 : Disabling a PoE interface

Description: This exercise demonstrates disabling a PoE interface, disable the collection of power consumption data for a PoE interface. Instructions 1. Enter into PoE hierarchy mode on SW2 that has PoE enabled ports. 2. The command syntax is: set interface (all | interface-name) disable 3. Verify using show poe interface command user@SW2>configure [edit] user@SW2#edit poe [edit poe] user@SW2#set interface ge-0/0/0 disable [edit poe] user@SW2#exit [edit] user@SW2#commit [edit] user@SW2#exit user@SW2>show poe interface Back
23.4 : Lab Exercise 4 : Setting power priority on all PoE enabled interfaces
Description: This exercise demonstrates the command required to set the power priority value on all PoE enabled interfaces or an individual interface. Instructions:
Version 1.0
92
1. Enter into [edit poe] hierarchy level on SW2 that has PoE enabled ports. 2. The command syntax is set interface (all | interface-name) priority (low|high) 3. Commit the configurations and verify using show command user@SW2>configure [edit] user@SW2#edit poe [edit poe] user@SW2#set interface all priority high [edit poe] user@SW2#set interface ge-0/0/0 priority low [edit poe] user@SW2#exit [edit] user@SW2#commit [edit] user@SW2#show user@SW2#exit user@SW2>show poe interface Note: Set the power priority for individual interfaces when there is insufficient power for all PoE interfaces. If the switch needs to shut down powered devices because PoE demand exceeds the PoE budget, low priority devices are shut down before high priority devices. Among interfaces that have the same assigned priority, priority is determined by port number, with lower-numbered ports having higher priority. Default: low Back
24. FINAL EXAM 24.1 : Objective Test Final Exam : Answer the following questions
1. What is the standard boot sequence for JUNOS? A. PCMCIA flash, compact flash, hard-drive, network B. Compact flash, PCMCIA flash, network, hard-drive C. Hard-Drive, compact flash, network, PCMCIA flash D. PCMCIA flash, compact flash, network, hard-drive 2. What is the name of the 100MB link between the PFE and the RE? A. So0/0 B. Eth0
C. Fxp0 D. Fxp1 3. On a Juniper Router, where is the JUNOS software located? A. EPROM B. Zip drive C. hard drive D. compact flash 4. If the PFE does not have a route to the destination address of a packet, which action will be taken? A. The PFE floods the packet out of all interfaces. B. The PFE drops the packet and sends a destination unreachable notification back to source device. C. The PFE forwards the packet to the routing engine for further processing. D. The PFE queues the packet and sends a request for a layer 3 lookup to the routing engine. 5. Which user authentication methods are available in JUNOS? A. MD5 and SHA B. RADIUS and TACACS only C. Local User Database D. Local user Database, RADIUS, and TACACS+ 6. Which two statements regarding JUNOS architecture are correct? (Choosetwo.) A. The Routing Engine handles all exception traffic. B. The Routing Engine synchronizes the route table with the PFE. C. The Routing Engine is hot-pluggable. D. The Routing Engine controls the PFE. 7. What are two valid initial configuration methods supported on Juniper routers? (Choose two) A. CLI B. J-Web C. JUNOScope D. PCMCIA flash card 8. To troubleshoot interface problems, you can use both the disable command and the deactivate command. Which two statements are correct? A. If the interface is disabled, the logical unit will administratively shutdown. B. If the interface is deactivated, the physical interface will administratively shutdown. C. If the interface is deactivated, the interface configuration is ignored during commit. D. If the interface is disabled, the logical unit configuration is ignored during commit.
9. Which statement is correct about logical units on Juniper Router interfaces? A. Logical units are used only when a Layer 2 identifier is present such as a VLAN. B. A logical unit of 0 is required when using a frame-relay DLCI. C. A logical unit is always required. D. Logical units are not required unless ATM or 802.1Q VLAN tagging is configured. 10. How many IP addresses can be configured in a given interface? A. one primary and one secondary IP address B. one IP address C. as many IP addresses as you want D. one primary and multiple secondary IP addresses 11. Which logical unit number must be configured on an interface using PPP encapsulation? A. unit 0 B. unit 1 C. unit 100 D. unit 255 12. How can you reset your router or switch to factory defaults? A. reset configuration B. load factory-default C. load override default D. set default configuration 13. Which three steps are considered part of the initial configuration? (Choose three.) A. SNMP B. hostname C. root password D. user password E. management access interface 14. Which two media types support asynchronous transfer mode? (Choose two.) A. T3 B. SONET C. Gigabit-Ethernet D. EIA/TIA-232 serial 15. RouterID is set under which of the configuration level? A. [edit protocols] B. [edit router-options] C. [edit system]
D. [edit routing-options] 16. Which method loads the configuration which was active before your last commit? A. load replace last-active B. load rollback 1 C. rollback 1 D. rollback last-active 17. Which command will configure an IP address upon fe-0/0/0.0 from the [edit interfaces fe0/0/0 unit 0] prompt? A. set address 10.45.123.32/30 B. set family inet address 10.45.123.32/30 C. set address family inet 10.45.123.32/30 D. set inet family address 10.45.123.32/30 18. You have just issued the command commit confirmed and your network continues to be operational with no further changes required. You issue a commit and-quit. A short time later, users start complaining about network problems. Which commands (in order) need to be entered to resolve this issue? A. >commit confirmed B. >configure #rollback 1 #commit C. >configure #commit confirmed and-quit D. >configure #confirm and-quit 19. Which command will display the temperature of the Routing Engine's CPU? A. show chassis environment B. show chassis routing-engine C. show chassis temperatures D. show chassis status 20. Which three statements are true of dynamic routing protocols? (Choose three.) A. They are scalable. B. They are Dijkstra based. C. They share network layer reachability information among neighbors. D. They automate next hop decisions.. E. They are tolerant of configuration errors. 21. Which two statements are correct about routing tables in JUNOS? (Choose two.) A. There are separate tables for IPv4 and IPv6 called inet.0 and inet6.0 respectively. B. They only contain the best possible route to each destination.
C. All running protocols can populate the routing tables at the same time. D. Routes with the highest preference value are placed as active routes in the routing table. 22. What are three advantages of dynamic routing protocols over static routing protocols? (Choose three.) A. lower administrative overhead B. increased network availability C. greater network scalability D. easier to implement qualified next hops E. easier ECMP route implement 23. Which two commands are needed to create and apply an export policy that advertises static routes to OSPF neighbors? (Choose two.) A. edit policy-options policy-statement policy-name set term 1 from protocol static set term 1 then accept B. edit ospf policy set from protocol static set 1 then accept C. set protocols OSPF export policy-name D. set protocols OSPF policy policy-name 24. Your routing table contains four static routes which you need to redistribute to your OSPF peers. Which method would accomplish this? A. Apply an import policy to OSPF; this will import the static routes into OSPF. B. Apply an export policy to protocol "static"; this will export the routes to other protocols. C. Apply an import policy to the forwarding table; this will import the routes, allowing them to be forwarded to OSPF neighbors. D. Apply an export policy to OSPF; this will export the static routes to your OSPF neighbors. 25. You have used ping command to see whether the remote router is working. You have got a response "U". What does it mean? A. Successful receipt of echo reply B. Packet experienced Congestion C. Destination Unreachable D. Packet time to live exceeded
Version 1.0
97
25. Appendix 25.1. Answer keys for objective test 1

1. C, D 2. C 3. A 4. D 5. D 6. C 7. D 8. B 9. B 10. C
25.2. Answer keys for objective test 2

1. B 2. D 3. B 4. A 5. D

1. D 2. B
Version 1.0
98
3. A 4. C, D 5. B

1. A 2. D 3. A, D 4. B, D 5. C

1. C 2. C 3. C 4. C 5. A

1. B 2. C 3. D

1. B 2. B 3. C
Version 1.0
99
4. C 5. A 6. B
25.8. Answer keys for final exam

1. A 2. D 3. D 4. B 5. D 6. C, D 7. A, B 8. B, C 9. C 10. C 11. A 12. B 13. B, C, E 14. A, B 15. D 16. C 17. B 18. B 19. B 20. A, C, D 21. A, C
22. A, B, C 23. A, C 24. D 25. C
Disclaimer: CertExams.com is not associated with Juniper Systems Inc or any other company. Junos is a trade mark of Juniper Systems Inc. and duly recognized.
Version 1.0
101

Juniper Lab Manual

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Juniper Lab Manual

Uploaded by

Copyright:

Available Formats

LAB MANUAL FOR JNCIA

Copyright 2002 - 2011 CertExams.com

Copyright 2002 - 2011 CertExams.com

1. About Juniper Routers

2. Classification of Juniper Routers:

2.1 Differences between different series of juniper routers are

Copyright 2002 - 2011 CertExams.com

3. Juniper Routers Architecture

3.1. Routing Engine

3.2. Packet Forwarding Engine

3.3. Routing Engine Hardware Components

Copyright 2002 - 2011 CertExams.com

3.4. Router Boot Methods

4. J-Series Router Overview

Slot numbering for J2350 router

Copyright 2002 - 2011 CertExams.com

4.1. J2320 Router Front Panel and its Components

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

Copyright 2002 - 2011 CertExams.com

Copyright 2002 - 2011 CertExams.com

Color State Blinking Green On steadily Red Blinking

Copyright 2002 - 2011 CertExams.com

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

A 1-port Gigabit Ethernet uPIM is as shown

Copyright 2002 - 2011 CertExams.com

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

Copyright 2002 - 2011 CertExams.com

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

5. M-Series Routers Overview

5.1 M7i Front Panel and its Components

5.2 M7i Rear Panel

6. JUNOS Command Line Interface

7.1. Permanent Interfaces:

7.2. Transient Interfaces:

8. Interface Representation 8.1. On J-Series routers

8.2. On M-Series routers 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

user@R1>configure [edit] user@R1#exit user@R1> Back

9.2 :Lab Exercise 2 : Setting Host Name

9.3 : Lab Exercise 3 : Setting Routers Domain Name

Copyright 2002 - 2011 CertExams.com

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

Copyright 2002 - 2011 CertExams.com

9.7 : Lab Exercise 7 : Router Interface Address Configuration

Copyright 2002 - 2011 CertExams.com

9.8 : Lab Exercise 8 : Shut down an Interface

9.9 : Lab Exercise 9 : Set Interface Description

9.10 : Lab Exercise 10 : Configuring the 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 the Management Ethernet interface (fxp0)

9.14 : Lab Exercise 14 : Setting Bandwidth on an interface

Copyright 2002 - 2011 CertExams.com

9.16 : Lab Exercise 16 : Configuring 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