CISCO-CFS-MIB

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.

Imported Objects

ciscoMgmtCISCO-SMI
InetAddressType, InetAddressINET-ADDRESS-MIB
SnmpAdminStringSNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUPSNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPESNMPv2-SMI
TEXTUAL-CONVENTION, TimeStampSNMPv2-TC
ciscoCFSMIB .1.3.6.1.4.1.9.9.433
ciscoCFSMIBNotifs .1.3.6.1.4.1.9.9.433.0
ciscoCFSFeatureActionNotif .1.3.6.1.4.1.9.9.433.0.1
ciscoCFSMergeFailNotif .1.3.6.1.4.1.9.9.433.0.2
ciscoCFSDiscoveryCompleteNotif .1.3.6.1.4.1.9.9.433.0.3
ciscoCFSMIBObjects .1.3.6.1.4.1.9.9.433.1
cfsFeature .1.3.6.1.4.1.9.9.433.1.1
cfsFeatureOpTable .1.3.6.1.4.1.9.9.433.1.1.1
cfsFeatureOpEntry .1.3.6.1.4.1.9.9.433.1.1.1.1
cfsFeatureOpName .1.3.6.1.4.1.9.9.433.1.1.1.1.1
cfsFeatureOpShowCfgOption deprecated.1.3.6.1.4.1.9.9.433.1.1.1.1.10
cfsFeatureOpStatus .1.3.6.1.4.1.9.9.433.1.1.1.1.11
cfsFeatureOpAttribs .1.3.6.1.4.1.9.9.433.1.1.1.1.12
cfsFeatureOpAction .1.3.6.1.4.1.9.9.433.1.1.1.1.2
cfsFeatureOpScopeType .1.3.6.1.4.1.9.9.433.1.1.1.1.3
cfsFeatureOpScopeVal .1.3.6.1.4.1.9.9.433.1.1.1.1.4
cfsFeatureOpLastAction .1.3.6.1.4.1.9.9.433.1.1.1.1.5
cfsFeatureOpLastScopeType .1.3.6.1.4.1.9.9.433.1.1.1.1.6
cfsFeatureOpLastScopeVal .1.3.6.1.4.1.9.9.433.1.1.1.1.7
cfsFeatureOpLastActionResult .1.3.6.1.4.1.9.9.433.1.1.1.1.8
cfsFeatureOpLastFailureReason .1.3.6.1.4.1.9.9.433.1.1.1.1.9
cfsPendingConfOwnerTable .1.3.6.1.4.1.9.9.433.1.1.2
cfsPendingConfOwnerEntry .1.3.6.1.4.1.9.9.433.1.1.2.1
cfsPendingConfOwnerScopeType .1.3.6.1.4.1.9.9.433.1.1.2.1.1
cfsPendingConfOwnerScopeVal .1.3.6.1.4.1.9.9.433.1.1.2.1.2
cfsPendingConfOwnerAddrType .1.3.6.1.4.1.9.9.433.1.1.2.1.3
cfsPendingConfOwnerAddr .1.3.6.1.4.1.9.9.433.1.1.2.1.4
cfsPendingConfOwnerIDType .1.3.6.1.4.1.9.9.433.1.1.2.1.5
cfsPendingConfOwnerID .1.3.6.1.4.1.9.9.433.1.1.2.1.6
cfsMergeStatusTable .1.3.6.1.4.1.9.9.433.1.1.3
cfsMergeStatusEntry .1.3.6.1.4.1.9.9.433.1.1.3.1
cfsMergeStatusScopeType .1.3.6.1.4.1.9.9.433.1.1.3.1.1
cfsMergeStatusScopeVal .1.3.6.1.4.1.9.9.433.1.1.3.1.2
cfsMergeStatusValue .1.3.6.1.4.1.9.9.433.1.1.3.1.3
cfsMergeMembersTable .1.3.6.1.4.1.9.9.433.1.1.4
cfsMergeMembersEntry .1.3.6.1.4.1.9.9.433.1.1.4.1
cfsMergeMemberAddrType .1.3.6.1.4.1.9.9.433.1.1.4.1.1
cfsMergeMemberAddr .1.3.6.1.4.1.9.9.433.1.1.4.1.2
cfsMergeMemberFabricType .1.3.6.1.4.1.9.9.433.1.1.4.1.3
cfsMergeMemberRole .1.3.6.1.4.1.9.9.433.1.1.4.1.4
cfsPeersTable .1.3.6.1.4.1.9.9.433.1.1.5
cfsPeersEntry .1.3.6.1.4.1.9.9.433.1.1.5.1
cfsPeerAddrType .1.3.6.1.4.1.9.9.433.1.1.5.1.1
cfsPeerAddr .1.3.6.1.4.1.9.9.433.1.1.5.1.2
cfsFeaturePeersTable .1.3.6.1.4.1.9.9.433.1.1.6
cfsFeaturePeersEntry .1.3.6.1.4.1.9.9.433.1.1.6.1
cfsFeaturePeersScopeType .1.3.6.1.4.1.9.9.433.1.1.6.1.1
cfsFeaturePeersScopeVal .1.3.6.1.4.1.9.9.433.1.1.6.1.2
cfsFeaturePeersAddrType .1.3.6.1.4.1.9.9.433.1.1.6.1.3
cfsFeaturePeersAddr .1.3.6.1.4.1.9.9.433.1.1.6.1.4
cfsFeatureOpExtTable .1.3.6.1.4.1.9.9.433.1.1.7
cfsFeatureOpExtEntry .1.3.6.1.4.1.9.9.433.1.1.7.1
cfsFeatureOpExtScopeType .1.3.6.1.4.1.9.9.433.1.1.7.1.1
cfsFeatureOpExtScopeVal .1.3.6.1.4.1.9.9.433.1.1.7.1.2
cfsFeatureOpExtLastAction .1.3.6.1.4.1.9.9.433.1.1.7.1.3
cfsFeatureOpExtLastActionResult .1.3.6.1.4.1.9.9.433.1.1.7.1.4
cfsFeatureOpExtLastFailureReason .1.3.6.1.4.1.9.9.433.1.1.7.1.5
cfsFeatureOpExtShowCfgOption .1.3.6.1.4.1.9.9.433.1.1.7.1.6
cfsFeatureOpExtLastActionTime .1.3.6.1.4.1.9.9.433.1.1.7.1.7
cfsNotifObjects .1.3.6.1.4.1.9.9.433.1.2
cfsMergeFailFeatureName .1.3.6.1.4.1.9.9.433.1.2.1
cfsMergeFailScopeType .1.3.6.1.4.1.9.9.433.1.2.2
cfsMergeFailScopeVal .1.3.6.1.4.1.9.9.433.1.2.3
cfsMergeFailReasonDescription .1.3.6.1.4.1.9.9.433.1.2.4
cfsDiscoveryObjects .1.3.6.1.4.1.9.9.433.1.3
cfsStartPeersDiscovery .1.3.6.1.4.1.9.9.433.1.3.1
cfsPeersDiscoveryResult .1.3.6.1.4.1.9.9.433.1.3.2
cfsPeersDiscoveryFailureReason .1.3.6.1.4.1.9.9.433.1.3.3
cfsDistCtrlObjects .1.3.6.1.4.1.9.9.433.1.4
cfsDistCtrl .1.3.6.1.4.1.9.9.433.1.4.1
cfsDistCtrlTable .1.3.6.1.4.1.9.9.433.1.4.2
cfsDistCtrlEntry .1.3.6.1.4.1.9.9.433.1.4.2.1
cfsDistCtrlAddrType .1.3.6.1.4.1.9.9.433.1.4.2.1.1
cfsDistCtrlAddr .1.3.6.1.4.1.9.9.433.1.4.2.1.2
cfsDistCtrlAction .1.3.6.1.4.1.9.9.433.1.4.2.1.3
ciscoCFSMIBConformance .1.3.6.1.4.1.9.9.433.2
ciscoCFSMIBCompliances .1.3.6.1.4.1.9.9.433.2.1
ciscoCFSMIBGroups .1.3.6.1.4.1.9.9.433.2.2