Juniper JUNOS OS 10.3 - SOFTWARE, Manual

Page: 1117 / 3946

•
Monitoring Virtual Chassis Configuration Status and Statistics on page 1041
•
Replacing a Member Switch of a Virtual Chassis Configuration (CLI Procedure) on
page 1042
•
Reverting to the Default Factory Configuration for the EX Series Switch on page 427
Configuring Mastership of the Virtual Chassis (CLI Procedure)
You can designate the role (master, backup, or linecard) that a member switch performs
within a Virtual Chassis configuration whether or not you are using a preprovisioned
configuration.
NOTE: A multimember Virtual Chassis configuration has two Routing Engines,
one in the master and the other in the backup. Therefore, we recommend
that you always use commit synchronize rather than simply commit to save
configuration changes made for a Virtual Chassis. This ensures that the
configuration changes are saved in both Routing Engines.
This topic describes:
•
Configuring Mastership Using a Preprovisioned Configuration File on page 1021
• Configuring Mastership Using a Configuration File That Is Not Preprovisioned on page 1022
Configuring Mastership Using a Preprovisioned Configuration File
To configure mastership using a preprovisioned configuration:
1.
Note the serial numbers of the switches that you want to function in the master role
and backup role.
2.
Power on only the switch (SWA-0) that you want to function in the master role.
3.
Edit the configuration to specify the preprovisioned configuration mode:
[edit virtual-chassis]
user@SWA-0#
set preprovisioned
4.
List the serial numbers of the member switches that you want to function as master
and backup, specifying their role as
routing-engine
:
[edit]
user@SWA-0# set virtual-chassis member 0 serial-number abc123 role routing-engine
user@SWA-0#
set virtual-chassis member 2 serial-number def456 role routing-engine
1021 Copyright © 2010, Juniper Networks, Inc.
Chapter 45: Configuring Virtual Chassis