CISCO-TPC-MIB

All MIBs › CISCO-TPC-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2005-01-24

Category: Cisco Devices, Fibre Channel and Storage

Description: Manages third-party copy (TPC) operations for storage or transmit power control functions on Cisco devices.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-TPC-MIB?

CISCO-TPC-MIB is a Cisco-specific SNMP module for MDS-series Fibre Channel/storage switches, managing Third Party Copy (TPC/XCOPY) operations -- SCSI Extended Copy commands that let a third-party device orchestrate backup/restore data movement directly between a source and destination storage device without routing data through a host. It models the switch modules performing TPC, the VSANs (virtual SANs) over which copy operations run, and target device tables identifying copy-capable storage targets by node/port name and operational state. For monitoring, its target and VSAN tables reveal whether TPC-capable storage targets and their hosting VSANs are correctly configured and active, essential for diagnosing failed or stalled backup/restore jobs in a SAN environment, and it defines its own notifications for TPC-related events. It depends on the underlying Fibre Channel/VSAN and Entity MIB conventions on Cisco MDS switches rather than a generic IETF storage MIB. It is deployed on Cisco MDS 9000-series SAN directors/switches supporting serverless (LAN-free) backup architectures in enterprise storage networks. Engineers can download the CISCO-TPC-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-TPC-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco MDS series Fibre Channel/SAN switch

Monitoring Examples

A storage administrator investigating a failed backup job would check ctpcTargetTable/ctpcTargetEntry for the relevant ctpcTargetNodeName/ctpcTargetPortName, examining ctpcTargetState to confirm the copy-capable target is online and available for the TPC session. ctpcVsanTable/ctpcVsanRowStatus would be checked to confirm the VSAN carrying the copy operation is active, and ctpcModuleTable/ctpcModuleId identifies which switch module is executing the TPC operation, useful for isolating a hardware module suspected of causing copy failures.

What Can Be Monitored

TPC target device status
VSAN row/operational status
switch module executing TPC operations
copy-capable target node/port identity

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From CISCO-ST-TC

FcNameIdOrZero

From CISCO-VSAN-MIB

vsanIndex

OBJECT-TYPE

From ENTITY-MIB

PhysicalIndex

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using ctpcTargetNumXcopies OID:

Select a Cisco MDS series Fibre Channel/SAN switch (Third Party Copy) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type ctpcTargetNumXcopies into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The total number of XCOPY commands processed by the TPC target since the module on which this target has been configured has been online. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline (in commands), since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
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.
ciscoTpcNotification	1.3.6.1.4.1.9.9.460.0
ciscoTpcObjects	1.3.6.1.4.1.9.9.460.1
ciscoTpcConfig	1.3.6.1.4.1.9.9.460.1.1
ctpcModuleTable	1.3.6.1.4.1.9.9.460.1.1.1		not-accessible	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.
ctpcModuleEntry	1.3.6.1.4.1.9.9.460.1.1.1.1		not-accessible	A conceptual row in the ctpcModuleTable. Each row represents a TPC capable module.
PHY ctpcModuleId	1.3.6.1.4.1.9.9.460.1.1.1.1.1	PhysicalIndex	read-only	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.
ctpcVsanTable	1.3.6.1.4.1.9.9.460.1.1.2		not-accessible	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'.
ctpcVsanEntry	1.3.6.1.4.1.9.9.460.1.1.2.1		not-accessible	An entry in the TPC VSAN table for each configured VSAN on this module.
ROW ctpcVsanRowStatus	1.3.6.1.4.1.9.9.460.1.1.2.1.1	RowStatus	read-create	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'.
ctpcTargetTable	1.3.6.1.4.1.9.9.460.1.1.3		not-accessible	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.
ctpcTargetEntry	1.3.6.1.4.1.9.9.460.1.1.3.1		not-accessible	An entry in the TPC target table for each TPC target in this VSAN on this module.
U32 ctpcTargetIndex	1.3.6.1.4.1.9.9.460.1.1.3.1.1	Unsigned32	not-accessible	The unique id number associated with the TPC target. This id number is unique within the vsan in which the TPC target is configured.
FCN ctpcTargetNodeName	1.3.6.1.4.1.9.9.460.1.1.3.1.2	FcNameIdOrZero	read-only	The TPC target's node world-wide-name.
FCN ctpcTargetPortName	1.3.6.1.4.1.9.9.460.1.1.3.1.3	FcNameIdOrZero	read-only	The TPC target's port world-wide-name.
TPC ctpcTargetState	1.3.6.1.4.1.9.9.460.1.1.3.1.4	TpcTargetState	read-only	The current state of the TPC target
C32 ctpcTargetNumXcopiesEx	1.3.6.1.4.1.9.9.460.1.1.3.1.5	Counter32	read-only	The total number of XCOPY commands processed by the TPC target since the module on which this target has been configured has been online
G32 ctpcTargetMinXcopy	1.3.6.1.4.1.9.9.460.1.1.3.1.6	Gauge32	read-only	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.
G32 ctpcTargetMaxXcopy	1.3.6.1.4.1.9.9.460.1.1.3.1.7	Gauge32	read-only	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.
G32 ctpcTargetAvgKbPerSec	1.3.6.1.4.1.9.9.460.1.1.3.1.8	Gauge32	read-only	The average kilobytes per second throughput of the TPC target in processing the XCOPY commands.
ciscoTpcMIBConformance	1.3.6.1.4.1.9.9.460.2
ctpcMIBCompliances	1.3.6.1.4.1.9.9.460.2.1
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.
ctpcMIBGroups	1.3.6.1.4.1.9.9.460.2.2
ctpcVsanTargetGroup	1.3.6.1.4.1.9.9.460.2.2.1			A collection of objects for displaying and configuring the TPC target.

RFC description

Cisco Third Party Copy (TPC/XCOPY) MIB for managing data copying operations in storage networks involving three entities: copy originator, data source, and destination.

Start monitoring Cisco MDS series Fibre Channel/SAN switch (Third Party Copy) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-TPC-MIB