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 > Use policies and set alerts in SRM Profiler

Use policies and set alerts in SRM Profiler

Table of contents
No headers

Updated: June 16, 2017

The SRM Profiler server has the capability of configuring multiple agents at once using policies. Policies consists of Rules that contain configuration parameters for the devices.

Policies are intended for advanced users. Typically the default policies do not need to be changed. You can make changes by clicking on the pencil icon.

An agent can belong to only one policy. If you move an agent from one policy to another, all settings (even ones set specifically for that agent) are overwritten to the values of the policy.

Protection: You can protect an agent from being updated by the policy setup push to preserve special setups on a specific agent.

For example: On a critical server you might want the performance interval to be 1 minute, but on other servers you want the interval to be 5 minutes. To accomplish this configuration, you would define the policy setup performance frequency at 5 minutes and then use the Device Config icon to configure the critical server to 1 minute. The configuration for the one agent is automatically "protected" and is unaffected by changes to the policy. This setting is only overwritten in two cases:

  • If you select the Override Protection box when you configure a policy.
  • If you move the agent from one policy to another.

Override Protection: You can also override protection. When choosing the agents to push parameter(s) to you can choose to override any protection on the agent.

This override is for all parameters you select on a push, not parameter by parameter (unless you push them one at a time). So for the above example, if you want to change a parameter (for example: Disk Usage threshold) on the protected agent, you could do so by selecting Yes for the Override Protection on the Push screen.

Self-Configure: When a new agent registers it automatically adds itself to the configuration push list (for all parameters). This function allows you to quickly set up all your agents during installation. As soon as the SRM Profiler server is running you should configure Policy Setup parameters so any agents that self-register subsequently will have the configuration you want.

Monitoring: You can also monitor the push list to see the progress of your configuration. From the push report, you can see pending pushes, as well as failures.

Notification of Failures: If the server cannot push a configuration to a server, it will try once an hour for twenty-four hours, and then abort the push. When it aborts, it also sends a trap to the Event Receiver, which can then notify you of the failure.

Additional information about policies is available at the following links:

 
Last modified
11:16, 26 Jun 2017

Tags

Classifications

Public