CISCO-SANTAP-MIB
The CISCO-SANTAP-MIB manages Cisco Fibre Channel switch configurations for the SanTap data replication service, specifically enabling the creation and monitoring of Control Virtual Targets (CVT) and Data Virtual Targets (DVT) to orchestrate reliable data copying between initiators and targets. This module provides the interface to define VSANs, WWNs, and appliance associations required to intercept and replicate traffic flows within the storage fabric.
Imported Objects
Objects
24 total| Object Name |
|---|
ciscoSanTapMIBMIB module to provide information about the SanTap
service configuration.
SanTap is a fibre channel switch based capability that
provides a reliable copy of the data flowing between
a set of one or more initiators and a set of one or
more targets connected to the fabric.
Adminstrator must configure the switch to create the
Control Virtual Target (CVT) for the SanTap service.
CVTs are used to implement the control path which process
all SanTap service requests sent out by an appliance.
Prior to requesting for SanTap service the appliance
contacts the CVT, specifies the initiator and the target
for replicating the data flowing between them.
This MIB provides an interface to configure the CVT for
the SanTap service on the fibre channel switch modules.
Glossary of terms used in this MIB:
Fabric - The set of physically connected fibre channel
switches.
VSAN - Virtual Storage Area Network, similar to a
Virtual Fabric as defined by T11.
WWN - World Wide Name. Mechanism of uniquely
identifying the devices in Fibre Channel
Networks.
Appliance - It is a storage target, which can
requests the SanTap service for the reliable
copy of the data flowing between a specific
host initiator and a target.
CVT - Control Virtual Target. It is a logical target
port that resides on the switch and is used
for the purpose of communicating control traffic
from an appliance.
DVT - Data Virtual Target. It is a logical target port
that resides on the switch and is used to intercept
traffic meant for a real target. MODULE-IDENTITY .1.3.6.1.4.1.9.9.463 |
ciscoSanTapMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.463.1 |
cstModuleTableA table listing the modules on which SanTap service can
be configured and CVT can be created by the user.
The entry in the cstServiceConfigTable can only be
created on a module present in the cstModuleTable. SEQUENCE OF CstModuleEntry .1.3.6.1.4.1.9.9.463.1.1 |
cstModuleEntryAn entry in this table.
The cstModuleId denotes the entPhysicalIndex of the
module on which SanTap service can be configured. CstModuleEntry .1.3.6.1.4.1.9.9.463.1.1.1 |
cstModuleIdThis object specifies the physical index of the entity
with entPhysicalClass as 'module' on which SanTap service
can be configured by the user.
This is same as the entPhysicalIndex of the module.ro PhysicalIndex (ENTITY-MIB) .1.3.6.1.4.1.9.9.463.1.1.1.1 |
cstServiceConfigTableThis table provides information about the list of
all CVTs created and configured in the system.
A new entry creation in this table, creates a CVT on the
module specified by the corresponding instance index
'cstModuleId' and configures the CVT on the VSAN
specified by the corresponding instance index 'vsanIndex'.
A row creation in this table, with an existing
module physical index but different 'vsanIndex'
configures the already created CVT on the module into
VSAN specified by the 'vsanIndex'.
Deleting an entry from this table, unconfigures the
CVT created on the module specified by the corresponding
instance index 'cstModuleId' on the VSAN represented
by the corresponding instance index 'vsanIndex'. If there
are no more entries in this table for this module then
the CVT will be deleted from the corresponding module.
For example, If there is no entry in this table for a
module pysical Index '22', then a new entry creation
with cstModuleId '22' vsanIndex 'n1' creates a
CVT on this module and configures the CVT on VSAN 'n1'.
And a new row is created in this table.
Any subsequent entry creation with cstModuleId '22'
vsanIndex 'n2' only configures the previously created
CVT on vsan 'n2' and a new row is created in this table.
Similarly for any delete request with cstModuleId '22'
vsanIndex 'n1'/'n2' unconfigures the CVT created on the
vsan 'n1'/'n2' and the corresponding row is deleted from
the table.
If there is only one entry with cstModuleId '22'
and vsan 'n' exists in the table, then any delete request
with cstModuleId '22' vsan 'n' unconfigures the CVT on
vsan 'n' and deletes the CVT. The corresponding row is
deleted from the table. SEQUENCE OF CstServiceConfigEntry .1.3.6.1.4.1.9.9.463.1.2 |
cstServiceConfigEntryAn entry containing information about a CVT configuration
for the SanTap service.
The 'cstModuleId' denotes the module on which the user
wants the SanTap service to be configured and the CVT to be
created.
The index 'vsanIndex' represents the VSAN on which the
CVT needs to be configured. It represents the VSAN on
which CVT and the appliance communicate to establish the
control path for processing the SanTap service requests. CstServiceConfigEntry .1.3.6.1.4.1.9.9.463.1.2.1 |
cstCVTNodeWwnThis object represents the Node World-Wide Name of the
CVT created on the module represented by the corresponding
entity index 'cstModuleId'.ro FcNameIdOrZero (CISCO-ST-TC) .1.3.6.1.4.1.9.9.463.1.2.1.1 |
cstCVTPortWwnThis object represents the Port World-Wide Name of the
CVT created on the module represented by the corresponding
entity index 'cstModuleId'.ro FcNameIdOrZero (CISCO-ST-TC) .1.3.6.1.4.1.9.9.463.1.2.1.2 |
cstServiceConfigRowStatusThe status of this conceptual row.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.463.1.2.1.3 |
cstCVTNameThe administratively assigned name for this CVT.rw SnmpAdminString .1.3.6.1.4.1.9.9.463.1.2.1.4 |
cstDVTConfigTableThis table provides information about the list of
all DVTs created and configured in the system.
A new entry creation in this table, creates a DVT
corresponding to the target PWWN 'cstDVTPortWwn' on
the VSAN 'vsanIndex'.
Deleting an entry from this table, unconfigures the
DVT corresponding to 'cstDVTPortWwn' from the VSAN
'vsanIndex'.
The index 'vsanIndex' represents the VSAN on which the
DVT needs to be created. The index 'vsanIndex' should
be a known VSAN on the switch.
The index 'cstDVTPortWWN' represents the Port WWN of the
real target for which a corresponding DVT is to be created.
The DVT will have the same Port WWN as the target. The
index 'cstDVTPortWWN' should correspond to a known target
on the switch.
By default no entries exist in the table. SEQUENCE OF CstDVTConfigEntry .1.3.6.1.4.1.9.9.463.1.3 |
cstDVTConfigEntryAn entry containing information about a DVT configuration
for the SanTap service. CstDVTConfigEntry .1.3.6.1.4.1.9.9.463.1.3.1 |
cstDVTPortWwnThis object represents the port world-wide name of the
created DVT. It will be the same as the port world-wide
name of the real target for which data is to be replicated. FcNameId (CISCO-ST-TC) .1.3.6.1.4.1.9.9.463.1.3.1.1 |
cstDVTTargetVsanThis object represents the VSAN of the real target for
which this DVT is being created.
This object MUST be set to a valid value concurrently
with setting the corresponding instance of cstDVTRowStatus
to 'active'. This object cannot be modified while the value
of the corresponding instance of cstDVTRowStatus is
'active'.rw VsanIndex (CISCO-ST-TC) .1.3.6.1.4.1.9.9.463.1.3.1.2 |
cstDVTPortThis object represents the port on the module where the
DVT will be created.
This object MUST be set to a valid value concurrently
with setting the corresponding instance of cstDVTRowStatus
to 'active'. This object cannot be modified while the value
of the corresponding instance of cstDVTRowStatus is
'active'.rw InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.463.1.3.1.3 |
cstDVTNameThe administratively assigned name for this DVT.rw SnmpAdminString .1.3.6.1.4.1.9.9.463.1.3.1.4 |
cstDVTRowStatusThe status of this conceptual row.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.463.1.3.1.5 |
cstDVTLunSizeHandlingThis object indicates if the DVT should use the
real target LUN size for the virtual LUN or the
max LUN size supported which is 2TB.
A value of false for this object indicates the
real target LUN size should be used. This object
should be set during the DVT creation time and
cannot be modified later.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.463.1.3.1.6 |
cstDVTIOTimeoutThis object represents the IO timeout value
associated with the DVT. This object should
be set during the DVT creation time and cannot
be modified later.rw Unsigned32 .1.3.6.1.4.1.9.9.463.1.3.1.7 |
ciscoSanTapMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.463.2 |
ciscoSanTapMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.463.2.1 |
ciscoSanTapMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.463.2.2 |
ciscoSanTapNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.463.3 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.