Need assistance with 5230 appliance and ACSLS SL8500 configuration

Question

Hi guys,I am trying to setup tapes drives on a 5230 Veritas appliance. The tapes drives are in a SL8500 which is controlled by an ACSLS server.I have edited the vm.conf file on the appliance to what I think is the correct config.When I try to inventory the robot I get error unable to initialize robot.Doing a robtest on the appliance I getacs_query_server() failedUnable to query server taco, ACS status = 54, STATUS_IPC_FAILURE Robotic test utility /usr/openv/volmgr/bin/acstestreturned abnormal exit status (1).Doing a acstest -rn 0 -r (ACSLS_SERVER) -s 30031I get connection refused.On the ACSLS server I have added the IP and server to the internet.addresses file and rebuilt the access config.What am I doing wrong/missing??

nicolai · Accepted Answer

Hi
From the process&nbsp;list, I can see you are missing&nbsp;acsssi process.
From a media server with ACSLS connection:
root 34406 1 0 Nov14 ? 00:00:34 /usr/openv/volmgr/bin/ltidroot 34412 1 0 Nov14 ? 00:00:48 vmdroot 34589 34406 0 Nov14 ? 00:00:08 acsdroot 34592 34406 0 Nov14 ? 00:00:14 avrdroot 34595 34589 0 Nov14 ? 00:00:01 acssel -s 13740root 34642 34589 0 Nov14 ? 00:01:01 acsssi 13741
Try the following in vm.conf
ACS_TCP_RPCSERVICEACS_CSI_HOSTPORT = {acsls_server_name}&nbsp;30031ACS_SSI_INET_PORT = {acsls server_name} 30031
Then ensure ALL acsls related process are stopped/killed. Then start Netbackup again.&nbsp;
Your appliance, is it multihomned e.g. does it have more than one network interface connected ?
PS: Yes, the update is missing the ACS_ prefix. Updated

marianne · Answer

Was ACSLS configured for firewall access?Nicolai&nbsp;has published this excellent blog:
http://www.mass.dk/netbackup-quick-hints/netbackup-and-the-acsls-firewall-feature-2/
You will see that vm.conf are somewhat different - e.g&nbsp;CSI_HOSTNAME and not&nbsp;ACS_CSI_HOSTNAME&nbsp;
Please perform the rpcinfo tests as well.
More about ACSLS over here:&nbsp;http://www.veritas.com/docs/000026984
Look for RPC comms (section 6) and interpreting and troubleshooting ACS error messages (section 7).
&nbsp;
&nbsp;
&nbsp;
&nbsp;

marianne · Answer

Please share Appliance vm.conf and device config:tpconfig -lIs there a firewall between Appliance and ACSLS?

marianne · Answer

I agree with Nicolai - those 3 vm.conf are the only really important ones.
ACS_SSI_HOSTNAME is only neccessary if comms with ACSLS is using an interface other than 'uname -a' output.&nbsp;
I would also add VERBOSE entry.After stopping NBU, check that ALL acs... processes have also stopped.
Restart rpc on Appliance for good measure... then start NBU.&nbsp;Check if&nbsp;acsd, acsssi and assel&nbsp;are all running.&nbsp;
If still experiencing issues, check event.log in ACSLS as well as /var/log/messages on the Appliance.&nbsp;

nicolai · Answer

Yes - it smell of the firewall only allow traffic in one direction. But I could be wrong ...

tikkytakk · Answer

MM_SERVER_NAME = applianceACS_TCP_RPCSERVICEACS_CSI_HOSTPORT = ACSSERVER 30031ACS_SSI_INET_PORT = ACSSERVER 30031ACS_SSI_HOSTNAME = APPLIANCEACS_SSI_SOCKET = ACSSERVER 30031ACS_CSI_HOSTNAME = ACSSERVERtpconfig -lDevice Robot Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Robot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Device&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SecondType&nbsp;&nbsp;&nbsp;&nbsp; Num Index&nbsp; Type DrNum Status&nbsp; Comment&nbsp;&nbsp;&nbsp; Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Path&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Device Pathrobot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; ACS&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ACSLSGSU&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 0 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HP.ULTRIUM5-SCSI.000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /dev/nst9&nbsp;&nbsp; ACS=0, LSM=0, PANEL=1, DRIVE=11&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 1 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive029_BAY35&nbsp; /dev/nst7&nbsp;&nbsp; ACS=0, LSM=1, PANEL=1, DRIVE=7&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 2 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive026_BAY59&nbsp; /dev/nst11&nbsp; ACS=0, LSM=0, PANEL=1, DRIVE=5&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 3 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; T1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive031_BAY63&nbsp; /dev/nst6&nbsp;&nbsp; ACS=0, LSM=0, PANEL=1, DRIVE=4&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 4 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HP.ULTRIUM5-SCSI.005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /dev/nst4&nbsp;&nbsp; ACS=0, LSM=0, PANEL=1, DRIVE=0&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 5 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive015_BAY57&nbsp; /dev/nst10&nbsp; ACS=0, LSM=0, PANEL=1, DRIVE=13&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 6 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive006_BAY40&nbsp; /dev/nst8&nbsp;&nbsp; ACS=0, LSM=1, PANEL=1, DRIVE=2&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 7 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive013_BAY34&nbsp; /dev/nst5&nbsp;&nbsp; ACS=0, LSM=1, PANEL=1, DRIVE=11&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 8 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive010_BAY48&nbsp; /dev/nst3&nbsp;&nbsp; ACS=0, LSM=1, PANEL=1, DRIVE=0&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 9 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive030_BAY31&nbsp; /dev/nst1&nbsp;&nbsp; ACS=0, LSM=2, PANEL=1, DRIVE=4&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp; 10 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive028_BAY55&nbsp; /dev/nst12&nbsp; ACS=0, LSM=0, PANEL=1, DRIVE=6&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp; 11 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive025_BAY51&nbsp; /dev/nst0&nbsp;&nbsp; ACS=0, LSM=0, PANEL=1, DRIVE=7&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp; 12 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive023_BAY44&nbsp; /dev/nst2&nbsp;&nbsp; ACS=0, LSM=1, PANEL=1, DRIVE=1&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp; 14 hcart2&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GSU_SL8500_LTO5_Drive008_BAY62&nbsp; /dev/nst13&nbsp; ACS=0, LSM=0, PANEL=1, DRIVE=8&nbsp;Yes there is a firewall&nbsp;between appliance and acsls but port 30031 and 1556 TCP have been opened and confirmed open.&nbsp;

Forum Discussion

Need assistance with 5230 appliance and ACSLS SL8500 configuration

11 Replies

Related Content

Steps to configure robot on Flex appliance

configure Flex Appliance 5250

Orphan images on appliance

Blat & NetBackup - Need assistance in configuration

Veritas Compliance Accelerator Configuration

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date