Setup generic email for warning and critical events from servers in Compute Ops

[BigbirdDK]

Hey,

I am trying to setup our servicedesk email to recieve email related to any issues with a server in compute ops.

Disk failure, PSU failure etc.

However, i can't seem to locate this kind of notification.

It seems as I can only configure my email notifications to the my personal email, however I cannot input our servicedesk email anywhere. 

Do I really have to create a new user and use that to configure ? That option is not avalible for us, as I can't create a user for the generic servicedesk email, as I wont be to do SSO/MFA on that account.....

[Mark-S]

Hi BigbirdDK,

Thank you for your question in regards to HPE Compute Ops Manager.
There have been prior request for a feature like this to allow an non HPE GreenLake Account to be added as contact for Service events.

This has been prioritzed and HPE is working on adding this capability to HPE GreenLake platform so that the Admin users will be allowed to specify a non-invited email address as a Service Delivery Contact for Auto Case Creation Events. I can't say specfically when this will be rolled out but watch in the upcoming month for new feature releases within HPE GreenLake coming soon. https://common.cloud.hpe.com/whats-new

For now, you are correct, that capability is not available in the product.

Thanks-

Mark

[LazyUnicorn]

It sounds like a tricky issue! You're right that R7 shouldn't normally be altered by the core during an exception return, so it's odd that you're seeing this behavior. Since this is happening in a simulation, there are a few things you could check:

1. Stack alignment: Make sure the stack is correctly aligned before entering the exception. If there’s a misalignment, it might cause corruption of registers like R7 when unwinding the stack during EXC_RETURN.

2. Compiler optimization: If you're using optimizations, the compiler might be using R7 for some internal purposes, like a frame pointer, and that could be affecting the register's value when returning from the exception.

3. Simulation bug: Since you’re running on ARM FastModels, it could be worth checking if there are any known issues with that version (11.26). If this behavior doesn't happen on real hardware, it could point to a bug in the simulation environment. 

Hope that helps point you in the right direction! Let us know if you find anything else.