Reply to Message

View discussion in a popup

Replying to:
hostasaurus
Enthusiast
Enthusiast

Just adding to this ancient thread that if you call Cisco about this, they may not find this issue because they believe it only occurs on specific B220 M2 hardware with linux as the OS.  It also occurs on other hardware, such as the B440, with the E7 CPU's and obviously vsphere as the OS.  The fix involves a change to the BMC settings that end users are not allowed access to, as it requires Cisco's symmetric key auth they'll do via webex session; so any blade will need to be reboot and have the fix applied, one at a time, via webex with them.  It does resolve the issue.

Reply
0 Kudos