β08-13-2014 11:57 AM
Dear All,
Master server - 7.1.0.4 (windows)
Media server - 6.5.6 (Solaris 10)
ACS server - Solaris 10
I have ACLS server which connected to storagetek library and 4 media server out of which 3 are windows media server and 1 solaris server. Master server is on Windows.
Suddenly backup stop writing through the solaris media server with error robotic library is down but backup is running fine from other 3 media servers.
When I tried Robtest from solaris media server it is giving error :obtest will probably return an error:
acs_response() failed
Unable to obtain Query Server Acknowledge response, ACS status = 72, Status pending
Robotic test utility /usr/openv/volmgr/bin/acstest
returned abnormal exit status (1)
and drives connected to this media server are in AVR mode.
I checked all symatec blogs and add acls server name in vm.conf file. But still I am receiving error. Enable / Disable acsss, reboot the media server, acls server.
ATTACHED ACSS event and trace log.
No idea what is causing this issue.
I need your help As quickly as possible......
Solved! Go to Solution.
β08-13-2014 12:43 PM
The errors in acsss_event log matches the errors seen in this TN: http://www.symantec.com/docs/TECH31526 for ACS Status 72.
Can ACSLS server communicate with media server IP address 57.33.0.232?
What does 'bpclntcmd -self' show on the media server?
How many NICs in this media server?
If more than one, does each NIC/IP have a dedicated hostname?
Which hostname/IP is supposed to communicate with ACSLS?
Have you created ACS_SSI_HOSTNAME entry in vm.conf for the interface that should be used for ACSLS comms?
If this IP address is on another subnet, does the 'defaultrouter' defined on ACSLS server provide a route to this IP address?
Can you media server and ACSLS server 'ping' one another?
Can you confirm that RPC is running on the media server?
β08-13-2014 12:43 PM
The errors in acsss_event log matches the errors seen in this TN: http://www.symantec.com/docs/TECH31526 for ACS Status 72.
Can ACSLS server communicate with media server IP address 57.33.0.232?
What does 'bpclntcmd -self' show on the media server?
How many NICs in this media server?
If more than one, does each NIC/IP have a dedicated hostname?
Which hostname/IP is supposed to communicate with ACSLS?
Have you created ACS_SSI_HOSTNAME entry in vm.conf for the interface that should be used for ACSLS comms?
If this IP address is on another subnet, does the 'defaultrouter' defined on ACSLS server provide a route to this IP address?
Can you media server and ACSLS server 'ping' one another?
Can you confirm that RPC is running on the media server?
β08-13-2014 01:41 PM
β08-13-2014 01:52 PM
Could be acsssi process is hanging (has exactly same issue today on Linux). Stop media manger on the media server. Verify with vmps and ensure *all* acsd acsssi acsssl processes are stopped. Re-start volume manger daemons - that will also start acssl,acssi and acsd. Verify with acstest that communication is restored.
β08-13-2014 02:39 PM
If your issue is very urgent please open a ticket with your robot vendor.
β08-13-2014 07:59 PM
The issue has been resolved after entring media server host name on vm.conf ACS_SSI_HOSTNAME = <media server host name>. It was by mistake set as ACS host name. There was no such entry before but as the trouble started someone made an entry on acs hostname but changing it to media server resolved the issue.
Thanks everyone for quick reply.
β08-13-2014 11:11 PM
Pleased you have it resolved.
I think Marianne made the suggestion before myself, so perhaps you could move the solution to her post ...
β08-16-2014 03:25 AM
Thanks Martin. I have moved the solution to Marianne but I want to give big thank to both of you :)