Configuring Sup Boot Variables
Configuring Sup Boot Variables
POST http://<IP_Address>/api/mo/sys/boot/image.json
{
"bootImage": {
"attributes": {
"sup1" : "bootflash:/nxos.9.2.0.101.I9.1.bin",
"sup2" : "bootflash:/nxos.9.2.0.101.I9.1.bin"
}
}
}
POST: http://<IP_Address>/restconf/data/Cisco-NX-OS-device:
<System xmlns="http://cisco.com/ns/yang/cisco-nx-os-device">
<boot-items>
<image-items>
<sup1>bootflash:/nxos.9.2.0.101.I9.1.bin</sup1>
<sup2>bootflash:/nxos.9.2.0.101.I9.1.bin</sup2>
</image-items>
</boot-items>
</System>
CLI Command
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload.
boot nxos bootflash:/nxos.9.2.0.101.I9.1.bin sup-1 sup-2
Note: The Sup-1 and Sup-2 variables are optional. If sup-1 or sup-2 are not entered, both are taken by default.
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference: http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload: https://developer.cisco.com/media/dme/index.html
Configuring the Autocopy of Bootvar Images
Configuring the Autocopy of Bootvar Images
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"autoCopy": "enable"
}}}]}}
{
imdata:[]
}
<System>
<boot-items>
<autoCopy>enable</autoCopy>
</boot-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
boot auto-copy
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
autoCopy | boot:AutoCopy (scalar:Enum8) | Boot Auto Copy | SELECTION: 0 - disable 1 - enable DEFAULT: enable |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Autocopy of Bootvar Images
Deleting the Autocopy of Bootvar Images
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"autoCopy": "disable"
}}}]}}
{
imdata:[]
}
<System>
<boot-items>
<autoCopy>disable</autoCopy>
</boot-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no boot auto-copy
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
autoCopy | boot:AutoCopy (scalar:Enum8) | Boot Auto Copy | SELECTION: 0 - disable 1 - enable DEFAULT: enable |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring PXE Boot
Configuring PXE Boot
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"order": "bootflash2pxe"
}}}]}}
{
imdata:[]
}
<System>
<boot-items>
<order>bootflash2pxe</order>
</boot-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
boot order bootflash pxe
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
order | boot:Order (scalar:Enum8) | Boot Order bootflash/pxe | SELECTION: 0 - bootflash 1 - pxe 2 - pxe2bootflash 3 - bootflash2pxe DEFAULT: bootflash |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting PXE Boot
Deleting PXE Boot
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"order": "bootflash"
}}}]}}
{
imdata:[]
}
<System>
<boot-items>
<order>bootflash</order>
</boot-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no boot order bootflash pxe
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
order | boot:Order (scalar:Enum8) | Boot Order bootflash/pxe | SELECTION: 0 - bootflash 1 - pxe 2 - pxe2bootflash 3 - bootflash2pxe DEFAULT: bootflash |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring Boot from Bootflash
Configuring Boot from Bootflash
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"order": "pxe2bootflash"
}}}]}}
{
imdata:[]
}
<System>
<boot-items>
<order>pxe2bootflash</order>
</boot-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
boot order pxe bootflash
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
order | boot:Order (scalar:Enum8) | Boot Order bootflash/pxe | SELECTION: 0 - bootflash 1 - pxe 2 - pxe2bootflash 3 - bootflash2pxe DEFAULT: bootflash |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting Boot from Bootflash
Deleting Boot from Bootflash
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"order": "bootflash"
}}}]}}
{
imdata:[]
}
<System>
<boot-items>
<order>bootflash</order>
</boot-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no boot order pxe bootflash
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
order | boot:Order (scalar:Enum8) | Boot Order bootflash/pxe | SELECTION: 0 - bootflash 1 - pxe 2 - pxe2bootflash 3 - bootflash2pxe DEFAULT: bootflash |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring Boot Mode LXC
Configuring Boot Mode LXC
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"mode": "lxc"
}}}]}}
{
imdata:[]
}
<boot-items>
<mode>lxc</mode>
</boot-items>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
boot mode lxc
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
mode | boot:Mode (scalar:Enum8) | Select boot mode type | SELECTION: 0 - native 1 - lxc 3 - dockerCluster DEFAULT: native |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting Boot Mode LXC
Deleting Boot Mode LXC
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"mode": "none"
}}}]}}
{
imdata:[]
}
<boot-items>
<mode>none</mode>
</boot-items>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no boot mode lxc
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
mode | boot:Mode (scalar:Enum8) | Select boot mode type | SELECTION: 0 - native 1 - lxc 3 - dockerCluster DEFAULT: native |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring Boot Mode Docker Cluster Mode
Configuring Boot Mode Docker Cluster Mode
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"dhcp": "250",
"mode": "dockerCluster"
}}}]}}
{
imdata:[]
}
<boot-items>
<dhcp>250</dhcp>
<mode>dockerCluster</mode>
</boot-items>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
boot mode docker_cluster
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
dhcp | boot:Dhcp (scalar:Uint32) | Set the dhcp value | RANGE: [0 , 2147483647] DEFAULT: 250 |
mode | boot:Mode (scalar:Enum8) | Select boot mode type | SELECTION: 0 - native 1 - lxc 3 - dockerCluster DEFAULT: native |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting Boot Mode Docker Cluster Mode
Deleting Boot Mode Docker Cluster Mode
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"bootBoot": {
"attributes": {
"mode": "none"
}}}]}}
{
imdata:[]
}
<boot-items>
<mode>none</mode>
</boot-items>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no boot mode docker_cluster
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
topSystem | sys |
bootBoot | sys/boot |
bootBoot Properties
The following table contains information about the bootBoot properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
mode | boot:Mode (scalar:Enum8) | Select boot mode type | SELECTION: 0 - native 1 - lxc 3 - dockerCluster DEFAULT: native |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide: