...
The resource discovery command issued by the device driver hits the following resource path on the server:
|
A server with 2 Intel CPU cores in one socket, 16 GB of DDR4 DRAM, and a single-port Mellanox 100 GbE NIC might provide the following response:
...
The CPU, main memory, and NIC monitoring command issued by the device driver hits the following resource path on the server:
|
...
A server with NICs in mode "flow" allows the server device driver to manage its rules.
To install a NIC rules rule on a server's NIC with instance name fd0, associated with CPU core 0, the device driver POST issues the following JSON HTTP POST command to the server's resource:
...
HTTP POST: http://serverIp/metron/rules
{
...
|
...
|
For your convenience the same rule is visualized below in a user-friendly JSON format:
{ {
"rules":
[
{
"id": "5057dd63-93ea-42ca-bb14-8a5e37e214da",
...
The NIC rule monitoring command issued by the device driver hits the following resource path on the server:
|
...
To delete multiple rules at once, you should append a comma-separated rule IDs as follows:
|
...
To retrieve statistics related to a server's NIC tables, the server device driver needs to hit the following path:
|
NIC Port Administration
To enable a NIC port, the server device driver needs to issue the following HTTP post command to a server:
...
To access the server device driver's UI click on the Menu button (top left corner on the ONOS UI), then select one of the tabs "Servers-CPU", "Servers-MemoryLatency", "Servers-ThroughputMemory", or "Servers-LatencyThroughput" at the bottom of the list in Section "Network" as shown in the figure below:
...