Map QOS and Alarms for CDM Network Devices to the CDM robot.
Article ID: 282494
Updated On:
Products
Issue/Introduction
QOS and Alarms from Network disks discovered with the CDM probe are issued by default with mapping (dev_id and met_id) of the Network Device. This means that in the Operator Console (OC) the metrics and alarms will be listed under the specific network device.
Is there any option to Map QOS and Alarms for CDM Network Devices to the CDM robot rather than to the Network disks?
Environment
DX UIM 23.4 / 20.4.*
CDM probe 7.20 and earlier
Cause
Network disks discovered with the CDM probe are hardcoded to network devices mapping for alarms and QOS
Resolution
There is no out-of-the-box configuration to achieve this scope as Network disks discovered with the CDM probe are hardcoded to network devices mapping for alarms and QOS.
Below is an alternative approach using a simple LUA Script and pre-processing NAS rule:
Example/Workaround:
• you are monitoring disk E and disk K on robot called ,,robot01", disk E is local disk, disk K is network disk.
• Alarm for disk K will be mapped to the network server it belongs to.
If you want the disk alarm for K to belong to robot robot01, you may want to override the alarm hostname with robot01 by doing the following:
1. first create a simple LUA Script as below:
open nas go to Auto-Operator > scripts > create new:
event.hostname = "robot01"
return event
2. now create a Pre-processing rule that would match, uniquely, the alarms for disk K. (for example you could match the specific message or anything that will ensure you are matching alarms for the specific disk)
Filter type should be set to custom
then select your created custom script.
3. Like this all alarms that will match the pre-processing criteria, will be overridden with a the robot01 hostname in the alarm.
Additional Information
Enhancement Request/IDEA in the DX UIM community.
Add ability in CDM to map network device to the CDM robot rather than to the device itself.
Feedback
