Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
DANOS can then be installed inside the VM by typing "install image"
If in doubt accept the default response to the installation questions.. 
Enter and then re-enter a password for the default account (for example vyatta), and then
type "yes" when asked to “Continue”.
Type reboot (it will come back to the same point since the VM will still boot from the ISO volume not the newly created disk image)

J. Delete the server created from the iso but preserving the disk image

Code Blockopenstack server delete INSTANCE_NAMEBefore you run “install image” it may be appropriate to modify /config/config.boot to use dhcp on the dp0s3 interface and to activate the ssh service so that we can use ssh for the configuration. You typically can not copy/paste in the console window via horizon so you will have to type this in.

Code Block
interfaces {
      loopback 

...

lo
      dataplane dp0s3 {
          address dhcp
      }
}
service {
     ssh
}

...

Save the file and then run “install image”

after the update to /dev/vda2 is complete , you can simply exit out of the console

J. Delete the server created from the iso but preserving the disk image

Code Block
openstack server delete INSTANCE_NAME 
   
openstack server delete danosVRRFromISO

"openstack volume list" will show the preserved volume danosVRRVolume as available once the instance is deleted.

+--------------------------------------+----------------+--------+------+------------------------------------------+
| ID | Name | Status | Size | Attached to |
+--------------------------------------+----------------+--------+------+------------------------------------------+
| 21133635-433f-4411-8a40-9fbca1a59a07 | danosVRRVolume | in-use | 8 | Attached to danosVRRFromISO on /dev/vda |
+--------------------------------------+----------------+--------+------+------------------------------------------+

...

Configure the external network port since we did not enable cloud-init

a. show interfacesb. enter config mode and add the external network (get ip address from horiazon ) so we don't have to use console anymoreset interfaces dataplane dp0s3 address 10.0.200.135/24 # replace 10.0.200.135 with your external ip address
set protocols static route 0.0.0.0/0 next-hop 10.0.200.1 # replace 10.0.200.1 with your gateway ip address
set service ssh
set service ssh allow-root
set service ssh listen-address 10.0.200.135

if the update to config.boot worked correctly show interfaces should show the IP address on dp0s3. If so you can move to Step N. If not then:
b. enter config mode and add the external network (get ip address from horizon ) so we don't have to use console anymore

config

set interfaces dataplane dp0s3 address dhcp
set service ssh
commit
exit
show interfaces @ should show dp0s3 as u/u

N. Login to the instance via SSH on the external port since console is slow

login via ssh: ssh vyatta@10.0.200.135 135 # using your ip

vyatta@vyatta:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Speed/Duplex Description

...

O. Add configuration for the 3 others ports on the private networks using ip address from horizonip address from horizon

you can either set the static IP addresses or set them as address ‘dhcp’

config
set interfaces dataplane dp0s4 address 192.168.101.222/24
set interfaces dataplane dp0s5 address 192.168.102.216/24
set interfaces dataplane dp0s6 address 192.168.103.227/24
commit
exit

or

config
set interfaces dataplane dp0s4 address dhcp
set interfaces dataplane dp0s5 address dhcp
set interfaces dataplane dp0s6 address dhcp
commit
exit

NOTE: you could have done all three dataplane interfaced in config.boot if you wanted but for real world examples you would likely set these per instance and they would not likely be dhcp based.


show interfaces

vyatta@vyatta:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Speed/Duplex Description

...

dp0s3 10.0.200.135/24 u/u a-10g/a-full
dp0s4 192.168.101.222/24 u/u a-10g/a-full
dp0s5 192.168.102.216/24 u/u a-10g/a-full
dp0s6 192.168.103.227/24 u/u a-10g/a-full

P. you can also Optionally start NETCONF if you want
set service netconf

Danos should now route for the 192.168.101, 102 and 103 networks but we need to setup the routing on the trafficSource and the trafficSink.

...