Add Course Title Here

High Availability Features

© 2010 Juniper Networks, Inc. All rights reserved. | www.juniper.net

What Is High Availability?

 The ability to ensure a high degree of operational

continuity to a resource for a user community
•Typically measured over a specific period of time

Resources

User Community

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 2

Chapter 1: Course Introduction 1

Add Course Title Here

High Availability Networks

 High availability networks include provisions that allow

for the maximum amount of uptime and accessibility
Key Considerations
1. Is the base functionality of the network’s hardware,
software, protocols, and overall operations protected?
2. When a failure occurs, how will the overall system or
network react and what level of recovery can be expected?

Increase uptime and accessibility

Decrease downtime

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 3

High Availability Features

 EX Series switches support a number of features to

help increase uptime and availability including:
•Link aggregation groups (LAGs)
•Redundant Trunk Groups (RTG)
•Virtual Chassis

Resources

User Community

Note: Feature support varies by product; check the product-specific documentation for support details

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 4

Chapter 1: Course Introduction 2

Add Course Title Here

What Is It?

 Link aggregation combines multiple Ethernet

interfaces in to a single link layer interface, also
known as a link aggregation group (LAG) or bundle
•Defined in the 802.3ad standard
Participating interfaces are
Commonly used on
known as member links
trunk port connections

Switch-1 Switch-2
ge-0/0/12

ge-0/0/13
Aggregation

Access

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 5

Benefits of 802.3ad Link Aggregation

 Benefits of 802.3ad link aggregation include:

•Increases bandwidth
•Provides link efficiency
•Creates physical layer redundancy

Switch-1 Switch-2
ge-0/0/12

ge-0/0/13
Aggregation

Access

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 6

Chapter 1: Course Introduction 3

Add Course Title Here

Link Requirements and Considerations

 Interface requirements and considerations include:

•Duplex and speed must match
•Up to eight member links per LAG
•Member links do not need to be contiguous ports nor must
they be on the same switch when part of a Virtual Chassis

Switch-1 Switch-2
ge-0/0/1
…
…
…
ae0 ge-0/0/5 ae0
ge-0/0/10
…
…
ge-0/0/13

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 7

Traffic Processing and Forwarding

 Traffic processing and forwarding considerations:

•CPU control traffic is always sent on the lowest member link
•IP traffic hashing uses Layer 2, Layer 3, and Layer 4 details
•Non-IP traffic hashing uses source and destination MAC
addresses

Control traffic

Switch-1 Switch-2
ge-0/0/1

IP traffic
Traffic is shared across
ae0 ae0
all member links
Non-IP traffic
ge-0/0/13

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 8

Chapter 1: Course Introduction 4

Add Course Title Here

Link Aggregation Control Protocol (LACP)

 LACP performs link monitoring and controls the

member links that form a single logical channel
 You can set the LACP mode as active or passive:
•Active mode initiates transmission of LACP packets
•Passive mode responds to LACP packets
Switch-1 Switch-2
ae1 ae1

ae0 Active Active

Aggregation

Access

ae0 Passive
Note: At least one device must be configured for
active mode for the link to become operational.

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 9

Implementing LAGs (1 of 2)

 Create an aggregated Ethernet interface:

{master:0}[edit chassis]
user@Switch-1# run show interfaces terse | match ae0

{master:0}[edit chassis]
user@Switch-1# set aggregated-devices ethernet device-count 1

{master:0}[edit chassis]
user@Switch-1# commit
configuration check succeedscommit complete

{master:0}[edit chassis]
user@Switch-1# run show interfaces terse | match ae0
ae0 up down
Link state remains down until operational
member links are added to LAG

Switch-1 Switch-2
ge-0/0/12

ae0 ae0
ge-0/0/13

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 10

Chapter 1: Course Introduction 5

Add Course Title Here

Implementing LAGs (2 of 2)

 Configure the aggregated Ethernet interface and

associate desired member links with the LAG:
{master:0}[edit interfaces]
user@Switch-1# set ae0 unit 0 family ethernet-switching

{master:0}[edit interfaces]
user@Switch-1# set ae0 aggregated-ether-options lacp active

{master:0}[edit interfaces]
user@Switch-1# set ge-0/0/12 ether-options 802.3ad ae0

{master:0}[edit interfaces]
user@Switch-1# set ge-0/0/13 ether-options 802.3ad ae0
edit interface ae0 aggregated-ether-options lacp
{master:0}[edit interfaces]
user@Switch-1# commit
Set periodic fast | slow (1s or 30s)
configuration check succeedscommit complete when active and passive interface have different rate, the
reciever will be preferred
{master:0}[edit interfaces]
user@Switch-1# run show interfaces terse | match ae0
ge-0/0/12.0 up up aenet --> ae0.0 Switch-1 Switch-2
ge-0/0/13.0 up up aenet --> ae0.0 ge-0/0/12
ae0 up up ae0 ae0
ae0.0 up up eth-switch ge-0/0/13

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 11

Monitoring LAGs

 Use the show interfaces output to determine

state information for aggregated interfaces:
{master:0}
user@Switch-1> show interfaces terse | match ae0
ge-0/0/12.0 up up aenet --> ae0.0
ge-0/0/13.0 up up aenet --> ae0.0
ae0 up up
ae0.0 up up eth-switch

{master:0}
user@Switch-1> show interfaces extensive ae0.0 | find "LACP Statistics:"
LACP Statistics: LACP Rx LACP Tx Unknown Rx Illegal Rx
ge-0/0/12.0 26 516 0 0
ge-0/0/13.0 25 519 0 0
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
ge-0/0/12.0 0 0 0 0
ge-0/0/13.0 0 0 0 0
Protocol eth-switch, Generation: 195, Route table: 0
Flags: None

•Note that other commands exist that show similar details

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 12

Chapter 1: Course Introduction 6

Add Course Title Here

Test Your Knowledge

 Given the sample outputs, can you guess what might

be causing ae0.0 to remain in the down state?
{master:0}
lab@Switch-1> show interfaces terse | match ae0
ge-0/0/12.0 up up aenet --> ae0.0
ge-0/0/13.0 up up aenet --> ae0.0
ae0 up down
ae0.0 up down eth-switch

{master:0}
lab@Switch-1> show interfaces extensive ae0.0 | find "LACP Statistics:"
LACP Statistics: LACP Rx LACP Tx Unknown Rx Illegal Rx
ge-0/0/12.0 0 224 0 0
ge-0/0/13.0 0 223 0 0
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
ge-0/0/12.0 0 0 0 0
ge-0/0/13.0 0 0 0 0
Protocol eth-switch, Generation: 195, Route table: 0
Flags: None

•The remote device does not have LACP enabled

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 13

What Is It?

 A redundant trunk group provides a quick and simple

failover mechanism for redundant Layer 2 links
•Can be used as a replacement for STP on access switches
that are connected to two aggregation switches

Switch-1 Switch-2
ge-0/0/1
RSTP
ge-0/0/2

Aggregation
Access

RTG

Switch-3 Switch-4 Switch-5

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 14

Chapter 1: Course Introduction 7

Add Course Title Here

How Does It Work?

 Only active link is used to forward traffic, other links

serve as backup links and do not forward traffic
•When active link fails, a backup link becomes active

Switch-1 Switch-2
ge-0/0/1
RSTP
ge-0/0/2

Aggregation
Access
Active Link Backup Link
Only Data traffic is blocked. Control traffic such as LLDP, LACP still can run
RTG

Switch-3

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 15

Configuration Considerations

 RTG is typically only configured on access switches

•RTG and STP are mutually exclusive on a given port
•STP BPDUs received on RTG links are discarded
•STP is configured on aggregation switches

Switch-1 Switch-2
ge-0/0/1
RSTP
ge-0/0/2

Aggregation
Access
ge-0/0/8 ge-0/0/10
RTG
Switch-3 Switch-4 Switch-5

Note: A maximum of 16 redundant trunk groups per switch

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 16

Chapter 1: Course Introduction 8

Add Course Title Here

Case Study: Topology and Objectives

 Objectives:
•Implement RTG on Switch-3 to ensure only a single path is
available toward the aggregation switches
•Ensure Switch-3 forwards user traffic out ae0.0 whenever it
is operational
Switch-1 Switch-2

Aggregation
Access

Switch-3

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 17

Case Study: Configuring RTG

 You configure RTG under the [edit ethernet-
switching-options] hierarchy:
{master:0}[edit ethernet-switching-options]
user@Switch-3# set redundant-trunk-group group rtg-1 interface ae0.0 primary

{master:0}[edit ethernet-switching-options]
user@Switch-3# set redundant-trunk-group group rtg-1 interface ge-0/0/10.0

{master:0}[edit ethernet-switching-options]
user@Switch-3# show Switch-1 Switch-2
redundant-trunk-group {
group rtg-1 {
interface ge-0/0/10.0;
interface ae0.0 { Aggregation
primary;
} Access
}
}
Interface marked as primary is
always active when operational Switch-3

Note: If primary knob is omitted, highest-numbered interface initially becomes active link but does not
preempt lower-numbered interfaces functioning as the active link in failure and recovery scenarios

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 18

Chapter 1: Course Introduction 9

Add Course Title Here

Case Study: Monitoring RTG

 Use show redundant-trunk-group to monitor
RTG operations:
{master:0}
user@Switch-3> show redundant-trunk-group
Group Interface State Time of last flap Flap
name count

rtg-1 ae0.0 Up/Pri/Act Never 0

ge-0/0/10.0 Up Never 0

(Pri) = Primary interface with preemption enabled

(Act) = Active interface currently forwarding traffic

Switch-1 Switch-2

Aggregation
ae0.0 is selected as the primary Access
interface for the rtg-1 RTG group

Switch-3

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 19

What Is It?

 Two or more interconnected EX 4200 Series switches

operating as a single Juniper chassis system

Up to 10 switches can
10 RU
be interconnected Junos

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 20

Chapter 1: Course Introduction 10

Add Course Title Here

Benefits of Virtual Chassis

 Virtual Chassis benefits include:

•High availability: Redundant Routing Engines (REs)
•Simplified network design: Single network entity to manage,
configure, and monitor; potential elimination of STP; flexible
placement of member switches

LC
RE 0
LC
LC
RE 1
LC
LC
LC
LC
LC
Junos

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 21

Virtual Chassis Components

 Virtual Chassis components include:

•EX Series switches (currently only the EX 4200 Series)
• Participating switches serve as REs or line cards (LC)
•Virtual Chassis ports (can be dedicated VC ports or uplink
ports converted to extended VC ports through configuration)
• Virtual Chassis ports interconnect PFEs from one switch to another
to form a single backplane request virtual-chassis vc-port set pic-slot 1 port 0
Dedicated Virtual Chassis Gigabit Ethernet or 10 GbE extended Virtual Chassis
ports (enabled by default) ports (must be enabled through configuration)

Location 1 Location 2
LC LC
RE 0 RE 1
LC LC
LC LC

Gigabit Ethernet or 10 GbE extended Virtual Chassis ports

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 22

Chapter 1: Course Introduction 11

Add Course Title Here

Virtual Chassis Cabling Options (1 of 3)

 Dedicated Virtual Chassis daisy-chained ring method

•Longest cable spans the entire Virtual Chassis; maximum
length between end systems is 5 meters

Note: The EX 4200 Series switches come with a .5 meter cable.

You can acquire longer cables in lengths of 1, 3, and 5 meters.

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 23

Virtual Chassis Cabling Options (2 of 3)

 Dedicated Virtual Chassis braided ring method

•Maximum length between end devices in a Virtual Chassis
consisting of 10 EX Series switch is 22.5 meters

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 24

Chapter 1: Course Introduction 12

Add Course Title Here

Virtual Chassis Cabling Options (3 of 3)

 Extended Virtual Chassis ring method

•Maximum circumference of ring using is 100km; uses 1 GbE
or 10 GbE uplinks to extend distance of Virtual Chassis
Up to 100 km
Dedicated Virtual
Chassis ports GbE or 10 GbE uplink ports

Virtual Chassis Location 1 Virtual Chassis Location 2

GbE or 10 GbE uplink ports

This option is required when the circumference of a Virtual Chassis exceeds 22.5 meters.
This option is often used to interconnect wiring closets or data center racks or rows.

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 25

Recommended RE Placement (1 of 2)

 RE placement recommendations:
•Ensure spatial redundancy and avoid split VC issues and
other failure conditions by evenly spacing the master and
backup REs (by hop) and by separating REs from uplinks

RE 0 Uplink

Uplink RE 0

RE 1 RE 1

Uplink Uplink

Dedicated Virtual Chassis daisy-chained ring Dedicated Virtual Chassis braided ring

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 26

Chapter 1: Course Introduction 13

Add Course Title Here

Recommended RE Placement (2 of 2)

 RE placement recommendations (contd.):

•When implementing an extended Virtual Chassis, you should
place the master and backup REs in different locations

Dedicated Virtual
GbE or 10 GbE extended Virtual Chassis ports
Chassis ports

Location 1 Location 2

RE 0 RE 1

GbE or 10 GbE extended Virtual Chassis ports

Extended Virtual Chassis ring

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 27

Master and Backup Election

 Mastership determination:
1. Member with the highest user-configured priority
• Priority range is 1–255, factory-default value is 128
2. Member previously functioning as master prior to reboot
3. Member with the longest standing uptime
• Difference must be greater than 1 minute
4. Member with the lowest MAC address
• Used as tie breaker if all is equal through the first 3
determination steps
5. Second member in election decision tree becomes
backup switch; all other members are line cards

Note: If a master or backup fails, one of the line card switches

is elected the new backup switch using the same criteria.

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 28

Chapter 1: Course Introduction 14

Add Course Title Here

Member ID and Interface Names

 All member switches are assigned a member ID (0–9)

•Member ID is assigned manually through configuration or
dynamically from the master switch (usually member ID 0)
•Member ID is preserved through reboots
•Member ID serves as slot number for interface naming
Member ID: 0 RE 0

Member ID: 1 LC

Member ID: 2 RE 1

Member ID: 3 LC

request virtual-chassis renumber member-id 0 new-member-id 5

request system halt member 2
request session member 1

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 29

Replacing a Member Switch

 When a member switch is removed, its member ID is

not automatically released and made available nor
will the replacement switch automatically inherit the
configuration associated with the previous switch
•Recommended replacement steps:
1. Recycle the member ID of the switch being replaced so it
becomes the next-lowest available unused member ID
2. Add replacement switch which should automatically be assigned
the recycled member ID and inherit the required configuration
{master:0}
user@Switch-1> request virtual-chassis recycle member-id <member-id>

Note: You recycle member IDs on the master switch.

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 30

Chapter 1: Course Introduction 15

Add Course Title Here

Think About It!

 Given the member ID assignments, what are the

interface names for the highlighted interfaces?
•Hint: All member switches are 48 port models and all
interfaces are Gigabit Ethernet interfaces
Location #2

Member ID: 0 RE 0

Member ID: 1 LC

Member ID: 2 RE 1

Member ID: 3 LC

ge-1/0/0 and ge-1/0/1 ge-3/0/46 and ge-3/0/47

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 31

Management Connectivity (1 of 2)

 Single management interface and IP address

•Individual management Ethernet ports (me0) on member
switches are tied to a special management VLAN associated
with a Layer 3 virtual management interface (vme)
•The Virtual Chassis system is managed as a single network
element; therefore, it has only one management IP address
{master:0}[edit] RE 0
user@Switch-1# show interfaces vme
unit 0 {
LC
family inet {
address 10.210.14.148/27;
} RE 1
}
LC
{master:0}[edit]
user@Switch-1# run show interfaces terse vme
Interface Admin Link Proto Local Remote
vme up up
vme.0 up up inet 10.210.14.148/27

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 32

Chapter 1: Course Introduction 16

Add Course Title Here

Management Connectivity (2 of 2)

 Single virtual console

•Connection to a console on any member switch in a Virtual
Chassis system is redirected to the master switch by the
virtual console software running on all member switches

RE 0

LC

RE 1

LC

Console ports

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 33

Software Upgrades

 You can perform software upgrades for a single VC

member or for all members from the master switch
{master:0}
user@Switch-1> request system software add member ?
Possible completions:
<member> Install package on VC Member (0..9)

 Master switch performs a software compatibility

check for each member added to the Virtual Chassis
•If a version mismatch exists, a syslog message is generated
and the newly added switch is placed in an inactive state
•Upgrade incompatible switches from the master switch
manually or enable the automatic software upgrade option

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 34

Chapter 1: Course Introduction 17

Add Course Title Here

Topology Discovery (1 of 3)

 VC members use VCCP to create a loop-free topology

•LSA-based discovery messages are exchanged between all
PFEs and build the member switch and PFE topology maps
•Each switch runs the shortest-path first (SPF) algorithm for
each PFE which creates PFE map tables between all PFEs
•Each PFE builds source ID egress filter tables used to
prevent broadcast and multicast packets from looping
Switch-1 Switch-2 Switch-3

PFEs a b c d e f g h i

VCCP LSA-based messages

VC cables and backplane

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 35

Topology Discovery (2 of 3)

 Topology discovery example:

d e f g h i b c
a b c d
a e

Virtual Chassis Backplane

i f
h g

Physical Virtual Chassis Cabling Logical Virtual Chassis Ring Topology

Note: a, b, c, … i are PFEs

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 36

Chapter 1: Course Introduction 18

Add Course Title Here

Topology Discovery (3 of 3)

 Topology discovery example (contd.):

b c d e

b c d i h g f
a e

Virtual Chassis Backplane PFE a’s Rooted Reachability SPF Tree

i f
h g
f e d c

Logical Virtual Chassis Ring Topology

h i a b

Note: a, b, c, … i are PFEs

PFE g’s Rooted Reachability SPF Tree

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 37

Inter-Chassis Packet Flow

 Packets always take the shortest path through a VC

•Shortest path is determined by hop count and bandwidth
•Inter-chassis packet flow examples:
1. Packets going from ge-0/0/10 to ge-0/0/28 ge-0/0/10
ge-3/0/14 pass through member 0
4 because it is a shorter path
2. Packets going from ge-0/0/28 to
ge-2/0/47 pass through member 1
1 because it is a shorter path ge-2/0/47

ge-3/0/14
3

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 38

Chapter 1: Course Introduction 19

Add Course Title Here

Virtual Chassis Configuration

 You enable Virtual Chassis configuration options under

the [edit virtual-chassis] hierarchy:
{master:0}[edit virtual-chassis]
user@Switch-1# set ?
Possible completions:
+ apply-groups Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
> auto-sw-update Auto software update
> fast-failover Fast failover mechanism
id Virtual Chassis identifier, of type ISO system-id
> mac-persistence-timer How long to retain MAC address when member leaves Virtual Chassis
> member Member of Virtual Chassis configuration
no-split-detection Disable split detection. Only recommended in a 2 member setup
preprovisioned Only accept preprovisioned members
> traceoptions Global tracing options for Virtual Chassis

•To minimize traffic interruption during an RE failover scenario,

enable graceful routing-engine switchover (GRES) :
{master:0}[edit chassis]
user@Switch-1# set redundancy graceful-switchover?
Possible completions:
> graceful-switchover Enable graceful switchover on supported hardware

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 39

Dynamic Configuration Process (1 of 2)

 Dynamic configuration steps:

Master (Active RE)
1. Install desired master switch: 0 ON
• Power up desired master switch,
switch becomes master and obtains Backup (Backup RE)

member ID 0, assign mastership 1 ON

priority 255
Linecard
2. Add desired backup switch: 2
• Connect to master switch using VC
Linecard
cable, power up desired backup
switch, switch is elected as backup 3
and dynamically assigned member Linecard
ID 1, assign mastership priority 254 4

{master:0}[edit virtual-chassis]
user@Switch-1# set member <member-id> mastership-priority <priority>

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 40

Chapter 1: Course Introduction 20

Add Course Title Here

Dynamic Configuration Process (2 of 2)

 Dynamic configuration steps (contd.):

Master (Active RE)
3. Add line card switch: 0 ON
• Connect to switch above with VCB
cable, power up third switch—switch Backup (Backup RE)

becomes line card and is dynamically 1 ON

assigned member ID 2, assign

Linecard
desired mastership priority
2 ON
4. Repeat Step 3 to add subsequent
line card switches: Linecard
3 ON
• Last line card switch completes loop
by connecting with master Linecard
4 ON

{master:0}[edit virtual-chassis]
user@Switch-1# set member <member-id> mastership-priority <priority>

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 41

Preprovisioned Configuration Example

{master:0}[edit virtual-chassis]
user@Switch-1# show
Note when preprovisioned option is used, you do not specify a
preprovisioned;
member 0 { mastership priority but rather only assign the role to a given device.
role routing-engine;
serial-number BM0208105168;
}
member 1 {
role line-card;
serial-number BM0208124111;
}
member 2 { Member ID: 0 RE 0
role routing-engine;
serial-number BM0208124231; Member ID: 1 LC
} RE 1
Member ID: 2
member 3 {
role line-card; Member ID: 3 LC
serial-number BM0208124333;
}

Note: You should power on the switch designated as RE0 first, create and activate
the desired preprovisioned configuration, and then add the remaining switches.

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 42

Chapter 1: Course Introduction 21

Add Course Title Here

Monitoring Virtual Chassis Operations

 Use the show virtual-chassis commands to
monitor Virtual Chassis operations:
{master:0}
user@Switch-1> show virtual-chassis ?
Possible completions:
<[Enter]> Execute this command
active-topology Virtual Chassis active topology
device-topology PFE device topology
fast-failover Fast failover status
login
protocol Show Virtual Chassis protocol information
status Virtual Chassis information
vc-path Show virtual-chassis packet path
vc-port Virtual Chassis port information
| Pipe through a command

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 43

Verifying VC Port State

 Use show virtual-chassis vc-port to view
VC port state and details:
{master:0}
user@Switch-1> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
vcp-0 Dedicated 2 Up 32000 1 vcp-0
vcp-1 Dedicated 1 Up 32000 1 vcp-1

fpc1:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
vcp-0 Dedicated 2 Up 32000 0 vcp-0
vcp-1 Dedicated 1 Up 32000 0 vcp-1

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 44

Chapter 1: Course Introduction 22

Add Course Title Here

Enabling and Disabling VC Ports

 Built-in VC ports (vcp-0/vcp-1) are enabled by default
•You can disable or re-enable VC ports in operational mode:
{master:0}
user@Switch-1> request virtual-chassis vc-port set interface vcp-0 disable

{master:0}
user@Switch-1> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
vcp-0 Dedicated 2 Disabled 32000
vcp-1 Dedicated 1 Down 32000

{master:0}
user@Switch-1> request virtual-chassis vc-port set interface vcp-0

{master:0}
user@Switch-1> show virtual-chassis vc-port
fpc0:
--------------------------------------------------------------------------
Interface Type Trunk Status Speed Neighbor
or ID (mbps) ID Interface
PIC / Port
vcp-0 Dedicated 2 Down 32000
vcp-1 Dedicated 1 Down 32000

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 45

Verifying Status Information

 Use show virtual-chassis status to view
Virtual Chassis status information:
{master:0}
user@Switch-1> show configuration virtual-chassis
preprovisioned;
member 0 {
role routing-engine;
serial-number BM0208105168;
Member ID: 0 RE 0
}
member 1 { Member ID: 1 LC
role line-card;
serial-number BM0208124231;
}

{master:0}
user@Switch-1> show virtual-chassis status

Preprovisioned Virtual Chassis

Virtual Chassis ID: 8d5c.a77f.8de8
Mastership Neighbor List
Member ID Status Serial No Model priority Role ID Interface
0 (FPC 0) Prsnt BM0208105168 ex4200-24t 129 Master* 1 vcp-0
1 vcp-1
1 (FPC 1) Prsnt BM0208124231 ex4200-24t 0 Linecard 0 vcp-0
0 vcp-1

© 2010 Juniper Networks, Inc. All rights reserved. www.juniper.net | 46

Chapter 1: Course Introduction 23

Add Course Title Here

Chapter 1: Course Introduction 24