A trap message processed for discovery purposes conveys one of the following conditions for a device in the managed network:

  • A device, not yet in the modeled topology, was started.

  • A device, already in the modeled topology, was equipped with an additional field-replaceable unit (FRU) or had an FRU removed; for example, a Card was inserted into the device.

  • A device, already in the modeled topology, had a TCP connection closed by a remote application; for example, a Telnet session to the device was terminated.

    SNMP traps processed by IP Availability Managerand IP Performance Managerfor discoverylists the SNMP traps that IP Availability Managerprocesses for discovery purposes.

Table 1. SNMP traps processed by IP Availability Managerand IP Performance Managerfor discovery

Trap type

Trap name

MIB module

Generic traps

coldStart

Standard SNMP (RFC 1215 MIB)

warmStart

Enterprise-specific traps for 3Com Corporation

a3ComSysModuleCardInsertEvent

CB9000-MIB

Enterprise-specific traps for Cisco

cefcFRUInserted

CISCO-ENTITY-FRU-CONTROL-MIB

cefcFRURemoved

tcpConnectionClose

CISCO-GENERAL-TRAPS
Note:

IP Availability Managerand IP Performance Managerprocesses this trap, but takes no action.

IP Availability Managerand IP Performance Managerplaces the associated device for this trap on the Pending Devices list.

As indicated in the table, only for a trap message by indicating the insertion or removal of a component does IP Availability Managerplace the associated device, (which is already in the modeled topology) on the Pending Devices list. During the next pending discovery, IP Availability Managerwill send SNMP polls to the device to rediscover the device and its components.