With v4.1.3 of the UCS Management Service for SCOM, alerts are generated in the SCOM console even though these UCS faults have cleared in the UCS console (reboot completed successfully).
This didn't seem to be the case with the v4.1.1 version of the UCS Management Service. Our procedure is to place a chassis into maintenance mode in SCOM during reboot operations, and no faults generate SCOM alerts during this time. The reboots complete, and severity changes to cleared. Once SCOM maintenance mode is removed from the chassis, the cleared faults would not then generating alarms in SCOM, even though they were still present in the UCS management console.
If I manually acknowledge the fault in UCS, SCOM closes the alert.
Is there a way to not generate SCOM alerts or close SCOM alerts on faults that have cleared in the console?
Was trying to get neworking to work on a new Ubuntu install on a UCS server. I did a "shutdown -r" and rebooted the server. Now it seems to be stuck in the Aptio setup utility. I either choose "save and exit" or exit without saving changes and I am brough...
Just wonder we recently try to add 2 M200 with firmware 4.1.1b, our UCS manager version is 4.0.2d, we got error said cannot donwgrade. I know we can update ucs manager from 4.0 to 4.1, bur wonder we can downgrade
OpenStack Neutron project offers pluggable framework means you can extend the capability of Neutron by orchestrating the Neutron functions to your upstream networking gears. For example, if you have provisioned a VLAN tagged Neutron network in Op...
https://soundcloud.com/user-327105904/s7e25-from-the-office-to-anywhere-empowering-secure-remote-work-with-cisco-vdi-solutions As organizations have had to rapidly respond and transition in the face of swift change, Cisco VDI solutions have enabled ...