Commiting the firmware upgrade – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 94
62
Network OS NETCONF Operations Guide
53-1003231-02
Evaluating a firmware upgrade
5
<control-processor-vendor>Freescale Semiconductor
</control-processor-vendor>
<control-processor-chipset>8548E</control-processor-chipset>
<control-processor-memory>2000 MB</control-processor-memory>
<node-info>
<firmware-version-info>
<primary-version>v3.0.1_bldg57</primary-version>
<secondary-version>v4.0.0_bldg56</primary-version>
</firmware-version-info>
</node-info>
</show-firmware-version>
</rpc>
ATTENTION
If you want to restore the firmware, stop here and skip ahead to
on page 63; otherwise, continue to
“Commiting the firmware upgrade”
page 62 to complete the firmware download process.
You are now ready to evaluate the new version of firmware.
Commiting the firmware upgrade
If you decide to keep the firmware upgrade, use the firmware commit operation to update the
secondary partition with new firmware. On modular switches you must perform this operation on
both management modules. It may take several minutes to complete the commit operation.
1. Issue the <firmware> action and specify the <commit> element.
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="410">
<action xmlns:nca="http://tail-f.com/ns/netconf/actions/1.0">
<data>
<firmware xmlns="urn:brocade.com:mgmt:brocade-firmware">
<commit/>
</firmware>
</data>
</action>
</rpc>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="410">
<data>
<firmware xmlns="urn:brocade.com:mgmt:brocade-firmware">
<commit>
<result></result>
</commit>
</firmware>
</data>
</rpc-reply>
2. Issue the <show-firmware-version> custom RPC to confirm that both the primary partition and
the secondary partition of the switch contain the new firmware.
<rpc message-id="411" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<show-firmware-version xmlns="urn:brocade.com:mgmt:brocade-firmware-ext">
<switchid xmlns="urn:brocade.com:mgmt:brocade-ras-ext">24</switchid>
</show-firmware-version>
</rpc>