I'm supporting a UCS POD in my environment running with 2.2(3b) infra version

[arnab.kar11]

I'm supporting a UCS POD in my environment running with 2.2(3b) infra version . Recently we seated a B420 M3 & created a new profile associating to the blade . However, during the activity we got pending reboot notifications for total 7 blades from different different chassis collectively. When I expand the tab , it says pending reboot due to changes made by <User ID> w.r.t networkng operational-policy . I'm not having clue as to what has been changed ? Any way I can revert back the change & stop the reboot ?

Also just to give you more heads up , we don't use updating template & there were no changes made to any host firmware package .....

[Qiese Dides]

Hi Arnab,

To cancel the pending status you must revert the changes that have been made. Since you do not know what was changed the best thing would be to open a TAC case so someone can deep dive the logs and see what was actually changed. If you can please attach a screenshot of the error so we can understand better the warning.

This guide explains the situation better;

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-0/b_UCSM_GUI_Configuration_Guide_2_0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_011110.html

Basted on the working you have Network Operational Policy that has something to do with Configuring network related situations such as adding a VNIC to a template. Examples within this policy is located in the guide below;

http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/2-1/b_UCSM_GUI_Configuration_Guide_2_1/b_UCSM_GUI_Configuration_Guide_2_1_chapter_010101.html

Something must have been configured that is listed in the above link to cause this pending activity, the logs will be able to show what was changed specifically.

Regards,

Qiese Dides

[AFROJ AHMAD]

Hi Arnab,

Generally, the following changes can cause reboots:

-        MAC address changes with Oplin/Menlo.
-        Port or Node WWN changes.
-        Adding (when capacity permits) or removing an interface.
-        Applying a new boot-from-SAN policy that has "reboot on boot order change" clicked.
-        Enabling failover for a vNIC that didn't have it enabled previously.
-        Changing host firmware pack that has pack-items different from running firmware versions on the associated server.
-        Changing firmware host pack itself that is being used by service-profiles. Note that this could reboot all the servers using this pack.

IMP **you can check the "UCSM show tech" > look for "sam_techsupport under the active or primary Fabric Interconnect  and look for "`show audit-logs detail" that will definitely help you finding the changes made.

Thanks-

Afroz

***Ratings Encourages Contributors ***