CISCO-TPC-MIB
AI MIB Summary
The CISCO-TPC-MIB manages Cisco Fibre Channel storage targets to configure and monitor Third Party Copy (TPC) capabilities, specifically enabling SCSI Extended Copy (XCOPY) operations for direct data transfers between source and destination Logical Unit Numbers (LUNs) within a specified Virtual Storage Area Network (VSAN). Key monitored elements include TPC target port status, module and VSAN configuration parameters, and the operational state of XCOPY-capable interfaces.
The MIB module for Third Party Copy(TPC): Third Party Copy derives its name from the fact that there are three entities involved in the process of copying data either for backup operations or restore operations. The three entities:
- entity originating the copy commands
- data source for the copy
- data destination for the copy.
The entity originating the copy commands to perform the data transfer can use the SCSI Extended Copy (XCOPY).
The TPC feature exposes a disk target with Logical Unit Number(LUN) 0 that is capable of processing the SCSI Extended Copy Command (XCOPY) to transfer data from a specified source to a specified destination. On receiving the XCOPY command, the TPC target performs the actual data transfer from the data source to the data destination on behalf of the entity issuing the XCOPY command.
The MIB provides an interface to configure the TPC targets. The user specifies the module and the VSAN on which the TPC feature needs to be configured. Once the feature has been configured target ports are created on the specified module and VSAN that are XCOPY capable. Any application that can source a XCOPY command can use these targets to perform data movement.
Acronyms The following acronyms are used in this document:
XCOPY:
SCSI Extended Copy Command.
TPC:
Third Party Copy.
LUN:
Logical Unit Number.
VSAN:
Virtual Storage Area Network.
Main OID:
ciscoTpcMIB.1.3.6.1.4.1.9.9.460
23
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
23 total| Object Name |
|---|
ciscoTpcMIBThe MIB module for Third Party Copy(TPC):
Third Party Copy derives its name from the fact
that there are three entities involved in the
process of copying data either for backup operations
or restore operations. The three entities:
- entity originating the copy commands
- data source for the copy
- data destination for the copy.
The entity originating the copy commands to perform
the data transfer can use the SCSI Extended Copy
(XCOPY).
The TPC feature exposes a disk target with
Logical Unit Number(LUN) 0 that is capable of
processing the SCSI Extended Copy Command (XCOPY)
to transfer data from a specified source to a
specified destination. On receiving the XCOPY
command, the TPC target performs the actual data
transfer from the data source to the data
destination on behalf of the entity issuing the
XCOPY command.
The MIB provides an interface to configure the
TPC targets. The user specifies the module and
the VSAN on which the TPC feature needs to be
configured. Once the feature has been configured
target ports are created on the specified module
and VSAN that are XCOPY capable. Any application
that can source a XCOPY command can use these
targets to perform data movement.
Acronyms
The following acronyms are used in this document:
XCOPY:
SCSI Extended Copy Command.
TPC:
Third Party Copy.
LUN:
Logical Unit Number.
VSAN:
Virtual Storage Area Network. MODULE-IDENTITY .1.3.6.1.4.1.9.9.460 |
ciscoTpcNotification OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.460.0 |
ciscoTpcObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.460.1 |
ciscoTpcConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.460.1.1 |
ctpcModuleTableA table listing the modules on which TPC functionality
can be configured by the user. Each such module is
identified by ctpcModuleId.
The agent creates an entry in this table on
detecting a module that can support TPC
functionality. Similarly, it will remove the entry
when the TPC functionality cannot be supported on
this module any longer.
The entry in the ctpcVsanTable can only be created
on a module present in this table. SEQUENCE OF CtpcModuleEntry .1.3.6.1.4.1.9.9.460.1.1.1 |
ctpcModuleEntryA conceptual row in the ctpcModuleTable. Each row
represents a TPC capable module. CtpcModuleEntry .1.3.6.1.4.1.9.9.460.1.1.1.1 |
ctpcModuleIdThis object specifies the physical index of the
module on which TPC 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.460.1.1.1.1.1 |
ctpcVsanTableA table listing all the VSANs for which TPC
functionality has been configured by the user. The
user configures TPC functionality on a per VSAN basis
by specifying the module, identified by ctpcModuleId,
on which to configure TPC and the VSAN number.
An entry can be created in this table only if an
entry exists in ctpcModuleTable for this module.
If a management application attempts to create
a row in this table corresponding to a module that
does not exist in ctpcModuleTable table then the
agent would respond with an error-status set to
'inconsistentValue'.
Once an entry is created, even if this module no
longer exists in the ctpcModuleTable, still
this entry is not deleted. The entry can only be
deleted by setting ctpcVsanRowStatus to 'delete'. SEQUENCE OF CtpcVsanEntry .1.3.6.1.4.1.9.9.460.1.1.2 |
ctpcVsanEntryAn entry in the TPC VSAN table for each configured
VSAN on this module. CtpcVsanEntry .1.3.6.1.4.1.9.9.460.1.1.2.1 |
ctpcVsanRowStatusThis object controls and reflects the status of rows
in this table. When the agent successfully creates
the entry, this object is set to 'active' by the
agent.
Deleting an entry from this table, unconfigures the
TPC functionality on the module specified by the
corresponding instance index 'ctpcModuleId'
on the VSAN represented by the corresponding
instance index 'vsanIndex'
To delete an entry, set this object value to
'destroy'.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.460.1.1.2.1.1 |
ctpcTargetTableA list of all the TPC targets that are configured
on this module and on this VSAN. There can be more
than one TPC target in the same VSAN on a module.
The number of TPC targets is implementation specific.
Each TPC target has a unique node world-wide-name,
identified by ctpcTargetNodeName and a unique port
world-wide-name, identified by ctpcTargetPortName.
Each TPC target exposes a single LUN (LUN 0) that is
XCOPY capable and is only concerned with moving data
in its own VSAN.
Once an entry is created in ctpcVsanTable, one or
more entries are created in this table by agent.
Similarly the entries in this table are deleted
when the entry with the same ctpcModuleId and
vsanIndex is deleted from the ctpcVsanTable. SEQUENCE OF CtpcTargetEntry .1.3.6.1.4.1.9.9.460.1.1.3 |
ctpcTargetEntryAn entry in the TPC target table for each TPC target
in this VSAN on this module. CtpcTargetEntry .1.3.6.1.4.1.9.9.460.1.1.3.1 |
ctpcTargetIndexThe unique id number associated with the TPC target.
This id number is unique within the vsan in which
the TPC target is configured. Unsigned32 .1.3.6.1.4.1.9.9.460.1.1.3.1.1 |
ctpcTargetNodeNameThe TPC target's node world-wide-name.ro FcNameIdOrZero (CISCO-ST-TC) .1.3.6.1.4.1.9.9.460.1.1.3.1.2 |
ctpcTargetPortNameThe TPC target's port world-wide-name.ro FcNameIdOrZero (CISCO-ST-TC) .1.3.6.1.4.1.9.9.460.1.1.3.1.3 |
ctpcTargetStateThe current state of the TPC targetro TpcTargetState .1.3.6.1.4.1.9.9.460.1.1.3.1.4 |
ctpcTargetNumXcopiesThe total number of XCOPY commands processed by the
TPC target since the module on which this target has
been configured has been onlinero Counter32 UNITS "commands" .1.3.6.1.4.1.9.9.460.1.1.3.1.5 |
ctpcTargetMinXcopyThe smallest amount of data in Kilobytes transferred
by the TPC target in a single xcopy command since the
module on which this target has been configured has
been online.ro Gauge32 UNITS "Kilobytes" .1.3.6.1.4.1.9.9.460.1.1.3.1.6 |
ctpcTargetMaxXcopyThe largest amount of data in Kilobytes transferred
by the TPC target in a single xcopy command since the
module on which this target has been configured has
been online.ro Gauge32 UNITS "Kilobytes" .1.3.6.1.4.1.9.9.460.1.1.3.1.7 |
ctpcTargetAvgKbPerSecThe average kilobytes per second throughput of the
TPC target in processing the XCOPY commands.ro Gauge32 UNITS "Kilobytes/second" .1.3.6.1.4.1.9.9.460.1.1.3.1.8 |
ciscoTpcMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.460.2 |
ctpcMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.460.2.1 |
ctpcMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.460.2.2 |