05-16-2017
02:31 AM
- last edited on
03-25-2019
01:21 PM
by
ciscomoderator
Is there a recommended way to decommission fabric nodes before deleting them, via the API?
Currently I am pushing this json:
{
"fabricRsDecommissionNode": {
"attributes": {
"tDn": "topology/pod-1/node-102",
"status": "created,modified",
"removeFromController": "true"
},
"children": []
}
}
to this URL:
https://<apic>/api/node/mo/uni/fabric/outofsvc.json
Solved! Go to Solution.
05-16-2017 07:46 AM
Hi Rob
From my point of view you're doing it the correct way. There are some options:
A) You can post the fabricRsDecommissionNode-MO to either https://<apic>/api/node/mo/uni/fabric/outofsvc.json or https://<apic>/api/mo/uni/fabric/outofsvc.json - That doesn't matter.
B) You don't need the status and children part, the following JSON will do the same job:
{
"fabricRsDecommissionNode": {
"attributes": {
"tDn": "topology/pod-1/node-101",
"removeFromController": "true"
}
}
}
Marcel
05-16-2017 07:46 AM
Hi Rob
From my point of view you're doing it the correct way. There are some options:
A) You can post the fabricRsDecommissionNode-MO to either https://<apic>/api/node/mo/uni/fabric/outofsvc.json or https://<apic>/api/mo/uni/fabric/outofsvc.json - That doesn't matter.
B) You don't need the status and children part, the following JSON will do the same job:
{
"fabricRsDecommissionNode": {
"attributes": {
"tDn": "topology/pod-1/node-101",
"removeFromController": "true"
}
}
}
Marcel
05-18-2017 09:59 AM
Many thanks Marcel, good to know I'm not way off base!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide