VTN does not configure nodes until switches are connected
Change-Id: I20ec07d41c22af288a64b940e8697df9590127e6
(cherry picked from commit 2e29a4c594e45424167aeda4b0a974a440ad413e)
diff --git a/docs/appendix_basic_config.md b/docs/appendix_basic_config.md
index 1b9ed23..6301ad0 100644
--- a/docs/appendix_basic_config.md
+++ b/docs/appendix_basic_config.md
@@ -13,14 +13,12 @@
Log into the XOS GUI an click on `Core`, then `Tags`. Each compute node is tagged with its data plane IP address. For nodes connected to leaf2, change the `dataPlaneIp` tag to a unique IP address on the `10.6.2.0/24` subnet and click `Save`.
-XOS will communicate the new IP address to the ONOS VTN app, which will change it on the nodes. Log into each compute node and verify that `br-int` has the new IP address:
+XOS will communicate the new IP address to the ONOS VTN app, which will change it on the nodes. Once the switches are connected to ONOS as part of the fabric configuration process (see subsequent sections), log into each compute node and verify that `br-int` has the new IP address:
```
ip addr list br-int
```
->NOTE: It can take several minutes to complete the IP address change
-
###Add Routes to Fabric Subnets
Routes must be manually configured on the compute nodes so that traffic between nodes on different leaves will be forwarded via the local spine switch.