cisco-santap-mib.mib object
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2025 can import MIB file cisco-santap-mib and use it to monitor vendor specific OID's.
cisco-santap-mib file content
Object view of cisco-santap-mib:
| Scalar Object |
| cstModuleEntry |
.1.3.6.1.4.1.9.9.463.1.1.1 |
|
An entry in this table.
The cstModuleId denotes the entPhysicalIndex of the
module on which SanTap service can be configured.
|
| cstServiceConfigEntry |
.1.3.6.1.4.1.9.9.463.1.2.1 |
|
An 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.
|
| Tabular Object |
| cstModuleId |
.1.3.6.1.4.1.9.9.463.1.1.1.1 |
|
This 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.
|
| cstCVTNodeWwn |
.1.3.6.1.4.1.9.9.463.1.2.1.1 |
|
This object represents the Node World-Wide Name of the
CVT created on the module represented by the corresponding
entity index 'cstModuleId'.
|
| cstCVTPortWwn |
.1.3.6.1.4.1.9.9.463.1.2.1.2 |
|
This object represents the Port World-Wide Name of the
CVT created on the module represented by the corresponding
entity index 'cstModuleId'.
|
| cstServiceConfigRowStatus |
.1.3.6.1.4.1.9.9.463.1.2.1.3 |
|
The status of this conceptual row.
|
| Table |
| cstModuleTable |
.1.3.6.1.4.1.9.9.463.1.1 |
|
A 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.
|
| cstServiceConfigTable |
.1.3.6.1.4.1.9.9.463.1.2 |
|
This 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.
|
| Object Identifier |
| ciscoSanTapMIB |
.1.3.6.1.4.1.9.9.463 |
|
MIB 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.
|
| ciscoSanTapMIBObjects |
.1.3.6.1.4.1.9.9.463.1 |
| ciscoSanTapMIBConformance |
.1.3.6.1.4.1.9.9.463.2 |
| ciscoSanTapNotifications |
.1.3.6.1.4.1.9.9.463.3 |
| ciscoSanTapMIBCompliances |
.1.3.6.1.4.1.9.9.463.2.1 |
| ciscoSanTapMIBGroups |
.1.3.6.1.4.1.9.9.463.2.2 |
| Group |
| ciscoSanTapServiceConfigGroup |
.1.3.6.1.4.1.9.9.463.2.2.1 |
|
A Collection of objects to configure the CVT for SanTap
service.
|
