Hello,

thanks to contact us.

Can you check if the idrac firmware level is the same for all the servers?

Any difference about the discovering method?

Thanks
Marco

Hi Marco,

Thanks for your response. All iDrac Firmware levels: 4.22.00.53. This is my lab enviroment with two MX7000 Chasis. Three MX740c in one, two MX840c in second one. Discovered by the lead chasi, all devices Proxied/Managed with Alerts state. iSM service installed on all Guest OS. I installed SAE Plugin for test purposes I'm checkingif I can deploy it at my client's enviroments. I verified that some blade servers are working fine and have Collection Capability Status: Success, some got it failed. It is also weird why IOMs are not monitored by SAE Plugin.

After posting, my Images are missing. Hope you can see them. If not please tell me I will upload them somewhere else. @DELL-Marco B 

Can you try to reset the idrac? It just restart the module, without restarting the server.

https://dell.to/3mxK9Yl

Thanks
Marco

Hi Marco,

I redeployed OME in my lab, rediscovered devices and it looks fine now for servers and chasis. Do you know if I can also monitor IOMs? MX9116n/MX5108n etc? In a User Guide I can see that we should be able to monitor network devices. It is available in SAE VE for sure. But all my IOMs are in a Unmanaged Devices group. So it looks like those devices are not Staging but are not supported. I may be wrong.

Hello,

following this documentation they are supported from with fw 10.4.3.4, but you need to manually configure SNMP on the network device.

https://dell.to/3euWUA9

Thanks

Marco

Hello,

If I've misunderstood you, I apologize, but let me know if this clears anything up.

OpenManage Enterpise does support Switches. However, the SA plugin won't interface with them. If you like, we can submit a request to bring it up to feature parity for the next release (can't say when that may be, no access to that information). If that's a route you're interested in, let us know. There may just be a small amount of information we'd need to get from you as part of that submission.

Hi Marco,

Nothing to apologize for:) 

I'm pretty sure that should be the roadmap of the product development if we want to replace additional SAE VE / DRM with new Plugins for OME like SAE v1.0, Update Manager (instead DRM). Only if the new ones give us 100% features from the old ones we can implement only OME with plugins in our client enviroments. For that moment I won't be using SAE Plugin because it is not supporting switches and I will need to still deploy OME+SAE VE+DRM to ensure all the features. Not to be so critical I think this SAE Plugin is really good and I hope that in next releases it would cover all the features from SAE VE.

If I can have any influence on product development I will suggest some basic changes based on my experience:

1. SAE Plugin - network devices support.
2. Backup - all appliance settings backup, to quickly recover with newly deployed appliance.Thats something that should be available since OME 3.0.
3. SSO - Virtual Console / iDrac access from OMEnterprise without additional login to iDrac. Should be same as in OME-Modular (OIDC Server). Just quick redirection without need to provide credentials that are already in OME to onboard.
4. Virtual Disk - VD information at the server Dashboard or in Hardware section. This is something that is available in OMEssential 2.5 but not in OMEnteprise. 
5. Login Banner - this is some minor feature. But after we discover our server in OME and start managing from console, it could be automaticly setting iDrac Security Notice: This device is managed by OpenManage Enterprise. Like in HPE OneView: "This system is being managed by: HP OneView
   Changes made locally in iLO will be out of sync with the centralized settings."
6. Identity Pool - Identity Pool usage may have Advanced Filters option to easier filter all the values. When we have 16 pages of Virtual Identities its hard to find anything. I know it is now available also from Profile section, but still it could be better.
7. Profiles - column "Last Action Status" is something I don't like from the beggining. We can schedule profile deployment for 15 servers and if on one of them we got some minor issues and it is setted to failed we got all of those profiles with status "Completed with Error". It is not very nice to have it in a newly deployed enviroment where everyting should be 'green'. Profile Status is most important I don't see the point to have this Last Action Status columnt in there.

Hello,

thanks for your suggestions.
I will make my best to escalate it internally.

Marco