Running Multiple OcNOS VMs in EVE NG Quick Start Guide 07023
Running Multiple OcNOS VMs in EVE NG Quick Start Guide 07023
Running Multiple
OcNOS® VMs in EVE-NG
Quick Start Guide
August 2023
Contents
About the OcNOS VM............................................................................................................................................... 2
Benefits of the OcNOS VM................................................................................................................................................... 2
Feature List................................................................................................................................................................................ 2
Running Multiple OcNOS switches in the EVE-NG............................................................................................ 3
System Requirements for Running OcNOS VMs in EVE-NG............................................................................ 3
Files Provided for Running OcNOS VMSs in EVE-NG........................................................................................ 4
Setup the EVE-NG Environment for Validating BGP and L3 VPN................................................................... 4
1. Install the EVE-NG VM in the VMware vSphere Hypervisor.................................................................................... 4
2. Install EVE-NG Client side pack....................................................................................................................................... 8
3. Install Linux Ubuntu 21.04 Server in the EVE-NG...................................................................................................... 9
4. Install OcNOS VM in the EVE-NG ................................................................................................................................. 9
5. Set up BGP and L3 VPN Lab on the EVE-NG...............................................................................................................10
6. Verify BGP and L3 VPN Project.......................................................................................................................................17
References................................................................................................................................................................... 20
OcNOS.....................................................................................................................................................................................20
EVE-NG....................................................................................................................................................................................20
Appendix-A - Example BGP and L3 VPN Configuration Used in the EVE-NG Environment.................. 21
CSR-1 Switch Configuration................................................................................................................................................21
AGGR-1 Switch Configuration............................................................................................................................................23
AGGR-2 Switch Configuration............................................................................................................................................25
CORE-1 Switch Configuration............................................................................................................................................27
AGGR-3 Switch Configuration............................................................................................................................................29
About the OcNOS VM
The OcNOS Virtual Machine (VM) from IP Infusion helps you get familiar with OcNOS. The OcNOS
VM runs on a standard x86 environment. The OcNOS VM is used to validate configurations and test
L2, L3, and MPLS features at your own pace, with no costs associated. Without bare metal switches,
OcNOS VM can be on popular open-source software emulators EVE-NG and GNS3, and hypervisors
including KVM, VirtualBox, and VMware. This document provides information on how to run OcNOS
VM in the EVE-NG environment.
All basic Layer 2, Layer 3, and multicast functionality are available. MPLS support is also available,
including limited support of MPLS forwarding. The OcNOS VM comes with a 365 days valid license.
The data plane forwarding functions have limited support. OcNOS VM is designed for feature testing,
and not for data plane performance testing or full bandwidth traffic testing.
Feature List
CLIs for the following features are available. The complete feature set of OcNOS is supported on
hardware platforms such as the whitebox switches from Dell, Delta Agema, Edgecore, and UFISpace.
For the complete feature list, please contact IP Infusion Sales.
SYSTEM FEATURES • VLAN Interface
• ARP support • QinQ
• SSH/Telnet • 802.1x
• SNMP LAYER-3 FEATURES
• Debugging and logging • IPv4 Routing
• AAA • VRF Support
• DHCP, DNS • RIP v2, RIP NG
LAYER-2 FEATURES • BFD with BGP, OSPF, ISIS
• STP/RSTP/MSTP • BGP
• BPDU Guard and Root Guard • OSPF v2, OSPF v3
• VLAN, Private VLAN • ISIS
• LACP • VRRP
• LLDP
One Cell Site Router (CSR), three Aggregation Routers (AGGR) and a core router are used in this EVE-NG
test topology. Two Debian Linux servers are used in EVE-NG environment for generating the test traffic.
2. ocnos.yml: This is OcNOS QEMU VM Template. You can import this template to create OcNOS
VMs in EVE-NG.
4. BGP-L3VPN-switches-config.zip: Configuration files for the topology given in this document. You
can copy the configuration given in these files to corresponding OcNOS switch in EVE-NG
environment.
2. Install EVE-NG Client Side pack that will install everything necessary for running telnet, vnc and
wireshark when working on Building labs
3. Install Linux Ubuntu 21.04 Server in the EVE-NG for generating and receiving test traffic.
a. Download the EVE-NG OVF Template Community Version to run in the VMware vSphere ESXi
hypervisor. In this example EVE-NG VM version 5.0.1-19 and VMware ESXi version 7.0.3 are
used for testing.
b. Install EVE-NG VM: Import EVE-NG OVF template to create a VM named EVE-NG-VM in ESXi
server using the downloaded OVF file by following the instructions from this video. Make sure
the VM Network to which EVE-NG-VM is connected is set to Accept Promiscuous mode as
instructed in the video. This allows the VM to send multiple MAC addresses to the switches.
c. Configure EVE-NG-VM: After you install the EVE-NG-VM, turn off the VM power, select edit
settings and expand CPU to check the nested VM support in the ESXi server. Hardware
Virtualization needs to be enabled in this case as shown below.
The EVE-NG-VM gets its IP address 10.10.25.234. The default credentials for login are also
given in the console: username is root and password is eve. The Web URL to access the
EVE-NG-VM environment is given as http://10.10.25.234.
Repeat enter root user’s password again and click return. Then set new password for root user
and hit return and repeat the same thing to confirm the new password set for root and hit return.
Enter the DNS domain name as shown below and hit return
In this example we are not using any Proxy to reach the Internet.
Hence we will choose direct connection and hit return.
From the EVE-NG-VM console, enter the username as root and enter the newly set password
earlier in this section. Verify the management IP address by executing the command ifconfig
pnet0. You can see EVE-NG-VM’s management IP address is 10.10.25.234. Verify whether
EVE-NG_VM can access Internet by executing the command ping example.com as shown below.
Now let us access the EVE-NG_VM from the web browser using URL http://10.10.25.234 and
verify login using default credentials: admin/eve
a. Download the EVE-NG Client Side pack based on your laptop type.
i. Windows Version
c. Install the EVE-NG side pack on your laptop. If you get permission error on MacOS laptop, do
the following: Open System Preferences -> Security & Privacy -> General and click Open Anyway.
a. Download the Linux Ubuntu 22.04 server image from here to your laptop.
b. Copy the Linux server image from your laptop to EVE-NG VM as follows. You can also copy file
using WinSCP or FileZilla:
c. Log into EVE-NG and execute following commands to install the Ubuntu Server in EVE-NG:
cd /opt/unetlab/addons/qemu/
tar xzvf linux-ubuntu-22.04-server.tar.gz
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
Verify management IP address using the following command:
a. Copy the ocnos.yml template file to EVE-NG as follows. You can also copy file using WinSCP or
FileZilla.
SSH into EVE-NG and execute following commands for copying OcNOS-VM image to the
EVE-NG:
cd /opt/unetlab/addons/qemu/
mkdir ocnos-SP-MPLS-x86-6.3.0-126-GA
Please Note: Name of the directory need to start with the same name phrase associated with
the Template file name. “ocnos” prefix is used in this example.
From your laptop copy the downloaded OcNOS VM image (uncomoressed version) to EVE-NG
as follows:
root@eve-ng-vm:~# cd /opt/unetlab/addons/qemu/OcNOS-SP-MPLS-x86-6.3.0-126-GA
root@eve-ng-vm:/opt/unetlab/addons/qemu/OcNOS-SP-MPLS-x86-6.3.0-126-GA# mv
OcNOS-SP-MPLS-x86-6.3.0-126-GA.qcow2 virtioa.qcow2
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
a. Login to EVE-NG Web UI by accessing the EVE-NG_VM from the web browser using URL
http://10.10.25.234 and verify login using default credentials: admin/eve
Click Add new lab icon enter the new lab Name as shown below and click Save.
Following is the topology we are going to setup in the BGP and L3 VPN lab.
c. Add Management Network: Right click on the new Lab page and select Network as shown
below.
Following are steps to set up five OcNOS switches as part of BGP and L3 VPN Lab in EVE-NG.
i. Set up first OcNOS node: Right click on the new Lab page and select Node as shown
below.
Right click on the CSR-1 device and click Start as shown below.
ii. Set up four more OcNOS switches: Setup four more OcNOS switches as shown in the
Topology picture given above by repeating steps mentioned in the item (i) for creating
each switch.
iv. Stop all the nodes and make connections as shown above: From the left menu click on
the More actions and select Stop all nodes.
v. Setup data plane connections between the OcNOS switches and Linux servers: Hover
over the device you want to connect, it will show a power plug sign as shown below.
Right click over the Power Plug and drag it to the other device you want to connect.
vi. Start all devices: From the left menu click on the More actions and select Start all nodes.
vii. Deploy configuration in each switch each: Double click on each switch icon to access
console. Enter into enable and configuration modes. Extract switches configuration
files from the BGP-L3VPN-switches-config.zip file you have downloaded earlier.
Copy corresponding switch file configuration and paste it on the switch (for example:
copy CSR-1.txt file and paste it on CSR-1) switch console in configuration mode and
commit the configuration.
CSR-1> en
CSR-1# conf t
CSR-1(config)# <paste the config>
CSR-1(config)# commit
Perform the following command to copy the configuration to persistent memory in the
switch.
CSR-1# copy running-config startup-config
Building Configuration...
[OK]
viii. Configure the Linux servers to setup for Traffic Testing: Double click on the first
server to open VNC console session to the server and login to the server.
root@ubuntu22-server# cd /etc/netplan
root@ubuntu22-server# su
Update the content of the file as follows and save the file:
Next change the name of the server as follows. Edit /etc/hostname file using vi editor
and change contents to Linux-Server-1 and save the file. Reboot the server to make
changes permanent.
root@ubuntu22-server# reboot
Similarly, double click on the second server to open VNC console session to the server
and login to the server. Set the IP address of ens3 interface to 40.1.1.200 using
commands shown above. Set the host name of second server to Linux-Server-2.
Reboot the server.
a. Generate Test Traffic: Log into the console of the Linux-Server-1 and execute the following
Linux shell command to send 1000 packets from the Linux-Server-1 Server to the Linux-Server-2
on the TEST_VRF.
debian@debian:~$ ping -c 1000 -i 1 40.1.1.200
PING 40.1.1.200 (40.1.1.200) 56(84) bytes of data.
64 bytes from 40.1.1.200: icmp_seq=1 ttl=63 time=4.15 ms
64 bytes from 40.1.1.200: icmp_seq=2 ttl=63 time=4.84 ms
64 bytes from 40.1.1.200: icmp_seq=3 ttl=63 time=5.45 ms
64 bytes from 40.1.1.200: icmp_seq=4 ttl=63 time=3.56 ms
64 bytes from 40.1.1.200: icmp_seq=5 ttl=63 time=3.63 ms
…
b. Check summary of known neighbor: Log into the console of the CSR-1 OcNOS virtual switch
(or SSH into CSR-1) and run the following commands to verify the BGP and L3 VPN
functionalities. The show clns neighbors command provides a summary of known neighbors,
the connecting interface, and the state of the adjacency.
CSR-1#show clns neighbors
c. Check TEST_VRF forwarding table: Following output shows we have path to reach the second server.
CSR-1# show mpls vrf-forwarding-table vrf TEST_VRF
Also check Incoming Label Map entries. Use the following command to view Incoming label
mapping (ILM) table entries
CSR-1#show mpls ilm-table
Codes: > - installed ILM, * - selected ILM, p - stale ILM
K - CLI ILM, T - MPLS-TP, s - Stitched ILM
S - SNMP, L - LDP, R - RSVP, C - CRLDP
B - BGP , K - CLI , V - LDP_VC, I - IGP_SHORTCUT
O - OSPF/OSPF6 SR, i - ISIS SR, k - SR CLI
P - SR Policy, U - unknown
Code FEC/VRF/L2CKT ILM-ID In-Label Out-Label In-Intf Out-Intf/VRF Nexthop LSP-Type
L> 10.1.1.106/31 11 24965 3 N/A eth3 10.1.1.103 LSP_DEFAULT
L> 10.1.1.3/32 7 24961 3 N/A eth3 10.1.1.103 LSP_DEFAULT
B> TEST_VRF 1 24320 Nolabel N/A TEST_VRF N/A LSP_DEFAULT
L> 10.1.1.2/32 13 24967 3 N/A eth2 10.1.1.101 LSP_DEFAULT
L> 10.1.1.104/31 14 24968 3 N/A eth2 10.1.1.101 LSP_DEFAULT
Code FEC FTN-ID Nhlfe-ID Tunnel-id Pri LSP-Type Out-Label Out-Intf ELC Nexthop
L> 10.1.1.2/32 1 32 - Yes LSP_DEFAULT 3 eth2 No 10.1.1.101
L> 10.1.1.3/32 2 14 - Yes LSP_DEFAULT 3 eth3 No 10.1.1.103
L> 10.1.1.4/32 3 16 - Yes LSP_DEFAULT 24962 eth3 No 10.1.1.103
48 - Yes LSP_DEFAULT 24962 eth2 No 10.1.1.101
L> 10.1.1.5/32 4 20 - Yes LSP_DEFAULT 24963 eth3 No 10.1.1.103
49 - Yes LSP_DEFAULT 24963 eth2 No 10.1.1.101
L> 10.1.1.104/31 5 32 - Yes LSP_DEFAULT 3 eth2 No 10.1.1.101
L> 10.1.1.106/31 6 14 - Yes LSP_DEFAULT 3 eth3 No 10.1.1.103
L> 10.1.1.108/31 7 28 - Yes LSP_DEFAULT 24965 eth3 No 10.1.1.103
50 - Yes LSP_DEFAULT 24966 eth2 No 10.1.1.101
You can see AGGR-5 can be reached via eth2 and eth3.
f. Check route between two Debian Servers: Check the route from one Debian Server to other
using the following command:
One server is directly connected to 30.1.1.0/24 network and other server in 40.1.1.0/24
network is accessible via BGP.
CSR-1#show ip route vrf TEST_VRF database
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2,
ia - IS-IS inter area, E - EVPN,
v - vrf leaked
> - selected route, * - FIB route, p - stale info
h. Stop flow of traffic between CSR-1 and AGGR-1 and verify whether traffic flows from one
server to the other:
When the ICMP traffic is flowing, let us stop the traffic between the CSR-1 and the AGGR-1.
To do this perform the following CLI commands in CSR-1 Switch.
CSR-1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
CSR-1(config)#int eth2
CSR-1(config-if)#shut
CSR-1(config-if)#commit
This will stop the traffic flowing between CSR-1 and AGGR-1. Now traffic will not go through
eth2 interface. Traffic will only go through eth3 interface.
Codes:
‘!’ - Success, ‘Q’ - request not sent, ‘.’ - timeout,
‘x’ - Retcode 0, ‘M’ - Malformed Request, ‘m’ - Errored TLV,
‘N’ - LBL Mapping Err, ‘D’ - DS Mismatch,
‘U’ - Unknown Interface, ‘R’ - Transit (LBL Switched),
‘B’ - IP Forwarded, ‘F’ No FEC Found, ‘f’ - FEC Mismatch,
‘P’ - Protocol Error, ‘X’ - Unknown code,
‘Z’ - Reverse FEC Validation Failed
References
OcNOS
The following are reference materials related to OcNOS:
EVE-NG
The following are reference materials related to EVE-NG:
!
router bgp 65000
bgp router-id 10.1.1.1
neighbor 10.1.1.2 remote-as 65000
neighbor 10.1.1.3 remote-as 65000
neighbor 10.1.1.2 update-source lo
neighbor 10.1.1.3 update-source lo
!
address-family vpnv4 unicast
neighbor 10.1.1.2 activate
neighbor 10.1.1.3 activate
exit-address-family
!
address-family ipv4 vrf TEST_VRF
redistribute connected
exit-address-family
!
line vty 0
exec-timeout 0 0
!
!
end
ABOUT IP INFUSION
IP Infusion is a leading provider of open network software and solutions for carriers, service providers and data center operators. Our solutions enable network operators to
disaggregate their networks to accelerate innovation, streamline operations, and reduce Total Cost of Ownership (TCO). Network OEMs may also disaggregate network devices
to expedite time to market, offer comprehensive services, and achieve carrier grade robustness. IP Infusion network software platforms have a proven track record in carrier-
grade open networking with over 500 customers and over 10,000 deployments. IP Infusion is headquartered in Santa Clara, Calif., and is a wholly owned and independently
operated subsidiary of ACCESS CO., LTD. Additional information can be found at http://www.ipinfusion.com
© 2023 IP Infusion, Inc. All rights reserved. IP Infusion is a registered trademark and the ipinfusion logo and OcNOS are trademarks of IP Infusion, Inc. All other trademarks
and logos are the property of their respective owners. IP Infusion assumes no responsibility for any inaccuracies in this document. IP Infusion reserves the right to change,
modify, transfer, or otherwise revise this publication without notice.