Rediscover system and cluster, Reinitialize complex manager, Set data collection volume – HP Integrity NonStop J-Series User Manual
Page 237: Set days to persist for diagnostic data, Set system type, Suppress problem incident report creation, Suppress, Problem incident report creation
Rediscover System and Cluster
Causes OSM to
and
all components within the system and the ServerNet cluster
or NonStop BladeCluster.
NOTE:
This action is not available for Integrity NonStop NS1000, NS1200, NS2000 series,
NS2100, NS2200 series, NS2300, NS2400 series, NS5000, or NS3000AC servers.
Reinitialize Complex Manager
Reinitializes the Complex Manager Auxiliary Process (CMAP) for each processor in the system.
This action is intended only for Integrity NonStop NS14000 series and NS16000 series servers
running H06.12 or later; it fails harmlessly (and no CMAP events are logged) when performed on
other system types or when running pre-H06.12 SUTs.
CAUTION:
The action should be performed only in cooperation with HP Support. If used
improperly, an outage could occur. You must avoid all processor actions and cable changes while
CMAP reinitialization is in progress.
It is recommended that you open an OSM event viewer session with the following retrieval criteria
before proceeding with this action: $ZLOG, using View Options - Realtime, Filter Criteria owner
TANDEM, Subsys name(s) - CMAP. (To launch an event viewer session from the OSM Service
Connection, it may be necessary to cancel the action, open the event viewer session, then initiate
the action again.)
After clicking "Yes" to three confirmation dialog boxes and OSM reports that the action has
completed successfully, check the OSM event viewer session opened earlier to locate CMAP event
135 (CMAP started reinitialization) and a corresponding CMAP event 136 (CMAP completed
reinitialization) for each logical processor running NSK. Reinitialization for each processor is
complete when the CMAP event 136 appears. (Other CMAP events occur as the PEs (Processor
Elements) for each logical processor are rediscovered.) Once CMAP reinitialization completes
successfully for all processors, you can proceed with any necessary processor actions or cable
changes.
Set Data Collection Volume
Used to specify a volume in which
or
data collection will take place. The volume
should be something other than $SYSTEM to avoid the possibility of filling that volume with collected
data.
The
Diagnostic Data Collection Volume
attribute displays the currently specified volume. How long
the files are retained in this volume before being automatically deleted is determined by the
Days to Persist for Diagnostic Data
action. This value is displayed by the
attribute.
Set Days to Persist for Diagnostic Data
Determines how many days the collected hardware failure data is retained on the system before
being deleted. Any PAK or LOG file older than this value is deleted the next time automatic or
manual data collection is initiated.
Set System Type
Specifies whether the System is a standard "Commercial" (AC-powered) or a "Central Office"
(DC-powered) system.
Suppress Problem Incident Report Creation
This action, which can be initiated by a user or guided procedure, suppresses both dial-outs and
the creation of Problem Incident Reports for the default time of 40 minutes. The default value can
System 237