CISCO-TPC-MIB

File: CISCO-TPC-MIB.mib (15743 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF SNMPv2-TC
CISCO-ST-TC CISCO-VSAN-MIB CISCO-SMI
ENTITY-MIB

Imported symbols

MODULE-IDENTITY OBJECT-TYPE Unsigned32
Counter32 Gauge32 MODULE-COMPLIANCE
OBJECT-GROUP RowStatus TEXTUAL-CONVENTION
FcNameIdOrZero vsanIndex ciscoMgmt
PhysicalIndex

Defined Types

TpcTargetState  
Represents the state of the TPC target. 'active' - indicates that the TPC target is ready to process XCOPY requests. 'initializing' - indicates that the TPC target is not ready. 'error' - indicates that the TPC target was brought down due to error conditions.
TEXTUAL-CONVENTION    
  INTEGER active(1), initializing(2), error(3)  

CtpcModuleEntry  
SEQUENCE    
  ctpcModuleId PhysicalIndex

CtpcVsanEntry  
SEQUENCE    
  ctpcVsanRowStatus RowStatus

CtpcTargetEntry  
SEQUENCE    
  ctpcTargetIndex Unsigned32
  ctpcTargetNodeName FcNameIdOrZero
  ctpcTargetPortName FcNameIdOrZero
  ctpcTargetState TpcTargetState
  ctpcTargetNumXcopies Counter32
  ctpcTargetMinXcopy Gauge32
  ctpcTargetMaxXcopy Gauge32
  ctpcTargetAvgKbPerSec Gauge32

Defined Values

ciscoTpcMIB 1.3.6.1.4.1.9.9.460
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.
MODULE-IDENTITY    

ciscoTpcNotification 1.3.6.1.4.1.9.9.460.0
OBJECT IDENTIFIER    

ciscoTpcObjects 1.3.6.1.4.1.9.9.460.1
OBJECT IDENTIFIER    

ciscoTpcMIBConformance 1.3.6.1.4.1.9.9.460.2
OBJECT IDENTIFIER    

ciscoTpcConfig 1.3.6.1.4.1.9.9.460.1.1
OBJECT IDENTIFIER    

ctpcModuleTable 1.3.6.1.4.1.9.9.460.1.1.1
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    CtpcModuleEntry

ctpcModuleEntry 1.3.6.1.4.1.9.9.460.1.1.1.1
A conceptual row in the ctpcModuleTable. Each row represents a TPC capable module.
Status: current Access: not-accessible
OBJECT-TYPE    
  CtpcModuleEntry  

ctpcModuleId 1.3.6.1.4.1.9.9.460.1.1.1.1.1
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.
Status: current Access: read-only
OBJECT-TYPE    
  PhysicalIndex  

ctpcVsanTable 1.3.6.1.4.1.9.9.460.1.1.2
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'.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    CtpcVsanEntry

ctpcVsanEntry 1.3.6.1.4.1.9.9.460.1.1.2.1
An entry in the TPC VSAN table for each configured VSAN on this module.
Status: current Access: not-accessible
OBJECT-TYPE    
  CtpcVsanEntry  

ctpcVsanRowStatus 1.3.6.1.4.1.9.9.460.1.1.2.1.1
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'.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

ctpcTargetTable 1.3.6.1.4.1.9.9.460.1.1.3
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    CtpcTargetEntry

ctpcTargetEntry 1.3.6.1.4.1.9.9.460.1.1.3.1
An entry in the TPC target table for each TPC target in this VSAN on this module.
Status: current Access: not-accessible
OBJECT-TYPE    
  CtpcTargetEntry  

ctpcTargetIndex 1.3.6.1.4.1.9.9.460.1.1.3.1.1
The unique id number associated with the TPC target. This id number is unique within the vsan in which the TPC target is configured.
Status: current Access: not-accessible
OBJECT-TYPE    
  Unsigned32  

ctpcTargetNodeName 1.3.6.1.4.1.9.9.460.1.1.3.1.2
The TPC target's node world-wide-name.
Status: current Access: read-only
OBJECT-TYPE    
  FcNameIdOrZero  

ctpcTargetPortName 1.3.6.1.4.1.9.9.460.1.1.3.1.3
The TPC target's port world-wide-name.
Status: current Access: read-only
OBJECT-TYPE    
  FcNameIdOrZero  

ctpcTargetState 1.3.6.1.4.1.9.9.460.1.1.3.1.4
The current state of the TPC target
Status: current Access: read-only
OBJECT-TYPE    
  TpcTargetState  

ctpcTargetNumXcopies 1.3.6.1.4.1.9.9.460.1.1.3.1.5
The total number of XCOPY commands processed by the TPC target since the module on which this target has been configured has been online
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

ctpcTargetMinXcopy 1.3.6.1.4.1.9.9.460.1.1.3.1.6
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

ctpcTargetMaxXcopy 1.3.6.1.4.1.9.9.460.1.1.3.1.7
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.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

ctpcTargetAvgKbPerSec 1.3.6.1.4.1.9.9.460.1.1.3.1.8
The average kilobytes per second throughput of the TPC target in processing the XCOPY commands.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

ctpcMIBCompliances 1.3.6.1.4.1.9.9.460.2.1
OBJECT IDENTIFIER    

ctpcMIBGroups 1.3.6.1.4.1.9.9.460.2.2
OBJECT IDENTIFIER    

ctpcMIBCompliance 1.3.6.1.4.1.9.9.460.2.1.1
The compliance statement for entities which implement the CISCO-TPC-MIB mib.
Status: current Access: read-only
MODULE-COMPLIANCE    

ctpcVsanTargetGroup 1.3.6.1.4.1.9.9.460.2.2.1
A collection of objects for displaying and configuring the TPC target.
Status: current Access: read-only
OBJECT-GROUP