VCM-OA communication down

[NNag1]

Hello,

I have an HPE c7000 Blade System with two HP VC FlexFabric-20/40 F8 Modules.

Issue: Every 9 days, the Virtual Connect Manager becomes unavailable for a few minutes.
In the Virtual Connect Log, the following notes appear:

• VCM-OA communication down

• Enclosure state NO_COMM: Enclosure is in no-comm state. Previous state: Enclosure state OK. Cause: Enclosure enc0 unable to communicate with OA.

After a few minutes, the state returns to OK, and I can access the Virtual Connect Manager with the message:

• VCM-OA communication up

What I’ve tried to resolve the issue:

1. Reseated the VC modules → The problem reoccurred.

2. Reseated the OA modules → The problem reoccurred.

3. Replaced both OA modules and the OA Tray with new ones → The problem reoccurred.

4. Replaced the VC modules with new ones → The problem reoccurred.

What else can I try to resolve this issue?

[Azr_geek]

Hi @NNag1,

Ensure you’re on the latest stable Virtual Connect firmware, or at least a version that includes a fix or improvement for the database save-related communication drops.

• VC Firmware 4.60 or higher had improvements related to stability during internal saves.

• Check the HPE Virtual Connect Release Notes for your current version to determine if this is a documented behavior or if it has been fixed in a newer release.

Make sure the Onboard Administrator firmware is also up to date and compatible with your VC firmware. Mismatches can lead to strange behavior even if both are individually on supported versions.

Use the HPE Virtual Connect Support Matrix to confirm compatibility: Support Matrix PDF 

Regards,
Azr_geek

[NNag1]

Hello, @Azr_geek,

The firmware is up to date. OA - 4.97, VC modules - 4.85.

Any other ideas?

[Azr_geek]

@NNag1 

Memory or Resource Leaks Leading to Crashes

• Cause: Over time, memory leaks or resource exhaustion could cause VCM to become unresponsive.

• Solution:

  • Monitor system resource usage (CPU, memory).

  • Check for firmware or software updates that address memory leaks.

  • Consider restarting VCM services more frequently as a temporary workaround.
    
    

    Known Firmware Bugs

    • Cause: There could be a known bug in the VCM firmware causing periodic crashes.

    • Solution:

      • Check HP/HPE support site for firmware release notes.

      • Upgrade to the latest stable firmware version.

      • Contact vendor support with your logs.