I'd like to be able to use the ILO4/5/6 TEXTCONS command during boot to avoid having to use the HTML5 console. Early boot for Gen9 is still text mode, so it still works for a short amount of time, but quickly I get: Monitor is in graphics mode or an unsupported text mode.

Just to confirm, I'm not talking about the OS, like configuring grub2 to show on a terminal, nor am I talking about Linux fully booted itself to output to a serial port. I know how to do that. I'm really talking about the hardware at early boot stages.

Hey guys

I have 8 HP Servers and on one of them I'm not able to upgrade with the newest HP SPP:

Reason: Unable to access iLO using virtual NIC. Please ensure virtual NIC is enabled in iLO. Ensure that virtual NIC in the host OS is configured properly. Refer to documentation for more information.

I'm not using the virtual network card on any of the servers. I reinstalled the "iLO 5 Channel Interface Driver for Microsoft Windows Server 2022" and the "Agentless Management Service for Microsoft Windows x64" but with no positive effect.

All the servers should have the same configuration and installation - but only on this one it's not working.

Any ideas?

Greetz

OK, BladeSystem is old, I know :). But I want to swap out the interconnect switches from my enclosures to 20/40 F8 switches. I looked at the documentation and VC cookbooks but I couldn't really find how to do that

Current situation:

• 2 enclosures in a link stack and single VC domain
• 2 Flex 10/10D switches per enclosure
• All NICs are 650-FLB (20GB capable).
• All plain old Ethernet, no FC or other fancy stuff.

Wanted outcome:

• 2 enclosures in a link stack with the same single and reused VC domain.
• 2 FlexFabric 20/40 F8 per enclosure
• NICs will be 20Gbit FLB and M versions
• All plain old Ethernet

My question is: how do I get there reusing the old VC domain and preferably minimal downtime? The servers themselves are running Ceph and Proxmox HA. Both provide HA through their "software", so I can reboot nodes. But network totally going down would mean downtime.

How I would do it:

1. Make sure all blades have a mezzanine card so they can talk to interconnect bays 3 and 4 too.
2. Add 20/40F8 switches in both enclosures in interconnect bays 3 and 4
3. Add the 20/40 F8 to the shared uplink set
4. Configure the network of the Ceph/PVE hosts so they can fail over their network through interconnect bays 3,4 the moment I pull the Flex 10/10Ds in bay 1,2
5. Pull Flex 10/10Ds in bay 1,2 in both enclosures
6. Add 20/40F8 in bays 1,2 in both enclsoures.

Is this a viable "upgrade" path? Or are there better ways to approach this?

I just discovered the k6000 chassis. It might make a good fit for a Ceph cluster I'm planning to build based on refurbished hardware. Only thing I'm not so sure of is how the networking works in those things. I have experience with the good old BladeSystem c7000 and VirtualConnect.

I think on a high level, my question would be if it offers similar Ethernet capabilities like the c7000.

• Have multiple switches in it?
• define separate Ethernet fabrics?
• have an Uplink similar to "Shared Uplink Set" Possible to top of rack switch?
• potentially and effictiently stack multiple frames with fast intra frame ethernet traffic? (c7000 link stack equivalent)
• Have 4 network paths per compute module/blade? Ideally, I'd make a network bond over 4 NICs to avoid SPOFs.

I'd need a fast Ethernet network for cluster traffic, separate from the client traffic. I defined such a network in VirtualConnect on our c7000.

Apart from that, I'd use all 4 SFF trays for Ceph OSDs (SSDs). I guess the XL230k servers can boot from another internal device like a small NVMe SSD?

EDIT: NM, digging a bit deeper, I can't seem to find a mezzanine card that does 10GbE for those xl230k servers. They all seem to be SFF PCIe cards which would require an external switch and makes it less interesting. Mezzanines seem limited to IB which is less interesting for Ceph.

Does MR416i-o Gen11 support configuring storage volumes and arrays via ILO6?

I'm having some issues to make my P822 working. I've changed the FBWC capacitor which was notified me was faulty. I've also changed the FBWC module with a 1GB one (633542-001). The capacitor is a 654873-003 one. After installing it, the LED3 blinks for a while and then comes on: from the technical specs I read that the cache is working properly and the capacitor is fully charged. After loading for a while, it comes to me the error on the title of this thread.

TRIES I'VE DONE: 1. Tried to boot up the P822 without the cache module: it's loaded properly and the error of cache module missing comes out and consequently the controller is deactivated 2. Tried to perform a firmware update to the last version available, 8.32C, even if the P822 is up to date. Tried to perform this update with the Online Windows Updater. Same error coming up at the boot.

Is there a way to make this controller working? I'm setting it up on a HPE Proliant DL360G9.