Performing a Diagnostic Reboot (CLI)
Properties:
label = CPU 0
present = true
faulted = false
manufacturer = AMD
model = Quad-Core AMD Opteron(tm) Processor 8356
part = 1002
revision = 03
cores = 4
speed = 2.14G
Performing a Diagnostic Reboot (CLI)
Caution - Only issue the diagnostic reboot command as instructed by Oracle Service personnel.
A diagnostic reboot gathers diagnostic information before power cycling the appliance. This
operation could take a long time to complete and could cause adverse results if not performed
properly. Do not reboot when system-affecting operations are occurring, such as upgrading
firmware, executing commands, and configuring or unconfiguring storage.
To perform a diagnostic reboot, use the following CLI command:
hostname:maintenance system> diagreboot
Configuring the Management Port
All standalone controllers should have at least one NIC port configured as a management
interface. Select the Allow Admin option in the BUI to enable BUI connections on port 215 and
CLI connections on ssh port 22.
All cluster installations should have at least one NIC port on each controller configured as a
management interface as described above. In addition, the NIC instance number must be unique
on each controller. For example, nodeA uses igb0 and nodeB uses igb1, so that neither may be
used as a cluster data interface. In addition, these interfaces must be locked to the controller
using the Configuration > Cluster option in the BUI. In some cases, this may require installation
of an additional network interface card on each controller in a cluster configuration.
If access to the appliance data interfaces is impossible for any reason, the management network
interface will maintain BUI and CLI access. During a cluster takeover, interfaces are taken
30 Oracle ZFS Storage Appliance Customer Service Manual • July 2016
To Next Page
Loading...
Need help?
General