Siemens OSM Uživatelská příručka stáhnout pdf (Strana 227)

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 automatic or manual 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 Set

Days to Persist for Diagnostic Data action. This value is displayed by the Days to Persist Collected

Diagnostic Data 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

be changed in the OSMCONF file or extended for an action currently in progress by using the

Extend Problem Incident Report Suppression Time action. Performing this action while the system

is already in the suppressed state resets the duration of the current suppression to the default time.

Synchronize iLO Clocks to NonStop Clock

Synchronizes the iLO clock on each Processor Blade (for NonStop BladeSystems) or Blade Element

(for NS-Series systems) to the NonStop system's clock. OSM does this automatically, once every

24 hours; this action allows you to synchronize the clocks immediately, as needed.

System Power Off

Puts Blade Elements, LSUs, and ServerNet enclosures into low power mode (FCDMs remain powered

on).

NOTE: To power the system back on, use the Power On System action in the OSM Low-Level

Link.

Test Incident Report Delivery Paths

This action tests the Incident Report delivery paths used for remote support of NonStop systems.

For HP Insight Remote Support Advanced, this action sends a periodic incident report to all incident

subscribers, including every member in the fault tolerant subscriber group. OSM asks whether or

not you want to delete the failed path, if one is identified by the test. An EMS event is logged

containing information on connectivity from OSM to every member in the fault tolerant subscriber

group. An Alarm is created if there is a problem.

System 227

1 2 ... 222 223 224 225 226 227 228 229 230 231 232 ... 305 306

Komentáře k této Příručce

Žádné komentáře

Siemens OSM Uživatelská příručka Strana 227

Komentáře k této Příručce

Související produkty a manuály pro Sítě Siemens OSM