disable disk

[sys-sbd]

Hello,
Is it possible to disable Event Monitor Notification for just one disk , without stopping Event Monitoring Service Event Notification.
Thanks by advance

[Jean-Louis Phelix]

Hi

Try to apply this procedure ...

Regards.

The startmon_client program reads the file:

/var/stm/data/tools/monitor/disabled_instances

The above file is read before the *.sapcfg file is read, and so there is no startup of the monitor for the specific instance listed in the disabled_instances file.

The disabled_instances file is a text file with each fully qualified instance listed, one instance per line. In addition, wildcards can be used in the instance names to specify more than more instance. For example: /storage/events/disks/default/* could be used to specify all the instances associated with the default disk resource names.

For those instances listed in the disabled_instances file, no monitoring requests will show up in the list displayed by the monconfig "C)heck monitoring" command.

NOTE: This does not mean that the monitor will stop polling the device. It just means that any events will not be forwarded to the log files, based on information in the *.sapcfg files.

In order to use the disabled_instances file, the user must perform the following:

1. Run monconfig K)ill monitoring.

2. With editor of your choice, Add/delete/modify instances at
/var/stm/data/tools/monitor/disabled_instances.

3. Run monconfig; select the "E)nable Monitoring" command.

4. Wait for monitoring to be re-enabled.

5. Do a C)heck monitors.

The resource class that was disabled should show up in the list with no description of what to do with events. (ie. There are no monitoring requests.)

NOTE: The PSM (Peripheral Status Monitor) associated with the event monitor cannot be disabled via this technique. This ONLY disables the event monitor.

[Jean-Louis Phelix]

Hi

Try to apply this procedure ...

Regards.

The startmon_client program reads the file:

/var/stm/data/tools/monitor/disabled_instances

The above file is read before the *.sapcfg file is read, and so there is no startup of the monitor for the specific instance listed in the disabled_instances file.

The disabled_instances file is a text file with each fully qualified instance listed, one instance per line. In addition, wildcards can be used in the instance names to specify more than more instance. For example: /storage/events/disks/default/* could be used to specify all the instances associated with the default disk resource names.

For those instances listed in the disabled_instances file, no monitoring requests will show up in the list displayed by the monconfig "C)heck monitoring" command.

NOTE: This does not mean that the monitor will stop polling the device. It just means that any events will not be forwarded to the log files, based on information in the *.sapcfg files.

In order to use the disabled_instances file, the user must perform the following:

1. Run monconfig K)ill monitoring.

2. With editor of your choice, Add/delete/modify instances at
/var/stm/data/tools/monitor/disabled_instances.

3. Run monconfig; select the "E)nable Monitoring" command.

4. Wait for monitoring to be re-enabled.

5. Do a C)heck monitors.

The resource class that was disabled should show up in the list with no description of what to do with events. (ie. There are no monitoring requests.)

NOTE: The PSM (Peripheral Status Monitor) associated with the event monitor cannot be disabled via this technique. This ONLY disables the event monitor.