Juniper JUNOS OS 10.3 - SOFTWARE Manual page 1143

CHAPTER 47
Troubleshooting Virtual Chassis
Troubleshooting a Virtual Chassis Configuration
Clear Virtual Chassis NotPrsnt Status and Make Member ID Available for Reassignment
Problem
Solution
Load Factory Default Does Not Commit on a Multimember Virtual Chassis
Problem
Solution
Member ID Persists When a Member Switch Is Disconnected From a Virtual Chassis
Problem
Copyright © 2010, Juniper Networks, Inc.
Troubleshooting a Virtual Chassis Configuration on page 1047
Clear Virtual Chassis NotPrsnt Status and Make Member ID Available for
Reassignment on page 1047
Load Factory Default Does Not Commit on a Multimember Virtual Chassis on page 1047
Member ID Persists When a Member Switch Is Disconnected From a Virtual
Chassis on page 1047
You disconnected an EX4200 from the Virtual Chassis configuration, but the disconnected
switch's member ID is still displayed in the status output. You cannot reassign that
member ID to another switch.
When you disconnect a member of a Virtual Chassis configuration, the master retains
the member ID and member configuration in its configuration database. The
command continues to display the member ID of the disconnected
virtual-chassis status
member with a status of NotPrsnt
If want to permanently disconnect the member switch, you can free up the member ID
by using the
request virtual-chassis recycle
that member.
The load factory default command fails on a multimember Virtual Chassis configuration.
The command is not supported on a multimember Virtual Chassis
load factory default
configuration. For information on how to revert to factory default settings, see "Reverting
to the Default Factory Configuration for the EX Series Switch" on page 427.
Gigabit Ethernet interfaces retain their previous slot numbers when a member switch is
disconnected from the Virtual Chassis configuration.
.
command. This will also clear the status of
show
1047