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.
Parsed from file CISCO-SANTAP-MIB.mib
Module: CISCO-SANTAP-MIB
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.
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.
Parsed from file CISCO-SANTAP-MIB.my.txt
Company: None
Module: CISCO-SANTAP-MIB
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.
cstServiceConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF CstServiceConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { ciscoSanTapMIBObjects 2 }
cstServiceConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF CstServiceConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "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." ::= { ciscoSanTapMIBObjects 2 }
Vendor: Cisco
Module: CISCO-SANTAP-MIB
[Automatically extracted from oidview.com]
cstServiceConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF CstServiceConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { ciscoSanTapMIBObjects 2 }
cstServiceConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF CstServiceConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { ciscoSanTapMIBObjects 2 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.9.9.463.1.2.1 | cstServiceConfigEntry | 4 | 4 | An entry containing information about a CVT configuration for the SanTap service. The 'cstModuleId' denotes the module on which t… |
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.9.9.463.1.1 | cstModuleTable | 1 | 2 | A table listing the modules on which SanTap service can be configured and CVT can be created by the user. The entry in the cstSer… |
1.3.6.1.4.1.9.9.463.1.3 | cstDVTConfigTable | 1 | 8 | This table provides information about the list of all DVTs created and configured in the system. A new entry creation in this tab… |