Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Storage Manager (STM) > SRM Profiler Administrator Guide > Common tasks with SRM Profiler > Set up an alert for disk failure on a SAN > Create a policy for the disk failure rule

Create a policy for the disk failure rule

Table of contents
No headers

Updated: June 16, 2017

  1. Click Settings > Policies > Add New Policy.
  2. For Policy Class, select SMI-S.
  3. For "Base Policy on," select Default SMI-S Policy.
  4. For Name, give the policy a unique name.
  5. Click Save.
  6. For Edit Policy, click Rules. On the next screen select the new Disk Failure rule and place it under Selected Rules.
  7. Click Save.
  8. You should now be back to the Edit Policy page. Select Devices.
  9. For Choose Devices - <policy name>, look under Available Devices, select all of the SAN devices you wish to be notified when a disk failure occurs and place them under Selected Devices by clicking the down arrow.
  10. Click Save.
  11. You should be back to the Edit Policy page. Click SMI-S Configuration.
  12. Verify the settings for SMI-S Configuration. If you select the Override Agent Values option, this pushes the changes to all SRM Profiler Proxy agents. If you choose not to select this option, any new proxy agents assigned to SRM Profiler are updated leaving the agents there prior to the policy creation unchanged.
  13. Click Save.
  14. You should be back to the Edit Policy page. Click Push. This will push the policy to the relevant agents.
  15. Next you can verify the progress of the configuration push by clicking the Push List Report link in the top right corner. This will show No Data if the push has worked for the resource. You can also verify if any trap events are being received (assuming the thresholds have been meet) by going to the web console > Monitors > Event Monitor.

These events are sent to the server from the SRM Profiler agents when a threshold is met. They can be edited to change any details of the trap going forward. For example, if you're seeing an event as Critical, you can edit this to reduce its priority.



Last modified
15:30, 3 Jul 2017