Reference record for OID 1.3.6.1.4.1.9.9.433


parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
node code
433
node name
ciscoCFSMIB
dot oid
1.3.6.1.4.1.9.9.433
type
OBJECT IDENTIFIER
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoCFSMIB(433)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoCFSMIB(433)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoCFSMIB(433)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoCFSMIB(433)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoCFSMIB(433)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoCFSMIB(433)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoCFSMIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoCFSMIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoCFSMIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoCFSMIB
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoCFSMIB
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoCFSMIB
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/9/9/433

    Description by circitor

    This MIB applies to one or more of a set of devices
    which have connectivity through some kind of 'fabric'.
    Many features which run in such an environment require
    the exchange of information between the peer devices
    which participate in providing the feature. An example
    of the type of information exchanged is configuration
    information. It would be advantageous to have the ability
    to have configuration for a feature done on one device
    and propagated to all other devices in the fabric.
    Cisco Fabric Service (CFS) is a general mechanism for
    data distribution within the fabric that could be used
    by most features.

    A feature supported in a device may or may not be CFS
    capable. In case a feature is CFS capable, the control
    of the CFS operations are instrumented through this MIB.

    A CFS capable feature can be enabled for data
    distribution within the fabric by the user via SNMP.
    When a CFS capable feature is enabled for data
    distribution, CFS operations can then be performed for
    that particular feature.

    As part of the CFS configuration the first mandatory step
    is to explicitly enable the feature for data distribution.
    This enabling of distribution for a feature needs to be
    done for those devices in the fabric where the distribution
    is intended. Following this mandatory step, feature specific
    configurations can be instrumented in the respective MIBs.

    Once a feature is enabled for data distribution, first
    subsequent feature specific configuration SET operation
    results in a snapshot of current 'Running Configuration'
    of the feature, on the local device. This snapshot is used
    for subsequent modifications by feature specific SET
    operations. Such modified configuration is referred to as
    'Pending Configuration'. There can only be one 'Pending
    Configuration' in the fabric. Additionally, such 'Pending
    Configuration' can be maintained within the context of
    additional scope, specific to the respective features.
    The user who initiates the creation of the 'Pending
    Configuration' is its owner. When a 'Pending Configuration'
    for a feature exists in one of the devices of the fabric,
    an attempt to create a 'Pending Configuration' for the same
    feature and on a different device by way of feature specific
    SET operation results in an error. This means feature
    specific SET operations intended for distribution can only
    be performed on the device that has the 'Pending
    Configuration' with it. This ensures data consistency for
    distribution.

    Once the configuration of a feature is ready to be
    distributed to all devices connected to the fabric, a
    'commit' action performed on the local device overwrites
    the local 'Running Configuration' and then distributes the
    new local 'Running Configuration' to all other devices in
    the fabric. The successful 'commit' action also results into
    destroying of the 'Pending Configuration' and makes the
    feature available for new distribution. Any attempt to
    perform 'commit' without any modification results in to an
    error. The 'commit' action can only be performed by the
    owner of the 'Pending Configuration'.

    The 'Pending Configuration' can optionally be destroyed
    without any distribution. This can be done by using either
    'abort' or 'clear' action. The 'abort' action needs to
    performed only on that device where the 'Pending
    Configuration' exists and can only be performed by the owner
    of the 'Pending Configuration'. The 'clear' action can be
    initiated through any of the devices in the fabric. The
    successful 'abort' or 'clear' operation makes the feature
    available for new distribution.

    The CFS, in addition to providing the basic distribution
    infrastructure to the CFS capable features in a stable
    fabric, also provides infrastructure to handle data
    distribution when two stable fabrics merge.

    This MIB module is to facilitate the global level control
    (enabling/disabling) and actions (commit/abort/clear) over
    the CFS capable features in the system.

    Glossary of the terms used in this MIB:


    VSAN - Virtual Storage Area Network,
    similar to a VLAN.

    CFS feature Scope - The scope of distribution.
    The scope provides the context
    within which the CFS actions
    are performed on a CFS capable
    feature.

    CFS Fabric Merge - The merging of two stable fabrics.
    The CFS provides infrastructure
    to handle data distribution for
    CFS distribution enabled features
    when the two stable fabrics merge.

    CFS control and actions :

    CFS Distribution Enable - This is to enable data distribution
    for CFS capable feature.

    CFS Distribution Disable - This is to disable data
    distribution for CFS capable
    feature.

    CFS Commit - This is to commit the 'Pending
    Configuration' on the local device.
    This action triggers the
    distribution of the 'Pending
    Configuration' to all the devices
    in the fabric.

    CFS Abort - This is to Destroy the 'Pending
    Configuration' on the local device
    without any distribution. Once
    local 'Pending Configuration' is
    destroyed, creation of 'Pending
    Configuration' in the local or any
    other device connected to the
    fabric is allowed.

    CFS Clear - This is to Destroy the 'Pending
    Configuration' that exists in any
    of the device in the fabric. Once
    'Pending Configuration' that exists
    with one of the devices in the
    fabric is destroyed, creation of
    'Pending Configuration' in the
    local or any other device connected
    to the fabric is allowed.

    Parsed from file CISCO-CFS-MIB.mib
    Module: CISCO-CFS-MIB

    Description by mibdepot

    This MIB applies to one or more of a set of devices
    which have connectivity through some kind of 'fabric'.
    Many features which run in such an environment require
    the exchange of information between the peer devices
    which participate in providing the feature. An example
    of the type of information exchanged is configuration
    information. It would be advantageous to have the ability
    to have configuration for a feature done on one device
    and propagated to all other devices in the fabric.
    Cisco Fabric Service (CFS) is a general mechanism for
    data distribution within the fabric that could be used
    by most features.

    A feature supported in a device may or may not be CFS
    capable. In case a feature is CFS capable, the control
    of the CFS operations are instrumented through this MIB.

    A CFS capable feature can be enabled for data
    distribution within the fabric by the user via SNMP.
    When a CFS capable feature is enabled for data
    distribution, CFS operations can then be performed for
    that particular feature.

    As part of the CFS configuration the first mandatory step
    is to explicitly enable the feature for data distribution.
    This enabling of distribution for a feature needs to be
    done for those devices in the fabric where the distribution
    is intended. Following this mandatory step, feature specific
    configurations can be instrumented in the respective MIBs.

    Once a feature is enabled for data distribution, first
    subsequent feature specific configuration SET operation
    results in a snapshot of current 'Running Configuration'
    of the feature, on the local device. This snapshot is used
    for subsequent modifications by feature specific SET
    operations. Such modified configuration is referred to as
    'Pending Configuration'. There can only be one 'Pending
    Configuration' in the fabric. Additionally, such 'Pending
    Configuration' can be maintained within the context of
    additional scope, specific to the respective features.
    The user who initiates the creation of the 'Pending
    Configuration' is its owner. When a 'Pending Configuration'
    for a feature exists in one of the devices of the fabric,
    an attempt to create a 'Pending Configuration' for the same
    feature and on a different device by way of feature specific
    SET operation results in an error. This means feature
    specific SET operations intended for distribution can only
    be performed on the device that has the 'Pending
    Configuration' with it. This ensures data consistency for
    distribution.

    Once the configuration of a feature is ready to be
    distributed to all devices connected to the fabric, a
    'commit' action performed on the local device overwrites
    the local 'Running Configuration' and then distributes the
    new local 'Running Configuration' to all other devices in
    the fabric. The successful 'commit' action also results into
    destroying of the 'Pending Configuration' and makes the
    feature available for new distribution. Any attempt to
    perform 'commit' without any modification results in to an
    error. The 'commit' action can only be performed by the
    owner of the 'Pending Configuration'.

    The 'Pending Configuration' can optionally be destroyed
    without any distribution. This can be done by using either
    'abort' or 'clear' action. The 'abort' action needs to
    performed only on that device where the 'Pending
    Configuration' exists and can only be performed by the owner
    of the 'Pending Configuration'. The 'clear' action can be
    initiated through any of the devices in the fabric. The
    successful 'abort' or 'clear' operation makes the feature
    available for new distribution.

    The CFS, in addition to providing the basic distribution
    infrastructure to the CFS capable features in a stable
    fabric, also provides infrastructure to handle data
    distribution when two stable fabrics merge.

    This MIB module is to facilitate the global level control
    (enabling/disabling) and actions (commit/abort/clear) over
    the CFS capable features in the system.

    Glossary of the terms used in this MIB:


    VSAN - Virtual Storage Area Network,
    similar to a VLAN.

    CFS feature Scope - The scope of distribution.
    The scope provides the context
    within which the CFS actions
    are performed on a CFS capable
    feature.

    CFS Fabric Merge - The merging of two stable fabrics.
    The CFS provides infrastructure
    to handle data distribution for
    CFS distribution enabled features
    when the two stable fabrics merge.

    CFS control and actions :

    CFS Distribution Enable - This is to enable data distribution
    for CFS capable feature.

    CFS Distribution Disable - This is to disable data
    distribution for CFS capable
    feature.

    CFS Commit - This is to commit the 'Pending
    Configuration' on the local device.
    This action triggers the
    distribution of the 'Pending
    Configuration' to all the devices
    in the fabric.

    CFS Abort - This is to Destroy the 'Pending
    Configuration' on the local device
    without any distribution. Once
    local 'Pending Configuration' is
    destroyed, creation of 'Pending
    Configuration' in the local or any
    other device connected to the
    fabric is allowed.

    CFS Clear - This is to Destroy the 'Pending
    Configuration' that exists in any
    of the device in the fabric. Once
    'Pending Configuration' that exists
    with one of the devices in the
    fabric is destroyed, creation of
    'Pending Configuration' in the
    local or any other device connected
    to the fabric is allowed.

    Parsed from file CISCO-CFS-MIB.my.txt
    Company: None
    Module: CISCO-CFS-MIB

    Description by cisco

    This MIB applies to one or more of a set of devices
    which have connectivity through some kind of 'fabric'.
    Many features which run in such an environment require
    the exchange of information between the peer devices
    which participate in providing the feature. An example
    of the type of information exchanged is configuration
    information. It would be advantageous to have the ability
    to have configuration for a feature done on one device
    and propagated to all other devices in the fabric.
    Cisco Fabric Service (CFS) is a general mechanism for
    data distribution within the fabric that could be used
    by most features.

    A feature supported in a device may or may not be CFS
    capable. In case a feature is CFS capable, the control
    of the CFS operations are instrumented through this MIB.

    A CFS capable feature can be enabled for data
    distribution within the fabric by the user via SNMP.
    When a CFS capable feature is enabled for data
    distribution, CFS operations can then be performed for
    that particular feature.

    As part of the CFS configuration the first mandatory step
    is to explicitly enable the feature for data distribution.
    This enabling of distribution for a feature needs to be
    done for those devices in the fabric where the distribution
    is intended. Following this mandatory step, feature specific
    configurations can be instrumented in the respective MIBs.

    Once a feature is enabled for data distribution, first
    subsequent feature specific configuration SET operation
    results in a snapshot of current 'Running Configuration'
    of the feature, on the local device. This snapshot is used
    for subsequent modifications by feature specific SET
    operations. Such modified configuration is referred to as
    'Pending Configuration'. There can only be one 'Pending
    Configuration' in the fabric. Additionally, such 'Pending
    Configuration' can be maintained within the context of
    additional scope, specific to the respective features.
    The user who initiates the creation of the 'Pending
    Configuration' is its owner. When a 'Pending Configuration'
    for a feature exists in one of the devices of the fabric,
    an attempt to create a 'Pending Configuration' for the same
    feature and on a different device by way of feature specific
    SET operation results in an error. This means feature
    specific SET operations intended for distribution can only
    be performed on the device that has the 'Pending
    Configuration' with it. This ensures data consistency for
    distribution.

    Once the configuration of a feature is ready to be
    distributed to all devices connected to the fabric, a
    'commit' action performed on the local device overwrites
    the local 'Running Configuration' and then distributes the
    new local 'Running Configuration' to all other devices in
    the fabric. The successful 'commit' action also results into
    destroying of the 'Pending Configuration' and makes the
    feature available for new distribution. Any attempt to
    perform 'commit' without any modification results in to an
    error. The 'commit' action can only be performed by the
    owner of the 'Pending Configuration'.

    The 'Pending Configuration' can optionally be destroyed
    without any distribution. This can be done by using either
    'abort' or 'clear' action. The 'abort' action needs to
    performed only on that device where the 'Pending
    Configuration' exists and can only be performed by the owner
    of the 'Pending Configuration'. The 'clear' action can be
    initiated through any of the devices in the fabric. The
    successful 'abort' or 'clear' operation makes the feature
    available for new distribution.

    The CFS, in addition to providing the basic distribution
    infrastructure to the CFS capable features in a stable
    fabric, also provides infrastructure to handle data
    distribution when two stable fabrics merge.

    This MIB module is to facilitate the global level control
    (enabling/disabling) and actions (commit/abort/clear) over
    the CFS capable features in the system.

    Glossary of the terms used in this MIB:


    VSAN - Virtual Storage Area Network,
    similar to a VLAN.

    CFS feature Scope - The scope of distribution.
    The scope provides the context
    within which the CFS actions
    are performed on a CFS capable
    feature.

    CFS Fabric Merge - The merging of two stable fabrics.
    The CFS provides infrastructure
    to handle data distribution for
    CFS distribution enabled features
    when the two stable fabrics merge.

    CFS control and actions :

    CFS Distribution Enable - This is to enable data distribution
    for CFS capable feature.

    CFS Distribution Disable - This is to disable data
    distribution for CFS capable
    feature.

    CFS Commit - This is to commit the 'Pending
    Configuration' on the local device.
    This action triggers the
    distribution of the 'Pending
    Configuration' to all the devices
    in the fabric.

    CFS Abort - This is to Destroy the 'Pending
    Configuration' on the local device
    without any distribution. Once
    local 'Pending Configuration' is
    destroyed, creation of 'Pending
    Configuration' in the local or any
    other device connected to the
    fabric is allowed.

    CFS Clear - This is to Destroy the 'Pending
    Configuration' that exists in any
    of the device in the fabric. Once
    'Pending Configuration' that exists
    with one of the devices in the
    fabric is destroyed, creation of
    'Pending Configuration' in the
    local or any other device connected
    to the fabric is allowed.

    Information by circitor

    ciscoCFSMIB MODULE-IDENTITY LAST-UPDATED "200606130000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Network Management Technology Group Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This MIB applies to one or more of a set of devices which have connectivity through some kind of 'fabric'. Many features which run in such an environment require the exchange of information between the peer devices which participate in providing the feature. An example of the type of information exchanged is configuration information. It would be advantageous to have the ability to have configuration for a feature done on one device and propagated to all other devices in the fabric. Cisco Fabric Service (CFS) is a general mechanism for data distribution within the fabric that could be used by most features. A feature supported in a device may or may not be CFS capable. In case a feature is CFS capable, the control of the CFS operations are instrumented through this MIB. A CFS capable feature can be enabled for data distribution within the fabric by the user via SNMP. When a CFS capable feature is enabled for data distribution, CFS operations can then be performed for that particular feature. As part of the CFS configuration the first mandatory step is to explicitly enable the feature for data distribution. This enabling of distribution for a feature needs to be done for those devices in the fabric where the distribution is intended. Following this mandatory step, feature specific configurations can be instrumented in the respective MIBs. Once a feature is enabled for data distribution, first subsequent feature specific configuration SET operation results in a snapshot of current 'Running Configuration' of the feature, on the local device. This snapshot is used for subsequent modifications by feature specific SET operations. Such modified configuration is referred to as 'Pending Configuration'. There can only be one 'Pending Configuration' in the fabric. Additionally, such 'Pending Configuration' can be maintained within the context of additional scope, specific to the respective features. The user who initiates the creation of the 'Pending Configuration' is its owner. When a 'Pending Configuration' for a feature exists in one of the devices of the fabric, an attempt to create a 'Pending Configuration' for the same feature and on a different device by way of feature specific SET operation results in an error. This means feature specific SET operations intended for distribution can only be performed on the device that has the 'Pending Configuration' with it. This ensures data consistency for distribution. Once the configuration of a feature is ready to be distributed to all devices connected to the fabric, a 'commit' action performed on the local device overwrites the local 'Running Configuration' and then distributes the new local 'Running Configuration' to all other devices in the fabric. The successful 'commit' action also results into destroying of the 'Pending Configuration' and makes the feature available for new distribution. Any attempt to perform 'commit' without any modification results in to an error. The 'commit' action can only be performed by the owner of the 'Pending Configuration'. The 'Pending Configuration' can optionally be destroyed without any distribution. This can be done by using either 'abort' or 'clear' action. The 'abort' action needs to performed only on that device where the 'Pending Configuration' exists and can only be performed by the owner of the 'Pending Configuration'. The 'clear' action can be initiated through any of the devices in the fabric. The successful 'abort' or 'clear' operation makes the feature available for new distribution. The CFS, in addition to providing the basic distribution infrastructure to the CFS capable features in a stable fabric, also provides infrastructure to handle data distribution when two stable fabrics merge. This MIB module is to facilitate the global level control (enabling/disabling) and actions (commit/abort/clear) over the CFS capable features in the system. Glossary of the terms used in this MIB: VSAN - Virtual Storage Area Network, similar to a VLAN. CFS feature Scope - The scope of distribution. The scope provides the context within which the CFS actions are performed on a CFS capable feature. CFS Fabric Merge - The merging of two stable fabrics. The CFS provides infrastructure to handle data distribution for CFS distribution enabled features when the two stable fabrics merge. CFS control and actions : CFS Distribution Enable - This is to enable data distribution for CFS capable feature. CFS Distribution Disable - This is to disable data distribution for CFS capable feature. CFS Commit - This is to commit the 'Pending Configuration' on the local device. This action triggers the distribution of the 'Pending Configuration' to all the devices in the fabric. CFS Abort - This is to Destroy the 'Pending Configuration' on the local device without any distribution. Once local 'Pending Configuration' is destroyed, creation of 'Pending Configuration' in the local or any other device connected to the fabric is allowed. CFS Clear - This is to Destroy the 'Pending Configuration' that exists in any of the device in the fabric. Once 'Pending Configuration' that exists with one of the devices in the fabric is destroyed, creation of 'Pending Configuration' in the local or any other device connected to the fabric is allowed. " REVISION "200606130000Z" DESCRIPTION "Added cfsFeatureOpExtLastActionTime object to cfsFeatureOpExtTable Added cfsFeatureOpExtGroupRev1 Added ciscoCFSMIBComplianceRev3 " REVISION "200511300000Z" DESCRIPTION "Added the following: - cfsDistCtrlTable table - cfsFeatureOpAttribs object to cfsFeatureOpTable " REVISION "200504270000Z" DESCRIPTION "Added an enumeration value of 'partialSuccess' to the 'CiscoCFSFeatureActionResult' TC. " REVISION "200412240000Z" DESCRIPTION "Added the cfsDistCtrl object to control the CFS distribution capability. " REVISION "200412030000Z" DESCRIPTION "Added the following tables: - cfsMergeMembersTable - cfsPeersTable - cfsFeaturePeersTable - cfsFeatureOpExtTable Added the following scalar objects: - cfsStartPeersDiscovery - cfsPeersDiscoveryResult - cfsPeersDiscoveryFailureReason Added additional enumerations for: - cfsMergeStatusValue Added notification: - ciscoCFSDiscoveryCompleteNotif " REVISION "200409150000Z" DESCRIPTION "Initial version of this MIB. " ::= { ciscoMgmt 433 }

    Information by cisco_v1

    ciscoCFSMIB OBJECT IDENTIFIER ::= { ciscoMgmt 433 }

    Information by oid_info

    Vendor: Cisco
    Module: CISCO-CFS-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    ciscoCFSMIB MODULE-IDENTITY LAST-UPDATED "200606130000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Network Management Technology Group Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This MIB applies to one or more of a set of devices which have connectivity through some kind of 'fabric'. Many features which run in such an environment require the exchange of information between the peer devices which participate in providing the feature. An example of the type of information exchanged is configuration information. It would be advantageous to have the ability to have configuration for a feature done on one device and propagated to all other devices in the fabric. Cisco Fabric Service (CFS) is a general mechanism for data distribution within the fabric that could be used by most features. A feature supported in a device may or may not be CFS capable. In case a feature is CFS capable, the control of the CFS operations are instrumented through this MIB. A CFS capable feature can be enabled for data distribution within the fabric by the user via SNMP. When a CFS capable feature is enabled for data distribution, CFS operations can then be performed for that particular feature. As part of the CFS configuration the first mandatory step is to explicitly enable the feature for data distribution. This enabling of distribution for a feature needs to be done for those devices in the fabric where the distribution is intended. Following this mandatory step, feature specific configurations can be instrumented in the respective MIBs. Once a feature is enabled for data distribution, first subsequent feature specific configuration SET operation results in a snapshot of current 'Running Configuration' of the feature, on the local device. This snapshot is used for subsequent modifications by feature specific SET operations. Such modified configuration is referred to as 'Pending Configuration'. There can only be one 'Pending Configuration' in the fabric. Additionally, such 'Pending Configuration' can be maintained within the context of additional scope, specific to the respective features. The user who initiates the creation of the 'Pending Configuration' is its owner. When a 'Pending Configuration' for a feature exists in one of the devices of the fabric, an attempt to create a 'Pending Configuration' for the same feature and on a different device by way of feature specific SET operation results in an error. This means feature specific SET operations intended for distribution can only be performed on the device that has the 'Pending Configuration' with it. This ensures data consistency for distribution. Once the configuration of a feature is ready to be distributed to all devices connected to the fabric, a 'commit' action performed on the local device overwrites the local 'Running Configuration' and then distributes the new local 'Running Configuration' to all other devices in the fabric. The successful 'commit' action also results into destroying of the 'Pending Configuration' and makes the feature available for new distribution. Any attempt to perform 'commit' without any modification results in to an error. The 'commit' action can only be performed by the owner of the 'Pending Configuration'. The 'Pending Configuration' can optionally be destroyed without any distribution. This can be done by using either 'abort' or 'clear' action. The 'abort' action needs to performed only on that device where the 'Pending Configuration' exists and can only be performed by the owner of the 'Pending Configuration'. The 'clear' action can be initiated through any of the devices in the fabric. The successful 'abort' or 'clear' operation makes the feature available for new distribution. The CFS, in addition to providing the basic distribution infrastructure to the CFS capable features in a stable fabric, also provides infrastructure to handle data distribution when two stable fabrics merge. This MIB module is to facilitate the global level control (enabling/disabling) and actions (commit/abort/clear) over the CFS capable features in the system. Glossary of the terms used in this MIB: VSAN - Virtual Storage Area Network, similar to a VLAN. CFS feature Scope - The scope of distribution. The scope provides the context within which the CFS actions are performed on a CFS capable feature. CFS Fabric Merge - The merging of two stable fabrics. The CFS provides infrastructure to handle data distribution for CFS distribution enabled features when the two stable fabrics merge. CFS control and actions : CFS Distribution Enable - This is to enable data distribution for CFS capable feature. CFS Distribution Disable - This is to disable data distribution for CFS capable feature. CFS Commit - This is to commit the 'Pending Configuration' on the local device. This action triggers the distribution of the 'Pending Configuration' to all the devices in the fabric. CFS Abort - This is to Destroy the 'Pending Configuration' on the local device without any distribution. Once local 'Pending Configuration' is destroyed, creation of 'Pending Configuration' in the local or any other device connected to the fabric is allowed. CFS Clear - This is to Destroy the 'Pending Configuration' that exists in any of the device in the fabric. Once 'Pending Configuration' that exists with one of the devices in the fabric is destroyed, creation of 'Pending Configuration' in the local or any other device connected to the fabric is allowed. " REVISION "200606130000Z" DESCRIPTION "Added cfsFeatureOpExtLastActionTime object to cfsFeatureOpExtTable Added cfsFeatureOpExtGroupRev1 Added ciscoCFSMIBComplianceRev3 " REVISION "200511300000Z" DESCRIPTION "Added the following: - cfsDistCtrlTable table - cfsFeatureOpAttribs object to cfsFeatureOpTable " REVISION "200504270000Z" DESCRIPTION "Added an enumeration value of 'partialSuccess' to the 'CiscoCFSFeatureActionResult' TC. " REVISION "200412240000Z" DESCRIPTION "Added the cfsDistCtrl object to control the CFS distribution capability. " REVISION "200412030000Z" DESCRIPTION "Added the following tables: - cfsMergeMembersTable - cfsPeersTable - cfsFeaturePeersTable - cfsFeatureOpExtTable Added the following scalar objects: - cfsStartPeersDiscovery - cfsPeersDiscoveryResult - cfsPeersDiscoveryFailureReason Added additional enumerations for: - cfsMergeStatusValue Added notification: - ciscoCFSDiscoveryCompleteNotif " REVISION "200409150000Z" DESCRIPTION "Initial version of this MIB. " ::= { ciscoMgmt 433 }

    Information by cisco

    ciscoCFSMIB MODULE-IDENTITY LAST-UPDATED "200606130000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Network Management Technology Group Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "This MIB applies to one or more of a set of devices which have connectivity through some kind of 'fabric'. Many features which run in such an environment require the exchange of information between the peer devices which participate in providing the feature. An example of the type of information exchanged is configuration information. It would be advantageous to have the ability to have configuration for a feature done on one device and propagated to all other devices in the fabric. Cisco Fabric Service (CFS) is a general mechanism for data distribution within the fabric that could be used by most features. A feature supported in a device may or may not be CFS capable. In case a feature is CFS capable, the control of the CFS operations are instrumented through this MIB. A CFS capable feature can be enabled for data distribution within the fabric by the user via SNMP. When a CFS capable feature is enabled for data distribution, CFS operations can then be performed for that particular feature. As part of the CFS configuration the first mandatory step is to explicitly enable the feature for data distribution. This enabling of distribution for a feature needs to be done for those devices in the fabric where the distribution is intended. Following this mandatory step, feature specific configurations can be instrumented in the respective MIBs. Once a feature is enabled for data distribution, first subsequent feature specific configuration SET operation results in a snapshot of current 'Running Configuration' of the feature, on the local device. This snapshot is used for subsequent modifications by feature specific SET operations. Such modified configuration is referred to as 'Pending Configuration'. There can only be one 'Pending Configuration' in the fabric. Additionally, such 'Pending Configuration' can be maintained within the context of additional scope, specific to the respective features. The user who initiates the creation of the 'Pending Configuration' is its owner. When a 'Pending Configuration' for a feature exists in one of the devices of the fabric, an attempt to create a 'Pending Configuration' for the same feature and on a different device by way of feature specific SET operation results in an error. This means feature specific SET operations intended for distribution can only be performed on the device that has the 'Pending Configuration' with it. This ensures data consistency for distribution. Once the configuration of a feature is ready to be distributed to all devices connected to the fabric, a 'commit' action performed on the local device overwrites the local 'Running Configuration' and then distributes the new local 'Running Configuration' to all other devices in the fabric. The successful 'commit' action also results into destroying of the 'Pending Configuration' and makes the feature available for new distribution. Any attempt to perform 'commit' without any modification results in to an error. The 'commit' action can only be performed by the owner of the 'Pending Configuration'. The 'Pending Configuration' can optionally be destroyed without any distribution. This can be done by using either 'abort' or 'clear' action. The 'abort' action needs to performed only on that device where the 'Pending Configuration' exists and can only be performed by the owner of the 'Pending Configuration'. The 'clear' action can be initiated through any of the devices in the fabric. The successful 'abort' or 'clear' operation makes the feature available for new distribution. The CFS, in addition to providing the basic distribution infrastructure to the CFS capable features in a stable fabric, also provides infrastructure to handle data distribution when two stable fabrics merge. This MIB module is to facilitate the global level control (enabling/disabling) and actions (commit/abort/clear) over the CFS capable features in the system. Glossary of the terms used in this MIB: VSAN - Virtual Storage Area Network, similar to a VLAN. CFS feature Scope - The scope of distribution. The scope provides the context within which the CFS actions are performed on a CFS capable feature. CFS Fabric Merge - The merging of two stable fabrics. The CFS provides infrastructure to handle data distribution for CFS distribution enabled features when the two stable fabrics merge. CFS control and actions : CFS Distribution Enable - This is to enable data distribution for CFS capable feature. CFS Distribution Disable - This is to disable data distribution for CFS capable feature. CFS Commit - This is to commit the 'Pending Configuration' on the local device. This action triggers the distribution of the 'Pending Configuration' to all the devices in the fabric. CFS Abort - This is to Destroy the 'Pending Configuration' on the local device without any distribution. Once local 'Pending Configuration' is destroyed, creation of 'Pending Configuration' in the local or any other device connected to the fabric is allowed. CFS Clear - This is to Destroy the 'Pending Configuration' that exists in any of the device in the fabric. Once 'Pending Configuration' that exists with one of the devices in the fabric is destroyed, creation of 'Pending Configuration' in the local or any other device connected to the fabric is allowed. " REVISION "200606130000Z" DESCRIPTION "Added cfsFeatureOpExtLastActionTime object to cfsFeatureOpExtTable Added cfsFeatureOpExtGroupRev1 Added ciscoCFSMIBComplianceRev3 " REVISION "200511300000Z" DESCRIPTION "Added the following: - cfsDistCtrlTable table - cfsFeatureOpAttribs object to cfsFeatureOpTable " REVISION "200504270000Z" DESCRIPTION "Added an enumeration value of 'partialSuccess' to the 'CiscoCFSFeatureActionResult' TC. " REVISION "200412240000Z" DESCRIPTION "Added the cfsDistCtrl object to control the CFS distribution capability. " REVISION "200412030000Z" DESCRIPTION "Added the following tables: - cfsMergeMembersTable - cfsPeersTable - cfsFeaturePeersTable - cfsFeatureOpExtTable Added the following scalar objects: - cfsStartPeersDiscovery - cfsPeersDiscoveryResult - cfsPeersDiscoveryFailureReason Added additional enumerations for: - cfsMergeStatusValue Added notification: - ciscoCFSDiscoveryCompleteNotif " REVISION "200409150000Z" DESCRIPTION "Initial version of this MIB. " ::= { ciscoMgmt 433 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Greg Satz

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Cisco Systems, Inc.

    Children (3)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.9.433.0 ciscoCFSMIBNotifs 3 3 None
    1.3.6.1.4.1.9.9.433.1 ciscoCFSMIBObjects 4 77 None
    1.3.6.1.4.1.9.9.433.2 ciscoCFSMIBConformance 2 19 None

    Brothers (645)

    To many brothers! Only 100 nearest brothers are shown.

    OIDNameSub childrenSub Nodes TotalDescription
    ...
    1.3.6.1.4.1.9.9.383 ciscoCidsMIB 3 183 Cisco Intrusion Detection System MIB. Provides
    trap definitions for the evAlert and evError
    elements of the IDIOM (Intrusion Det…
    1.3.6.1.4.1.9.9.384 ciscoDot11AntennaMIB 2 11 This MIB is intended to be implemented on 802.11
    Access Points and Wireless Bridges to provide
    information about the antennas con…
    1.3.6.1.4.1.9.9.385 ciscoUnityMIB 3 101 The MIB Module for the management of Cisco Unity server.
    Cisco Unity is a Unified Communications solution that provides
    advanced,…
    1.3.6.1.4.1.9.9.386 ciscoModuleAutoShutdownMIB 3 36 The CISCO-MODULE-AUTO-SHUTDOWN-MIB is used to configure
    the module automatic shutdown feature. Modules will be
    reset by the syste…
    1.3.6.1.4.1.9.9.387 ciscoNetflowMIB 3 206 The Netflow MIB provides a simple and easy method
    to get NetFlow cache information, current NetFlow
    configuration and statistics.…
    1.3.6.1.4.1.9.9.388 ciscoVirtualSwitchMIB 3 128 This MIB module defines the managed objects that support the
    virtual switch architecture.

    The virtual switch concept combines sev…
    1.3.6.1.4.1.9.9.389 ciscoVoiceCasModuleMIB 3 22 This MIB is used to support Programmable
    CAS signaling Bit configuration on modules
    that support voice traffic.

    This MIB will enab…
    1.3.6.1.4.1.9.9.390 ciscoCableDiagMIB 3 33 This MIB module defines objects for managing cable
    diagnostic test capabilites supported by the Cisco devices.

    Cable diagnostic t…
    1.3.6.1.4.1.9.9.391 ciscoFcspMIB 3 46 MIB module for managing Fibre Channel Security for the
    fibre channel devices.

    This MIB is used to configure and monitor the
    Fibre-…
    1.3.6.1.4.1.9.9.392 ciscoRemoteAccessMonitorMIB 3 199 Acronyms and Definitions
    The following acronyms and terms are used in this
    document:

    IPSec: Secure IP Protocol

    VPN: Virtual Priv…
    1.3.6.1.4.1.9.9.393 ciscoVoiceConnectivityMIB 3 44 This MIB module provides connectivity related
    information for devices (e.g., 'connectivity between
    voice gateway, phones, gatekee…
    1.3.6.1.4.1.9.9.394 ciscoIpTapMIB 3 28 This module manages Cisco's intercept feature for IP.

    This MIB is used along with CISCO-TAP2-MIB to
    intercept IP traffic. CISCO-T…
    1.3.6.1.4.1.9.9.395 cisco802TapMIB 3 20 This module manages Cisco's intercept feature for
    802 (layer 2) streams.

    This MIB is used along with CISCO-TAP2-MIB to
    intercept 8…
    1.3.6.1.4.1.9.9.396 ciscoMlrMIB 3 190 The MIB for providing information about Multi-layer
    Routing(MLR). This MIB will provide information used to
    control and measure S…
    1.3.6.1.4.1.9.9.397 ciscoH225MIB 1 176 Cisco H225 MIB module. This module consists of H225
    call signaling and H225 RAS (Registration, Admission
    and Status). These are p…
    1.3.6.1.4.1.9.9.398 ciscoMauExtMIB 3 23 A MIB module for extending the MAU-MIB (RFC 3636)
    to add objects which provide additional management
    information about MAU or Jac…
    1.3.6.1.4.1.9.9.399 ciscoTap2MIB 3 69 This module manages Cisco's intercept feature.
    This MIB replaces CISCO-TAP-MIB. This MIB defines
    a generic stream table that cont…
    1.3.6.1.4.1.9.9.400 ciscoUserConnectionTapMIB 2 13 This module manages Cisco's intercept feature for
    user connections.

    This MIB is used along with CISCO-TAP2-MIB to
    intercept user t…
    1.3.6.1.4.1.9.9.401 ciscoBridgeExtMIB 3 34 A MIB module for extending BRIDGE-MIB specified in RFC 1493.
    1.3.6.1.4.1.9.9.402 ciscoPowerEthernetExtMIB 3 79 A MIB module for extending the POWER-ETHERNET-MIB
    (RFC3621) to add objects which provide additional
    management information about …
    1.3.6.1.4.1.9.9.405 ciscoDnsServerMIB 3 400 The MIB module for entities implementing the server side
    of the Domain Name System (DNS) protocol.
    P. Mockapetris, 'Domain names …
    1.3.6.1.4.1.9.9.407 ciscoAtmTrunkStatMIB 3 101 The MIB module contains ATM Trunk statistics.

    TERMINOLOGY

    PVC: Permanent Virtual Circuit
    OAM: Operation and Management
    CRC: Cyclic…
    1.3.6.1.4.1.9.9.408 ciscoSnmpNotificationExtMIB 3 13 This MIB extends the functionality provided
    by SNMP-NOTIFICATION-MIB.
    This MIB provides for the aging of the
    notification filters …
    1.3.6.1.4.1.9.9.409 ciscoSnmpVacmExtMIB 2 11 The management information definitions to extend
    the View-based Access Control Model (RFC3415) for
    SNMP.

    This MIB extends the 'SN…
    1.3.6.1.4.1.9.9.411 ciscoVlanTranslationMIB 3 27 The MIB module for the management of VLAN translations.

    VLAN translation refers to the ability of the device
    to translate between…
    1.3.6.1.4.1.9.9.412 ciscoSnmpTargetExtMIB 2 30 This MIB is an extension of the SNMP-TARGET-MIB
    specified in RFC3413.

    This MIB module contains Cisco-defined extension
    to the sn…
    1.3.6.1.4.1.9.9.413 ciscoDot11SsidSecMIB 2 71 This MIB module provides network management
    support for Cisco IEEE 802.11 Wireless LAN
    devices association and authentication.

    ACR…
    1.3.6.1.4.1.9.9.414 ciscoPoePdMIB 3 17 This MIB is intended for devices powered by
    external power sources, in particular Power
    Over Ethernet (PoE or formerly called inl…
    1.3.6.1.4.1.9.9.415 ciscoWlanManMIB 3 13 This MIB module provides network management
    and configuration support for IEEE 802.11
    Wireless LAN devices.

    ACRONYMS

    HTTP
    Hypertext …
    1.3.6.1.4.1.9.9.416 ciscoDot11QosMIB 3 49 This MIB module provides network management
    support for QoS on wireless LAN devices. The
    objects defined in this MIB provide equ…
    1.3.6.1.4.1.9.9.420 ciscoUnityExpressMIB 3 179 The MIB Module for the management of the Cisco Unity
    Express (CUE) service. CUE is a voicemail service that
    runs in a Cisco rout…
    1.3.6.1.4.1.9.9.421 ciscoDpvmMIB 3 55 The MIB module for the management of the
    Dynamic Port Vsan Membership (DPVM) module.
    DPVM provides the ability to assign (virtual…
    1.3.6.1.4.1.9.9.422 ciscoIPsecTc 0 0 This MIB module defines the textual conventions
    used in the IPsec suite of MIBs. This includes
    Internet DOI numbers defined in RF…
    1.3.6.1.4.1.9.9.423 ciscoIkeConfigMIB 3 93 This is a MIB Module for configuring and viewing IKE
    parameters and policies.

    Acronyms
    The following acronyms are used in this do…
    1.3.6.1.4.1.9.9.424 ciscoCableMeteringMIB 3 53 This is the MIB module for Usage Based Metering for the
    DOCSIS-compliant Cable Modem Termination Systems (CMTS).

    Usage Based Mete…
    1.3.6.1.4.1.9.9.426 ciscoLinkErrorMonitorMIB 3 34 The MIB module for managing Link Error Monitoring
    Feature on devices.

    Link Error Monitoring Feature provides a mechanism
    to monito…
    1.3.6.1.4.1.9.9.427 ciscoZsExtMIB 3 33 The MIB module for the management of zoning within
    the framework of Cisco's Zoning Server (ZS) Archi-
    tecture which realizes the …
    1.3.6.1.4.1.9.9.428 ciscoIkeFlowExtMIB 3 18 This MIB module is an extension to
    CISCO-IKE-FLOW-MIB and contains Cisco Specific
    extensions for monitoring IKE.

    It is for monito…
    1.3.6.1.4.1.9.9.429 ciscoIkeFlowMIB 3 80 This is a MIB module for monitoring the structures
    and status of IPsec control flows based on Internet
    Key Exchange protocol. The…
    1.3.6.1.4.1.9.9.430 ciscoFcDeviceAliasMIB 3 14 The MIB module for the management of Device
    Aliases in a Fibre Channel Fabric. A Fibre
    Channel fabric consists of devices such as…
    1.3.6.1.4.1.9.9.431 ciscoIPsecProvisioningMIB 3 98 IPSec is the next-generation network layer crypto
    framework described in RFC2401-2411.
    This MIB defines the IPsec configurations.…
    1.3.6.1.4.1.9.9.432 ciscoEnhancedIpsecFlowMIB 3 330 This is a MIB Module for monitoring the structures
    and status of IPSec-based networks. The MIB has been
    designed to be adopted as…
    1.3.6.1.4.1.9.9.434 ciscoIpNetworkDiscoveryMIB, ciscoIsnsIpNetDiscoveryMIB 3 58 MIB to provide the information about the disjoint
    IP networks connected to the various gigabit ethernet
    interfaces in the 'Fabric…
    1.3.6.1.4.1.9.9.435 ciscoFcMulticastMIB 3 14 MIB module for monitoring and configuring
    Fibre Channel Multicast feature.
    1.3.6.1.4.1.9.9.436 ciscoDNSClientMIB 3 28 The MIB module for entities implementing the client
    side of the Domain Name System (DNS) protocol.
    1.3.6.1.4.1.9.9.437 ciscoPortTrackMIB 2 18 A MIB to configure the Port-Track feature.

    When a link goes down, all the services which depend
    on the link are notified of the o…
    1.3.6.1.4.1.9.9.438 ciscoIPsecSignalingMIB 3 140 This MIB Module models status, performance and failures
    of a protocol with the generic characteristics of signalling
    protocols us…
    1.3.6.1.4.1.9.9.439 ciscoCcmeMIB 3 338 This MIB allows management of Cisco CallManager Express
    (CCME) feature in Cisco IOS. CCME is optional software
    feature that enabl…
    1.3.6.1.4.1.9.9.441 ciscoSrstMIB 3 149 This MIB allows management of Cisco Survivable Remote
    Site Telephony (SRST) feature in Cisco IOS. SRST is
    an optional software fe…
    1.3.6.1.4.1.9.9.443 ciscoCommonMgmtMIB 3 37 MIB module for integrating different elements of
    managing a device. For example, different device access
    methods like SNMP, CLI, …
    1.3.6.1.4.1.9.9.445 ciscoQinqVlanMIB 3 25 This MIB defines configuration and monitoring capabilities
    relating to 802.1QinQ interfaces. QinQ interfaces are capable
    of term…
    1.3.6.1.4.1.9.9.447 ciscoScsiFlowMIB 3 99 A SCSI Flow is described as a SCSI Initiator
    SCSI Target combination. This MIB is used to
    configure and monitor SCSI Flows.

    Gloss…
    1.3.6.1.4.1.9.9.448 ciscoSsmProvMIB 2 26 This MIB is used to provision features
    on a Data Path Processor (DPP) of a Storage Service
    Module (SSM). A DPP is assigned to a c…
    1.3.6.1.4.1.9.9.449 ciscoEigrpMIB 3 103 Enhanced Interior Gateway Protocol (EIGRP) is a Cisco
    proprietary distance vector routing protocol. It is based on
    the Diffusin…
    1.3.6.1.4.1.9.9.450 ciscoCableAdmCtrlMIB 3 123 This MIB module defines the managed objects enabling
    the management of Cable Modem Termination System
    (CMTS) admission control.

    CM…
    1.3.6.1.4.1.9.9.451 ciscoIpUrpfMIB 3 47 Unicast Reverse Path Forwarding (URPF) is a function that
    checks the validity of the source address of IP packets
    received on an …
    1.3.6.1.4.1.9.9.454 ciscoDot11LbsMIB 3 23 This MIB module supports network management
    for Location Based Services on IEEE 802.11 wireless
    LAN devices. Location Based Serv…
    1.3.6.1.4.1.9.9.455 ciscoImageTc 0 0 This MIB module defines the textual conventions
    used in the enhanced image MIB.

    Glossary:

    Base Image
    Essential part of the operatin…
    1.3.6.1.4.1.9.9.456 ciscoDot11WidsMIB 3 50 This MIB is intended to be implemented on the
    following IOS based network entities for the purpose
    of providing network managemen…
    1.3.6.1.4.1.9.9.457 ciscoWdsIdsMIB 2 18 This MIB is intended to be implemented on all
    IOS based network entities that provide Wireless
    Domain Services, for the purpose o…
    1.3.6.1.4.1.9.9.458 ciscoApplianceRedundancyMIB 3 47 This mib defines the SNMP objects to report the status of
    High Availability (HA) functionality in Cisco network
    management applia…
    1.3.6.1.4.1.9.9.459 ciscoBitsClockMIB 3 21 This MIB provides information on Building Integrated
    Timing Supply(BITS) clocking sources and modes of
    operations. It is used to…
    1.3.6.1.4.1.9.9.460 ciscoTpcMIB 3 24 The MIB module for Third Party Copy(TPC):
    Third Party Copy derives its name from the fact
    that there are three entities involved …
    1.3.6.1.4.1.9.9.461 ciscoEtherCfmMIB 3 39 This MIB module defines the managed objects
    and notifications for Ethernet Connectivity
    Fault Management (CFM).

    CFM is an end-to-e…
    1.3.6.1.4.1.9.9.463 ciscoSanTapMIB 3 30 MIB module to provide information about the SanTap
    service configuration.

    SanTap is a fibre channel switch based capability that
    p…
    1.3.6.1.4.1.9.9.466 ciscoEthernetAccessMIB 2 20 The tables defined by this MIB module contain a collection
    of managed objects that are general in nature and apply to
    an edge dev…
    1.3.6.1.4.1.9.9.467 ciscoCryptoAcceleratorMIB 3 107 The MIB module for monitoring the identity, status,
    activity and faults of crypto accelerator (CA) modules
    used in devices implem…
    1.3.6.1.4.1.9.9.468 ciscoContextMappingMIB 2 35 A single SNMP agent sometimes needs to support multiple
    instances of the same MIB module, and does so through the
    use of multiple…
    1.3.6.1.4.1.9.9.470 ciscoEnhancedSlbMIB 3 106 The MIB for managing Server Load Balancing
    Manager(s), and products supporting Server
    Load Balancing(SLB) features.

    This MIB exten…
    1.3.6.1.4.1.9.9.471 ciscoFlexLinksMIB 3 36 This MIB module is for configuration and status query
    of Flex Links feature on the Cisco device.

    Flex Links are a pair of Layer 2…
    1.3.6.1.4.1.9.9.472 ciscoModuleVirtualizationMIB 3 35 This MIB provides a way to create virtual contexts,
    and managing them. A virtual context is logical
    partition of a physical devi…
    1.3.6.1.4.1.9.9.473 ciscoCcaMIB 3 200 The Cisco Contact Center Applications (CCCA) Management
    Information Base (MIB) module defines management
    instrumentation for appl…
    1.3.6.1.4.1.9.9.474 ciscoFilterGroupMIB 3 55 The MIB module is for creating and configuring
    object groups to support packet filtering and
    access control on IP and other proto…
    1.3.6.1.4.1.9.9.479 ciscoCableWidebandMIB 3 77 This is the MIB module for the support of Channel Bonding
    Protocol for the Cable Modem Termination System (CMTS).

    Wideband DOCSIS…
    1.3.6.1.4.1.9.9.480 ciscoL4L7moduleResourceLimitMIB 4 100 The MIB module for managing resource classes
    and configuring limits(max/min) to different
    resources. The resource referenced in …
    1.3.6.1.4.1.9.9.482 ciscoInterfaceTopNExtMIB 3 16 This MIB module is an extension to INTERFACETOPN-MIB.
    It provides additional management information for
    sorting device interfaces.
    1.3.6.1.4.1.9.9.483 ciscoIpRanBackHaulMIB 3 248 This MIB provides information on the IP-RAN traffic
    from cell site to aggregation site in the following
    situations. In an GSM en…
    ...