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 > SRM Profiler settings > Trap Forwarding settings

Trap Forwarding settings

Updated: June 16, 2017

The SRM Profiler server and its agents generate traps that are sent to the SRM Profiler Trap Receiver. These traps can also be forwarded to a network operations center.

Forward traps for SRM Profiler server

To forward SRM Profiler server traps to a network operations center, you must configure the trap forwarding features of SRM Profiler. You can also set up alerts based on traps.

SRM Profiler only forwards SRM Profiler traps.

To configure Trap Forwarding, navigate to Settings > Server Setup: All >Trap Forwarding, and then configure the following fields:

Forward Traps

Enable the forwarding of traps when set to true.

Destination IP

Set the IP address of the server to which you want to forward traps.

Destination Port

Set the port of the server to which you want to forward traps.

Community String

Set the community string of the server to which you want to forward traps.

Disk Usage Warning Limit

Set the threshold for a file system, volume or drive that you want to forward as a Warning trap.

Disk Usage Critical Limit

Set the threshold for a file system, volume or drive that you want to forward as a Critical trap.

Disk Usage Error Limit

Set the threshold for a file system, volume or drive that you want to forward as an Error trap. In general, you want the Warning Limit to be less than the Critical Limit, which will be less than the Error Limit (e.g., 70 < 80 < 90).

Persist Trap

Determine if trap is persisted in database.

Forward traps for SRM Profiler agent

  1. Click Settings on the SRM Profiler web console.
  2. Click the edit icon for the Default OS Policy.
  3. Select the Communication link.
  4. Click the Add Trap Destination bar.
  5. Place the IP address of the trap server you want to forward the traps to.
  6. Configure the port and community string to your desired settings.
  7. Select Override Agent Values, and then click Save.
  8. Push your changes to the external agents by clicking the Push button.

SRM Profiler agents do not filter any traps being forwarded to a remote host and many traps are logged to the destination server. Filtering of these traps must be done by the destination. 

 

 

Last modified
11:16, 26 Jun 2017

Tags

Classifications

Public