The sysedge.cf file located in the SystemEDGE\data\port<n> directory contains definitions for SNMPv1 trap communities, which tell SystemEDGE where to send SNMPv1 trap messages. You can configure trap destinations and SNMPv1 communities during SystemEDGE installation or by editing the sysedge.cf file. You can configure the agent to send traps to any number of management systems.
Important! Before you edit the sysedge.cf file on the monitored server, verify that SystemEDGE runs in unmanaged mode, that is, the server is not registered in Policy Configuration. If SystemEDGE runs in managed mode, Policy Configuration in CA Server Automation can overwrite your changes.
To configure SNMPv1 traps by editing sysedge.cf
The trap destination section contains a brief description of trap destinations and communities.
trap_community community-name [IP-address | hostname] [port-number]
Specifies the SNMP community; for example, public or admin.
(Optional) Specifies the IP address of the target system.
Default: 127.0.0.1
(Optional) Specifies the name of the target system.
Default: localhost
(Optional) Specifies a port to send the trap to.
Default: 162
net stop sysedge net start sysedge
/etc/init.d/sysedge restart (Linux, Solaris) /etc/init.d/sysedge restart (HP-UX) /etc/rc.d/sysedge restart (AIX)
Example
Add the following lines to sysedge.cf to send traps with a community-name of mycommunity to two systems. The first system has the IP address 192.168.5.26. The second system is the host atlanta-noc and listens on port number 1692.
trap_community mycommunity 192.168.5.26 trap_community mycommunity atlanta-noc 1692
Note: sysedge.cf only defines SNMPv1 trap communities. For information about configuring SNMPv2c or SNMPv3 traps, see the SystemEDGE User Guide installed in the SE_Install_Dir\doc directory (Windows) or in the /opt/EMPsysedge/doc directory (UNIX, Linux).
Copyright © 2013 CA. All rights reserved. |
|