Flex - After VIO Password and IP change 'Request Access' fails
DanielJMartin 060001XHWG Visits (3507)
So you've updated your VIO server with a new hostname, IP address and changed the password. Now it would appear that after re-discovering the system your 'Request Access' just fails, like this -
There are a number of a reasons why this could be happening, from simply having the password wrong to the CAS agent not running. But in this case we will assume none of those are not a issue, so after a system discovery as below -
Then try to set the password it fails as per the first image, your see the error "The Request Access attempt was not successful on one or more target systems within the time allotted...". So there are 2 things that you can do on the VIO server where the problem is -
First login as root
And run the following command to unmanage the common agent from any details it has with the FSM.
BTC7861I Checking if the common agent is already registered...done
BTC7862E The common agent is already configured (it contains certificates).
BTC7872I Checking the common agent state...the common agent is running
BTC7875I Stopping the common agent...done
BTC7876I Reporting 'uninstallation' status...failed
BTC7852E Unable to update the status of the common agent.
The common agent is going to be reconfigured - force option specified
The common agent connection information:
name = localhost
port = 9510
jport = 9514
nport = 9515
wport = disabled
wsport = disabled
The agent manager information:
Common agent not managed by the agent manager
The common agent service information:
noinstall = false
nostart = false
BTC7878I Validating the resolved configuration of the common agent...done
BTC7880I Configuring the common agent...done
BTC7881I Installing the common agent service...done
BTC7882I Starting the common agent...done
Then you can confirm its all working and ready to connect from the padmin shell.
$ startsvc director_agent
cimlistener is already running.
tier1slp is already running.
Director Common Agent is already running.
After this you should be able to get access to the server and see that your discovery is a success, along with linking the OS to the Virtual server -