Chapter 10: Routine V-Switch Maintenance 191
reboots with the last good configuration, all data written on the third child
will be lost.
The suspicious database is saved and can then be exported to SANRAD technical
support for examination using the CLI command ft export problem after
initializing the V-Switch. Please see “Level 4:
Level 5:
If the V-Switch enters a reboot loop, after a given number of times, the reboot loop will
be stopped and the V-Switch will enter safe mode 5. A reboot loop is most often
caused by the connection of a problematic device to the V-Switch. In addition to
contacting Technical Support, SANRAD recommends disconnecting storage and
Ethernet connections and rebooting the V-Switch. If the V-Switch reboots without
problems, an attached device is the culprit.
Exporting a Corrupted Database,” page 191.
Level 2: Reboot with Default Factory Database
This does not clear
user login profiles.
This is the recommended option.
This clears the database of all configurations that may have been done, e.g.
IP addresses, subdisks, volumes and targets. The suspicious database is
copied to the directory corrupted database where it can then be exported
to SANRAD technical support for examination using the CLI command ft
export problem after initializing the V-Switch.
Level 3: Reboot with Default Factory System
This clears all user
login profiles. You
will have to login with
the user name
sanrad and password
sanrad.
This clears the database of all configurations executed on the V-Switch,
including user login profiles. You will have to log in with the user name
sanrad and password sanrad.
Level 4:
Level 5:
If the V-Switch enters a reboot loop, after a given number of times, the
reboot loop will be stopped and the V-Switch will enter safe mode 5. A
reboot loop is most often caused by the connection of a problematic device
to the V-Switch. In addition to contacting Technical Support, SANRAD
recommends disconnecting storage and Ethernet connections and rebooting
the V-Switch. If the V-Switch reboots without problems, an attached device
is the culprit.
