Answered in the support forums, posted here as well
Dilip,
The API is operating correctly, processing the XML that was sent to approriately. The XML code is setting the Floppy object boot order to 1 which resulted in what you see in the boot policy shown in the GUI.
The GUI builds the XML based on what is requested and "helps" the GUI user, in the case of a boot policy by modifying the order number of the above or below boot option depending upon which direction the boot option is moved.
The XML code sent to the UCS Manager by the GUI will send the code for ALL the affected boot objects. The code your application needs to do the same.
If you want the Floppy to be order 1 then the boot object that is order 1 needs to become the order of what the Floppy was, in your picture that would be the Local Disk.
You code needs to look like this, the difference is the addition of the Local Disk object. Also please notice that I am changing a boot policy called "localboot" not "default"
<configConfMos inHierarchical="true" cookie="1316615902/0221f3e1-beae-4958-9589-26bc704654f7">
<inConfigs>
<pair key ="org-root/boot-policy-localboot">
<lsbootPolicy name="localboot" descr="Modified by GaleForce Adapter" purpose="operational" dn="org-root/boot-policy-localboot" rebootOnUpdate="no" enforceVnicName="no">
<lsbootVirtualMedia rn="read-write-vm" order="1" access="read-write" />
<lsbootStorage order="2" rn="storage">
<lsbootLocalStorage rn="local-storage"/>
</lsbootStorage>
</lsbootPolicy>
</pair>
</inConfigs>
</configConfMos>
Hope that helps.
John
