ACS SE 4.2- CLI access ONLY via serial?

js88888888 · ‎07-13-2009

Just want someone else to verify this.

Need to apply a patch to 4.2, so I run the autorun.bat file, etc, everything is working from a nice remotely-managed point of view UNTIL I have to stop CSAGENT. I can only access the CLI via serial connection? Is this by design? Why is the SSH command list so limited? Is the CLI via serial the only way to manage individual services (and access all those other useful commands)?

thanks!

Lucien Avramov · ‎07-13-2009

4.2 can have SSH :

http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_

for_windows/4.2/release/notes/ACS42_RN.html#wp56367

Now, as you said, the only thing SSH allows on CLI is : RDBMS synchronization on the ACS Appliance.

Jagdeep Gambhir · ‎07-14-2009

The ACS is a closed system and SSH does not allow access to the Operating System, it's only use is for RDBMS synchronization.

So CLI via serial is the only way to manage the services.

Regards,

~JG

Do rate helpful posts

js88888888 · ‎07-14-2009

Thanks for the verification. I was assuming since the slick upgrade packages were all self-contained and able to run from pretty much anywhere on the network, that serial access would not be required for one crucial but simple step. It just seems completely backwards and counter-intuitive for pretty much any process in IT. My 2 cents. thanks.