Creating Checkpoints
Creating a Checkpoint to a File
Creating a Checkpoint to a File
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys]"
}
"children" : [{
"topSystemCreateCheckpointLTask": {
"attributes": {
"adminSt": "start",
"name": "xyz",
"description": "",
"filename": "",
"delete": "no",
"dn": "sys/action/lsubj-[sys]/topSystemCreateCheckpointLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata":[]
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
checkpoint xyz
Note: The property information for this example was added in Release 9.3(3).
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 |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
topSystemCreateCheckpointLTask | sys/action/lsubj-{[oDn]}/topSystemCreateCheckpointLTask |
actionLSubj Properties
The following table contains information about the actionLSubj 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 |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
topSystemCreateCheckpointLTask Properties
The following table contains information about the topSystemCreateCheckpointLTask 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 |
---|---|---|---|
adminSt | action:AdminSt scalar:Enum8 | The administrative state of the object or policy. | SELECTION:
|
name | infra:checkpointStr string:Basic | The name of the object. | RANGE: Min: "0" Max: "79" |
description | infra:checkpointStr string:Basic | The description of this configuration item. | RANGE: Min: "0" Max: "79" |
filename | string:Basic | NO COMMENTS | RANGE: Min: "0" Max: "512" |
delete | infra:deletemode scalar:Enum8 | NO COMMENTS | SELECTION:
|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. | |
freq | action:Freq scalar:Time | Frequency at which tasks are executed | SELECTION:
|
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:
Creating a Checkpoint to a Bootflash File
Creating a Checkpoint to a Bootflash File
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys]"
}
"children" : [{
"topSystemCreateCheckpointLTask": {
"attributes": {
"adminSt": "start",
"name": "",
"description": "",
"filename": "bootflash:ckp1",
"delete": "no",
"dn": "sys/action/lsubj-[sys]/topSystemCreateCheckpointLTask",
"freq": "one-shot"
}
}
}]
}
}
{"imdata":[]}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
checkpoint bootflash:ckp1
Note: The property information for this example was added in Release 9.3(3).
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 |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
topSystemCreateCheckpointLTask | sys/action/lsubj-{[oDn]}/topSystemCreateCheckpointLTask |
actionLSubj Properties
The following table contains information about the actionLSubj 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 |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
topSystemCreateCheckpointLTask Properties
The following table contains information about the topSystemCreateCheckpointLTask 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 |
---|---|---|---|
adminSt | action:AdminSt scalar:Enum8 | The administrative state of the object or policy. | SELECTION:
|
name | infra:checkpointStr string:Basic | The name of the object. | RANGE: Min: "0" Max: "79" |
description | infra:checkpointStr string:Basic | The description of this configuration item. | RANGE: Min: "0" Max: "79" |
filename | string:Basic | NO COMMENTS | RANGE: Min: "0" Max: "512" |
delete | infra:deletemode scalar:Enum8 | NO COMMENTS | SELECTION:
|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. | |
freq | action:Freq scalar:Time | Frequency at which tasks are executed | SELECTION:
|
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:
Creating a Checkpoint to a Volatile File
Creating a Checkpoint to a Volatile File
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys]"
}
"children" : [{
"topSystemCreateCheckpointLTask": {
"attributes": {
"adminSt": "start",
"name": "",
"description": "",
"filename": "volatile:ckp2",
"delete": "no",
"dn": "sys/action/lsubj-[sys]/topSystemCreateCheckpointLTask",
"freq": "one-shot"
}
}
}]
}
}
{"imdata":[]}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
checkpoint volatile:ckp2
Note: The property information for this example was added in Release 9.3(3).
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 |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
topSystemCreateCheckpointLTask | sys/action/lsubj-{[oDn]}/topSystemCreateCheckpointLTask |
actionLSubj Properties
The following table contains information about the actionLSubj 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 |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
topSystemCreateCheckpointLTask Properties
The following table contains information about the topSystemCreateCheckpointLTask 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 |
---|---|---|---|
adminSt | action:AdminSt scalar:Enum8 | The administrative state of the object or policy. | SELECTION:
|
name | infra:checkpointStr string:Basic | The name of the object. | RANGE: Min: "0" Max: "79" |
description | infra:checkpointStr string:Basic | The description of this configuration item. | RANGE: Min: "0" Max: "79" |
filename | string:Basic | NO COMMENTS | RANGE: Min: "0" Max: "512" |
delete | infra:deletemode scalar:Enum8 | NO COMMENTS | SELECTION:
|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. | |
freq | action:Freq scalar:Time | Frequency at which tasks are executed | SELECTION:
|
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:
Creating a Checkpoint
Creating a Checkpoint
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys]"
}
"children" : [{
"topSystemCreateCheckpointLTask": {
"attributes": {
"adminSt": "start",
"name": "",
"description": "",
"filename": "",
"delete": “yes”,
"dn": "sys/action/lsubj-[sys]/topSystemCreateCheckpointLTask",
"freq": "one-shot"
}
}
}]
}
}
{
"imdata": []
}
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
checkpoint
Note: The property information for this example was added in Release 9.3(3).
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 |
---|---|
actionLSubj | sys/action/lsubj-{[oDn]} |
topSystemCreateCheckpointLTask | sys/action/lsubj-{[oDn]}/topSystemCreateCheckpointLTask |
actionLSubj Properties
The following table contains information about the actionLSubj 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 |
---|---|---|---|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. |
topSystemCreateCheckpointLTask Properties
The following table contains information about the topSystemCreateCheckpointLTask 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 |
---|---|---|---|
adminSt | action:AdminSt scalar:Enum8 | The administrative state of the object or policy. | SELECTION:
|
name | infra:checkpointStr string:Basic | The name of the object. | RANGE: Min: "0" Max: "79" |
description | infra:checkpointStr string:Basic | The description of this configuration item. | RANGE: Min: "0" Max: "79" |
filename | string:Basic | NO COMMENTS | RANGE: Min: "0" Max: "512" |
delete | infra:deletemode scalar:Enum8 | NO COMMENTS | SELECTION:
|
dn | reference:BinRef | A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module. | |
freq | action:Freq scalar:Time | Frequency at which tasks are executed | SELECTION:
|
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: