Title: Script to eject tape or check drive using CLI tools fails with "Failed to start a CLI session"
Date: Oct 07
Product & Version: All
Module & Version: All
OS Version: N/A
Application version: N/A
This document explains the error message above and provides the solution to prevent it.
When the command nvdeviceeject (or any other CLI commands that require a servername to be supplied) is used the error message:
"Failed to start a CLI session"
is displayed and the command fails.
Example (For Linux/Unix):
/usr/netvault/util/nvcheckdrive -servername UKWK1624 -drivename LTO
The servername value must be the name of the server that controls the drive. This is not always (and does not need to be) the server to which the drive is physically connected.
*** If the drivename/devicename contains spaces or special characters such as colons and dashes ( : and - ) then it will need to be enclosed in double quotes ( " ). Eg: "UKWK1624: 2-0.5.0 (IBM ULTRIUM TD3)".
Version franÃ§aise disponible ID
Deutsche Version verfÃ¼gbar ID