Un-registers a DR2000v based on the specified service tag.
virtual_machine --delete --service_tag DR4xVM1-09
Please enter the administrator password:
WARNING: This command will delete the DR2000v registration!
Do you want to continue? (yes/no) [n]? yes
DR2000v(DR4xVM1-09) deleted successfully.
Maintaining the DR Series System
This topic introduces the CLI commands that are useful for collecting diagnostics information, and managing the filesystem and performing system maintenance-related tasks. These CLI commands are grouped into two categories:
- The Diagnostics command and its options are used to collect DR Series system log file information. For more information, see Diagnostics.
- The Maintenance command and its options are used to perform filesystem and system maintenance. For more information, see Maintenance.
The DR Series system CLI diagnostics command lets you display, collect, and manage the diagnostic log file information for your system, which provides these benefits:
- Captures a snapshot of the current state of DR Series system operations.
- Assists Technical Support personnel to understand the sequence of DR Series system operations.
- Records DR Series system operations in the event that Technical Support needs to provide technical assistance.
The diagnostics command works by collecting all system-related information that assists in understanding system operations when diagnosing a problem or error condition in the DR Series system.
The diagnostics service runs during system startup, and listens for incoming requests sent to the DR Series system. There are two modes in which the diagnostics collection process is started:
- Admin-Generated Mode: when a DR Series system CLI or GUI request is made by the administrator (and the default reason is listed as admin-generated).
- Auto-Generated Mode: when a process or service failure is reported, the DR Series system starts collecting a wide variety of system-related information. After a successful completion of the auto-generated collection, the DR Series system also generates a system event.
NOTE: Use the alerts --show --events or the alerts --show --alerts command to display or check the current events or alerts.
The Diagnostics service stores all log information in a primary log directory, and the DR Series system also maintains a backup copy of each log in a separate, secondary log directory. After each new diagnostics log is collected, the Diagnostics process computes the sizes of each of these two log location directories.
Whenever a log directory exceeds its maximum storage capacity, the oldest logs are deleted to free up space for the current logs that the DR Series system generates.
NOTE: Diagnostics that you run from the GUI will run the largest bundle collection routine (the equivalent of running diagnostics --collect --all from the CLI). If you want to reduce the bundle collection time and file size for individual files and small bundle collection, see the options in the topics that follow.
This topic introduces the diagnostics command usage:
- diagnostics --show
- diagnostics --collect [options]
- diagnostics --delete [options]
- diagnostics --copy [options]
- diagnostics --start-service
- diagnostics --help
NOTE: If you specify a command without supplying the expected value or option, you will be prompted to provide the correct value or option.