HP StorageWorks 2/140 FW 08.01.00 McDATA E/OS SNMP Support Manual (620-000131- - Page 288

FC Management MIB B 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. For an entry to be considered to be valid, both the X (local) and the Y (remote) need to have one valid value. 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 via GetNexts. The value of the indexes are not required to be contiguous. Each entry created in this table will be 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. connUnitLinkTable Syntax Access Status Description Sequence SEQUENCE OF ConnUnitLinkEntry not-accessible mandatory A list of links know to this agent from this connectivity unit to other connectivity units. ::= { connSet 12 } connUnitLinkEntry Syntax Access Status ConnUnitLinkEntry not-accessible mandatory B-40 E/OS SNMP Support Manual