Have you pushed the ACL's to the agent?
Initially you would normally create an entry in the /usr/lib/rsc/users.local file for the user that would push the ACL's to the server.
Normally this is something like:
Once the ACL's have been pushed to the servers all other users/roles access should work.
Does the RSCD Agent version match your BSA application server version? Have you run an Update Server Properties Job against the target and refreshed it?
This is quite a common fault if the add server to console fails for some reason
The simplest method is to decommission the server and re-add, or re-deploy the configuration objects if you do not want to decomission.
1 of 1 people found this helpful
running a USP job w/ the 'register server objects' option checked should do it, assuming the appserver and agent are the same version or the appserver has the CO versions present in the COD that match the agent version.
Thanks for the prompt replies. Agent is at 8.3.02-332 and console is at 8.3.03.82. Ok I will give your suggestions a try since I have several hosts that have IP filters to install agents on today.
The update server job did the trick on AIX. Same successful results in RH Linux. Thanks