Configuring Support Ticket options
This task may only be carried out by an Admin user from the GUI. There is no CLI equivalent.
Select
Device Configuration — Support Ticket
from the navigation panel and click
Modify
.
Table 42
Description
Name
Shows whether data collection for a system crash is enabled or not.
Automatic data collection
enabled
This is the retention policy. The number denotes the number of previously collected tar
files to be retained in each node. The HP B6000 Series Backup System allocates a 45
Number of data sets to be
retained
GB repository (/jail on the local file system) for support tickets and software packages.
A default of 30 tickets is far too many for normal use, and this should be set to meet your
requirements.If this number is exceeded, an automatic purge/overwrite occurs with the
oldest being overwritten.
After each data collection, a zip file containing specified B6000 and system command
outputs representing the cluster configuration may be sent by email. This can be enabled
Sending cluster configuration
by email enabled
or disabled. If enabled, you must set the appropriate parameters. (Note:this can be a
large package of information.)
SMTP server to send the cluster configuration information
SMTP server
Email ID from which the cluster configuration email will be sent
From
Email ID to which cluster configuration will be sent
To
Data collection
Select
Device Configuration — Support Ticket — Data Collection
option from the Navigator tree.
This page provides a log of data collections that have been generated. All users can collect and
download a log from this page. Admin users may also delete a log from this page.
IMPORTANT:
When you create a support ticket for the HP B6000 Backup System, it is saved
locally on the node running the active management service at the time of collection. HP recommends
that you download that support ticket as soon as possible, before doing anything else to the system,
such as rebooting or changing a node to maintenance. If the active management service moves
to another node before the ticket is downloaded, it cannot be retrieved from the Web Management
Console.
130 Troubleshooting
