Sounds like you're using this in production, correct?

@pete-s a mix, where I currently work we ha e our own Colo and in office servers. A large number of our customers require on premise hardware for their offices, cloud servi es make sense for a lot, but not everything. Even colod workloads make little sense to a lot of our customers.

While it makes a ton of sense to move to hosted email, or even file shares, there are so many proprietary systems that business uses that aren't cloud ready.

@pete-s said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

@dustinb3403

Unfortunately tech that goes obsolete always causes problems but it's more technically sound to monitor through the OOB management interface.

It's after all independent of the OS running on the hardware, independent of the server's NICs, independent of most hardware failures and can be used for a lot more than just monitoring.

And in any modern installation, the OOB management should have been setup and in use already.

Absolutely I agree with that, except the only OOBM that existed before OneView was Ilo and smtp emailing. Which is hardly reliable.

And I do agree that moving to an OOBM like OneView makes sense, it doesn't make sense for an ITSP to have to use though, as it's setup per customer, and would be running on the same hardware it's monitoring in most cases.

Edits are corrected typos

@scottalanmiller said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

@dustinb3403 said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

@voip_n00b said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

@dustinb3403 Why?

Because you're required to setup and maintain and additional environment for it.

1 customers won't want to spend more money for something they've previously had included (by hpe) and 2 ESXi needs this functioning to report on the underlying health status.

Explain.... "Well, this happened because you are overpaying for something that you don't need and now it costs even more because they know you will pay because you are already paying just for the sake of paying. Instead of paying more, you could pay less."

And they will instantly say "oh heck no way do we want to SAVE money, spend spend spend"

What?

HPE is removing a hardware monitoring provider for VMWare (and presumably everything else). The assumption that anyone who has hardware, must be able to monitor it, ideally through their hypervisor.

Sure shifting to monitoring through the hardware interface, such as ILO or OneView but these approaches add yet another administrative panel that must be used and managed and maintained.

@voip_n00b said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

@dustinb3403 Why?

Because you're required to setup and maintain and additional environment for it.

1 customers won't want to spend more money for something they've previously had included (by hpe) and 2 ESXi needs this functioning to report on the underlying health status.

@voip_n00b said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

@dustinb3403 It’s free and has more functionality.

For a standalone environment, it is not msp/itsp friendly.

@voip_n00b said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

@dustinb3403 who cares. This is what the iLO Amplifier Pack is for. Just use that. It even automatically opens tickets with HPE.

You clearly don't support customers.

"Hey those new servers that were easy to monitor and support, yeah well now all of that is gone. But you can buy this other thing to get a tiny portion of the functionality back."

@scottalanmiller said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

@dustinb3403 said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

@dashrender said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

Good thing no one here runs ESXi..

Sure and none of us support it either.

....

Just like HPE. jajaja

That is actually a good one

@dashrender said in Goodbye hardware monitoring on HPE Gen10 and newer equipment running ESXi:

Good thing no one here runs ESXi..

Sure and none of us support it either.

....

So this will definitely impact some if not all of you, but all Gen 10 and newer HPE Servers with hardware RAID, running ESXi will no longer be able to monitor the drive or array's health. Below I'm quoting Mario Glenwin from L2 Technical Solutions Consultant from HPE.

We received a confirmation from engineering team. Smx-provider package is set to retire and we are recommending customers to remove the same going further.
There is no additional development/research happening on smx-provider.

Engineering team have recommended that we could monitor drives from ILO/AMS and One View if configured.

Support article for the recommended fix: https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00117054en_us

With 3.53 or newer raid controller firmware on Gen10 or newer servers you can expect to see misreported issues like the ones pictured below.

HPE's current officially recommended solution to prevent seeing these errors is to uninstall the SMX-Providers from within ESXi. Unfortunately VMWare and HPE documentation lists the smx-provider as the solely supported way to monitor storage.

https://www.vmware.com/resources/compatibility/pdf/vi_cim_guide.pdf

You could of course move to HPE OneView or potentially use ILO to email alerts out of an individual server but there are far more fault domains then getting directly reported from the tooling on the Hypervisor (in this case VMWare).

I've been in conversations for months now about this with HPE and it appears that this is likely not going to change for the better.

@wrcombs said in NTFS Permissions Tools:

@voip_n00b said in NTFS Permissions Tools:

I'm looking for a NTFS Permissions Tool that can give me a simply report to show who has access to what.

Anyone have a tool they like?

have you tried the powershell script for this?

I actually have one written, I'll try to remember to post it when I get a free minute.

University loses 77TB of research data due to backup error

@gjacobse said in Miscellaneous Tech News:

I challenge you-

Just another surprising TikTok Challenge with a possible shocking outcome.

-to do better.

Electric Shiffle Challenge.

Climb a high power transfer tower, and connect all 3 wires together using a copper wire AND SURVIVE the climb down.

At the vet hospital again, 2nd time in 4 days. Dog has started having seizures, which have returned even though she is on medication.

I've had continual issues across chrome, edge firefox and brave on Android mobile.

Scrolling sucks now were as before it was smooth. Or I can't post for some error etc, so I just don't post any more.

The site is more and more broken with each update.

Happy Thursday to you!

This is all you have within the SonicWall control, on or off. I saw this yesterday and assumed I was missing something critical. The most basic APs in the world include the "Identify AP" functionality.

Apparently, SonicWall APs are more basic than basic as they don't include this functionality at all.

On or off is all you get.

They include no means of blinking the LEDs on these AP's!

It's on or off, which works but is annoying..

How do you blink the LEDs on a sonicwave AP to identify it?

@dafyre said in What Are You Doing Right Now:

@dustinb3403 said in What Are You Doing Right Now:

@krzykat said in What Are You Doing Right Now:

@dustinb3403 said in What Are You Doing Right Now:

I'll be in west palm tomorrow

What you doing in my back yard?

Flew down to pick up a car and drove it back to NY.

Ooof. Bet that was a fun trip!

It was definitely a rough drive back due to the duration. But otherwise uneventful.