HP StorageWorks 2/16V Brocade Fabric OS MIB Reference - Supporting Fabric OS 5 - Page 224

8 connUnitId 1.3.6.1.3.94.1.6.1.1 connUnitId 1.3.6.1.3.94.1.6.1.1 The unique identification for this connectivity unit among those within this proxy domain. The value must be unique within the proxy domain because it is the index variable for connUnitTable. The value assigned to a given connectivity unit should be persistent across agent and unit resets. It should be the same as connUnitGlobalId if connUnitGlobalId is known and stable. The Brocade implementation maps the switch WWN to the top 8 octets of this variable and sets the remaining lower 8 octets to 0. To specify a particular instance of any columnar variable in the connUnitEntry (such as connUnitType), specify the instance identifier as a 16-octet value. connUnitType.10.0.0.60.69.4.11.19.0.0.0.0.0.0.0.0 where the object instance identifier consists of 16 octets, each representing the byte value from high-byte order to low-byte order of this 128-bit integer. connUnitGlobalId 1.3.6.1.3.94.1.6.1.2 An optional global-scope identifier for this connectivity unit. It must be a WWN for this connectivity unit or 16 octets of value 0. The following characteristics are required: • WWN formats requiring fewer than 16 octets must be extended to 16 octets with trailing 0 octets. • If a WWN is used for connUnitId, the same WWN must be used for connUnitGlobalId. When a non-zero value is provided, the following characteristics are strongly recommended: • It should be persistent across agent and unit resets. • It should be globally unique. • It should be one of these FC-PH/PH3 formats: - IEEE (NAA=1) - IEEE Extended (NAA=2) - IEEE Registered (NAA=5) - IEEE Registered extended (NAA=6) Use of the IEEE formats allows any IEEE-registered vendor to assure global uniqueness independently. The following are some references on IEEE WWN formats: http://standards.ieee.org/regauth/oui/tutorials/fibreformat.html http://standards.ieee.org/regauth/oui/tutorials/fibrecomp_id.html If one or more WWNs are associated with the connUnit via other management methods, one of them should be used for connUnitGlobalId. If a WWN is not assigned specifically to the connUnit, there is some merit to using a WWN assigned to (one of) its permanently attached FC/LAN interfaces. This cannot risk uniqueness, though. As a counterexample, if your agent runs in a host and the host has an HBA, it is quite possible that agent, host, and HBA are all distinct connUnits, so the host and agent cannot use the WWN of the HBA. 208 Fabric OS MIB Reference 53-1000439-01