Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
Media Manager status code 181
Explanation: A caller requesting services from a robotic daemon is not authenticated or authorized. Or when two systems try to authenticate one another, a problem occurs.
Recommended Action:
See the NetBackup Security and Encryption Guide for information on Media Manager security.
Media Manager security is based on NetBackup authentication and authorization, but has extensions for handling SERVER entries in the Media Manager configuration file.
Examine the debug log files for a more detailed message on the authentication and authorization problem.
See "Setting Media Manager debug logging to a higher level" in the NetBackup Logging Reference Guide.
Determine whether authorization fails on vmd. Examine the debug log files for Media Manager status code 126 occurrences (not authorized to connect to vmd).
Correct the Media Manager security configuration by adjusting the authentication configuration, the AUTHORIZATION_REQUIRED entry, the ENABLE_ROBOT_AUTH entry, and the SERVER entries.
If an authentication problem (rather than a configuration issue) is suspected, do the following:
Check the
methods_allow.txt
files on the systems that have problems to ensure that authentication is enabled. The files are in the following locations:Windows:
install_path\NetBackup\var\auth
UNIX and Linux:
/usr/openv/var/auth
On the systems that have the authentication problem, remove the remote host that is not authenticated from the
methods_allow.txt
file and retry the operation.For example, if Host A and Host B have the problem, remove Host A from the file on Host B, and vice versa.
If the problem still exists, the error is caused by connection problems not related to authentication.
Add the removed names and retry the operation.