T11-FC-FSPF-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. In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics can operate within one (or more) physical infrastructures. In such a case, index value is used to uniquely identify a particular Fabric within a physical infrastructure. In a Fabric that has (can have) only a single Fabric operating within the physical infrastructure, the value of this Fabric Index will always be 1.

Unsigned32 (0..65535) · milliSeconds

The minimum time after accepting a Link State Record (LSR) on this Fabric before accepting another update of the same LSR on the same Fabric. An LSR update that is not accepted because of this time interval is discarded. ⓘ

Unsigned32 (0..65535) · milliSeconds

The minimum time after this switch sends an LSR on this Fabric before it will send another update of the same LSR on the same Fabric. ⓘ

Unsigned32 · Minutes

The interval between transmission of refresh LSRs on this Fabric. ⓘ

Unsigned32 · Minutes

The maximum age an LSR will be retained in the FSPF database on this Fabric. An LSR is removed from the database after MaxAge is reached. ⓘ

Counter32

The number of LSRs discarded due to their age reaching t11FspfMaxAge in this Fabric. The last discontinuity of this counter is indicated by t11FspfCreateTime.

Counter32

The number of times that the path computation algorithm has been invoked by this Switch on this Fabric to compute a set of minimum cost paths for this Fabric. The last discontinuity of this counter is indicated by t11FspfCreateTime. ⓘ

Counter32

The number of FSPF checksum errors that were detected locally (and therefore discarded) on this Fabric. The last discontinuity of this counter is indicated by t11FspfCreateTime. ⓘ

Gauge32

The current number of entries for this Fabric in the t11FspfLsrTable.

T11FspfLastCreationTimeThis TC describes an object that stores the last time it, and the row containing it, was created. This can be used by management applications to determine that a row has been deleted and re-created between reads, causing an otherwise undetectable discontinuity in the data. · TimeTicks

The value of sysUpTime when this entry was last created.

INTEGER1 = up2 = down · Integer32

The desired state of FSPF in this Fabric. If value of this object is set to 'up', then FSPF is enabled in this Fabric. If set to 'down', then FSPF is disabled in this Fabric -- when FSPF is disabled, FSPF provides no routes to be included in the T11-FC-ROUTE-MIB module. (see the T11-FC-ROUTE-MIB). ⓘ

INTEGER1 = up2 = down · Integer32

State of FSPF in this Fabric. If 't11FspfAdminStatus' is 'down', then the 't11FspfOperStatus' should be 'down'. If 't11FspfAdminStatus' is changed to 'up', then 't11FspfOperStatus' should change to 'up' as and when FSPF is active in this Fabric.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Specifies whether or not the local agent should issue the notification 't11FspfNbrStateChangNotify' when the local switch learns of a change of state in the FSPF Neighbor Finite State Machine on an interface in this Fabric. If the value of the object is 'true, then the notification is generated. If the value is 'false', notification is not generated.

INTEGER1 = default2 = noOp · Integer32

Setting this value to 'default' changes the value of each and every writable object in this row to its default value. No action is taken if this object is set to 'noOp'. The value of the object, when read, is always 'noOp'.

StorageType1 = other2 = volatile3 = nonVolatile4 = permanent5 = readOnlyDescribes the memory realization of a conceptual row. A row which is volatile(2) is lost upon reboot. A row which is either nonVolatile(3), permanent(4) or readOnly(5), is backed up by stable storage. A row which is permanent(4) can be changed but not deleted. A row which is readOnly(5) cannot be changed nor deleted. If the value of an object with this syntax is either permanent(4) or readOnly(5), it cannot be written. Conversely, if the value is either other(1), volatile(2) or nonVolatile(3), it cannot be modified to be permanent(4) or readOnly(5). (All illegal modifications result in a 'wrongValue' error.) Every usage of this textual convention is required to specify the columnar objects which a permanent(4) row must at a minimum allow to be writable. · Integer32

The storage type for read-write objects in this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

The value of ifIndex that identifies the local Fibre Channel interface for which this entry contains FSPF information.

Unsigned32 (1..65535) · Seconds

Interval between the periodic HELLO messages sent on this interface in this Fabric to verify the link health. Note that this value must be same at both ends of a link in this Fabric.

Unsigned32 (2..65535) · Seconds

Maximum time for which no HELLO messages can be received on this interface in this Fabric. After this time, the interface is assumed to be broken and removed from the database. Note that this value must be greater than the HELLO interval specified on this interface in this Fabric.

Unsigned32 (1..65535) · Seconds

The time after which an unacknowledged LSR is retransmitted on this interface in this Fabric.

Counter32

Number of Link State Update (LSU) packets received on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.

Counter32

Number of Link State Acknowledgement (LSA) packets received on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.

Counter32

Number of Link State Update (LSU) packets transmitted on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.

Counter32

Number of Link State Acknowledgement (LSA) packets transmitted on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.

Counter32

Number of HELLO packets transmitted on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.

Counter32

Number of HELLO packets received on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.

Counter32

The number of LSU packets that contained one or more retransmitted LSRs, and that were transmitted on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.

Counter32

Number of invalid FSPF control packets received on this interface in this Fabric. The last discontinuity of this counter is indicated by t11FspfIfCreateTime.

T11FspfInterfaceState1 = down2 = init3 = dbExchange4 = dbAckwait5 = dbWait6 = fullThe state of the FSPF Neighbor Finite State Machine for the neighbor (switch) on a particular interface. Possible values are : down(1) - Down init(2) - Init dbExchange(3) - Database Exchange dbAckwait(4) - Database AckWait dbWait(5) - Database Wait full(6) - Full (Connected)Reference: Fibre Channel - Switch Fabric - 4 (FC-SW-4), ANSI INCITS 418-2006, section 8.7. · Integer32

The state of FSPF's 'neighbor state machine', which is the operational state of the interaction with the neighbor's interface that is connected to this interface. If the 't11FspfIfAdminStatus' is 'down', then this object should be 'down'. If the 't11FspfIfAdminStatus' is 'up', then this object's value depends on the state of FSPF's 'neighbor state machine' on this interface in this Fabric. ⓘ

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

The Domain Id of the neighbor in this Fabric.

Unsigned32 (0..16777215)

The index, as known by the neighbor, of the neighbor's interface that is connected to this interface in this Fabric. ⓘ

INTEGER1 = up2 = down · Integer32

The desired state of FSPF on this interface in this Fabric, whenever 't11FspfAdminStatus' is 'up'. If the value of this object is set to 'up', then FSPF is enabled on this interface in this Fabric. If set to 'down', then FSPF is disabled on this interface in this Fabric. Note that the operational state of FSPF on an interface is given by t11FspfIfNbrState.

T11FspfLastCreationTimeThis TC describes an object that stores the last time it, and the row containing it, was created. This can be used by management applications to determine that a row has been deleted and re-created between reads, causing an otherwise undetectable discontinuity in the data. · TimeTicks

The value of sysUpTime when this entry was last created.

INTEGER1 = default2 = noOp · Integer32

Setting this value to 'default' changes the value of each and every writable object in this row to its default value. If all the configuration parameters have their default values, and if the interface is down, then the row is deleted automatically. No action is taken if this object is set to 'noOp'. The value of the object, when read, is always 'noOp'.

Unsigned32 (1..65535)

The administrative factor used in calculating the cost of sending a frame on this interface in this Fabric. The formula used to calculate the link cost is: Link Cost = S * (1.0625e12 / ifSpeed) where: S = (the value of this object / 100) ifSpeed = interface speed (as defined in the IF-MIB). ⓘ

StorageType1 = other2 = volatile3 = nonVolatile4 = permanent5 = readOnlyDescribes the memory realization of a conceptual row. A row which is volatile(2) is lost upon reboot. A row which is either nonVolatile(3), permanent(4) or readOnly(5), is backed up by stable storage. A row which is permanent(4) can be changed but not deleted. A row which is readOnly(5) cannot be changed nor deleted. If the value of an object with this syntax is either permanent(4) or readOnly(5), it cannot be written. Conversely, if the value is either other(1), volatile(2) or nonVolatile(3), it cannot be modified to be permanent(4) or readOnly(5). (All illegal modifications result in a 'wrongValue' error.) Every usage of this textual convention is required to specify the columnar objects which a permanent(4) row must at a minimum allow to be writable. · Integer32

The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.

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 the conceptual row. This object can be used to create an entry only if there is an entry in the t11FspfTable for the corresponding Fabric, and if the interface is either isolated or is a non-E_port. Setting this object to 'destroy' will typically fail; to reverse the creation process, set the corresponding instance of t11FspfIfSetToDefault to 'default'.

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

Domain Id of the LSR owner in this Fabric. It is the Link State Id of this LSR.

T11FspfLsrTypeType of the Link State Record. FC-SW-4 defines two types of LSRs and allows for the possibility for more will be defined in the future: 01 - Switch Link Record 02 - Obsolete 240 - 255 - Vendor Specific others - Reserved.Reference: Fibre Channel - Switch Fabric - 4 (FC-SW-4), ANSI INCITS 418-2006, section 6.1.9.3. (0..255) · Integer32

Type of this LSR.

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

Domain Id of the switch that is advertising the LSR on the behalf of the switch owning it.

Unsigned32 (0..65535) · Seconds

The time since this LSR was inserted into the database.

Unsigned32

The link state incarnation number of this LSR. This is used to identify most recent instance of an LSR while updating the topology database when an LSR is received. The updating of an LSR includes incrementing its incarnation number prior to transmission of the updated LSR. So, the most recent LSR is the one with the largest incarnation number.

Unsigned32 (0..65535)

The checksum of the LSR.

Unsigned32 (0..65355)

Number of entries in the t11FspfLinkTable associated with this LSR.

Unsigned32 (1..4294967295)

An arbitrary index of this link.

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

The Domain Id of the neighbor on the other end of this link in this Fabric.

Unsigned32 (0..16777215)

The source E_port of this link, as indicated by the index value in the LSR received from the switch identified by 't11FspfLsrDomainId'.

Unsigned32 (0..16777215)

The destination E_port of this link, as indicated by the index value in the LSR received from the switch identified by 't11FspfLinkNbrDomainId'.

T11FspfLinkTypeType of an the FSPF Link. Presently defined values: 1 - Point-to-Point 240-255 - Vendor Specific all others - Reserved.Reference: Fibre Channel - Switch Fabric - 4 (FC-SW-4), ANSI INCITS 418-2006, section 6.1.9.4. (0..255) · Integer32

The type of this link.

Integer32 (0..65535)

The cost of sending a frame on this link in this Fabric. Link cost is calculated using the formula: link cost = S * (1.0625e12 / Signalling Rate) For issued LSRs, S is determined by the value of t11FspfIfLinkCostFactor for the corresponding interface and Fabric.