diff --git a/xos/configurations/cord/README-VTN.md b/xos/configurations/cord/README-VTN.md
index 8c25be8..c923dbb 100644
--- a/xos/configurations/cord/README-VTN.md
+++ b/xos/configurations/cord/README-VTN.md
@@ -18,13 +18,16 @@
     # not still an issue lurking...
     cat > /usr/local/etc/neutron/plugins/ml2/conf_onos.ini <<EOF
     [ml2_onos]
-    url_path = http://$ONOS_VTN_HOSTNAME:8181/onos/vtn
+    url_path = http://$ONOS_VTN_HOSTNAME:8181/onos/openstackswitching
     username = karaf
     password = karaf
     EOF
     emacs /etc/neutron/plugins/ml2/ml2_conf.ini
         update settings as per vtn docs ([ml2] and [ml2_type_vxlan] sections)
-    systemctl restart neutron-server
+    systemctl stop neutron-server
+    # I started neutron manually to make sure it's using exactly the right config
+    # files. Maybe it can be restarted using systemctl instead...
+    /usr/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /usr/local/etc/neutron/plugins/ml2/conf_onos.ini
 
 Compute node that has the ONOS Container
 
@@ -36,11 +39,15 @@
 Compute nodes (all of them):
 
     systemctl stop neutron-plugin-openvswitch-agent
-    /usr/share/openvswitch/scripts/ovs-ctl
+    emacs /usr/share/openvswitch/scripts/ovs-ctl
         update settings as per vtn docs to make port 6640 visible
     service openvswitch-switch restart
+    ovs-vsctl del-br br-int
 
 VTN doesn't seem to like cloudlab's networks (flat-net-1, ext-net, etc). You might have to delete them all.
 
 For development, I suggest using the bash configuration (remember to start the ONOS observer manually) so that 
 there aren't a bunch of preexisting Neutron networks and nova instances to get in the way. 
+
+Problems:
+* If you have more than one compute node, then the node that isn't running ONOS VTN will report as incomplete in VTN. This is because the openvswitch is trying to contact VTN on 172.17.0.2:6653.