Added more to the configuration chapter
AAA
IPv6 router advertisement
External connectivity
vRouter
Static route
Route blackholing
Change-Id: I91a51b12f5aae35ca881846f812b84c57e33ba14
diff --git a/configuration/bridging-unicast.rst b/configuration/bridging-unicast.rst
index 1eb54a9..fe2d2aa 100644
--- a/configuration/bridging-unicast.rst
+++ b/configuration/bridging-unicast.rst
@@ -133,8 +133,79 @@
}
-Notes
------
+IPv6 Router Advertisement
+-------------------------
+
+Router Advertisement overview
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Router advertisement application is for enabling **Router Advertisement** and **Router Solicitation** functionalities supported by IPv6 routers.
+More details are available in `RFC 4861 <https://tools.ietf.org/html/rfc4861>`_.
+
+Application identifies which IPv6 interfaces are currently configured in the system and it will try to send out **unsolicited Router Advertisement** (RA) messages from these interfaces.
+Each such RA message will have two mandatory options named **Source link-layer address** and **MTU**.
+Additional RA option **prefix** can be enabled using component configuration **raGlobalPrefixConfStatus**.
+
+Application also processes **Router Solicitations** (RS) sent from hosts. Upon receiving RS on a particular interface application stops RA transmission in that interface and immediately sends RA targeted to the solicited host. After that application continues unsolicited RA transmission on that interface.
+
+Activate and configure RA
+^^^^^^^^^^^^^^^^^^^^^^^^^
+RA application can be activated from CLI by running
+
+.. code-block:: console
+
+ onos> app activate routeradvertisement
+
+Behavior of RA application is controlled by ONOS component configuration subsystem and following are possible configuration options.
+
+- ``raThreadDelay``: Delay between consecutive RA transmissions
+- ``raPoolSize``: Capacity of thread pool to be used for RA transmissions
+- ``raFlagMbitStatus``: RA flag “Managed address configuration” enabled/disabled
+- ``raFlagObitStatus``: RA flag “Other configuration” enabled/disabled
+- ``raOptionPrefixStatus``: RA Option “prefix” is enabled/disabled. Router prefixes will be available in RA only if this flag is “true”
+- ``raGlobalPrefixConfStatus``: Enable switch level global prefix configuration.
+ Once “raGlobalPrefixConfStatus” is enabled, RA prefix option is generated from port configuration of device, see for more details.
+
+Prefix details are picked up from network interface configuration.
+RA app will filter out link-local IPs while preparing prefixes.
+For example, in following configuration, Prefix will include only **2001:0558:FF10:04C9::2:1ff/120**.
+
+.. code-block:: json
+
+ {
+ "ports": {
+ "of:0000000000000018/16": {
+ "interfaces": [{
+ "ips": [ "192.168.114.1/24", "2001:0558:FF10:04C9::2:1ff/120", "FE80::4EA8:2AFF:FE24:8E5F/120" ],
+ "vlan-untagged": "11",
+ "name": "18-15",
+ "mac": "8c:ea:1b:67:24:90"
+ }]
+ }
+ }
+ }
+
+Global prefix configuration
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+In some cases, users may want to have a set of global prefix **advertised on all edge interfaces**.
+Such prefixes can be configured in **devices** section of network configuration in the following way.
+
+.. code-block:: json
+
+ {
+ "devices": {
+ "of:0000000000000018": {
+ "routeradvertisement" : {
+ "prefixes": [ "2001:0558:FF10:04C9::3:1ff/120"]
+ }
+ }
+ }
+ }
+
+.. note::
+ When global prefix is configured, RA app will ignore any prefixes configured on switch interfaces.
+
+Notes about interface config
+----------------------------
There is no need to configure ports on switches that are meant to connect to other switches.
The VLAN (untagged or tagged) configuration is only meant for ports that are connected to hosts (edge ports).