- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- [AMS] Unable to specify iLO credentials. SMAD sta...
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
yesterday
yesterday
[AMS] Unable to specify iLO credentials. SMAD start with 'proxy loop'
Hello,
I work with 'ProLiant DL360 Gen11' with 'RHEL 9.5'.
I want to use ASM to modify, for example, the Power Regulator Settings.
But when I try to specify iLO credentials, I have the following error.
# amscli set -u <ilo_username> -p <ilo_password>
Unable to send username and password. Check if SMAD service is running and waiting for amscli data
Amsd service seem is ok.
Smad service is 'running' but on log we have:
Aug 19 12:02:25 mysrv001 smad[564582]: [INFO ]: AgentX trap received
Aug 19 12:02:25 mysrv001 smad[564582]: [NOTICE]: AgentX trap MIB-II (.1.3.6.1.6.3.1.1.4.1.0:.1.3.6.1.6.3.1.1.5.1)
Aug 19 12:03:00 mysrv001 smad[564581]: [INFO ]: Got a new socket connection
Aug 19 12:03:00 mysrv001 smad[564953]: [NOTICE]: Init iLO Socket in Regular mode with CCB
Aug 19 12:03:00 mysrv001 smad[564953]: [INFO ]: BMC device is /dev/hpilo/d0ccb1
Aug 19 12:03:00 mysrv001 smad[564953]: [NOTICE]: iLO6: 1.66 (2024/12/13)
Aug 19 12:03:00 mysrv001 smad[564953]: [INFO ]: Reset iLO AgentX session
Aug 19 12:03:00 mysrv001 smad[564953]: [INFO ]: [CHIF] Clear out buffer
Aug 19 12:03:00 mysrv001 smad[564953]: [INFO ]: [CHIF] Close previous AgentX session if any
Aug 19 12:03:01 mysrv001 smad[564953]: [INFO ]: [CHIF] AgentX session is ready to use
Aug 19 12:03:01 mysrv001 smad[564953]: [INFO ]: Open iLO AgentX session in Regular Mode
Aug 19 12:03:01 mysrv001 smad[564953]: [NOTICE]: (size = 12 cmd = 8093 seq = 3) errcode=0
Aug 19 12:03:01 mysrv001 smad[564953]: [NOTICE]: 'AMS Linux AgentX sub-agent' connected to AgentX master in regular mode
Aug 19 12:03:01 mysrv001 smad[564953]: [NOTICE]: Session initialized with ID: 24
Aug 19 12:03:01 mysrv001 smad[564953]: [INFO ]: Completed the iLO Socket Init
Aug 19 12:03:01 mysrv001 smad[564953]: [NOTICE]: Start proxy loop
If I stop the amsd service and start it with 'amsd -f -L', I have
Can't find directory of RPM packagessystemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
systemstats_linux: unexpected header length in /proc/net/snmp. 237 != 224
Warning: Failed to connect to the agentx master agent (/var/agentx/bmc):
setUpHealthStatusArray: error bind socket failed
According to this RedHat solution, this is due to the Kernel version being too old.
Questions:
- Are there any software requirements for AMS ? (I've tested versions 4.0.0 and 4.2.0)
- What could be wrong with amscli set -u <ilo_username> -p <ilo_password> ?
thx