An optional global-scope identifier for this connectivity
unit. It MUST 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.html
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.
Parsed from file fcmgmt_efcm.mib.txt
Company: emc
Module: mcdata_31
fcConnUnitGlobalId OBJECT-TYPE SYNTAX FcGlobalId MAX-ACCESS read-only STATUS current DESCRIPTION "An optional global-scope identifier for this connectivity unit. It MUST 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.html 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." ::= { fcConnUnitEntry 2 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.8888.1.1.3.1.1 | fcConnUnitId | 0 | 0 | The unique identification for this connectivity unit among those within this proxy domain. The value MUST be unique within the pr… |
| 1.3.6.1.2.1.8888.1.1.3.1.3 | fcConnUnitType | 0 | 0 | The type of this connectivity unit. |
| 1.3.6.1.2.1.8888.1.1.3.1.4 | fcConnUnitNumPorts | 0 | 0 | The number of physical ports in the connectivity unit (internal/embedded, external). |
| 1.3.6.1.2.1.8888.1.1.3.1.5 | fcConnUnitNumLinks, fcConnUnitState | 0 | 0 | This object reports the overall state of the connectivity unit. The meaning of all values is essentially self-explanatory. Any … |
| 1.3.6.1.2.1.8888.1.1.3.1.6 | fcConnUnitStatus | 0 | 0 | This object reports the overall status of the connectivity unit. The warning (4) value means that the connectivity unit needs at… |
| 1.3.6.1.2.1.8888.1.1.3.1.7 | fcConnUnitProduct | 0 | 0 | The connectivity unit vendor's product model name. |
| 1.3.6.1.2.1.8888.1.1.3.1.8 | fcConnUnitSerialNo | 0 | 0 | The serial number identification for this connectivity unit. |
| 1.3.6.1.2.1.8888.1.1.3.1.9 | fcConnUnitUpTime | 0 | 0 | The number of centiseconds since the last unit initialization. |
| 1.3.6.1.2.1.8888.1.1.3.1.10 | fcConnUnitUrl | 0 | 0 | URL to launch a management application, if applicable. Otherwise empty string. In a standalone unit, this would be the same as th… |
| 1.3.6.1.2.1.8888.1.1.3.1.11 | fcConnUnitDomainId | 0 | 0 | 24 bit Fibre Channel address ID of this connectivity unit. Following the fibre channel standard, the right-most bit of the right-… |
| 1.3.6.1.2.1.8888.1.1.3.1.12 | fcConnUnitProxyMaster | 0 | 0 | A value of 'yes' means this is the proxy master unit for a set of managed units. For example, this could be the only unit with a … |
| 1.3.6.1.2.1.8888.1.1.3.1.13 | fcConnUnitPrincipal | 0 | 0 | Whether this connectivity unit is the principal unit within the group of fabric elements. If this value is not applicable, return… |
| 1.3.6.1.2.1.8888.1.1.3.1.14 | fcConnUnitNumSensors | 0 | 0 | Number of sensors in the fcConnUnitSensorTable. |
| 1.3.6.1.2.1.8888.1.1.3.1.15 | fcConnUnitNumRevs | 0 | 0 | The number of revisions in the fcConnUnitRevsTable. |
| 1.3.6.1.2.1.8888.1.1.3.1.16 | fcConnUnitModuleId | 0 | 0 | This is a unique id, persistent between boots, that can be used to group a set of connectivity units together into a module. The … |
| 1.3.6.1.2.1.8888.1.1.3.1.17 | fcConnUnitName | 0 | 0 | A name for this connectivity unit. This object value should be persistent between boots. |
| 1.3.6.1.2.1.8888.1.1.3.1.18 | fcConnUnitInfo | 0 | 0 | Information about this connectivity unit. This object value should be persistent between boots. |
| 1.3.6.1.2.1.8888.1.1.3.1.19 | fcConnUnitControl | 0 | 0 | This object is used to control the addressed connectivity unit. NOTE: 'ColdStart' and 'WarmStart' are as defined in mib-2 and are … |
| 1.3.6.1.2.1.8888.1.1.3.1.20 | fcConnUnitContact | 0 | 0 | Contact information for this connectivity unit. The contact information is intended to facilitate contacting someone in case of p… |
| 1.3.6.1.2.1.8888.1.1.3.1.21 | fcConnUnitLocation | 0 | 0 | Location information for this connectivity unit. |
| 1.3.6.1.2.1.8888.1.1.3.1.22 | fcConnUnitEventFilter | 0 | 0 | This value defines the event severity that will be logged by this connectivity unit. All events of severity less than or equal to… |
| 1.3.6.1.2.1.8888.1.1.3.1.23 | fcConnUnitNumEvents | 0 | 0 | Number of events currently in the fcConnUnitEventTable. |
| 1.3.6.1.2.1.8888.1.1.3.1.24 | fcConnUnitMaxEvents | 0 | 0 | Max number of events that can be recorded at any one time in the fcConnUnitEventTable. |
| 1.3.6.1.2.1.8888.1.1.3.1.25 | fcConnUnitEventCurrID | 0 | 0 | The last used event ID (fcConnUnitEventId) recorded in the fcConnUnitEventTable. When no events are presently recorded in the fc… |
| 1.3.6.1.2.1.8888.1.1.3.1.27 | fcConnUnitFabricID | 0 | 0 | A globally unique value to identify the fabric that this ConnUnit belongs to, otherwise empty string. This would typically be equ… |