Changing Destination of Notifications on Windows

This section describes how to change an existing destination to a new NMS destination. To add a new destination without changing the existing destination, see the procedure Adding a New Destination for Notifications on Windows.

Before you begin

To deliver notifications to the correct destination, you must know whether your destination uses SNMPv1 or SNMPv2c. If you do not know which version you are using (v1 or v2), find out before you change the destination of the notifications. If you do not set the destination on a line of the file containing the correct version of SNMP, you will receive no notifications.

Changing Destination of Notifications on Windows

To change the destination of notifications, do the following:

1 Use a text editor to open theC:\Program Files\Cantata\SNMP\srconf\agt\snmpd.cnf file, located in the directory, snmp\srconf\agt.

2 Search for and edit the snmpTargetAddrEntry object in the snmpd.cnf file. The entry will look similar to the following:

#Entry type: snmpTargetAddrEntry

#Format: snmpTargetAddrName (text)

# snmpTargetAddrTDomain (snmpUDPDomain, snmpIPX
Domain, etc.)

# snmpTargetAddrTAddress (transport address,

i.e. 192.147.142.254:0)

# snmpTargetAddrTimeout (integer)

# snmpTargetAddrRetryCount (integer)

# snmpTargetAddrTagList (text)

# snmpTargetAddrParams (text)

# snmpTargetAddrStorageType (nonVolatile,
permanent, readOnly)

# tgtAddressMask (transport mask,
i.e. 255.255.255.255:0)

snmpTargetAddrEntry 31 snmpUDPDomain 127.0.0.1:0 100 3 localhost_v1 v1ExampleParams nonVolatile 255.255.255.255:0

snmpTargetAddrEntry 32 snmpUDPDomain 127.0.0.1:0 100 3 localhost_v2 v2cExampleParams nonVolatile 255.255.255.255:0

The first 10 lines of the entry (all lines beginning with pound (#) signs) describe the format of the snmpTargetAddrEntry fields. They are informational only.

If your destination uses SNMP v1 protocol, edit the following lines:

snmpTargetAddrEntry 31 snmpUDPDomain 127.0.0.1:0 100 3 localhost_v1 v1ExampleParams nonVolative 255.255.255.255:0

Note the destination: localhost_v1.

If your destination uses SNMP v2 protocol, edit the following lines:

snmpTargetAddrEntry 32 snmpUDPDomain 127.0.0.1:0 100 3 localhost_v2 v2cExampleParams nonVolative 255.255.255.255:0

Note the destination: localhost_v2.

Do not change all these lines, only the ones that apply to the version of the protocol you are using (v1 or v2).

3 Modify the IP address on the appropriate line to the new destination IP address. The IP address of the destination is the snmpTargetAddrTAddress field. It is the fourth field in the line. The IP address must be followed by :0. For example, an IP address might be 192.143.43.22:0.

4 If localhost_v1 or localhost_v2 are not acceptable names for the new notification destination, then see the procedure Adding a New Destination for Notifications on Windows.

5 Save the snmpd.cnf file. Make a copy of this file and store it in another directory. The SNMP Master Agent overwrites modified or added entries.

6 Stop the SNMP Master Agent by opening a Command Prompt window and typing the following:

net stop snmpdm

After stopping the SNMP Master Agent, the following messages should be displayed:

# The SNMP EMANATE Master Agent service is stopping.

# The SNMP EMANATE Master Agent service was stopped successfully.

7 Restart the SNMP Master Agent by opening a Command Prompt window and typing the following:

# net start snmpdm

After the restart, the following message should be displayed:

# The SNMP EMANATE Master Agent service was started successfully.

8 You should not need to stop and restart the LLC and traprcv. You should now see notifications at the new destination.

Outlook

Once the system is running, you can direct notifications to a corporate SNMP system such as HP OpenView or Castlerock.