T11-FC-FABRIC-ADDR-MGR-MIB

T11FabricIndexA Fabric Index that is used as a unique index value to identify a particular Fabric within one (or more) physical infrastructures. In an environment that is conformant to FC-SW-3, where there is always exactly one Fabric in a single physical infrastructure, the value of this Fabric Index will always be 1. However, the current standard, FC-SW-4, defines how multiple Fabrics, each with its own management instrumentation, could operate within one (or more) physical infrastructures. When such multiple Fabrics are in use, this index value is used to uniquely identify a particular Fabric within a physical infrastructure. Note that the value of this textual convention has a range of (0..4095) so as to be consistent with FC-SW-4, which says that a 'VF_ID Bitmap' is 512 bytes long, with the high-order bit representing VF_ID zero, and the low-order bit representing 4095.Reference: Fibre Channel - Switch Fabric - 4 (FC-SW-4), ANSI INCITS 418-2006, section 6.1.27.2.4. (0..4095) · Unsigned32 · hint d

A unique index value that uniquely identifies a particular Fabric known to a particular switch. In a Fabric conformant to FC-SW-3, only a single Fabric can operate within a physical infrastructure, and thus, the value of this Fabric Index will always be 1. However, the current standard, FC-SW-4, defines how multiple Fabrics, each with its own management instrumentation, could operate within one (or more) physical infrastructures. When such multiple Fabrics are in use, this index value is used to uniquely identify a particular Fabric within a physical infrastructure.

FcDomainIdOrZeroThe Domain Id (of an FC switch), or zero if the no Domain Id has been assigned. (0..239) · Integer32

The configured Domain_ID of the particular switch on this Fabric, or zero if no Domain_ID has been configured. The meaning of this object depends on t11FamConfigDomainIdType object. If t11FamConfigDomainIdType is 'preferred', then the configured Domain_ID is called the 'preferred Domain_ID'. Valid values are between 0 and 239. In a situation where this Domain_ID cannot be assigned, any other Domain_ID will be acceptable. A value of zero means any Domain_ID. If t11FamConfigDomainIdType is 'insistent', then the configured Domain_ID is called the 'insistent Domain_ID' and valid values are between 1 and 239. In a situation where this Domain_ID cannot be assigned, no other Domain_ID is acceptable. In both of the above cases, the switch sends an RDI (Request Domain_ID) to request this Domain_ID to the Principal Switch. If no Domain_ID is able to be granted in the case of 'preferred', or if an 'insistent' Domain_ID is configured but not able to be granted, then it is an error condition. When this error occurs, the switch will continue as if it receives a SW_RJT with a reason/explanation of 'Unable to perform command request'/'Domain_ID not available'. That is, its E_Ports on that Fabric will be isolated and the administrator informed via a 't11FamDomainIdNotAssigned' notification. If t11FamConfigDomainIdType is 'static', then the configured Domain_ID is called the 'static Domain_ID' and valid values are between 1 and 239. In this situation, there is no Principal Switch in the Fabric and the Domain_ID is simply assigned by configuration, together with the Fabric_Name. A switch configured with a static Domain_ID, on receiving an EFP, BF, RCF, DIA, or RDI SW_ILS, shall reply with an SW_RJT having Reason Code Explanation 'E_Port is Isolated' and shall isolate the receiving E_Port. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause. ⓘ

INTEGER1 = preferred2 = insistent3 = static · Integer32

Type of configured Domain_ID contained in t11FamConfigDomainId. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object determines how a particular switch responds to certain error conditions. The condition that might cause these errors is the merging of two disjoint Fabrics that have overlapping Domain_ID lists. If value of this object is 'true', the switch will send an RCF (ReConfigureFabric) to rebuild the Fabric. If 'false', the switch will isolate the E_Ports on which the errors happened. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Determines how a particular switch behaves when elected as the Principal Switch. If true, the switch will only accept RDIs with a contiguous allocation; specifically, it will reject RDIs with non-contiguous Domain_IDs, and if an RDI for a contiguous Domain_ID is not able to be fulfilled, it will try to replace all the Domain_IDs in the list with contiguous Domain_IDs, and if that fails, the RDI will be rejected. If false, then the switch acts normally in granting the Domain_IDs even if they are not contiguous. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.

T11FamDomainPriorityPriority of a switch. The Principal Switch selection is influenced by the priority of the switches. Some values of importance are: 1 : The highest priority in Principal Switch selection, which is used by the administrator to establish which switch becomes the Principal Switch. 255 : Indicates that the switch is not capable of acting as a Principal Switch.Reference: Fibre Channel - Switch Fabric - 3 (FC-SW-3), ANSI INCITS 384-2004, section 6.1.5. (1..255) · Unsigned32 · hint d

The initial or configured priority of a particular switch to be used in Principal Switch selection process. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.

FcNameIdOrZeroThe World Wide Name (WWN) associated with a Fibre Channel (FC) entity. WWNs were initially defined as 64-bits in length. The latest definition (for future use) is 128-bits long. The zero-length string value is used in circumstances in which the WWN is unassigned/unknown. SIZE (0 | 8 | 16) · OCTET STRING

The WWN of the Principal Switch on this Fabric, or zero-length string if the identity of the principal switch is unknown.

FcNameIdOrZeroThe World Wide Name (WWN) associated with a Fibre Channel (FC) entity. WWNs were initially defined as 64-bits in length. The latest definition (for future use) is 128-bits long. The zero-length string value is used in circumstances in which the WWN is unassigned/unknown. SIZE (0 | 8 | 16) · OCTET STRING

The WWN of the particular switch on this Fabric.

OCTET STRING SIZE (0..256)

The list of (zero or more) Area_IDs that have been assigned by a particular switch in this Fabric, formatted as an array of octets in ascending order. Each octet represents one Area_ID. So, the list containing Area_IDs 23, 45, 235, and 56 would be formatted as the 4-octet string x'172d38eb'. A particular area's Area_ID is used as the index into the t11FamAreaTable to get the statistics on that area.

Counter32

The total number of Fibre Channel Address Identifiers granted (for local use, i.e., with a particular switch's Domain_ID) by the Fabric Address Manager on that switch. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.

Counter32

The total number of Fibre Channel Address Identifiers that have been recovered by the Fabric Address Manager on a particular switch since the switch has been initialized. A recovered Fibre Channel Address Identifier is one that is explicitly returned after previously being used. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.

Gauge32

The number of Fibre Channel Address Identifiers that are currently unassigned on this Fabric and could be available for assignment either immediately or at some later time. The sum of the instances of FreeFcIds and AssignedFcIds corresponding to a particular Fabric is the total number of Fibre Channel Address Identifiers that the local Fabric Address Management is capable of assigning on that Fabric.

Gauge32

The number of Fibre Channel Address Identifiers that are currently assigned on this Fabric. The sum of the instances of FreeFcIds and AssignedFcIds corresponding to a particular Fabric is the total number of Fibre Channel Address Identifiers that the local Fabric Address Management is capable of assigning on that Fabric.

Gauge32

The number of Fibre Channel Address Identifiers that are unassigned and currently available for immediate assignment on the Fabric, e.g., with the 'Clean Address' bit set to 1. ⓘ

T11FamDomainPriorityPriority of a switch. The Principal Switch selection is influenced by the priority of the switches. Some values of importance are: 1 : The highest priority in Principal Switch selection, which is used by the administrator to establish which switch becomes the Principal Switch. 255 : Indicates that the switch is not capable of acting as a Principal Switch.Reference: Fibre Channel - Switch Fabric - 3 (FC-SW-3), ANSI INCITS 384-2004, section 6.1.5. (1..255) · Unsigned32 · hint d

The running priority of a particular switch on this Fabric. This value is initialized to the value of t11FamPriority, and subsequently altered as specified by the procedures defined in FC-SW-3.

T11FamDomainPriorityPriority of a switch. The Principal Switch selection is influenced by the priority of the switches. Some values of importance are: 1 : The highest priority in Principal Switch selection, which is used by the administrator to establish which switch becomes the Principal Switch. 255 : Indicates that the switch is not capable of acting as a Principal Switch.Reference: Fibre Channel - Switch Fabric - 3 (FC-SW-3), ANSI INCITS 384-2004, section 6.1.5. (1..255) · Unsigned32 · hint d

The running priority of the Principal Switch on this Fabric.

T11FamState1 = other2 = starting3 = unconfigured4 = principalSwitchSelection5 = domainIdDistribution6 = buildFabricPhase7 = reconfigureFabricPhase8 = stable9 = stableWithNoEports10 = noDomains11 = disabled12 = unknownThe state of the Fabric Address Manager, as described in Table 86 and Figure 15 of FC-SW-3. - 'other' represents a switch that is in a state not represented by any of the below enumerations. - 'starting' represents a switch engaged in the process represented by the first row in Table 86. - 'unconfigured' represents a switch that requires operator input before it can begin the process represented by the first row in Table 86. - 'principalSwitchSelection' represents a switch engaged in the process represented by the second row in Table 86, but not in states F0 or F1 of Figure 15. - 'domainIdDistribution' represents a switch engaged in the process represented by the third row in Table 86. - 'buildFabricPhase' represents a switch that is in state F0 of Figure 15. - 'reconfigureFabricPhase' represents a switch that is in state F1 of Figure 15. - 'stable' represents a switch that has successfully completed the process represented by the third row in Table 86 and has at least one E_Port. - 'stableWithNoEports' represents a switch that has successfully completed the process represented by the third row in Table 86 but has no E_Ports. - 'noDomains' represents a switch that has completed the process represented by the third row in Table 86 but failed to obtain a Domain_ID. - 'disabled' represents any situation in which the corresponding instance of t11FamEnable has the value 'false'. - 'unknown' represents a switch that is confused about what state it is in.Reference: Fibre Channel - Switch Fabric - 3 (FC-SW-3), ANSI INCITS 384-2004, Table 86 and Figure 15. · Integer32

The state of the Fabric Address Manager on a particular switch on this Fabric.

Counter32

The number of times a particular switch became the Principal Switch on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.

Counter32

The number of Principal Switch selections on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.

Counter32

The number of non-disruptive fabric reconfigurations (BFs) that have occurred on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.

Counter32

The number of disruptive fabric reconfigurations (RCFs) that have occurred on this Fabric. This counter has no discontinuities other than those that all Counter32s have when sysUpTime=0.

FcDomainIdOrZeroThe Domain Id (of an FC switch), or zero if the no Domain Id has been assigned. (0..239) · Integer32

The Domain_ID of a particular switch on this Fabric or zero if no Domain_ID has been assigned.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

An indication of whether a particular switch is supporting the concept of Preferred Domain_IDs via a best-effort attempt to re-assign the same Fibre Channel Address Identifier value to a port on the next occasion when a port requests an assignment on this Fabric. If the value of this object is 'true', then the switch is maintaining rows in the t11FamFcIdCacheTable for this Fabric.

INTEGER1 = nonDisruptive2 = disruptive3 = noOp · Integer32

This object tells the Fabric Address Manager to request a Fabric reconfiguration. If this object is set to 'disruptive', then an RCF (ReConfigure Fabric) is generated in the Fabric in order for the Fabric to recover from the errors. If this object is set to 'nonDisruptive', then a BF (Build Fabric) is generated in the Fabric. No action is taken if this object is set to 'noOp'. The value of the object when read is always 'noOp'. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

An indication of whether or not a particular switch should issue a t11FamFabricChangeNotify notification on sending or receiving ReConfigureFabric (RCF) on a Fabric. If the value of the object is 'true', then the notification is generated. If the value is 'false', notification is not generated. If an implementation requires all Fabrics to have the same value, then setting one instance of this object to a new object will result in all corresponding instances being set to that same new value. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Enables the Fabric Address Manager on this switch on this Fabric. If enabled on a Fabric, the switch will participate in Principal Switch selection, and Domain_IDs are assigned dynamically. If disabled, the switch will not participate in Principal Switch selection, and Domain_IDs are assigned statically. Thus, the corresponding value of t11FamConfigDomainIdType needs to be 'static'. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause. ⓘ

FcNameIdOrZeroThe World Wide Name (WWN) associated with a Fibre Channel (FC) entity. WWNs were initially defined as 64-bits in length. The latest definition (for future use) is 128-bits long. The zero-length string value is used in circumstances in which the WWN is unassigned/unknown. SIZE (0 | 8 | 16) · OCTET STRING

The WWN that is configured on this switch to be used as the name of this Fabric when the value of t11FamEnable is 'false'. If the value of t11FamEnable is 'true', this value is not used. Fibre Channel requires that: a) all switches in an operational Fabric be configured with the same Fabric name; and b) each Fabric have a unique Fabric name. If either of these is violated, either by switches within a single Fabric being configured with different Fabric names, or by multiple Fabrics that share management applications or interact in other ways having the same Fabric name, then the behavior of the switches and associated management functions is not specified by Fibre Channel or Internet standards. For the persistence of values across reboots, see the MODULE-IDENTITY's DESCRIPTION clause. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object determines if the incoming ReConfigure Fabric (RCF) messages on this interface on this Fabric is accepted or not. If this object is 'true', then the incoming RCF is rejected. If 'false', incoming RCF is accepted. Note that this object does not apply to the outgoing RCFs generated by this interface. Implementations that support write-access to this object can do so under whatever conditions they choose.

T11FamDomainInterfaceRole1 = nonPrincipal2 = principalUpstream3 = principalDownsteam4 = isolated5 = down6 = unknownThe 'designated' state/role of the Inter-Switch Link (ISL) to which an interface connects, or (if not connected) the state of the interface: nonPrincipal (1) - non-Principal ISL principalUpstream (2) - Upstream Principal ISL principalDownsteam (3) - Downstream Principal ISL isolated (4) - interface is isolated down (5) - interface is down unknown (6) - state/role is unknownReference: Fibre Channel - Switch Fabric - 3 (FC-SW-3), ANSI INCITS 384-2004, Sections 3.1, 5.7, and Figure 9. · Integer32

The role of this interface.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

The status of this row.

Unsigned32 (0..255)

The Area_ID of this area.

OCTET STRING SIZE (0..256)

The list of Port_IDs which have been assigned in this area and Fabric, formatted as an array of octets in ascending order. There could be zero or more Port_IDs assigned on this area and Fabric. Each octet represents one Port_ID. So, the list containing the Port_IDs 23, 45, 235, and 56 would be formatted as the 4-octet string x'172d38eb'.

FcDomainIdOrZeroThe Domain Id (of an FC switch), or zero if the no Domain Id has been assigned. (1..239) · Integer32

The Domain_ID for which this row contains information. The value must be non-zero.

FcNameIdOrZeroThe World Wide Name (WWN) associated with a Fibre Channel (FC) entity. WWNs were initially defined as 64-bits in length. The latest definition (for future use) is 128-bits long. The zero-length string value is used in circumstances in which the WWN is unassigned/unknown. SIZE (0 | 8 | 16) · OCTET STRING

The node name (WWN) of the switch to which the corresponding value of t11FamDatabaseDomainId is currently assigned for the particular Fabric.

FcNameIdOrZeroThe World Wide Name (WWN) associated with a Fibre Channel (FC) entity. WWNs were initially defined as 64-bits in length. The latest definition (for future use) is 128-bits long. The zero-length string value is used in circumstances in which the WWN is unassigned/unknown. SIZE (0 | 8 | 16) · OCTET STRING

The N_Port_Name (WWN) of the port associated with this entry.

OCTET STRING SIZE (2)

The combination of this object and t11FamFcIdCachePortIds represent one range of Fibre Channel Address Identifiers, which were assigned and later released. This object contains the Area_ID and Port_ID of the first Fibre Channel Address Identifier in the range. Note that this object is only 2 bytes.

Unsigned32 (0..65535)

The combination of t11FamFcIdCacheAreaIdPortId and this object represent one range of Fibre Channel Address Identifiers, which were assigned and later released. This object contains the number of (consecutive) Fibre Channel Address Identifiers in the range.