COMISIÓN PERMANENTE Nº 1

In this lab part, you configure and monitor VRRP. You should refer to the diagram for this lab part for topological details. Note that the lab diagram used for this lab part is

Step 3.1

Navigate to the [edit interfaces ge-0/0/4] hierarchy and define two new logical interfaces using the details provided on the network diagram for this lab part. Step 3.2

Activate the configuration change and ensure that you can ping the remote student device and the virtual routers. Note that each of the defined subnets has an

assigned virtual router.

Question: Can you ping the remote student device and virtual routers?

Step 3.3

Configure VRRP on the newly defined logical interfaces. Associate the new logical interface with the lower VLAN-ID with vrrp-group 1z and the new logical interface with the higher VLAN-ID with vrrp-group 2z. Refer to the network diagram associated with this lab part for all interface and VRRP configuration variables for your assigned pod and device.

Question: Based on the newly defined VRRP configuration, which VRRP state should each participating interface assume?

Step 3.4

Activate the configuration changes using the commit command then issue the run

show vrrp command to determine the current VRRP state for each VRRP group.

Question: Which VRRP state has each participating interface assumed within its respective VRRP group?

Note

Before proceeding, ensure that the remote student team in your pod finishes the previous step.

Step 3.5

Open a separate Telnet session to the virtual router.

Step 3.6

Log in to the virtual router attached to your team’s device using the login information shown in the following table:

Step 3.7

From the virtual routers associated with your pod, ping the Internet host listed on the network diagram. Note that each virtual router used in this lab part has a default static route with the virtual IP (VIP) address associated with each respective subnet as the gateway address.

Virtual Router Login Details Student Device Username Password

srxA-1 a1 lab123 srxA-2 a2 lab123 srxB-1 b1 lab123 srxB-2 b2 lab123 srxC-1 c1 lab123 srxC-2 c2 lab123 srxD-1 d1 lab123 srxD-2 d2 lab123

Question: Do the ping operations succeed?

Step 3.8

From the virtual routers associated with your pod, ping the gateway address for each virtual router’s respective subnet.

Question: Do the ping operations succeed? If not, explain why not.

Step 3.9

Return to your assigned student device and enable the accept-data

configuration option for both VRRP groups. Activate the configuration changes using the commit command.

Step 3.10

From the virtual routers associated with your pod, ping the gateway address for each virtual router’s respective subnet once again.

Note Note

Remember to reference the appropriate instance name when sourcing ICMP traffic from a virtual router. The instance names match the virtual router names listed on the network diagram for this lab.

Note

Remember to reference the appropriate instance name when sourcing ICMP traffic from a virtual router. The instance names match the virtual router names listed on the network diagram for this lab.

Remember to reference the appropriate instance name when sourcing ICMP traffic from a virtual router. The instance names match the virtual router names listed on

Question: Do the ping operations now succeed?

Step 3.11

Return to the console session opened for your assigned student device. Enable the interface tracking option for the VRRP group for which your device is currently functioning as master VRRP router. Track the ge-0/0/3.0 interface and reduce the priority value by 101 if the tracked interface goes down. Activate the configuration change and return to the root of the configuration hierarchy.

Step 3.12

Disable the ge-0/0/3.0 interface and activate the change using the commit command.

Step 3.13

Issue the run show vrrp track command to view the current interface tracking details.

Question: According to the output, what is the current interface state of the tracked interface? Also, what is the current VRRP state and priority value for the associated VRRP group?

Step 3.14

Re-enable the ge-0/0/3.0 interface and activate the change by using the commit command.

Step 3.15

Verify the current status of the tracked interface and its associated VRRP group by issuing the run show vrrp track command.

Note

If you are assigned srxX-1, you should enable interface tracking only for

vrrp-group 1z. If you are assigned srxX-2, you should enable interface tracking only for vrrp-group 2z. Refer to the network diagram for this lab part for the z values.

Question: What is the current status of the tracked interface? Which VRRP state and priority value are now assigned to the VRRP interface?

Step 3.16

Reload the reset configuration by issuing the load override /var/tmp/

reset.conf command. Activate the reset configuration and return to operational

mode using the commit and-quit command. Log out of all open sessions.

Lab 7

IPv6 (Optional)

Overview

This lab demonstrates configuration and monitoring of IP version 6 (IPv6) interfaces on devices running the Junos operating system. In this lab, you use the command-line interface (CLI) to configure and monitor interfaces, static routing, basic OSPF, and generic routing encapsulation (GRE) tunnels.

The lab is available in two formats: a high-level format designed to make you think through each step and a detailed format that offers step-by-step instructions complete with sample output from most commands.

By completing this lab, you will perform the following tasks:

• Configure and verify proper operation of IPv6 network interfaces. • Configure and monitor static IPv6 routing.

• Configure and monitor OSPF with IPv6 interfaces.

• Configure a GRE interface to tunnel IPv6 traffic over an IP version 4 (IPv4) network.