CISCO-TPC-MIB: View SNMP OID List / Download MIB

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.

A 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.

A conceptual row in the ctpcModuleTable. Each row represents a TPC capable module.

This 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.

A 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'.

An entry in the TPC VSAN table for each configured VSAN on this module.

This 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'.

A 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.

An entry in the TPC target table for each TPC target in this VSAN on this module.

The unique id number associated with the TPC target. This id number is unique within the vsan in which the TPC target is configured.

The TPC target's node world-wide-name.

The TPC target's port world-wide-name.

The current state of the TPC target

The total number of XCOPY commands processed by the TPC target since the module on which this target has been configured has been online

The 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.

The 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.

The average kilobytes per second throughput of the TPC target in processing the XCOPY commands.

The compliance statement for entities which implement the CISCO-TPC-MIB mib.

A collection of objects for displaying and configuring the TPC target.