HP StorageWorks 8B - FC Entry Switch Reference Manual page 135

connUnitEventDescr [connUnitEventTable]
Syntax
Display String
Access
Read-only
Status
Mandatory
Description
The description of the event.
Note:
Note:
MIB Reference Manual Version 3.0
The link table is intended to organize and communicate any information the agent has, that
might assist a management application to discover the connectivity units in the framework
and the topology of their interconnect.
That is, the goal is to assist the management application by mapping the elements of the
framework in addition to listing them.
With this goal, the agent SHOULD include as much as it possesses about any links from its
own connectivity units to others, including links among its own units.
An agent SHOULD include partial information about links if it is not able to fully define
them in accord with the following structure; however, the information MUST include either
a nonzero connUnitNodeId- or a nonzero connUnitPortWwn - for each end of the link.
If the agent is able to discover links which do not directly attach to members of its agency
and its discovery algorithm gives some assurance the links are recently valid, it MAY
include these links.
Link information entered by administrative action MAY be included even if not validated
directly if the link has at least one endpoint in this agency, but SHOULD NOT be included
otherwise.
A connectivity unit should fill the table in as best it can. One of the methods to fill this in
would be to use the RNID ELS (ANSI document 99-422v0). This allows one to query a
port for the information needed for the link table.
This table is accessed either directly if the management software has an index value or
using "GetNext". The value of the indexes are not required to be contiguous. Each entry
created in this table is assigned an index. This relationship is kept persistent until the entry
is removed from the table or the system is reset. The total number of entries are defined by
the size of the table
For an entry to be considered to be valid, both the X (local) and the Y (remote) need to have
one valid value.
Same as the string shown in the telnet command errShow.
Fibre Alliance MIB Object Types
2
2-49