ProLiant Servers (ML,DL,SL)
1836281 Members
1698 Online
110097 Solutions
New Discussion

[AMS] Unable to specify iLO credentials. SMAD start with 'proxy loop'

 
tdene
Occasional Contributor

[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

2 REPLIES 2
Rama2
HPE Pro

Re: [AMS] Unable to specify iLO credentials. SMAD start with 'proxy loop'

AMS acts as a bridge between the server’s operating system and iLO.
When AMS is installed, iLO can directly collect server health information, OS driver details, and performance data.
AMS has certain software requirements, such as a supported RHEL kernel, compatible iLO firmware, etc.

Recommended Steps to Address the Issue

Restart the smad service to clear any previous state:
sudo systemctl restart smad

Specify the iLO administrator credentials. The amscli set command provides a fallback option if the normal credential exchange process fails.
sudo amscli set -u <ilo_username> -p <ilo_password>
<ilo_username>: The username for a local iLO account.
<ilo_password>: The password for that iLO account.

Restart the amsd service and check the status to confirm the proxy loop error is gone.
sudo systemctl restart amsd
sudo systemctl status amsd



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
tdene
Occasional Contributor

Re: [AMS] Unable to specify iLO credentials. SMAD start with 'proxy loop'

Hello,

Thank you for your reply.
Exactly, when I try to run the `sudo amscli set -u <ilo_local_admin_username> -p <ilo_local_admin_password>` command, I get the following error message and no specific log.
I also tried with a specifically created system user, but the behavior is the same.

# systemctl stop smad
# systemctl start smad
# amscli set -u $ilo_local_admin_username-p $ilo_local_admin_password
Unable to send username and password. Check if SMAD service is running and waiting for amscli data
# journalctl -u smad
Sep 19 10:10:01 mysrv smad[1517]: [NOTICE]: Stopping worker...
Sep 19 10:10:01 mysrv systemd[1]: Stopping System Management Assistant daemon...
Sep 19 10:10:01 mysrv smad[1491]: [NOTICE]: Stopping daemon...
Sep 19 10:10:01 mysrv smad[2208]: [NOTICE]: Stopping worker...
Sep 19 10:10:01 mysrv smad[1517]: [NOTICE]: Close iLO Socket
Sep 19 10:10:01 mysrv smad[2208]: [NOTICE]: Close iLO Socket
Sep 19 10:10:01 mysrv smad[2208]: [NOTICE]: (size = 12 cmd = 8093 seq = 15153) errcode=0
Sep 19 10:10:02 mysrv smad[1491]: [INFO ]: Collecting child process: 1517
Sep 19 10:10:02 mysrv smad[1491]: [NOTICE]: Close AgentX Socket
Sep 19 10:10:02 mysrv smad[1491]: [NOTICE]: Stopped /sbin/smad
Sep 19 10:10:02 mysrv systemd[1]: smad.service: Deactivated successfully.
Sep 19 10:10:02 mysrv systemd[1]: Stopped System Management Assistant daemon.
Sep 19 10:10:02 mysrv systemd[1]: smad.service: Consumed 31.428s CPU time.
Sep 19 10:10:31 mysrv systemd[1]: Starting System Management Assistant daemon...
Sep 19 10:10:31 mysrv smad[3624453]: [NOTICE]: Started /sbin/smad
Sep 19 10:10:31 mysrv smad[3624453]: [NOTICE]: Log level is 6 (INFO )
Sep 19 10:10:31 mysrv smad[3624453]: iLO gen is 5
Sep 19 10:10:31 mysrv smad[3624453]: [NOTICE]: Init AgentX Socket in Regular Mode
Sep 19 10:10:31 mysrv smad[3624453]: [INFO ]: Completed the AgentX Socket Init
Sep 19 10:10:31 mysrv systemd[1]: Started System Management Assistant daemon.