Vyatta Network OS Documentation

Learn how to install, configure and operate the Vyatta NOS, which helps drive our virtual networking & physical platforms portfolio.

Show Page Sections

Testing the system

After the system has successfully booted, you see the vyatta login: prompt. This prompt indicates that the system is operational.

Check the Vyatta NOS release version and host system type

How to check that the Vyatta NOS environment is as you expect.

  1. At the vyatta login: prompt, log in with the username and password that you set when you installed Vyatta NOS.
  2. Enter show version. Check that the system response displays the details that you expect.
    • The Version: field displays the version number of the system that is running — is this the version that you require and that you expected?
    • The System type: field displays the type of hardware on which the system is running and whether it is in a virtual environment — does this meet your needs, is it as you expected?
    • The Boot via: field displays the type of system that is running — is this as you expected?
  3. If any of the details do not match your expectations, investigate further.

Check the connectivity of Vyatta NOS and the host system

How to check that you can reach Vyatta NOS over the local network. A simple method in which you create an Ethernet interface on the system and then ping this interface from another host on the network.

Note: In the system, a data plane interface is an abstraction that represents the underlying physical or virtual Ethernet interface of the system. The terms Ethernet interface and data plane interface are synonymous in this guide.

In this example, we use addresses as follows:

  • Network address: 192.168.1.0/24
  • IP address of the interface: 192.168.1.81

You should of course substitute addresses that are appropriate for your specific environment.

  1. At the command prompt, enter these commands.
    user@system:~$ configure
    user@system# set interfaces dataplane dp0sN address 192.168.1.81/24
    user@system# commit
    user@system# save
    user@system# exit
    user@system:~$
  2. From another host on the same subnet, use the command prompt to ping the interface to ensure that it is active.
    ping 192.168.1.81
    If the response to the command shows replies from the interface then your system is installed and accessible on your network. Otherwise, you will need to investigate further.