user@device# delete member member-id
where member-id is the member ID of the device that is removed in this procedure.
Add the new device to the VCF configuration:
[edit virtual-chassis]
user@device# set member member-id serial-number serial-number role [line-card | routing-engine]
For instance, to configure a device with the serial number OU81234567890 into the Routine Engine
role as member 3:
[edit virtual-chassis]
user@device# set member 3 serial-number OU81234567890 role routing-engine
(For spine devices only) The set virtual-chassis member member-id fabric-tree-root configuration
statement specifies that only certain devices will be root nodes in the multicast distribution trees (MDTs)
created for directing traffic within the VCF. This configuration item preempts the default VCF behavior
to create one MDT for every device in the VCF with that device as a root node. (See Understanding
Traffic Flow Through a Virtual Chassis Fabric and fabric-tree-root for more information about this option.)
If your VCF uses this option to configure the spine devices as fabric tree roots (which is the
recommended usage), then configure the new spine device as a fabric tree root as well:
[edit virtual-chassis]
user@device# set member member-id fabric-tree-root
For instance, to configure the spine device configured as member 3 as a fabric tree root node:
[edit virtual-chassis]
user@device# set member 3 fabric-tree-root
4. Commit the VCF configuration.
[edit]
user@device# commit
5. Log in to the device that is going to be added to the VCF.
6. Configure the device into fabric mode. If needed, also configure the device into mixed mode. Reboot
the device to complete this configuration step.
If you are configuring a non-mixed VCF:
user@device> request virtual-chassis mode fabric local reboot
If you are configuring a mixed-mode VCF:
400
To Next Page
Loading...
Need help?
General
