Snmp informs, Snmp informs 4, Customizing a registered trap definition – Brocade Network Advisor SAN User Manual v12.3.0 User Manual

Page 1326

Advertising
background image

1274

Brocade Network Advisor SAN User Manual

53-1003154-01

SNMP informs

32

Customizing a registered trap definition

To modify the definitions of registered traps, complete the following steps.

1. Click the Trap Configuration tab.

2. Click the Registered button.

The Trap tree displays the MIBs that contain the registered traps.

3. Expand a MIB folder to display the traps that have been registered for that MIB.

4. Select a trap to display its current definition. You can change the severity, message, or alias of

the trap.

5. When you have finished, click OK or Apply to accept your entries.

If you modified a default trap, its status changes from Registered - Default to Registered -
Customized.

Reverting the customization of a registered trap to default

To revert to the default definitions of registered-customized traps, complete the following steps.

1. Click the Trap Configuration tab.

2. Click the Registered button.

The Trap tree displays the MIBs that contain the registered traps.

3. Expand a MIB folder to display the traps that have been registered for that MIB.

4. Select a trap to display its current definition.

5. If the trap has been customized, a button labeled Default is available. Click Default to revert

the previous changes to its default.

SNMP informs

The SNMP Informs dialog box allows you to enable or disable informs on informs-capable products.
SNMP traps are unreliable because the receiver does not send any acknowledgment when it
receives a trap. The sender cannot determine if the trap was received. However, an SNMP manager
that receives an inform request acknowledges the message with an SNMP response protocol data
unit (PDU). If the manager does not receive an inform request, it does not send a response. If the
sender (switch) never receives a response, the inform request can be sent again. For this reason,
informs are more likely to reach their intended destination.

When using informs, the engine ID must be set to correspond to the management engine IP
address to authenticate the inform request. When informs are enabled, the sender sends initial
informs request for engine ID discovery from any of its ephemeral ports (ranging from 32768 to
65535) to port 161 on the Management server. The sender receives the acknowledgement of the
informs requests on these ephemeral ports. If there is a firewall between the Management
application and the switches, the ephemeral ports must be open for SNMP informs to work.

Advertising