CISCO-CFS-MIB
AI MIB Summary
The CISCO-CFS-MIB provides SNMP control for Cisco Fabric Service (CFS) to manage the global enablement, distribution, and synchronization of configuration data across devices within a Cisco fabric. It specifically governs the lifecycle of pending configurations through commit, abort, and clear actions to ensure data consistency during feature propagation and fabric merge operations.
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.
Main OID:
ciscoCFSMIB.1.3.6.1.4.1.9.9.433
78
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
78 total| Object Name |
|---|
ciscoCFSMIBThis 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. MODULE-IDENTITY .1.3.6.1.4.1.9.9.433 |
ciscoCFSMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.433.0 |
ciscoCFSFeatureActionNotifNotification to covey the information of the action
performed on a CFS capable feature.
This notification gets generated when :
- a CFS operation action is triggered on CFS capable
feature
- the result of last action performed on the CFS
capable feature changes.
The 'cfsFeatureOpLastActionResult' indicates the new
value of the last action result performed on the feature. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.433.0.1 |
ciscoCFSMergeFailNotifNotification to convey the information of the 'Merge
Failure' occurred in the fabric. This notification gets
generated when the merge of the two fabrics fail for a
CFS capable feature. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.433.0.2 |
ciscoCFSDiscoveryCompleteNotifNotification to indicate that the CFS has completed
discovering the CFS capable devices in the fabric.
If the value of cfsPeersDiscoveryResult is 'successful',
then the cfsPeersTable is appropriately populated. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.433.0.3 |
ciscoCFSMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.433.1 |
cfsFeature OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.433.1.1 |
cfsFeatureOpTableThis table lists all the CFS capable features in the local
device.
The table provides control, actions, current operating
state information and last action result information for
CFS capable features.
Each entry in this table represents a CFS capable feature.
An entry in the table is created by the agent when CFS
capable feature registers with CFS infrastructure. The
agent removes the entry from the table when the CFS
capable de-registers with CFS infrastructure. Management
application can not create new entry in this table. SEQUENCE OF CfsFeatureOpEntry .1.3.6.1.4.1.9.9.433.1.1.1 |
cfsFeatureOpEntryA conceptual row in the cfsFeatureOpTable. Each row
represents a CFS capable feature in the system. CfsFeatureOpEntry .1.3.6.1.4.1.9.9.433.1.1.1.1 |
cfsFeatureOpNameA human readable string value uniquely identifying the
name of this feature. SnmpAdminString .1.3.6.1.4.1.9.9.433.1.1.1.1.1 |
cfsFeatureOpActionThe CFS action to be triggered for the feature. An operator
should successfully enable CFS distribution of a feature
by issuing an 'enable' action before performing a
'commit' or 'abort' operation.
The value of this object and the values of corresponding
instance of cfsFeatureOpScopeType and cfsFeatureOpScopeVal
are interpreted and applied together as single CFS action
trigger on the feature. The scope type and values provide
the context/scope within which the this action is applied.
Setting of this object will fail with 'inconsistentValue',
if the value of the corresponding instance of
cfsFeatureOpLastActionResult is 'inProgress'. However, the
value of this object can be set to 'clear' regardless of
the value of the corresponding instance of
cfsFeatureOpLastActionResult.
Retrieving the value of this object via SNMP will always
return 'noop'.rw CiscoCFSAction .1.3.6.1.4.1.9.9.433.1.1.1.1.2 |
cfsFeatureOpScopeTypeThe value of this object specifies the type of the value
of the corresponding instance of cfsFeatureOpScopeVal.
The agent is not required to retain the modified value of
this object across the agent restart.rw CiscoCFSScopeType .1.3.6.1.4.1.9.9.433.1.1.1.1.3 |
cfsFeatureOpScopeValThe CFS feature scope value to be used with
cfsFeatureOpScopeType.
The value of this object may not be relevant when the value
of the corresponding instance of cfsFeatureOpAction is SET
to 'enable' or 'disable'.
The agent is not required to retain the modified value of
this object across the agent restart.rw CiscoCFSScopeValue .1.3.6.1.4.1.9.9.433.1.1.1.1.4 |
cfsFeatureOpLastActionThe last action performed on this feature. If no action
has been triggered for the feature since the last reboot
of the system, then retrieving the value of this object
will return 'noop'.ro CiscoCFSAction .1.3.6.1.4.1.9.9.433.1.1.1.1.5 |
cfsFeatureOpLastScopeTypeThe last CFS feature scope type used for
cfsFeatureOpLastAction. If no action has been triggered
for the feature since the last reboot of the system, then
retrieving the value of this object will return 'none'.ro CiscoCFSScopeType .1.3.6.1.4.1.9.9.433.1.1.1.1.6 |
cfsFeatureOpLastScopeValThe last CFS feature scope value used for
cfsFeatureOpLastScopeType. If no action has been triggered
for the feature since the last reboot of the system, then
retrieving the value of this object will return zero-length
string.ro CiscoCFSScopeValue .1.3.6.1.4.1.9.9.433.1.1.1.1.7 |
cfsFeatureOpLastActionResultThe result of the execution of the last action (represented
by the value of cfsFeatureOpLastAction) for the feature.
When the value of this object is 'actionInProgress', the
value of the corresponding instance of cfsFeatureOpAction
can not be modified.ro CiscoCFSFeatureActionResult .1.3.6.1.4.1.9.9.433.1.1.1.1.8 |
cfsFeatureOpLastFailureReasonThe failure reason description for the failed execution
of last action performed on this feature.
If the corresponding instance of
cfsFeatureOpLastActionResult has the value
'actionFailed', then this object contains the reason
as to why it failed. Otherwise, the value of this
object is the zero-length string.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.433.1.1.1.1.9 |
cfsFeatureOpShowCfgOptionThis object provides a means for management
applications to either view the contents of 'Running
Configuration' or 'Pending Configuration'.
When the value of this object is 'runningConfig', all the
subsequent configuration retrieval for this feature will be
from 'Running Configuration' on the local device.
When the value of this object is 'pendingConfig', all the
subsequent configuration retrieval for this feature will be
from 'Pending Configuration' on the local device.
The value of this object is meaningful only when the value
of the corresponding instance of 'cfsFeatureOpStatus' is
'enabled'.
The agent is not required to retain the modified value of
this object across the agent restart.rwdeprecated Enumeration .1.3.6.1.4.1.9.9.433.1.1.1.1.10 |
cfsFeatureOpStatusThe current operating status of the feature.ro CiscoCFSFeatureStatus .1.3.6.1.4.1.9.9.433.1.1.1.1.11 |
cfsFeatureOpAttribsThe value of this object represents the attributes of
a CFS capable feature as registered with the CFS
infrastructure.
'fcFabric' - indicates that the CFS based
distribution for a feature spans the
entire FC (Fibre Channel) fabric
'ipNetwork' - indicates that the CFS based
distribution for a feature spans the
entire IP network
'vsanScope' - indicates that the CFS based
distribution for a feature is done
on per VSAN basis and restricted to a
specific VSAN in a FC (Fibre Channel)
fabricro Bits .1.3.6.1.4.1.9.9.433.1.1.1.1.12 |
cfsPendingConfOwnerTableThis table contains per-feature 'Pending Configuration'
owner information. This table will have entries only
for those features for which 'Pending Configuration'
exists in one of the devices in the fabric. This table
provides the 'Pending Configuration' owner (type and name)
information and Device address where the 'Pending
Configuration' exists in the fabric.
The 'Pending Configuration' owner details are per CFS
capable feature within a specific scope. SEQUENCE OF CfsPendingConfOwnerEntry .1.3.6.1.4.1.9.9.433.1.1.2 |
cfsPendingConfOwnerEntryA conceptual row in the 'cfsPendingConfOwnerTable'.
Each row represents a CFS capable feature within the
context of the combination of scope type and scope value
in the system. CfsPendingConfOwnerEntry .1.3.6.1.4.1.9.9.433.1.1.2.1 |
cfsPendingConfOwnerScopeTypeThis indicates the type of the cfsPendingConfOwnerScopeVal. CiscoCFSScopeType .1.3.6.1.4.1.9.9.433.1.1.2.1.1 |
cfsPendingConfOwnerScopeValThe CFS scope value used with cfsPendingConfOwnerScopeType.
This indicates the scope of the feature within which
the 'Pending Configuration' for the feature exists. CiscoCFSScopeValue .1.3.6.1.4.1.9.9.433.1.1.2.1.2 |
cfsPendingConfOwnerAddrTypeThe type of address of the device in the fabric where the
'Pending Configuration' exists for the feature within this
scope.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.433.1.1.2.1.3 |
cfsPendingConfOwnerAddrThe address of the device in the fabric where the 'Pending
Configuration' exists for the feature within this scope.
The type of address of an instance of this object is
determined by the value of the corresponding instance of
cfsPendingConfOwnerAddrType.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.433.1.1.2.1.4 |
cfsPendingConfOwnerIDTypeThe value of this object indicates the type of the value
of the corresponding instance of 'cfsPendingConfOwnerID':
'other' - indicates that the value of
'cfsPendingConfOwnerID' is
other than any of the enumerations
defined
'snmpCommunityName' - indicates that the value of
'cfsPendingConfOwnerID' is
'snmpCommunityName' of SNMPv1/
SNMPv2c
'snmpv3SecurityName' - indicate that the value of
'cfsPendingConfOwnerID' is
'securityName' of SNMPv3 user
'cliLoginName' - indicates that the value of
'cfsPendingConfOwnerID' is
CLI 'User Login Name' of CLI userro Bits .1.3.6.1.4.1.9.9.433.1.1.2.1.5 |
cfsPendingConfOwnerIDA human readable string representing the identity of the
owner of the 'Pending Configuration' that exists in the
device represented by the values of corresponding instance
of cfsPendingConfOwnerAddrType and cfsPendingConfOwnerAddr.
The value of the corresponding instance of
cfsPendingConfOwnerIDType indicates the type of the value
of this object.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.433.1.1.2.1.6 |
cfsMergeStatusTableThis table provides status of the 'Fabric Merge' on
the CFS capable features within the context of a
scope.
This table will have entries only for those features
for which CFS fabric distribution is enabled and
'Fabric Merge' is supported. SEQUENCE OF CfsMergeStatusEntry .1.3.6.1.4.1.9.9.433.1.1.3 |
cfsMergeStatusEntryA conceptual row in the cfsMergeStatusTable.
Each row represents a CFS capable feature within the
context of the combination of scope type and scope value
in the system. CfsMergeStatusEntry .1.3.6.1.4.1.9.9.433.1.1.3.1 |
cfsMergeStatusScopeTypeThis indicates the type of the cfsMergeStatusScopeVal. CiscoCFSScopeType .1.3.6.1.4.1.9.9.433.1.1.3.1.1 |
cfsMergeStatusScopeValThe CFS scope value used with cfsMergeStatusScopeType.
This indicates the scope of the feature within which
the 'Fabric Merge' for the feature has occurred. CiscoCFSScopeValue .1.3.6.1.4.1.9.9.433.1.1.3.1.2 |
cfsMergeStatusValueThe result of the last 'Fabric Merge' for the feature
within the context of the combination of
'cfsMergeStatusScopeType' and 'cfsMergeStatusScopeVal'
in the system:
'success' - Fabric Merge successfully
completed
'inProgress' - Fabric Merge in progress
'failure' - Fabric Merge failed
'waiting' - Waiting for existing Merge
conflict to be cleared
'other' - None of the other values of
this enumeration
The value of this object is 'inProgress' when the local
device is part of a fabric that is in the process of
merging with another fabric.
The value of this object is 'waiting' when this local
device is waiting for any existing 'Fabric Merge
Conflict' to be resolved before it initiates the new
instance of 'Fabric Merge'.ro Enumeration .1.3.6.1.4.1.9.9.433.1.1.3.1.3 |
cfsMergeMembersTableThis table provides a list of devices in the local/
remote fabric after 'Fabric Merge' on a per CFS capable
feature basis within the context of a scope.
This table will have entries only for those features
for which CFS fabric distribution is enabled and
'Fabric Merge' is supported. SEQUENCE OF CfsMergeMembersEntry .1.3.6.1.4.1.9.9.433.1.1.4 |
cfsMergeMembersEntryA conceptual row in the 'cfsMergeMembersTable'.
Each row represents a device in the local/remote
fabric supporting CFS capable feature within the
context of a scope in the system. CfsMergeMembersEntry .1.3.6.1.4.1.9.9.433.1.1.4.1 |
cfsMergeMemberAddrTypeThe type of the address of the device in the fabric
which has participated in the 'Fabric Merge' within
the context of a CFS feature and scope. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.433.1.1.4.1.1 |
cfsMergeMemberAddrThe address of the device in the fabric which has
participated in the 'Fabric Merge' within the context
of a CFS feature and scope.
The type of address of an instance of this object is
determined by the value of the corresponding instance
of cfsMergeMemberAddrType. InetAddress .1.3.6.1.4.1.9.9.433.1.1.4.1.2 |
cfsMergeMemberFabricTypeThe type of the fabric to which the device belongs to,
during/after the 'Fabric Merge'.
The fabric to which the local device is attached to is
referred to as 'local fabric'. The fabric which attempted
to merge with the local fabric is referred to as 'remote
fabric'.
When the value of the corresponding instance of
cfsMergeStatusValue is 'successful' or 'waiting', all
the devices will be in a single 'CFS fabric' and belong
to the 'local' fabric.
When the value of the corresponding instance of
cfsMergeStatusValue is 'failure' or 'inProgress', the
devices in the other fabric which attempted 'Fabric Merge'
are marked as 'remote'.ro Enumeration .1.3.6.1.4.1.9.9.433.1.1.4.1.3 |
cfsMergeMemberRoleThe role of the device during the 'Fabric Merge'.
In case of a successful fabric merge/stable fabric
only one device can be a 'master'. In case of a
fabric merge failure, there can be multiple 'master'
devices, corresponding to each of the fabric fragments.
All other devices which are not 'master' assume the role
of a 'peer'.
The algorithm for the selection of the 'Merge Master'
device within a stable fabric is platform specific.ro Enumeration .1.3.6.1.4.1.9.9.433.1.1.4.1.4 |
cfsPeersTableThis table provides list of devices in a stable fabric.
This table is populated with the entries only when the
CFS discovery cycle is successfully completed. SEQUENCE OF CfsPeersEntry .1.3.6.1.4.1.9.9.433.1.1.5 |
cfsPeersEntryA conceptual row in the 'cfsPeersTable'. Each row
represents a device in a stable fabric supporting
CFS capability. CfsPeersEntry .1.3.6.1.4.1.9.9.433.1.1.5.1 |
cfsPeerAddrTypeThe type of the address of the CFS capable device
in the fabric. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.433.1.1.5.1.1 |
cfsPeerAddrThe address of a CFS capable device in the fabric.
The type of address of an instance of this object is
determined by the value of the corresponding instance of
cfsPeerAddrType.ro InetAddress .1.3.6.1.4.1.9.9.433.1.1.5.1.2 |
cfsFeaturePeersTableThis table provides list of devices in a stable
fabric on per CFS capable feature basis. SEQUENCE OF CfsFeaturePeersEntry .1.3.6.1.4.1.9.9.433.1.1.6 |
cfsFeaturePeersEntryA conceptual row in the 'cfsMergeMembersTable'.
Each row represents a device in a stable fabric
supporting CFS capable feature within the context
of a scope in the system. CfsFeaturePeersEntry .1.3.6.1.4.1.9.9.433.1.1.6.1 |
cfsFeaturePeersScopeTypeThis indicates the type of the cfsFeaturePeersScopeVal. CiscoCFSScopeType .1.3.6.1.4.1.9.9.433.1.1.6.1.1 |
cfsFeaturePeersScopeValThe CFS scope value used with cfsFeaturePeersScopeType.
This indicates the scope of the feature within which
the device exists in the fabric. CiscoCFSScopeValue .1.3.6.1.4.1.9.9.433.1.1.6.1.2 |
cfsFeaturePeersAddrTypeThe type of the address of a peer device in the
fabric for a CFS capable feature within the context
of a scope. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.433.1.1.6.1.3 |
cfsFeaturePeersAddrThe address of a peer device in the fabric for a CFS
capable feature within the context of a scope.
The type of address of an instance of this object is
determined by the value of the corresponding instance of
cfsFeaturePeersAddrType.ro InetAddress .1.3.6.1.4.1.9.9.433.1.1.6.1.4 |
cfsFeatureOpExtTableThis table lists all the CFS capable features in the local
device and provides:
- the information of the result of the last CFS action
triggered on the CFS capable feature within the context
of a scope
- control flag to specify the source of 'configuration
view', within the context of a scope of the CFS capable
feature
The last action corresponds to the action triggered on a
CFS capable feature using the cfsFeatureOpAction of the
cfsFeatureOpTable. SEQUENCE OF CfsFeatureOpExtEntry .1.3.6.1.4.1.9.9.433.1.1.7 |
cfsFeatureOpExtEntryA conceptual row in the cfsFeatureOpExtTable. Each row
represents a CFS capable feature within the context of
the combination of scope type and scope value in the
system.
The combination of cfsFeatureOpExtScopeType and
cfsFeatureOpExtScopeVal forms a scope context within
which a CFS operation was performed on CFS capable
feature using the cfsFeatureOpScopeType and
cfsFeatureOpScopeVal of cfsFeatureOpTable. CfsFeatureOpExtEntry .1.3.6.1.4.1.9.9.433.1.1.7.1 |
cfsFeatureOpExtScopeTypeThis indicates the type of the cfsFeatureOpExtScopeVal. CiscoCFSScopeType .1.3.6.1.4.1.9.9.433.1.1.7.1.1 |
cfsFeatureOpExtScopeValThe CFS feature scope value to be used with
cfsFeatureOpExtScopeType. CiscoCFSScopeValue .1.3.6.1.4.1.9.9.433.1.1.7.1.2 |
cfsFeatureOpExtLastActionThe last action performed on this feature within the
context of a scope. If no action has been triggered
for the feature since the last reboot of the system,
then retrieving the value of this object will return
'noop'.ro CiscoCFSAction .1.3.6.1.4.1.9.9.433.1.1.7.1.3 |
cfsFeatureOpExtLastActionResultThe result of the execution of the last action (represented
by the value of cfsFeatureOpExtLastAction) for the feature.ro CiscoCFSFeatureActionResult .1.3.6.1.4.1.9.9.433.1.1.7.1.4 |
cfsFeatureOpExtLastFailureReasonThe failure reason description for the failed execution
of last action performed on this feature.
If the corresponding instance of
cfsFeatureOpExtLastActionResult has the value
'actionFailed', then this object contains the reason
as to why it failed. Otherwise, the value of this
object is a zero-length string.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.433.1.1.7.1.5 |
cfsFeatureOpExtShowCfgOptionThis object provides a means for management
applications to either view the contents of 'Running
Configuration' or 'Pending Configuration'.
When the value of this object is 'runningConfig', all the
subsequent configuration retrieval for this feature within
the specified context of the scope will be from 'Running
Configuration' on the local device.
When the value of this object is 'pendingConfig', all the
subsequent configuration retrieval for this feature within
the specified context of the scope will be from 'Pending
Configuration' on the local device.
The value of this object is meaningful only when the value
of the corresponding instance of 'cfsFeatureOpStatus' is
'enabled'.
The agent is not required to retain the modified value of
this object across the agent restart.rw Enumeration .1.3.6.1.4.1.9.9.433.1.1.7.1.6 |
cfsFeatureOpExtLastActionTimeTime stamp of the last action performed. If no action
has been triggered for the feature (i.e cfsFeatureOpExtLastAction
equal to one '1') since the last reboot of the system, the value
zero will be returned.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.433.1.1.7.1.7 |
cfsNotifObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.433.1.2 |
cfsMergeFailFeatureNameA human readable string value uniquely identifying the
name of this feature for which the 'Merge Failure' occurred.ro SnmpAdminString .1.3.6.1.4.1.9.9.433.1.2.1 |
cfsMergeFailScopeTypeThe value of this object indicates the type of the value
of 'cfsMergeFailScopeVal'.ro CiscoCFSScopeType .1.3.6.1.4.1.9.9.433.1.2.2 |
cfsMergeFailScopeValThe value of this object indicates the scope of the
feature ('cfsMergeFailFeatureName') within which the
'Merge Failure' occurred.ro CiscoCFSScopeValue .1.3.6.1.4.1.9.9.433.1.2.3 |
cfsMergeFailReasonDescriptionThe failure reason description for the 'Merge Failure'ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.433.1.2.4 |
cfsDiscoveryObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.433.1.3 |
cfsStartPeersDiscoveryThis object specifies whether a discovery cycle
should be started by the CFS to discover all the
'peers' in the fabric.
When the value of this object is set to 'startDiscovery',
the discovery of the CFS capable devices in the fabric
is started by the CFS. On successful completion of the
discovery, the entries in the 'cfsPeersTable' will be
populated.
When the value of cfsPeersDiscoveryResult is
'inProgress', setting the value of this object to
'startDiscovery' results in an error.
No action is taken if this object is set to 'noOp'.
The value of this object when read is always 'noOp'.rw Enumeration .1.3.6.1.4.1.9.9.433.1.3.1 |
cfsPeersDiscoveryResultThis object represents the result of the last discovery
command issued by way of setting the value of
cfsStartPeersDiscovery to 'startDiscovery'.
When the CFS discovery was never initiated using the
cfsStartPeersDiscovery, the value of this object is
'notInitiated'.
When the value of this object is 'notInitiated', the
management station needs initiate the discovery cycle by
setting the value of cfsStartPeersDiscovery to
'startDiscovery'.
If the value of this object is 'successful', then the
cfsPeersTable is appropriately populated.ro Enumeration .1.3.6.1.4.1.9.9.433.1.3.2 |
cfsPeersDiscoveryFailureReasonThe failure reason description for the last failed CFS
peers discovery.
If the value of cfsPeersDiscoveryResult object has the
value 'failed', then the value of this object contains
the reason as to why it failed. Otherwise, the value
of this object is a zero-length string.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.433.1.3.3 |
cfsDistCtrlObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.433.1.4 |
cfsDistCtrlThe object to control CFS for distribution.
On setting the value of this object to 'enable', CFS will
be ready for distribution of the data across the fabric.
On setting the value of this object to 'disable', CFS will
disable its capability to distribute the data across the
fabric. The CFS continues to honour distribution requests
from the CFS capable features of the local device, with the
scope of the distribution limited only to the local device
and not fabric wide.
The value of the object when read, reflects the current
operating state of the CFS.rw Enumeration .1.3.6.1.4.1.9.9.433.1.4.1 |
cfsDistCtrlTableThe table to control CFS for distribution over IP. SEQUENCE OF CfsDistCtrlEntry .1.3.6.1.4.1.9.9.433.1.4.2 |
cfsDistCtrlEntryAn entry (conceptual row) in the cfsDistCtrlTable. Each row
represents a configuration set required to control CFS for
distribution over IP on each of the address families. CfsDistCtrlEntry .1.3.6.1.4.1.9.9.433.1.4.2.1 |
cfsDistCtrlAddrTypeThe type of multicast address to which the CFS distribution
is restricted. Only the entries corresponding to the 'ipv4'
and 'ipv6' internet address types exist in this table. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.433.1.4.2.1.1 |
cfsDistCtrlAddrThe multicast address domain to which the CFS distribution
is restricted.
The type of this address is determined by the instance
identifier value of the cfsDistCtrlAddrType.
There is a default multicast address for both IPv4 and IPv6
through which the Keep-alive messages are sent and received
to discover the CFS capable switches over IP. All switches
with similar multicast address form one CFS-over-IP fabric.
The default multicast address for IPv4 is 239.255.70.83 and
range supported is [239.255.0.0 - 239.255.255.255]
The default multicast address for IPv6 is ff13::7743:4653 and
the supported range is [ff13::0000:0000 - ff13::ffff:ffff]
The value of this object can only be modified when the
value of the corresponding instance of cfsDistCtrlAction is
'disable'.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.433.1.4.2.1.2 |
cfsDistCtrlActionThis object specifies the current operating
mode employed in CFS for distribution over the
corresponding type of Internet address.
By setting the value of this object to 'enable', CFS will
enable its capability to distribute the application data
across the fabric over the corresponding type of Internet
address.
By setting the value of this object to 'disable', CFS will
disable its capability to distribute the data across the
fabric over the corresponding type of Internet address.
Only one instance of this object can have the value of
'enable' among all the conceptual rows.rw Enumeration .1.3.6.1.4.1.9.9.433.1.4.2.1.3 |
ciscoCFSMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.433.2 |
ciscoCFSMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.433.2.1 |
ciscoCFSMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.433.2.2 |