Running OcNOS in GNS3 Quick Start Guide 06 23
Running OcNOS in GNS3 Quick Start Guide 06 23
Contents
About the OcNOS VM............................................................................................................................................... 2
Benefits of the OcNOS VM................................................................................................................................................... 2
Feature List................................................................................................................................................................................ 2
3. Import an Example GNS3 Project called BGP and L3 VPN on the Remote GNS3 VM........................................ 7
References................................................................................................................................................................... 14
OcNOS.....................................................................................................................................................................................14
GNS3........................................................................................................................................................................................14
Appendix-A - Example BGP and L3 VPN Configuration Used in the GNS3 Environment....................... 15
CSR-1 Switch Configuration................................................................................................................................................15
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
Commercial off-the-shelf (COTS) hardware platforms switches from Dell, Delta Agema, Edgecore,
and UFISpace. For the complete feature list, please contact IP Infusion Sales.
core
Aggregation
PE
One Cell Site Router (CSR), three Aggregation Routers (AGGR) and a core router are used in this GNS3
test topology. Two Debian Linux servers are used in GNS3 for generating the test traffic.
• We will be using GNS3 project image that contains the following VMs: five OcNOS VMs (version
6.3.0 Build 126) with BGP and L3 VPN configuration, and 2 Debian Linux Servers.
The GNS3 VM gets its IP address 10.10.25.127 and TCP port 80 in this example from the DHCP
server and the IP address is displayed on the console. The credentials for login are also given in
the console: username is gns3 and password is gns3. The Web URL to access the GNS
environment is given as http://10.10.25.127.
Select Server Summary tab, you will see the Main Server running with green color status.
Click OK. Press Play button at the top to start all devices in GNS3 project.
Please note: Management IP addresses for your OcNOS switches will be different than the ones given
in the above screen. You need to edit the above screen to change Management IP addresses. To get
the Management IP address of a specific switch, please use the info provided in the section. To edit the
screen to change the Management IP address, click the Pencil Icon at the top menu.
Now on you can SSH to the switch using the following command from your laptop CLI:
ssh [email protected] and enter password as ocnos. You can use SSH session for running
verification commands listed in later section.
c. Check TEST_VRF forwarding table: Following output shows we have path to reach the second server.
d. Check for path to AGGR-3 in MPLS forwarding Table: Run the following command in CSR-1.
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.
g. Check L3VPN routes: Use the following command to display information relating to MPLS VPN.
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, right click on the link between the CSR-1 and the AGGR-1.
Select Suspend to stop the traffic flowing through that link as shown below. Now traffic will not
go through eth2 interface. Traffic will only go through eth3 interface.
Code FEC FTN-ID Nhlfe-ID Tunnel-id Pri LSP-Type Out-Label Out-Intf ELC Nexthop
L> 10.1.1.2/32 1 10 - Yes LSP_DEFAULT 24961 eth3 No
10.1.1.103
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
L> 10.1.1.5/32 4 20 - Yes LSP_DEFAULT 24963 eth3 No
10.1.1.103
L> 10.1.1.104/31 5 27 - Yes LSP_DEFAULT 24964 eth3 No
10.1.1.103
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
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:
• OcNOS Configuration Guides
GNS3
The following are reference materials related to GNS3:
• Getting Started with GNS3
!
no service password-encryption
!
logging console 2
logging monitor 7
logging cli
!
ip vrf management
!
ip vrf TEST_VRF
rd 10.1.1.1:1
route-target both 65000:1
!
hostname CSR-1
ip domain-lookup
feature telnet
feature ssh
feature rsyslog
!
router ldp
router-id 10.1.1.1
transport-address ipv4 10.1.1.1
!
!
interface lo
ip address 127.0.0.1/8
ip address 10.1.1.1/32 secondary
ipv6 address ::1/128
ip router isis 1
!
interface eth0
ip vrf forwarding management
ip address dhcp
!
interface eth1
ip vrf forwarding TEST_VRF
ip address 30.1.1.1/24
!
interface eth2
ip address 10.1.1.100/31
label-switching
mpls ldp-igp sync isis level-1
!
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
!
no service password-encryption
!
logging console 2
logging monitor 7
logging cli
!
ip vrf management
!
hostname AGGR-1
no ip domain-lookup
ip domain-lookup vrf management
feature telnet vrf management
feature ssh vrf management
feature rsyslog vrf management
!
router ldp
router-id 10.1.1.2
transport-address ipv4 10.1.1.2
!
!
interface lo
ip address 127.0.0.1/8
ip address 10.1.1.2/32 secondary
ipv6 address ::1/128
ip router isis 1
!
interface eth0
ip vrf forwarding management
ip address dhcp
!
interface eth1
ip address 10.1.1.101/31
label-switching
mpls ldp-igp sync isis level-1
isis network point-to-point
ip router isis 1
enable-ldp ipv4
lldp-agent
set lldp enable txrx
exit
!
interface eth2
ip address 10.1.1.104/31
label-switching
mpls ldp-igp sync isis level-1
isis network point-to-point
ip router isis 1
enable-ldp ipv4
lldp-agent
!
no service password-encryption
!
logging console 2
logging monitor 7
logging cli
!
ip vrf management
!
hostname AGGR-2
no ip domain-lookup
ip domain-lookup vrf management
feature telnet vrf management
feature ssh vrf management
feature rsyslog vrf management
!
router ldp
router-id 10.1.1.3
transport-address ipv4 10.1.1.3
!
!
interface lo
ip address 127.0.0.1/8
ip address 10.1.1.3/32 secondary
ipv6 address ::1/128
ip router isis 1
!
interface eth0
ip vrf forwarding management
ip address dhcp
!
interface eth1
ip address 10.1.1.103/31
label-switching
mpls ldp-igp sync isis level-1
isis network point-to-point
ip router isis 1
enable-ldp ipv4
lldp-agent
set lldp enable txrx
exit
!
interface eth2
ip address 10.1.1.106/31
label-switching
mpls ldp-igp sync isis level-1
isis network point-to-point
ip router isis 1
enable-ldp ipv4
lldp-agent
no service password-encryption
!
logging console 2
logging monitor 7
logging cli
!
ip vrf management
!
hostname core-1
no ip domain-lookup
ip domain-lookup vrf management
feature telnet vrf management
feature ssh vrf management
feature rsyslog vrf management
!
router ldp
router-id 10.1.1.4
transport-address ipv4 10.1.1.4
!
interface lo
ip address 127.0.0.1/8
ip address 10.1.1.4/32 secondary
ipv6 address ::1/128
ip router isis 1
!
interface eth0
ip vrf forwarding management
ip address dhcp
!
interface eth1
ip address 10.1.1.108/31
label-switching
mpls ldp-igp sync isis level-1
isis network point-to-point
ip router isis 1
enable-ldp ipv4
lldp-agent
set lldp enable txrx
exit
!
interface eth2
ip address 10.1.1.105/31
label-switching
mpls ldp-igp sync isis level-1
isis network point-to-point
ip router isis 1
enable-ldp ipv4
lldp-agent
set lldp enable txrx
exit
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.