Configuring Breakout on High-Bandwidth Interfaces
Cisco NX-OS supports breakout interfaces. The breakout command works at the module level and splits the 40G interface of a module into four 10G interfaces.
The module is reloaded and the configuration for the interface is removed when the command is executed.
When doing a module/port-level breakout through REST, upon the completion of the action by the switch, you should see the corresponding l1PhysIf MOs get created with the DN as "sys/intf/phys-[id]" as an example.
- interface breakout module
- interface breakout module
port map - show interface brief
- show system internal im info interface ethernet 1/1/1
- show system internal im info module 1
This section contains payload examples to demonstrate how to use the NX-API REST API to configure breakout on high-bandwidth interfaces.
Posting a Task
Posting a Task
POST http://<mgmt0_IP>/api/mo/sys/action.json
{
"actionLCont": {
"attributes": {
"dn": "sys/action"
},
"children": [
{
"actionLSubj": {
"attributes": {
"dn": "sys/action/lsubj-[sys]”
},
"children": [
{
“topSystemCopyRSLTask”: {
"attributes": {
"adminSt": "start",
"dn": "sys/action/lsubj-[sys]/topSystemCopyRSLTask”
“freq”: “one-shot”
}
}
}
]
}
}
]
}
}
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
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting a Task
Deleting a Task
DELETE http://<mgmt0_IP>/api/mo/sys/action/lsubj-[sys].json
Deleting All Tasks (Example 1)
Deleting All Tasks (Example 1)
DELETE http://<mgmt0_IP>/api/mo/sys/action.json
Deleting All Tasks (Example 2)
Deleting All Tasks (Example 2)
POST http://IP-address/api/mo/sys/action.json
{
"actionLCont": {
"attributes": {
"dn": "sys/action"
“status”: “deleted”
}}}
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
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html