Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Logging of state changes

&pagelevel(4)&pagelevel

The monitoring functions of SHC-OSD show:

  • State changes in the configuration of the storage system

  • Status of the units

  • Status of remote copy mode

  • Status of local replications

  • Status of Thin provisioning and Automated Storage Tiering

  • Status of Storage Clusters

When state changes are detected, a console message is output with routing code D. The message describes the detected state changes. State changes involving changes to host access to the storage system or the availability of the remote link between two storage systems are output as queries or a message (settable, see "Logging of state changes") on the console, also using routing code D.

The monitoring function in SHC-OSD is called at intervals and implicitly for each command call of the SHC-OSD subsystem.

Logging of device-specific changes is dependent on subsystem-global operand SELECT-DEVICES of /MODIFY-SHC-PROCESSING. You can display the setting using /SHOW-SHC-PROCESSING:

*ALL

Changes are displayed for all generated and non-generated devices.

*ATTACHED

Changes are displayed only for the devices currently attached.

If only the state changes of the attached BS2000 devices are to be logged, only SELECT-DEVICES=*ATTACHED need be specified as this has a direct influence on the amount of configuration data required. In order to monitor the state changes, SHC-OSD periodically updates (default value: every 10 min.) the configuration data of the storage systems managed. In the event of large configurations, this can result in losses in performance and increased CPU requirements for the SHC user task.

Logging of state changes is dependent on the subsystem-global operand LOG-CHANGES in /MODIFY-SHC-PROCESSING. You can display the setting using /SHOW-SHC-PROCESSING:

*ALL-EVENTS

All state changes are logged.

*MAJOR-EVENTS-ONLY

Global state changes are logged. In addition, state changes of the replication functions are logged.

Whether important state changes are logged as a query (operator order) or a message depends on the subsystem-global operand OPERATOR-ORDERS in /MODIFY-SHC-PROCESSING. You can display the setting using /SHOW-SHC-PROCESSING:

*YES

Important state changes are logged as a query (operator order).

*NO

Important state changes are not logged as a query (operator order) but as a simple message.

The tables below provide an overview of the monitored and logged state changes for ETERNUS DX/AF storage systems:

Message no.

Output for
*MAJOR-
EVENTS-ONLY

Output for
*ALL-EVENTS

Output as a
question (if
selected)

NDE0008 

x

x

x

NDE0019

x

x

x

NDE0051

x

x

-

NDE0053

x

x

-

NDE0055

x

x

x

NDE0057 - 59

x

x

x

NDE0070

x

x

x

NDE0073 - 74

x

x

x

NDE0077 - 78

x

x

x

NDE0080 - 81

x

x

x

NDE0083

x

x

x

NDE0087 - 88

x

x

x

Changes to the storage system

Message no.

Output for
*MAJOR-
EVENTS-ONLY

Output for
*ALL-EVENTS

Output as a
question
(if selected)

NDE0001

-

x

-

NDE0020

x

x

-

NDE0024xx-

NDE0025 - 27

x

x

-

NDE0032

x

x

-

NDE0050

x

x

-

NDE0060

x

x

-

NDE0061

x

x

-

Changes to the device state


Message no.

Output for
*MAJOR-
EVENTS-ONLY

Output for
*ALL-EVENTS

Output as a
question
(if selected)

NDE0100

x

x

-

Changes to the operating mode