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

Fibre Alliance MIB
A
fcConnUnitType
fcConnUnitNumPorts
E/OS SNMP Support Manual
A-10
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
HBA.
Another example: If your hub has a built-in Ethernet port, it might be
reasonable for the hub to use its LAN address (prefixed with the
appropriate NAA) as its fcConnUnitId. But if the Ethernet were a
replaceable PCCard, the hub should have an independent ID.
Sequence
::= { fcConnUnitEntry 2 }
FcUnitType
Syntax
read-only
Max-Access
current
Status
The type of this connectivity unit.
Description
Sequence
::= { fcConnUnitEntry 3 }
Unsigned32
Syntax
IEEE Extended (NAA=2)
IEEE Registered (NAA=5).
IEEE Registered extended (NAA=6).