Juniper QFX3500, Hardware Documentation

Page: 426 / 669

BEST PRACTICE: When adding a leaf device to an existing VCF, interconnect the new device
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.
Adding a Spine or Leaf Device to a Nonprovisioned Virtual Chassis Fabric
CAUTION: Configure your VCF using autoprovisioning or preprovisioning unless you
have a compelling reason to use nonprovisioned configuration. You can configure all
aspects of a VCF using autoprovisioned or preprovisioned configuration.
Nonprovisioned VCF configuration is highly discouraged. Nonprovisioned VCF
configuration should only be used by VCF experts in specialized scenarios.
To add a spine or leaf device to a nonprovisioned VCF:
1. Log in to your VCF.
2. If you are replacing a device that is already part of the VCF, power off the device in the VCF. Uncable
the device once the power off is complete.
You can skip this step if you are adding a new device without replacing an existing device. You must
skip this step if there is no configuration for the device that you are removing from the VCF.
If the device is configured, delete the device from the VCF configuration:
[edit virtual-chassis]
user@device#
delete member member-id
where member-id is the member ID of the device that you are removing.
3. Log in to the device that you are going to add to the VCF.
4. Configure the device into fabric mode. If needed, also configure the device into mixed mode.
402