Trouble Ticket Integration Using SNMP Traps
eG Enterprise is capable of transmitting alarms generated by the eG manager via SNMP traps to an SNMP management console such as HP OpenView, Netcool etc. In this case typically, for every alert that is generated in the eG Enterprise system, individual traps will be generated. In other words, a new SNMP trap will be sent out whenever a new problem is detected or an old problem changes (eg., a change in alarm priority, a change in alarm description, a change in the services impacted, etc.). This means that if a problem occurs across multiple descriptors of the same test, traps will be sent for each of the descriptors to the SNMP management system. Sometimes however, you may want to track an issue closely so that you can tell when it actually occurred and when it 'changed'. To ensure this, the eG Enterprise system provides you with the option to implement SNMP traps in the trouble ticketing integration module. When this is done, each trap sent by the eG manager to the third-party SNMP management console will be accompanied by a unique TTID. The SNMP console should be able to recognize the TT ID, and if a trap with the same TT ID re-appears, it should overwrite the last state it has for that TT ID. This way, the SNMP management system can differentiate between new alarms and modified alarms.
To enable integration via SNMP traps, the following steps should be followed:
- Configure at least one SNMP manager for the eG manager to integrate with. Refer to Configuring a Third-party SNMP Manager to know how to configure an SNMP manager.
- Configure the eG manager to send traps to the SNMP manager(s) as trouble tickets (i.e., with a TTID). Refer to Sending Trouble Tickets over SNMP Traps to know how to configure the eG manager so.