McDATA 316095-B21 - StorageWorks Edge Switch 2/24 Manual page 121

McDATA SNMP Support
2
The value assigned to a given connectivity unit SHOULD be
persistent across agent and unit resets. It SHOULD be the same as
fcConnUnitGlobalId if fcConnUnitGlobalId is known and stable.
FcConnUnitGlobalId
FcGlobalId
Type
Switch's WWN.
Product Mapping
R
Access
An optional global-scope identifier for this connectivity unit. It MUST
Description
be a WWN for this connectivity unit or 16 octets of value zero.
WWN formats requiring fewer than 16 octets MUST be extended to
16 octets with trailing zero octets. If a WWN is used for
fcConnUnitId, the same WWN MUST be used for
fcConnUnitGlobalId.
When a non-zero value is provided, 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.htm
l
If one or more WWNs are associated with the connectivity unit via
other management methods, one of them SHOULD be used for
fcConnUnitGlobalId. If there is not a WWN assigned specifically to
the connectivity unit, there is some merit, though not a requirement,
to using a WWN assigned to (one of) its permanently attached
FC/LAN interface(s). This can not 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 will all be distinct
connectivity units, so the host and agent can not use the WWN of the
Fibre Alliance MIB
2-99