Brocade Network Advisor SMI Agent Developer’s Guide
103
53-1002169-01
Chapter
4
Indications
In this chapter
•
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
•
Alert indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
•
Life-cycle indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Introduction
The Brocade Network Advisor SMI Agent delivers events in the form of two types of indications:
alert indications
and
life-cycle indications
.
Alert indications are used to represent all fabric events. To get the alert indications, the clients
must first register with the fabric for these events.
Life-cycle indications are delivered by the classes in reaction to a change in the status of a
connection such as, when elements (for example, switch or node) leave or join the fabric.
The Configuration tool allows you to enable mutual authentication for indications. If this is enabled,
all the indications are received over the HTTPS port. By default, the HTTPS is enabled without
mutual authentication.
Alert indications
Table 14
explains the supported alert indications.
