"owningControllerIp":"172.17.6.70",
"dataPaths":[
{
"dpid":"00:01:44:31:92:5c:af:86",
"owningControllerIp":"172.17.6.70"
}
]
},
{
"deviceIp":"192.168.1.102",
"owningControllerIp":"172.17.6.70",
"dataPaths":[
{
"dpid":"00:1e:c8:cb:b8:dd:f0:c0",
"owningControllerIp":"172.17.6.70"
}
]
},
{
"deviceIp":"192.168.1.103",
"owningControllerIp":"172.17.6.70",
"dataPaths":[
{
"dpid":"00:1e:f0:92:1c:21:af:00",
"owningControllerIp":"172.17.6.70"
}
]
},
{
"deviceIp":"192.168.1.104",
"owningControllerIp":"172.17.6.70",
"dataPaths":[
{
"dpid":"00:01:cc:3e:5f:6b:19:00",
"owningControllerIp":"172.17.6.70"
}
]
},
{
"deviceIp":"192.168.1.105",
"owningControllerIp":"172.17.6.70",
"dataPaths":[
{
"dpid":"00:1e:00:9c:02:e0:e4:00",
"owningControllerIp":"172.17.6.70"
}
]
}
]
}
]
}
Getting the status of all regions using curl
This
GET
command retrieves the current status of all regions, including their configured devices
and the controller that currently owns each device. You can filter the returned content of this
command in order to get the current status for a specified device, allowing you to determine
which region the device is configured in addition to which controller owns the device.
You can also specify the optional
dataPathDetails
parameter to enhance the output for
devices to include DPID information consisting of each DPID associated with the device and the
controller that currently owns each DPID. You can specify this parameter independently of the
deviceIp
parameter, and the resulting output is similar to that when the optional
196
curl commands