Forum Discussion

TikkyTakk's avatar
TikkyTakk
Level 2
8 years ago

Need assistance with 5230 appliance and ACSLS SL8500 configuration

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 w...
  • Nicolai's avatar
    Nicolai
    8 years ago

    Hi

    From the process list, I can see you are missing acsssi process.

    From a media server with ACSLS connection:

    root 34406 1 0 Nov14 ? 00:00:34 /usr/openv/volmgr/bin/ltid
    root 34412 1 0 Nov14 ? 00:00:48 vmd
    root 34589 34406 0 Nov14 ? 00:00:08 acsd
    root 34592 34406 0 Nov14 ? 00:00:14 avrd
    root 34595 34589 0 Nov14 ? 00:00:01 acssel -s 13740
    root 34642 34589 0 Nov14 ? 00:01:01 acsssi 13741

    Try the following in vm.conf

    ACS_TCP_RPCSERVICE
    ACS_CSI_HOSTPORT = {acsls_server_name} 30031
    ACS_SSI_INET_PORT = {acsls server_name} 30031

    Then ensure ALL acsls related process are stopped/killed. Then start Netbackup again. 

    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

  • TikkyTakk's avatar
    TikkyTakk
    8 years ago

    Ignore the above post as I was having issues logging in.

    With the help of Veritas support I was able to resolve this issue.

    As I had mentioned earlier the absence of the acsssi process was an indication something was wrong.

    When we restarted ltid and observed the acsssi debug long we saw the error message "unable to bind sicket to port 30031"

    This was preventing the acsd service from firing off the acsssi process.

    The issue lay within the vm.conf file.

    ACS_SSI_SOCKET = ACSLSSERVER 30031

    This socket has to be free and especially not configured to the firewall port.

    After removing this line everything worked fine.