HP StorageWorks 2/16V Brocade Fabric OS Documentation Addendum - Supporting Fa - Page 88

connUnitSnsTable 1.3.6.1.3.94.5.2.1

Get HP StorageWorks 2/16V - SAN Switch PDF manuals and user guides View all HP StorageWorks 2/16V manuals
Add to My Manuals
Save this manual to your list of manuals

Page 88 highlights

3 connUnitSnsTable 1.3.6.1.3.94.5.2.1 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: 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 that do not directly attach to members of its agency and its discovery algorithm gives some assurance that the links are recently valid, it might include these links. Link information entered by administrative action might be included even if not validated directly if the link has at least one endpoint in this agency, but it 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 command (ANSI document 99-422v0). This command queries 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 values 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 is defined by the size of the table. For an entry to be considered valid, both the X (local) and the Y (remote) values need to have one valid value. A Brocade Access Gateway has no ISLs (InterSwitch Links); therefore all F_Port and N_Port connections display in ag --show for online F_Ports. The following table shows the possible values for F_Ports and N_Ports on a Brocade Access Gateway: connUnitSnsTable 1.3.6.1.3.94.5.2.1 This table contains an entry for each object registered with this port in the switch. Implementation of the Connectivity Unit Service Tables group is mandatory for all systems. A Brocade Access Gateway has no name server information; therefore this table is disabled. 3-8 Fabric OS Documentation Addendum Publication Number: 53-1000429-01-HP

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
3-8
Fabric OS Documentation Addendum
Publication Number: 53-1000429-01-HP
connUnitSnsTable 1.3.6.1.3.94.5.2.1
3
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: 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 that do not directly attach to members of its agency and its
discovery algorithm gives some assurance that the links are recently valid, it might include these links.
Link information entered by administrative action might be included even if not validated directly if the
link has at least one endpoint in this agency, but it 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 command (ANSI document 99-422v0). This command queries 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 values 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 is defined by the size of the table.
For an entry to be considered valid, both the X (local) and the Y (remote) values need to have one valid
value.
A Brocade Access Gateway has no ISLs (InterSwitch Links); therefore all F_Port and N_Port
connections display in ag --show for online F_Ports. The following table shows the possible values for
F_Ports and N_Ports on a Brocade Access Gateway:
connUnitSnsTable 1.3.6.1.3.94.5.2.1
This table contains an entry for each object registered with this port in the switch.
Implementation of the Connectivity Unit Service Tables group is mandatory for all systems.
A Brocade Access Gateway has no name server information; therefore this table is disabled.