- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: ssh authentication with HPSIM WIN2003 server ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2006 08:54 AM
05-01-2006 08:54 AM
ssh authentication with HPSIM WIN2003 server to HPUX
Got HPSIM 5.0 loaded on WIN 2003 server
How do I authenticate SSH from HPSIM to the HPUX system?
I used to do mxagentconfig when HPSIM was on HPUX but I cannot get the same for the WIN box
Any help? Please?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2006 12:03 PM
05-01-2006 12:03 PM
Re: ssh authentication with HPSIM WIN2003 server to HPUX
You should be able to run it as before from a Command window.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2006 06:13 AM
05-02-2006 06:13 AM
Re: ssh authentication with HPSIM WIN2003 server to HPUX
Thanks, I did find the mxagentconfig.
I am running the mxagentconfig command and it is asking for passwd and then completed saying that it is successful.
I have also put out keys on the HPUX server. I can ssh login from the WIN to the HPUX without a passwd. I am doing this with a common account name on both the WIN/SIM system and the HPUX system.
However, when I execute a command from within HPSIM it errors out saying "Ssh Operation failed for node:
One question I do have, when it fails it states the CMS node name as the target but I am specifically choosing a HPUX system as the target. What gives?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2006 08:24 AM
05-02-2006 08:24 AM
Re: ssh authentication with HPSIM WIN2003 server to HPUX
What version of HPSIM - SP?, IIRC there were some recent changes regarding custom commands logging in.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2006 08:49 AM
05-02-2006 08:49 AM
Re: ssh authentication with HPSIM WIN2003 server to HPUX
Trying to do on the CMS as well but the ever so common error message that I cannot get away from;
"Failed to register as an agent to
Error: Configuration failed to complete due to the following exception: Ssh operation failed for node
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2006 05:02 AM
05-03-2006 05:02 AM
Re: ssh authentication with HPSIM WIN2003 server to HPUX
Still, I had been trying the mxagentconfig command on the managed node as well as the CMS for the other accounts. No dice. Going to have Administrator own all of the commands and get around the trust issue.
Doesn't answer the question but it is a working solution.