Guide For ACSLS Library Software

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's
Guide for Au... Page 1 of 20

Document ID: 267306 http://support.veritas.com/docs/267306 E-Mail this document
to a colleague DOCUMENTATION: Supplemental Information to Media Manager System A
dministrator's Guide for Automated Cartridge System Library Software Details: Ma
nual: Media Manager System Administrator's Guide, Page: Appendix Modification Ty
pe: Addition Modification: Please review all sections before calling VERITAS sup
port to see if this document can help you resolve your issue. If not, please pla
ce a support call and a NetBackup (tm) Technical Support Engineer will respond w
ithin a timely manner. Quick overview of acsd and acsssi processes: Unlike the t
ldcd design for TLD robots that requires one robotic control host, acsd is a rob
otic daemon that runs on each media server with Automated Cartridge System (ACS)
drives attached. Robotic mount and dismount requests are sent from each media s
erver to the Automated Cartridge System Library Software (ACSLS) server via the
acsssi daemon which is an API call. Tape drive requests to read, write, position
, and rewind are done through the device paths on each media server, not through
the Automated Cartridge System Library Software (ACSLS) server. For a complete
overview of Automated Cartridge System (ACS) and NetBackup (tm), please refer th
e Automated Cartridge System (ACS) section in the Media Manager System Administr
ator's Guide. TABLE OF CONTENTS 1. LOGGING 1.1 LOG LOCATIONS 1.1.1 Event Logs 1.
2 ACS PROCESS TRACING 1.2.1 ACSSSI Tracing on the VERITAS NetBackup media server 1
.2.2 ACSSS Tracing on the Library Server 2 ACS LIBRARY SERVER (ACSLS) FUNCTIONS
AND COMMANDS 2.1 ACCESS CONTROL ON THE ACS LIBRARY SERVER (ACSLS) 2.2 ACSSA COMM
ANDS ON THE ACS LIBRARY SERVER 2.2.1 Log on to the ACSLS Server 2.2.2 Query the
Library Management Unit 2.2.3 Query the Cartridge Access Ports 2.2.4 Query silos
(Library Storage Modules) 2.2.5 Query Drives 2.2.6 Query Volumes 2.2.7 Command
to Start Request Processing 2.2.8 Vary on LSM 2.2.9 Logoff from ACSSA (ACSLS Ser
ver interface) 2.3 ACSLS TAPE CLEANING
file://H:\study\netbackup\Upload_site_done\done\New Folder\Information to Media
Manager System Admi...
7/6/2010

3 DEVICE CONFIGURATION FOR ACSLS CONTROLLED TAPE DRIVES 3.1 DEVICE CONFIGURATION
3.1.1 SSO Device Configuration for ACSLS 3.1.2 NON-SSO Device Configuration for
ACSLS 3.1.3 Initial configuration of StorageTek T9940A and T9940B tape drives i
n an ACSLS environment 4 ROBTEST FOR ACS LIBRARIES 4.1 INVOKING ROBTEST 4.2 ROBT
EST SYNTAX 4.2.1 Command to Obtain Drive Status 4.2.2 Command to Query Volumes 4
.2.3 Command to Mount a Volume 4.2.4 Command to Dismount a Volume 4.3 HOW TO DEF
INE ACSLS SCRATCH POOLS AND ADD VOLUMES USING ROBTEST 5 MEDIA 5.1 AVAILABLE MEDI
A SCRIPT 5.2 HOW TO SPECIFY WHICH MEDIA ACCESS PORT (MAP) TO USE FOR TAPE EJECTI
ON 6 COMMUNICATION 6.1 REMOTE PROCEDURE CALL 6.1.1 How to Start RPC on Different
Operating Systems 6.1.2 How to Verify that RPC is Running 6.1.3 How to Verify t
he ACSSS Program Registration 6.1.4 Basic snoop Output 7 COMMON ACS ERROR MESSAG
ES 7.1 ACS (2) UNAVAILABLE: INITIALIZATION FAILED: UNABLE TO INITIALIZE ROBOT 7.
2 ACS STATUS = 54, STATUS_IPC_FAILURE 7.3 ACS STATUS = 72, STATUS_PENDING 7.4 ST
ATUS_NI_FAILURE 7.4.1 ACS status = 104, STATUS_NI_FAILURE 7.4.2 ACS status = 105
, STATUS_NI_TIMEDOUT 1. LOGGING This section covers ACSLS log locations and ACS
process tracing. 1.1 LOG LOCATIONS 1.1.1 Event Logs Event log location on NetBac
kup media server: /usr/openv/volmgr/debug/acsssi/event.log Event log location on
ACS Library Server: /export/home/ACSSS/log/acsss_event.log (There is also an in
stall, configuration change, and statistics log in the same directory.) Typical
event log entries are cap operations, remote procedure call (RPC) and client ini
tialization, robot errors, NI failures, and drive status changes. 1.2 ACS PROCES
S TRACING 1.2.1 ACSSSI Tracing on the VERITAS NetBackup media server 1.2.1.1 To
turn on acsssi tracing on the NetBackup media server, send an SIGUSR1 signal to
7/6/2010

the acsssi process as follows: a. Ensure this directory exists:
/usr/openv/volmgr/debug/acsssi
b. Find the acsssi PID by running the command:
/usr/openv/volmgr/bin/vmps
c. Toggle on acsssi tracing:
kill -USR1 <pid of acsssi>
(This will start a trace.log in the /usr/openv/volmgr/debug/acsssi directory.) d
. To turn off acsssi tracing:
kill -USR1 <pid of acsssi>
Tracing can be turned on or off multiple times using the same kill command. NOTE
: To read the trace.log, it is necessary to use the StorageTek trace_decode. Ple
ase contact StorageTek for a copy and instructions for use. 1.2.2 ACSSS Tracing
on the Library Server 1.2.2.1 To turn on the Library Server ability to trace the
ONC RPC session and capture packets exchanged between the media server (SSI) an
d Library Server system (CSI): a. Run toggle with the option "on" located in /ex
port/home/ACSSS/diag/bin:
#./toggle on
b. To turn on CSI tracing, simply send a SIGUSR1 signal to the CSI process. This
can be accomplished by using the kill command as follows:
# kill -USR1 [CSI pid]
NOTE: It is necessary to first get the PID of the CSI using the ps command. Once
enabled, an acsssi_trace.log will be created in the /export/home/ACSSS/log dire
ctory. The log file contains a record of all packet activity between the media s
erver and the ACSLS server. Each packet is displayed with a time stamp, the dire
ction of the packet, the SSI client IP address, port, identifier, and a hex dump
of the contents of the packet. To read the trace.log, it is necessary to use th
e StorageTek trace_decode. Please contact StorageTek for a copy and instructions
for use. The decoder from StorageTek will output each packet with the time stam
p, the packet direction (to or from the ACSLS), the command type (i.e. start), t
he packet type (i.e. request, response), the number of bytes in the packet and t
he values of each of the fields in the CSI header and message header structures,
plus any command specific parameters. For each field in the structure, the byte
offset, size, and value (in hex and ASCII) are also given. To turn off tracing,
use the same method used to turn on tracing. Tracing can be toggled on/off mult
iple times using the same command. For Windows: Windows event logging is turned
on using the mini_el and the ACSSEL function shipped with the ACS product. The p
acket trace is controlled using the toggle_trace script. Both tools are in the
7/6/2010

Program Files\StorageTek\LibAttach\bin directory. NOTE: Do not leave tracing on
indefinitely because it may fill disk space over time. 2. ACS LIBRARY SERVER (AC
SLS) FUNCTIONS AND COMMANDS This section covers ACSLS functions and commands. 2.
1 ACCESS CONTROL ON THE ACS LIBRARY SERVER (ACSLS) Under ACSLS there exists the
ability to control command and volume access. ACSLS uses a set of client identif
ication files and a series of allow or disallow files to manage access control.
These control files reside on the ACSLS library server in the $ACS_HOME/data/ext
ernal/access_control directory. The internet.addresses file allows access contro
l of hosts. ACSLS will compare this file against the user_id field in the receiv
ed RPC request packet to determine whether to forward the packet on for further
processing. A non-zero return code for this operation will result in a STATUS_IN
VALID_OPTION response being sent back to the media server. Volume control can be
done through the set owner command in the cmd_proc utility or in the file owner
ship.assignment. A 'STATUS_INVALID_OPTION' status will return to commands which
are rejected due to access control violations. Volume access control applies to
the following commands:
dismount, lock, mount_readonly, set_clean, set_scratch, eject, mount, query_volu
me, set_owner, unlock
For further information on access control, please contact StorageTek. 2.2 ACSSA
COMMANDS ON THE ACS LIBRARY SERVER 2.2.1 Log on to the ACSLS Server
# su - acsss
At the prompt, enter:
$ cmd_proc -ql
Wait for the ACSSA> prompt. 2.2.2 Query the Library Management Unit
ACSSA> q lmu all 2004-01-28 14:24:10 ACS: 0 Mode: SCSI LMU Communicating Port 0,
0 Port State online Role LMU Status Master Status: Standby Status: CL Port Name - /dev/mchanger2 2.2.3 Query the Cartridge Access Ports
ACSSA> q cap all
7/6/2010

2004-01-28 14:25:30 CAP Status Identifier Priority Size State Mode Status 0, 0,0
0 10 online automatic available
2.2.4 Query silos (Library Storage Modules)
ACSSA> q lsm all 2004-01-28 14:26:22 Identifier State Dismount Enter Eject C/P 0
, 0 0/0
2.2.5 Query Drives
LSM Status Free Cell Audit Count C/P 0/0
Mount C/P 0/0 C/P 0/0
C/P online 0/0
36
ACSSA> q drive all 2004-01-28 14:27:34 Identifier State 0, 0, 0, 0 online 0, 0,
0, 1 online 0, 0, 0, 2 online 0, 0, 0, 3 online
2.2.6 Query Volumes
Drive Status Status Volume available available available available
Type DLT7000 DLT7000 9840 9840
ACSSA> q volume all 2004-01-28 15:58:36 Identifier Status 000002 home 000003 hom
e 000004 home 000005 home 000006 home 000008 home 000009 home <snip!> 2004-01-28
15:58:37 Identifier Status 000047 home 000048 home 000049 home 000050 home FX00
23 home
Volume Status Current Location 0, 0, 1, 0, 0 0, 0, 0, 2, 0 0, 0, 0, 3, 0 0, 0, 1
, 5, 0 0, 0, 1, 8, 1 0, 0, 0,23, 0 0, 0, 1,12, 1 Volume Status Current Location
0, 0, 1, 9, 0 0, 0, 1,10, 1 0, 0, 0, 7, 0 0, 0, 0, 4, 0 0, 0, 0, 0, 0
Type STK1R STK1R STK1R STK1R STK1R STK1R STK1R
Type STK1R STK1R STK1R STK1R SDLT
7/6/2010

2.2.7 Command to Start Request Processing
ACSSA> start Start: ACSLM Request Processing Started: Success.
2.2.8 Vary on LSM
ACSSA> vary lsm LSM identifier (acs,lsm): 0,0 LSM identifier (acs/lsm): State(di
agnostic/offline/online): online 2004-03-26 11:20:53 107 LSM 0,0: online ACSSA>
LSM 0,0 varied online
2.2.9 Logoff from ACSSA (ACSLS Server interface)
ACSSA> logoff
2.3 ACSLS TAPE CLEANING ACS robot types are self cleaning. Tape cleaning should
not be initiated by NetBackup. If a TapeAlert-based cleaning flag is set by LTID
or avrd for an ACS, TLH, or an LMF drive, the vmd/DA will not release the drive
s. To disable TapeAlert checking and eliminate "TapeAlert is not supported" mess
ages in the syslog, add the NO_TAPEALERT touch file. For UNIX: /usr/openv/volmgr
/database/NO_TAPEALERT For Windows: <install path>\volmgr\database\NO_TAPEALERT
The StorageTek library transport control unit tracks how much tape passes throug
h each transport and sends a message to ACSLS when a transport requires cleaning
. If auto-cleaning is enabled, ACSLS automatically mounts a cleaning cartridge o
n the transport. If all the cleaning cartridges have expired (MAX_USAGE), ACSLS
will post an error message 376N into the acsss_event log. If auto-cleaning is di
sabled, ACSLS logs a message in the event log and displays a message at the cmd_
proc when cleaning is required. This option is enabled or disabled using the acs
ss_config configuration utility. This utility will allow you to specify how the
cartridges are ordered for selection and queries. NOTE: You cannot use the acsss
_config configuration program to enable auto-cleaning for drives attached to a S
CSI connected library storage module (LSM). For more information regarding ACSLS
tape cleaning, please contact StorageTek. 3. DEVICE CONFIGURATION FOR ACSLS CON
TROLLED TAPE DRIVES This section covers device configuration. 3.1 DEVICE CONFIGU
RATION NOTE: All Automated Cartridge System (ACS) robots configured on a media s
erver must be configured with at least one drive, or the acsd daemon will exit,
putting all Automated Cartridge System Library Software (ACSLS) drives in Automa
tic Volume Recognition (AVR) mode.
7/6/2010

3.1.1 SSO Device Configuration for ACSLS During setup (in the Device Configurati
on Wizard), NetBackup will attempt to discover the tape drives available to it a
nd, for robot types where serialization is available, their positions within the
library. NetBackup does not yet obtain drive serial numbers from the ACS roboti
c library control interface, so manual configuration is required. The manual con
figuration cannot be avoided in a non-Shared Storage Option (non-SSO) environmen
t, where drives are not being shared. Using NetBackup 4.5 FP6, the user can sign
ificantly reduce the amount of manual configuration required by following these
steps in an SSO environment. 1. Run the device configuration wizard on just one
of the hosts where drives in an ACS-controlled library are attached. Let the dri
ves be added as standalone drives. 2. Add the ACS robot definition, and update e
ach drive to indicate its appropriate position in the ACS robot. (Make the drive
robotic, and add the ACS, LSM, Panel, and Drive information.) See the VERITAS M
edia Manager System Administration Guide, Configuring Storage Devices chapter, i
n the section "Co-relating Device Files to Physical Drives When Adding Drives."
3. Verify the drive paths, if this hasn't already been done in the previous step
, based on the documentation referenced above 4. Once the drive paths have been
verified on one host, re-run the device configuration wizard, and specify all ho
sts with ACS drives in the library to be scanned. The device configuration wizar
d will add the ACS robot definition and the drives to the remaining servers auto
matically, with correct device paths, assuming that the devices were successfull
y discovered, along with their serial numbers. By following the above steps, the
time savings can be significant. For example, if there are 20 drives shared on
30 hosts, the above configuration steps require just 20 paths to be manually con
figured, instead of 600 paths. 3.1.2 Non-SSO Device Configuration for ACSLS Duri
ng setup (in the Device Configuration Wizard), NetBackup will attempt to discove
r the tape drives available to it, and, for robot types where serialization is a
vailable, their positions within the library. Do not use the Device Configuratio
n Wizard. NetBackup does not obtain drive serial numbers from the ACS robotic li
brary control interface, so manual configuration is required. 3.1.3 Initial conf
iguration of StorageTek T9940A and T9940B tape drives in an ACSLS environment It
is advised to separate the two drive types within the NetBackup Media Managemen
t device configuration to alleviate density conflicts. This issue surfaces becau
se ACS treats the T9940A and T9940B drive media as identical, however, the T9940
B version writes at a higher density therefore the T9940A drive cannot read a ta
pe written by a T9940B drive. So, when trying to use both drives within a single
library, different densities must be used for each drive. The same issue will o
ccur with SDLT220 and SDLT320 drives in the same ACS-based library. Workaround:
7/6/2010

Add the ACS robot to the NetBackup device configuration according to the steps d
escribed within the NetBackup Media Manager Device Configuration Guide. Configur
e the STK 9940A drives as type hcart and configure the STK 9940B drives as type
hcart2. Then define a NetBackup storage unit for each density, hcart and hcart2.
Steps to inventory media for each density type: 1. In the /usr/openv/volmgr/vm.
conf file on the server where vmupdate is run, add "IGNORE_WRONG_MEDIA_TYPE" to
the end of the file 2. Run /usr/openv/volmgr/bin/vmupdate -rn <robot number> -rt
acs -acs_stk2p hcart -- All new media found will be configured as hcart 3. Next
, add the STK 9940B media to the robot 4. Finally, run /usr/openv/volmgr/bin/vmu
pdate -rn <robot number> -rt acs -acs_stk2p hcart2 -- All new media found will b
e configured as hcart2. When an inventory of ACS robotics is done, NetBackup wil
l receive a vendor media type back as well as the barcode. That vendor media typ
e is mapped to one of the NetBackup media types. The tag "IGNORE_WRONG_MEDIA_TYP
E" allows NetBackup to map a single ACS vendor media type to multiple NetBackup
media types. Disadvantages: 1. If for any reason, media is ejected from the libr
ary, verification is required when re-injecting media that it goes to the correc
t media type (hcart for 9940A, hcart2 for 9940B). 2. T9940B drives cannot be use
d to read the 9940A media; they have to be segregated. 4 ROBTEST FOR ACS LIBRARI
ES This section covers acstest (robtest) 4.1 INVOKING ROBTEST
# /usr/open/volmgr/bin/robtest
Configured robots with local control supporting test utilities:
ACS(0)
ACSLS host = taco
Robot Selection --------------1) ACS 0 2) none/quit Enter choice: 1 Robot select
ed: ACS(0) ACSLS host = taco, SSI socket = 13741 Invoking robotic test utility:
/usr/openv/volmgr/bin/acstest -r taco -s 13741 d /dev/rmt/1cbn 0,3,1,0Server 0 w
ith 24 free cells is in state "STATE_RUN" QUERY SERVER complete
7/6/2010

Enter acs commands (? returns help information)
4.2 ROBTEST SYNTAX
? To exit the utility, type q or Q. cancel <request_id> request defpool <pool> <
lwm> <hwm> <attrib> delpool <pool> pool dm <vol> [<drive>|<drive_id>] [f] (optio
nally forced) drstat <drive_id> eject <cap_id> <vol_list> volumes to the specifi
ed CAP enter <cap_id> specified CAP capstat [<cap_id>] varycap <cap_id> online|o
ffline given CAP setmode <cap_id> automatic|manual given CAP setpriority <cap_id
> <priority> the given CAP m <vol> [<drive>|<drive_id>] qmmi media information q
pool [<pool>] qreq [<request_id>] requests qscr [<pool>] volumes by pool qserver
qvol [<vol>] setscr <pool> ON|OFF <vol> [<vol>] attributes for volume range sta
rt Manager (request RUN state) types ACS media types
SCSI commands:
- Cancel server - Define scratch pool - Delete empty scratch - Dismount volume Print drive status - Eject a list of - Enter volumes in the - Print CAP status
- set the state of the - set the mode of the - set the priority of - Mount volum
e - Query actual mixed - Query pools - Query server - Query scratch - Query ACSL
S server - Query volumes - Set scratch - Start ACS Library - Print list of known
7/6/2010

Guide for ... Page 10 of 20
unload <drive>|<drive_id>
- Issue SCSI unload
where: <acs>=0-126, <lsm>=0-23, <cap>=0-2, <drive>=0-15, <priority>=0-127 <drive
_id> = [<acs>,<lsm>,<panel>,<drive>] <drive> = d1 if drive 1, d2 if drive 2, ...
, d15 if drive 15 <lwm> = scratch pool low water mark <hwm> = scratch pool high
water mark <cap_id> = <acs>,<lsm>,<cap> <vol_list> = <vol1>[:<vol2>:...:<vol42>]
4.2.1 Command to Obtain Drive Status
drstat Drive 1 information: ID (acs,lsm,panel,drv): drive type: volume ID: state
: status: Drive 2 information: ID (acs,lsm,panel,drv): drive type: volume ID: st
ate: status: Drive 3 information: ID (acs,lsm,panel,drv): drive type: volume ID:
state: status: Drive 4 information: ID (acs,lsm,panel,drv): drive type: volume
ID: state: status: DRIVE STATUS complete
4.2.2 Command to Query Volumes
0,0,0,0 DLT7000 <none> STATE_ONLINE STATUS_DRIVE_AVAILABLE 0,0,0,1 DLT7000 <none
> STATE_ONLINE STATUS_DRIVE_AVAILABLE 0,0,0,2 9840 <none> STATE_ONLINE STATUS_DR
IVE_AVAILABLE 0,0,0,3 9840 <none> STATE_ONLINE STATUS_DRIVE_AVAILABLE
qvol
7/6/2010

000002 STK1R home 000003 STK1R home 000004 STK1R home 000005 STK1R home 000006 S
TK1R home 000008 STK1R home QUERY VOLUME complete
4.2.3 Command to Mount a Volume
0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0,
1, 0, 0, 1, 1, 0,
0, 0 2, 0 3, 0 5, 0 8, 1 23, 0
m 000040 0,0,0,2 MOUNT complete
4.2.4 Command to Dismount a Volume
dm 000040 0,0,0,2 f DISMOUNT complete
4.3 HOW TO DEFINE ACSLS SCRATCH POOLS AND ADD VOLUMES USING ROBTEST Start the ro
btest utility: On UNIX:
# /usr/openv/volmgr/bin/robtest
On Windows:
<install_path>veritas\volmgr\bin\robtest.exe
Select the ACS robot. Enter the 'define pool' command as follows:
defpool 4 0 500 1 Scratch pool 4 has been defined
NOTE: DEFINE POOL completes robot inventories for ACS, where 4 is the pool numbe
r where 0 500 is the low and high water marks where 1 is overflow on (could be 0
for overflow off) Next, define ACSLS scratch volumes in this pool:
qpool 4 Pool ID 4 has 0 volumes QUERY POOL complete setscr 4 ON 000040 000044 00
0040 STATUS_SUCCESS 000041 STATUS_SUCCESS 000042 STATUS_SUCCESS
7/6/2010

000043 STATUS_SUCCESS 000044 STATUS_SUCCESS SET SCRATCH complete qpool 4 Pool ID
4 has 5 volumes QUERY POOL complete
Quit 'robtest' and perform a normal robot inventory with NetBackup. 5 MEDIA This
section covers "available_media" script output and tape ejection. 5.1 AVAILABLE
MEDIA SCRIPT The utility /usr/openv/netbackup/bin/goodies/available_media does
not report robot slot numbers for ACS libraries. This is not a bug. The informat
ion on slot location is managed by ACS and not by Media Manager. Below is a samp
le output from the available_media report, which can be generated by running the
following command: Windows: <install_path>\netbackup\bin\goodies\available_medi
a or UNIX: /usr/openv/netbackup/bin/goodies/available_media
media media robot robot robot side/ ret size status ID type type # slot face lev
el Kbytes --------------------------------------------------------NetBackup pool
NB0001 DLT ACS 0 0 2848 ACTIVE NB0002 DLT ACS 0 0 2848 ACTIVE ABC234 DLT ACS 0
AVAILABLE ABC345 DLT ACS 0 AVAILABLE
5.2 HOW TO SPECIFY WHICH MEDIA ACCESS PORT (MAP) TO USE FOR TAPE EJECTION In the
media server's /usr/openv/volmgr/vm.conf file, it is possible to specify the me
dia access port (MAP) to use when ejecting media to a particular ACS robot. If t
his entry is present, NetBackup (including the Vault extension) will eject to th
e specified MAP instead of the default 0,0,0 MAP. The vm.conf entry syntax:
MAP_ID = robot-num map-id
Example: If a user wants the ACS(0) robot to eject via its 0,0,1 MAP and the ACS
(1) robot to eject via its 0,1,0 MAP, the following vm.conf entries would be nec
essary on the media servers that use these robots:
MAP_ID = 0 0,0,1 MAP_ID = 1 0,1,0
7/6/2010

6. COMMUNICATION This section covers RPC and communication. 6.1 REMOTE PROCEDURE
CALL (RPC) NetBackup uses RPC to connect to the ACSLS server, and rpcbind is th
e service that converts RPC program numbers into universal addresses. It must be
running on the host to be able to make RPC calls on a server on that machine. I
f this service is not running this could cause the root file system to fill up.
NetBackup could send data to the links in /dev and since they cannot connect to
the drives the data will spool until the system runs out of disk space. Since th
e links in /dev have no size it will be difficult to determine what is using up
all the disk space on the file system. 6.1.1 How to start RPC on different opera
ting systems Starting RPC is best accomplished using the operating system vendor
startup scripts. The following are the ways of starting RPC on various operatin
g systems. a. Solaris i. Solaris (7,8,9)
# # # #
c. AIX
/etc/init.d/rpc start svcadm enable svc:/network/rpc/bind:default svcadm restart
svc:/network/rpc/bind:default /sbin/init.d/Rpcd start startsrc -s portmap /etc/
rc.d/init.d/portmap start /usr/sbin/portmap
ii. Solaris 10
b. HP-UX
# # #
d. Linux e. Tru/64 f. Windows Click Start | Settings | Control Panel | Administr
ative Tools | Services. Select Remote Procedure Call (RPC) and click Start. 6.1.
2 How to Verify that RPC is Running The following commands will verify that the
rpcbind is active and that the RPC service is functioning between the media serv
er and ACSLS Library Server. From a terminal window on the media server, issue t
he following command to ACSLS.
# rpcinfo program version netid address owner 100000 4 ticots hotdog.rpc superus
er 100000 3 ticots hotdog.rpc superuser 100000 4 ticotsord hotdog.rpc superuser
service rpcbind rpcbind rpcbind
7/6/2010

100000 3 superuser 100000 4 superuser 100000 3 superuser 100000 4 superuser 1000
00 3 superuser 100000 2 superuser 100000 4 superuser 100000 3 superuser 100000 2
superuser
ticotsord hotdog.rpc ticlts ticlts tcp tcp tcp udp udp udp hotdog.rpc hotdog.rpc
0.0.0.0.0.111 0.0.0.0.0.111 0.0.0.0.0.111 0.0.0.0.0.111 0.0.0.0.0.111 0.0.0.0.0
.111
rpcbind rpcbind rpcbind rpcbind rpcbind rpcbind rpcbind rpcbind rpcbind
If the service is not running, rpcinfo will report: "can't contact rpcbind: RPC:
rpcbind failure RPC: Failed ( unspecified error )" Examine the /export/home/ACS
SS/log/acsss_event.log for "RPC: Rpcbind failure." The error message should incl
ude an IP that it is trying to communicate with. Verify it is the correct IP add
ress. 6.1.3 How to Verify the ACSSS Program Registration
#rpcinfo -t {acsls_hostname} 300031 2 program 300031 version 2 ready and waiting
#rpcinfo -t {acsls_hostname} 300031 1 program 300031 version 1 ready and waitin
g
You should get a response from both programs, but you only need a response from
the version that you are using (2 = UDP or 3 = TCP). The NetBackup default for t
his communications service is UDP. 6.1.4 Basic snoop Output Basic snoop of a que
ry server sent automatically by initiating the robtest utility:
# snoop salid carter 1 0.00000 salad -> carter.min.veritas.com C GETPORT prog=30
0031 (?) vers=1 proto=UDP 2 0.00108 carter.min.veritas.com -> salad R GETPORT po
rt=1025 3 0.00056 salad -> carter.min.veritas.com XID=1066379121 PROG=300031 (?)
VERS=1 PROC=1000 4 0.00091 carter.min.veritas.com -> salad
PORTMAP PORTMAP RPC C RPC R
7/6/2010

(#3) XID=1066379121 Success 5 0.00459 carter.min.veritas.com -> salad RPC C XID=
1066114434 PROG=1073741824 (transient) VERS=1 PROC=1000 6 0.00031 salad -> carte
r.min.veritas.com RPC R (#5) XID=1066114434 Success 7 0.15656 carter.min.veritas
.com -> salad RPC C XID=1065841469 PROG=1073741824 (transient) VERS=1 PROC=1000
8 0.00029 salad -> carter.min.veritas.com RPC R (#7) XID=1065841469 Success
This trace shows that the portmapper and program registration was successful. Fo
r additional assistance with NetBackup options as they pertain to ACSLS, referen
ce the Media Manager System Administrator's Guide. 7 COMMON ACS ERROR MESSAGES T
his section covers common ACSLS error messages. 7.1 ACS(2) UNAVAILABLE: INITIALI
ZATION FAILED: UNABLE TO INITIALIZE ROBOT Resolution: Verify the IP address spec
ified for the robotic host is correct in LibAttach on the master server. 7.2 ACS
STATUS = 54, STATUS_IPC_FAILURE Robtest will show:
acs_query_server() failed Unable to query server taco, ACS status = 54, STATUS_I
PC_FAILURE Robotic test utility /usr/openv/volmgr/bin/acstest returned abnormal
exit status (1). STATUS_PENDING
Cause: local network interface is down. 7.3 ACS STATUS = 72, STATUS_PENDING Exam
ple 1: robtest will show:
acs_response() failed Unable to obtain Query Server acknowledge response, ACS st
atus = 72, STATUS_PENDING Robotic test utility /usr/openv/volmgr/bin/acstest ret
urned abnormal exit status (1).
7/6/2010

Media Server event.log will log:
02-05-04 13:49:18 SSI[0]: ONC RPC: csi_rpccall(): status:STATUS_NI_FAILURE; fail
ed: clntudp_create() RPC UDP client connection failed, RPC: Rpcbind failure Remo
te Internet address:10.82.56.67, Port: 0
Cause: ACSLS server network interface is down Example 2: Media server system log
:
Nov 15 11:18:06 hoehpt07 acsd[8807]: ACS(0) not been returned by Mount command s
equence status = 72, STATUS_PENDING Nov 15 11:28:06 hoehpt07 acsd[8807]: ACS(0)
not been returned by Mount command sequence status = 72, STATUS_PENDING
Event log from the ACSLS :
Response has 4434, ACS Response has 4434, ACS
2003-05-22 11:33:51 CSI[0]: 1022 N csi_net_send.c 1 474 ONC RPC: csi_net_send():
status:STATUS_NI_TIMEDOUT; failed: st_net_send() Cannot send message to NI:disc
arded, Network timeout Errno = 0 (none) Remote Internet address: 207.169.154.59,
Port: 53429 2003-05-22 11:33:51 CSI[0]: 1026 N csi_freeqmem.c 1 142 ONC RPC: cs
i_freeqmem(): status:STATUS_QUEUE_FAILURE; Dropping from Queue: Remote Internet
address: 207.169.154.59,Port: 53429 , ssi_identifier: 1, Protocol: 2, Connect ty
pe: 1 2003-05-22 11:33:51 ACSSA[0]: 1432 N sa_demux.c 1 273 Server System networ
k interface timeout.
Cause: The errors above indicate that NetBackup is able to reach the ACSLS serve
r with a status request, but the ACSLS server is unable to respond. By default,
the IP address sent to the ACSLS as part of the packet STATUS request is that of
the primary hostname of the media server, i.e. the hostname given by uname -a.
This error occurs when the ACSLS cannot resolve reverse name or is configured (v
ia routing) to only reach a secondary interface on the media server. If the issu
e is failure to do reserve name lookup, add the media server's IP to the domain
name
7/6/2010

service (DNS) reverse tables or to the ACSLS /etc/hosts file. If the ACSLS serve
r cannot route to the media server's hostname, override the default behavior by
using "ACS_SSI_HOSTNAME = <hostname>" in the /usr/openv/volmgr/vm.conf file wher
e the value for <hostname> is a hostname associated with an IP address the ACSLS
can reach on the media server. 7.4 STATUS_NI_FAILURE Explanation of message: ST
ATUS_NI_TIMEDOUT: The CSI (media server) has timed out waiting for a response fr
om a client (ACSLS). The actual "Waiting to obtain XXXXX ACS sequence YYY acknow
ledge response" indicates that the daemon has not received an acknowledgment fro
m the LibraryStation module for 30 seconds (which is a hard-coded limit) followi
ng a sent command. "Unable to obtain" means it has given up. The timeouts seen o
ccur after a 30 second delay, when no acknowledgment has been received. These ti
meout periods are determined by two tunable environment variables: CSI_RETRY_TIM
EOUT - The default for which is 3 seconds, not 2 as described in the Media Manag
ement manual. CSI_RETRY_TRIES - The default for this is 5 retries. Changes: Add
the following to /usr/openv/volmgr/vm.conf on the media server. CSI_RETRY_TIMEOU
T=30 CSI_RETRY_TRIES=10 or Change the OS environment variable CSI_RETRY_TIMEOUT
to 30 and CSI_RETRY_TRIES to 10. From bash/ksh prompt: #CSI_RETRY_TIMEOUT=30;exp
ort CSI_RETRY_TIMEOUT #CSI_RETRY_TRIES=10;export CSI_RETRY_TRIES Add to the NetB
ackup startup script for a permanent solution. Isolating the problem: a. Ensure
that the media server can successfully ping the ACS server and vice-versa b. Che
ck that ltid has started the acsd, acsssi and assel service daemons on the VERIT
AS media server by performing a bpps -a from /usr/openv/netbackup/bin or vmps fr
om /usr/openv/volmgr/bin/volmgr. If acsssi is not running, ensure that RPC is ru
nning c. Run snoop between the media server and ACS. Initiate robtest and check
that the query server, sent upon robtest initialization, is responded to by the
ACSLS server (reference basic snoop below)
7/6/2010

d. Verify the RPC communications between the media server and ACSLS host using t
he rpcinfo command. The rpcinfo -t <acs_host> 300031 1 h command checks RPC conn
ectivity, portmapper registration and that the ACSLS program (service) is availa
ble (reference 'How to start RPC' above). e. Check the event logs from the media
server and library server for errors (reference Logging above) f. Check the sys
log or event file for errors g. Enable tracing (reference Logging above) h. This
error can occur if the users.ALL.allow file on the ACSLS Library Server does no
t contain an entry for the requesting media server. This file is found on the AC
SLS server in the $ACS_HOME/data/external/access_control directory and is used f
or granting/denying library access. For example, entries of the users.ALL.allow
consult the ACSLS administrators guide. 7.4.1 ACS status=104, STATUS_NI_FAILURE
robtest will show:
acs_response() failed Unable to obtain Query Server acknowledge response, ACS st
atus = 104, STATUS_NI_FAILURE Robotic test utility /usr/openv/volmgr/bin/acstest
returned abnormal exit status (1).
acsssi event.log:
02-05-04 13:31:54 SSI[0]: ONC RPC: csi_rpccall(): status:STATUS_NI_FAILURE; fail
ed: clntudp_create() RPC UDP client connection failed, RPC: Program not register
ed Remote Internet address:10.82.56.67, Port: 0;
Cause: ACSLS is down or not responding 7.4.2 ACS status = 105, STATUS_NI_TIMEDOU
T Example of the message log:
Aug 26 17:06:57 sdhra1a acsd[15914]: ACS(0) Unable to obtain Query ACS sequence
3420 acknowledge response, ACS status = 105, STATUS_NI_TIMEDOUT Aug 26 17:06:57
sdhra1a acsd[5476]: DecodeDismount(): ACS (0) driveid 0,0,10,5, Actual status: U
nable to initialize robot Aug 26 17:06:57 sdhra1a acsd[5476]: ACS(0) going to DO
WN state, status: Unable to initialize robot Aug 26 17:07:15 sdhra1a acsd[15910]
: ACS(0) Waiting to obtain Query Drive sequence 3381 acknowledge response, ACS
7/6/2010

status = 72, STATUS_PENDING
Cause: The CSI (media server) has timed out waiting for a response from a client
(ACSLS). Windows NT and Win2000: STK LibAttach for Windows is required for ACSL
S use. The current version of STK LibAttach for Windows only allows for a single
instance of ACSLS, which means you can only enter one IP address for the Librar
y Server. Multiple ACS off the same Library Server is allowed. The VERITAS robot
definition must match the address specified in LibAttach. Related Documents: 24
6747: NetBackup DataCenter 4.5 Media Manager System Administrator's Guide for UN
IX http://support.veritas.com/docs/246747 264249: VERITAS NetBackup (tm) 5.0 Med
ia Manager System Administrator's Guide For UNIX http://support.veritas.com/docs
/264249 268103: VERITAS NetBackup (tm) 5.1 Media Manager System Administrators G
uide for UNIX http://support.veritas.com/docs/268103
Products Applied: NetBackup DataCenter 4.5, 4.5 (FP3), 4.5 (FP4), 4.5 (FP5), 4.5
(FP6), 4.5 (MP1), 4.5 (MP2), 4.5 (MP3), 4.5 (MP4), 4.5 (MP5), 4.5 (MP6) NetBack
up Enterprise Server 5.0, 5.0 MP1 Last Updated: December 03 2007 09:21 PM GMT Ex
pires on: 12-02-2008 Subscribe to receive critical updates about this document S
ubjects: NetBackup DataCenter Application: Informational NetBackup Enterprise Se
rver Application: Informational Languages: English (US) Operating Systems: HP-UX
11.0, 11.11
7/6/2010

Solaris 7.0 (32-bit), 8.0 (32-bit), 9.0 (32-bit) Symantec World Headquarters: 20
330 Stevens Creek Blvd. Cupertino, CA 95014 World Wide Web: http://www.symantec.
com/, Tech Support Web: http://entsupport.symantec.com/, E-Mail Support: http://
seer.entsupport.symantec.com/email_forms, FTP: ftp://ftp.entsupport.symantec.com
/ or ftp://ftp.entsupport.symantec.com/
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS
IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, E
ITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNES
S FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS
BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CO
NSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWA
RE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME S
TATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR
INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
7/6/2010

Guide For ACSLS Library Software

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Guide For ACSLS Library Software

Transféré par

Droits d'auteur :

Formats disponibles

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

Guide for Au... Page 1 of 20

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

DOCUMENTATION: Supplemental Information to Media Manager System Administrator's

Vous aimerez peut-être aussi