White Papers
Diagnostics VRTX Chassis
To virtually reseat the server, in the Reset Server section, click Virtual Reseat in the Reset drop-
down menu for the servers you want to reseat, and then click Apply Selections. This operation
causes the servers to behave as if they were removed and reinserted.
The following RACADM command can also be used to reseat servers:
racadm serveraction –m <server-n> reseat –f
where n is the server number.
Restoring VRTX Chassis Configuration
VRTX Chassis configuration can be backed up and restored in case of any issues in the chassis. To
save or restore a backup of the Chassis configuration using the CMC Web interface, select Chassis
Overview > Setup > Chassis Backup.
To save the chassis configuration, in the Save window, click Save. Override the default file path
(optional) and click OK to save the file.
The default backup file name contains the service tag of the chassis. This backup file can be used
later to restore the settings and certificates for this chassis only as the file is encrypted for use on
the chassis generating the backup. To restore the chassis configuration, in the Restore window click
Browse, specify the backup file, and then click Restore.
VRTX Chassis CMC does not reset after restoring the configuration. However, CMC services may take
some time to effectively impose any changed or new configuration. After successful completion, all
current sessions are closed.
Troubleshooting Network Time Protocol (NTP) Errors
After configuring CMC to synchronize its clock with a remote time server over the network, it may
take 2–3 minutes before a change occurs in the date and time. After this time, if there is still no
change, it may be necessary to troubleshoot an issue. CMC may not be able to synchronize its clock
for the following reasons:
Issue with the settings of NTP Server1, NTP Server2, and NTP Server3.
Invalid host name or IP address may have been entered.
Network connectivity issue that prevents CMC from communicating with any of the
configured NTP servers.
DNS problem, preventing any of the NTP server host names from being resolved.
To troubleshoot these issues, check the information in the CMC Trace Log. This log contains an error
message for NTP–related issues. If CMC is not able to synchronize with any of the configured remote
NTP servers, then CMC time is synchronized to the local system clock and the trace log contains an
entry similar to the following:
Jan 8 20:02:40 cmc ntpd[1423]: synchronized to LOCAL(0), stratum 10
You can also check the ntpd status by running the following racadm command:
racadm getractime –n