Device Configuration Status Codes

Device configuration status codes appear in exit status and command output for the tpconfig and the tpautoconf commands, and in system or debug logs. Programs that call tpconfig and tpautoconf, such as media and device management user interfaces and the vmoprcmd command, also present these codes.

0 Success
1 Cannot execute command, permission denied
2 The device_mappings file has invalid license info
3 Could not get hostname
7 Invalid SCSI port number for the robot
8 Invalid SCSI bus number for the robot
9 Invalid SCSI target for the robot
10 Invalid SCSI logical unit number for the robot
11 Invalid Usage
13 Failed reading drive or robot config file
14 Invalid drive index
15 Invalid robot number
16 A SCSI inquiry sent to the device has failed
17 This robot type does not support multiple media types
18 Invalid robot type
19 Invalid device path name
21 Robot number is already in use
22 Device path is already in use
24 Incomplete robot information
25 Robot drive number in use for this robot
27 Invalid drive type for the robot
28 Invalid robot drive number for the robot type
29 Drive index is in use by another drive
30 Robot number is in use by another robot
31 Robot number does not exist
33 Robot type must be controlled locally
34 Drive name is already in use by another drive
35 Drive name does not exist
36
37 Residence is not licensed for shared drive support
38 Current version does not support remote device host
39 Adding this drive would exceed the maximum allowed
40 Adding this device would exceed the maximum allowed
41 Cannot change terminal mode
42 Cannot create miscellaneous working repository
44 Cannot discover devices. See the Troubleshooting Guide for details.
48 RSM is not supported
49 global device database host name is invalid
51 No compatible device is registered at these SCSI coordinates
52 The device name is not valid, no device responded.
53 Shared Storage Option (SSO) is not licensed
55 Invalid NDMP hostname
56 Invalid NDMP username
57 Internal NDMP error
58 NDMP failed to verify host
59 NDMP is not installed on platform
60 Invalid NDMP password
61 NDMP host exists, use change option
62 NDMP host does not exist
63 NDMP request failed
64 Invalid NDMP device
65 NDMP robot exists, use change option
66 NDMP robot does not exist
67 Unable to connect to NDMP host verify hostname
68 Unable to process NDMP message
69 NDMP host not connected
70 Unable to create NDMP session
71 NDMP get_host_info failed
72 NDMP get_server_info failed
73 Unsupported NDMP version
74 NDMP authorization error, verify username/password
75 NDMP config_get_mover_type failed
76 NDMP config_get_connection_type failed
77 Unable to connect to the EMM server
78 The EMM server failed to process the request
79 Unable to allocate memory for this process
81 This is a drive path operation, use the -drpath option
82 Add Drive Name Rule request failed
83 Update Drive Name Rule request failed
84 Delete Drive Name Rule request failed
85 List Drive Name Rule request failed
86 Invalid Drive Name Rule
87 System Error
88 Invalid host
89 Drive name rule has exceeded its maximum length of 48 characters
90 Another device configuration is already in progress
91 The drive serial number already exists in the device database
92 VxSS access denied
93 Database Server is down
95 The specified Disk Array Host is not configured in NetBackup
96 The specified Disk Array Host is not configured in NetBackup
97 No valid license key for Disk Array configuration
98 Open Storage feature is not licensed
99 Credentials already exist
100 NetBackup Snapshot client not licensed
101 authorization error, verify username/password


Source : symantec.com

Please Select Embedded Mode To Show The Comment System.*

Previous Post Next Post