HPE iLO AlertMail-169: (INFO) iSCSI link/session is down

[Sapphire_11]

EVENT (12-Mar-2024 05:50): iSCSI link/session is down
ACTION: Check the iSCSI initiator driver status or iSCSI initiator/target configuration. If no problems are found, the iSCSI initiator driver may need need to be installed, or an iSCSI session may need to be configured on initiator and target system

Integrated Management Log Severity: INFORMATIONAL

The mail is continuing. Please give a suggestion. If there are no problems, then why are mails triggered?

[GM_M]

Hi Sapphire_11

Check the iSCSI initiator driver status and the iSCSI initiator/target connection. If no connection problems are found, the iSCSI initiator driver might need to be installed or iSCSI virtual disk location might need to be configured

I hope this link might help you to resolve this issue.

Thanks and Regards,
Manoj.

[Sapphire_11]

Hello Manoj,

I'm checking in on the server when the iSCSI link is down and the iSCSI
initiator/target is blank, and when the iSCSI link is up and the iSCSI
initiator/target is connected, why is it happening? I'm pinging iSCSI from
my server, and there are not any packet drops, so why has it happened?
Please advise.

Thanks & regards,
*Girirajsinh Chudasama*
*Network Engineer* *| Sapphire Software Solutions*
*Office:* +91 79 484860 77/88 | *Mobile:* Personal info erased| *Email*:
itsupport@sapphiresolutions.net
*Web:* http://www.sapphiresolutions.net/ | *Go Social:* Facebook
<> | LinkedIn
<> | Twitter
<>
Sapphire Software Solutions, C/102, Ganesh Meridian, S.G. Highway.
Ahmedabad, Gujarat. India - 380060

"Provide a solution to ensure success"
----------------------------------------------------------------------------------------------------------------------
This e-mail is intended only for the named recipient(s) and may contain
information that is privileged, confidential and/or exempt from disclosure
under applicable law. No waiver of privilege, confidence or otherwise is
intended by virtue of communication via the internet. Any unauthorized use,
dissemination or copying is strictly prohibited. If you have received this
e-mail in error, or are not named as a recipient, please immediately notify
the sender and destroy all copies of this e-mail.

[thutchings]

Hello,

This type of information is going to be supplied using AMS running on top of the host OS. It is possible there may be some type of communication problem that could result in this behavior. For instance, there is a fix in the Windows version of AMS in rev 2.50 for this kind of problem:

Handled more running exceptions when AMS is querying iSCSI information.

https://internal.support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-e9a54d5b255e4c18&tab=revisionHistory

I would expect that this may be the same type of problem on your system, depending on what OS is in use.

Regards

[Rama2]

As mentioned in the previous message, it could be because of AMS. Try updating to the latest version and check the status. It might also be due to firmware and driver mismatch. These pieces of information can be validated through logs. If AMS didn't address the issue, log a ticket with HPE for further analysis.

[SprinkleJames]

We recently got this alarm in OneView on a cluster of four Synergy servers, running ESXi 7 and latest supported vLCM driver/firmware combo. Restarting the AMS service on each of the servers automatically cleared the alarms.

Opened a support case and uploaded logs. After analysis, they say: there's no recent port flapping, all downlinks are connected and up, and let us know if it happens again. Not super helpful.