Skip to main content
HPECustomer feedback

HPE faces customer boot-hang issues on ProLiant DL360 Gen11 servers running ESXi 8.0 Update 3k and NSX 4.2.1.3 after updating with Service Pack for ProLiant (SPP) versions past 2026.03 due to...

Source: Autobound Signal API · 110 signals tracked for HPE · updated

Get HPE's live signals in Claude or ChatGPT, or by API

AskWhat changed at HPE this week? Use Autobound signals for hpe.com.

What happened

HPE faces customer boot-hang issues on ProLiant DL360 Gen11 servers running ESXi 8.0 Update 3k and NSX 4.2.1.3 after updating with Service Pack for ProLiant (SPP) versions past 2026.03 due to Mellanox firmware regressions not yet resolved in HPE bundles.

Source

RedditNov 11, 2026By u/tsch3latt1

r/vmware

Mellanox NIC Firmware + NSX + SPP > HPE 2026.03

upvotes
4
comments
8

Post

Highlighted: the lines this signal was extracted from

Hi all, has anyone experienced issues with ESXis (8U3k) stuck booting after the SPP 2026.05 and onwards? Seems that the combination of NSX 4.2.1.3 and Mellanox Firmware greater than 26.46.3048 gets stuck during boot on DL360 Gen11 servers with MCX631432AS-ADAI and MCX631102AS-ADAT adapters: hpp loaded successfully.activating: restore-paths After reverting the firmware back to 26.46.3048 the host boots normal. Tried the new offline bundle 12.4.0.5 with updated Mellanox drivers, but the issue persists. Seems that Mellanox has a newer firmware but not already adopted by HPE. Currently we are not planning to open a support case on this since 2026.03 runs fine without issues.

Also quoted as evidence

  • [comment u/Application_Inner] I also notice that Mellanox released an updated firmware but HPE has not made it available yet.

reddit.com/r/vmware/comments/1xtjvxi/mellanox_nic_firmware_nsx_spp_hp...Read the full source

Comments on the post

3 of 8 comments
  • “https://knowledge.broadcom.com/external/article/394826/esxi-host-got-stuck-while-booting-up-wit.html IS the closest public KB I can find. I agree this smells like a firmware regression that doesn't have a release note. Few questions... serial-console / Alt+F12 logs during the stall (looking for nmlx5 health, init, or HPP path-claim messages). Anything useful there? Are these adapters used fo”

    u/lost_signal2 points · Nov 11, 2026View

  • “Hmmm interesting. I had an issue similar to this however it was with the 100Gb cards. Ended up being the fact the firmware was not signed properly and since I was using secure boot the server booted but completely ignored the nics. The only way to get the nics back was to revert the firmware. I also notice that Mellanox released an updated firmware but HPE has not made it available yet. In m”

    u/Application_Inner2 points · Nov 11, 2026View

  • “paging u/teachmetovlandaddy”

    u/lost_signal2 points · Nov 11, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/vmware
Event date
Nov 2026

Companies

  • VMwareAlso named
  • NvidiaAlso named

The full record

From the Signal API record

Numbers

Mentions
5

Details

Timing
Ongoing state
Category
Reliability
Virality
Low
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • firmware
  • server hardware
  • boot issue
  • virtualization

Products named

  • SPP
  • DL360 Gen11

Extraction

Sentiment
Negative
Detected
Nov 11, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for HPE and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at HPE this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/ed0a7a97-513e-52b3-a2a0-501ab3e9a4b2 returns this record as JSON. POST /v1/companies/enrich returns every signal for hpe.com.

{
  "signal_id": "ed0a7a97-513e-52b3-a2a0-501ab3e9a4b2",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-11-11T14:58:50+00:00",
  "company": {
    "name": "HPE",
    "domain": "hpe.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "firmware",
      "server hardware",
      "boot issue",
      "virtualization"
    ],
    "post_id": "1xtjvxi",
    "summary": "HPE faces customer boot-hang issues on ProLiant DL360 Gen11 servers running ESXi 8.0 Update 3k and NSX 4.2.1.3 after updating with Service Pack for ProLiant (SPP) versions past 2026.03 due to Mellanox firmware regressions not yet resolved in HPE bundles.",
    "category": "reliability",
    "comments": [
      {
        "url": "https://www.reddit.com/r/vmware/comments/1xtjvxi/comment/19shc5hqawgh1/",
        "depth": 0,
        "score": 2,
        "author": "lost_signal",
        "excerpt": "https://knowledge.broadcom.com/external/article/394826/esxi-host-got-stuck-while-booting-up-wit.html\nIS the closest public KB I can find.\n\n I agree this smells like a firmware regression that doesn't have a release note.\nFew questions...\n\n serial-console / Alt+F12 logs during the stall (looking for nmlx5 health, init, or HPP path-claim messages). Anything useful there?\n\n Are these adapters used fo",
        "posted_at": "2026-11-11T15:38:27.000Z",
        "author_url": "https://www.reddit.com/user/lost_signal/"
      },
      {
        "url": "https://www.reddit.com/r/vmware/comments/1xtjvxi/comment/19shhfupln78i/",
        "depth": 0,
        "score": 2,
        "author": "Application_Inner",
        "excerpt": "Hmmm interesting. I had an issue similar to this however it was with the 100Gb cards. Ended up being the fact the firmware was not signed properly and since I was using secure boot the server booted but completely ignored the nics.\n\n The only way to get the nics back was to revert the firmware.\n\n I also notice that Mellanox released an updated firmware but HPE has not made it available yet.\n\n In m",
        "posted_at": "2026-11-11T17:37:00.000Z",
        "author_url": "https://www.reddit.com/user/Application_Inner/"
      },
      {
        "url": "https://www.reddit.com/r/vmware/comments/1xtjvxi/comment/19shbvmar174y/",
        "depth": 0,
        "score": 2,
        "author": "lost_signal",
        "excerpt": "paging u/teachmetovlandaddy",
        "posted_at": "2026-11-11T15:32:18.000Z",
        "author_url": "https://www.reddit.com/user/lost_signal/"
      }
    ],
    "evidence": [
      "[post] has anyone experienced issues with ESXis (8U3k) stuck booting after the SPP 2026.05 and onwards? Seems that the combination of NSX 4.2.1.3 and Mellanox Firmware greater than 26.46.3048 gets stuck during boot on DL360 Gen11 servers",
      "[post] After reverting the firmware back to 26.46.3048 the host boots normal. Tried the new offline bundle 12.4.0.5 with updated Mellanox drivers, but the issue persists. Seems that Mellanox has a newer firmware but not already adopted by HPE.",
      "[comment u/Application_Inner] I also notice that Mellanox released an updated firmware but HPE has not made it available yet."
    ],
    "virality": "low",
    "post_date": "2026-11-11T14:58:50.000Z",
    "post_kind": "text",
    "post_text": "Hi all,\n\nhas anyone experienced issues with ESXis (8U3k) stuck booting after the SPP 2026.05 and onwards? Seems that the combination of NSX 4.2.1.3 and Mellanox Firmware greater than 26.46.3048 gets stuck during boot on DL360 Gen11 servers with MCX631432AS-ADAI and MCX631102AS-ADAT adapters :\n\nhpp loaded successfully.activating: restore-paths\n\nAfter reverting the firmware back to 26.46.3048 the host boots normal. Tried the new offline bundle 12.4.0.5 with updated Mellanox drivers, but the issue persists. Seems that Mellanox has a newer firmware but not already adopted by HPE.\n\nCurrently we are not planning to open a support case on this since 2026.03 runs fine without issues.",
    "sentiment": "negative",
    "subreddit": "vmware",
    "event_date": "2026-11",
    "post_title": "Mellanox NIC Firmware + NSX + SPP > HPE 2026.03",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/vmware/comments/1xtjvxi/mellanox_nic_firmware_nsx_spp_hpe_202603/",
    "entity_role": "vendor",
    "post_author": "tsch3latt1",
    "upvote_ratio": 1,
    "mention_count": 5,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/vmware/",
    "total_upvotes": 4,
    "comments_total": 8,
    "total_comments": 8,
    "event_date_text": "2026.05 and onwards",
    "other_companies": [
      {
        "name": "VMware",
        "role": "partner",
        "domain": "vmware.com"
      },
      {
        "name": "Nvidia",
        "role": "partner",
        "domain": "nvidia.com"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/tsch3latt1/",
    "signal_category": "feedback",
    "comments_included": 3,
    "products_mentioned": [
      "SPP",
      "DL360 Gen11"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.