Adding A Spine Device To An Autoprovisioned Virtual Chassis Fabric - Juniper QFX5110 Series Hardware Documentation

BEST PRACTICE:
to the spine member that is in the primary Routing Engine role first, which is the most efficient
way to synchronize the new member with the current VCF configuration and state.
Interconnecting a new member only to the backup or another spine member can cause
flooding of messages within the VCF as the primary tries to synchronize the new member
through other leaf and spine member VCP links.
After the new member is fully incorporated into the VCF, you can interconnect the remaining
redundant VCP links to the backup and other spine devices without affecting traffic within
the VCF.
No further configuration is required.

Adding a Spine Device to an Autoprovisioned Virtual Chassis Fabric

To add a spine device to an autoprovisioned VCF:
1. Log in to your VCF.
2. If you are replacing a spine device that is already part of the VCF, power off the spine device in the
VCF.
Follow the steps in "Removing a Device From a Virtual Chassis Fabric" on page 405
from the VCF.
3. Modify the configuration.
If your new spine device is replacing an existing spine, modify the configuration to remove the old
spine.
You can skip this step if you are not replacing an existing spine device.
[edit virtual-chassis]
user@device# delete member member-id
where member-id is the member ID of the spine that is removed from this procedure.
Add the spine device to the configuration:
[edit virtual-chassis]
user@device# set member member-id serial-number serial-number role [line-card | routing-engine]
For instance, to configure a spine device acting in the linecard role with the serial number
OU81234567890 as member 3:
When adding a leaf device to an existing VCF, interconnect the new device
to remove the device
397