Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
In legacy IP/Ethernet networks, network and connectivity configuration (for example configuring BGP, IP subnets, VLANs, or ACLs) usually requires configuring multiple individual devices. With ONOS, equivalent functionality is usually provided by an network application. Some ONOS applications – software packages for a particular task or use case – that usually provide services across multiple devices or the entire network. Some ONOS applications (such as reactive forwarding) either require no configuration or operate perfectly well with a default configuration. However, but other applications may require additional specific configuration information that cannot be inferred automatically. These applications can be configured using the Network Configuration Service.
...
Information on configuring ONOS itself (such as setting up an ONOS cluster, or activating applications), as well as using ONOS to configure network devices, can be found in appropriate sections of this guideof Configuring ONOS.
| Table of Contents | ||
|---|---|---|
|
...
Syntax
A subject key describes the category of network element, e.g. links, devices, hosts, etc. Each network element is associated with a unique identifier (a subject) and one or more attributes, associated with some value, grouped into configs. The configs themselves are classified by config keys.
The JSON file used with the service then takes on the following format:
| Code Block | ||
|---|---|---|
| ||
{
subject key : { # element category, e.g. "devices", "links", etc.
subject : { # unique string, e.g. a device ID
config key 1 : { # config class of config, e.g. "basic"
attr1 : value1, # attribute : value pairs associated with a config
attr2 : value2,
...
},
...
},
...
},
...
} |
Sample configuration files may be found in ${ONOS_ROOT}/tools/test/configs/ .
Network Configurations for Southbound Providers.
Different southbound providers, namely NETCONF, SNMP, REST and TL1 use net-cfg as the mechanism to inject ip, port, username, password of a device.
You can find information about each of these protocols and json examples in their respecitive wiki pages.
Sample configuration for these protocols are also stored in ${ONOS_ROOT}/tools/test/configs/ .
...