Question

How to install Versa FlexVNF on a white box using USB?


Solution

Follow these steps to create and boot Versa FlexVNF on an a white box using an USB:

  1. Create a bootable USB drive. Follow one of these methods (as published by Ubuntu):

          *Please download the ISO file for the required image.


Detailed Steps: https://docs.versa-networks.com/Getting_Started/Deployment_and_Initial_Configuration/Branch_Deployment/Installation/Install_on_Bare_Metal


  1. Boot from the USB drive.
    • After the White box boots up with the USB drive, it displays the boot: prompt.
    • Run the versa-branch-usb command and click <Enter>.

    • Press <SPACE> when prompted for the video mode.


Since this process is automated, the installation finishes after this step. 


Note:  

  1. If you get an error "Your installation CD-ROM couldn't be mounted.."  then please remove the USB drive from the device and re-insert it. Wait for 5 seconds and then choose the <Yes> option to retry mounting the CD-ROM
  2. If you are installing on a system where the hard disk already had partitions, you may get prompted to Unmount partitions in use. Choose <Yes> and continue the installation.



NOTE: After installation, eth0 comes up with the static address of 10.10.10.10/8.


Validating Installation

Follow these steps to validate the successful installation of Versa FlexVNF on the white box:

  1. Login to the White box using the console. The box must be connected at a baud rate of 115200.

    Default Login Credentials:
    Username: admin
    Password: versa123


2. Run the cli comand to enter the CLI mode.

3. Run the show interface brief|tab|nomore [CLI command].


Command output:

admin@versa-flexvnf-cli> show interfaces brief | tab | nomore
NAME       MAC                OPER   ADMIN  TENANT  VRF                        IP
-----------------------------------------------------------------------------------------------
eth-0/0    74:fe:48:09:3a:ae  up     up     0       global           10.10.10.10/8
tvi-0/0    n/a                up     up     -       -
tvi-0/0.0  n/a                pdown  up     1       Versa-Provider-Control-VR
tvi-0/1    n/a                up     up     -       -
tvi-0/1.0  n/a                pdown  up     1       Versa-Provider-Control-VR
vni-0/0    74:fe:48:07:d5:73  down   up     -       -
vni-0/0.0  74:fe:48:07:d5:73  down   up     1       WAN1-Transport-VR
vni-0/0.1  74:fe:48:07:d5:73  down   up     1       WAN1-Transport-VR
vni-0/1    74:fe:48:09:3a:af  down   up     -       -
vni-0/1.0  74:fe:48:09:3a:af  down   up     1       global           192.168.1.1/24
vni-0/2    74:fe:48:07:d5:70  down   up     -       -
vni-0/2.0  74:fe:48:07:d5:70  down   up     1       WAN1-Transport-VR
vni-0/2.1  74:fe:48:07:d5:70  down   up     1       WAN1-Transport-VR
vni-0/3    74:fe:48:07:d5:74  down   down   -       -
vni-0/4    74:fe:48:09:3a:ad  down   down   -       -

[ok][2018-02-02 19:11:31]
admin@versa-flexvnf-cli>


  • Check for this line in the command output.
    vni-0/1.0  74:fe:48:09:3a:af  down   up     1       global           192.168.1.1/24



  • If this line does not appear in the output, wait for 2 minutes and go back to Step 3.
    Alternatively, you can click the up arrow button to reenter the last used command. 
  • Power-Off the White box when the above line appears in the command output.



Steps to Load Default Configuration

Versa software installs default device configuration upon first boot in the factory. If the system is rebooted before the software has had a chance to load the config then the system is left without the default config.

Follow these steps when the validation procedure mentioned in the section above (Validating Installation) fails:

  1. Run the cli shell command to enter the CLI mode.
  2. Run the config command to enter the configuration mode.
  3. In config mode, enter load merge /opt/versa/etc/bootcfg/default-device.cfg filepath to install the default configuration.
  4. Run the commit command to save and commit the default configuration.
  5. Run the show interface brief|tab|nomore CLI command to check for the interface status.

Example:

admin@Controller1:~$ cli


             .---.,
            (      ``.
       _     \        )    __      ________ _____   _____
      (  `.   \      /     \ \    / /  ____|  __ \ / ____|  /\
       \    `. )    /       \ \  / /| |__  | |__) | (___   /  \
        \     |    /         \ \/ / |  __| |  _  / \___ \ / /\ \
         \    |   /           \  /  | |____| | \ \ ____) / ____ \
          \   |  /             \/   |______|_|  \_\_____/_/    \_\
           \  | /
            \_|/                   _  _ ___ _______      _____  ___ _  _____
                                  | \| | __|_   _\ \    / / _ \| _ \ |/ / __|
                                  | .` | _|  | |  \ \/\/ / (_) |   / ' <\__ \
                                  |_|\_|___| |_|   \_/\_/ \___/|_|_\_|\_\___/



admin connected from 10.40.40.1 using ssh on Controller1
admin@Controller1-cli> conf
Entering configuration mode private
[ok][2018-07-06 12:41:24]

[edit]
admin@Controller1-cli(config)% load merge /opt/versa/etc/bootcfg/default-device.cfg
[ok][2018-07-06 12:41:27]

[edit]
admin@Controller1-cli(config)% commit