Jncia Lab Guide

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 18

JNCIA Lab Manual

Developed by
Mr. Khiem Bui Mr. Han Nguyen Ms. Loc Nguyen

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Day 3:

ROUTING FUNDAMENTALS
Routing Fundamentals: By completing this lab, you will perform the following tasks: Configure and verify proper operation of network interfaces. Configure and monitor static routing Configure and monitor OSPF.

In this part you will configure the device hostnames, root password, the management network interface details including definition of specific services allowed for accessing the device. + Configure root password on every device with the value of labmentor123. + Based on the topology diagram configure the management and loopback interfaces on each device with the IP address as listed in the table below: Device R1 R2 Management IP 192.168.1.10/24 10.1.42.10/24 Loopback IP 192.168.1.100/24 10.1.42.100/24 WAN address 15.0.0.1/24 15.0.0.2/24

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

+ The management interface on each device needs to be used purely only for management access and wont accept any transit traffic. In addition this interface will accept only specific services as defined in the table below Device R1 (SRX) R2 (SRX) Hostname ssh with allowed root access, telnet, http, https ssh with allowed root access, telnet, http, https

Login as user root with the password labmentor123:

Issue the show route command to display the contents of the route table: root@R1> show route root@R1> show route all

Issue the show interfaces terse command to verify the current state of the recently configured interfaces: root@R1> show interfaces terse

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

This case we will changes Fe_0/0/0 = em0, Se_0/0/2 = em1. Enter configuration mode and navigate to the [ edit interfaces ] hierarchy level: root@R1> configure root@R1# edit interfaces root@R1# set lo0 unit 0 family inet address 192.168.1.100/24 root@R1# set em0 unit 0 family inet address 192.168.1.10/24 root@R1# set em1 unit 0 family inet address 15.0.0.1/24 root@R1# commit

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Issue the show interfaces terse command to verify the current state of the recently configured interfaces: root@R1# run show interfaces terse

The configured interfaces should all show Admin and Link states of up, as show in the previous output. If the configured interfaces are in the down state, contact your instructor (Khiem Bui).

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Issue the show route command to view the current route entries: root@R1# run show route

Note:

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Now We use the ping utility to verify reachability to the neighboring devices connect to your device: root@R2# run ping 192.168.1.10

What does the result from the ping? -

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Configure the Static route on the Router R1: root@R1# set routing-option static route 10.1.42.0/24 next-hop 15.0.0.2 roo@R1# commit

Configure the Static route on the Router R2: root@R2# set routing-option static route 192.168.1.0/24 next-hop 15.0.0.1 roo@R2# commit

Verifying command: root@R1# run ping 10.1.42.100

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

root@R1# run show route

root@R1# run show route protocol static

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

root@R1# run show configuration root@R1# run show interfaces terse

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Configure and monitor OSPF

In this part, you will configure and monitor OSPF. You will configure a single OSPF area based on the network diagram for this lab. Finally, you will perform some verification tasks to that OSPF work properly. In this part you will configure the device hostnames, root password, the management network interface details including definition of specific services allowed for accessing the device. + Configure root password on every device with the value of labmentor123. + Based on the topology diagram configure the management and loopback interfaces on each device with the IP address as listed in the table below: Device R1 R2 Management IP 192.168.1.10/24 10.1.42.10/24 Loopback IP 192.168.1.100/24 10.1.42.100/24 WAN address 15.0.0.1/24 15.0.0.2/24

This case we will changes Fe_0/0/0 = em0, Se_0/0/2 = em1.

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Enter configuration mode and navigate to the [edit protocols ospf] hierarchy level: root@R1> configure root@R1# edit protocols ospf

Define OSPF area 0 and include all internal interfaces that connect to the remote teams device and the directly connected virtual router: root@R1# set area 0 interface em0 root@R1# set area 0 interface em1 root@R1# set area 0 interface lo0 root@R1# show

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

root@R2# set area 0 interface em0 root@R2# set area 0 interface em1 root@R2# set area 0 interface lo0 root@R2# show

Activate the candidate configuration using the commit command: root@R1# commit

Issue the run show ospf neighbor command to veriry OSPF neighbor adjacency state information: root@R1# run show ospf neighbor

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

root@R2# run show ospf neighbor

If you do not see this state after several minutes, check with the remote team and with your instructor, if need. Good luck Issue the run show route protocols ospf to view the active OSPF routes in your devices route table: root@R1# run show route protocols ospf

root@R2# run show route protocols ospf

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Delete all static routes used for internal connectivity: root@R2# top edit routing-options root@R2# show

root@R2# delete static route 192.168.1.0/24 root@R2# show root@R2# commit and-quit

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Now, activate the configuration and return to operational mode. Issue the show route protocol ospf command to verify that the OSPF routes are now active:

Ping all internal devices to verify reachability through the OSPF router:

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

Do the ping tests succeed? -

http: // w w w . L a b M e n t o r . o r g

LABMENTOR

You might also like