CISCO-STP-EXTENSIONS-MIB

OCTET STRING SIZE (128)

A string of octets containing one bit per VLAN in the management domain on this trunk port. The first octet corresponds to VLANs with VlanIndex values of 0 through 7; the second octet to VLANs 8 through 15; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is preferred on this trunk port, then the bit corresponding to that VLAN is set to '1'. The default value is 128 bytes of zeros. To avoid conflicts between overlapping partial updates by multiple managers, i.e., updates which modify only a portion of an instance of this object (e.g., enable/disable a single VLAN on the trunk port), any SNMP Set operation accessing an instance of this object should also write the value of vlanTrunkPortSetSerialNo.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 1024 through 2047 in the management domain on this trunk port. The first octet corresponds to VLANs with VlanIndex values of 1024 through 1031; the second octet to VLANs 1032 through 1039; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is preferred on this trunk port, then the bit corresponding to that VLAN is set to '1'. The default value is 128 bytes of zeros. To avoid conflicts between overlapping partial updates by multiple managers, i.e., updates which modify only a portion of an instance of this object (e.g., enable/disable a single VLAN on the trunk port), any SNMP Set operation accessing an instance of this object should also write the value of vlanTrunkPortSetSerialNo.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 2048 through 3071 in the management domain on this trunk port. The first octet corresponds to VLANs with VlanIndex values of 2048 through 2055; the second octet to VLANs 2056 through 2063; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is preferred on this trunk port, then the bit corresponding to that VLAN is set to '1'. The default value is 128 bytes of zeros. To avoid conflicts between overlapping partial updates by multiple managers, i.e., updates which modify only a portion of an instance of this object (e.g., enable/disable a single VLAN on the trunk port), any SNMP Set operation accessing an instance of this object should also write the value of vlanTrunkPortSetSerialNo.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 3072 through 4095 in the management domain on this trunk port. The first octet corresponds to VLANs with VlanIndex values of 3072 through 3079; the second octet to VLANs 3080 through 3087; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is preferred on this trunk port, then the bit corresponding to that VLAN is set to '1'. The default value is 128 bytes of zeros. To avoid conflicts between overlapping partial updates by multiple managers, i.e., updates which modify only a portion of an instance of this object (e.g., enable/disable a single VLAN on the trunk port), any SNMP Set operation accessing an instance of this object should also write the value of vlanTrunkPortSetSerialNo.

VlanIndexThe VLAN-id of a VLAN on ISL or 802.1q trunks. Modification of default parameters is allowed. Implementations are allowed to restrict the range of VLANs. For entities support up to 1024 VLANS. VLANs above 1000 are reserved for default VLANs and future use. Modification of default parameters is allowed. Creation or deletion of VLANs above 1000 is not allowed. For a new object which needs the vlan-id of a VLAN as its SYNTAX, it is suggested to import VlanIndex from Q-BRIDGE-MIB instead of importing this TC here in CISCO-VTP-MIB. (0..4095) · Integer32

An index value that uniquely identifies the Virtual LAN associated with this information.

INTEGER1 = enabled2 = disabled3 = notApplicable · Integer32

Indicates whether Spanning Tree PVST+ Protocol is enabled for this Virtual LAN. If Spanning Tree PVST+ Protocol is not supported on this VLAN, then notApplicable(3) will be returned while retrieving the object value for this VLAN. If the device only supports a single global Spanning Tree PVST+ Protocol enable/disable for all the existing VLANs, then the object value assigned to this VLAN will be applied to the object values of all the instances in this table which do not have the value of notApplicable(3). If the value of stpxSpanningTreeType is neither pvstPlus(1) nor rapidPvstPlus(5), then the value of stpxPVSTVlanEnable for this VLAN can not be changed.

VlanIndexThe VLAN-id of a VLAN on ISL or 802.1q trunks. Modification of default parameters is allowed. Implementations are allowed to restrict the range of VLANs. For entities support up to 1024 VLANS. VLANs above 1000 are reserved for default VLANs and future use. Modification of default parameters is allowed. Creation or deletion of VLANs above 1000 is not allowed. For a new object which needs the vlan-id of a VLAN as its SYNTAX, it is suggested to import VlanIndex from Q-BRIDGE-MIB instead of importing this TC here in CISCO-VTP-MIB. (0..4095) · Integer32

The VLAN id of the VLAN.

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

BITS

Reference: dot1dStpPortState is defined in RFC-1493.

The types of inconsistency which have been discovered on this port for this VLAN's Spanning Tree. When this object exists, the value of the corresponding instance of the Bridge MIB's dot1dStpPortState object will be 'broken(6)'.

Integer32 (0..65535)

The Spanning Tree Instance ID, such as the MST instance.

Integer32 (1..65535)

The value of dotdBasePort (i.e. dot1dBridge.1.4) for the bridge port.

BITS

Reference: dot1dStpPortState is defined in RFC-1493.

The type of inconsistency which has been discovered on this port for this Spanning Tree. When this object exists, the value of the corresponding instance of the Bridge MIB's dot1dStpPortState object will be 'broken(6)'.

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

An indication of whether the RootGuard capability is enabled on this port or not. This configuration will be applied to all Spanning Tree instances in which this port exists.

Integer32 (0..65535)

The Spanning Tree instance id, such as the VLAN id of the VLAN if the object value of stpxSpanningTreeType is pvstPlus(1) or rapidPvstPlus(5).

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Indicates whether the port on a particular Spanning Tree instance is currently in root-inconsistent state or not.

Unsigned32

The contribution of this port to the path cost (in 32 bits value) of paths towards the spanning tree root which include this port. This object is used to configure the spanning tree port path cost in 32 bits value range when the stpxSpanningTreePathCostOperMode is long(2). If the stpxSpanningTreePathCostOperMode is short(1), this MIB object is not instantiated.

Integer32 (1..256)

An arbitrary integer within the range from 1 to the value of stpxMISTPInstanceNumber that uniquely identifies an instance.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates whether the MISTP protocol is currently enabled on the MISTP instance. If this object is set to 'true' - the MISTP protocol will run on this instance. 'false' - the MISTP protocol will stop running on this instance.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN. The first octet corresponds to VLANs with VlanIndex values of 0 through 7; the second octet to VLANs 8 through 15; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MISTP instance, then the bit corresponding to that VLAN is set to '1'.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 1024 through 2047. The first octet corresponds to VLANs with VlanIndex values of 1024 through 1031; the second octet to VLANs 1032 through 1039; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MISTP instance, then the bit corresponding to that VLAN is set to '1'. This object is only instantiated on devices with support for VlanIndex up to 4095.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 2048 through 3071. The first octet corresponds to VLANs with VlanIndex values of 2048 through 2055; the second octet to VLANs 2056 through 2063; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MISTP instance, then the bit corresponding to that VLAN is set to '1'. This object is only instantiated on devices with support for VlanIndex up to 4095.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 3072 through 4095. The first octet corresponds to VLANs with VlanIndex values of 3072 through 3079; the second octet to VLANs 3080 through 3087; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MISTP instance, then the bit corresponding to that VLAN is set to '1'. This object is only instantiated on devices with support for VlanIndex up to 4095.

Integer32 (0..256)

The MISTP instance, to which the corresponding vlan is mapped. If this value of this mib object is 0, the corresponding vlan is not configured to be mapped to any MISTP instance and all the ports under this VLAN remain in blocking state.

Integer32 (0..256)

The MISTP instance, to which the corresponding vlan would be mapped. The value of this mib object is from 0 to the value of stpxMISTPInstanceNumber. If setting the value of this object to 0, the corresponding vlan will not be mapped to a MISTP instance and all the ports under this VLAN will be moved into the blocking state.

OCTET STRING SIZE (1..32)

A string of octets containing one bit per MISTP instances in the management domain on this trunk port. The first octet corresponds to MISTP instances with InstIndex values of 1 through 8; the second octet to MISTP instances 9 through 16; etc. The most significant bit of each octet corresponds to the lowest value instanceIndex in that octet. The number of bits for this mib object will be determined by the value of stpxMISTPInstanceNumber. For each instance, if it is preferred on this trunk port, then the bit corresponding to that instance is set to '1'. To avoid conflicts between overlapping partial updates by multiple managers, i.e., updates which modify only a portion of an instance of this object (e.g., enable/disable a single instance on the trunk port), any SNMP Set operation accessing an instance of this object should also write the value of vlanTrunkPortSetSerialNo.

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

An indication of whether the LoopGuard capability is enabled on this port or not. This configuration will be applied to all the Spanning Tree instances in which this port exists. In order to support additional Loop Guard config mode (default) as defined in stpxLoopGuardConfigMode other than enable (true(1)) or disable (false(2)) as defined in this object, stpxLoopGuardConfigMode object needs to be used. When the stpxLoopGuardConfigMode object has the value of enable(1), the value of stpxLoopGuardConfigEnabled for the same instance will be true(1). When the stpxLoopGuardConfigMode object has the value of disable(2), the value of stpxLoopGuardConfigEnabled for the same instance will be false(2). When the stpxLoopGuardConfigMode object has the value of default(3), the value of stpxLoopGuardConfigEnabled for the same instance will depend on the object value of stpxLoopGuardGlobalDefaultMode.

INTEGER1 = enable2 = disable3 = default · Integer32

Indicates the mode of Loop Guard Feature on this port. This configuration will be applied to all the Spanning Tree instances in which this port exists. enable -- the Loop Guard feature is enabled on this port. disable -- the Loop Guard feature is disabled on this port. default -- whether the Loop Guard feature is enabled or not on this port depends on the object value of stpxLoopGuardGlobalDefaultMode.

Integer32 (0..65535)

The Spanning Tree instance id, such as the VLAN id of the VLAN if the object value of stpxSpanningTreeType is pvstPlus(1) or rapidPvstPlus(5).

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Indicates whether the port on a particular Spanning Tree instance is currently in loop-inconsistent state or not.

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Indicates whether the port is operating in spantree fast start mode. A port with fast start enabled is immediately put in spanning tree forwarding state when that port is detected by the Spanning Tree, rather than starting in blocking state which is the normal operation. In order to support additional Fast Start enable mode (enableForTrunk and default) as defined in stpxFastStartPortMode other than enable (true(1)) or disable (false(2)) as defined in this object, stpxFastStartPortMode object needs to be used. When the stpxFastStartPortMode has the value of enable(1) or enableForTrunk(3), the value of stpxFastStartPortEnable for the same instance will be true(1). When the stpxFastStartPortMode has the value of disable(2), the value of stpxFastStartPortEnable for the same instance will be false(2). When the stpxFastStartPortMode has the value of default(4), the value of stpxFastStartPortEnable for the same instance depends on the object value of stpxFastStartGlobalDefaultMode.

INTEGER1 = enable2 = disable3 = enableForTrunk4 = default5 = network · Integer32

Indicates the mode of Fast Start Feature on the port. A port with fast start enabled is immediately put in spanning tree forwarding state when the port is detected by the Spanning Tree, rather than starting in blocking state which is the normal operation. enable -- the fast start feature is enabled on this port but will only take effect when the object value of its vlanTrunkPortDynamicStatus as specified in CISCO-VTP-MIB is notTrunking(2). disable -- the fast start feature is disabled on this port. enableForTrunk -- the fast start feature is enabled on this port and will take effect regardless of the object value of its vlanTrunkPortDynamicStatus. default -- whether the fast start feature is enabled or not on this port depends on the object value of stpxFastStartGlobalDefaultMode. network -- the network mode is enabled on this port.

INTEGER1 = enable2 = disable3 = default · Integer32

Indicates the mode of Bpdu Guard Feature on the port. A port with Bpdu Guard enabled is immediately disabled when the system receives a BPDU from that port. enable -- the Bpdu Guard feature is enabled on this port. disable -- the Bpdu Guard feature is disabled on this port. default -- whether the Bpdu Guard feature is enabled or not on this port depends on the object value of stpxFastStartBpduGuardEnable. If the value of stpxFastStartBpduGuardEnable is true(1) and Fast Start feature is also enabled operationally on this port, then this port is immediately disabled when the system receives a BPDU from this port.

INTEGER1 = enable2 = disable3 = default · Integer32

Indicates the mode of Bpdu Filter Feature on the port. The system will not transmit BPDUs on a port with Bpdu Filter feature enabled. enable -- the Bpdu Filter feature is enabled on this port. disable -- the Bpdu Filter feature is disabled on this port. default -- whether the Bpdu Filter feature is enabled or not on this port depends on the object value of stpxFastStartBpduFilterEnable. If the value of stpxFastStartBpduFilterEnable is true(1) and Fast Start feature is also enabled operationally on this port, then no BPDUs will be transmitted on this port.

Integer32 (0..65535)

The Spanning Tree instance id, such as the VLAN id of the VLAN if the object value of stpxSpanningTreeType is pvstPlus(1).

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

INTEGER1 = enabled2 = disabled3 = network · Integer32

Indicates the fast start operational status of the port on a particular Spanning Tree Instance. enable -- the fast start feature is operationally enabled on this port and the port is in edge mode. disable -- the fast start feature is operationally disabled on this port. network -- the port is in network mode.

Integer32 (0..65535)

The Spanning Tree instance id, such as the VLAN id of the VLAN if the object value of stpxSpanningTreeType is pvstPlus(1).

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

Unsigned32 · milliseconds

Indicates the skew duration in milliseconds of the last BPDU skewing detected.

Unsigned32 · milliseconds

Indicates the skew duration in milliseconds of the worst BPDU skewing detected.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

Indicates the value of sysUpTime when the worst BPDU skewing was detected.

Integer32 (0..256)

An integer that uniquely identifies an MST instance within the range of 0 to the object value of stpxMSTMaxInstanceNumber. This object is deprecated and replaced by stpxSMSTInstanceIndex.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN. The first octet corresponds to VLANs with VlanIndex values of 0 through 7; the second octet to VLANs 8 through 15; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. This object is deprecated and replaced by stpxSMSTInstanceVlansMapped1k2k.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 1024 through 2047. The first octet corresponds to VLANs with VlanIndex values of 1024 through 1031; the second octet to VLANs 1032 through 1039; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. This object is deprecated and replaced by stpxSMSTInstanceVlansMapped1k2k.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 2048 through 3071. The first octet corresponds to VLANs with VlanIndex values of 2048 through 2055; the second octet to VLANs 2056 through 2063; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. This object is deprecated and replaced by stpxSMSTInstanceVlansMapped3k4k.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 3072 through 4095. The first octet corresponds to VLANs with VlanIndex values of 3072 through 3079; the second octet to VLANs 3080 through 3087; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. This object is deprecated and replaced by stpxSMSTInstanceVlansMapped3k4k.

Integer32 (0..40)

The remaining hop count for this MST instance. This object will take on value of 40 if the object value of stpxSMSTInstanceRemainingHopCount is greater than 40. This object is only instantiated when the object value of stpxSpanningTreeType is mst(4). This object is deprecated and replaced by stpxSMSTInstanceRemainingHopCount.

Integer32 (0..256)

An integer that uniquely identifies an MST instance from 0 to the object value of stpxMSTMaxInstanceNumber. The instances of this table entry with stpxMSTInstanceEditIndex of zero can not be modified. This object is deprecated and replaced by stpxSMSTInstanceEditIndex.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN. The first octet corresponds to VLANs with VlanIndex values of 0 through 7; the second octet to VLANs 8 through 15; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. Each VLAN can only be mapped to one unique MST instance in the range from 1 to stpxMSTMaxInstanceNumber. If the bit corresponding to a VLAN is changed from '1' to '0', then that VLAN will be automatically mapped to MST instance 0 by the device. This object is deprecated and replaced by stpxSMSTInstanceEditVlansMap1k2k.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 1024 through 2047. The first octet corresponds to VLANs with VlanIndex values of 1024 through 1031; the second octet to VLANs 1032 through 1039; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. Each VLAN can only be mapped to one unique MST instance in the range from 1 to stpxMSTMaxInstanceNumber. If the bit corresponding to a VLAN is changed from '1' to '0', then that VLAN will be automatically mapped to MST instance 0 by the device. This object is deprecated and replaced by stpxSMSTInstanceEditVlansMap1k2k.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 2048 through 3071. The first octet corresponds to VLANs with VlanIndex values of 2048 through 2055; the second octet to VLANs 2056 through 2063; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. Each VLAN can only be mapped to one unique MST instance in the range from 1 to stpxMSTMaxInstanceNumber. If the bit corresponding to a VLAN is changed from '1' to '0', then that VLAN will be automatically mapped to MST instance 0 by the device. This object is deprecated and replaced by stpxSMSTInstanceEditVlansMap3k4k.

OCTET STRING SIZE (0..128)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 3072 through 4095. The first octet corresponds to VLANs with VlanIndex values of 3072 through 3079; the second octet to VLANs 3080 through 3087; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. Each VLAN can only be mapped to one unique MST instance in the range from 1 to stpxMSTMaxInstanceNumber. If the bit corresponding to a VLAN is changed from '1' to '0', then that VLAN will be automatically mapped to MST instance 0 by the device. This object is deprecated and replaced by stpxSMSTInstanceEditVlansMap3k4k.

OCTET STRING SIZE (1..32)

A string of octets containing one bit per MST instances on this trunk port. The first octet corresponds to MST instances of 0 through 7; the second octet to MST instances 8 through 15; etc. The most significant bit of each octet corresponds to the lowest MST instance value in that octet. The number of bits for this mib object will be determined by the value of stpxMSTMaxInstanceNumber. For each instance, if it is preferred on this trunk port, then the bit corresponding to that instance is set to '1'.

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

INTEGER1 = pointToPoint2 = shared3 = auto · Integer32

Indicates the administrative link type configuration of a bridge port for the MST protocol. pointToPoint -- the port is administratively configured to be connected to a point-to-point link. shared -- the port is administratively configured to be connected to a shared medium. auto -- the administrative configuration of the port's link type depends on link duplex of the port. If the port link is full-duplex, the administrative link type configuration on this port will be taken as pointTopoint(1). If the port link is half-duplex, the administrative link type configuration on this port will be taken as shared(2). This configuration of this object only takes effect when the stpxSpanningTreeType is mst(4) or rapidPvstPlus(5). stpxMSTPortAdminLinkType is deprecated and replaced with stpxRSTPPortAdminLinkType.

INTEGER1 = pointToPoint2 = shared3 = other · Integer32

Indicates the operational link type of a bridge port for the MST protocol. pointToPoint -- the port is operationally connected to a point-to-point link. shared -- the port is operationally connected to a shared medium. other -- none of the above. This object is only instantiated when the object value of stpxSpanningTreeType is mst(4). stpxMSTPortOperLinkType is deprecated and replaced with stpxRSTPPortOperLinkType.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Reference: IEEE 802.1w clause 14.8.2.4, 17.26.

The protocol migration control on this port. When the object value of stpxSpanningTreeType is mst(4) or rapidPvstPlus(5), setting true(1) to this object forces the device to try using version 2 BPDUs on this port. When the object value of stpxSpanningTreeType is neither mst(4) nor rapidPvstPlus(5), setting true(1) to this object has no effect. Setting false(2) to this object has no effect. This object always returns false(2) when read. stpxMSTPortProtocolMigration is deprecated and replaced with stpxRSTPPortProtocolMigration.

BITS

Indicates the operational status of the port for the MST protocol. edge -- this port is an edge port for the MST region. boundary -- this port is a boundary port for the MST region. pvst -- this port is connected to a PVST/PVST+ bridge. stp -- this port is connected to a Single Spanning Tree bridge. This object is only instantiated when the object value of stpxSpanningTreeType is mst(4). This object is deprecated and replaced by stpxSMSTPortStatus.

Integer32 (0..256)

The MST instance id within the range of 0 to stpxMSTMaxInstanceNumber.

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

INTEGER1 = disabled2 = root3 = designated4 = alternate5 = backUp6 = boundary7 = master · Integer32

Indicates the port role on a particular MST instance for the MST protocol. disabled -- this port has no role on this MST instance. root -- this port has the role of root port on this MST instance. designated -- this port has the role of designated port on this MST instance. alternate -- this port has the role of alternate port on this MST instance. backUp -- this port has the role of backup port on this MST instance. boundary -- this port has the role of boundary port on this MST instance. master -- this port has the role of master port on this MST instance.

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

INTEGER1 = pointToPoint2 = shared3 = auto · Integer32

Indicates the administrative link type configuration of a bridge port for the RSTP protocol. pointToPoint -- the port is administratively configured to be connected to a point-to-point link. shared -- the port is administratively configured to be connected to a shared medium. auto -- the administrative configuration of the port's link type depends on link duplex of the port. If the port link is full-duplex, the administrative link type configuration on this port will be taken as pointTopoint(1). If the port link is half-duplex, the administrative link type configuration on this port will be taken as shared(2). This configuration of this object only takes effect when the stpxSpanningTreeType is mst(4) or rapidPvstPlus(5).

INTEGER1 = pointToPoint2 = shared3 = other · Integer32

Indicates the operational link type of a bridge port for the RSTP protocol. pointToPoint -- the port is operationally connected to a point-to-point link. shared -- the port is operationally connected to a shared medium. other -- none of the above. This object is only instantiated when the object value of stpxSpanningTreeType is mst(4) or rapidPvstPlus(5).

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Reference: IEEE 802.1w clause 14.8.2.4, 17.26.

The protocol migration control on this port. When the object value of stpxSpanningTreeType is mst(4) or rapidPvstPlus(5), setting true(1) to this object forces the device to try using version 2 BPDUs on this port. When the object value of stpxSpanningTreeType is neither mst(4) nor rapidPvstPlus(5), setting true(1) to this object has no effect. Setting false(2) to this object has no effect. This object always returns false(2) when read.

Integer32 (0..4095)

The Spanning Tree instance id, it can either be a VLAN number if the stpxSpanningTreeType is rapidPvstPlus(5) or an MST instance id if the stpxSpanningTreeType is mst(4).

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

INTEGER1 = disabled2 = root3 = designated4 = alternate5 = backUp6 = boundary7 = master · Integer32

Indicates the port role on a particular Spanning Tree instance for the RSTP protocol. disabled -- this port has no role in this Spanning Tree instance. root -- this port has the role of root port in this Spanning Tree instance. designated -- this port has the role of designated port in this Spanning Tree instance. alternate -- this port has the role of alternate port in this Spanning Tree instance. backUp -- this port has the role of backup port in this Spanning Tree instance. boundary -- this port has the role of boundary port in this Spanning Tree instance. master -- this port has the role of master port in this Spanning Tree instance. This object could have a value of 'boundary' or 'master' only when the object value of stpxSpanningTreeType is mst(4).

VlanIndexThe VLAN-id of a VLAN on ISL or 802.1q trunks. Modification of default parameters is allowed. Implementations are allowed to restrict the range of VLANs. For entities support up to 1024 VLANS. VLANs above 1000 are reserved for default VLANs and future use. Modification of default parameters is allowed. Creation or deletion of VLANs above 1000 is not allowed. For a new object which needs the vlan-id of a VLAN as its SYNTAX, it is suggested to import VlanIndex from Q-BRIDGE-MIB instead of importing this TC here in CISCO-VTP-MIB. (0..4095) · Integer32

The VLAN id of the VLAN.

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

BITS

Indicates the operational status of the port for the Rapid PVST+ protocol. edge -- this port is an edge port for the RST region. unused1 -- unused bit 1. unused2 -- unused bit 2. stp -- this port is connected to a Single Spanning Tree/PVST+ bridge. dispute -- this port, as a designated port, received an inferior BPDU with a designated role and the learning bit being set.

Unsigned32

The MST instance ID, the value of which is in the range from 0 to stpxSMSTMaxInstanceID.

OCTET STRING SIZE (0..256)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 0 through 2047. The first octet corresponds to VLANs with VlanIndex values of 0 through 7; the second octet to VLANs 8 through 15; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. If the length of this string is less than 256 octets, any 'missing' octets are assumed to contain the value of zero.

OCTET STRING SIZE (0..256)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 2048 through 4095. The first octet corresponds to VLANs with VlanIndex values of 2048 through 2055; the second octet to VLANs 2056 through 2063; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. If the length of this string is less than 256 octets, any 'missing' octets are assumed to contain the value of zero.

Integer32 (-1..2147483647)

The remaining hop count for this MST instance. If this object value is not applicable on an MST instance, then the value retrieved for this object for that MST instance will be -1. This object is only instantiated when the object value of stpxSpanningTreeType is mst(4).

OCTET STRING SIZE (8)

Reference: IEEE 802.1S-2002: Section 13.9.

Indicates the Bridge Identifier (refer to BridgeId defined in BRIDGE-MIB) of CIST (Common and Internal Spanning Tree) Regional Root for the MST region. This object is only instantiated when the object value of stpxSpanningTreeType is mst(4) and stpxSMSTInstanceIndex is 0.

Unsigned32

Reference: IEEE 802.1S-2002: Section 13.9.

Indicates the CIST Internal Root Path Cost, i.e., the path cost to the CIST Regional Root as specified by the corresponding stpxSMSTInstanceCISTRegionalRoot for the MST region. This object is only instantiated when the object value of stpxSpanningTreeType is mst(4) and stpxSMSTInstanceIndex is 0.

Unsigned32

The MST instance ID, the value of which is in the range from 0 to stpxSMSTMaxInstanceID. The instances of this table entry with stpxSMSTInstanceEditIndex of zero is automatically created by the device and can not modified.

OCTET STRING SIZE (0..256)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 0 through 2047. The first octet corresponds to VLANs with VlanIndex values of 0 through 7; the second octet to VLANs 8 through 15; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. Each VLAN can only be mapped to one unique MST instance with the range from 0 to stpxSMSTMaxInstanceNumber. If the bit corresponding to a VLAN is changed from '1' to '0', then that VLAN will be automatically mapped to SMST instance 0 by the device. If the bit corresponding to a VLAN is changed from '0' to '1', then that VLAN will be automatically removed from the MST instance this VLAN was previously mapped to. If the length of this string is less than 256 octets, any 'missing' octets are assumed to contain the value of zero.

OCTET STRING SIZE (0..256)

A string of octets containing one bit per VLAN for VLANS with VlanIndex values of 2048 through 4095. The first octet corresponds to VLANs with VlanIndex values of 2048 through 2055; the second octet to VLANs 2056 through 2063; etc. The most significant bit of each octet corresponds to the lowest value VlanIndex in that octet. For each VLAN, if it is mapped to this MST instance, then the bit corresponding to that VLAN is set to '1'. Each VLAN can only be mapped to one unique MST instance with the range from 0 to stpxSMSTMaxInstanceNumber. If the bit corresponding to a VLAN is changed from '1' to '0', then that VLAN will be automatically mapped to SMST instance 0 by the device. If the bit corresponding to a VLAN is changed from '0' to '1', then that VLAN will be automatically removed from the MST instance this VLAN was previously mapped to. If the length of this string is less than 256 octets, any 'missing' octets are assumed to contain the value of zero.

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

This object controls the creation and deletion of a row in stpxSMSTInstanceEditTable. When creating an entry in this table, 'createAndGo' method is used and the value of this object is set to 'active'. Deactivation of an 'active' entry is not allowed. When deleting an entry in this table, 'destroy' method is used. Once a row becomes active, value in any other column within such a row may be modified. When a row is active, setting the instance of stpxSMSTInstanceEditVlansMap1k2k stpxSMSTInstanceEditVlansMap3k4k for the same MST instance both to the value of zero length can not be allowed.

Integer32 (1..65535)

Reference: dot1dBasePort is defined in RFC1493.

The value of dot1dBasePort (i.e. dot1dBridge.1.4) for the bridge port.

BITS

Indicates the operational status of the port for the MST protocol. edge -- this port is an edge port for the MST region. boundary -- this port is a boundary port for the MST region. pvst -- this port is connected to a PVST/PVST+ bridge. stp -- this port is connected to a Single Spanning Tree bridge. dispute -- this port, as a designated port, received an inferior BPDU with a designated role and the learning bit being set. rstp -- this port is connected to a RSTP bridge or an MST bridge in a different MST region.

Unsigned32 · hundredth of seconds

The adminitratively configured hello time in hundredth of seconds on a port for IEEE MST. The granularity of this timer is 1 second. An agent may return a badValue error if a set is attempted to a value which is not a whole number of seconds. This object value of zero means the hello time is not specifically configured on this port and object value of stpxSMSTPortConfigedHelloTime retrieved for this port will take on the value of dot1dStpBridgeHelloTime defined in BRIDGE-MIB.

Unsigned32 · hundredth of seconds

Indicates the effective configuration of the hello time on a port.

Integer32 (-1..2147483647) · hundredth of seconds

The operational hello time in hundredth of seconds on a port for IEEE MST. If this object value is not applicable on a port, then the value retrieved on that port will be -1.

INTEGER1 = preStandard2 = auto · Integer32

The desired MST mode of this port. preStandard -- this port is administratively configured to transmit pre-standard, i.e. pre IEEE MST, BPDUs. auto -- the BPDU transmission mode of this port is based on automatic detection of neighbor ports.

INTEGER1 = unknown2 = preStandard3 = standard · Integer32

Indicates the current operational MST mode of this port. unknown -- the operational mode is currently unknown. preStandard -- this port is currently operating in pre-standard MSTP BPDU transmission mode. standard -- this port is currently operating in IEEE MST BPDU transmission mode.