Cisco UCS 62XX firmware upgrade for personal use

Cisco UCS 62XX firmware upgrade for personal use

Because again to some blades, the new blade firmware different, the version is very new, some can be downgraded to the current use of 2.2.1b, some do not know why not down ...

More fixed bug, compatible with Vmware6, so upgrade ...

Main preparatory work:

1, confirm that the machine is running well, there are no major errors;

2, check your profile file, confirm their network card and HBA card how to go (I am 4 network cards, 2 HBA cards, 4 network cards only use 1, walk IO module A, so only on the fi-a have business data traffic), Verify that the failover of the network card in the profile file is turned on (so that fi-a hangs directly failover fi-b the business flow will not be interrupted).

3, upload firmware, up to now + consulting Cisco will present the latest 2.2.5b import.

4,show cluster state confirms HA status, this step is most important ...

Upgrade Order:

UCS has a rule that is what version of UCSM will turn IO module into a version,

So the upgrade sequence is as follows,

1,acitve UCSM

2,update IO Module B

3,active IO Module B

4,active Fi-b

5,fi-b After the upgrade succeeds, the command line enforces the Fi-b, upgrades Fi-a, and does not disrupt the business.

6,update IO Module A

7,active IO Module A

8,active fi-a

9,fi-a after the successful upgrade, the command line to force the management of FI-A, this is the main work done.

10, finally upgrade the blade, because I am running VMware, so close half of the blade (into the maintenance mode), let the virtual machine run to the other half up, upgrade, after the virtual machine migrated back, upgrade the other half ...

11, when upgrading, note that the status is ready and pending next boot, you can proceed to the next step, if the status is updating or schedule the next possible error ...

Firmware upgrade sequence for the Adpter--bios-cimc-board controller is update once the active over the time of the update four components can be together, active when it seems you have to order ... caution will automatically restart if the ACK in the maintenance in your profile file is not checked ...

Now start 2.2.1b---"2.2.5b

Upgrade UCSM Direct Acitve2.2.5b,ok, start will be schedule, then UCSM management Disconnect, re-login ...

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/73/7E/wKioL1X_uDnw5wmqAATKzHhIWtw152.jpg "style=" float: none; "title=" 1.jpg "alt=" Wkiol1x_udnw5wmqaatkzhhiwtw152.jpg "/>

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/73/81/wKiom1X_tfzzdacTAAVF4CX5r7U177.jpg "style=" float: none; "title=" 2.jpg "alt=" Wkiom1x_tfzzdactaavf4cx5r7u177.jpg "/>

Disconnected not ...

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/73/81/wKiom1X_tfyjFg3ZAAXbRN9S_Is794.jpg "style=" float: none; "title=" 3.jpg "alt=" Wkiom1x_tfyjfg3zaaxbrn9s_is794.jpg "/>

Fi-b's UCSM has been upgraded to 2.2.5b

A lot of error is it, it doesn't matter, do not affect the business, all upgrade will be good ...

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/73/81/wKiom1X_tf3xYOWaAASMtdLoHLE437.jpg "style=" float: none; "title=" 5.jpg "alt=" Wkiom1x_tf3xyowaaasmtdlohle437.jpg "/>

Upgrade IO module B first update, wait 10 minutes or so to complete, status only show ready when the time is complete, show updating time is not finished, he will be completed in order.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/73/7E/wKioL1X_uDvAaZIqAAevuXBdhcg475.jpg "style=" float: none; "title=" 6.jpg "alt=" Wkiol1x_udvaaziqaaevuxbdhcg475.jpg "/>

Reactivate, active, when the display pending next boot is complete, do not restart here, to restart the fi-b when the restart

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/73/7E/wKioL1X_uDyxndb0AAUodjol0zs675.jpg "style=" float: none; "title=" 8.jpg "alt=" Wkiol1x_udyxndb0aauodjol0zs675.jpg "/>

IO module B is completed after upgrading Fi-b direct active display updating

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/73/7E/wKioL1X_uDzB82m6AANsO_Qws3g252.jpg "style=" float: none; "title=" 9.jpg "alt=" Wkiol1x_udzb82m6aanso_qws3g252.jpg "/>

Show ready, this time Fi-b has been automatically restarted, fi-b a reboot IO module B also restarted, that is, IO module B and fi-b upgrade complete ...

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/73/81/wKiom1X_tf_xL0adAAbNrITo_UQ935.jpg "style=" float: none; "title=" 10.jpg "alt=" Wkiom1x_tf_xl0adaabnrito_uq935.jpg "/>

Fi-b upgrade completed, will be management cut to the top of the cluster lead B, business I feel is fi-a restart when I failover to B ...

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/73/7F/wKioL1X_uD3zVDvOAAXn8EoEY2Q951.jpg "style=" float: none; "title=" 11.jpg "alt=" Wkiol1x_ud3zvdvoaaxn8eoey2q951.jpg "/>

Management of traffic will be broken, re-login to find Fi-b-based, management of the main, business traffic does not know in a run, then forgot to use the flow software to look at the upstream port

, management traffic is broken, business traffic is all right ...

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/73/81/wKiom1X_tgCBgsSPAAX5Q68bqM4467.jpg "style=" float: none; "title=" 12.jpg "alt=" Wkiom1x_tgcbgsspaax5q68bqm4467.jpg "/>

Repeat above process upgrade a first updating IO module a

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/73/7F/wKioL1X_uD7yZ-hJAAckkGHDzrg192.jpg "style=" float: none; "title=" 13.jpg "alt=" Wkiol1x_ud7yz-hjaackkghdzrg192.jpg "/>

Active but do not reset IO module, and so on and fi-a upgrade complete together reboot

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/73/81/wKiom1X_tgGTbX9MAAYw5l_WRyM299.jpg "style=" float: none; "title=" 14.jpg "alt=" Wkiom1x_tggtbx9maayw5l_wrym299.jpg "/>

, my business traffic has not been interrupted, VMware Normal, even if the UCS management traffic problems lost several packages, business traffic has not lost packets

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/73/81/wKiom1X_tgHh-cHmAAeYvlaulPY035.jpg "style=" float: none; "title=" 15.jpg "alt=" Wkiom1x_tghh-chmaaeyvlaulpy035.jpg "/>

Ok fi all upgrade completed IO module Well, the most difficult to complete, business and management everything is good ...

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/73/7F/wKioL1X_uD_hbprYAAiSeeCl9tM817.jpg "style=" float: none; "title=" 16.jpg "alt=" Wkiol1x_ud_hbpryaaiseecl9tm817.jpg "/>

Cluster lead a switches management traffic back ...

You may be confused by what I said earlier,

Perhaps fi-a an upgrade completed, run normal, business traffic is not going to go failover fi-b, because I profile set the network card to walk IO module A---"Fi-a, so a good on the grab back, as for the management of traffic is still in the b,b or management of the Lord, I manually specify admin back to a,

If you have a monitoring software you can see the change in traffic ...

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/73/7F/wKioL1X_uEDQQI47AASw_qHep3g985.jpg "style=" float: none; "title=" 17.jpg "alt=" Wkiol1x_uedqqi47aasw_qhep3g985.jpg "/>

Re-login to start the upgrade blade, very simple, update, come together, no tube sequence

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/73/81/wKiom1X_tgPhN6n9AAYClGRGmq0697.jpg "style=" float: none; "title=" 18.jpg "alt=" Wkiom1x_tgphn6n9aayclgrgmq0697.jpg "/>

Active, this has to order ah ... (But I'm the top two components together, the following two components together, so fast no error ... ）

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/73/81/wKiom1X_tgPDQ8NfAAYClGRGmq0530.jpg "style=" float: none; "title=" 19.jpg "alt=" Wkiom1x_tgpdq8nfaayclgrgmq0530.jpg "/>

Finally, the backup version is also the same as update

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/73/81/wKiom1X_tgSwumIFAAXtJAp3sm0901.jpg "style=" float: none; "title=" 20.jpg "alt=" Wkiom1x_tgswumifaaxtjap3sm0901.jpg "/>

Everything OK ... A year later in the work of repeating it ...

Shortcomings, please correct me ...

Reference documents:

Http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/firmware-mgmt/gui/2-2/b_GUI_Firmware_Management_ 22/b_gui_firmware_management_22_chapter_0110.html

Cisco UCS 62XX firmware upgrade for personal use