summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/appendix/vyos-on-clouds.rst7
-rw-r--r--docs/system/flow-accounting.rst4
2 files changed, 9 insertions, 2 deletions
diff --git a/docs/appendix/vyos-on-clouds.rst b/docs/appendix/vyos-on-clouds.rst
index 7fbd1b04..33b7011e 100644
--- a/docs/appendix/vyos-on-clouds.rst
+++ b/docs/appendix/vyos-on-clouds.rst
@@ -98,6 +98,13 @@ Deploy VyOS on Azure.
ssh -i ~/.ssh/vyos_azure vyos@203.0.113.3
vyos@vyos-doc-r1:~$
+Add interface
+-------------
+
+If instance was deployed with one **eth0** ``WAN`` interface and want to add new one.
+To add new interface an example **eth1** ``LAN`` you need shutdown the instance. Attach the interface in the Azure portal and then start the instance.
+
+.. NOTE:: Azure does not allow you attach interface when the instance in the **Running** state.
References
----------
diff --git a/docs/system/flow-accounting.rst b/docs/system/flow-accounting.rst
index 64c20dcf..f09c1c9a 100644
--- a/docs/system/flow-accounting.rst
+++ b/docs/system/flow-accounting.rst
@@ -39,8 +39,8 @@ NetFlow is usually enabled on a per-interface basis to limit load on the router
components involved in NetFlow, or to limit the amount of NetFlow records
exported.
-Configururation
-===============
+Configuration
+=============
In order for flow accounting information to be collected and displayed for an
interface, the interface must be configured for flow accounting.