I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

I logged into ASMI/BMC/nameoftheday.  Under Firmware "BMC and server" it says fw1060.21-1-1060.2446.20250214a-prod (ML1060_093)

I logged into HMC, in view system firmware levels I see fw1060.21 (093)  Which basically looks like the above with just a bunch of stuff in the middle chopped out.  Basically, upgrading the firmware via the HMC updates BMC code also, right?  There's no additional process needed?  Someone said something to me and I wanted to make sure I'm not missing anything.

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

I logged into ASMI/BMC/nameoftheday.  Under Firmware "BMC and server" it says fw1060.21-1-1060.2446.20250214a-prod (ML1060_093)

I logged into HMC, in view system firmware levels I see fw1060.21 (093)  Which basically looks like the above with just a bunch of stuff in the middle chopped out.  Basically, upgrading the firmware via the HMC updates BMC code also, right?  There's no additional process needed?  Someone said something to me and I wanted to make sure I'm not missing anything.

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

I logged into ASMI/BMC/nameoftheday.  Under Firmware "BMC and server" it says fw1060.21-1-1060.2446.20250214a-prod (ML1060_093)

I logged into HMC, in view system firmware levels I see fw1060.21 (093)  Which basically looks like the above with just a bunch of stuff in the middle chopped out.  Basically, upgrading the firmware via the HMC updates BMC code also, right?  There's no additional process needed?  Someone said something to me and I wanted to make sure I'm not missing anything.

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

So basically this is the major concern, right?  If one leaves the ASMI password at the default, or if they assign it a weak password and it gets guessed, then someone can power off the server?  Much like if I leave my IBM i password for QSECOFR at QSECOFR someone could issue PWRDWNSYS *IMMED?  Or if I leave my AIX root user's password at a default value someone could issue the shutdown command?  But it's not like they get any backdoor access to any LPAR's data hosted on the system, right?

And, with the growing popularity of vHMC, taking that ASMI cable and plugging it into a dedicated port on the HMC is out of the question.  So you end up plugging it into a switch anyway, right?  So, sure, we can configure it on a vlan, just as long as I, or my team can get to it.  Our Power systems are either a few hours south or a few hours north of our office.

<snip>

Unfortunately ASMI also has a poor history of using weak passwords. If
I can access your ASMI from a PC on your public LAN, and guess the IBM
default, I can turn off your server without warning.

</snip>

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

So basically this is the major concern, right?  If one leaves the ASMI password at the default, or if they assign it a weak password and it gets guessed, then someone can power off the server?  Much like if I leave my IBM i password for QSECOFR at QSECOFR someone could issue PWRDWNSYS *IMMED?  Or if I leave my AIX root user's password at a default value someone could issue the shutdown command?  But it's not like they get any backdoor access to any LPAR's data hosted on the system, right?

And, with the growing popularity of vHMC, taking that ASMI cable and plugging it into a dedicated port on the HMC is out of the question.  So you end up plugging it into a switch anyway, right?  So, sure, we can configure it on a vlan, just as long as I, or my team can get to it.  Our Power systems are either a few hours south or a few hours north of our office.

<snip>

Unfortunately ASMI also has a poor history of using weak passwords. If
I can access your ASMI from a PC on your public LAN, and guess the IBM
default, I can turn off your server without warning.

</snip>

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

So basically this is the major concern, right?  If one leaves the ASMI password at the default, or if they assign it a weak password and it gets guessed, then someone can power off the server?  Much like if I leave my IBM i password for QSECOFR at QSECOFR someone could issue PWRDWNSYS *IMMED?  Or if I leave my AIX root user's password at a default value someone could issue the shutdown command?  But it's not like they get any backdoor access to any LPAR's data hosted on the system, right?

And, with the growing popularity of vHMC, taking that ASMI cable and plugging it into a dedicated port on the HMC is out of the question.  So you end up plugging it into a switch anyway, right?  So, sure, we can configure it on a vlan, just as long as I, or my team can get to it.  Our Power systems are either a few hours south or a few hours north of our office.

<snip>

Unfortunately ASMI also has a poor history of using weak passwords. If
I can access your ASMI from a PC on your public LAN, and guess the IBM
default, I can turn off your server without warning.

</snip>

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

So basically this is the major concern, right?  If one leaves the ASMI password at the default, or if they assign it a weak password and it gets guessed, then someone can power off the server?  Much like if I leave my IBM i password for QSECOFR at QSECOFR someone could issue PWRDWNSYS *IMMED?  Or if I leave my AIX root user's password at a default value someone could issue the shutdown command?  But it's not like they get any backdoor access to any LPAR's data hosted on the system, right?

And, with the growing popularity of vHMC, taking that ASMI cable and plugging it into a dedicated port on the HMC is out of the question.  So you end up plugging it into a switch anyway, right?  So, sure, we can configure it on a vlan, just as long as I, or my team can get to it.  Our Power systems are either a few hours south or a few hours north of our office.

<snip>

Unfortunately ASMI also has a poor history of using weak passwords. If
I can access your ASMI from a PC on your public LAN, and guess the IBM
default, I can turn off your server without warning.

</snip>

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

> It's bad, but shouldn't be any data access. Unexpected downtime and risk of inoperable hardware.

This is what you can easily accomplish if you have ASMI access from a corporate network and can read IBM documentation.

Don't forget that ASMI works on the same hardware as all your LPARs and nothing else, like a small Linux system. It has access to all data in RAM. Your LPARs don't write directly to disks, but write first to the RAM. If someone can hack into it, they can get access to all your LPARs and data. No, I never heard about such a case, and this is a theory. But separate your ASMI/BMC interfaces into a separate VLAN, where nobody has access except the HMC. Make the VLAN non-routable.

So basically this is the major concern, right?  If one leaves the ASMI password at the default, or if they assign it a weak password and it gets guessed, then someone can power off the server?  Much like if I leave my IBM i password for QSECOFR at QSECOFR someone could issue PWRDWNSYS *IMMED?  Or if I leave my AIX root user's password at a default value someone could issue the shutdown command?  But it's not like they get any backdoor access to any LPAR's data hosted on the system, right?

And, with the growing popularity of vHMC, taking that ASMI cable and plugging it into a dedicated port on the HMC is out of the question.  So you end up plugging it into a switch anyway, right?  So, sure, we can configure it on a vlan, just as long as I, or my team can get to it.  Our Power systems are either a few hours south or a few hours north of our office.

<snip>

Unfortunately ASMI also has a poor history of using weak passwords. If
I can access your ASMI from a PC on your public LAN, and guess the IBM
default, I can turn off your server without warning.

</snip>

So basically BMC is a rename of ASMI?

If I log into my HMC and upgrade the firmware that way, doesn't that automatically upgrade the BMC also?

I've never understood why the ASMI port needs to be on a separate network.  I don't keep HR data, proprietary engineering drawings, strategic business plans, etc on a separate network.  Why should the ASMI port be on a separate network?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?

I have had multiple Power systems for years.  I've done numerous upgrades.

I used to have physical HMC's but now have vHMC's and would never go back to physical HMCs.

I'm familiar with ASMI and can log into that.

I hear talk of BMC but I'm not really sure what that is, or, if my setup would even use it.  What is it?

I use my HMC to upgrade firmware on my Power systems.  I keep firmware, vios, IBM i, HMC releases current and patched.  Is BMC something to be concerned about too?