topic Query: Regarding OA failover in Integrity Servers

Regarding OA failover

akash7 — Mon, 20 Apr 2026 04:34:13 GMT

Hi Team,

I have a Superdome 2 16s server and need to fail over the OA from active to standby. However, the configuration shows an error, such as the standby OA not being configured with a static IP and the link status not being active. Is this an issue, or can we perform the failover test without any problems?

OA-10605BA5C1BD> show OA status all

Onboard Administrator #1 Status:
Name: OA-10605BA5C1BD
Role: Active
UID: Off
Status: OK

Diagnostic Status:
Internal Data OK
Device Failure OK
Missing Device OK
Firmware Mismatch OK
Indicted OK

Onboard Administrator #2 Status:
Name: OA-10604CA5C147
Role: Standby
UID: Off
Status: OK

Diagnostic Status:
Internal Data OK
Device Failure OK
Missing Device OK
Firmware Mismatch OK

OA-10605BA5C1BD>

OA-10605BA5C1BD> SHOW OA NETWORK ALL

Onboard Administrator #1 Network Information:
Name: OA-10605BA5C1BD

- - - - - IPv4 Information - - - - -
DHCP: Disabled
IPv4 Address: 11.211.142.72
Netmask: 255.255.255.192
Gateway Address: 11.211.142.65

- - - - - IPv6 Information - - - - -
IPv6: Disabled
Static Address: Not Set
DHCPv6: Disabled
Router Advertisement: Disabled
Static IPv6 DNS 1: Not Set
Static IPv6 DNS 2: Not Set

- - - - - General Information - - - - -
Active DNS Addresses:
Primary: Not Set
Secondary: Not Set
Tertiary: Not Set

MAC Address: 11:60:4C:A5:C1:BD
Link Settings: Auto-Negotiation, 100 Mbps, Full Duplex
Link Status: Active
Enclosure IP Mode: Enabled

Onboard Administrator #2 Network Information:
Name: OA-10604CA5C147

- - - - - IPv4 Information - - - - -
DHCP: Enabled
IPv4 Address: 0.0.0.0
Netmask:
Gateway Address:

- - - - - IPv6 Information - - - - -
IPv6: Disabled
Static Address: Not Set
DHCPv6: Disabled
Router Advertisement: Disabled
Static IPv6 DNS 1: Not Set
Static IPv6 DNS 2: Not Set

- - - - - General Information - - - - -
Active DNS Addresses:
Primary: Not Set
Secondary: Not Set
Tertiary: Not Set

MAC Address: 11:60:4c:A5:C1:47
Link Settings: Auto-Negotiation, 100 Mbps, Full Duplex
Link Status: Not Active
Enclosure IP Mode: Enabled

OA-10604BA5C1BD>

Re: Regarding OA failover

akash7 — Thu, 09 Apr 2026 07:12:47 GMT

Can I get any reply from anyone?

My standby OA is showing Link Status: Not Active, and my enclosure IP mode is ON. Can I do a failover from active to standby safely?

Re: Regarding OA failover

Rakshitha_K — Fri, 10 Apr 2026 04:56:17 GMT

Hi @akash7 ,

On Superdome 2, “I2C Buses: Failed” on an IOX generally means something on the internal I2C management chain is stuck or not responding. Because I2C is a shared bus, a single faulty device can pull the bus low and make the entire shelf report failed. Since you replaced the IOX 9 chassis but reused the existing I/O cards, the most likely causes are:

- A faulty or marginal PCIe I/O card in IOX 9 that’s holding the I2C lines
- A card with incompatible/old firmware causing I2C timeouts
- A seating/connector issue or contamination in a slot
- Less likely (but possible): a bad fan/FRU on the shelf or a backplane issue in the replacement unit, though other sensors look OK

Recommended isolation steps

Please schedule a brief maintenance window and do the following in order:

1) Soft reset the IOX shelf
- From the Superdome 2 OA/management interface, perform a reset of IOX 9’s management controller or power-cycle the IOX 9 shelf if there is a supported option. Sometimes an I2C bus lock clears with a controller reset.
- If there’s no software reset option, you can perform a cold power cycle by removing power to the shelf (both PSUs) for at least 60 seconds, then reapply power. Do this only during a window and after confirming redundancy and impact.

2) Reseat external items
- Verify and reseat the Xfabric cables to IOX 9 and the Xfabric modules on both ends. Your links show OK, but it’s quick to eliminate a marginal connection.
- Check both IOX 9 PSUs and fan trays: reseat them. Ensure both fans spin up and the LEDs look normal.

3) Check for obvious slot issues
- Inspect each IOX 9 PCIe slot for bent pins, debris, or damage.
- Ensure cards are fully seated and locking mechanisms engaged.

4) Remove all I/O cards from IOX 9 and retest
- Power down or offline the IOX shelf per HPE procedures (to avoid hot-plug impact on the management bus).
- Remove all PCIe cards from IOX 9.
- Power up IOX 9 and check if “I2C Buses” changes from Failed to OK.
- If I2C now reports OK with no cards installed: add cards back one at a time (or in small batches), checking the I2C status after each addition to identify the offending card/slot.
- If I2C still reports Failed with all cards removed: the replacement IOX shelf itself may have a backplane or management FRU issue. Proceed to step 7 and contact HPE.

5) Verify firmware baselines
- Ensure the complex firmware bundle (system/Onboard Administrator/Xfabric/IOX) is at a supported and consistent level.
- Check each I/O card’s firmware and option ROM versions against the Superdome 2 supported matrix for your exact model and OS. Update any cards that are behind. Even though “Firmware Mismatch: OK” is shown for the shelf, individual adapter firmware mismatches can still cause I2C issues.

6) Identify the culprit card
- When the I2C fails after reinserting cards, the last card/slot you reintroduced is the likely culprit. Swap that card into a different known-good slot or a different IOX to confirm the fault follows the card.
- If the fault stays with the slot, inspect that slot for damage and consider the IOX backplane as a suspect.

7) Collect logs and engage HPE if needed
- From the OA/complex manager, collect a full support/diag bundle (OA logs, hardware inventory, event logs). On Superdome 2, HPE may ask for an “sx3000/complex” log pack and IOX logs.
- Note the exact IOX 9 FRU part numbers and firmware, plus the list of cards/slots and their firmware versions.
- Open a case with HPE if:
- I2C still fails with all cards removed, or
- The issue follows the replacement shelf, or
- You identify a specific card model repeatedly causing I2C failures even with current firmware.

Regards,
Rakshitha K

Query: Regarding OA failover

support_s — Tue, 12 May 2026 07:21:10 GMT

Hello,

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

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

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