Query: fw_oa_get_interconnectTrayStatus failed,

[Liyanz]

Please find the error information what can be the issue c7000 blade system

2024] (48052)[VcsuCore.cpp:620] : Failed to get Bay IP address, trying again
[Fri May 03 10:03:00 2024] (48052)[VcsuCore.cpp:633] : Get Bay IP call failed all retries
[Fri May 03 10:03:00 2024] (48052)[VcsuCore.cpp:1035] : fillEnetTrayinfo failed
[Fri May 03 10:03:00 2024] (48052)[VcsuCore.cpp:1071] : [**Confidential info erased**:2] Failed to get the Enclosure tray Info
[Fri May 03 10:03:01 2024] (48052)[OaWrap.cpp:1009] : OA Soap Call failed with error 1
[Fri May 03 10:03:01 2024] (48052)[VcsuCore.cpp:944] : fw_oa_get_interconnectTrayStatus failed, trying again
[Fri May 03 10:03:02 2024] (48052)[OaWrap.cpp:1009] : OA Soap Call failed with error 1
[Fri May 03 10:03:02 2024] (48052)[VcsuCore.cpp:944] : fw_oa_get_interconnectTrayStatus failed, trying again
[Fri May 03 10:03:04 2024] (48052)[OaWrap.cpp:1009] : OA Soap Call failed with error 1
[Fri May 03 10:03:04 2024] (48052)[VcsuCore.cpp:944] : fw_oa_get_interconnectTrayStatus failed, trying again
[Fri May 03 10:03:05 2024] (48052)[OaWrap.cpp:1009] : OA Soap Call failed with error 1
[Fri May 03 10:03:05 2024] (48052)[VcsuCore.cpp:944] : fw_oa_get_interconnectTrayStatus failed, trying again
[Fri May 03 10:03:06 2024] (48052)[OaWrap.cpp:1009] : OA Soap Call failed with error 1
[Fri May 03 10:03:06 2024] (48052)[VcsuCore.cpp:944] : fw_oa_get_interconnectTrayStatus failed, trying again
[Fri May 03 10:03:08 2024] (48052)[OaWrap.cpp:1009] : OA Soap Call failed with error 1
[Fri May 03 10:03:08 2024] (48052)[VcsuCore.cpp:944] : fw_oa_get_interconnectTrayStatus failed, trying again
[Fri May 03 10:03:10 2024] (48052)[OaWrap.cpp:1009] : OA Soap Call failed with error 1
[Fri May 03 10:03:10 2024] (48052)[VcsuCore.cpp:944] : fw_oa_get_interconnectTrayStatus failed, trying

[MV3]

Hello,

Could you provide more details on the issue at hand?
When did the problem initially arise? Have you attempted to update the firmware?
Have you attempted to switch over the OA and verify if the issue persists?
Have you noticed any synchronization errors in the VC Domain?
Could you try removing and reseating both the OA and OA tray?

Here's the procedure:

Begin by removing and reseating the Standby OA module, allowing it a minimum of 5-6 minutes to boot.
Perform a Soft Failover of the OA and wait for some time. You can observe the failover online.
Once the Management traffic is accessible from the OA, proceed to remove and reseat the then Primary OA module.

If you require further assistance, I strongly recommend opening a support case with HPE.

Please be aware: It is imperative to back up the OA and VC domain before conducting any physical actions.

Cheers...

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.