Sunteți pe pagina 1din 216

Data Center Switching

13.a

Lab Guide

Worldwide Education Services

1133 Innovation Way


Sunnyvale, CA 94089
USA
408-745-2000
www.juniper.net

Course Number: EDU-JUN-DCX


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

Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.
YEAR 2000 NOTICE
Juniper Networks hardware and software products do not suffer from Year 2000 problems and hence are Year 2000 compliant. The Junos operating system has no known
time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
SOFTWARE LICENSE
The terms and conditions for using Juniper Networks software are described in the software license provided with the software, or to the extent applicable, in an agreement
executed between you and Juniper Networks, or Juniper Networks agent. By using Juniper Networks software, you indicate that you understand and agree to be bound by its
license terms and conditions. Generally speaking, the software license restricts the manner in which you are permitted to use the Juniper Networks software, may contain
prohibitions against certain uses, and may state conditions under which the license is automatically terminated. You should consult the software license for further details.
Contents
Lab 1: Zero Touch Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Part 1: Logging In Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Part 2: Downgrading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Part 3: Verifying Services and DHCP Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-14
Part 4: Performing and Monitoring ZTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-21

Lab 2: In-Service Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1


Part 1: Logging In Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Part 2: Downgrading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Part 3: Verifying Environmental Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Part 4: Performing an In-Service Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Lab 3: Multichassis Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1


Part 1: Logging In Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Part 2: Configuring Multichassis Link Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Part 3: Enabling Layer 3 Gateway Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25

Lab 4: Mixed Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1


Part 1: Analyze the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Part 2: Logging In Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Part 3: Configuring the Master RE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19
Part 4: Adding Members to the Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-23
Part 5: Activating the Members of the Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-30
Part 6: Configuring the Mixed Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-33
Part 7: Resetting the Members the Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-35

Lab 5: Virtual Chassis Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1


Part 1: Analyze the Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Part 2: Logging In Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Part 3: Configuring the Master RE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19
Part 4: Adding Members to the VCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-24
Part 5: Configuring the VCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32
Part 6: Managing a VCF Using Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-35
Part 7: Resetting the Members of the VCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-50

www.juniper.net Contents • iii


iv • Contents www.juniper.net
Course Overview

This two-day course is designed to introduce the features introduced by the QFX5100 and EX4300 Series Ethernet
Switches including, but not limited to, zero touch provisioning (ZTP), unified in-service software upgrade (ISSU),
multichassis link aggregation (MC-LAG), mixed Virtual Fabric, and Virtual Chassis Fabric (VCF). Students will learn to
configure and monitor these features that exist on the Junos operating system running on the QFX5100 and
EX4300 Series platform.
Through demonstrations and hands-on labs, students will gain experience configuring, monitoring, and analyzing the
above features of the Junos OS. This course is based on Junos OS Release 13.2X51-D21.1.
Objectives
After successfully completing this course:
• Identify current challenges in today’s data center environments and explain how the QFX5100 system
solves some of those challenges.
• List the various models of QFX5100 Series switches.
• List some data center architecture options.
• Explain the purpose and value of ZTP.
• Describe the components and operations of ZTP.
• Deploy a QFX5100 Series switch using ZTP.
• Explain the purpose and value of ISSU.
• Describe the components and operations of ISSU.
• Upgrade a QFX5100 Series switch using ISSU.
• Explain the purpose and value of MC-LAG.
• Describe the components and operations of MC-LAG.
• Implement an MC-LAG on QFX5100 Series Switches.
• Describe key concepts and components of a mixed Virtual Chassis.
• Explain the operational details of a mixed Virtual Chassis.
• Implement a mixed Virtual Chassis and verify its operations.
• Describe key concepts and components of a Virtual Chassis Fabric.
• Describe the control plane and forwarding plane of a Virtual Chassis Fabric.
• Describe how to use the CLI to configure and monitor a Virtual Chassis Fabric.
• Describe how to provision a Virtual Chassis Fabric using nonprovisioning, preprovisioning, and
autoprovisioning.
• Describe the software requirements and upgrade procedure of Virtual Chassis Fabric.
• Describe how to manage a Virtual Chassis Fabric with Junos Space.
Intended Audience
This course benefits individuals responsible for configuring and monitoring switching features that exist on the Junos OS
running on the QFX5100 and EX4300 Series platforms, including individuals in professional services, sales and support
organizations, and the end users.
Course Level
Data Center Switching (DCX) is an intermediate-level course.

www.juniper.net Course Overview • v


Prerequisites
The following are the prerequisites for this course:
• Understanding of the OSI model;
• Junos OS configuration experience—the Introduction to the Junos Operating System (IJOS) course or
equivalent;
• Intermediate routing knowledge—the Junos Routing Essentials (JRE) course or equivalent; and
• Intermediate switching knowledge—the Junos Enterprise Switching Using Enhanced Layer 2 Software
(JEX-ELS) course or equivalent.

vi • Course Overview www.juniper.net


Course Agenda

Day 1
Chapter 1: Course Introduction
Chapter 2: System Overview
Chapter 3: Zero Touch Provisioning
Zero Touch Provisioning Lab
Chapter 4: In-Service Software Upgrades
In-Service Software Upgrade Lab
Chapter 5: Multichassis Link Aggregation
Multichassis Link Aggregation Lab
Day 2
Chapter 6: Mixed Virtual Chassis
Answers to Review Questions
Chapter 7: Virtual Chassis Fabric
Chapter 8: Virtual Chassis Fabric Management
Virtual Chassis Fabric Lab

www.juniper.net Course Agenda • vii


Document Conventions

CLI and GUI Text


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

Style Description Usage Example

Franklin Gothic Normal text. Most of what you read in the Lab Guide
and Student Guide.

Courier New Console text:


commit complete
• Screen captures
• Noncommand-related Exiting configuration mode
syntax
GUI text elements:
Select File > Open, and then click
• Menu names Configuration.conf in the
Filename text box.
• Text field entry

Input Text Versus Output Text


You will also frequently see cases where you must enter input text yourself. Often these instances will be shown in the
context of where you must enter them. We use bold style to distinguish text that is input versus text that is simply
displayed.

Style Description Usage Example

Normal CLI No distinguishing variant. Physical interface:fxp0,


Enabled
Normal GUI
View configuration history by clicking
Configuration > History.

CLI Input Text that you must enter. lab@San_Jose> show route
GUI Input Select File > Save, and type
config.ini in the Filename field.

Defined and Undefined Syntax Variables


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

Style Description Usage Example

CLI Variable Text where variable value is already policy my-peers


assigned.
GUI Variable Click my-peers in the dialog.

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

viii • Document Conventions www.juniper.net


Additional Information

Education Services Offerings


You can obtain information on the latest Education Services offerings, course dates, and class locations from the World
Wide Web by pointing your Web browser to: http://www.juniper.net/training/education/.
About This Publication
The Data Center Switching Lab Guide was developed and tested using the Junos OS Release 13.2X51-D21.1. Previous
and later versions of software might behave differently so you should always consult the documentation and release
notes for the version of code you are running before reporting errors.
This document is written and maintained by the Juniper Networks Education Services development team. Please send
questions and suggestions for improvement to training@juniper.net.
Technical Publications
You can print technical manuals and release notes directly from the Internet in a variety of formats:
• Go to http://www.juniper.net/techpubs/.
• Locate the specific software or hardware release and title you need, and choose the format in which you
want to view or print the document.
Documentation sets and CDs are available through your local Juniper Networks sales office or account representative.
Juniper Networks Support
For technical support, contact Juniper Networks at http://www.juniper.net/customers/support/, or at 1-888-314-JTAC
(within the United States) or 408-745-2121 (from outside the United States).

www.juniper.net Additional Information • ix


x • Additional Information www.juniper.net
Lab
Zero Touch Provisioning

Overview
In this lab, you provision QFX5100 Series switches using the zero touch provisioning (ZTP)
process.
By completing this lab, you will perform the following tasks:
• Access your assigned QFX5100 switches.
• Verify communications between your switches and the server.
• Downgrade your QFX5100 switches to an earlier software version.
• Modify DHCP server configuration and ensure services are running.
• Initiate the ZTP process on your QFX5100 switches and monitor its progress.

Part 1: Logging In Using the CLI

In this lab part, you become familiar with the access details used to connect to the lab
equipment. Once you are familiar with the access details, you will use the CLI to log in to your
team’s designated switches. Once you have logged in to your device you will make sure your
devices are running the appropriate starting configurations for this lab.
Step 1.1
Ensure that you know to which switches you have been assigned. Check with your instructor if
you are not certain. Consult the management network diagram to determine your switches’
management addresses.

Question: What are the management addresses assigned to


your switches?

Answer: The answer varies and depends on your assigned


environment and devices. If you are unsure of your assignment,
ask your instructor.

www.juniper.net Zero Touch Provisioning • Lab 1–1


Data Center Switching
Step 1.2
Using console access, connect to your qfx1 switch and log in using the lab and lab123 login
credentials.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1>
Step 1.3
Enter configuration mode and load the lab1-start.config configuration file from the /
var/home/lab/dcx directory. Commit your changes and return to operational mode.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# load override dcx/lab1-start.config
load complete

{master:0}[edit]
lab@qfx1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@qfx1>
Step 1.4
Open a new and separate console session to your qfx2 switch and perform the same steps
previously completed on qfx1 ensuring that the lab1-start.config configuration file is
ultimately loaded on both qfx1 and qfx2.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx2> configure
Entering configuration mode

{master:0}[edit]
lab@qfx2# load override dcx/lab1-start.config
load complete

{master:0}[edit]
lab@qfx2# commit and-quit

Lab 1–2 • Zero Touch Provisioning www.juniper.net


Data Center Switching
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@qfx2>
Step 1.5
On qfx2, issue the show vlans extensive command to determine the current VLAN details
and assignments.
{master:0}
lab@qfx2> show vlans extensive

Routing instance: default-switch


VLAN Name: default State: Active
Tag: 1
Internal index: 2, Generation Index: 2, Origin: Static
MAC aging time: 300 seconds
Layer 3 interface: irb.0
Interfaces:
ge-0/0/0.0*,untagged,access
Number of interfaces: Tagged 0 , Untagged 1
Total MAC count: 2

Question: Does qfx2 currently have any active VLANs? If so,


what are the associated details?

Answer: Your qfx2 switch should have a single active VLAN in


the form of the default VLAN, which uses the VLAN ID or tag
value of 1.

Question: Are any interfaces associated with this VLAN? If so,


which ones?

Answer: As shown in the sample output, there is a single access


port (ge-0/0/0.0) and a Layer 3 interface (irb.0) associated with
this VLAN.

Question: What is the state of ge-0/0/0.0?

Answer: As shown in the sample output, ge-0/0/0.0 should be


active as indicated by the presence of the asterisk (*)). If you
see some other state for this interface, consult with your
instructor before proceeding.

Step 1.6
Issue the show interfaces irb command to view the details associated with the
integrated routing and bridging (IRB) interface.
www.juniper.net Zero Touch Provisioning • Lab 1–3
Data Center Switching
{master:0}
lab@qfx2> show interfaces irb
Physical interface: irb, Enabled, Physical link is Up
Interface index: 640, SNMP ifIndex: 502
Type: Ethernet, Link-level type: Ethernet, MTU: 1514
Device flags : Present Running
Interface flags: SNMP-Traps
Link type : Full-Duplex
Link flags : None
Current address: dc:38:e1:5d:1c:00, Hardware address: dc:38:e1:5d:1c:00
Last flapped : Never
Input packets : 0
Output packets: 0

Logical interface irb.0 (Index 548) (SNMP ifIndex 503)


Flags: SNMP-Traps 0x4004000 Encapsulation: ENET2
Bandwidth: 1000mbps
Routing Instance: default-switch Bridging Domain: default+1
Input packets : 852
Output packets: 256694
Protocol inet, MTU: 1500
Flags: Sendbcast-pkt-to-re, Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 172.25.10/24, Local: 172.25.10.22,
Broadcast: 172.25.10.255

Question: What is the hardware address associated with qfx2’s


IRB interface?

Answer: The answer will vary and is dependent on your assigned


device. In the sample output, the hardware address is
dc:38:e1:5d:1c:00.

Note
Please make sure you document the hardware
address in this step as it will be needed in a
subsequent lab part (Part 3 Step 4).

Question: What IP address is associated irb.0?

Answer: The IP address associated qfx2’s irb.0 should be


172.25.10.22. As indicated on the lab diagram associated with
this lab, this is the assigned IP address for qfx2’s irb.0
regardless of your assigned kit. Please note that this IP address
will change during the ZTP process!

Step 1.7
Issue the ping 172.25.10.1 rapid count 5 command to verify communications and
reachability between qfx2 and the DHCP/FTP server.

Lab 1–4 • Zero Touch Provisioning www.juniper.net


Data Center Switching
{master:0}
lab@qfx2> ping 172.25.10.1 rapid count 5
PING 172.25.10.1 (172.25.10.1): 56 data bytes
!!!!!
--- 172.25.10.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 21.689/21.939/22.252/0.188 ms

Question: Was the ping test successful?

Answer: Yes, as shown in the sample output the ping test


should succeed. If your ping test does not succeed, check your
work and, if needed, consult with your instructor.

Question: For ZTP, why is it important that a clear


communications path exist between the switch and the DHCP
and FTP servers?

Answer: ZTP will not work unless a clear communications path


exists between the switch being provisioned and the DHCP and
FTP servers. As described in the lecture, the switch being
provisioned must be able to acquire an IP address from the
DHCP server and then retrieve its configuration file and
software image from the FTP server based on the defined DHCP
options. We explore the DHCP and FTP server elements in a
subsequent lab part.

Step 1.8
Return to the console session opened to your qfx1 switch.
On your qfx1 switch, issue the show vlans extensive command to determine the current
VLAN details and assignments.
{master:0}
lab@qfx1> show vlans extensive

Routing instance: default-switch


VLAN Name: default State: Active
Tag: 1
Internal index: 2, Generation Index: 2, Origin: Static
MAC aging time: 300 seconds
Layer 3 interface: irb.0
Interfaces:
ge-0/0/0.0*,untagged,access
Number of interfaces: Tagged 0 , Untagged 1
Total MAC count: 2

www.juniper.net Zero Touch Provisioning • Lab 1–5


Data Center Switching
Question: Does qfx1 currently have any active VLANs? If so,
what are the associated details?

Answer: Your qfx1 switch should have a single active VLAN in the
form of the default VLAN, which uses the VLAN ID or tag value of
1.

Question: Are any interfaces associated with this VLAN? If so,


which ones?

Answer: As shown in the sample output, there is a single access


port (ge-0/0/0.0) and a Layer 3 interface (irb.0) associated with
this VLAN.

Question: What is the state of ge-0/0/0.0?

Answer: As shown in the sample output, ge-0/0/0.0 should be


active as indicated by the presence of the asterisk (*)). If you
see some other state for this interface, consult with your
instructor before proceeding.

Step 1.9
Issue the show interfaces irb command to view the details associated with the integrated
routing and bridging (IRB) interface.
{master:0}
lab@qfx1> show interfaces irb
Physical interface: irb, Enabled, Physical link is Up
Interface index: 640, SNMP ifIndex: 502
Type: Ethernet, Link-level type: Ethernet, MTU: 1514
Device flags : Present Running
Interface flags: SNMP-Traps
Link type : Full-Duplex
Link flags : None
Current address: dc:38:e1:5e:48:00, Hardware address: dc:38:e1:5e:48:00
Last flapped : Never
Input packets : 0
Output packets: 0

Logical interface irb.0 (Index 549) (SNMP ifIndex 503)


Flags: SNMP-Traps 0x4004000 Encapsulation: ENET2
Bandwidth: 1000mbps
Routing Instance: default-switch Bridging Domain: default+1
Input packets : 929
Output packets: 256297
Protocol inet, MTU: 1500
Flags: Sendbcast-pkt-to-re, Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary

Lab 1–6 • Zero Touch Provisioning www.juniper.net


Data Center Switching
Destination: 172.25.10/24, Local: 172.25.10.11,
Broadcast: 172.25.10.255

Question: What is the hardware address associated with qfx1’s


IRB interface?

Answer: The answer will vary and is dependent on your


assigned device. In the sample output, the hardware address is
dc:38:e1:5e:48:00.

Note
Please make sure you document the hardware
address in this step as it will be needed in a
subsequent lab part (Part 3 Step 4).

Question: What IP address is associated irb.0?

Answer: The IP address associated qfx1’s irb.0 should be


172.25.10.11. As indicated on the lab diagram associated with
this lab, this is the assigned IP address for qfx1’s irb.0
regardless of your assigned kit. Please note that this IP address
will change during the ZTP process!

Step 1.10
Issue the ping 172.25.10.1 rapid count 5 command to verify communications and
reachability between qfx1 and the DHCP/FTP server.
{master:0}
lab@qfx1> ping 172.25.10.1 rapid count 5
PING 172.25.10.1 (172.25.10.1): 56 data bytes
!!!!!
--- 172.25.10.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 21.733/26.329/44.413/9.043 ms

Question: Was the ping test successful?

Answer: Yes, as shown in the sample output the ping test


should succeed. If your ping test does not succeed, check your
work and, if needed, consult with your instructor.

Note
Do not proceed until you have documented the MAC addresses
assigned to the IRB interfaces on both qfx1 and qfx2 and
confirmed reachability between those switches and the DHCP/FTP
server as illustrated on the diagram associated with this lab.

www.juniper.net Zero Touch Provisioning • Lab 1–7


Data Center Switching

Part 2: Downgrading Software

In this lab part, you downgrade the software on both of your assigned QFX Series switches to an
earlier version in preparation of provisioning them from a zeroized state using ZTP.
Step 2.1
On qfx1, verify the software version running on the system using the show version command.
{master:0}
lab@qfx1> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx1
Model: qfx5100-48s-6q
JUNOS Base OS Software Suite [13.2X51-D21.1]
JUNOS Base OS boot [13.2X51-D21.1]
JUNOS Crypto Software Suite [13.2X51-D21.1]
JUNOS Online Documentation [13.2X51-D21.1]
JUNOS Kernel Software Suite [13.2X51-D21.1]
JUNOS Packet Forwarding Engine Support (qfx-ex-x86-32) [13.2X51-D21.1]
JUNOS Routing Software Suite [13.2X51-D21.1]
JUNOS Enterprise Software Suite [13.2X51-D21.1]
JUNOS py-base-i386 [13.2X51-D21.1]
JUNOS Host Software [13.2X51-D21.1]

Question: Which software version is running on qfx2? Are all


packages running the same version?

Answer: Your qfx1 switch should be running 13.2X51-D21.1. At


this point all packages, including the JUNOS Host Software,
should be running this version.

Step 2.2
Use secure copy to download the 13.2X51-D15.5 Junos OS image from the server (172.25.10.1)
to the /var/tmp directory on qfx1. If prompted for a security authorization, type yes. When
prompted for a password, use lab123.
{master:0}
lab@qfx1> file copy scp://172.25.10.1/home/lab/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz /var/tmp/
The authenticity of host '172.25.10.1 (172.25.10.1)' can't be established.
RSA key fingerprint is 01:f0:61:09:8d:e3:2e:a1:a6:ac:fe:a5:cf:8c:38:3c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.25.10.1' (RSA) to the list of known hosts.
lab@172.25.10.1's password:
jinstall-qfx-5-13.2X51-D15.5-domestic-signed. 100% 395MB 1.4MB/s 04:49

Lab 1–8 • Zero Touch Provisioning www.juniper.net


Data Center Switching
Question: Did the image successfully download?

Answer: Yes, you should see a successful download of the


target image as shown in the sample output.

Step 2.3
Once the 13.2X51-D15.5 Junos OS image has been downloaded to qfx1, use the file
checksum md5 command and ensure the MD5 checksum matches the
bf4d1adc93ca922233aa0024dd7e3c32 value.
{master:0}
lab@qfx1> file checksum md5 /var/tmp/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz
MD5 (/var/tmp/jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz) =
bf4d1adc93ca922233aa0024dd7e3c32

Question: Does the resulting MD5 checksum match the


expected checksum value?

Answer: The checksum value of the file should be


bf4d1adc93ca922233aa0024dd7e3c32. If you see a different
value, check your work and, if needed, download the file again
and work with your instructor as needed.

Step 2.4
Use the request system software add /var/tmp/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz reboot command to
perform a software downgrade to the referenced software version. Once the downgrade is
complete, log in using the lab and lab123 login credentials and verify the software version
using the show version command.
{master:0}
lab@qfx1> request system software add /var/tmp/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz reboot
Verified jinstall-vjunos-13.2X51-D15.5-domestic.tgz signed by
PackageProductionVJunos_13_2_0
Adding vjunos...
Saving contents of boot area prior to installation

WARNING: This package will load JUNOS 13.2X51-D15.5 software.


WARNING: It will save JUNOS configuration files, and SSH keys
WARNING: (if configured), but erase all other files and information
WARNING: stored on this machine. It will attempt to preserve dumps
WARNING: and log files, but this can not be guaranteed. This is the
WARNING: pre-installation stage and all the software is loaded when
WARNING: you reboot the system.

POST-INSTALL...
Saving the config files ...

www.juniper.net Zero Touch Provisioning • Lab 1–9


Data Center Switching
NOTICE: uncommitted changes have been saved in /var/db/config/
juniper.conf.pre-install
Pushing installation package to host...
Extracting jinstall-qfx-5-13.2X51-D15.5-domestic ...
Install jinstall-qfx-5-13.2X51-D15.5-domestic completed
Install jinstall-vjunos completed

WARNING: A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the


WARNING: 'request system reboot' command when software installation is
WARNING: complete. To abort the installation, do not reboot your system,
WARNING: instead use the 'request system software delete jinstall'
WARNING: command as soon as this operation completes.

Saving state for rollback ...


Rebooting ...
shutdown: [pid 75438]
Shutdown NOW!

*** FINAL System shutdown message from root@qfx1 ***

System going down IMMEDIATELY

...TRIMMED...

qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D15.5 built 2014-03-06 10:05:33 UTC


{master:0}
lab@qfx1> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx1
Model: qfx5100-48s-6q
JUNOS Base OS Software Suite [13.2X51-D15.5]
JUNOS Base OS boot [13.2X51-D15.5]
JUNOS Crypto Software Suite [13.2X51-D15.5]
JUNOS Online Documentation [13.2X51-D15.5]
JUNOS Kernel Software Suite [13.2X51-D15.5]
JUNOS Packet Forwarding Engine Support (qfx-x86-32) [13.2X51-D15.5]
JUNOS Routing Software Suite [13.2X51-D15.5]
JUNOS Enterprise Software Suite [13.2X51-D15.5]
JUNOS py-base-i386 [13.2X51-D15.5]
JUNOS Host Software [13.2X51-D21.1]

Lab 1–10 • Zero Touch Provisioning www.juniper.net


Data Center Switching
Question: Which software version is running on qfx1? Are all
packages running the same version?

Answer: Your qfx1 switch should be running 13.2X51-D15.5. At


this point all packages, except the JUNOS Host Software,
should be running this version. When upgrading or downgrading
software on a QFX5100 the Host Software image does not
change unless you use the force-host option. In our case,
we did not use the force-host option so that package
remains untouched.

Note
The JUNOS Host Software package is the underlying host
operating system and is based on centOS. It is through
this host operating system and some key processes that
the virtual Junos OS switch instances are managed. Note
that there should not be any negative consequence of
having this package different from the other packages.

Step 2.5
Move to the console session opened for your qfx2 switch.
On qfx2, verify the software version running on the system using the show version
command.
{master:0}
lab@qfx2> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx2
Model: qfx5100-48s-6q
JUNOS Base OS Software Suite [13.2X51-D21.1]
JUNOS Base OS boot [13.2X51-D21.1]
JUNOS Crypto Software Suite [13.2X51-D21.1]
JUNOS Online Documentation [13.2X51-D21.1]
JUNOS Kernel Software Suite [13.2X51-D21.1]
JUNOS Packet Forwarding Engine Support (qfx-ex-x86-32) [13.2X51-D21.1]
JUNOS Routing Software Suite [13.2X51-D21.1]
JUNOS Enterprise Software Suite [13.2X51-D21.1]
JUNOS py-base-i386 [13.2X51-D21.1]
JUNOS Host Software [13.2X51-D21.1]

Question: Which software version is running on qfx2? Are all


packages running the same version?

Answer: Your qfx2 switch should be running 13.2X51-D21.1. At


this point all packages, including the JUNOS Host Software,
should be running this version.

www.juniper.net Zero Touch Provisioning • Lab 1–11


Data Center Switching
Step 2.6
Use secure copy to download the 13.2X51-D15.5 Junos OS image from the server (172.25.10.1)
to the /var/tmp directory on qfx2. When prompted for a password, use lab123.
{master:0}
lab@qfx2> file copy scp://172.25.10.1/home/lab/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz /var/tmp/
The authenticity of host '172.25.10.1 (172.25.10.1)' can't be established.
RSA key fingerprint is 01:f0:61:09:8d:e3:2e:a1:a6:ac:fe:a5:cf:8c:38:3c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.25.10.1' (RSA) to the list of known hosts.
lab@172.25.10.1's password:
jinstall-qfx-5-13.2X51-D15.5-domestic-signed. 100% 395MB 1.4MB/s 04:49

Question: Did the image successfully download?

Answer: You should see a successful download of the target


image as shown in the sample output.

Step 2.7
Once the 13.2X51-D15.5 Junos OS image has been downloaded to qfx2, use the file
checksum md5 command and ensure the MD5 checksum matches the
bf4d1adc93ca922233aa0024dd7e3c32 value.
{master:0}
lab@qfx2> file checksum md5 /var/tmp/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz
MD5 (/var/tmp/jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz) =
bf4d1adc93ca922233aa0024dd7e3c32

Question: Does the resulting MD5 checksum match the


expected checksum value?

Answer: The checksum value of the file should be


bf4d1adc93ca922233aa0024dd7e3c32. If you see a different
value, check your work and, if needed, download the file again
and work with your instructor as needed.

Step 2.8
Use the request system software add /var/tmp/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz reboot command to
perform a software downgrade to the referenced software version. Once the downgrade is
complete, log in using the lab and lab123 login credentials and verify the software version
using the show version command.
{master:0}
lab@qfx2> request system software add /var/tmp/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz reboot
Verified jinstall-vjunos-13.2X51-D15.5-domestic.tgz signed by
PackageProductionVJunos_13_2_0

Lab 1–12 • Zero Touch Provisioning www.juniper.net


Data Center Switching
Adding vjunos...
Saving contents of boot area prior to installation

WARNING: This package will load JUNOS 13.2X51-D15.5 software.


WARNING: It will save JUNOS configuration files, and SSH keys
WARNING: (if configured), but erase all other files and information
WARNING: stored on this machine. It will attempt to preserve dumps
WARNING: and log files, but this can not be guaranteed. This is the
WARNING: pre-installation stage and all the software is loaded when
WARNING: you reboot the system.

POST-INSTALL...
Saving the config files ...
NOTICE: uncommitted changes have been saved in /var/db/config/
juniper.conf.pre-install
Pushing installation package to host...
Extracting jinstall-qfx-5-13.2X51-D15.5-domestic ...
Install jinstall-qfx-5-13.2X51-D15.5-domestic completed
Install jinstall-vjunos completed

WARNING: A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the


WARNING: 'request system reboot' command when software installation is
WARNING: complete. To abort the installation, do not reboot your system,
WARNING: instead use the 'request system software delete jinstall'
WARNING: command as soon as this operation completes.

Saving state for rollback ...


Rebooting ...
shutdown: [pid 75438]
Shutdown NOW!

*** FINAL System shutdown message from root@qfx1 ***

System going down IMMEDIATELY


...TRIMMED...
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D15.5 built 2014-03-06 10:05:33 UTC


{master:0}
lab@qfx2> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx1
Model: qfx5100-48s-6q
JUNOS Base OS Software Suite [13.2X51-D15.5]
JUNOS Base OS boot [13.2X51-D15.5]
JUNOS Crypto Software Suite [13.2X51-D15.5]
JUNOS Online Documentation [13.2X51-D15.5]
JUNOS Kernel Software Suite [13.2X51-D15.5]
JUNOS Packet Forwarding Engine Support (qfx-x86-32) [13.2X51-D15.5]
JUNOS Routing Software Suite [13.2X51-D15.5]
JUNOS Enterprise Software Suite [13.2X51-D15.5]

www.juniper.net Zero Touch Provisioning • Lab 1–13


Data Center Switching
JUNOS py-base-i386 [13.2X51-D15.5]
JUNOS Host Software [13.2X51-D21.1]

Question: Which software version is running on qfx2? Are all


packages running the same version?

Answer: Your qfx2 switch should be running 13.2X51-D15.5. At


this point all packages, except the JUNOS Host Software, should
be running this version.

Part 3: Verifying Services and DHCP Configuration File

In this lab part, you log in to your designated DHCP/FTP server to perform some verification
tasks. Specifically you will verify that the required services are running on the server and that the
configuration file for the DHCP service is properly configured.
Step 3.1
Open a session to the DHCP/FTP server (172.25.10.1) as directed by your instructor and log in
using the lab and lab123 login credentials.
Note that the access method used may vary between delivery environments!
Welcome to the Juniper Networks Education Services Lab
Rack

Main Menu

1) Connect to a device (telnet/SSH)


2) Connect to a device (console)
3) Start a shell
4) Quit

Select an option: 3

sh-3.2$
Step 3.2
From the shell of your assigned DHCP/FTP server, issue the service dhcpd status
command to determine if the DHCP service is running.
sh-3.2$ service dhcpd status
dhcpd (pid 3105) is running...

Lab 1–14 • Zero Touch Provisioning www.juniper.net


Data Center Switching
Question: Is the DHCP service running? If so, what is its process
identifier (PID)?

Answer: Yes, the DHCP service should be running. The PID


assigned to the DHCP service will vary. If the DHCP service is
not running on your server, attempt to start the service using
the service dhcpd start command.

Note
Make sure the DHCP service is running on
your assigned server before proceeding!

Step 3.3
Issue the cat /etc/dhcpd.conf command to view the DHCP server configuration.
sh-3.2$ cat /etc/dhcpd.conf
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
#

set vendor-string = option vendor-class-identifier;


ddns-update-style none;
default-lease-time 600;
log-facility local7;
max-lease-time 7200;

option option-150 code 150 = ip-address;


subnet 172.25.10.0 netmask 255.255.255.0 {
option routers 172.25.10.1;
option subnet-mask 255.255.255.0;
default-lease-time 21600;
max-lease-time 43200;
range 172.25.10.100 172.25.10.225;

option space SUNW;


option SUNW.server-image code 4 = text;
option SUNW.server-image code 0 = text;
option SUNW.server-file code 1 = text;
option SUNW.image-file-type code 2 = text;
option SUNW.transfer-mode code 3 = text;
option SUNW-encapsulation code 43 = encapsulate SUNW;

host qfx1 {
hardware ethernet aa:bb:aa:bb:aa:00;
fixed-address 172.25.10.111;
option option-150 172.25.10.1;# Define FTP Server Address

www.juniper.net Zero Touch Provisioning • Lab 1–15


Data Center Switching
option SUNW.server-image "/var/ftp/pub/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz";
option SUNW.server-file "/var/ftp/pub/qfx1-ZTP.config";

host qfx2 {
hardware ethernet bb:aa:bb:aa:bb:00;
fixed-address 172.25.10.222;
option option-150 172.25.10.1;# Define FTP Server Address
option SUNW.server-image "/var/ftp/pub/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz";
option SUNW.server-file "/var/ftp/pub/qfx2-ZTP.config";

option SUNW.transfer-mode "ftp";


#option SUNW.image-file-type "symlink";
#option SUNW.server-image "IMAGES/jinstall-qfx-image.tgz";
#option bootfile-name "IMAGES/jinstall-qfx-image.tgz";

#option SUNW.server-file "CONFIG/ZTP_autoConfig-sym";

Question: What is DHCP IP address pool configured on your


server? Are there any static assignments?

Answer: The DHCP configuration should have an IP address pool


defined for the 172.25.10.0/24 subnet with an IP address
range of 172.25.10.100 - 172.25.10.225. Within the defined IP
range, two static assignments are defined; one for qfx1
(172.25.10.111) and one for qfx2 (172.25.10.222).

Question: Do the static assignments in the DHCP configuration


reference the hardware addresses assigned to your switches’
IRB interfaces? Note these are the MAC addresses you logged in
Part 1 of this lab.

Answer: The static assignments in the DHCP configuration do


not currently reference the correct hardware addresses
assigned to your switches’ IRB interfaces. You will correct this in
a subsequent step by modifying the DHCP configuration file.

Question: According to the configuration file, what file transfer


method will be used when transferring the switch configuration
files and software image during the ZTP process?

Answer: According to the configuration file, FTP will be used to


transfer the switch configuration files and the software image
during the ZTP process.

Lab 1–16 • Zero Touch Provisioning www.juniper.net


Data Center Switching
Question: To which software version should your switches be
upgraded during the ZTP process?

Answer: As shown in the configuration file, your switches should


be upgraded to the 13.2X51-D21.1 Junos OS version during the
ZTP process.

Question: According to the configuration file, in which directory


should the configuration files and the software image be
stored?

Answer: According to the configuration file, the configuration


files and the software image should be stored in the /var/ftp/
pub directory.

Step 3.4
Using the details logged in Part 1 (Steps 1.6 and 1.9) of this lab, locate the hardware addresses
assigned to the qfx1 and qfx2 IRB interfaces. Once located, note the hardware addresses in the
following spaces:

IRB Hardware Addresses

qfx1
qfx2

Note
If needed, return to the console opened to qfx1 and qfx2 and
locate the hardware addresses of the IRBs associated with
each switch using the show interfaces irb command.

Step 3.5
Update the hardware addresses in the DHCP configuration file as outlined:
1. Issue the vi /etc/dhcpd.conf command to open the configuration file using the
vi editing utility:
sh-3.2$ vi /etc/dhcpd.conf
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
#

set vendor-string = option vendor-class-identifier;


ddns-update-style none;
default-lease-time 600;
log-facility local7;

www.juniper.net Zero Touch Provisioning • Lab 1–17


Data Center Switching
max-lease-time 7200;

option option-150 code 150 = ip-address;


subnet 172.25.10.0 netmask 255.255.255.0 {
option routers 172.25.10.1;
option subnet-mask 255.255.255.0;
default-lease-time 21600;
max-lease-time 43200;
range 172.25.10.100 172.25.10.225;

option space SUNW;


"/etc/dhcpd.conf" 56L, 1714C

2. Using your arrow keys, navigate to the end of the aa:bb:aa:bb:aa:00 MAC address
referenced in the static mapping definition associated with qfx1.
option space SUNW;
option SUNW.server-image code 4 = text;
option SUNW.server-image code 0 = text;
option SUNW.server-file code 1 = text;
option SUNW.image-file-type code 2 = text;
option SUNW.transfer-mode code 3 = text;
option SUNW-encapsulation code 43 = encapsulate SUNW;

host qfx1 {
hardware ethernet aa:bb:aa:bb:aa:00;<<<<<<< Place Cursor Here
fixed-address 172.25.10.111;
option option-150 172.25.10.1;# Define FTP Server Address
option SUNW.server-image "/var/ftp/pub/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz";
option SUNW.server-file "/var/ftp/pub/qfx1-ZTP.config";

3. Type the letter ‘i’ to start the insert mode in the vi editor utility. Once in insert mode,
press the Delete key as needed to remove the current MAC address. Once the
current MAC address is removed, enter the hardware address associated with the IRB
interface on qfx1.
host qfx1 {
hardware ethernet place:mac:address:here:xx:xx;
fixed-address 172.25.10.111;
option option-150 172.25.10.1;# Define FTP Server Address
option SUNW.server-image "/var/ftp/pub/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz";
option SUNW.server-file "/var/ftp/pub/qfx1-ZTP.config";

-- INSERT --

Lab 1–18 • Zero Touch Provisioning www.juniper.net


Data Center Switching
4. While still in insert mode, use your arrow keys to navigate to the end of the
bb:aa:bb:aa:bb:00 MAC address referenced in the static mapping definition
associated with qfx2. Once positioned at the end of the MAC address, press the
Delete key as needed to remove the current MAC address. Once the current MAC
address is removed, enter the hardware address associated with the IRB interface on
qfx2.
host qfx2 {
hardware ethernet place:mac:address:here:xx:xx;
fixed-address 172.25.10.222;
option option-150 172.25.10.1;# Define FTP Server Address
option SUNW.server-image "/var/ftp/pub/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz";
option SUNW.server-file "/var/ftp/pub/qfx2-ZTP.config";

-- INSERT --
5. Once the correct hardware addresses are entered, press the Esc key to leave the
insert mode in the vi editor utility. Note that once you stop insert mode you should no
longer see the -- INSERT -- indicator at the bottom of the screen. Next, save the
changes and exit the vi editor using the :wq! key sequence followed by pressing the
Enter key.
host qfx1 {
hardware ethernet dc:38:e1:5e:48:00;
fixed-address 172.25.10.111;
option option-150 172.25.10.1;# Define FTP Server Address
option SUNW.server-image "/var/ftp/pub/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz";
option SUNW.server-file "/var/ftp/pub/qfx1-ZTP.config";

host qfx2 {
hardware ethernet dc:38:e1:5d:1c:00;
fixed-address 172.25.10.222;
option option-150 172.25.10.1;# Define FTP Server Address
option SUNW.server-image "/var/ftp/pub/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz";
option SUNW.server-file "/var/ftp/pub/qfx2-ZTP.config";

:wq!
"/etc/dhcpd.conf" 56L, 1714C written
sh-3.2$
Step 3.6
Issue the sudo service dhcpd restart command to restart the DHCP service. Next,
issue the service dhcpd status command to verify the DHCP service is running.
sh-3.2$ sudo service dhcpd restart
Shutting down dhcpd: [ OK ]
Starting dhcpd: [ OK ]

www.juniper.net Zero Touch Provisioning • Lab 1–19


Data Center Switching
sh-3.2$ service dhcpd status
dhcpd (pid 14847) is running...

Question: Is the DHCP service running?

Answer: Yes, the DHCP service should be running. You should


now see a new PID assigned to the DHCP service now that the
service has restarted.

Note
Make sure the DHCP service is running on
your assigned server before proceeding!

Step 3.7
Issue the sudo service vsftpd status command to verify that the FTP service is
running.
sh-3.2$ sudo service vsftpd status
vsftpd (pid 3094) is running...

Question: Is the FTP service running? If so, what is its process


identifier (PID)?

Answer: Yes, the FTP service should be running. The PID


assigned to the FTP service will vary. If the FTP service is not
running on your server, attempt to start the service using the
sudo service vsftpd start command.

Note
Make sure the FTP service is running on
your assigned server before proceeding!

Step 3.8
Test anonymous FTP access to your server using the ftp 172.25.10.1 command. When
prompted for a user name, enter anonymous. When prompted for a password, simply press the
Enter key.
sh-3.2$ ftp 172.25.10.1
Connected to 172.25.10.1.
220 Welcome Guardians of the Galaxy!
530 Please login with USER and PASS.
530 Please login with USER and PASS.
KERBEROS_V4 rejected as an authentication type
Name (172.25.10.1:lab): anonymous
331 Please specify the password.
Password:

Lab 1–20 • Zero Touch Provisioning www.juniper.net


Data Center Switching
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp>

Question: Does your server accept anonymous FTP


connections?

Answer: Yes, as shown in the sample output, the server should


accept anonymous FTP connections. If you see a different
result, check your work and, if needed, consult with your
instructor.

Step 3.9
Issue the bye command to close the FTP session on your server.
ftp> bye
221 Goodbye.
sh-3.2$

Part 4: Performing and Monitoring ZTP

In this lab part, you initiate ZTP on qfx1 and qfx2 and monitor the results.
Step 4.1
Return to the session opened for qfx1.
On qfx1, issue the request system zeroize command. When prompted with the warning
and asked if the system should proceed, type yes and press Enter.
{master:0}
lab@qfx1> request system zeroize
warning: System will be rebooted and may not boot without configuration
Erase all data, including configuration and log files? [yes,no] (no) yes

warning: ipsec-key-management subsystem not running - not needed by configuration.


warning: zeroizing fpc0

{master:0}
lab@qfx1> Aug 23 02:42:05 init: tnp-process (PID 1240) stopped by signal 17
Terminated
.
Aug 23 02:42:11 init: event-processing (PID 1007) exited with status=0 Normal Exit
Waiting (max 60 seconds) for system process `vnlru_mem' to stop...done
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...0 0 0 done

syncing disks... All buffers synced.


Uptime: 11h13m45s
recorded reboot as normal shutdown

www.juniper.net Zero Touch Provisioning • Lab 1–21


Data Center Switching
unloading fpga driver
unloading host-dev
Shutting down ACPI
Rebooting...

...TRIMMED...
Step 4.2
Once the system boots, login using the root account and no password. Once you have logged in
enter operational mode using the cli command and monitor the activity on the console. Note
that you will need to monitor the console for several minutes!
Amnesiac (ttyd0)

login: root

--- JUNOS 13.2X51-D15.5 built 2014-03-06 10:05:33 UTC


root@:RE:0% cli
{master:0}
root>
Auto Image Upgrade: DHCP Client Bound interfaces:

Auto Image Upgrade: DHCP Client Unbound interfaces: irb.0 vme.0

Auto Image Upgrade: No DHCP Client in bound state, reset all enabled DHCP clients

Auto Image Upgrade: DHCP Client State Reset: irb.0 vme.0

Auto Image Upgrade: DHCP Client Bound interfaces:

Auto Image Upgrade: DHCP Client Unbound interfaces: irb.0 vme.0

Auto Image Upgrade: No DHCP Client in bound state, reset all enabled DHCP clients

Auto Image Upgrade: DHCP Client State Reset: irb.0 vme.0

Auto Image Upgrade: DHCP Options for client interface irb.0:


ConfigFile: /var/ftp/pub/qfx1-ZTP.config ImageFile: /var/ftp/pub/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz Gateway: 172.25.10.1 File
Server: 172.25.10.1 Options state: All options set

Auto Image Upgrade: DHCP Client Bound interfaces: irb.0

Auto Image Upgrade: DHCP Client Unbound interfaces: vme.0 ge-0/0/0.0 et-0/0/48.0
et-0/0/49.0 et-0/0/50.0 et-0/0/51.0

Auto Image Upgrade: Active on client interface: irb.0

Auto Image Upgrade: Interface:: "irb"


Auto Image Upgrade: Server:: "172.25.10.1"
Auto Image Upgrade: Image File::
"jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz"
Auto Image Upgrade: Config File:: "qfx1-ZTP.config"
Auto Image Upgrade: Gateway:: "172.25.10.1"
Auto Image Upgrade: Protocol:: "ftp"

Lab 1–22 • Zero Touch Provisioning www.juniper.net


Data Center Switching
Auto Image Upgrade: Start fetching qfx1-ZTP.config file from server 172.25.10.1
through irb using ftp
Auto Image Upgrade: File qfx1-ZTP.config fetched from server 172.25.10.1 through
irb
Auto Image Upgrade: Start fetching
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz file from server 172.25.10.1
through irb using ftp

Auto Image Upgrade: File jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz fetched


from server 172.25.10.1 through irb
Auto Image Upgrade: To install /var/tmp/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz image fetched from server
172.25.10.1 through irb

WARNING!!! On successful image installation, system will reboot automatically

Auto Image Upgrade: Installation of /var/tmp/


jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz image fetched from server
172.25.10.1 through irb is done, proceeding for reboot of system

Broadcast Message from root@


(no tty) at 20:41 UTC...
Auto image Upgrade: Stopped
*** FINAL System shutdown message from root@ ***

System going down IMMEDIATELY


...TRIMMED...

Question: Based on the log messages, what is the first step


performed during the ZTP process? Why is this step required at
the beginning of the process?

Answer: As shown in the sample output, the first step


performed in the ZTP process is for the switch to obtain an IP
address through DHCP. This is a required step and facilitates
communications between the switch and the server which are
needed for the switch to retrieve the required software image
and its configuration file.

Question: Does qfx1 successfully work through ZTP?

Answer: Yes, as shown in the sample output, qfx1 should


successfully work through ZTP wherein it retrieves the needed
software image to which it will be upgraded and its assigned
configuration.

www.juniper.net Zero Touch Provisioning • Lab 1–23


Data Center Switching
Question: Based on the log messages, what is the final step
performed during the ZTP process?

Answer: As shown in the sample output, the final step


performed during the ZTP process is for the switch to halt the
auto-image upgrade process and perform a system reboot to
finalize the upgrade.

Step 4.3
Once the system reboots, log in using the lab and lab123 login credentials to verify the software
has been upgraded and the designated configuration is applied.
...TRIMMED...
Amnesiac (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1-ZTP> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx1-ZTP
Model: qfx5100-48s-6q
JUNOS Base OS Software Suite [13.2X51-D21.1]
JUNOS Base OS boot [13.2X51-D21.1]
JUNOS Crypto Software Suite [13.2X51-D21.1]
JUNOS Online Documentation [13.2X51-D21.1]
JUNOS Kernel Software Suite [13.2X51-D21.1]
JUNOS Packet Forwarding Engine Support (qfx-ex-x86-32) [13.2X51-D21.1]
JUNOS Routing Software Suite [13.2X51-D21.1]
JUNOS Enterprise Software Suite [13.2X51-D21.1]
JUNOS py-base-i386 [13.2X51-D21.1]
JUNOS Host Software [13.2X51-D21.1]

{master:0}
lab@qfx1-ZTP> show configuration system
host-name qfx1-ZTP;
arp {
aging-timer 5;
}
root-authentication {
encrypted-password "$1$kBv/jxIX$wCC5Jz8C5p0GuTbFK7MHJ."; ## SECRET-DATA
}
login {
user lab {
uid 2001;
class super-user;
authentication {
encrypted-password "$1$i38TAAb5$.9O8J9f2GGJUh5pdS5eC70"; ## SECRET-DATA
}
}

Lab 1–24 • Zero Touch Provisioning www.juniper.net


Data Center Switching
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
processes {
dhcp-service {
traceoptions {
file dhcp_logfile size 10m;
level all;
flag all;
}
}
app-engine-virtual-machine-management-service {
traceoptions {
level notice;
flag all;
}
}
}
ntp {
server 10.210.14.130;
}

{master:0}
lab@qfx1-ZTP>

Question: Has qfx1 successfully been upgraded to the


13.2X51-D21.1 version?

Answer: Yes, as shown in the sample output, the software has


been upgraded. Note that this point is also evident when you
first log in based on the initial message showing the software
version!

Question: Has qfx1 successfully retrieved and applied its


designated configuration file?

Answer: Yes, as shown in the sample output, the configuration


for qfx1 has been retrieved and applied. Note that this point is
also evident when you first log in based on the fact that you
must enter login credentials and that the new hostname is
displayed!

www.juniper.net Zero Touch Provisioning • Lab 1–25


Data Center Switching
Step 4.4
Return to the console opened for qfx2.
Using the previous steps performed on qfx1, initiate and monitor the ZTP process on qfx2. Once
complete, answer the questions that follow.
{master:0}
lab@qfx2> request system zeroize
warning: System will be rebooted and may not boot without configuration
Erase all data, including configuration and log files? [yes,no] (no) yes

warning: ipsec-key-management subsystem not running - not needed by configuration.


warning: zeroizing fpc0

{master:0}
lab@qfx2> Aug 25 21:50:40 init: tnp-process (PID 1240) stopped by signal 17
Terminated
.
Aug 25 21:50:46 init: event-processing (PID 1007) exited with status=0 Normal Exit
Waiting (max 60 seconds) for system process `vnlru_mem' to stop...done
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...0 0 0 done

syncing disks... All buffers synced.


Uptime: 3d3h57m9s
recorded reboot as normal shutdown
unloading fpga driver
unloading host-dev
Shutting down ACPI
Rebooting...

...TRIMMED...

Amnesiac (ttyd0)

login: root

--- JUNOS 13.2X51-D15.5 built 2014-03-06 10:05:33 UTC


root@:RE:0% cli
{master:0}
root>
Auto Image Upgrade: DHCP Client Bound interfaces:

Auto Image Upgrade: DHCP Client Unbound interfaces: irb.0 vme.0

Auto Image Upgrade: No DHCP Client in bound state, reset all enabled DHCP clien
ts

Auto Image Upgrade: DHCP Client State Reset: irb.0 vme.0

Lab 1–26 • Zero Touch Provisioning www.juniper.net


Data Center Switching
Auto Image Upgrade: DHCP Client Bound interfaces:

Auto Image Upgrade: DHCP Client Unbound interfaces: irb.0 vme.0

Auto Image Upgrade: No DHCP Client in bound state, reset all enabled DHCP clien
ts

Auto Image Upgrade: DHCP Client State Reset: irb.0 vme.0

Auto Image Upgrade: DHCP Options for client interface irb.0:


ConfigFile: /var/ftp/pub/qfx2-ZTP.config ImageFile: /var/ftp/pub/jinstall-qfx-5
-13.2X51-D21.1-domestic-signed.tgz Gateway: 172.25.10.1 File Server: 172.25.10.
1 Options state: All options set

Auto Image Upgrade: DHCP Client Bound interfaces: irb.0

Auto Image Upgrade: DHCP Client Unbound interfaces: vme.0 ge-0/0/0.0 et-0/0/4
8.0 et-0/0/49.0 et-0/0/50.0 et-0/0/51.0

Auto Image Upgrade: Active on client interface: irb.0

Auto Image Upgrade: Interface:: "irb"

Auto Image Upgrade: Server:: "172.25.10.1"

Auto Image Upgrade: Image File:: "jinstall-qfx-5-13.2X51-D21.1-domestic-signed


.tgz"

Auto Image Upgrade: Config File:: "qfx2-ZTP.config"

Auto Image Upgrade: Gateway:: "172.25.10.1"

Auto Image Upgrade: Protocol:: "ftp"

Auto Image Upgrade: Start fetching qfx2-ZTP.config file from server 172.25.10.1
through irb using ftp

Auto Image Upgrade: File qfx2-ZTP.config fetched from server 172.25.10.1 throug
h irb

Auto Image Upgrade: Start fetching jinstall-qfx-5-13.2X51-D21.1-domestic-signed


.tgz file from server 172.25.10.1 through irb using ftp

www.juniper.net Zero Touch Provisioning • Lab 1–27


Data Center Switching
Auto Image Upgrade: File jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz fetch
ed from server 172.25.10.1 through irb

Auto Image Upgrade: To install /var/tmp/jinstall-qfx-5-13.2X51-D21.1-domestic-s


igned.tgz image fetched from server 172.25.10.1 through irb

WARNING!!! On successful image installation, system will reboot automatically

Auto Image Upgrade: Installation of /var/tmp/jinstall-qfx-5-13.2X51-D21.1-domes


tic-signed.tgz image fetched from server 172.25.10.1 through irb is done, proce
eding for reboot of system

Broadcast Message from root@


(no tty) at 22:01 UTC...

Auto image Upgrade: Stopped

*** FINAL System shutdown message from root@ ***

System going down IMMEDIATELY

...TRIMMED...

Amnesiac (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx2-ZTP> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx2-ZTP
Model: qfx5100-48s-6q
JUNOS Base OS Software Suite [13.2X51-D21.1]
JUNOS Base OS boot [13.2X51-D21.1]
JUNOS Crypto Software Suite [13.2X51-D21.1]
JUNOS Online Documentation [13.2X51-D21.1]
JUNOS Kernel Software Suite [13.2X51-D21.1]
JUNOS Packet Forwarding Engine Support (qfx-ex-x86-32) [13.2X51-D21.1]
JUNOS Routing Software Suite [13.2X51-D21.1]
JUNOS Enterprise Software Suite [13.2X51-D21.1]
JUNOS py-base-i386 [13.2X51-D21.1]
JUNOS Host Software [13.2X51-D21.1]

{master:0}
lab@qfx2-ZTP> show configuration system
host-name qfx2-ZTP;
arp {

Lab 1–28 • Zero Touch Provisioning www.juniper.net


Data Center Switching
aging-timer 5;
}
root-authentication {
encrypted-password "$1$kBv/jxIX$wCC5Jz8C5p0GuTbFK7MHJ."; ## SECRET-DATA
}
login {
user lab {
uid 2001;
class super-user;
authentication {
encrypted-password "$1$i38TAAb5$.9O8J9f2GGJUh5pdS5eC70"; ## SECRET-DATA
}
}
}
...TRIMMED...
ntp {
server 10.210.14.130;
}

{master:0}
lab@qfx2-ZTP>

Question: Has qfx2 successfully been upgraded to the


13.2X51-D21.1 version?

Answer: Yes, as shown in the sample output, the software has


been upgraded.

Question: Has qfx2 successfully retrieved and applied its


designated configuration file?

Answer: Yes, as shown in the sample output, the configuration


for qfx2 has been retrieved and applied.

Step 4.5
On qfx2, enter configuration mode and load the lab1-start.config configuration file from
the /var/home/lab/dcx directory. Commit your changes, return to operational mode, and
log out of the switch.
{master:0}
lab@qfx2-ZTP> configure
Entering configuration mode

{master:0}[edit]
lab@qfx2-ZTP# load override dcx/lab1-start.config
load complete

{master:0}[edit]
lab@qfx2-ZTP# commit and-quit
configuration check succeeds
commit complete

www.juniper.net Zero Touch Provisioning • Lab 1–29


Data Center Switching
Exiting configuration mode

{master:0}
lab@qfx2> exit

qfx2 (ttyd0)

login:
Step 4.6
Return to the console session opened for qfx1.
On qfx1, enter configuration mode and load the lab1-start.config configuration file from
the /var/home/lab/dcx directory. Commit your changes, return to operational mode, and
log out of the switch.
{master:0}
lab@qfx1-ZTP> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1-ZTP# load override dcx/lab1-start.config
load complete

{master:0}[edit]
lab@qfx1-ZTP# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@qfx1> exit

qfx1 (ttyd0)

login:

STOP Tell your instructor that you have completed this lab.

Lab 1–30 • Zero Touch Provisioning www.juniper.net


Data Center Switching

www.juniper.net Zero Touch Provisioning • Lab 1–31


Data Center Switching

Lab 1–32 • Zero Touch Provisioning www.juniper.net


Lab
In-Service Software Upgrade

Overview
In this lab, you perform an in-service software upgrade to upgrade the software running on one
of your QFX5100 Series switches with minimal traffic disruption during the upgrade.
By completing this lab, you will perform the following tasks:
• Access your assigned QFX5100 switches.
• Load starting configurations and verify connectivity.
• Downgrade qfx1 to an earlier software version.
• Perform an in-service software upgrade on qfx1.

Part 1: Logging In Using the CLI

In this lab part, you become familiar with the access details used to connect to the lab
equipment. Once you are familiar with the access details, you will use the CLI to log in to your
team’s designated switches. Once you have logged in to your device you will make sure your
devices are running the appropriate starting configurations for this lab.
Step 1.1
Ensure that you know to which switches you have been assigned. Check with your instructor if
you are not certain. Consult the management network diagram to determine your switches’
management addresses.

Question: What are the management addresses assigned to


your switches?

Answer: The answer varies and depends on your assigned


environment and devices. If you are unsure of your assignment,
ask your instructor.

Step 1.2
Using console access, connect to your qfx1 switch and log in using the lab and lab123 login
credentials.

www.juniper.net In-Service Software Upgrade • Lab 2–1


Data Center Switching
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1>
Step 1.3
Enter configuration mode and load the lab2-start.config configuration file from the /
var/home/lab/dcx directory. Commit your changes and return to operational mode.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# load override dcx/lab2-start.config
load complete

{master:0}[edit]
lab@qfx1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@qfx1>
Step 1.4
Open a new and separate console session to your qfx2 switch and perform the same steps
previously completed on qfx1 ensuring that the lab2-start.config configuration file is
ultimately loaded on both qfx1 and qfx2.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx2> configure
Entering configuration mode

{master:0}[edit]
lab@qfx2# load override dcx/lab2-start.config
load complete

{master:0}[edit]
lab@qfx2# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

Lab 2–2 • In-Service Software Upgrade www.juniper.net


Data Center Switching
{master:0}
lab@qfx2>

Part 2: Downgrading Software

In this lab part, you perform a standard downgrade of the software on qfx1 in preparation of an
in-service software upgrade performed in a subsequent lab part.
Step 2.1
Return to the console session opened for qfx1.
On qfx1, verify the software version running on the system using the show version
command.
{master:0}
lab@qfx1> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx1
Model: qfx5100-48s-6q
JUNOS Base OS Software Suite [13.2X51-D21.1]
JUNOS Base OS boot [13.2X51-D21.1]
JUNOS Crypto Software Suite [13.2X51-D21.1]
JUNOS Online Documentation [13.2X51-D21.1]
JUNOS Kernel Software Suite [13.2X51-D21.1]
JUNOS Packet Forwarding Engine Support (qfx-ex-x86-32) [13.2X51-D21.1]
JUNOS Routing Software Suite [13.2X51-D21.1]
JUNOS Enterprise Software Suite [13.2X51-D21.1]
JUNOS py-base-i386 [13.2X51-D21.1]
JUNOS Host Software [13.2X51-D21.1]

Question: Which software version is running on qfx2? Are all


packages running the same version?

Answer: Your qfx1 switch should be running 13.2X51-D21.1. At


this point all packages, including the JUNOS Host Software,
should be running this version.

Step 2.2
Use secure copy to download the 13.2X51-D15.5 Junos OS image from the server (172.25.10.1)
to the /var/tmp directory on qfx1. If prompted for a security authorization, type yes. When
prompted for a password, use lab123.
{master:0}
lab@qfx1> file copy scp://172.25.10.1/home/lab/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz /var/tmp/
lab@172.25.10.1's password:
jinstall-qfx-5-13.2X51-D15.5-domestic-signed. 100% 395MB 1.4MB/s 04:49

www.juniper.net In-Service Software Upgrade • Lab 2–3


Data Center Switching
Question: Did the image successfully download?

Answer: You should see a successful download of the target


image as shown in the sample output.

Step 2.3
Once the 13.2X51-D15.5 Junos OS image has been downloaded to qfx1, use the file
checksum md5 command and ensure the MD5 checksum matches the
bf4d1adc93ca922233aa0024dd7e3c32 value.
{master:0}
lab@qfx1> file checksum md5 /var/tmp/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz
MD5 (/var/tmp/jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz) =
bf4d1adc93ca922233aa0024dd7e3c32

Question: Does the resulting MD5 checksum match the


expected checksum value?

Answer: The checksum value of the file should be


bf4d1adc93ca922233aa0024dd7e3c32. If you see a different
value, check your work and, if needed, download the file again
and work with your instructor as needed.

Step 2.4
Use the request system software add /var/tmp/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz reboot command to
perform a software downgrade to the referenced software version. Once the downgrade is
complete, log in using the lab and lab123 login credentials and verify the software version
using the show version command.
{master:0}
lab@qfx1> request system software add /var/tmp/
jinstall-qfx-5-13.2X51-D15.5-domestic-signed.tgz reboot
Verified jinstall-vjunos-13.2X51-D15.5-domestic.tgz signed by
PackageProductionVJunos_13_2_0
Adding vjunos...
Saving contents of boot area prior to installation

WARNING: This package will load JUNOS 13.2X51-D15.5 software.


WARNING: It will save JUNOS configuration files, and SSH keys
WARNING: (if configured), but erase all other files and information
WARNING: stored on this machine. It will attempt to preserve dumps
WARNING: and log files, but this can not be guaranteed. This is the
WARNING: pre-installation stage and all the software is loaded when
WARNING: you reboot the system.

POST-INSTALL...
Saving the config files ...

Lab 2–4 • In-Service Software Upgrade www.juniper.net


Data Center Switching
NOTICE: uncommitted changes have been saved in /var/db/config/
juniper.conf.pre-install
Pushing installation package to host...
Extracting jinstall-qfx-5-13.2X51-D15.5-domestic ...
Install jinstall-qfx-5-13.2X51-D15.5-domestic completed
Install jinstall-vjunos completed

WARNING: A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the


WARNING: 'request system reboot' command when software installation is
WARNING: complete. To abort the installation, do not reboot your system,
WARNING: instead use the 'request system software delete jinstall'
WARNING: command as soon as this operation completes.

Saving state for rollback ...


Rebooting ...
shutdown: [pid 75438]
Shutdown NOW!

*** FINAL System shutdown message from root@qfx1 ***

System going down IMMEDIATELY

...TRIMMED...

qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D15.5 built 2014-03-06 10:05:33 UTC


{master:0}
lab@qfx1> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx1
Model: qfx5100-48s-6q
JUNOS Base OS Software Suite [13.2X51-D15.5]
JUNOS Base OS boot [13.2X51-D15.5]
JUNOS Crypto Software Suite [13.2X51-D15.5]
JUNOS Online Documentation [13.2X51-D15.5]
JUNOS Kernel Software Suite [13.2X51-D15.5]
JUNOS Packet Forwarding Engine Support (qfx-x86-32) [13.2X51-D15.5]
JUNOS Routing Software Suite [13.2X51-D15.5]
JUNOS Enterprise Software Suite [13.2X51-D15.5]
JUNOS py-base-i386 [13.2X51-D15.5]
JUNOS Host Software [13.2X51-D21.1]

www.juniper.net In-Service Software Upgrade • Lab 2–5


Data Center Switching
Question: Which software version is running on qfx1? Are all
packages running the same version?

Answer: Your qfx1 switch should be running 13.2X51-D15.5. At


this point all packages, except the JUNOS Host Software, should
be running this version. When upgrading or downgrading
software on a QFX5100 the Host Software image does not
change unless you use the force-host option. In our case,
we did not use the force-host option so that package
remains untouched.

Note
The JUNOS Host Software package is the underlying host
operating system and is based on centOS. It is through
this host operating system and some key processes that
the virtual Junos OS switch instances are managed. Note
that there should not be any negative consequence of
having this package different from the other packages.

Note
You cannot use the force-host option when
performing an in-service software upgrade!

Part 3: Verifying Environmental Operations

In this lab part, you become familiar with the environment and verify operations. Specifically, you
verify that the virtual routers configured on qfx2 can communicate through qfx1 and that the
expected OSPF neighbor adjacencies are BGP peering sessions are up and operational.
Step 3.1
On qfx1, issue the show ethernet-switching interface command to verify the state and
VLAN assignments of the Layer 2 interfaces used to interconnect the virtual routers (vr1 and vr2)
configured on qfx2.
Refer to the diagram for this lab for a visual of the topological details.

{master:0}
lab@qfx1> show ethernet-switching interface
Routing Instance Name : default-switch
Logical Interface flags (DL - disable learning, AD - packet action drop,
LH - MAC limit hit, DN - interface down )
Logical Vlan TAG MAC STP Logical Tagging
interface members limit state interface flags
et-0/0/48.0 294912 untagged
v15 15 294912 Forwarding untagged
Routing Instance Name : default-switch
Logical Interface flags (DL - disable learning, AD - packet action drop,

Lab 2–6 • In-Service Software Upgrade www.juniper.net


Data Center Switching
LH - MAC limit hit, DN - interface down )
Logical Vlan TAG MAC STP Logical Tagging
interface members limit state interface flags
et-0/0/49.0 294912 untagged
v15 15 294912 Forwarding untagged

Question: What is the state of the Layer 2 interfaces used to


interconnect vr1 and vr2?

Answer: The Layer 2 interfaces should be up and operational.


Note that this is verified by the lack of the DN logical interface
flag. If you see some other state, check your work and, if
needed, consult with your instructor.

Question: To which VLAN are these interfaces assigned? What


is their current port mode?

Answer: Both et-0/0/48.0 and et-0/0/49.0 should be assigned


to the v15 VLAN. Both interfaces should be configured as
access ports; determined by the untagged reference in the
far-right column. If you see some other state, check your work
and, if needed, consult with your instructor.

Step 3.2
Return to the console session opened for qfx2.
On qfx2, issue the show configuration routing-instances command to determine
the current routing instance configuration details on qfx2.
{master:0}
lab@qfx2> show configuration routing-instances
vr1 {
instance-type virtual-router;
interface et-0/0/48.0;
interface lo0.1;
routing-options {
autonomous-system 65535;
}
protocols {
bgp {
group ibgp {
type internal;
neighbor 192.168.100.2 {
local-address 192.168.100.1;
}
}
}
ospf {
area 0.0.0.0 {
interface lo0.1;
interface et-0/0/48.0;

www.juniper.net In-Service Software Upgrade • Lab 2–7


Data Center Switching
}
}
}
}
vr2 {
instance-type virtual-router;
interface et-0/0/49.0;
interface lo0.2;
routing-options {
autonomous-system 65535;
}
protocols {
bgp {
group ibgp {
type internal;
neighbor 192.168.100.1 {
local-address 192.168.100.2;
}
}
}
ospf {
area 0.0.0.0 {
interface lo0.2;
interface et-0/0/49.0;
}
}
}
}

Question: Which interfaces belong to the vr1 and vr2 routing


instances? Based on the configuration details shown in the
output and the topology details shown in the associated lab
diagram, what would happen if these interfaces went down?

Answer: The et-0/0/48.0 and et-0/0/49.0 interfaces are


assigned to the vr1 and vr2 routing instances respectively.
Based on the configuration details and the current topology, if
one or both of these interfaces went down, vr1 and vr2 could no
longer communicate, which means their OSPF adjacency and
BGP peering session would go down thus impacting all local and
transit routing services using these virtual routers.

Step 3.3
Issue the ping routing-instance vr1 192.168.100.2 rapid count 10
command to verify reachability between vr1 and vr2.
{master:0}
lab@qfx2> ping routing-instance vr1 192.168.100.2 rapid count 10
PING 192.168.100.2 (192.168.100.2): 56 data bytes
!!!!!!!!!!

Lab 2–8 • In-Service Software Upgrade www.juniper.net


Data Center Switching
--- 192.168.100.2 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 32.825/45.736/84.379/13.572 ms

Question: Did the ping test succeed?

Answer: Yes, as shown in the sample output, the ping test


should succeed. If not, check your work and, if needed, work
with your instructor.

Step 3.4
Issue the show ospf neighbor instance vr1 and show bgp summary instance
vr1 commands to verify the state of the OSPF adjacency and BGP peering session that rely on
the connections passing through qfx1.
{master:0}
lab@qfx2> show ospf neighbor instance vr1
Address Interface State ID Pri Dead
172.25.15.2 et-0/0/48.0 Full 192.168.100.2 128 38

{master:0}
lab@qfx2> show bgp summary instance vr1
Groups: 1 Peers: 1 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
vr1.inet.0
0 0 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn
State|#Active/Received/Accepted/Damped...
192.168.100.2 65535 2068 2072 0 3 7:57 Establ
vr1.inet.0: 0/0/0/0

Question: What is the state of the OSPF adjacency?

Answer: As shown in the sample output, the OSPF adjacency


should be in the Full state. If not, check your work and, if
needed, work with your instructor.

Question: What is the state of the BGP peering session?

Answer: As shown in the sample output, the BGP peering


session should be in the Establ state. If not, check your work
and, if needed, work with your instructor.

Part 4: Performing an In-Service Software Upgrade

In this lab part, you perform an in-service software upgrade and verify its impact on transit
traffic and the protocol adjacency and peering sessions that are established using connections
that pass through the switch being upgraded.
www.juniper.net In-Service Software Upgrade • Lab 2–9
Data Center Switching
Step 4.1
On qfx2, issue the ping routing-instance vr1 192.168.100.2 command to
generate an ongoing flow of traffic between vr1 and vr2.
Note
Ensure you let the ping operation continue for now. In a later
step, you will stop this ping operation. After stopping the ping
operation, you will verify the impact an ISSU performed on qfx1
had on the traffic flowing between the two virtual routers.

lab@qfx2> ping routing-instance vr1 192.168.100.2


PING 192.168.100.2 (192.168.100.2): 56 data bytes
64 bytes from 192.168.100.2: icmp_seq=0 ttl=64 time=33.226 ms
64 bytes from 192.168.100.2: icmp_seq=1 ttl=64 time=44.038 ms
64 bytes from 192.168.100.2: icmp_seq=2 ttl=64 time=44.040 ms
64 bytes from 192.168.100.2: icmp_seq=3 ttl=64 time=44.039 ms
64 bytes from 192.168.100.2: icmp_seq=4 ttl=64 time=44.071 ms
64 bytes from 192.168.100.2: icmp_seq=5 ttl=64 time=44.040 ms
64 bytes from 192.168.100.2: icmp_seq=6 ttl=64 time=44.038 ms
64 bytes from 192.168.100.2: icmp_seq=7 ttl=64 time=44.039 ms
64 bytes from 192.168.100.2: icmp_seq=8 ttl=64 time=33.037 ms

...
Step 4.2
Return to the console opened for qfx1.
On qfx1, use secure copy to download the 13.2X51-D21.1 Junos OS image from the server
(172.25.10.1) to the /var/tmp directory on qfx1. If prompted for a security authorization, type
yes. When prompted for a password, use lab123.
{master:0}
lab@qfx1> file copy scp://172.25.10.1/home/lab/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz /var/tmp/
lab@172.25.10.1's password:
jinstall-qfx-5-13.2X51-D21.1-domestic-signed. 100% 393MB 1.4MB/s 04:49

Question: Did the image successfully download?

Answer: You should see a successful download of the target


image as shown in the sample output.

Step 4.3
Once the 13.2X51-D21.1 Junos OS image has been downloaded to qfx1, use the file
checksum md5 command and ensure the MD5 checksum matches the
42b7ceba290aaf121bddbedb55bb3a05 value.
{master:0}
lab@qfx1> file checksum md5 /var/tmp/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz
MD5 (/var/tmp/jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz) =
42b7ceba290aaf121bddbedb55bb3a05

Lab 2–10 • In-Service Software Upgrade www.juniper.net


Data Center Switching
Question: Does the resulting MD5 checksum match the
expected checksum value?

Answer: The checksum value of the file should be


42b7ceba290aaf121bddbedb55bb3a05. If you see a different
value, check your work and, if needed, download the file again
and work with your instructor as needed.

Step 4.4
Issue the request system software in-service-upgrade /var/tmp/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz command to attempt an
in-service software upgrade.
{master:0}
lab@qfx1> request system software in-service-upgrade /var/tmp/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz
warning: GRES not configured

{master:0}
lab@qfx1>

Question: Was the attempted in-service software upgrade


successful? If not, why?

Answer: The attempted in-service software upgrade should not


succeed at this time because all of the configuration
requirements are not yet met.

Question: Which configuration requirements exist for a


QFX5100 switch to perform ISSU?

Answer: As the warning in the CLI output indicates, graceful


routing engine switchover (GRES) is required for ISSU. In
addition to GRES, you should also enable non-stop bridging
(NSB) and non-stop routing (NSR). We configure these features
in the next steps.

Step 4.5
Enter configuration mode and enable GRES under the [edit chassis redundancy]
hierarchy.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# set chassis redundancy graceful-switchover

www.juniper.net In-Service Software Upgrade • Lab 2–11


Data Center Switching
{master:0}[edit]
lab@qfx1#
Step 4.6
Enable NSB and NSR under the [edit protocols layer2-control] and [edit
routing-options] hierarchy levels respectively.
{master:0}[edit]
lab@qfx1# set protocols layer2-control nonstop-bridging

{master:0}[edit]
lab@qfx1# set routing-options nonstop-routing
Step 4.7
Issue the set system commit synchronize command from the root hierarchy level to
enable commit synchronization for the system. Once commit synchronization is enabled, activate
the changes and return to operational mode.
{master:0}[edit]
lab@qfx1# set system commit synchronize

{master:0}[edit]
lab@qfx1# commit and-quit

configuration check succeeds


commit complete
Exiting configuration mode

{master:0}
lab@qfx1>
Step 4.8
Issue the request system software in-service-upgrade /var/tmp/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz command to perform an
in-service software upgrade.
{master:0}
lab@qfx1> request system software in-service-upgrade /var/tmp/
jinstall-qfx-5-13.2X51-D21.1-domestic-signed.tgz
warning: Do NOT use /user during ISSU. Changes to /user during ISSU may get lost!
ISSU: Validating Image
ISSU: Preparing Backup RE
Prepare for ISSU
ISSU: Backup RE Prepare Done

Extracting jinstall-qfx-5-13.2X51-D21.1-domestic ...


Install jinstall-qfx-5-13.2X51-D21.1-domestic completed
Spawning the backup RE
Spawn backup RE, index 0 successful
GRES in progress
GRES done in 8 seconds
Waiting for backup RE switchover ready
GRES operational
Copying home directories
Copying home directories successful

Lab 2–12 • In-Service Software Upgrade www.juniper.net


Data Center Switching
Initiating Chassis In-Service-Upgrade
Chassis ISSU Started
ISSU: Preparing Daemons
ISSU: Daemons Ready for ISSU
ISSU: Starting Upgrade for FRUs
ISSU: FPC Warm Booting
ISSU: FPC Warm Booted
ISSU: Preparing for Switchover
ISSU: Ready for Switchover
Checking In-Service-Upgrade status
Item Status Reason
FPC 0 Online (ISSU)
Send ISSU done to chassisd on backup RE
Chassis ISSU Completed
ISSU: IDLE
Initiate em0 device handoff
pci-stub 0000:01:00.2: transaction is not cleared; proceeding with reset anyway
pci-stub 0000:01:00.2: transaction is not cleared; proceeding with reset anyway
pci-stub 0000:01:00.1: transaction is not cleared; proceeding with reset anyway
pci-stub 0000:01:00.1: transaction is not cleared; proceeding with reset anyway
pci-stub 0000:01:00.2: transaction is not cleared; proceeding with reset anyway
pci-stub 0000:01:00.2: transaction is not cleared; proceeding with reset anyway
pci-stub 0000:01:00.1: transaction is not cleared; proceeding with reset anyway
pci-stub 0000:01:00.1: transaction is not cleared; proceeding with reset anyway
em0: bus=0, device=3, func=0, Ethernet address dc:38:e1:5e:4c:f8

Note
At this point you will need to press the Enter
key as there is a soft reset of the console
connection that occurs during the ISSU.

Step 4.9
Once you see the login prompt, log in using the lab and lab123 login credentials. Next, issue
the show version command to confirm the software has been upgraded to the 13.2X51-21.1
version.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1> show version
fpc0:
--------------------------------------------------------------------------
Hostname: qfx1
Model: qfx5100-48s-6q
JUNOS Base OS Software Suite [13.2X51-D21.1]
JUNOS Base OS boot [13.2X51-D21.1]
JUNOS Crypto Software Suite [13.2X51-D21.1]
JUNOS Online Documentation [13.2X51-D21.1]
JUNOS Kernel Software Suite [13.2X51-D21.1]
JUNOS Packet Forwarding Engine Support (qfx-ex-x86-32) [13.2X51-D21.1]
www.juniper.net In-Service Software Upgrade • Lab 2–13
Data Center Switching
JUNOS Routing Software Suite [13.2X51-D21.1]
JUNOS Enterprise Software Suite [13.2X51-D21.1]
JUNOS py-base-i386 [13.2X51-D21.1]
JUNOS Host Software [13.2X51-D21.1]

{master:0}
lab@qfx1>

Question: Was the attempted in-service software upgrade


successful?

Answer: The attempted in-service software upgrade should have


succeed and your qfx1 switch should now be running the
13.2X51-D21.1 version.

Step 4.10
Return to the console session of your qfx2 switch.
On qfx2, break the continuous ping operation by issuing the Ctrl + C key sequence and
assess the resulting statistics presented at the bottom of the output.
...
64 bytes from 192.168.100.2: icmp_seq=1717 ttl=64 time=44.039 ms
64 bytes from 192.168.100.2: icmp_seq=1718 ttl=64 time=33.037 ms
64 bytes from 192.168.100.2: icmp_seq=1719 ttl=64 time=44.040 ms
64 bytes from 192.168.100.2: icmp_seq=1720 ttl=64 time=44.040 ms
64 bytes from 192.168.100.2: icmp_seq=1721 ttl=64 time=44.038 ms
64 bytes from 192.168.100.2: icmp_seq=1722 ttl=64 time=44.039 ms
64 bytes from 192.168.100.2: icmp_seq=1723 ttl=64 time=33.037 ms
64 bytes from 192.168.100.2: icmp_seq=1724 ttl=64 time=44.040 ms
64 bytes from 192.168.100.2: icmp_seq=1725 ttl=64 time=44.038 ms
64 bytes from 192.168.100.2: icmp_seq=1726 ttl=64 time=44.039 ms
64 bytes from 192.168.100.2: icmp_seq=1727 ttl=64 time=33.037 ms
^C
--- 192.168.100.2 ping statistics ---
1728 packets transmitted, 1728 packets received, 0% packet loss
round-trip min/avg/max/stddev = 16.060/42.770/96.070/9.138 ms

{master:0}
lab@qfx2>

Question: Based on the displayed output, was the traffic


transiting your qfx1 switch sent between vr1 and vr2 affected by
the ISSU performed on qfx1?

Answer: While your statistics may vary from that shown in the
sample output, you should not see much if any impact to the
transit traffic passing through qfx1 during the time of the ISSU.
In the sample output, you can see that there was no impact and
we see a 0% packet loss.

Lab 2–14 • In-Service Software Upgrade www.juniper.net


Data Center Switching
Step 4.11
Issue the show ospf neighbor instance vr1 detail and show bgp summary
instance vr1 commands to verify the state of the OSPF adjacency and BGP peering session
that rely on the connections passing through qfx1.
{master:0}
lab@qfx2> show ospf neighbor instance vr1 detail
Address Interface State ID Pri Dead
172.25.15.2 et-0/0/48.0 Full 192.168.100.2 128 39
Area 0.0.0.0, opt 0x52, DR 172.25.15.2, BDR 172.25.15.1
Up 00:30:43, adjacent 00:30:03

{master:0}
lab@qfx2> show bgp summary instance vr1
Groups: 1 Peers: 1 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
vr1.inet.0
0 0 0 0 0 0
vr1.mdt.0
0 0 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn
State|#Active/Received/Accepted/Damped...
192.168.100.2 65535 68 68 0 0 29:38 Establ
vr1.inet.0: 0/0/0/0

Question: What is the state of the OSPF adjacency?

Answer: As shown in the sample output, the OSPF adjacency


should be in the Full state. With the help of the detail option,
you can also see how long the adjacency has been up. In the
sample output, this adjacency has been up for over 30 minutes,
which means the ISSU performed on qfx1 had no impact on the
OSPF adjacency between the virtual routers configured on qfx2.

Question: What is the state of the BGP peering session?

Answer: As shown in the sample output, the BGP peering


session should be in the Establ state. You should also note
that there are no reported flaps in this BGP peering session,
which means the ISSU performed on qfx1 had no impact on the
BGP peering session between the virtual routers configured on
qfx2.

Step 4.12
Log out of your switches and close the console sessions.
{master:0}
lab@qfx2> exit

www.juniper.net In-Service Software Upgrade • Lab 2–15


Data Center Switching
qfx2 (ttyd0)

login:

{master:0}
lab@qfx1> exit

qfx1 (ttyd0)

login:

STOP Tell your instructor that you have completed this lab.

Lab 2–16 • In-Service Software Upgrade www.juniper.net


Data Center Switching

www.juniper.net In-Service Software Upgrade • Lab 2–17


Data Center Switching

Lab 2–18 • In-Service Software Upgrade www.juniper.net


Lab
Multichassis Link Aggregation

Overview
In this lab, you configure Multichassis Link Aggregation groups (MC-LAGs) between your
QFX5100 Series switches. You then perform monitoring and verification tasks to ensure proper
operations.
By completing this lab, you will perform the following tasks:
• Access your assigned QFX5100 and EX4300 switches.
• Load starting configurations and verify connectivity.
• Configure Multichassis Link Aggregation on QFX5100 switches.
• Verify proper operations for Layer 2 traffic within a VLAN.
• Enable Layer 3 gateway services on the MC-LAG peers.
• Verify proper operations for Layer 3 traffic between VLANs.

Part 1: Logging In Using the CLI

In this lab part, you become familiar with the access details used to connect to the lab
equipment. Once you are familiar with the access details, you will use the CLI to log in to your
team’s designated switches. Once you have logged in, you will make sure your devices are
running the appropriate starting configurations for this lab.
Step 1.1
Ensure that you know to which switches you have been assigned. Check with your instructor if
you are not certain. Consult the management network diagram to determine your switches’
management addresses.

Question: What are the management addresses assigned to


your switches?

Answer: The answer varies and depends on your assigned


environment and devices. If you are unsure of your assignment,
ask your instructor.

www.juniper.net Multichassis Link Aggregation • Lab 3–1


Data Center Switching
Step 1.2
Using console access, connect to your qfx1 switch and log in using the lab and lab123 login
credentials.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1>
Step 1.3
Enter configuration mode and load the lab3-start.config configuration file from the /
var/home/lab/dcx directory.
Commit your changes and remain in configuration mode.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# load override dcx/lab3-start.config
load complete

{master:0}[edit]
lab@qfx1# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx1#
Step 1.4
Open a new and separate console session to your qfx2 switch and log in using the lab and
lab123 login credentials. Once logged in, enter configuration mode and load the
lab3-start.config configuration file from the /var/home/lab/dcx directory.
Commit your changes and commit your changes and remain in configuration mode.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx2> configure
Entering configuration mode

{master:0}[edit]
lab@qfx2# load override dcx/lab3-start.config
load complete

Lab 3–2 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
{master:0}[edit]
lab@qfx2# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx2#
Step 1.5
Issue the show interfaces and show routing-instances commands.
{master:0}[edit]
lab@qfx2# show interfaces
ge-0/0/0 {
description "HostX-VR Interface - Do Not Delete!";
vlan-tagging;
mac dc:38:e1:5e:11:22;
unit 15 {
vlan-id 15;
family inet {
address 172.25.15.100/24;
}
}
unit 20 {
vlan-id 20;
family inet {
address 172.25.20.100/24;
}
}
}
em0 {
unit 0 {
family inet {
address 10.210.14.154/26;
}
}
}

{master:0}[edit]
lab@qfx2# show routing-instances
HostX-VR {
instance-type virtual-router;
interface ge-0/0/0.15;
interface ge-0/0/0.20;
}

www.juniper.net Multichassis Link Aggregation • Lab 3–3


Data Center Switching
Question: Beside the management em0 interface, are there any
other interfaces configured?

Answer: Yes, you should see the ge-0/0/0 interface configured


with two logical units (15 and 20), each associated with unique
VLANs (15 and 20 respectively). Note that this interface
configuration along with the HostX-VR routing instance are used
to simulate the Host X device displayed on the diagram for this
lab. If you do not see the ge-0/0/0 interface or the HostX-VR
routing instance, check your work and, if needed, consult with
your instructor.

Step 1.6
Open a new and separate console session to your ex1 switch and log in using the lab and
lab123 login credentials. Once logged in, enter configuration mode and load the
lab3-start.config configuration file from the /var/home/lab/dcx directory. Commit
your changes and return to operational mode.
ex1 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex1> configure
Entering configuration mode

{master:0}[edit]
lab@ex1# load override dcx/lab3-start.config
load complete

{master:0}[edit]
lab@ex1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@ex1-ServerA>
Note
The ex1 switch serves as the Server A device
illustrated on the diagram associated with this lab.

Step 1.7
Open a new and separate console session to your ex2 switch and log in using the lab and
lab123 login credentials. Once logged in, enter configuration mode and load the
lab3-start.config configuration file from the /var/home/lab/dcx directory. Commit
your changes and return to operational mode.

Lab 3–4 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
ex2 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex2> configure
Entering configuration mode

{master:0}[edit]
lab@ex2# load override dcx/lab3-start.config
load complete

{master:0}[edit]
lab@ex2# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@ex2-ServerB>
Note
The ex2 switch serves as the Server B device
illustrated on the diagram associated with this lab.

Part 2: Configuring Multichassis Link Aggregation

In this lab part, you configure Multichassis Link Aggregation on qfx1 and qfx2 to support the
connections from the attached Server A and Server B devices. Once configured, you will perform
some basic verification steps to ensure Layer 2 operations between devices on the same VLAN.
Step 2.1
Return to the console session opened for qfx1.
On qfx1, issue the run show interfaces terse | match ae command to determine if
any aggregated Ethernet interfaces currently exist.
{master:0}[edit]
lab@qfx1# run show interfaces terse | match ae

{master:0}[edit]
lab@qfx1#

Question: Based on the diagram for this lab, how many


aggregated Ethernet interfaces with qfx1 and qfx2 require?

Answer: Based on the diagram associated with this lab, you


should see that both qfx1 and qfx2 require 3 aggregated
Ethernet interfaces (ae0, ae1, and ae2). These will be created
and configured in subsequent steps in this lab part.

www.juniper.net Multichassis Link Aggregation • Lab 3–5


Data Center Switching
Step 2.2
Create three aggregated Ethernet interfaces under the [edit chassis] hierarchy and
commit the change. Once the configuration change has been activated, issue the run show
interfaces terse | match ae command to verify the aggregated Ethernet interfaces
have been created.
{master:0}[edit]
lab@qfx1# set chassis aggregated-devices ethernet device-count 3

{master:0}[edit]
lab@qfx1# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx1# run show interfaces terse | match ae
ae0 up down
ae1 up down
ae2 up down

Question: Have the aggregated Ethernet interfaces been


created? If so, what is their current state?

Answer: Yes, as shown in the sample output, you should now


see the ae0, ae1, and ae2 aggregated Ethernet interfaces. The
state of each should be administratively up (the first column)
and link down (the second column).

Question: What is required for an aggregated Ethernet


interface’s link status to be up?

Answer: By default, aggregated Ethernet interfaces must be


configured and require at least one associated member link that
is administratively and physically up. At this point, because the
aggregated Ethernet interfaces have not been configured and
do not have member links assigned to them, it is expected that
they all show the link down status.

Step 2.3
Configure ae0 for Layer 2 operations as a trunk port. Associate ae0 with the v100 VLAN, which
will be configured in a subsequent step. Note that ae0 will serve as the interchassis
link-protection link (ICL-PL) for the MC-LAGs, which you configure later in this lab part.
{master:0}[edit]
lab@qfx1# set interfaces ae0 unit 0 family ethernet-switching

{master:0}[edit]
lab@qfx1# set interfaces ae0.0 family ethernet-switching interface-mode trunk

Lab 3–6 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
{master:0}[edit]
lab@qfx1# set interfaces ae0.0 family ethernet-switching vlan members v100
Step 2.4
Configure VLAN v100 with a tag value of 100.
{master:0}[edit]
lab@qfx1# set vlans v100 vlan-id 100
Step 2.5
Configure et-0/0/48 and et-0/0/49 as member links for the ae0 interface and commit your
changes. Once the configuration changes have been activated, issue the run show
interfaces terse | match ae0 command to verify the state of the ae0 aggregated
Ethernet interface.
{master:0}[edit]
lab@qfx1# set interfaces et-0/0/48 ether-options 802.3ad ae0

{master:0}[edit]
lab@qfx1# set interfaces et-0/0/49 ether-options 802.3ad ae0

{master:0}[edit]
lab@qfx1# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx1# run show interfaces terse | match ae0
et-0/0/48.0 up up aenet --> ae0.0
et-0/0/49.0 up up aenet --> ae0.0
ae0 up up
ae0.0 up up eth-switch

Question: What is the current state of ae0?

Answer: As shown in the sample output, the current state of


ae0 should be administratively and operationally up. If you see
some other state, check your work and, as needed, work with
your instructor.

Step 2.6
Enable ae0 to support LACP and to actively initiate LACP communications. Once LACP has been
enabled, activate the configuration change and verify ae0’s interface status once again with the
run show interfaces terse | match ae0 command.
{master:0}[edit]
lab@qfx1# set interfaces ae0 aggregated-ether-options lacp active

{master:0}[edit]
lab@qfx1# commit
configuration check succeeds
commit complete

www.juniper.net Multichassis Link Aggregation • Lab 3–7


Data Center Switching

{master:0}[edit]
lab@qfx1# run show interfaces terse | match ae0
et-0/0/48.0 up up aenet --> ae0.0
et-0/0/49.0 up up aenet --> ae0.0
ae0 up down
ae0.0 up down eth-switch

Question: What is the current state of ae0? Can you explain the
current status of the ae0 interface?

Answer: As shown in the sample output, the current state of ae0


should be administratively up and operationally down. Now that
LACP has been enabled, the ae0 interface requires the proper
exchange of LACP packets from the remote side of the
connection. As this time, the remote device, qfx2, has not yet
been configured to support this connection.

Step 2.7
Return to the console connection opened for qfx2.
On qfx2, perform the following tasks:
1. Create three aggregated Ethernet interfaces.
{master:0}[edit]
lab@qfx2# set chassis aggregated-devices ethernet device-count 3

2. Configure ae0 as a trunk port associated with the v100 VLAN.


{master:0}[edit]
lab@qfx2# set interfaces ae0 unit 0 family ethernet-switching

{master:0}[edit]
lab@qfx2# set interfaces ae0.0 family ethernet-switching interface-mode trunk

{master:0}[edit]
lab@qfx2# set interfaces ae0.0 family ethernet-switching vlan members v100

3. Configure ae0 for LACP as an active participant.


{master:0}[edit]
lab@qfx2# set interfaces ae0 aggregated-ether-options lacp active

4. Configure et-0/0/48 and et-0/0/49 as member links for ae0.


{master:0}[edit]
lab@qfx2# set interfaces et-0/0/48 ether-options 802.3ad ae0

{master:0}[edit]
lab@qfx2# set interfaces et-0/0/49 ether-options 802.3ad ae0

5. Configure the v100 VLAN with a tag value of 100.

Lab 3–8 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
{master:0}[edit]
lab@qfx2# set vlans v100 vlan-id 100
Step 2.8
Activate the configuration changes using the commit command. Once the configuration has
been committed, issue the run show interfaces terse | match ae0 command to
verify the state of the ae0 aggregated Ethernet interface.
{master:0}[edit]
lab@qfx2# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx2# run show interfaces terse | match ae0
et-0/0/48.0 up up aenet --> ae0.0
et-0/0/49.0 up up aenet --> ae0.0
ae0 up up
ae0.0 up up eth-switch

Question: What is the current state of ae0?

Answer: As shown in the sample output, the current state of


ae0 should be administratively and operationally up. If you see
some other state, check your work and, as needed, work with
your instructor.

Step 2.9
Issue the run show lacp statistics interface ae0 command to determine if the
member links associated with ae0 are sending and receiving LACP traffic.
{master:0}[edit]
lab@qfx2# run show lacp statistics interfaces ae0
Aggregated interface: ae0
LACP Statistics: LACP Rx LACP Tx Unknown Rx Illegal Rx
et-0/0/48 246 248 0 0
et-0/0/49 246 248 0 0

Question: Are the member links associated with ae0 sending


and receiving LACP traffic?

Answer: Yes, as shown in the sample output, the member links


associated with ae0 should be sending and receiving LACP
traffic. If you see some other result, check your work and, as
needed, consult with your instructor.

Step 2.10
Continue configuring the required infrastructure elements required to support MC-LAGs on qfx2
by performing the following tasks:

www.juniper.net Multichassis Link Aggregation • Lab 3–9


Data Center Switching
1. Configure irb.100 (10.0.0.2/30) and associate it with VLAN v100.

{master:0}[edit]
lab@qfx2# set interfaces irb unit 100 family inet address 10.0.0.2/30

{master:0}[edit]
lab@qfx2# set vlans v100 l3-interface irb.100

2. Configure ICCP on qfx2 using 10.0.0.2 as the local IP address and 10.0.0.1, which will
soon be assigned to qfx1, as the peer IP address. Assign the following details to the
peering session with qfx1:
– Session establishment hold time: 50
– Backup Peer IP address: Management address of qfx1
– Liveness detection minimum receive interval: 1000
– Liveness detection transmit interval: 1000
{master:0}[edit]
lab@qfx2# edit protocols iccp

{master:0}[edit protocols iccp]


lab@qfx2# set local-ip-addr 10.0.0.2

{master:0}[edit protocols iccp]


lab@qfx2# edit peer 10.0.0.1

{master:0}[edit protocols iccp peer 10.0.0.1]


lab@qfx2# set session-establishment-hold-time 50

{master:0}[edit protocols iccp peer 10.0.0.1]


lab@qfx2# set backup-liveness-detection backup-peer-ip qfx1’s-mgmt-address

{master:0}[edit protocols iccp peer 10.0.0.1]


lab@qfx2# set liveness-detection minimum-receive-interval 1000

{master:0}[edit protocols iccp peer 10.0.0.1]


lab@qfx2# set liveness-detection transmit-interval minimum-interval 1000

{master:0}[edit protocols iccp peer 10.0.0.1]


lab@qfx2#

3. Enable multichassis protection with qfx1 (10.0.0.1) over ae0.


{master:0}[edit protocols iccp peer 10.0.0.1]
lab@qfx2# top

{master:0}[edit]
lab@qfx2# set multi-chassis multi-chassis-protection 10.0.0.1 interface ae0

{master:0}[edit]
lab@qfx2#

Lab 3–10 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
Step 2.11
Activate the configuration changes and view the ICCP details using the run show iccp
command.
{master:0}[edit]
lab@qfx2# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx2# run show iccp

Redundancy Group Information for peer 10.0.0.1


TCP Connection : In progress
Liveliness Detection : Unknown

Backup liveness peer status: Down

Client Application: l2ald_iccpd_client

Client Application: lacpd

Question: What is the status of the ICCP peer?

Answer: As shown in the sample output, the current status of


the TCP connection associated with ICCP should be In
progress. Because qfx1 has not yet been configured for ICCP,
this state is expected. We configure ICCP on qfx1 next.

Step 2.12
Return to the console session opened for qfx1.
On qfx1, continue configuring the required infrastructure elements required to support MC-LAGs
on qfx1 by performing the following tasks:
1. Configure irb.100 (10.0.0.1/30) and associate it with VLAN v100.

{master:0}[edit]
lab@qfx1# set interfaces irb unit 100 family inet address 10.0.0.1/30

{master:0}[edit]
lab@qfx1# set vlans v100 l3-interface irb.100

2. Configure ICCP on qfx1 using 10.0.0.1 as the local IP address and 10.0.0.2, which is
assigned to qfx2, as the peer IP address. Assign the following details to the peering
session with qfx2:
– Session establishment hold time: 50
– Backup Peer IP address: Management address of qfx2
– Liveness detection minimum receive interval: 1000
– Liveness detection transmit interval: 1000
www.juniper.net Multichassis Link Aggregation • Lab 3–11
Data Center Switching
{master:0}[edit]
lab@qfx1# edit protocols iccp

{master:0}[edit protocols iccp]


lab@qfx1# set local-ip-addr 10.0.0.1

{master:0}[edit protocols iccp]


lab@qfx1# edit peer 10.0.0.2

{master:0}[edit protocols iccp peer 10.0.0.2]


lab@qfx1# set session-establishment-hold-time 50

{master:0}[edit protocols iccp peer 10.0.0.2]


lab@qfx1# set backup-liveness-detection backup-peer-ip qfx2’s-mgmt-address

{master:0}[edit protocols iccp peer 10.0.0.2]


lab@qfx1# set liveness-detection minimum-receive-interval 1000

{master:0}[edit protocols iccp peer 10.0.0.2]


lab@qfx1# set liveness-detection transmit-interval minimum-interval 1000

{master:0}[edit protocols iccp peer 10.0.0.2]


lab@qfx1#

3. Enable multichassis protection with qfx2 (10.0.0.2) over ae0.


{master:0}[edit protocols iccp peer 10.0.0.2]
lab@qfx1# top

{master:0}[edit]
lab@qfx1# set multi-chassis multi-chassis-protection 10.0.0.2 interface ae0

{master:0}[edit]
lab@qfx1#

Step 2.13
Activate the configuration changes and view the ICCP details using the run show iccp
command.
{master:0}[edit]
lab@qfx1# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx1# run show iccp

Redundancy Group Information for peer 10.0.0.2


TCP Connection : Established
Liveliness Detection : Up

Backup liveness peer status: Up

Lab 3–12 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
Client Application: l2ald_iccpd_client

Client Application: lacpd

Question: What is the status of the ICCP peer?

Answer: As shown in the sample output, the TCP connection


status of the ICCP peering session should be Established.
You should also see Up for the associated BFD and backup BFD
detection sessions If you see some other state, check your work
and, if needed, consult with your instructor.

Step 2.14
Configure ae1 as an MC-LAG for Server A (ex1), which is associated with the v15 VLAN, by
performing the following tasks:
1. Define the v15 VLAN with a VLAN ID value of 15.
{master:0}[edit]
lab@qfx1# set vlans v15 vlan-id 15

2. Configure et-0/0/50 as a member link assigned to ae1.


{master:0}[edit]
lab@qfx1# set interfaces et-0/0/50 ether-options 802.3ad ae1

3. Configure ae1 as an access port associated with the v15 VLAN.


{master:0}[edit]
lab@qfx1# edit interfaces ae1

{master:0}[edit interfaces ae1]


lab@qfx1# set unit 0 family ethernet-switching vlan members v15

{master:0}[edit interfaces ae1]


lab@qfx1#

4. Associate ae1 with the MC-LAG role using the following details:
– mc-ae-id: 1
– chassis-id: 0
– mode: active-active
– status-control: active
{master:0}[edit interfaces ae1]
lab@qfx1# set aggregated-ether-options mc-ae mc-ae-id 1

{master:0}[edit interfaces ae1]


lab@qfx1# set aggregated-ether-options mc-ae chassis-id 0

{master:0}[edit interfaces ae1]


lab@qfx1# set aggregated-ether-options mc-ae mode active-active

www.juniper.net Multichassis Link Aggregation • Lab 3–13


Data Center Switching
{master:0}[edit interfaces ae1]
lab@qfx1# set aggregated-ether-options mc-ae status-control active

Step 2.15
Attempt to activate the configuration changes by issuing the commit command.
{master:0}[edit interfaces ae1]
lab@qfx1# commit
[edit interfaces ae1 aggregated-ether-options]
'mc-ae'
LACP admin-key must be configured for MC-AE
[edit interfaces ae1 aggregated-ether-options]
'mc-ae'
LACP system-id must be configured for MC-AE
error: commit failed: (statements constraint check failed)

Question: Did the commit operation succeed? If not, why not?

Answer: As shown in the sample output, the commit operation


should not succeed at this time because LACP has not yet been
configured on ae1 with its required admin-key and
system-id. We configure these required elements in the next
step.

Step 2.16
Configure ae1 as an active LACP participant with an admin-key value of 1 and a system-id
value of 01:01:01:01:01:01. Once configured, activate the configuration changes using the
commit command.
{master:0}[edit interfaces ae1]
lab@qfx1# set aggregated-ether-options lacp active

{master:0}[edit interfaces ae1]


lab@qfx1# set aggregated-ether-options lacp admin-key 1

{master:0}[edit interfaces ae1]


lab@qfx1# set aggregated-ether-options lacp system-id 01:01:01:01:01:01

{master:0}[edit interfaces ae1]


lab@qfx1# commit
configuration check succeeds
commit complete

Question: Did the commit operation succeed?

Answer: As shown in the sample output, the commit operation


should succeed now that all of the required LACP parameters
have been configured. If your configuration does not commit
properly, check your work and, if needed, consult with your
instructor.

Lab 3–14 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
Step 2.17
Configure ae2 as an MC-LAG for Server B (ex2), which is associated with the v20 VLAN, by
performing the following tasks:
1. Define the v20 VLAN with a VLAN ID value of 20.
{master:0}[edit interfaces ae1]
lab@qfx1# top

{master:0}[edit]
lab@qfx1# set vlans v20 vlan-id 20

{master:0}[edit]
lab@qfx1#

2. Configure et-0/0/51 as a member link assigned to ae2.


{master:0}[edit]
lab@qfx1# set interfaces et-0/0/51 ether-options 802.3ad ae2

3. Configure ae2 as an access port associated with the v20 VLAN.


{master:0}[edit]
lab@qfx1# edit interfaces ae2

{master:0}[edit interfaces ae2]


lab@qfx1# set unit 0 family ethernet-switching vlan members v20

{master:0}[edit interfaces ae2]


lab@qfx1#

4. Associate ae2 with the MC-LAG role using the following details:
– mc-ae-id: 2
– chassis-id: 1
– mode: active-active
– status-control: standby
{master:0}[edit interfaces ae2]
lab@qfx1# set aggregated-ether-options mc-ae mc-ae-id 2

{master:0}[edit interfaces ae2]


lab@qfx1# set aggregated-ether-options mc-ae chassis-id 1

{master:0}[edit interfaces ae2]


lab@qfx1# set aggregated-ether-options mc-ae mode active-active

{master:0}[edit interfaces ae2]


lab@qfx1# set aggregated-ether-options mc-ae status-control standby

5. Configure ae2 as an active LACP participant with an admin-key value of 2 and a


system-id value of 02:02:02:02:02:02.
{master:0}[edit interfaces ae2]
lab@qfx1# set aggregated-ether-options lacp active

www.juniper.net Multichassis Link Aggregation • Lab 3–15


Data Center Switching

{master:0}[edit interfaces ae2]


lab@qfx1# set aggregated-ether-options lacp admin-key 2

{master:0}[edit interfaces ae2]


lab@qfx1# set aggregated-ether-options lacp system-id 02:02:02:02:02:02

Step 2.18
Activate the configuration changes and return to the operational mode by issuing the commit
and-quit command.
{master:0}[edit interfaces ae2]
lab@qfx1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@qfx1>
Step 2.19
Issue the show interfaces terse | match ae command to determine the state of ae1
and ae2.
{master:0}
lab@qfx1> show interfaces terse | match ae
et-0/0/48.0 up up aenet --> ae0.0
et-0/0/49.0 up up aenet --> ae0.0
et-0/0/50.0 up up aenet --> ae1.0
et-0/0/51.0 up up aenet --> ae2.0
ae0 up up
ae0.0 up up eth-switch
ae1 up down
ae1.0 up down eth-switch
ae2 up down
ae2.0 up down eth-switch

Question: What is the state of ae1 and ae2?

Answer: As shown in the sample output, the state of both ae1


and ae2 are currently down.

Step 2.20
Issue the show interfaces mc-ae command to gather more detailed information on the
state of ae1 and ae2.
{master:0}
lab@qfx1> show interfaces mc-ae
Member Link : ae1
Current State Machine's State: mcae application connect error
Local Status : standby
Local State : up

Lab 3–16 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
Peer Status : Unknown
Peer State : down
Logical Interface : ae1.0
Topology Type : bridge
Local State : up
Peer State : Unknown
Peer Ip/MCP/State : 10.0.0.2 ae0.0 up

Member Link : ae2


Current State Machine's State: mcae application connect error
Local Status : standby
Local State : up
Peer Status : Unknown
Peer State : down
Logical Interface : ae2.0
Topology Type : bridge
Local State : up
Peer State : Unknown
Peer Ip/MCP/State : 10.0.0.2 ae0.0 up

Question: What detailed state information related to ae1 and


ae2 does the output provide?

Answer: As shown in the sample output, the local state of both


ae1 and ae2 is up with a status of standby. Note that the
standby status, in this context, simply means that the interface
has not yet received packets from the remote MC-LAG peer and
is not related to the control of the peering relationship. We also
see that the peer status is Unknown with a state of down. This
is expected at this point because qfx2 has not yet been
configured with these MC-LAGs. We configure qfx2 in the
subsequent steps.

Step 2.21
Return to the console opened for qfx2.
On qfx2, configure ae1 as an MC-LAG for Server A (ex1), which is associated with the v15 VLAN,
by performing the following tasks:
1. Define the v15 VLAN with a VLAN ID value of 15.
{master:0}[edit]
lab@qfx2# set vlans v15 vlan-id 15
2. Configure et-0/0/51 as a member link assigned to ae1.
{master:0}[edit]
lab@qfx2# set interfaces et-0/0/51 ether-options 802.3ad ae1

3. Configure ae1 as an access port associated with the v15 VLAN.


{master:0}[edit]
lab@qfx2# edit interfaces ae1

www.juniper.net Multichassis Link Aggregation • Lab 3–17


Data Center Switching
{master:0}[edit interfaces ae1]
lab@qfx2# set unit 0 family ethernet-switching vlan members v15

{master:0}[edit interfaces ae1]


lab@qfx2#

4. Associate ae1 with the MC-LAG role using the following details:
– mc-ae-id: 1
– chassis-id: 1
– mode: active-active
– status-control: standby
{master:0}[edit interfaces ae1]
lab@qfx2# set aggregated-ether-options mc-ae mc-ae-id 1

{master:0}[edit interfaces ae1]


lab@qfx2# set aggregated-ether-options mc-ae chassis-id 1

{master:0}[edit interfaces ae1]


lab@qfx2# set aggregated-ether-options mc-ae mode active-active

{master:0}[edit interfaces ae1]


lab@qfx2# set aggregated-ether-options mc-ae status-control standby

5. Configure ae1 as an active LACP participant with an admin-key value of 1 and a


system-id value of 01:01:01:01:01:01.
{master:0}[edit interfaces ae1]
lab@qfx2# set aggregated-ether-options lacp active

{master:0}[edit interfaces ae1]


lab@qfx2# set aggregated-ether-options lacp admin-key 1

{master:0}[edit interfaces ae1]


lab@qfx2# set aggregated-ether-options lacp system-id 01:01:01:01:01:01

Step 2.22
Configure ae2 as an MC-LAG for Server B (ex2), which is associated with the v20 VLAN, by
performing the following tasks:
1. Define the v20 VLAN with a VLAN ID value of 20.
{master:0}[edit interfaces ae1]
lab@qfx2# top

{master:0}[edit]
lab@qfx2# set vlans v20 vlan-id 20

{master:0}[edit]
lab@qfx2#

2. Configure et-0/0/50 as a member link assigned to ae2.

Lab 3–18 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
{master:0}[edit]
lab@qfx2# set interfaces et-0/0/50 ether-options 802.3ad ae2

3. Configure ae2 as an access port associated with the v20 VLAN.


{master:0}[edit]
lab@qfx2# edit interfaces ae2

{master:0}[edit interfaces ae2]


lab@qfx2# set unit 0 family ethernet-switching vlan members v20

{master:0}[edit interfaces ae2]


lab@qfx2#

4. Associate ae2 with the MC-LAG role using the following details:
– mc-ae-id: 2
– chassis-id: 0
– mode: active-active
– status-control: active
{master:0}[edit interfaces ae2]
lab@qfx2# set aggregated-ether-options mc-ae mc-ae-id 2

{master:0}[edit interfaces ae2]


lab@qfx2# set aggregated-ether-options mc-ae chassis-id 0

{master:0}[edit interfaces ae2]


lab@qfx2# set aggregated-ether-options mc-ae mode active-active

{master:0}[edit interfaces ae2]


lab@qfx2# set aggregated-ether-options mc-ae status-control active

5. Configure ae2 as an active LACP participant with an admin-key value of 2 and a


system-id value of 02:02:02:02:02:02.
{master:0}[edit interfaces ae2]
lab@qfx2# set aggregated-ether-options lacp active

{master:0}[edit interfaces ae2]


lab@qfx2# set aggregated-ether-options lacp admin-key 2

{master:0}[edit interfaces ae2]


lab@qfx2# set aggregated-ether-options lacp system-id 02:02:02:02:02:02
Step 2.23
Activate the configuration changes and return to the operational mode by issuing the commit
and-quit command.
{master:0}[edit interfaces ae2]
lab@qfx2# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

www.juniper.net Multichassis Link Aggregation • Lab 3–19


Data Center Switching
{master:0}
lab@qfx2>
Step 2.24
Issue the show interfaces terse | match ae command to determine the state of ae1
and ae2.
{master:0}
lab@qfx2> show interfaces terse | match ae
et-0/0/48.0 up up aenet --> ae0.0
et-0/0/49.0 up up aenet --> ae0.0
et-0/0/50.0 up up aenet --> ae2.0
et-0/0/51.0 up up aenet --> ae1.0
ae0 up up
ae0.0 up up eth-switch
ae1 up up
ae1.0 up up eth-switch
ae2 up up
ae2.0 up up eth-switch

Question: What is the state of ae1 and ae2?

Answer: As shown in the sample output, the state of both ae1


and ae2 should now be up.

Step 2.25
Issue the show interfaces mc-ae command to gather more detailed information on the
state of ae1 and ae2.
{master:0}
lab@qfx2> show interfaces mc-ae
Member Link : ae1
Current State Machine's State: mcae active state
Local Status : active
Local State : up
Peer Status : active
Peer State : up
Logical Interface : ae1.0
Topology Type : bridge
Local State : up
Peer State : up
Peer Ip/MCP/State : 10.0.0.1 ae0.0 up

Member Link : ae2


Current State Machine's State: mcae active state
Local Status : active
Local State : up
Peer Status : active
Peer State : up
Logical Interface : ae2.0
Topology Type : bridge

Lab 3–20 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
Local State : up
Peer State : up
Peer Ip/MCP/State : 10.0.0.1 ae0.0 up

Question: What detailed state information related to ae1 and


ae2 does the output provide?

Answer: As shown in the sample output, the local and peer


(qfx1 in this case) status and state of both ae1 and ae2 is
active and up respectively. You should also see that the
current state of the MC-LAG state machine should show the
mcae active state. If you see some other state in your
environment, check your work and, if needed, consult with your
instructor.

Step 2.26
Return to the console session opened to ex1.
On ex1, which is functioning as Server A, attempt to ping Host X device (172.25.15.100).
{master:0}
lab@ex1-ServerA> ping 172.25.15.100 rapid count 25
PING 172.25.15.100 (172.25.15.100): 56 data bytes
.........................
--- 172.25.15.100 ping statistics ---
25 packets transmitted, 0 packets received, 100% packet loss

{master:0}
lab@ex1-ServerA>

Question: Did the ping operation succeed? If not, can you


explain why not?

Answer: As shown in the sample output, the ping operation


should not succeed at this time. Because we have not yet
associated the v15 and v20 VLANs with the ICL-PL (ae0)
interface or the ge-0/0/0 interface, which connects to Host X,
we do not have a clear Layer 2 path suitable of supporting the
communications.

Step 2.27
Return to the console for qfx2.
On qfx2, enter configuration mode and associate the ae0 trunk port with the v15 and v20
VLANs. Once the configuration has been updated, commit the change.

{master:0}
lab@qfx2> configure
Entering configuration mode

www.juniper.net Multichassis Link Aggregation • Lab 3–21


Data Center Switching
{master:0}[edit]
lab@qfx2# show interfaces ae0
aggregated-ether-options {
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members v100;
}
}
}

{master:0}[edit]
lab@qfx2# set interfaces ae0.0 family ethernet-switching vlan members v15

{master:0}[edit]
lab@qfx2# set interfaces ae0.0 family ethernet-switching vlan members v20

{master:0}[edit]
lab@qfx2# show interfaces ae0
aggregated-ether-options {
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members [ v100 v15 v20 ];
}
}
}

{master:0}[edit]
lab@qfx2# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx2#
Step 2.28
Issue the run show vlans command to determine the current VLAN assignments.
{master:0}[edit]
lab@qfx2# run show vlans

Routing instance VLAN name Tag Interfaces


default-switch v100 100
ae0.0*

Lab 3–22 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
default-switch v15 15
ae0.0*
ae1.0*
default-switch v20 20
ae0.0*
ae2.0*

Question: Which interfaces are currently assigned to the


defined VLANs on qfx2?

Answer: As shown in the sample output, ae0 should be


assigned to the v100, v15, and v20 VLANs while ae1 and ae2
should be assigned to the v15 and v20 VLANs respectively. If
you see VLAN assignments that differ from what is shown in the
sample output, check your configuration and, if needed, consult
with your instructor.

Step 2.29
Return to the console for qfx1.
On qfx1, enter configuration mode and associate the ae0 trunk port with the v15 and v20
VLANs.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# show interfaces ae0
aggregated-ether-options {
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members v100;
}
}
}

{master:0}[edit]
lab@qfx1# set interfaces ae0.0 family ethernet-switching vlan members v15

{master:0}[edit]
lab@qfx1# set interfaces ae0.0 family ethernet-switching vlan members v20

{master:0}[edit]
lab@qfx1# show interfaces ae0
aggregated-ether-options {
lacp {

www.juniper.net Multichassis Link Aggregation • Lab 3–23


Data Center Switching
active;
}
}
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members [ v100 v15 v20 ];
}
}
}
Step 2.30
Configure ge-0/0/0 as a trunk port and associate it with the v15 and v20 VLANs. Once the
configuration has been updated, commit the change.
{master:0}[edit]
lab@qfx1# edit interfaces ge-0/0/0 unit 0

{master:0}[edit interfaces ge-0/0/0 unit 0]


lab@qfx1# set family ethernet-switching interface-mode trunk

{master:0}[edit interfaces ge-0/0/0 unit 0]


lab@qfx1# set family ethernet-switching vlan members v15

{master:0}[edit interfaces ge-0/0/0 unit 0]


lab@qfx1# set family ethernet-switching vlan members v20

{master:0}[edit interfaces ge-0/0/0 unit 0]


lab@qfx1# top

{master:0}[edit]
lab@qfx1# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx1#
Step 2.31
Issue the run show vlans command to determine the current VLAN assignments.
{master:0}[edit]
lab@qfx1# run show vlans

Routing instance VLAN name Tag Interfaces


default-switch v100 100
ae0.0*
default-switch v15 15
ae0.0*
ae1.0*
ge-0/0/0.0*

Lab 3–24 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
default-switch v20 20
ae0.0*
ae2.0*
ge-0/0/0.0*

Question: Which interfaces are currently assigned to the


defined VLANs on qfx1?

Answer: As shown in the sample output, ae0 should be


assigned to the v100, v15, and v20 VLANs; ge-0/0/0 should be
assigned to the v15 and v20 VLANs; and ae1 and ae2 should
be assigned to the v15 and v20 VLANs respectively. If you see
VLAN assignments that differ from what is shown in the sample
output, check your configuration and, if needed, consult with
your instructor.

Step 2.32
Return to the console session opened to ex1.
On ex1, which is functioning as Server A, attempt to ping Host X device (172.25.15.100) once
again.
{master:0}
lab@ex1-ServerA> ping 172.25.15.100 rapid count 25
PING 172.25.15.100 (172.25.15.100): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!
--- 172.25.15.100 ping statistics ---
25 packets transmitted, 25 packets received, 0% packet loss
round-trip min/avg/max/stddev = 19.714/22.469/36.724/3.091 ms

Question: Did the ping operation succeed?

Answer: As shown in the sample output, the ping operation


should succeed now that there is a clear Layer 2
communications path between Server A and Host X in the v15
VLAN. Note that with this configuration, Server B (ex2) should
also be able to communicate with Host X in the v20 VLAN.

Part 3: Enabling Layer 3 Gateway Services

In this lab part, you enable Layer 3 gateway services on qfx1 and qfx2 for the subnets
associated with the v15 and v20 VLANs. You will then verify reachability between Server A and
Server B, which reside on different Layer 3 subnets.
Step 3.1
On ex1, which is functioning as Server A, attempt to ping ex2, which is functioning as Server B,
using the 172.25.20.22 destination address.
{master:0}
lab@ex1-ServerA> ping 172.25.20.22 rapid count 25
www.juniper.net Multichassis Link Aggregation • Lab 3–25
Data Center Switching
PING 172.25.20.22 (172.25.20.22): 56 data bytes
.........................
--- 172.25.20.22 ping statistics ---
25 packets transmitted, 0 packets received, 100% packet loss

Question: Did the ping operation succeed?

Answer: As shown in the sample output, the ping operation


should not succeed at this time. We will remedy this in
subsequent lab steps.

Step 3.2
Return to the console connection opened to qfx1.
On qfx1, configure Layer 3 gateway services for the 172.25.15.0/24 subnet as follows:
1. Configure irb.15 as a Layer 3 interface with the 172.25.15.101/24 IP address.
{master:0}[edit]
lab@qfx1# edit interfaces irb unit 15

{master:0}[edit interfaces irb unit 15]


lab@qfx1# set family inet address 172.25.15.101/24

{master:0}[edit interfaces irb unit 15]


lab@qfx1#

2. Enable VRRP under irb.15’s newly defined IP address with the following values:
– vrrp-group: 15
– virtual-address: 172.25.15.1
– priority: 200
{master:0}[edit interfaces irb unit 15]
lab@qfx1# edit family inet address 172.25.15.101/24

{master:0}[edit interfaces irb unit 15 family inet address 172.25.15.101/24]


lab@qfx1# set vrrp-group 15 virtual-address 172.25.15.1

{master:0}[edit interfaces irb unit 15 family inet address 172.25.15.101/24]


lab@qfx1# set vrrp-group 15 priority 200

{master:0}[edit interfaces irb unit 15 family inet address 172.25.15.101/24]


lab@qfx1#

3. Associate irb.15 with the v15 VLAN.


{master:0}[edit interfaces irb unit 15 family inet address 172.25.15.101/24]
lab@qfx1# top

{master:0}[edit]
lab@qfx1# set vlans v15 l3-interface irb.15

Lab 3–26 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
{master:0}[edit]
lab@qfx1#
Step 3.3
Configure Layer 3 gateway services for the 172.25.20.0/24 subnet as follows:
1. Configure irb.20 as a Layer 3 interface with the 172.25.20.101/24 IP address.
{master:0}[edit]
lab@qfx1# edit interfaces irb unit 20

{master:0}[edit interfaces irb unit 20]


lab@qfx1# set family inet address 172.25.20.101/24

{master:0}[edit interfaces irb unit 20]


lab@qfx1#

2. Enable VRRP under irb.20’s newly defined IP address with the following values:
– vrrp-group: 20
– virtual-address: 172.25.20.1
– priority: 100
{master:0}[edit interfaces irb unit 20]
lab@qfx1# edit family inet address 172.25.20.101/24

{master:0}[edit interfaces irb unit 20 family inet address 172.25.20.101/24]


lab@qfx1# set vrrp-group 20 virtual-address 172.25.20.1

{master:0}[edit interfaces irb unit 20 family inet address 172.25.20.101/24]


lab@qfx1# set vrrp-group 20 priority 100

{master:0}[edit interfaces irb unit 20 family inet address 172.25.20.101/24]


lab@qfx1#

3. Associate irb.20 with the v20 VLAN.


{master:0}[edit interfaces irb unit 20 family inet address 172.25.20.101/24]
lab@qfx1# top

{master:0}[edit]
lab@qfx1# set vlans v20 l3-interface irb.20

{master:0}[edit]
lab@qfx1#
Step 3.4
Activate the configuration changes using the commit command. Next, issue the run show
vrrp summary command to determine the current state of VRRP.
{master:0}[edit]
lab@qfx1# commit
configuration check succeeds
commit complete

www.juniper.net Multichassis Link Aggregation • Lab 3–27


Data Center Switching
{master:0}[edit]
lab@qfx1# run show vrrp summary
Interface State Group VR state VR Mode Type Address
irb.15 up 15 master Active lcl 172.25.15.101
vip 172.25.15.1
irb.20 up 20 master Active lcl 172.25.20.101
vip 172.25.20.1

Question: What is the current interface and virtual router (VR)


states for VRRP groups 15 and 20?

Answer: As shown in the sample output, the current interface


and virtual router (VR) states on qfx1 for both VRRP groups are
up and master respectively.

Note
The intended design goal is to have qfx1 serve as master for VRRP
group 15 and qfx2 to serve as master for VRRP group 20. The VRRP
master for a given group is determined by the priority setting, where
the higher value is preferred over the lower value. We configure
qfx2 to support this design goal in subsequent lab steps.

Step 3.5
Return to the console connection opened to qfx2.
On qfx2, configure Layer 3 gateway services for the 172.25.15.0/24 subnet as follows:
1. Configure irb.15 as a Layer 3 interface with the 172.25.15.102/24 IP address.
{master:0}[edit]
lab@qfx2# edit interfaces irb unit 15

{master:0}[edit interfaces irb unit 15]


lab@qfx2# set family inet address 172.25.15.102/24

{master:0}[edit interfaces irb unit 15]


lab@qfx2#

2. Enable VRRP under irb.15’s newly defined IP address with the following values:
– vrrp-group: 15
– virtual-address: 172.25.15.1
– priority: 100
{master:0}[edit interfaces irb unit 15]
lab@qfx2# edit family inet address 172.25.15.102/24

{master:0}[edit interfaces irb unit 15 family inet address 172.25.15.102/24]


lab@qfx2# set vrrp-group 15 virtual-address 172.25.15.1

{master:0}[edit interfaces irb unit 15 family inet address 172.25.15.102/24]


lab@qfx2# set vrrp-group 15 priority 100

Lab 3–28 • Multichassis Link Aggregation www.juniper.net


Data Center Switching

{master:0}[edit interfaces irb unit 15 family inet address 172.25.15.102/24]


lab@qfx2#

3. Associate irb.15 with the v15 VLAN.


{master:0}[edit interfaces irb unit 15 family inet address 172.25.15.102/24]
lab@qfx2# top

{master:0}[edit]
lab@qfx2# set vlans v15 l3-interface irb.15

{master:0}[edit]
lab@qfx2#
Step 3.6
Configure Layer 3 gateway services for the 172.25.20.0/24 subnet as follows:
1. Configure irb.20 as a Layer 3 interface with the 172.25.20.102/24 IP address.
{master:0}[edit]
lab@qfx2# edit interfaces irb unit 20

{master:0}[edit interfaces irb unit 20]


lab@qfx2# set family inet address 172.25.20.102/24

{master:0}[edit interfaces irb unit 20]


lab@qfx2#

2. Enable VRRP under irb.20’s newly defined IP address with the following values:
– vrrp-group: 20
– virtual-address: 172.25.20.1
– priority: 200
{master:0}[edit interfaces irb unit 20]
lab@qfx2# edit family inet address 172.25.20.102/24

{master:0}[edit interfaces irb unit 20 family inet address 172.25.20.102/24]


lab@qfx2# set vrrp-group 20 virtual-address 172.25.20.1

{master:0}[edit interfaces irb unit 20 family inet address 172.25.20.102/24]


lab@qfx2# set vrrp-group 20 priority 200

{master:0}[edit interfaces irb unit 20 family inet address 172.25.20.102/24]


lab@qfx2#

3. Associate irb.20 with the v20 VLAN.


{master:0}[edit interfaces irb unit 20 family inet address 172.25.20.102/24]
lab@qfx2# top

{master:0}[edit]
lab@qfx2# set vlans v20 l3-interface irb.20

{master:0}[edit]

www.juniper.net Multichassis Link Aggregation • Lab 3–29


Data Center Switching
lab@qfx2#
Step 3.7
Activate the configuration changes using the commit command. Next, issue the run show
vrrp summary command to determine the current state of VRRP.
{master:0}[edit]
lab@qfx2# commit
configuration check succeeds
commit complete

{master:0}[edit]
lab@qfx2# run show vrrp summary
Interface State Group VR state VR Mode Type Address
irb.15 up 15 backup Active lcl 172.25.15.102
vip 172.25.15.1
irb.20 up 20 master Active lcl 172.25.20.102
vip 172.25.20.1

Question: What is the current interface and virtual router (VR)


states for VRRP groups 15 and 20? Based on the configured
values, is this the desired state?

Answer: As shown in the sample output, the current interface


and virtual router (VR) states on qfx2 for VRRP group 15 are up
and backup while on VRRP group 20 they are up and master
respectively. Based on the configured values on qfx1 and qfx2,
this is the expected and desired state of VRRP.

Step 3.8
Return to the console connection opened for ex1.
On ex1, which is functioning as Server A, attempt to ping ex2, which is functioning as Server B,
using the 172.25.20.22 destination address once again.
{master:0}
lab@ex1-ServerA> ping 172.25.20.22 rapid count 25
PING 172.25.20.22 (172.25.20.22): 56 data bytes
..!!!!!!!!!!!!!!!!!!!!!!!
--- 172.25.20.22 ping statistics ---
25 packets transmitted, 23 packets received, 8% packet loss
round-trip min/avg/max/stddev = 1.810/2.041/3.207/0.299 ms

{master:0}
lab@ex1-ServerA> ping 172.25.20.22 rapid count 25
PING 172.25.20.22 (172.25.20.22): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!
--- 172.25.20.22 ping statistics ---
25 packets transmitted, 25 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.871/2.298/3.988/0.621 ms

Lab 3–30 • Multichassis Link Aggregation www.juniper.net


Data Center Switching
Question: Did the ping operation succeed?

Answer: As shown in the sample output, the ping operation


should now succeed. Note that you may, as shown in the
sample output, see some initial packet loss. This is caused by
the lack of the required ARP entries on the MC-LAG peers
performing the gateway services. After the initial ARP process is
completed, you should not see any more packet loss.

Step 3.9
Log out of your switches and close the console sessions.
{master:0}
lab@ex1-ServerA> exit

ex1-ServerA (ttyu0)

login:

{master:0}
lab@ex2-ServerB> exit

ex2-ServerB (ttyu0)

login:

{master:0}[edit]
lab@qfx1# exit configuration-mode
Exiting configuration mode

{master:0}
lab@qfx1> exit

qfx1 (ttyd0)

login:

{master:0}[edit]
lab@qfx2# exit configuration-mode
Exiting configuration mode

www.juniper.net Multichassis Link Aggregation • Lab 3–31


Data Center Switching
{master:0}
lab@qfx2> exit

qfx2 (ttyd0)

login:

STOP Tell your instructor that you have completed this lab.

Lab 3–32 • Multichassis Link Aggregation www.juniper.net


Data Center Switching

www.juniper.net Multichassis Link Aggregation • Lab 3–33


Data Center Switching

Lab 3–34 • Multichassis Link Aggregation www.juniper.net


Lab
Mixed Virtual Chassis

Overview
In this lab, you provision a mixed Virtual Chassis using a combination of two QFX5100 Series
switches and two EX4300 Series switches. The QFX5100 Series switches will act as master and
backup Routing Engines (REs). The EX4300 Series switches will act as linecards for the Virtual
Chassis.
By completing this lab, you will perform the following tasks:
• Access your assigned switches.
• Configure the master RE for dynamic provisioning of the Virtual Chassis.
• Enable the Virtual Chassis Ports (VCPs) on each of the switches.
• Verify that each member switch has taken on the appropriate role.
• Configure network interfaces on the Virtual Chassis.
• Verify that the Virtual Chassis appears to act as a single switch.
• Reset the members of the Virtual Chassis into individual standalone switches.

Part 1: Analyze the Topology

In this lab part, you will review the lab diagram to determine the roles that each switch will take
as part of the Virtual Chassis. Use the lab diagram titled “Network Diagram: Mixed Virtual
Chassis Lab” for this part of the lab.
Step 1.1
Take a look at the diagram labeled “Network Diagram: Mixed Virtual Chassis Lab”.

Question: Which switch is supposed to be the master RE for the


mixed Virtual Chassis?

Answer: qfx1 is supposed to be the master RE for the Virtual


Chassis.

www.juniper.net Mixed Virtual Chassis • Lab 4–1


Data Center Switching
Question: Which switch is supposed to be the backup RE for the
mixed Virtual Chassis?

Answer: qfx2 is supposed to be the backup RE for the Virtual


Chassis.

Question: Which switches are supposed to be linecards for the


Virtual Chassis?

Answer: ex1 and ex2 will be linecards for the Virtual Chassis.

Question: What do you think is the purpose of the two virtual


routers?

Answer: The two virtual routers will be used to generate


IP-based traffic that will traverse the Virtual Chassis.

Part 2: Logging In Using the CLI

In this lab part, you become familiar with the access details used to connect to the lab
equipment. Once you are familiar with the access details, you will use the CLI to log in to your
team’s designated switches. Once you have logged in to your devices you will make sure your
devices are running the appropriate starting configurations for this lab. Use the lab diagram
titled “Network Diagram: Mixed Virtual Chassis Lab” for this part of the lab.
Step 2.1
Ensure that you know to which switches you have been assigned. Check with your instructor if
you are not certain. Consult the management network diagram to determine your switches’
management addresses.

Question: What are the management addresses assigned to


your switches?

Answer: The answer varies and depends on your assigned


environment and devices. If you are unsure of your assignment,
ask your instructor.

Step 2.2
Using console access, connect to your qfx1 switch and log in using the lab and lab123 login
credentials.
qfx1 (ttyd0)

login: lab
Password:

Lab 4–2 • Mixed Virtual Chassis www.juniper.net


Data Center Switching

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1>

Question: All switches in our lab default to Virtual Chassis


mode. What member is the master RE for the Virtual Chassis to
which qfx1 belongs?

Answer: Member 0 should be the master RE of the Virtual


Chassis. You can tell by the prompt after you log in
(master:0). If member 0 is not the master RE for the Virtual
Chassis, please notify your instructor.

Step 2.3
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@qfx1> show virtual-chassis status

Virtual Chassis ID: deb2.dc91.9c55


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

Question: How many members exist as part of the Virtual


Chassis?

Answer: Member 0 is the only member of the Virtual Chassis. If


member 0 is not the only member of the Virtual Chassis, please
notify your instructor.

Question: Which switch is the only member of the Virtual


Chassis? What type of switch is it?

Answer: qfx1, a QFX5100-48s-6q, is the only member of the


Virtual Chassis.

Step 2.4
View the status of the Virtual Chassis’ VCPs by issuing the show virtual-chassis
vc-port command.

www.juniper.net Mixed Virtual Chassis • Lab 4–3


Data Center Switching
{master:0}
lab@qfx1> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------

{master:0}
lab@qfx1>

Question: Which VCPs are enabled for the Virtual Chassis?

Answer: No VCP interfaces should be enabled. If any VCPs have


been enabled, please notify your instructor.

Step 2.5
Issue the show chassis hardware command to determine the serial number for qfx1. Write
the serial number on the appropriate line on your lab diagram.
{master:0}
lab@qfx1> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis VF3714170305 QFX5100-48S-6Q
Pseudo CB 0
Routing Engine 0 BUILTIN BUILTIN QFX Routing Engine
FPC 0 REV 05 650-056264 VF3714170305 QFX5100-48S-6Q
CPU BUILTIN BUILTIN FPC CPU
PIC 0 BUILTIN BUILTIN 48x10G-6x40G
Xcvr 0 REV 02 740-013111 D275324 SFP-T
Xcvr 48 REV 01 740-038623 MOC14136231262 QSFP+-40G-CU1M
Xcvr 49 REV 01 740-038623 MOC14136231597 QSFP+-40G-CU1M
Xcvr 50 REV 01 740-038624 141460MJ QSFP+-40G-CU3M
Xcvr 51 REV 01 740-038624 1412603F QSFP+-40G-CU3M
Power Supply 0 REV 03 740-041741 1GA24110534 JPSU-650W-AC-AFO
Power Supply 1 REV 03 740-041741 1GA24110529 JPSU-650W-AC-AFO
Fan Tray 0 QFX5100 Fan Tray 0, Front
to Back Airflow - AFO
Fan Tray 1 QFX5100 Fan Tray 1, Front
to Back Airflow - AFO
Fan Tray 2 QFX5100 Fan Tray 2, Front
to Back Airflow - AFO
Fan Tray 3 QFX5100 Fan Tray 3, Front
to Back Airflow - AFO
Fan Tray 4 QFX5100 Fan Tray 4, Front
to Back Airflow - AFO

Question: What is the serial number for qfx1?

Answer: The answer will vary by student. In this example, the


serial number is VF3714170305.

Lab 4–4 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Question: How many FPCs exist?

Answer: There is only one FPC, FPC 0.

Step 2.6
Enter configuration mode and load the lab4-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# load override dcx/lab4-start.config
load complete

{master:0}[edit]
lab@qfx1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@qfx1>
Step 2.7
View the configuration for qfx1 by issuing the show configuration command.
{master:0}
lab@qfx1> show configuration
system {
host-name qfx1;
root-authentication {
encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA
ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/
O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/
gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/
Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/
zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBHx9
elwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF2KHB
SIxL51lmIDW8Gql9hJfD/Dr/
NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu2C
8UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/
g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= configurator@server1.he"; ##
SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA

www.juniper.net Mixed Virtual Chassis • Lab 4–5


Data Center Switching
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
interfaces {
ge-1/0/14 {
vlan-tagging;
unit 301 {
vlan-id 301;
family inet {
address 172.16.1.2/24;
}
}
}
ge-2/0/7 {
vlan-tagging;
unit 301 {
vlan-id 301;
family inet {
address 172.16.1.1/24;
}
}
}
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.155/26;
}
}
}
}
routing-instances {
vr1 {
instance-type virtual-router;
interface ge-2/0/7.301;

Lab 4–6 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
}
vr2 {
instance-type virtual-router;
interface ge-1/0/14.301;
}
}

Question: Which interfaces have been configured?

Answer: The vme, ge-1/0/14, and ge-2/0/7 interfaces have


been configured.

Question: What is the IP address of the VME interface?

Answer: The answer will vary by student. In the example, the IP


address of qfx1’s vme interface is 10.210.14.155.

Step 2.8
Open a new and separate console session to your qfx2 switch and log in using the lab and
lab123 login credentials.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx2>

Question: All switches in our lab default to Virtual Chassis


mode. What member is the master RE for the Virtual Chassis to
which qfx2 belongs?

Answer: Member 0 should be the master RE of the Virtual


Chassis. You can tell by the prompt after you log in
(master:0). If member 0 is not the master RE for the Virtual
Chassis, please notify your instructor.

Step 2.9
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@qfx2> show virtual-chassis status

Virtual Chassis ID: deb2.dc91.9c55


Virtual Chassis Mode: Enabled

www.juniper.net Mixed Virtual Chassis • Lab 4–7


Data Center Switching
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170306 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

Question: How many members exist as part of the Virtual


Chassis?

Answer: Member 0 is the only member of the Virtual Chassis. If


member 0 is not the only member of the Virtual Chassis, please
notify your instructor.

Question: Which switch is the only member of the Virtual


Chassis? What type of switch is it?

Answer: qfx2, a QFX5100-48s-6q, is the only member of the


Virtual Chassis.

Step 2.10
View the status of the Virtual Chassis’ VCPs by issuing the show virtual-chassis
vc-port command.
{master:0}
lab@qfx2> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------

{master:0}
lab@qfx2>

Question: Which VCPs are enabled for the Virtual Chassis?

Answer: No VCP interfaces should be enabled. If any VCPs have


been enabled, please notify your instructor.

Step 2.11
Issue the show chassis hardware command to determine the serial number for qfx2. Write
the serial number on the appropriate line on your lab diagram.
{master:0}
lab@qfx2> show chassis hardware

Lab 4–8 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Hardware inventory:
Item Version Part number Serial number Description
Chassis VF3714170306 QFX5100-48S-6Q
Pseudo CB 0
Routing Engine 0 BUILTIN BUILTIN QFX Routing Engine
FPC 0 REV 05 650-056264 VF3714170306 QFX5100-48S-6Q
CPU BUILTIN BUILTIN FPC CPU
PIC 0 BUILTIN BUILTIN 48x10G-6x40G
Xcvr 0 REV 02 740-013111 B388216 SFP-T
Xcvr 48 REV 01 740-038623 MOC14136231262 QSFP+-40G-CU1M
Xcvr 49 REV 01 740-038623 MOC14136231597 QSFP+-40G-CU1M
Xcvr 50 REV 01 740-038624 1414629M QSFP+-40G-CU3M
Xcvr 51 REV 01 740-038624 14146087 QSFP+-40G-CU3M
Power Supply 0 REV 03 740-041741 1GA24110532 JPSU-650W-AC-AFO
Power Supply 1 REV 03 740-041741 1GA24110533 JPSU-650W-AC-AFO
Fan Tray 0 QFX5100 Fan Tray 0, Front
to Back Airflow - AFO
Fan Tray 1 QFX5100 Fan Tray 1, Front
to Back Airflow - AFO
Fan Tray 2 QFX5100 Fan Tray 2, Front
to Back Airflow - AFO
Fan Tray 3 QFX5100 Fan Tray 3, Front
to Back Airflow - AFO
Fan Tray 4 QFX5100 Fan Tray 4, Front
to Back Airflow - AFO

Question: What is the serial number for qfx2?

Answer: The answer will vary by student. In this example, the


serial number is VF3714170306.

Question: How many FPCs exist?

Answer: There is only one FPC, FPC 0.

Step 2.12
Enter configuration mode and load the lab4-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{master:0}
lab@qfx2> configure
Entering configuration mode

{master:0}[edit]
lab@qfx2# load override dcx/lab4-start.config
load complete

{master:0}[edit]
lab@qfx2# commit and-quit
configuration check succeeds
commit complete

www.juniper.net Mixed Virtual Chassis • Lab 4–9


Data Center Switching
Exiting configuration mode

{master:0}
lab@qfx2>
Step 2.13
View the configuration for qfx2 by issuing the show configuration command.
{master:0}
lab@qfx2> show configuration
## Last commit: 2014-09-26 19:47:17 UTC by lab
version 13.2X51-D21.1;
system {
host-name qfx2;
root-authentication {
encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA
ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/
O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/
gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/
Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/
zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBHx9e
lwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF2KHBSI
xL51lmIDW8Gql9hJfD/Dr/
NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu2C8
UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/
g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= configurator@server1.he"; ##
SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;

Lab 4–10 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
}
}
}
interfaces {
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.156/26;
}
}
}
}

Question: Which interfaces have been configured?

Answer: Only the vme interface has been configured.

Question: What is the IP address of the VME interface?

Answer: The answer will vary by student. In the example, the IP


address of qfx2’s vme interface is 10.210.14.156.

Step 2.14
Open a new and separate console session to your ex1 switch and log in using the lab and
lab123 login credentials.
ex1-ServerA (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex1-ServerA>

Question: All switches in our lab default to Virtual Chassis


mode. What member is the master RE for the Virtual Chassis to
which ex1 belongs?

Answer: Member 0 should be the master RE of the Virtual


Chassis. You can tell by the prompt after you log in
(master:0). If member 0 is not the master RE for the Virtual
Chassis, please notify your instructor.

Step 2.15
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.

www.juniper.net Mixed Virtual Chassis • Lab 4–11


Data Center Switching
{master:0}
lab@ex1-ServerA> show virtual-chassis status

Virtual Chassis ID: 51e4.3289.1627


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt PG3713360118 ex4300-24t 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

Question: How many members exist as part of the Virtual


Chassis?

Answer: Member 0 is the only member of the Virtual Chassis. If


member 0 is not the only member of the Virtual Chassis, please
notify your instructor.

Question: Which switch is the only member of the Virtual


Chassis? What type of switch is it?

Answer: ex1, a EX4300-24t, is the only member of the Virtual


Chassis.

Step 2.16
View the status of the Virtual Chassis’ VCPs by issuing the show virtual-chassis
vc-port command.
{master:0}
lab@ex1-ServerA> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------

{master:0}
lab@ex1-ServerA>

Question: Which VCPs are enabled for the Virtual Chassis?

Answer: No VCP interfaces should be enabled. If any VCPs have


been enabled, please notify your instructor.

Step 2.17
Issue the show chassis hardware command to determine the serial number for ex1. Write
the serial number on the appropriate line on your lab diagram.
{master:0}
lab@ex1-ServerA> show chassis hardware
Hardware inventory:

Lab 4–12 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Item Version Part number Serial number Description
Chassis PG3713360118 EX4300-24T
Routing Engine 0 REV 06 650-044936 PG3713360118 EX4300-24T
FPC 0 REV 06 650-044936 PG3713360118 EX4300-24T
CPU BUILTIN BUILTIN FPC CPU
PIC 0 REV 06 BUILTIN BUILTIN 24x 10/100/1000 Base-T
PIC 1 REV 06 BUILTIN BUILTIN 4x 40GE QSFP+
Xcvr 0 REV 01 740-044512 MOC13405122192 QSFP+-40G-CU50CM
Xcvr 1 REV 01 740-044512 MOC13405122146 QSFP+-40G-CU50CM
Xcvr 2 REV 01 740-038624 141460MJ QSFP+-40G-CU3M
Xcvr 3 REV 01 740-038624 1414629M QSFP+-40G-CU3M
Power Supply 0 REV 01 740-046873 1EDE3361564 JPSU-350-AC-AFO-A
Fan Tray 0 Fan Module, Airflow Out (AFO)
Fan Tray 1 Fan Module, Airflow Out (AFO)

Question: What is the serial number for ex1?

Answer: The answer will vary by student. In this example, the


serial number is PG3713360118.

Question: How many FPCs exist?

Answer: There is only one FPC, FPC 0.

Step 2.18
Enter configuration mode and load the lab4-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{master:0}
lab@ex1-ServerA> configure
Entering configuration mode

{master:0}[edit]
lab@ex1-ServerA# load override dcx/lab4-start.config
load complete

{master:0}[edit]
lab@ex1-ServerA# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@ex1>
Step 2.19
View the configuration for ex1 by issuing the show configuration command.
{master:0}
lab@ex1> show configuration
## Last commit: 2014-09-26 19:48:31 UTC by lab

www.juniper.net Mixed Virtual Chassis • Lab 4–13


Data Center Switching
version 13.2X51-D21.1;
system {
host-name ex1;
root-authentication {
encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA
ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/
O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/
gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/
Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/
zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBHx9e
lwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF2KHBSI
xL51lmIDW8Gql9hJfD/Dr/
NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu2C8
UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/
g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= configurator@server1.he"; ##
SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
interfaces {
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.135/26;
}
}

Lab 4–14 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
}
}

Question: Which interfaces have been configured?

Answer: Only the vme interface has been configured.

Question: What is the IP address of the VME interface?

Answer: The answer will vary by student. In the example, the IP


address of ex1’s vme interface is 10.210.14.135.

Step 2.20
Open a new and separate console session to your ex2 switch and log in using the lab and
lab123 login credentials.
ex2-ServerB (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex2-ServerB>

Question: All switches in our lab default to Virtual Chassis


mode. What member is the master RE for the Virtual Chassis to
which ex2 belongs?

Answer: Member 0 should be the master RE of the Virtual


Chassis. You can tell by the prompt after you log in
(master:0). If member 0 is not the master RE for the Virtual
Chassis, please notify your instructor.

Step 2.21
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@ex2-ServerB> show virtual-chassis status

Virtual Chassis ID: 47ad.f5bc.753c


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt PG3713330145 ex4300-24t 128 Master* N VC

Member ID for next new member: 1 (FPC 1))

www.juniper.net Mixed Virtual Chassis • Lab 4–15


Data Center Switching
Question: How many members exist as part of the Virtual
Chassis?

Answer: Member 0 is the only member of the Virtual Chassis. If


member 0 is not the only member of the Virtual Chassis, please
notify your instructor.

Question: Which switch is the only member of the Virtual


Chassis? What type of switch is it?

Answer: ex2, a EX4300-24t, is the only member of the Virtual


Chassis.

Step 2.22
View the status of the Virtual Chassis’ VCPs by issuing the show virtual-chassis
vc-port command.
{master:0}
lab@ex2-ServerB> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------

{master:0}
lab@ex2>

Question: Which VCPs are enabled for the Virtual Chassis?

Answer: No VCP interfaces should be enabled. If any VCPs have


been enabled, please notify your instructor.

Step 2.23
Issue the show chassis hardware command to determine the serial number for ex2. Write
the serial number on the appropriate line on your lab diagram.
{master:0}
lab@ex2-ServerB> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis PG3713330145 EX4300-24T
Routing Engine 0 REV 06 650-044936 PG3713330145 EX4300-24T
FPC 0 REV 06 650-044936 PG3713330145 EX4300-24T
CPU BUILTIN BUILTIN FPC CPU
PIC 0 REV 06 BUILTIN BUILTIN 24x 10/100/1000 Base-T
PIC 1 REV 06 BUILTIN BUILTIN 4x 40GE QSFP+
Xcvr 0 REV 01 740-044512 MOC13405122192 QSFP+-40G-CU50CM
Xcvr 1 REV 01 740-044512 MOC13405122146 QSFP+-40G-CU50CM
Xcvr 2 REV 01 740-038624 14146087 QSFP+-40G-CU3M
Xcvr 3 REV 01 740-038624 1412603F QSFP+-40G-CU3M
Power Supply 0 REV 01 740-046873 1EDE3290261 JPSU-350-AC-AFO-A

Lab 4–16 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Fan Tray 0 Fan Module, Airflow Out (AFO)
Fan Tray 1 Fan Module, Airflow Out (AFO)

Question: What is the serial number for ex2?

Answer: The answer will vary by student. In this example, the


serial number is PG3713330145.

Question: How many FPCs exist?

Answer: There is only one FPC, FPC 0.

Step 2.24
Enter configuration mode and load the lab4-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{master:0}
lab@ex2-ServerB> configure
Entering configuration mode

{master:0}[edit]
lab@ex2-ServerB# load override dcx/lab4-start.config
load complete

{master:0}[edit]
lab@ex2-ServerB# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@ex2>
Step 2.25
View the configuration for ex2 by issuing the show configuration command.
{master:0}
lab@ex2> show configuration
## Last commit: 2014-09-26 19:49:30 UTC by lab
version 13.2X51-D21.1;
system {
host-name ex2;
root-authentication {
encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA

www.juniper.net Mixed Virtual Chassis • Lab 4–17


Data Center Switching
ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/
O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/
gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/
Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/
zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBHx9e
lwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF2KHBSI
xL51lmIDW8Gql9hJfD/Dr/
NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu2C8
UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/
g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= configurator@server1.he"; ##
SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
interfaces {
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.136/26;
}
}
}
}

Lab 4–18 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Question: Which interfaces have been configured?

Answer: Only the vme interface has been configured.

Question: What is the IP address of the VME interface?

Answer: The answer will vary by student. In the example, the IP


address of ex2’s vme interface is 10.210.14.136.

Part 3: Configuring the Master RE

In this lab part, you will preprovision a mixed Virtual Chassis consisting of two REs and two
linecards. The QFX5100 Series switches will act as master (qfx1) and backup (qfx2) REs. The
EX4300 Series switches will act as line cards. Configuration of a preprovisioned Virtual Chassis
must be performed on the master RE. That means that all Virtual Chassis configuration will be
performed on qfx1. Use the lab diagram titled “Network Diagram: Mixed Virtual Chassis Lab” for
this part of the lab.
Step 3.1
Return to the console session opened for qfx1.
On qfx1, enter configuration mode and navigate to the [edit virtual-chassis]
hierarchy. Configure the Virtual Chassis as a preprovisioned Virtual Chassis.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# edit virtual-chassis

{master:0}[edit virtual-chassis]
lab@qfx1# set preprovisioned

{master:0}[edit virtual-chassis]
lab@qfx1#
Step 3.2
Configure member (qfx1) to take on the RE role. Make sure to specify the serial number for qfx1
that you determined in the previous part of the lab.
{master:0}[edit virtual-chassis]
lab@qfx1# set member 0 role routing-engine

{master:0}[edit virtual-chassis]
lab@qfx1# set member 0 serial-number serial-qfx1
Step 3.3
Configure member 1 to take on the linecard role. Make sure to specify the serial number for ex1
that you determined in the previous part of the lab.

www.juniper.net Mixed Virtual Chassis • Lab 4–19


Data Center Switching
{master:0}[edit virtual-chassis]
lab@qfx1# set member 1 role line-card

{master:0}[edit virtual-chassis]
lab@qfx1# set member 1 serial-number serial-ex1
Step 3.4
Configure member 2 to take on the linecard role. Make sure to specify the serial number for ex2
that you determined in the previous part of the lab.
{master:0}[edit virtual-chassis]
lab@qfx1# set member 2 role line-card

{master:0}[edit virtual-chassis]
lab@qfx1# set member 2 serial-number serial-ex2
Step 3.5
Configure member 3 to take on the RE role. Make sure to specify the serial number for qfx2 that
you determined in the previous part of the lab.
{master:0}[edit virtual-chassis]
lab@qfx1# set member 3 role routing-engine

{master:0}[edit virtual-chassis]
lab@qfx1# set member 3 serial-number serial-qfx2
Step 3.6
View your configuration so far and if you are satisfied commit your configuration and exit to
operational mode.
{master:0}[edit virtual-chassis]
lab@qfx1# show
preprovisioned;
member 0 {
role routing-engine;
serial-number VF3714170305;
}
member 1 {
role line-card;
serial-number PG3713360118;
}
member 2 {
role line-card;
serial-number PG3713330145;
}
member 3 {
role routing-engine;
serial-number VF3714170306;
}

{master:0}[edit virtual-chassis]
lab@qfx1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

Lab 4–20 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
{master:0}
lab@qfx1>
Step 3.7
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@qfx1> show virtual-chassis status

Preprovisioned Virtual Chassis


Virtual Chassis ID: deb2.dc91.9c55
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* N VC

Question: Are all members of the Virtual Chassis listed in the


output of the command? Why?

Answer: Only member 0 is listed. The reason for this is because


the master RE has not detected any VCCP neighbors.

Question: How does a member switch detect other members of


the Virtual Chassis?

Answer: Members of a Virtual Chassis detect other members


through the exchange of VCCP messages over VCPs.

Step 3.8
View the status of the VCPs by issuing the show virtual-chassis vc-port command.
lab@qfx1> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------

{master:0}
lab@qfx1>

Question: Are any VCPs enabled on the master RE?

Answer: There are no VCPs currently enabled on the master RE.

Step 3.9
Look at the diagram for this part of the lab.

www.juniper.net Mixed Virtual Chassis • Lab 4–21


Data Center Switching
Question: According to the diagram, what VCPs should be
enabled on the master RE so that it can form the appropriate
VCCP relationships.?

Answer: vcp-255/0/50 and vcp-255/0/51 should be enabled


on the master RE.

Step 3.10
Enable vcp-255/0/50 and vcp-255/0/51 on qfx1 by issuing the request
virtual-chassis vc-port set pic-slot 0 port port-number command for
each VCP.
{master:0}
lab@qfx1> request virtual-chassis vc-port set pic-slot 0 port 50
Port conversion initiated, use show virtual-chassis vc-port to verify

{master:0}
lab@qfx1> request virtual-chassis vc-port set pic-slot 0 port 51
Port conversion initiated, use show virtual-chassis vc-port to verify

{master:0}
lab@qfx1>
Step 3.11
View the status of the VCPs by issuing the show virtual-chassis vc-port command.
{master:0}
lab@qfx1> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
0/50 Configured -1 Down 40000
0/51 Configured -1 Down 40000

Question: Are any VCPs enabled on the master RE?

Answer: Yes, the vcp-255/0/50 and vcp-255/0/51 are enabled.

Question: What is the status of the VCPs? Why?

Answer: Both VCPs are in the down state because the


downstream switches have not had their VCPs enabled.

Lab 4–22 • Mixed Virtual Chassis www.juniper.net


Data Center Switching

Part 4: Adding Members to the Virtual Chassis

In this lab part, you will add the remaining member switches to the Virtual Chassis. To add a
member to an existing preprovisioned Virtual Chassis you simply enable the appropriate VCP
interfaces. Use the lab diagram titled “Network Diagram: Mixed Virtual Chassis Lab” for this part
of the lab.
Step 4.1
Return to the console session opened for ex1.
On ex1, enable vcp-255/1/3 by issuing the request virtual-chassis vc-port set
pic-slot 1 port 3 command.
{master:0}
lab@ex1> request virtual-chassis vc-port set pic-slot 1 port 3
Port conversion initiated, use show virtual-chassis vc-port to verify

{master:0}
lab@ex1>

Question: Although it is not required, why do you think you


enabled vcp-255/1/3 before enabling vcp-255/1/2? Why does
it make a difference? Look at the diagram to help answer your
question.

Answer: When you enable vcp-255/1/3 on ex1 first, the master


RE will not be able to detect the new member. This will allow you
to quickly enable vcp-255/1/2 from the console of ex1. If you
had enabled vcp-255/1/2 first, the master RE will detect the
new member and add it to the Virtual Chassis. Then you would
have to wait for the master RE and new member to synchronize
and also for the console of ex1 to be redirected to the master
RE. It will be after all of that before you will finally be able to
enable vcp-255/1/3.

Step 4.2
Enable vcp-255/1/2 on ex1 by issuing the request virtual-chassis vc-port set
pic-slot 1 port 2 command. After issuing the command you will be logged out of ex1.
Wait 60 seconds before moving to the next step.

{master:0}
lab@ex1> request virtual-chassis vc-port set pic-slot 1 port 2
Port conversion initiated, use show virtual-chassis vc-port to verify

{master:0}
lab@ex1>

www.juniper.net Mixed Virtual Chassis • Lab 4–23


Data Center Switching
ex1 (ttyu0)

login:
Step 4.3
Login to ex1 using the lab and lab123 login credentials.
ex1 (ttyu0)

login: lab

Logging to master
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1>

Question: Do you notice anything interesting about the CLI


prompt? What does this mean?

Answer: Once you have logged in you should notice that your
session has been redirected to qfx1. This means that ex1 has
become a member of the Virtual Chassis.

Step 4.4
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@qfx1> show virtual-chassis status

Preprovisioned Virtual Chassis


Virtual Chassis ID: deb2.dc91.9c55
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* N VC 1
vcp-255/0/50
1 (FPC 1) Inactive PG3713360118 ex4300-24t 0 Linecard N VC 0
vcp-255/1/2

Question: What is the member number of ex1?

Answer: ex1 has been added to the Virtual Chassis as member


1 as expected.

Lab 4–24 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Question: What are mode settings of both the master RE and
member 1?

Answer: Both members are set for non-mixed Virtual Chassis


mode.

Question: What is the status of member 1? Why?

Answer: Member 1 is in the Inactive state. It is in the


Inactive state because the master RE, a QFX5100 Series,
has detected that the new member is not a QFX5100 Series.

Question: What is necessary to allow for member 1 to become


and active member of the Virtual Chassis?

Answer: To become an active member of the Virtual Chassis, all


members of the Virtual Chassis must be set to mixed mode.

Step 4.5
View the configuration of the Virtual Chassis using the show configuration command.
{master:0}
lab@qfx1> show configuration
## Last commit: 2014-09-25 04:22:48 UTC by lab
version 13.2X51-D21.1;
system {
host-name qfx1;
root-authentication {
encrypted-password "$1$ZBczLr53$0ocGXc4o4GS9tCSikhcm3/"; ## SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {

www.juniper.net Mixed Virtual Chassis • Lab 4–25


Data Center Switching
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
interfaces {
ge-1/0/14 {
vlan-tagging;
unit 301 {
vlan-id 301;
family inet {
address 172.16.1.2/24;
}
}
}
ge-2/0/7 {
vlan-tagging;
unit 301 {
vlan-id 301;
family inet {
address 172.16.1.1/24;
}
}
}
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.155/26;
}
}
}
}
routing-instances {
vr1 {
instance-type virtual-router;
interface ge-2/0/7.301;
}
vr2 {
instance-type virtual-router;
interface ge-1/0/14.301;
}
}
virtual-chassis {
preprovisioned;
member 0 {
role routing-engine;
serial-number VF3714170305;
}

Lab 4–26 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
member 1 {
role line-card;
serial-number PG3713360118;
}
member 2 {
role line-card;
serial-number PG3713330145;
}
member 3 {
role routing-engine;
serial-number VF3714170306;
}
}

Question: What happened to the configuration and vme IP


address that had been configured on ex1 prior to being added
to the Virtual Chassis?

Answer: Once a non-master member is added to a Virtual


Chassis, its configuration is overridden by the configuration that
exists on the master RE.

Step 4.6
Return to the console session opened for qfx2.
On qfx2, enable vcp-255/0/51 on qfx2 by issuing the request virtual-chassis
vc-port set pic-slot 0 port 51 command. After issuing the command you will be
logged out of qfx2. Wait 60 seconds before moving to the next step.
{master:0}
lab@qfx2> request virtual-chassis vc-port set pic-slot 0 port 51
Port conversion initiated, use show virtual-chassis vc-port to verify

qfx2 (ttyd0)

login:
Step 4.7
Login to qfx2 using the lab and lab123 login credentials.
qfx2 (ttyd0)

login: lab

Logging to master
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1>

www.juniper.net Mixed Virtual Chassis • Lab 4–27


Data Center Switching
Question: Do you notice anything interesting about the CLI
prompt? What does this mean?

Answer: Once you have logged in you should notice that your
session has been redirected to qfx1. This means that qfx2 has
become a member of the Virtual Chassis.

Step 4.8
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@qfx1> show virtual-chassis status

Preprovisioned Virtual Chassis


Virtual Chassis ID: deb2.dc91.9c55
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* N VC 1
vcp-255/0/50
1 (FPC 1) Inactive PG3713360118 ex4300-24t 0 Linecard N VC 0
vcp-255/1/2
3 vcp-255/1/3
3 (FPC 3) Inactive VF3714170306 qfx5100-48s-6q 129 Linecard N VC 1
vcp-255/0/51

Question: What is the member number of qfx2?

Answer: qfx2 has been added to the Virtual Chassis as member


3 as expected.

Question: What is the role of member 3? Why is that interesting?

Answer: Although member 3 is configured to be an RE, is has


currently taken on a line card role. This is because it is
Inactive due to the fact that the Virtual Chassis has not been
set to run in mixed mode.

Step 4.9
Enable vcp-255/0/50 on member 3 by issuing the request virtual-chassis vc-port
set pic-slot 0 port 50 member 3 command.
{master:0}
lab@qfx1> request virtual-chassis vc-port set pic-slot 0 port 50 member 3
fpc3:
--------------------------------------------------------------------------
Port conversion initiated, use show virtual-chassis vc-port to verify

Lab 4–28 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Step 4.10
Return to the console session opened for ex2.
On ex2, enable vcp-255/1/2 on ex2 by issuing the request virtual-chassis vc-port
set pic-slot 1 port 2 command. After issuing the command you will be logged out of
ex2. Wait 60 seconds before moving to the next step.
{master:0}
lab@ex2> request virtual-chassis vc-port set pic-slot 1 port 2
Port conversion initiated, use show virtual-chassis vc-port to verify

{master:0}
lab@ex2>
ex2 (ttyu0)

login:
Step 4.11
Login to ex2 using the lab and lab123 login credentials.
ex2 (ttyu0)

login: lab

Logging to master
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1>

Question: Do you notice anything interesting about the CLI


prompt? What does this mean?

Answer: Once you have logged in you should notice that your
session has been redirected to qfx1. This means that ex2 has
become a member of the Virtual Chassis.

Step 4.12
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@qfx1> show virtual-chassis status

Preprovisioned Virtual Chassis


Virtual Chassis ID: deb2.dc91.9c55
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* N VC 1
vcp-255/0/50

www.juniper.net Mixed Virtual Chassis • Lab 4–29


Data Center Switching
1 (FPC 1) Inactive PG3713360118 ex4300-24t 0 Linecard N VC 0
vcp-255/1/2
3 vcp-255/1/3
2 (FPC 2) Inactive PG3713330145 ex4300-24t 0 Linecard N VC 3
vcp-255/1/2
3 (FPC 3) Inactive VF3714170306 qfx5100-48s-6q 129 Linecard N VC 2
vcp-255/0/50
1 vcp-255/
0/51

Question: What is the member number of ex2?

Answer: ex2 has been added to the Virtual Chassis as member


2 as expected.

Step 4.13
Enable vcp-255/1/3 on member 2 by issuing the request virtual-chassis vc-port
set pic-slot 1 port 3 member 2 command.
{master:0}
lab@qfx1> request virtual-chassis vc-port set pic-slot 1 port 3 member 2
fpc2:
--------------------------------------------------------------------------
Port conversion initiated, use show virtual-chassis vc-port to verify

Part 5: Activating the Members of the Virtual Chassis

As you have seen so far, only the master RE is in the Prsnt (or active) state. All other members
are Inactive because the master RE has detected at least one member that is a different
chassis than itself (a QFX5100 Series switch). In this lab part you will enable a mixed Virtual
Chassis so that all members of the Virtual Chassis will show as Prsnt. Use the lab diagram
titled “Network Diagram: Mixed Virtual Chassis Lab” for this part of the lab.
Step 5.1
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command. Take a moment to view all the things that appear to be a problem with the Virtual
Chassis.
{master:0}
lab@qfx1> show virtual-chassis status

Preprovisioned Virtual Chassis


Virtual Chassis ID: deb2.dc91.9c55
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* N VC 1
vcp-255/0/50

Lab 4–30 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
2 vcp-255/
0/51
1 (FPC 1) Inactive PG3713360118 ex4300-24t 0 Linecard N VC 0
vcp-255/1/2
3 vcp-255/1/3
2 (FPC 2) Inactive PG3713330145 ex4300-24t 0 Linecard N VC 3
vcp-255/1/2
0 vcp-255/1/3
3 (FPC 3) Inactive VF3714170306 qfx5100-48s-6q 129 Linecard N VC 2
vcp-255/0/50
1 vcp-255/
0/51

Question: List all of the problems that you see in the output of
this command?

Answer: Some of the problems that can be seen in the output of


the command are that all members are in non-mixed mode
even though there is a mixture of QFX5100 and EX4300 Series
switches, member 3 is supposed to be an RE but it is currently
a linecard, and all members, except the master RE, are in the
Inactive state.

Step 5.2
Change the mode of all members of the Virtual Chassis by issuing the request
virtual-chassis mode mixed reboot all-members. This command will also cause
all members to reboot. Wait for the reboot to complete before moving on to the next step.
{master:0}
lab@qfx1> request virtual-chassis mode mixed reboot all-members
fpc1:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with mixed devices'. Rebooting system...

fpc2:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with mixed devices'. Rebooting system...

fpc3:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with mixed devices'. Rebooting system...

fpc0:

www.juniper.net Mixed Virtual Chassis • Lab 4–31


Data Center Switching
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with mixed devices'. Rebooting system...

{master:0}
lab@qfx1>
*** System shutdown message from root@qfx1 ***

System going down in 1 minute


Step 5.3
Login to ex2 using the lab and lab123 login credentials and view the status of the Virtual
Chassis by issuing the show virtual-chassis status command. Take a moment to view
all the things that were fixed by the previous step’s command.
qfx1 (ttyu0)

login: lab

Logging to master
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1> show virtual-chassis status

Preprovisioned Virtual Chassis


Virtual Chassis ID: deb2.dc91.9c55
Virtual Chassis Mode: Mixed
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* Y VC 1
vcp-255/0/50
2 vcp-255/
0/51
1 (FPC 1) Prsnt PG3713360118 ex4300-24t 0 Linecard Y VC 0
vcp-255/1/2
3 vcp-255/1/3
2 (FPC 2) Prsnt PG3713330145 ex4300-24t 0 Linecard Y VC 3
vcp-255/1/2
0 vcp-255/1/3
3 (FPC 3) Prsnt VF3714170306 qfx5100-48s-6q 129 Backup Y VC 2
vcp-255/0/50
1 vcp-255/
0/51

Question: Of the problems that you found in the previous steps,


which problems remain?

Answer: No problems remain. All members have taken on their


appropriate role (member 3 is an RE) and they are in the Prsnt
state.

Lab 4–32 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Question: What are the modes of each of the members of the
Virtual Chassis?

Answer: All members are in the mixed and Virtual Chassis


modes.

Part 6: Configuring the Mixed Virtual Chassis

In this lab part you will configure a few of the interfaces for Ethernet switching. You will use the
member number to help determine the interfaces names. Use the lab diagram titled “Network
Diagram: Mixed Virtual Chassis Lab” for this part of the lab.
Step 6.1
Look at the diagram for this part of the lab. Notice the two interfaces on the Virtual Chassis that
are connected to the two virtual routers. Use your knowledge of member IDs to determine the
name of the interfaces. Fill in the spaces provided on the diagram.

Question: What are the names of the two interfaces?

Answer: The two interfaces are named ge-1/0/15 and 


ge-2/0/6.

Step 6.2
Enter configuration mode and navigate to the [edit vlans] hierarchy. Configure a VLAN
called vlan_301 using a VLAN ID of 301.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# edit vlans

{master:0}[edit vlans]
lab@qfx1# set vlan_301 vlan-id 301
Step 6.3
Navigate to the [edit interfaces] hierarchy and configure each of the virtual router-facing
interfaces to perform Ethernet switching as trunk interfaces for VLAN 301 only. Commit your
configuration and exit to operational mode.
{master:0}[edit vlans]
lab@qfx1# top edit interfaces

{master:0}[edit interfaces]
lab@qfx1# set ge-1/0/15 unit 0 family ethernet-switching interface-mode trunk

{master:0}[edit interfaces]
lab@qfx1# set ge-1/0/15 unit 0 family ethernet-switching vlan members vlan_301

www.juniper.net Mixed Virtual Chassis • Lab 4–33


Data Center Switching

{master:0}[edit interfaces]
lab@qfx1# set ge-2/0/6 unit 0 family ethernet-switching interface-mode trunk

{master:0}[edit interfaces]
lab@qfx1# set ge-2/0/6 unit 0 family ethernet-switching vlan members vlan_301

{master:0}[edit interfaces]
lab@qfx1# commit and-quit
configuration check succeeds
fpc1:
commit complete
fpc2:
commit complete
fpc3:
commit complete
commit complete
Exiting configuration mode

{master:0}
lab@qfx1>
Step 6.4
View the configured VLANs by issuing the show vlans command.
{master:0}
lab@qfx1> show vlans

Routing instance VLAN name Tag Interfaces


default-switch vlan_301 301
ge-1/0/15.0*
ge-2/0/6.0*

Question: What VLAN tag is supported on each of the newly


configured interfaces?

Answer: Both interfaces support VLAN tag 301.

Step 6.5
Verify proper operation by sending ICMP traffic from vr1 to vr2 using the ping 172.16.1.2
routing-instance vr1 count 5 command.
{master:0}
lab@qfx1> ping 172.16.1.2 routing-instance vr1 count 5
PING 172.16.1.2 (172.16.1.2): 56 data bytes
64 bytes from 172.16.1.2: icmp_seq=0 ttl=64 time=61.719 ms
64 bytes from 172.16.1.2: icmp_seq=1 ttl=64 time=41.115 ms
64 bytes from 172.16.1.2: icmp_seq=2 ttl=64 time=33.014 ms
64 bytes from 172.16.1.2: icmp_seq=3 ttl=64 time=29.075 ms
64 bytes from 172.16.1.2: icmp_seq=4 ttl=64 time=33.030 ms

Lab 4–34 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
--- 172.16.1.2 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 29.075/39.591/61.719/11.738 ms

Question: Were the pings successful?

Answer: The pings should have been successful.

Step 6.6
View the MAC table of the Virtual Chassis by issuing the show ethernet-switching
table command to see if MAC addresses are being learned by the Virtual Chassis.
{master:0}
lab@qfx1> show ethernet-switching table

MAC flags (S - static MAC, D - dynamic MAC, L - locally learned, P - Persistent


static
SE - statistics enabled, NM - non configured MAC, R - remote PE MAC)

Ethernet switching table : 2 entries, 2 learned


Routing instance : default-switch
Vlan MAC MAC Age Logical
name address flags interface
vlan_301 4c:96:14:e6:88:6a D - ge-2/0/6.0
vlan_301 4c:96:14:e8:e6:11 D - ge-1/0/15.0

Question: Are MAC addresses being learned by the Virtual


Chassis?

Answer: MAC addresses should be learned by the Virtual


Chassis.

Part 7: Resetting the Members the Virtual Chassis

In this lab part you will remove each of the members from the Virtual Chassis and return them to
a standalone state. Use the lab diagram titled “Network Diagram: Mixed Virtual Chassis Lab” for
this part of the lab.
Step 7.1
Delete each of the VCPs of ex2 by issuing the request virtual-chassis vc-port
delete pic-slot 1 port port-number member 2 command for each VCP. You will be
logged out of the Virtual Chassis.
{master:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 1 port port-number
member 2
fpc2:
--------------------------------------------------------------------------
vc-port successfully deleted

www.juniper.net Mixed Virtual Chassis • Lab 4–35


Data Center Switching

{master:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 1 port port-number
member 2

qfx1 (ttyu0)

login:
Step 7.2
Attempt to log back into ex2 using the lab and lab123 login credentials. ex2 will attempt to log
into the Virtual Chassis. After 10 attempts, it will allow you to log directly into the ex2 switch.
qfx1 (ttyu0)

login: lab

Logging to master
..........
Connection to master failed, enabling local login
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status command
executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:2}
lab@qfx1>
Step 7.3
Enter configuration mode and load the lab4-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{linecard:2}
lab@qfx1> configure

{linecard:2}[edit]
lab@qfx1# load override dcx/lab4-start.config
load complete

{linecard:2}[edit]
lab@qfx1# commit and-quit
commit complete
Exiting configuration mode

{linecard:2}
lab@ex2>

Lab 4–36 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Step 7.4
Change the mode of ex2 so that it operates in non-mixed Virtual Chassis mode. Also, make sure
that it reboots immediately. Wait for ex2 to reboot before continuing.
{linecard:2}
lab@ex2> request virtual-chassis mode mixed disable reboot
fpc2:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with similar devices'. Rebooting system...

*** System shutdown message from root@ex2 ***

System going down in 1 minute

{linecard:2}
lab@ex2>
Step 7.5
Log back into ex2 using the lab and lab123 login credentials. ex2 will attempt to log into the
Virtual Chassis. After 10 attempts, it will allow you to log directly into the ex2 switch. View the
status of the Virtual Chassis by issuing the show virtual-chassis status command.
ex2 (ttyu0)

login: lab

Logging to master
..........
Connection to master failed, enabling local login
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.

{linecard:2}
lab@ex2> show virtual-chassis status

Virtual Chassis ID: deb2.dc91.9c55


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) NotPrsnt VF3714170305 qfx5100-48s-6q
1 (FPC 1) NotPrsnt PG3713360118 ex4300-24t
2 (FPC 2) Inactive PG3713330145 ex4300-24t 128 Linecard* N VC
3 (FPC 3) NotPrsnt VF3714170306 qfx5100-48s-6q

www.juniper.net Mixed Virtual Chassis • Lab 4–37


Data Center Switching
Question: Why are members 0, 1, and 3 still listed in the output?

Answer: Even after a reboot, a member will remember it’s role


as well as the other members roles.

Question: What is the status of member 2 (ex2)?

Answer: Member 2 is in the Inactive state since it has


detected a split Virtual Chassis.

Step 7.6
Reactivate member 2 by issuing the request virtual-chassis reactivate command.
You will be logged out of ex2.
{linecard:2}
lab@ex2> request virtual-chassis reactivate

This member split from a virtual chassis. Please make sure that no active
switch belonging to this virtual chassis has conflicting configuration.

Do you want to continue ? [yes,no] (no) yes

{linecard:2}
lab@ex2>
ex2 (ttyu0)

login:
Step 7.7
Log back into ex2 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command.
ex2 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:2}
lab@ex2> show virtual-chassis status

Virtual Chassis ID: 47ad.f5bc.753c


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
2 (FPC 2) Prsnt PG3713330145 ex4300-24t 128 Master* N VC

Member ID for next new member: 0 (FPC 0)

Lab 4–38 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Question: What is the state and role of member 2 (ex2)?

Answer: Member 2 is in the Prsnt state and is in the master


RE role.

Step 7.8
Although not required, the final step in converting ex2 back to standalone mode is to renumber
its member ID to 0. Perform this step by issuing the request virtual-chassis
renumber member-id 2 new-member-id 0 command. You will be automatically logged
out of ex2.
{master:2}
lab@ex2> request virtual-chassis renumber member-id 2 new-member-id 0

To move configuration specific to member ID 2 to member ID 0, please


use the replace command. e.g. replace pattern ge-2/ with ge-0/

If member-specific configuration groups are present, perform a


"commit full" to synchronize inheritance with the new member number.

Do you want to continue ? [yes,no] (no) yes

{master:2}
lab@ex2>
ex2 (ttyu0)

login:
Step 7.9
Log back into ex2 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command. Log out of ex2 when
complete.
ex2 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex2> show virtual-chassis status

Virtual Chassis ID: 47ad.f5bc.753c


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt PG3713330145 ex4300-24t 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

www.juniper.net Mixed Virtual Chassis • Lab 4–39


Data Center Switching
{master:0}
lab@ex2> exit

ex2 (ttyu0)

login:

Question: Is ex2 in standalone mode?

Answer: Yes, ex2 has been successfully removed from the


Virtual Chassis.

Step 7.10
Return to the console session opened for qfx2.
On qfx2, attempt to log back into qfx2 using the lab and lab123 login credentials. Delete
vcp-255/0/50 of qfx2 by issuing the request virtual-chassis vc-port delete
pic-slot 0 port 50 member 3 command.
qfx1 (ttyd0)

login: lab

Logging to master
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 0 port 50 member 3
fpc3:
--------------------------------------------------------------------------
vc-port successfully deleted
Step 7.11
Delete vcp-255/0/51 of qfx2 by issuing the request virtual-chassis vc-port
delete pic-slot 0 port 51 member 3 command. You will be logged out of the Virtual
Chassis.
{master:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 0 port 51 member 3
fpc3:
--------------------------------------------------------------------------
vc-port successfully deleted

qfx1 (ttyu0)

login:

Lab 4–40 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Step 7.12
Attempt to log back into qfx2 using the lab and lab123 login credentials. Since qfx2 was the
backup RE and detected a Virtual Chassis split it became the master RE for its local Virtual
Chassis for a short period. However, following the rules of splitting qfx2 deactivated its virtual
chassis. Notice how qfx2 is now in the linecard role due to split detection.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:3}
lab@qfx1>
Step 7.13
Enter configuration mode and load the lab4-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{linecard:3}
lab@qfx1> configure
Entering configuration mode

{linecard:3}[edit]
lab@qfx1# load override dcx/lab4-start.config
load complete

{linecard:3}[edit]
lab@qfx1# commit and-quit

/config/license/JUNOS533859.lic:1:(0) JUNOS533859: licensed device [VF3714170306],


is not part of the virtual chassis
commit complete
Exiting configuration mode

{linecard:3}
lab@qfx2>
Step 7.14
Change the mode of qfx2 so that it operates in non-mixed Virtual Chassis mode. Also, make sure
that it reboots immediately. Wait for qfx2 to reboot before continuing.
{linecard:3}
lab@qfx2> request virtual-chassis mode mixed disable reboot
fpc3:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with similar devices'. Rebooting system...

www.juniper.net Mixed Virtual Chassis • Lab 4–41


Data Center Switching

*** System shutdown message from root@qfx2 ***

System going down in 1 minute

{linecard:3}
lab@qfx2>
Step 7.15
Log back into qfx2 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status command
executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:3}
lab@qfx2> show virtual-chassis

Virtual Chassis ID: deb2.dc91.9c55


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) NotPrsnt VF3714170305 qfx5100-48s-6q
1 (FPC 1) NotPrsnt PG3713360118 ex4300-24t
2 (FPC 2) NotPrsnt PG3713330145 ex4300-24t
3 (FPC 3) Inactive VF3714170306 qfx5100-48s-6q 128 Linecard* N VC

Question: What is the status of member 3 (qfx2)?

Answer: Member 2 is in the Inactive state since it has


detected a split Virtual Chassis.

Step 7.16
Reactivate member 3 by issuing the request virtual-chassis reactivate command.
You will be logged out of qfx2.
{linecard:3}
lab@qfx2> request virtual-chassis reactivate

Lab 4–42 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
This member split from a virtual chassis. Please make sure that no active
switch belonging to this virtual chassis has conflicting configuration.

Do you want to continue ? [yes,no] (no) yes

{linecard:3}
lab@qfx2>
qfx2 (ttyd0)

login:
Step 7.17
Log back into qfx2 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:3}
lab@qfx2> show virtual-chassis status

Virtual Chassis ID: 7f7b.ee63.23b0


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
3 (FPC 3) Prsnt VF3714170306 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 0 (FPC 0)

Question: What is the state and role of member 3 (qfx2)?

Answer: Member 3 is in the Prsnt state and is in the master


RE role.

Step 7.18
Although not required, the final step in converting qfx2 back to standalone mode is to renumber
its member ID to 0. Perform this step by issuing the request virtual-chassis
renumber member-id 3 new-member-id 0 command. You will be automatically logged
out of qfx2.
{master:3}
lab@qfx2> request virtual-chassis renumber member-id 3 new-member-id 0

To move configuration specific to member ID 3 to member ID 0, please


use the replace command. e.g. replace pattern ge-3/ with ge-0/

If member-specific configuration groups are present, perform a


"commit full" to synchronize inheritance with the new member number.

www.juniper.net Mixed Virtual Chassis • Lab 4–43


Data Center Switching

Do you want to continue ? [yes,no] (no) yes

{master:3}
lab@qfx2>
qfx2 (ttyd0)

login:
Step 7.19
Log back into qfx2 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command. Log out of qfx2 when
complete.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx2> show virtual-chassis status

Virtual Chassis ID: 7f7b.ee63.23b0


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170306 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 1 (FPC 1)


{master:0}
lab@qfx2> exit

qfx2 (ttyu0)

login:

Question: Is qfx2 in standalone mode?

Answer: Yes, qfx2 has been successfully removed from the


Virtual Chassis.

Step 7.20
Return to the console session opened for ex1.
On ex1,. attempt to log back in using the lab and lab123 login credentials. Delete vcp-255/1/
3 of ex1 by issuing the request virtual-chassis vc-port delete pic-slot 1
port 3 member 1 command.

Lab 4–44 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
qfx1 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:1}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 1 port 3 member 1
fpc1:
--------------------------------------------------------------------------
vc-port successfully deleted

{linecard:1}
lab@qfx1>
Step 7.21
Delete vcp-255/1/2 of ex1 by issuing the request virtual-chassis vc-port delete
pic-slot 1 port 2 member 1 command. You will be logged out of the Virtual Chassis.
{linecard:1}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 1 port 2 member 1

qfx1 (ttyu0)

login:

Step 7.22
Attempt to log back into ex1 using the lab and lab123 login credentials. Enter configuration
mode and load the lab4-start.config configuration file from the /var/home/lab/
dcx/ directory. Commit your changes and return to operational mode.
qfx1 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:1}

www.juniper.net Mixed Virtual Chassis • Lab 4–45


Data Center Switching
lab@qfx1> configure
Entering configuration mode

{linecard:1}[edit]
lab@qfx1# load override dcx/lab4-start.config
load complete

{linecard:1}[edit]
lab@qfx1# commit and-quit
commit complete
Exiting configuration mode

{linecard:1}
lab@ex1>
Step 7.23
Change the mode of ex1 so that it operates in non-mixed Virtual Chassis mode. Also, make sure
that it reboots immediately. Wait for ex1 to reboot before continuing.
lab@ex1> request virtual-chassis mode mixed disable reboot
fpc1:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with similar devices'. Rebooting system...

*** System shutdown message from root@ex1 ***

System going down in 1 minute

{linecard:1}
lab@ex1>
Step 7.24
Log back into ex1 using the lab and lab123 login credentials. ex1 will attempt to log into the
Virtual Chassis. After 10 attempts, it will allow you to log directly into the ex1 switch.View the
status of the Virtual Chassis by issuing the show virtual-chassis status command.
ex1 (ttyu0)

login: lab

Logging to master
..........
Connection to master failed, enabling local login
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status command
executed at this console.

Lab 4–46 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
warning: Please logout and log into the VC-M to use CLI.
{linecard:1}
lab@ex1> show virtual-chassis status

Virtual Chassis ID: deb2.dc91.9c55


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) NotPrsnt VF3714170305 qfx5100-48s-6q
1 (FPC 1) Inactive PG3713360118 ex4300-24t 128 Linecard* N VC
2 (FPC 2) NotPrsnt PG3713330145 ex4300-24t
3 (FPC 3) NotPrsnt VF3714170306 qfx5100-48s-6q

Question: What is the status of member 1 (ex1)?

Answer: Member 1 is in the Inactive state since it has


detected a split Virtual Chassis.

Step 7.25
Reactivate member 1 by issuing the request virtual-chassis reactivate command.
You will be logged out of ex1.
lab@ex1> request virtual-chassis reactivate

This member split from a virtual chassis. Please make sure that no active
switch belonging to this virtual chassis has conflicting configuration.

Do you want to continue ? [yes,no] (no) yes

{linecard:1}
lab@ex1>
ex1 (ttyu0)

login:
Step 7.26
Log back into ex1 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command.
{linecard:1}
lab@ex1>
ex1 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:1}
lab@ex1> show virtual-chassis status

Virtual Chassis ID: c4fc.38d3.f363

www.juniper.net Mixed Virtual Chassis • Lab 4–47


Data Center Switching
Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
1 (FPC 1) Prsnt PG3713360118 ex4300-24t 128 Master* N VC

Member ID for next new member: 0 (FPC 0)

Question: What is the state and role of member 1 (ex1)?

Answer: Member 1is in the Prsnt state and is in the master RE


role.

Step 7.27
Although not required, the final step in converting ex1 back to standalone mode is to renumber
its member ID to 0. Perform this step by issuing the request virtual-chassis
renumber member-id 1 new-member-id 0 command. You will be automatically logged
out of ex1.
{master:1}
lab@ex1> request virtual-chassis renumber member-id 1 new-member-id 0

To move configuration specific to member ID 1 to member ID 0, please


use the replace command. e.g. replace pattern ge-1/ with ge-0/

If member-specific configuration groups are present, perform a


"commit full" to synchronize inheritance with the new member number.

Do you want to continue ? [yes,no] (no) yes

{master:1}
lab@ex1>
ex1 (ttyu0)

login:
Step 7.28
Log back into ex1 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command. Log out of ex1 when
complete.
ex1 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex1> show virtual-chassis status

Virtual Chassis ID: c4fc.38d3.f363


Virtual Chassis Mode: Enabled

Lab 4–48 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt PG3713360118 ex4300-24t 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

{master:0}
lab@ex1> exit

ex1 (ttyu0)

login:

Question: Is ex1 in standalone mode?

Answer: Yes, ex1 has been successfully removed from the


Virtual Chassis.

Step 7.29
Return to the console session opened for qfx1.
On qfx1, attempt to login using the lab and lab123 login credentials. Delete vcp-255/0/50 of
qfx1 by issuing the request virtual-chassis vc-port delete pic-slot 0 port
50 command.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 0 port 50
vc-port successfully deleted
Step 7.30
Delete vcp-255/0/51 of qfx1 by issuing the request virtual-chassis vc-port
delete pic-slot 0 port 51 command.
{linecard:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 0 port 51
vc-port successfully deleted

www.juniper.net Mixed Virtual Chassis • Lab 4–49


Data Center Switching
{linecard:0}
lab@qfx1>
Step 7.31
Enter configuration mode and load the lab4-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{linecard:0}
lab@qfx1> configure
Entering configuration mode

{linecard:0}[edit]
lab@qfx1# load override dcx/lab4-start.config
load complete

{linecard:0}[edit]
lab@qfx1# commit and-quit

/config/license/JUNOS533858.lic:1:(0) JUNOS533858: licensed device [VF3714170305],


is not part of the virtual chassis

/config/license/JUNOS533859.lic:1:(0) JUNOS533859: licensed device [VF3714170306],


is not part of the virtual chassis
commit complete
Exiting configuration mode

{linecard:0}
lab@qfx1>
Step 7.32
Change the mode of qfx1 so that it operates in non-mixed Virtual Chassis mode. Also, make sure
that it reboots immediately. Wait for qfx1 to reboot before continuing.
{linecard:0}
lab@qfx1> request virtual-chassis mode mixed disable reboot
fpc0:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with similar devices'. Rebooting system...

{linecard:0}

*** System shutdown message from root@qfx1 ***

System going down in 1 minute


Step 7.33
Log back into qfx1 using the lab and lab123 login credentials. qfx1 will attempt to log into the
Virtual Chassis. After 10 attempts, it will allow you to log directly into the qfx1 switch. View the
status of the Virtual Chassis by issuing the show virtual-chassis status command.
qfx1 (ttyd0)

login: lab

Logging to master

Lab 4–50 • Mixed Virtual Chassis www.juniper.net


Data Center Switching
..........
Connection to master failed, enabling local login
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:0}
lab@qfx1> show virtual-chassis status

Virtual Chassis ID: deb2.dc91.9c55


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Inactive VF3714170305 qfx5100-48s-6q 128 Linecard* N VC
1 (FPC 1) NotPrsnt PG3713360118 ex4300-24t
2 (FPC 2) NotPrsnt PG3713330145 ex4300-24t
3 (FPC 3) NotPrsnt VF3714170306 qfx5100-48s-6q

{linecard:0}
lab@qfx1>

Question: What is the status of member 0 (qfx1)?

Answer: Member 0is in the Inactive state since it has


detected a split Virtual Chassis.

Step 7.34
Reactivate member 0 by issuing the request virtual-chassis reactivate command.
You will be logged out of qfx1.
lab@qfx1> request virtual-chassis reactivate

This member split from a virtual chassis. Please make sure that no active
switch belonging to this virtual chassis has conflicting configuration.

Do you want to continue ? [yes,no] (no) yes

{linecard:0}
lab@qfx1>
qfx1 (ttyd0)

login:

www.juniper.net Mixed Virtual Chassis • Lab 4–51


Data Center Switching
Step 7.35
Log back into qfx1 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command. Log out of qfx1 when
complete.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1> show virtual-chassis status

Virtual Chassis ID: c448.93df.7d39


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

{master:0}
lab@qfx1> exit

qfx1 (ttyu0)

login:

Question: What is the state and role of member 0 (qfx1)?

Answer: Member 0 is in the Prsnt state and is in the master RE


role.

Question: Is qfx1 in standalone mode?

Answer: Yes, qfx1 has been successfully removed from the


Virtual Chassis.

STOP Tell your instructor that you have completed this lab.

Lab 4–52 • Mixed Virtual Chassis www.juniper.net


Data Center Switching

www.juniper.net Mixed Virtual Chassis • Lab 4–53


Data Center Switching

Lab 4–54 • Mixed Virtual Chassis www.juniper.net


Lab
Virtual Chassis Fabric

Overview
In this lab, you provision a mixed Virtual Chassis Fabric (VCF) using a combination of two
QFX5100 Series switches and two EX4300 Series switches. The QFX5100 Series switches will
act as spines as well as master and backup Routing Engines (REs). The EX4300 Series switches
will act as leafs as well as linecards for the VCF.
By completing this lab, you will perform the following tasks:
• Access your assigned switches.
• Configure the master RE for auto-provisioning of the VCF.
• Enable the Virtual Chassis Ports (VCPs) on each of the switches.
• Verify that each member switch has taken on the appropriate role.
• Configure network interfaces on the VCF.
• Verify that the VCF appears to act as a single switch.
• Add a VCF into Junos Space for management purposes.
• Reset the members of the VCF into individual standalone switches.

Part 1: Analyze the Topology

In this lab part, you will review the lab diagram to determine the roles that each switch will take
as part of the VCF. Use the lab diagram titled “Network Diagram: Virtual Chassis Fabric Lab” for
this part of the lab.
Step 1.1
Take a look at the diagram labeled “Network Diagram: Virtual Chassis Fabric Lab.”

Question: Which switch is supposed to be the master RE for the


mixed VCF?

Answer: qfx1 is supposed to be the master RE for the VCF.

www.juniper.net Virtual Chassis Fabric • Lab 5–1


Data Center Switching
Question: Which switch is supposed to be the backup RE for the
mixed VCF?

Answer: qfx2 is supposed to be the backup RE for the VCF.

Question: Which switches are supposed to be leaf and linecards


for the VCF?

Answer: ex1 and ex2 will be both leafs and linecards for the VCF.

Question: What do you think is the purpose of the two virtual


routers?

Answer: The two virtual routers will be used to generate


IP-based traffic that will traverse the VCF.

Part 2: Logging In Using the CLI

In this lab part, you become familiar with the access details used to connect to the lab
equipment. Once you are familiar with the access details, you will use the CLI to log in to your
team’s designated switches. Once you have logged in to your devices you will make sure your
devices are running the appropriate starting configurations for this lab. Use the lab diagram
titled “Network Diagram: Virtual Chassis Fabric Lab” for this part of the lab.
Step 2.1
Ensure that you know to which switches you have been assigned. Check with your instructor if
you are not certain. Consult the management network diagram to determine your switches’
management addresses.

Question: What are the management addresses assigned to


your switches?

Answer: The answer varies and depends on your assigned


environment and devices. If you are unsure of your assignment,
ask your instructor.

Step 2.2
Using console access, connect to your qfx1 switch and log in using the lab and lab123 login
credentials.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


Lab 5–2 • Virtual Chassis Fabric www.juniper.net
Data Center Switching
{master:0}
lab@qfx1>

Question: All switches in our lab default to Virtual Chassis


mode. What member is the master RE for the Virtual Chassis to
which qfx1 belongs?

Answer: Member 0 should be the master RE of the Virtual


Chassis. You can tell by the prompt after you log in
(master:0). If member 0 is not the master RE for the Virtual
Chassis, please notify your instructor.

Step 2.3
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@qfx1> show virtual-chassis status

Virtual Chassis ID: deb2.dc91.9c55


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

Question: How many members exist as part of the Virtual


Chassis?

Answer: Member 0 is the only member of the Virtual Chassis. If


member 0 is not the only member of the Virtual Chassis, please
notify your instructor.

Question: Which switch is the only member of the Virtual


Chassis? What type of switch is it?

Answer: qfx1, a QFX5100-48s-6q, is the only member of the


Virtual Chassis.

Step 2.4
View the status of the Virtual Chassis’ VCPs by issuing the show virtual-chassis
vc-port command.
{master:0}
lab@qfx1> show virtual-chassis vc-port
fpc0:

www.juniper.net Virtual Chassis Fabric • Lab 5–3


Data Center Switching
--------------------------------------------------------------------------

{master:0}
lab@qfx1>

Question: Which VCPs are enabled for the Virtual Chassis?

Answer: No VCP interfaces should be enabled. If any VCPs have


been enabled, please notify your instructor.

Step 2.5
Issue the show chassis hardware command to determine the serial number for qfx1. Write
the serial number on the appropriate line on your lab diagram.
{master:0}
lab@qfx1> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis VF3714170305 QFX5100-48S-6Q
Pseudo CB 0
Routing Engine 0 BUILTIN BUILTIN QFX Routing Engine
FPC 0 REV 05 650-056264 VF3714170305 QFX5100-48S-6Q
CPU BUILTIN BUILTIN FPC CPU
PIC 0 BUILTIN BUILTIN 48x10G-6x40G
Xcvr 0 REV 02 740-013111 D275324 SFP-T
Xcvr 48 REV 01 740-038623 MOC14136231262 QSFP+-40G-CU1M
Xcvr 49 REV 01 740-038623 MOC14136231597 QSFP+-40G-CU1M
Xcvr 50 REV 01 740-038624 141460MJ QSFP+-40G-CU3M
Xcvr 51 REV 01 740-038624 1412603F QSFP+-40G-CU3M
Power Supply 0 REV 03 740-041741 1GA24110534 JPSU-650W-AC-AFO
Power Supply 1 REV 03 740-041741 1GA24110529 JPSU-650W-AC-AFO
Fan Tray 0 QFX5100 Fan Tray 0, Front
to Back Airflow - AFO
Fan Tray 1 QFX5100 Fan Tray 1, Front
to Back Airflow - AFO
Fan Tray 2 QFX5100 Fan Tray 2, Front
to Back Airflow - AFO
Fan Tray 3 QFX5100 Fan Tray 3, Front
to Back Airflow - AFO
Fan Tray 4 QFX5100 Fan Tray 4, Front
to Back Airflow - AFO

Question: What is the serial number for qfx1?

Answer: The answer will vary by student. In this example, the


serial number is VF3714170305.

Lab 5–4 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Question: How many FPCs exist?

Answer: There is only one FPC, FPC 0.

Step 2.6
Enter configuration mode and load the lab5-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# load override dcx/lab5-start.config
load complete

{master:0}[edit]
lab@qfx1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@qfx1>
Step 2.7
View the configuration for qfx1 by issuing the show configuration command.
{master:0}
lab@qfx1> show configuration
system {
host-name qfx1;
root-authentication {
encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA
ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/
O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/
gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/
Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/
zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBHx9
elwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF2KHB
SIxL51lmIDW8Gql9hJfD/Dr/
NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu2C
8UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/
g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= configurator@server1.he"; ##
SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA

www.juniper.net Virtual Chassis Fabric • Lab 5–5


Data Center Switching
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
interfaces {
ge-2/0/7 {
vlan-tagging;
unit 301 {
vlan-id 301;
family inet {
address 172.16.1.1/24;
}
}
}
ge-3/0/14 {
vlan-tagging;
unit 301 {
vlan-id 301;
family inet {
address 172.16.1.2/24;
}
}
}
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.155/26;
}
}
}
}
routing-instances {
vr1 {
instance-type virtual-router;
interface ge-2/0/7.301;

Lab 5–6 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
}
vr2 {
instance-type virtual-router;
interface ge-3/0/14.301;
}
}

Question: Which interfaces have been configured?

Answer: The vme, ge-3/0/14, and ge-2/0/7 interfaces have


been configured.

Question: What is the IP address of the VME interface?

Answer: The answer will vary by student. In the example, the IP


address of qfx1’s vme interface is 10.210.14.155.

Step 2.8
Open a new and separate console session to your qfx2 switch and log in using the lab and
lab123 login credentials.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx2>

Question: All switches in our lab default to Virtual Chassis


mode. What member is the master RE for the Virtual Chassis to
which qfx2 belongs?

Answer: Member 0 should be the master RE of the Virtual


Chassis. You can tell by the prompt after you log in
(master:0). If member 0 is not the master RE for the Virtual
Chassis, please notify your instructor.

Step 2.9
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@qfx2> show virtual-chassis status

Virtual Chassis ID: deb2.dc91.9c55


Virtual Chassis Mode: Enabled

www.juniper.net Virtual Chassis Fabric • Lab 5–7


Data Center Switching
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170306 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

Question: How many members exist as part of the Virtual


Chassis?

Answer: Member 0 is the only member of the Virtual Chassis. If


member 0 is not the only member of the Virtual Chassis, please
notify your instructor.

Question: Which switch is the only member of the Virtual


Chassis? What type of switch is it?

Answer: qfx2, a QFX5100-48s-6q, is the only member of the


Virtual Chassis.

Step 2.10
View the status of the Virtual Chassis’ VCPs by issuing the show virtual-chassis
vc-port command.
{master:0}
lab@qfx2> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------

{master:0}
lab@qfx2>

Question: Which VCPs are enabled for the Virtual Chassis?

Answer: No VCP interfaces should be enabled. If any VCPs have


been enabled, please notify your instructor.

Step 2.11
Issue the show chassis hardware command to determine the serial number for qfx2. Write
the serial number on the appropriate line on your lab diagram.
{master:0}
lab@qfx2> show chassis hardware
Hardware inventory:

Lab 5–8 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Item Version Part number Serial number Description
Chassis VF3714170306 QFX5100-48S-6Q
Pseudo CB 0
Routing Engine 0 BUILTIN BUILTIN QFX Routing Engine
FPC 0 REV 05 650-056264 VF3714170306 QFX5100-48S-6Q
CPU BUILTIN BUILTIN FPC CPU
PIC 0 BUILTIN BUILTIN 48x10G-6x40G
Xcvr 0 REV 02 740-013111 B388216 SFP-T
Xcvr 48 REV 01 740-038623 MOC14136231262 QSFP+-40G-CU1M
Xcvr 49 REV 01 740-038623 MOC14136231597 QSFP+-40G-CU1M
Xcvr 50 REV 01 740-038624 1414629M QSFP+-40G-CU3M
Xcvr 51 REV 01 740-038624 14146087 QSFP+-40G-CU3M
Power Supply 0 REV 03 740-041741 1GA24110532 JPSU-650W-AC-AFO
Power Supply 1 REV 03 740-041741 1GA24110533 JPSU-650W-AC-AFO
Fan Tray 0 QFX5100 Fan Tray 0, Front
to Back Airflow - AFO
Fan Tray 1 QFX5100 Fan Tray 1, Front
to Back Airflow - AFO
Fan Tray 2 QFX5100 Fan Tray 2, Front
to Back Airflow - AFO
Fan Tray 3 QFX5100 Fan Tray 3, Front
to Back Airflow - AFO
Fan Tray 4 QFX5100 Fan Tray 4, Front
to Back Airflow - AFO

Question: What is the serial number for qfx2?

Answer: The answer will vary by student. In this example, the


serial number is VF3714170306.

Question: How many FPCs exist?

Answer: There is only one FPC, FPC 0.

Step 2.12
Enter configuration mode and load the lab5-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{master:0}
lab@qfx2> configure
Entering configuration mode

{master:0}[edit]
lab@qfx2# load override dcx/lab5-start.config
load complete

{master:0}[edit]
lab@qfx2# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

www.juniper.net Virtual Chassis Fabric • Lab 5–9


Data Center Switching

{master:0}
lab@qfx2>
Step 2.13
View the configuration for qfx2 by issuing the show configuration command.
{master:0}
lab@qfx2> show configuration
## Last commit: 2014-09-26 19:47:17 UTC by lab
version 13.2X51-D21.1;
system {
host-name qfx2;
root-authentication {
encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA
ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/
O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/
gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/
Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/
zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBHx9e
lwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF2KHBSI
xL51lmIDW8Gql9hJfD/Dr/
NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu2C8
UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/
g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= configurator@server1.he"; ##
SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}

Lab 5–10 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
}
}
interfaces {
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.156/26;
}
}
}
}

Question: Which interfaces have been configured?

Answer: Only the vme interface has been configured.

Question: What is the IP address of the VME interface?

Answer: The answer will vary by student. In the example, the IP


address of qfx2’s vme interface is 10.210.14.156.

Step 2.14
Open a new and separate console session to your ex1 switch and log in using the lab and
lab123 login credentials.
ex1 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex1>

Question: All switches in our lab default to Virtual Chassis


mode. What member is the master RE for the Virtual Chassis to
which ex1 belongs?

Answer: Member 0 should be the master RE of the Virtual


Chassis. You can tell by the prompt after you log in
(master:0). If member 0 is not the master RE for the Virtual
Chassis, please notify your instructor.

Step 2.15
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.

www.juniper.net Virtual Chassis Fabric • Lab 5–11


Data Center Switching
{master:0}
lab@ex1> show virtual-chassis status

Virtual Chassis ID: 51e4.3289.1627


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt PG3713360118 ex4300-24t 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

Question: How many members exist as part of the Virtual


Chassis?

Answer: Member 0 is the only member of the Virtual Chassis. If


member 0 is not the only member of the Virtual Chassis, please
notify your instructor.

Question: Which switch is the only member of the Virtual


Chassis? What type of switch is it?

Answer: ex1, a EX4300-24t, is the only member of the Virtual


Chassis.

Step 2.16
View the status of the Virtual Chassis’ VCPs by issuing the show virtual-chassis
vc-port command.
{master:0}
lab@ex1> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------

{master:0}
lab@ex1>

Question: Which VCPs are enabled for the Virtual Chassis?

Answer: No VCP interfaces should be enabled. If any VCPs have


been enabled, please notify your instructor.

Step 2.17
Issue the show chassis hardware command to determine the serial number for ex1. Write
the serial number on the appropriate line on your lab diagram.
{master:0}
lab@ex1> show chassis hardware
Hardware inventory:

Lab 5–12 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Item Version Part number Serial number Description
Chassis PG3713360118 EX4300-24T
Routing Engine 0 REV 06 650-044936 PG3713360118 EX4300-24T
FPC 0 REV 06 650-044936 PG3713360118 EX4300-24T
CPU BUILTIN BUILTIN FPC CPU
PIC 0 REV 06 BUILTIN BUILTIN 24x 10/100/1000 Base-T
PIC 1 REV 06 BUILTIN BUILTIN 4x 40GE QSFP+
Xcvr 0 REV 01 740-044512 MOC13405122192 QSFP+-40G-CU50CM
Xcvr 1 REV 01 740-044512 MOC13405122146 QSFP+-40G-CU50CM
Xcvr 2 REV 01 740-038624 141460MJ QSFP+-40G-CU3M
Xcvr 3 REV 01 740-038624 1414629M QSFP+-40G-CU3M
Power Supply 0 REV 01 740-046873 1EDE3361564 JPSU-350-AC-AFO-A
Fan Tray 0 Fan Module, Airflow Out (AFO)
Fan Tray 1 Fan Module, Airflow Out (AFO)

Question: What is the serial number for ex1?

Answer: The answer will vary by student. In this example, the


serial number is PG3713360118.

Question: How many FPCs exist?

Answer: There is only one FPC, FPC 0.

Step 2.18
Enter configuration mode and load the lab5-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{master:0}
lab@ex1> configure
Entering configuration mode

{master:0}[edit]
lab@ex1# load override dcx/lab5-start.config
load complete

{master:0}[edit]
lab@ex1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@ex1>
Step 2.19
View the configuration for ex1 by issuing the show configuration command.
{master:0}
lab@ex1> show configuration
## Last commit: 2014-09-26 19:48:31 UTC by lab

www.juniper.net Virtual Chassis Fabric • Lab 5–13


Data Center Switching
version 13.2X51-D21.1;
system {
host-name ex1;
root-authentication {
encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA
ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/
O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/
gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/
Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/
zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBHx9e
lwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF2KHBSI
xL51lmIDW8Gql9hJfD/Dr/
NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu2C8
UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/
g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= configurator@server1.he"; ##
SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
interfaces {
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.135/26;
}
}

Lab 5–14 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
}
}

Question: Which interfaces have been configured?

Answer: Only the vme interface has been configured.

Question: What is the IP address of the VME interface?

Answer: The answer will vary by student. In the example, the IP


address of ex1’s vme interface is 10.210.14.135.

Step 2.20
Open a new and separate console session to your ex2 switch and log in using the lab and
lab123 login credentials.
ex2 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex2>

Question: All switches in our lab default to Virtual Chassis


mode. What member is the master RE for the Virtual Chassis to
which ex2 belongs?

Answer: Member 0 should be the master RE of the Virtual


Chassis. You can tell by the prompt after you log in
(master:0). If member 0 is not the master RE for the Virtual
Chassis, please notify your instructor.

Step 2.21
View the status of the Virtual Chassis by issuing the show virtual-chassis status
command.
{master:0}
lab@ex2> show virtual-chassis status

Virtual Chassis ID: 47ad.f5bc.753c


Virtual Chassis Mode: Enabled

www.juniper.net Virtual Chassis Fabric • Lab 5–15


Data Center Switching
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt PG3713330145 ex4300-24t 128 Master* N VC

Member ID for next new member: 1 (FPC 1))

Question: How many members exist as part of the Virtual


Chassis?

Answer: Member 0 is the only member of the Virtual Chassis. If


member 0 is not the only member of the Virtual Chassis, please
notify your instructor.

Question: Which switch is the only member of the Virtual


Chassis? What type of switch is it?

Answer: ex2, a EX4300-24t, is the only member of the Virtual


Chassis.

Step 2.22
View the status of the Virtual Chassis’ VCPs by issuing the show virtual-chassis
vc-port command.
{master:0}
lab@ex2> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------

{master:0}
lab@ex2>

Question: Which VCPs are enabled for the Virtual Chassis?

Answer: No VCP interfaces should be enabled. If any VCPs have


been enabled, please notify your instructor.

Step 2.23
Issue the show chassis hardware command to determine the serial number for ex2. Write
the serial number on the appropriate line on your lab diagram.
{master:0}
lab@ex2> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis PG3713330145 EX4300-24T
Routing Engine 0 REV 06 650-044936 PG3713330145 EX4300-24T
FPC 0 REV 06 650-044936 PG3713330145 EX4300-24T
CPU BUILTIN BUILTIN FPC CPU

Lab 5–16 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
PIC 0 REV 06 BUILTIN BUILTIN 24x 10/100/1000 Base-T
PIC 1 REV 06 BUILTIN BUILTIN 4x 40GE QSFP+
Xcvr 0 REV 01 740-044512 MOC13405122192 QSFP+-40G-CU50CM
Xcvr 1 REV 01 740-044512 MOC13405122146 QSFP+-40G-CU50CM
Xcvr 2 REV 01 740-038624 14146087 QSFP+-40G-CU3M
Xcvr 3 REV 01 740-038624 1412603F QSFP+-40G-CU3M
Power Supply 0 REV 01 740-046873 1EDE3290261 JPSU-350-AC-AFO-A
Fan Tray 0 Fan Module, Airflow Out (AFO)
Fan Tray 1 Fan Module, Airflow Out (AFO)

Question: What is the serial number for ex2?

Answer: The answer will vary by student. In this example, the


serial number is PG3713330145.

Question: How many FPCs exist?

Answer: There is only one FPC, FPC 0.

Step 2.24
Enter configuration mode and load the lab5-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{master:0}
lab@ex2> configure
Entering configuration mode

{master:0}[edit]
lab@ex2# load override dcx/lab5-start.config
load complete

{master:0}[edit]
lab@ex2# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@ex2>
Step 2.25
View the configuration for ex2 by issuing the show configuration command.
{master:0}
lab@ex2> show configuration
## Last commit: 2014-09-26 19:49:30 UTC by lab
version 13.2X51-D21.1;
system {
host-name ex2;
root-authentication {
encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA

www.juniper.net Virtual Chassis Fabric • Lab 5–17


Data Center Switching
ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/
O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/
gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/
Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/
zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBHx9e
lwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF2KHBSI
xL51lmIDW8Gql9hJfD/Dr/
NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu2C8
UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/
g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= configurator@server1.he"; ##
SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
interfaces {
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.136/26;
}
}
}
}

Lab 5–18 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Question: Which interfaces have been configured?

Answer: Only the vme interface has been configured.

Question: What is the IP address of the VME interface?

Answer: The answer will vary by student. In the example, the IP


address of ex2’s vme interface is 10.210.14.136.

Part 3: Configuring the Master RE

In this lab part, you will auto-provision a mixed VCF consisting of two REs and two linecards. The
QFX5100 Series switches (spines) will act as master (qfx1) and backup (qfx2) REs. The EX4300
Series switches (leafs) will act as line cards. Configuration of an auto-provisioned VCF must be
performed on the master RE. That means that all VCF configuration will be performed on qfx1.
Use the lab diagram titled “Network Diagram: Virtual Chassis Fabric Lab” for this part of the lab.
Step 3.1
Return to the console session opened for qfx1.
On qfx1, set the Virtual Chassis mode to a mixed VCF by issuing the request
virtual-chassis mode fabric mixed reboot command. qfx1 will reboot after this
command is issued. Wait until qfx1 has finished rebooting before continuing to the next step.
{master:0}
lab@qfx1> request virtual-chassis mode fabric mixed reboot
fpc0:
--------------------------------------------------------------------------
WARNING, Virtual Chassis Fabric mode enabled without a valid software license.

*** System shutdown message from root@qfx1 ***

System going down in 1 minute

Mode set to 'Fabric with mixed devices'. Rebooting system...

Question: Why do you think you specified the mixed modifier?

Answer: The mixed modifier was specified so that the VCF will
support the combination of QFX5100 and EX4300 Series in
your lab environment.

Step 3.2
Login to qfx1 using the lab and lab123 login credentials and view the status of the VCF by
issuing the show virtual-chassis status command.

www.juniper.net Virtual Chassis Fabric • Lab 5–19


Data Center Switching
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1> show virtual-chassis status

Fabric ID: c448.93df.7d39


Fabric Mode: Mixed
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 128 Master* Y F

Member ID for next new member: 1 (FPC 1)

Question: What route mode is qfx1 currently in?

Answer: qfx1 is currently in the fabric route mode.

Question: What fabric mode is qfx1 currently in? What does that
mean?

Answer: qfx1 is currently in mixed fabric mode. Mixed fabric


mode means that the VCF can support multiple chassis types
including QFX5100, QFX3500, QFX3600, and EX4300 Series
switches.

Step 3.3
Enter configuration mode and navigate to the [edit virtual-chassis] hierarchy.
Configure the VCF as an autoprovisioned VCF.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# edit virtual-chassis

{master:0}[edit virtual-chassis]
lab@qfx1# set auto-provisioned

Lab 5–20 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Step 3.4
Configure member (qfx1) to take on the RE role. Make sure to specify the serial number for qfx1
that you determined in the previous part of the lab.
{master:0}[edit virtual-chassis]
lab@qfx1# set member 0 role routing-engine

{master:0}[edit virtual-chassis]
lab@qfx1# set member 0 serial-number serial-qfx1
Step 3.5
Configure member 1 to take on the RE role. Make sure to specify the serial number for qfx2 that
you determined in the previous part of the lab.
{master:0}[edit virtual-chassis]
lab@qfx1# set member 1 role routing-engine

{master:0}[edit virtual-chassis]
lab@qfx1# set member 1 serial-number serial-qfx2
Step 3.6
View your configuration so far and if you are satisfied commit your configuration and exit to
operational mode.
{master:0}[edit virtual-chassis]
lab@qfx1# show
auto-provisioned;
member 0 {
role routing-engine;
serial-number VF3714170305;
}
member 1 {
role routing-engine;
serial-number VF3714170306;
}

{master:0}[edit virtual-chassis]
lab@qfx1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:0}
lab@qfx1>
Step 3.7
View the status of the VCF by issuing the show virtual-chassis status command.
{master:0}
lab@qfx1> show virtual-chassis status

Auto-provisioned Virtual Chassis Fabric


Fabric ID: c448.93df.7d39
Fabric Mode: Mixed

www.juniper.net Virtual Chassis Fabric • Lab 5–21


Data Center Switching
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* Y F

Question: How is the VCF being provisioned according to the


output? What does that mean?

Answer: According to the output, the VCF is auto-provisioned.


This means that only the spine devices need to be
preprovisioned. All leaf devices can be added dynamically to the
VCF simply by enabling the appropriate VCPs.

Question: Are all members of the VCF listed in the output of the
command? Why?

Answer: Only member 0 is listed. The reason for this is because


the master RE has not detected any VCCP neighbors.

Question: How does a member switch detect other members of


the VCF?

Answer: Members of a VCF detect other members through the


exchange of VCCP messages over VCPs.

Step 3.8
View the status of the VCPs by issuing the show virtual-chassis vc-port command.
lab@qfx1> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------

{master:0}
lab@qfx1>

Question: Are any VCPs enabled on the master RE?

Answer: No VCPs are currently enabled on the master RE.

Lab 5–22 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Step 3.9
Look at the diagram for this part of the lab.

Question: According to the diagram, what VCPs should be


enabled on the master RE so that it can form the appropriate
VCCP relationships.?

Answer: vcp-255/0/50 and vcp-255/0/51 should be enabled


on the master RE.

Step 3.10
Enable vcp-255/0/50 and vcp-255/0/51 on qfx1 by issuing the request
virtual-chassis vc-port set pic-slot 0 port port-number command for
each VCP.
{master:0}
lab@qfx1> request virtual-chassis vc-port set pic-slot 0 port 50
Port conversion initiated, use show virtual-chassis vc-port to verify

{master:0}
lab@qfx1> request virtual-chassis vc-port set pic-slot 0 port 51
Port conversion initiated, use show virtual-chassis vc-port to verify
Step 3.11
View the status of the VCPs by issuing the show virtual-chassis vc-port command.
{master:0}
lab@qfx1> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
0/50 Configured -1 Down 40000
0/51 Configured -1 Down 40000

Question: Are any VCPs enabled on the master RE?

Answer: Yes, the vcp-255/0/50 and vcp-255/0/51 are


enabled.

Question: What is the status of the VCPs? Why?

Answer: Both VCPs are in the down state because the


downstream switches have not had their VCPs enabled.

www.juniper.net Virtual Chassis Fabric • Lab 5–23


Data Center Switching

Part 4: Adding Members to the VCF

In this lab part you will add the remaining member switches to the VCF. To add a member to an
existing auto-provisioned VCF, you simply enable the appropriate VCP interfaces. Use the lab
diagram titled “Network Diagram: Virtual Chassis Fabric Lab” for this part of the lab.
Step 4.1
Return to the console session opened for ex1.
On ex1, enable vcp-255/1/3 by issuing the request virtual-chassis vc-port set
pic-slot 1 port 3 command.
{master:0}
lab@ex1> request virtual-chassis vc-port set pic-slot 1 port 3
Port conversion initiated, use show virtual-chassis vc-port to verify

{master:0}
lab@ex1>
Step 4.2
Enable vcp-255/1/2 on ex1 by issuing the request virtual-chassis vc-port set
pic-slot 1 port 2 command.

{master:0}
lab@ex1> request virtual-chassis vc-port set pic-slot 1 port 2
Port conversion initiated, use show virtual-chassis vc-port to verify
Step 4.3
Set the Virtual Chassis mode on ex1 to a mixed VCF by issuing the request
virtual-chassis mode fabric mixed reboot command. ex1 will reboot after this
command is issued. Wait until ex1 has finished rebooting before continuing to the next step.
{master:0}
lab@ex1> request virtual-chassis mode fabric mixed reboot
fpc0:
--------------------------------------------------------------------------
Mode set to 'Fabric with mixed devices'. Rebooting system...

{master:0}
lab@ex1>
*** System shutdown message from root@ex1 ***

System going down in 1 minute


Step 4.4
Login to ex1 using the lab and lab123 login credentials.
ex1 (ttyu0)

login: lab

Logging to master
Password:

Lab 5–24 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC
{master:0}
lab@qfx1>

Question: Do you notice anything interesting about the CLI


prompt? What does this mean?

Answer: Once you have logged in you should notice that your
session has been redirected to qfx1. This means that ex1 has
become a member of the VCF.

Step 4.5
View the status of the VCF by issuing the show virtual-chassis status command.
{master:0}
lab@qfx1> show virtual-chassis status

Auto-provisioned Virtual Chassis Fabric


Fabric ID: c448.93df.7d39
Fabric Mode: Mixed
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* Y F 2
vcp-255/0/50
2 (FPC 2) Prsnt PG3713360118 ex4300-24t 0 Linecard Y F 0
vcp-255/1/2

Question: What member ID and role does ex1 have in the VCF?

Answer: ex1 is member 2 and a linecard in the VCF.

Question: Why has ex1 not been assigned member ID 1?

Answer: Member ID 1 has been provisioned in the configuration


for qfx2’s serial number.

Step 4.6
View the configuration of the VCF using the show configuration command.
{master:0}
lab@qfx1> show configuration
## Last commit: 2014-09-26 20:50:12 UTC by lab
version 13.2X51-D21.1;
system {
host-name qfx1;
root-authentication {
encrypted-password "$1$KI99zGk6$MbYFuBbpLffu9tn2.sI7l1"; ## SECRET-DATA

www.juniper.net Virtual Chassis Fabric • Lab 5–25


Data Center Switching
ssh-dsa "ssh-dss AAAAB3NzaC1kc3MAAACBAMQrfP2bZyBXJ6PC7XXZ+MzErI8Jl6jah5L4/
O8BsfP2hC7EvRfNoX7MqbrtCX/9gUH9gChVuBCB+ERULMdgRvM5uGhC/
gs4UX+4dBbfBgKYYwgmisM8EoT25m7qI8ybpl2YZvHNznvO8h7kr4kpYuQEpKvgsTdH/
Jle4Uqnjv7DAAAAFQDZaqA6QAgbW3O/
zveaLCIDj6p0dwAAAIB1iL+krWrXiD8NPpY+w4dWXEqaV3bnobzPC4eyxQKBUCOr80Q5YBlWXVBHx9e
lwBWZwj0SF4hLKHznExnLerVsMuTMA846RbQmSz62vM6kGM13HFonWeQvWia0TDr78+rOEgWF2KHBSI
xL51lmIDW8Gql9hJfD/Dr/
NKP97w3L0wAAAIEAr3FkWU8XbYytQYEKxsIN9P1UQ1ERXB3G40YwqFO484SlyKyYCfaz+yNsaAJu2C8
UebDIR3GieyNcOAKf3inCG8jQwjLvZskuZwrvlsz/xtcxSoAh9axJcdUfSJYMW/
g+mD26JK1Cliw5rwp2nH9kUrJxeI7IReDp4egNkM4i15o= configurator@server1.he"; ##
SECRET-DATA
}
login {
user lab {
uid 2000;
class super-user;
authentication {
encrypted-password "$1$81ZPtsPx$2db9wN8zaZ4nFtk1qAuDe1"; ##
SECRET-DATA
}
}
}
services {
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
interfaces {
ge-1/0/14 {
vlan-tagging;
unit 301 {
vlan-id 301;
family inet {
address 172.16.1.2/24;
}
}
}
ge-2/0/7 {
vlan-tagging;
unit 301 {

Lab 5–26 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
vlan-id 301;
family inet {
address 172.16.1.1/24;
}
}
}
vme {
description "MGMT INTERFACE - DO NOT DELETE";
unit 0 {
family inet {
address 10.210.14.155/26;
}
}
}
}
routing-instances {
vr1 {
instance-type virtual-router;
interface ge-2/0/7.301;
}
vr2 {
instance-type virtual-router;
interface ge-1/0/14.301;
}
}
virtual-chassis {
auto-provisioned;
member 0 {
role routing-engine;
serial-number VF3714170305;
}
member 1 {
role routing-engine;
serial-number VF3714170306;
}
}

Question: What happened to the configuration and vme IP


address that had been configured on ex1 prior to being added
to the VCF?

Answer: Once a non-master member is added to a VCF, its


configuration is overridden by the configuration that exists on
the master RE.

Step 4.7
Return to the console session opened for qfx2.
On qfx2, set the Virtual Chassis mode to a mixed VCF by issuing the request
virtual-chassis mode fabric mixed reboot command. qfx2 will reboot after this
command is issued. Wait until qfx2 has finished rebooting before continuing to the next step.

www.juniper.net Virtual Chassis Fabric • Lab 5–27


Data Center Switching
{master:0}
lab@qfx2> request virtual-chassis mode fabric mixed reboot
fpc0:
--------------------------------------------------------------------------
WARNING, Virtual Chassis Fabric mode enabled without a valid software license.
Please contact Juniper Networks to obtain a valid Virtual Chassis Fabric
License.

Mode set to 'Fabric with mixed devices'. Rebooting system...

{master:0}
lab@qfx2>
*** System shutdown message from root@qfx2 ***

System going down in 1 minute


Step 4.8
Login to qfx2 using the lab and lab123 login credentials and view the status of the VCF by
issuing the show virtual-chassis status command.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx2> show virtual-chassis status

Fabric ID: 7f7b.ee63.23b0


Fabric Mode: Mixed
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170306 qfx5100-48s-6q 128 Master* Y F

Member ID for next new member: 1 (FPC 1)

Question: What route mode is qfx2 currently in?

Answer: qfx2 is currently in the fabric route mode.

Lab 5–28 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Question: What fabric mode is qfx2 currently in? What does that
mean?

Answer: qfx2 is currently in mixed fabric mode. Mixed fabric


mode means that the VCF can support multiple chassis types
including QFX5100, QFX3500, QFX3600, and EX4300 Series
switches.

Step 4.9
First, enable vcp-255/0/50 on qfx2 by issuing the request virtual-chassis vc-port
set pic-slot 0 port 50 command.
{master:0}
lab@qfx2> request virtual-chassis vc-port set pic-slot 0 port 50
Port conversion initiated, use show virtual-chassis vc-port to verify

Question: Although it is not required, why do you think you


enabled vcp-255/0/50 before enabling vcp-255/0/51? Why
does it make a difference? Look at the diagram to help answer
your question.

Answer: When you enable vcp-255/0/50 on qfx2 first, the


master RE will not be able to detect the new member. This will
allow you to quickly enable vcp-255/0/51 (next step) from the
console of qfx2. If you had enabled vcp-255/0/51 first, the
master RE will detect the new member and add it to the VCF.
Then you would have to wait for the master RE and new
member to synchronize and also for the console of qfx2 to be
redirected to the master RE. It will be after all of that before you
will finally be able to enable vcp-255/0/50.

Step 4.10
Enable vcp-255/0/51 on qfx2 by issuing the request virtual-chassis vc-port set
pic-slot 0 port 51 command. After issuing the command you will be logged out of qfx2.
Wait 60 seconds before moving to the next step.
{master:0}
lab@qfx2> request virtual-chassis vc-port set pic-slot 0 port 51
Port conversion initiated, use show virtual-chassis vc-port to verify

www.juniper.net Virtual Chassis Fabric • Lab 5–29


Data Center Switching
{master:0}
lab@qfx2>
qfx2 (ttyd0)

login:
Step 4.11
Login to qfx2 using the lab and lab123 login credentials.
qfx2 (ttyd0)

login: lab

Logging to master
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1>

Question: Do you notice anything interesting about the CLI


prompt? What does this mean?

Answer: Once you have logged in you should notice that your
session has been redirected to qfx1. This means that qfx2 has
become a member of the VCF.

Step 4.12
View the status of the VCF by issuing the show virtual-chassis status command.
{master:0}
lab@qfx1> show virtual-chassis status

Auto-provisioned Virtual Chassis Fabric


Fabric ID: c448.93df.7d39
Fabric Mode: Mixed
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* Y F 2
vcp-255/0/50
1 (FPC 1) Prsnt VF3714170306 qfx5100-48s-6q 129 Backup Y F 2
vcp-255/0/51
2 (FPC 2) Prsnt PG3713360118 ex4300-24t 0 Linecard Y F 0
vcp-255/1/2
1 vcp-255/1/3

Question: What is the member number of qfx2?

Answer: qfx2 has been added to the VCF as member 1 as


expected.

Lab 5–30 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Step 4.13
Return to the console session opened for ex2.
On ex2, enable vcp-255/1/2 and vcp-255/1/3 by issuing the request virtual-chassis
vc-port set pic-slot 1 port port-number command.
{master:0}
lab@ex2> request virtual-chassis vc-port set pic-slot 1 port 2
Port conversion initiated, use show virtual-chassis vc-port to verify

{master:0}
lab@ex2> request virtual-chassis vc-port set pic-slot 1 port 3
Port conversion initiated, use show virtual-chassis vc-port to verify
Step 4.14
Set the Virtual Chassis mode on ex2 to a mixed VCF by issuing the request
virtual-chassis mode fabric mixed reboot command. ex2 will reboot after this
command is issued. Wait until ex2 has finished rebooting before continuing to the next step.
{master:0}
lab@ex2> request virtual-chassis mode fabric mixed reboot
fpc0:
--------------------------------------------------------------------------
Mode set to 'Fabric with mixed devices'. Rebooting system...

{master:0}
lab@ex2>
*** System shutdown message from root@ex2 ***

System going down in 1 minute


Step 4.15
Login to ex2 using the lab and lab123 login credentials.
ex2 (ttyu0)

login: lab

Logging to master
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1>

Question: Do you notice anything interesting about the CLI


prompt? What does this mean?

Answer: Once you have logged in you should notice that your
session has been redirected to qfx1. This means that ex2 has
become a member of the VCF.

www.juniper.net Virtual Chassis Fabric • Lab 5–31


Data Center Switching
Step 4.16
View the status of the VCF by issuing the show virtual-chassis status command.
{master:0}
lab@qfx1> show virtual-chassis status

Auto-provisioned Virtual Chassis Fabric


Fabric ID: c448.93df.7d39
Fabric Mode: Mixed
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 129 Master* Y F 2
vcp-255/0/50
3 vcp-255/
0/51
1 (FPC 1) Prsnt VF3714170306 qfx5100-48s-6q 129 Backup Y F 3
vcp-255/0/50
2 vcp-255/
0/51
2 (FPC 2) Prsnt PG3713360118 ex4300-24t 0 Linecard Y F 0
vcp-255/1/2
1 vcp-255/1/3
3 (FPC 3) Prsnt PG3713330145 ex4300-24t 0 Linecard Y F 1
vcp-255/1/2
0 vcp-255/1/3

Question: What is the member number of ex2?

Answer: ex2 has been added to the VCF as member 3 as


expected.

Question: Are all of the members of the VCF active?

Answer: All members have taken on their appropriate role and


they are in the Prsnt state.

Question: What are the modes of each of the members of the


VCF?

Answer: All members are in the mixed and Fabric modes.

Part 5: Configuring the VCF

In this lab part you will configure a few of the interfaces for Ethernet switching. You will use the
member number to help determine the interfaces names. Use the lab diagram titled “Network
Diagram: Virtual Chassis Fabric Lab” for this part of the lab.

Lab 5–32 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Step 5.1
Look at the diagram for this part of the lab. Notice the two interfaces on the VCF that are
connected to the two virtual routers. Use your knowledge of member IDs to determine the name
of the interfaces. Fill in the spaces provided on the diagram.

Question: What are the names of the two interfaces?

Answer: The two interfaces are named ge-3/0/15 and ge-2/0/


6.

Step 5.2
Enter configuration mode and navigate to the [edit vlans] hierarchy. Configure a VLAN
called vlan_301 using a VLAN ID of 301.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# edit vlans

{master:0}[edit vlans]
lab@qfx1# set vlan_301 vlan-id 301
Step 5.3
Navigate to the [edit interfaces] hierarchy and configure each of the virtual router-facing
interfaces to perform Ethernet switching as trunk interfaces for VLAN 301 only. Commit your
configuration and exit to operational mode.
{master:0}[edit vlans]
lab@qfx1# top edit interfaces

{master:0}[edit interfaces]
lab@qfx1# set ge-3/0/15 unit 0 family ethernet-switching interface-mode trunk

{master:0}[edit interfaces]
lab@qfx1# set ge-3/0/15 unit 0 family ethernet-switching vlan members vlan_301

{master:0}[edit interfaces]
lab@qfx1# set ge-2/0/6 unit 0 family ethernet-switching interface-mode trunk

{master:0}[edit interfaces]
lab@qfx1# set ge-2/0/6 unit 0 family ethernet-switching vlan members vlan_301

{master:0}[edit interfaces]
lab@qfx1# commit and-quit
configuration check succeeds
fpc1:
commit complete
fpc2:
commit complete
fpc3:

www.juniper.net Virtual Chassis Fabric • Lab 5–33


Data Center Switching
commit complete
commit complete
Exiting configuration mode
Step 5.4
View the configured VLANs by issuing the show vlans command.
{master:0}
lab@qfx1> show vlans

Routing instance VLAN name Tag Interfaces


default-switch vlan_301 301
ge-2/0/6.0*
ge-3/0/15.0*

Question: What VLAN tag is supported on each of the newly


configured interfaces?

Answer: Both interfaces support VLAN tag 301.

Step 5.5
Verify proper operation by sending ICMP traffic from vr1 to vr2 using the ping 172.16.1.2
routing-instance vr1 count 5 command.
{master:0}
lab@qfx1> ping 172.16.1.2 routing-instance vr1 count 5
PING 172.16.1.2 (172.16.1.2): 56 data bytes
64 bytes from 172.16.1.2: icmp_seq=0 ttl=64 time=61.719 ms
64 bytes from 172.16.1.2: icmp_seq=1 ttl=64 time=41.115 ms
64 bytes from 172.16.1.2: icmp_seq=2 ttl=64 time=33.014 ms
64 bytes from 172.16.1.2: icmp_seq=3 ttl=64 time=29.075 ms
64 bytes from 172.16.1.2: icmp_seq=4 ttl=64 time=33.030 ms

--- 172.16.1.2 ping statistics ---


5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 29.075/39.591/61.719/11.738 ms

Question: Were the pings successful?

Answer: The pings should have been successful.

Step 5.6
View the MAC table of the VCF by issuing the show ethernet-switching table command
to see if MAC addresses are being learned by the VCF.
{master:0}
lab@qfx1> show ethernet-switching table

MAC flags (S - static MAC, D - dynamic MAC, L - locally learned, P - Persistent


static
SE - statistics enabled, NM - non configured MAC, R - remote PE MAC)

Lab 5–34 • Virtual Chassis Fabric www.juniper.net


Data Center Switching

Ethernet switching table : 2 entries, 2 learned


Routing instance : default-switch
Vlan MAC MAC Age Logical
name address flags interface
vlan_301 4c:96:14:e6:88:71 D - ge-3/0/15.0
vlan_301 4c:96:14:e8:e6:0a D - ge-2/0/6.0

Question: Are MAC addresses being learned by the VCF?

Answer: MAC addresses should be learned by the VCF.

Part 6: Managing a VCF Using Space

In this lab part, you perform basic management operations for your VCF using Junos Space.
Specifically, you will perform the discovery task and add your VCF in the Network Director
application. You then navigate the user interface and explore some of the management
functions. Use the lab diagram titled “Network Diagram: Virtual Chassis Fabric Lab” for this part
of the lab.
Step 6.1
Take a look at the diagram and notice the location of the Junos Space server.

Question: In order to communicate with the Space server, what


interface must be configured with IP addressing on the VCF?

Answer: You must configure the appropriate addressing on the


ge-0/0/0 interface of the VCF so that it can communicate with
the Space server.

Step 6.2
Enter configuration mode and issue show system services and answer the following
questions.
{master:0}
lab@qfx1> configure
Entering configuration mode

{master:0}[edit]
lab@qfx1# show system services
ftp;
ssh {
max-sessions-per-connection 32;
}
telnet;

www.juniper.net Virtual Chassis Fabric • Lab 5–35


Data Center Switching
Question: What service is required for Network Director to
discover and manage a VCF?

Answer: The NETCONF service using SSH must be enabled for


Network Director to discover and manage a VCF.

Step 6.3
Enable the NETCONF service with SSH.
{master:0}[edit]
lab@qfx1# set system services netconf ssh
Step 6.4
Enable SNMP version 2 with a defined community of public in order for the SNMP probe and
topology discovery operation performed through SNMP to work properly.
{master:0}[edit]
lab@qfx1# set snmp community public
Step 6.5
Navigate to the [edit interfaces] hierarchy and configure the ge-0/0/0 interface with the
addressing shown in the lab diagram. Once enabled, activate the configuration changes using
the commit command.
{master:0}[edit]
lab@qfx1# edit interfaces

{master:0}[edit interfaces]
lab@qfx1# set ge-0/0/0 unit 0 family inet address 172.25.10.21/24

{master:0}[edit interfaces]
lab@qfx1# commit
configuration check succeeds
fpc1:
commit complete
fpc2:
commit complete
fpc3:
commit complete
commit complete

{master:0}[edit interfaces]
lab@qfx1#
Step 6.6
Verify the ability to communicate between the VCF and the Space server by issuing the command
run ping 172.25.10.136 count 5 command.
{master:0}[edit interfaces]
lab@qfx1# run ping 172.25.10.136 count 5
PING 172.25.10.136 (172.25.10.136): 56 data bytes
64 bytes from 172.25.10.136: icmp_seq=0 ttl=64 time=41.107 ms
Lab 5–36 • Virtual Chassis Fabric www.juniper.net
Data Center Switching
64 bytes from 172.25.10.136: icmp_seq=1 ttl=64 time=22.033 ms
64 bytes from 172.25.10.136: icmp_seq=2 ttl=64 time=22.042 ms
64 bytes from 172.25.10.136: icmp_seq=3 ttl=64 time=22.158 ms
64 bytes from 172.25.10.136: icmp_seq=4 ttl=64 time=22.162 ms

--- 172.25.10.136 ping statistics ---


5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 22.033/25.900/41.107/7.603 ms

Question: Did the pings to the Space server succeed?

Answer: The pings should be successful. If they were not


successful, please inform your instructor.

Step 6.7
From your landing pad VM, open the FireFox browser located under the Applications >
Internet menu.

Step 6.8
Open the Junos Space login page by entering 172.25.10.136 in the address bar. When
prompted, enter super and lab123 as the username and password and click the Log In
button to login to the Junos Space GUI.
Note
Add and accept any security exceptions that may pop up
when accessing the Junos Space Management Platform!

www.juniper.net Virtual Chassis Fabric • Lab 5–37


Data Center Switching

Lab 5–38 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Step 6.9
From the drop-down menu options under the Applications panel, select the Network
Director application.

Question: Were you successfully directed to the Network


Director application interface?

Answer: Yes, as shown in the sample output you should now see
the Network Director application interface. If not, check your
work and, if needed, consult with your instructor.

Step 6.10
Once the Network Director application opens. From the Views drop-down menu, select
Logical View and examine the resulting web page.

www.juniper.net Virtual Chassis Fabric • Lab 5–39


Data Center Switching

Lab 5–40 • Virtual Chassis Fabric www.juniper.net


Data Center Switching

Question: Are there currently any devices discovered or listed


under the Logical View panel on the left-hand side of the
web page?

Answer: No, as shown in the sample output there should not


currently be any devices discovered or listed under the
Logical View panel. We discover the VCF, at which time it
will be added to the inventory, in a subsequent step.

Note
Alternatively, you could navigate to the Network Director application interface
directly using https://address/networkdirector/ in your browser.

Step 6.11
Under the Tasks pane, click on the Discover Devices option. Next, in the main window,
click the Add button to add a new device target.

www.juniper.net Virtual Chassis Fabric • Lab 5–41


Data Center Switching

Step 6.12
In the Add Device Target dialogue box, use the IP option and enter the IP address
assigned to your VCF’s ge-0/0/0 interface (172.25.10.21). Next, click Add to continue.

Step 6.13
Back in the main pane, ensure the newly added device target entry associated with your VCF is
selected and click Next to continue.

Lab 5–42 • Virtual Chassis Fabric www.juniper.net


Data Center Switching

Step 6.14
For the Discovery Options step, ensure the Use Ping and Use SNMP options are
selected. Next, click Add to add the credentials associated with your VCF.

www.juniper.net Virtual Chassis Fabric • Lab 5–43


Data Center Switching

Step 6.15
In the Add Device Credentials dialogue box, enter lab and lab123 as the username
and password and click Add to continue.

Step 6.16
Back in the main pane, ensure the newly added device credentials entry associated with your
VCF is selected and click Next to continue.

Lab 5–44 • Virtual Chassis Fabric www.juniper.net


Data Center Switching

Step 6.17
For the Schedule Options step, ensure the Run Now option is selected and click Next to
continue.

www.juniper.net Virtual Chassis Fabric • Lab 5–45


Data Center Switching

Step 6.18
For the Review step, review the discovery details associated with the target device and, once
you are comfortable with the specified variables, click Finish. Note that, if needed, you can
click Edit to change a defined value.

Lab 5–46 • Virtual Chassis Fabric www.juniper.net


Data Center Switching

Step 6.19
When prompted with the Job Status message, click OK to close the message box. Next, view the
job details shown on the resulting screen for the job that just finished.

www.juniper.net Virtual Chassis Fabric • Lab 5–47


Data Center Switching
Question: Did the discovery job successfully finish?

Answer: Yes, as shown in the sample output, the discovery job


should have successfully finished.

Question: Has your VCF successfully been discovered by and


added to the inventory in the Network Director application?

Answer: Yes, as shown in the sample output, the Number of


Devices Succeeded shows a value of 1, which indicates
that the target device was found and added to the system’s
inventory. Note that you should also see a new Fabric folder
added in the Logical View pane on the left-hand side of the
web page.

Step 6.20
In the Logical View pane on the left-hand side of the web page, expand the newly added
Fabric folder and VCF to inspect which elements have been discovered.

Question: Which components have been discovered and are


listed as part of the VCF?

Answer: As shown in the sample output, you should see


sub-folders within the qfx1 folder for the Spines and Leafs of the
VCF.

Step 6.21
Select the qfx1 folder > View VC/VCF Connectivity and mouse over each of the members in the
diagram.

Lab 5–48 • Virtual Chassis Fabric www.juniper.net


Data Center Switching

Question: Are all members of the VCF shown in Topology


diagram?

Answer: Yes, as shown in the sample output, all of the member


switches should now be shown as part of the VCF.

Question: Can you determine which device is acting as the


master RE for the VCF? How can you tell?

Answer: Both Spine devices have a star. The master RE will have
a yellow star and the backup RE will have a gray star. In the
diagram, member 0 is the master RE.

www.juniper.net Virtual Chassis Fabric • Lab 5–49


Data Center Switching
Question: Is the VCP connectivity in the topology diagram
accurate depicted when compared to what you configured
earlier in the lab?

Answer: The topology should match you configuration exactly.

Step 6.22
Explore the Network Director user interface on your own and discover some of its management
and monitoring capabilities. Some sample objectives include:
• Locate the serial numbers of the system components.
• Display the current configuration on the VCF.
• Determine the status of all logical interfaces.
• Verify reachability to a known host (e.g. 10.210.14.130).

Note
In some cases there may be multiple
ways to accomplish the same task!

Note
Configuration management is outside the scope
of this class. To learn more about Junos Space
and Network Director, please consider attending
the courses dedicated to those topics.

Part 7: Resetting the Members of the VCF

In this lab part, you will remove each of the members from the VCF and return them to a
standalone, Virtual Chassis state (the default state). Use the lab diagram titled “Network
Diagram: Virtual Chassis Fabric Lab” for this part of the lab.
Step 7.1
Return to the console session opened for ex2.
If necessary on ex2, enter configuration mode. Delete the netconf service as well as the snmp
configuration. Commit you configuration and exit to operational mode.
{master:0}[edit]
lab@qfx1# delete system services netconf

{master:0}[edit]
lab@qfx1# delete snmp

Lab 5–50 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
{master:0}[edit]
lab@qfx1# commit and-quit
configuration check succeeds
fpc1:
commit complete
fpc2:
commit complete
fpc3:
commit complete
commit complete
Exiting configuration mode

{master:0}
lab@qfx1>
Step 7.2
Delete each of the VCPs of ex2 by issuing the request virtual-chassis vc-port
delete pic-slot 1 port port-number member 3 command for each VCP. You will be
logged out of the VCF.
{master:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 1 port port-number
member 3
fpc2:
--------------------------------------------------------------------------
vc-port successfully deleted

{master:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 1 port port-number
member 3

qfx1 (ttyu0)

login:
Step 7.3
Attempt to log back into ex2 using the lab and lab123 login credentials. ex2 will attempt to log
you into master RE of the VCF. After 10 attempts, it will allow you to log directly into the ex2
switch.
qfx1 (ttyu0)

login: lab

Logging to master
..........
Connection to master failed, enabling local login
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis fabric (VCF) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.

www.juniper.net Virtual Chassis Fabric • Lab 5–51


Data Center Switching
warning: Full CLI access is provided by the Virtual Chassis Fabric Master (VCF-M)
chassis.
warning: The VCF-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VCF-M to use CLI.
{linecard:3}
lab@qfx1>
Step 7.4
Enter configuration mode and load the lab5-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{linecard:3}
lab@qfx1> configure

{linecard:3}[edit]
lab@qfx1# load override dcx/lab5-start.config
load complete

{linecard:3}[edit]
lab@qfx1# commit and-quit
commit complete
Exiting configuration mode

{linecard:3}
lab@ex2>
Step 7.5
Change the mode of ex2 so that it operates in non-mixed Virtual Chassis mode by disabling
mixed and fabric mode. Also, make sure that it reboots immediately. Wait for ex2 to reboot
before continuing.
{linecard:3}
lab@ex2> request virtual-chassis mode mixed fabric disable reboot
fpc3:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with similar devices'. Rebooting system...

{linecard:3}
lab@ex2>
*** System shutdown message from root@ex2 ***

System going down in 1 minute


Step 7.6
Log back into ex2 using the lab and lab123 login credentials. ex2 will attempt to log into the
Virtual Chassis. After 10 attempts, it will allow you to log directly into the ex2 switch. View the
status of the Virtual Chassis by issuing the show virtual-chassis status command.
ex2 (ttyu0)

login: lab

Logging to master
..........

Lab 5–52 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Connection to master failed, enabling local login
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:3}
lab@ex2> show virtual-chassis status

Virtual Chassis ID: c448.93df.7d39


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) NotPrsnt VF3714170305 qfx5100-48s-6q
1 (FPC 1) NotPrsnt VF3714170306 qfx5100-48s-6q
2 (FPC 2) NotPrsnt PG3713360118 ex4300-24t
3 (FPC 3) Inactive PG3713330145 ex4300-24t 128 Linecard* N VC

Question: Why are members 0, 1, and 3 still listed in the


output?

Answer: Even after a reboot, a member will remember it’s role


as well as the other members roles.

Question: What is the status of member 3 (ex2)?

Answer: Member 3 is in the Inactive state since it has


detected a split Virtual Chassis.

Step 7.7
Reactivate member 3 by issuing the request virtual-chassis reactivate command.
You will be logged out of ex2.
{linecard:3}
lab@ex2> request virtual-chassis reactivate

This member split from a virtual chassis. Please make sure that no active
switch belonging to this virtual chassis has conflicting configuration.

Do you want to continue ? [yes,no] (no) yes

{linecard:3}
lab@ex2>

www.juniper.net Virtual Chassis Fabric • Lab 5–53


Data Center Switching
ex2 (ttyu0)

login:
Step 7.8
Log back into ex2 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command.
ex2 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:3}
lab@ex2> show virtual-chassis status

Virtual Chassis ID: 52c3.f6e7.5bff


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
3 (FPC 3) Prsnt PG3713330145 ex4300-24t 128 Master* N VC

Member ID for next new member: 0 (FPC 0)

Question: What is the state and role of member 3 (ex2)?

Answer: Member 3 is in the Prsnt state and is in the master RE


role.

Step 7.9
Although not required, the final step in converting ex2 back to standalone mode is to renumber
its member ID to 0. Perform this step by issuing the request virtual-chassis
renumber member-id 3 new-member-id 0 command. You will be automatically logged
out of ex2.
{master:3}
lab@ex2> request virtual-chassis renumber member-id 3 new-member-id 0

To move configuration specific to member ID 3 to member ID 0, please


use the replace command. e.g. replace pattern ge-3/ with ge-0/

If member-specific configuration groups are present, perform a


"commit full" to synchronize inheritance with the new member number.

Do you want to continue ? [yes,no] (no) yes

{master:3}
lab@ex2>

Lab 5–54 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
ex2 (ttyu0)

login:
Step 7.10
Log back into ex2 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command. Log out of ex2 when
complete.
ex2 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex2> show virtual-chassis status

Virtual Chassis ID: 47ad.f5bc.753c


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt PG3713330145 ex4300-24t 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

{master:0}
lab@ex2> exit

ex2 (ttyu0)

login:

Question: Is ex2 in standalone mode?

Answer: Yes, ex2 has been successfully removed from the VCF.

Step 7.11
Return to the console session opened for qfx2.
On qfx2, attempt to log back in using the lab and lab123 login credentials. Delete vcp-255/0/
50 of qfx2 by issuing the request virtual-chassis vc-port delete pic-slot 0
port 50 member 1 command.
{master:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 0 port 50 member 1
fpc1:
--------------------------------------------------------------------------
vc-port successfully deleted

www.juniper.net Virtual Chassis Fabric • Lab 5–55


Data Center Switching
Step 7.12
Delete vcp-255/0/51 of qfx2 by issuing the request virtual-chassis vc-port
delete pic-slot 0 port 51 member 1 command. You will be logged out of the Virtual
Chassis.
{master:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 0 port 51 member 1

qfx1 (ttyu0)

login:

Step 7.13
Attempt to log back into qfx2 using the lab and lab123 login credentials. Since qfx2 was the
backup RE and detected a VCF split it becomes the master RE for its local VCF.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:1}
lab@qfx1> show virtual-chassis

Auto-provisioned Virtual Chassis Fabric


Fabric ID: c448.93df.7d39
Fabric Mode: Mixed
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) NotPrsnt VF3714170305 qfx5100-48s-6q
1 (FPC 1) Prsnt VF3714170306 qfx5100-48s-6q 129 Master* Y F
Step 7.14
Enter configuration mode and load the lab5-start.config configuration file from the
/var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{master:1}
lab@qfx1> configure
Entering configuration mode

{master:1}[edit]
lab@qfx1# load override dcx/lab5-start.config
load complete

{master:1}[edit]
lab@qfx1# commit and-quit
configuration check succeeds
commit complete
Exiting configuration mode

{master:1}
lab@qfx2>

Lab 5–56 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Step 7.15
Change the mode of qfx2 so that it operates in non-mixed Virtual Chassis mode by disabling the
modes mixed and fabric. Also, make sure that it reboots immediately. Wait for qfx2 to reboot
before continuing.
lab@qfx2> request virtual-chassis mode mixed fabric disable reboot
fpc1:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with similar devices'. Rebooting system...

*** System shutdown message from root@qfx2 ***

System going down in 1 minute


Step 7.16
Log back into qfx2 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:1}
lab@qfx2> show virtual-chassis status

Virtual Chassis ID: c448.93df.7d39


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) NotPrsnt VF3714170305 qfx5100-48s-6q
1 (FPC 1) Prsnt VF3714170306 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 2 (FPC 2)

Question: What is the status of member 1 (qfx2)?

Answer: Member 1 is in the Prsnt state and is the master RE


for it’s Virtual Chassis.

Step 7.17
Since member 0 (qfx1) is being removed from the topology, use the request
virtual-chassis recycle member-id 0 command to allow for another switch to be
assigned member ID 0.
{master:1}
lab@qfx2> request virtual-chassis recycle member-id 0

www.juniper.net Virtual Chassis Fabric • Lab 5–57


Data Center Switching
Step 7.18
Although not required, the final step in converting qfx2 back to standalone mode is to renumber
its member ID to 0. Perform this step by issuing the request virtual-chassis
renumber member-id 1 new-member-id 0 command. You will be automatically logged
out of qfx2.
{master:3}
lab@qfx2> request virtual-chassis renumber member-id 1 new-member-id 0

To move configuration specific to member ID 1 to member ID 0, please


use the replace command. e.g. replace pattern ge-3/ with ge-0/

If member-specific configuration groups are present, perform a


"commit full" to synchronize inheritance with the new member number.

Do you want to continue ? [yes,no] (no) yes

{master:3}
lab@qfx2>
qfx2 (ttyd0)

login:
Step 7.19
Log back into qfx2 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command. Log out of qfx2 when
complete.
qfx2 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx2> show virtual-chassis status

Virtual Chassis ID: 7f7b.ee63.23b0


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170306 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

{master:0}
lab@qfx2> exit

qfx2 (ttyu0)

login:

Lab 5–58 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Question: Is qfx2 in standalone mode?

Answer: Yes, qfx2 has been successfully removed from the VCF.

Step 7.20
Return to the console session opened for ex1.
On ex1, attempt to log back in using the lab and lab123 login credentials. Delete vcp-255/1/
3 of ex1 by issuing the request virtual-chassis vc-port delete pic-slot 1
port 3 member 2 command.
qfx1 (ttyu0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:2}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 1 port 3 member 2
fpc1:
--------------------------------------------------------------------------
vc-port successfully deleted

{linecard:2}
lab@qfx1>
Step 7.21
Delete vcp-255/1/2 of ex1 by issuing the request virtual-chassis vc-port delete
pic-slot 1 port 2 member 1 command. You will be logged out of the Virtual Chassis.
{linecard:1}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 1 port 2 member 2

qfx1 (ttyu0)

login:

Step 7.22
Attempt to log back into ex1 using the lab and lab123 login credentials. Enter configuration
mode and load the lab5-start.config configuration file from the /var/home/lab/
dcx/ directory. Commit your changes and return to operational mode.
qfx1 (ttyu0)

login: lab
www.juniper.net Virtual Chassis Fabric • Lab 5–59
Data Center Switching
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status command
executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:2}
lab@qfx1> configure
Entering configuration mode

{linecard:2}[edit]
lab@qfx1# load override dcx/lab5-start.config
load complete

{linecard:2}[edit]
lab@qfx1# commit and-quit
commit complete
Exiting configuration mode

{linecard:2}
lab@ex1>
Step 7.23
Change the mode of ex1 so that it operates in non-mixed Virtual Chassis mode by disabling
mixed and fabric mode. Also, make sure that it reboots immediately. Wait for ex1 to reboot
before continuing.
{linecard:2}
lab@ex1> request virtual-chassis mode mixed fabric disable reboot
fpc2:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with similar devices'. Rebooting system...

*** System shutdown message from root@ex1 ***

System going down in 1 minute

{linecard:2}
lab@ex1>
Step 7.24
Log back into ex1 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command.
ex1 (ttyu0)

login: lab
Password:

Lab 5–60 • Virtual Chassis Fabric www.juniper.net


Data Center Switching

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:2}
lab@ex1> show virtual-chassis status

Virtual Chassis ID: c448.93df.7d39


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) NotPrsnt VF3714170305 qfx5100-48s-6q
1 (FPC 1) NotPrsnt VF3714170306 qfx5100-48s-6q
2 (FPC 2) Inactive PG3713360118 ex4300-24t 128 Linecard* N VC
3 (FPC 3) NotPrsnt PG3713330145 ex4300-24t

Question: What is the status of member 2 (ex1)?

Answer: Member 2 is in the Inactive state.

Step 7.25
Reactivate member 2 by issuing the request virtual-chassis reactivate command.
You will be logged out of ex1.
{linecard:2}
lab@ex1> request virtual-chassis reactivate

This member split from a virtual chassis. Please make sure that no active
switch belonging to this virtual chassis has conflicting configuration.

Do you want to continue ? [yes,no] (no) yes

{linecard:2}
lab@ex1>
ex1 (ttyu0)

login:
Step 7.26
Log back into ex1 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command.
ex1 (ttyu0)

login: lab

www.juniper.net Virtual Chassis Fabric • Lab 5–61


Data Center Switching
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:2}
lab@ex1> show virtual-chassis status

Virtual Chassis ID: 6d18.0316.f3a1


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
2 (FPC 2) Prsnt PG3713360118 ex4300-24t 128 Master* N VC

Member ID for next new member: 0 (FPC 0)

Question: What is the state and role of member 2 (ex1)?

Answer: Member 2 is in the Prsnt state and is in the master RE


role.

Step 7.27
Although not required, the final step in converting ex1 back to standalone mode is to renumber
its member ID to 0. Perform this step by issuing the request virtual-chassis
renumber member-id 2 new-member-id 0 command. You will be automatically logged
out of ex1.
{master:2}
lab@ex1> request virtual-chassis renumber member-id 2 new-member-id 0

To move configuration specific to member ID 2 to member ID 0, please


use the replace command. e.g. replace pattern ge-2/ with ge-0/

If member-specific configuration groups are present, perform a


"commit full" to synchronize inheritance with the new member number.

Do you want to continue ? [yes,no] (no) yes

{master:2}
lab@ex1>
ex1 (ttyu0)

login:
Step 7.28
Log back into ex1 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command. Log out of ex1 when
complete.
ex1 (ttyu0)

login: lab
Password:

Lab 5–62 • Virtual Chassis Fabric www.juniper.net


Data Center Switching

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:49:28 UTC


{master:0}
lab@ex1> show virtual-chassis status

Virtual Chassis ID: c4fc.38d3.f363


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt PG3713360118 ex4300-24t 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

{master:0}
lab@ex1> exit

ex1 (ttyu0)

login:

Question: Is ex1 in standalone mode?

Answer: Yes, ex1 has been successfully removed from the VCF.

Step 7.29
Return to the console session opened for qfx1.
On qfx1, attempt to log back in using the lab and lab123 login credentials. Delete vcp-255/0/
50 of qfx1 by issuing the request virtual-chassis vc-port delete pic-slot 0
port 50 command.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 0 port 50
vc-port successfully deleted

www.juniper.net Virtual Chassis Fabric • Lab 5–63


Data Center Switching
Step 7.30
Delete vcp-255/0/51 of qfx1 by issuing the request virtual-chassis vc-port
delete pic-slot 0 port 51 command.
{linecard:0}
lab@qfx1> request virtual-chassis vc-port delete pic-slot 0 port 51
vc-port successfully deleted

{linecard:0}
lab@qfx1>
Step 7.31
Enter configuration mode and load the lab5-start.config configuration file from the /
var/home/lab/dcx/ directory. Commit your changes and return to operational mode.
{linecard:0}
lab@qfx1> configure
Entering configuration mode

{linecard:0}[edit]
lab@qfx1# load override dcx/lab5-start.config
load complete

{linecard:0}[edit]
lab@qfx1# commit and-quit

/config/license/JUNOS533858.lic:1:(0) JUNOS533858: licensed device [VF3714170305],


is not part of the virtual chassis

/config/license/JUNOS533859.lic:1:(0) JUNOS533859: licensed device [VF3714170306],


is not part of the virtual chassis
commit complete
Exiting configuration mode

{linecard:0}
lab@qfx1>
Step 7.32
Change the mode of qfx1 so that it operates in non-mixed Virtual Chassis mode by disabling
mixed and fabric mode. Also, make sure that it reboots immediately. Wait for qfx1 to reboot
before continuing.
{linecard:0}
lab@qfx1> request virtual-chassis mode mixed fabric disable reboot
fpc0:
--------------------------------------------------------------------------
Mode set to 'Virtual Chassis with similar devices'. Rebooting system...

{linecard:0}

*** System shutdown message from root@qfx1 ***

System going down in 1 minute

Lab 5–64 • Virtual Chassis Fabric www.juniper.net


Data Center Switching
Step 7.33
Log back into qfx1 using the lab and lab123 login credentials. qfx1 will attempt to log into the
Virtual Chassis. After 10 attempts, it will allow you to log directly into the qfx1 switch.View the
status of the Virtual Chassis by issuing the show virtual-chassis status command.
qfx1 (ttyd0)

login: lab

Logging to master
..........
Connection to master failed, enabling local login
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


warning: This chassis is operating in a non-master role as part of a
virtual-chassis (VC) system.
warning: Use of interactive commands should be limited to debugging and VC Port
operations.
warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.
warning: The VC-M can be identified through the show virtual-chassis status
command executed at this console.
warning: Please logout and log into the VC-M to use CLI.
{linecard:0}
lab@qfx1> show virtual-chassis status

Virtual Chassis ID: deb2.dc91.9c55


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Inactive VF3714170305 qfx5100-48s-6q 128 Linecard* N VC
1 (FPC 1) NotPrsnt PG3713360118 ex4300-24t
2 (FPC 2) NotPrsnt PG3713330145 ex4300-24t
3 (FPC 3) NotPrsnt VF3714170306 qfx5100-48s-6q

{linecard:0}
lab@qfx1>

Question: What is the status of member 0 (qfx1)?

Answer: Member 0 is in the Inactive state since it has


detected a split Virtual Chassis.

Step 7.34
Reactivate member 0 by issuing the request virtual-chassis reactivate command.
You will be logged out of qfx1.
lab@qfx1> request virtual-chassis reactivate

This member split from a virtual chassis. Please make sure that no active
switch belonging to this virtual chassis has conflicting configuration.

www.juniper.net Virtual Chassis Fabric • Lab 5–65


Data Center Switching
Do you want to continue ? [yes,no] (no) yes

{linecard:0}
lab@qfx1>
qfx1 (ttyd0)

login:
Step 7.35
Log back into qfx1 using the lab and lab123 login credentials. View the status of the Virtual
Chassis by issuing the show virtual-chassis status command. Log out of qfx1 when
complete.
qfx1 (ttyd0)

login: lab
Password:

--- JUNOS 13.2X51-D21.1 built 2014-05-29 11:41:16 UTC


{master:0}
lab@qfx1> show virtual-chassis status

Virtual Chassis ID: c448.93df.7d39


Virtual Chassis Mode: Enabled
Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt VF3714170305 qfx5100-48s-6q 128 Master* N VC

Member ID for next new member: 1 (FPC 1)

{master:0}
lab@qfx1> exit

qfx1 (ttyu0)

login:

Question: What is the state and role of member 0 (qfx1)?

Answer: Member 0 is in the Prsnt state and is in the master RE


role.

Question: Is qfx1 in standalone mode?

Answer: Yes, qfx1 has been successfully removed from the VCF.

STOP Tell your instructor that you have completed this lab.

Lab 5–66 • Virtual Chassis Fabric www.juniper.net


Data Center Switching

www.juniper.net Virtual Chassis Fabric • Lab 5–67


Data Center Switching

Lab 5–68 • Virtual Chassis Fabric www.juniper.net

S-ar putea să vă placă și