- Unfortunately GNS3 does not work with all versions of IOS, please see this official documentation for known working / recommended stable images. – Yevhen Stasiv Jan 10 '20 at 17:53 I use ASR9K-iosxr-k9-4.0.0 image.
- 'description': 'IOS XRv 9000 (aka Sunstone) is the 1st VM released running the 64-bit IOS XR operating system as used on the NCS-6xxx platform. This appliance requires 4 vCPUs and 16GB of memory to run!'
- May 24, 2004 Cisco IOS XR Software Release 3.5.2 for Cisco CRS-1 and XR 12000 Series Routers Field Notices Field Notice: FN - 63979 - ASR9000, CRS, and XR12000 That Run Cisco IOS-XR 5.3.0 and Earlier - Oct 17, 2015 SW Certificate Expiration - Software Upgrade Recommended 18-Jan-2019.
Here I am listing all the working versions of Cisco IOS which I have tested with the latest version of GNS3.
Update as on 14th May 2018 –
All the IOS, IOU, Nexus and other images has been updated, checked and verified with latest GNS3 & GSN3 VM. Download here – https://i.srijit.com/gns3images
Sep 16, 2017 In this post, we are going to deploy an IOS-XRv VirtualBox Image (a free demo image) in GNS3. First of all, we have to download an IOS-XRv VirtualBox Image on Cisco upload page. In this lab, we use IOS XRv 612 (iosxrv-k9-demo-6.1.2.ova). Bear in mind that we need a Cisco CCO account to download the image. Jul 14, 2014 GNS3 is an open source (GNU GPL) software that simulates complex networks while being as close as possible from the way real networks perform, all of this without having dedicated network hardware such as routers and switches.
Feel free to download them and use them for your Cisco certifications studies.
Old ones are kept intact for your reference-
- 1700 – http://i.srijit.com/CiscoIOS-GNS3
- 2600 – http://i.srijit.com/CiscoIOS-GNS3
- 2691 – http://i.srijit.com/CiscoIOS-GNS3
- 3640 – http://i.srijit.com/CiscoIOS-GNS3
- 3660 – http://i.srijit.com/CiscoIOS-GNS3
- 3725 – http://i.srijit.com/CiscoIOS-GNS3
- 3745 – http://i.srijit.com/CiscoIOS-GNS3
- 7200 (v15) – http://i.srijit.com/CiscoIOS-GNS3
- 7200p (v15) –http://i.srijit.com/CiscoIOS-GNS3
If you face any problem setting it up with GNS3 drop me a message and I will get back to you asap.
GNS3 is an open source (GNU GPL) software that simulates complex networks while being as close as possible from the way real networks perform, all of this without having dedicated network hardware such as routers and switches.
GNS3 provides an intuitive graphical user interface to design and configure virtual networks, it runs on traditional PC hardware and may be used on multiple operating systems, including Windows, Linux, and Mac OS X.
In order to provide complete and accurate simulations, GNS3 actually uses the following emulators to run the very same operating systems as in real networks:
- Dynamips, the well known Cisco IOS emulator.
- VirtualBox, runs desktop and server operating systems as well as Juniper JunOS.
- QEMU, a generic open source machine emulator, it runs Cisco ASA, PIX and IPS.
GNS3 is an excellent alternative or complementary tool to real labs for network engineers, administrators and people studying for certifications such as Cisco CCNA, CCNP andCCIE as well as Juniper JNCIA, JNCIS and JNCIE.
In the previous articles on MPLS, we have discussed MPLS Layer 3 VPN and the configurations involved. There is another type of MPLS VPN, which is called Layer 2 VPN. As the name implies, Layer 2 VPN doesn’t require any IP addresses from the service provider and it doesn’t require any routing protocol between customer and service provider routers. This is advantageous in that customers don’t need to worry how many routes they advertise to the service provider. Service providers often bill the customer depending on how many routes the customer advertise to the service provider’s MPLS network. From the customer’s perspective, the MPLS Layer 2 VPN is transparent to them.
MPLS Layer 2 VPN is similar in function and configuration as L2TPv3 (Layer 2 Tunnel Protocol Version 3). L2TPv3 is used to tunnel Layer 2 over IP networks and is widely used on the Internet. MPLS Layer 2 VPN functions in the same way but is used in the MPLS environment. These two protocols provide a “pseudo-wire” service, which means that they can emulate point-to-point connection over an IP network.
MPLS Layer 2 VPN has three types of connections, namely:
AToM (any transport over MPLS)—This is a point-to-point service and, as the name implies, AToM can be used in Ethernet, frame-relay, serial and PPP connections.
Interworking—This is a point-to-point service as well and considered an extension to AToM. Interworking is a feature that enables two connections of different handoffs (e.g., Ethernet-serial or POS – Ethernet) to be connected as a point-to-point link.
VPLS (virtual private LAN service)—This is a broadcast service, which means that the MPLS network emulates a Layer 2 switch. Several network devices can be connected into one broadcast domain as if they are connected in one local area network. VPLS is hardware-specific and is only supported on Cisco carrier-grade devices that run IOS-XR.
Interworking and VPLS are not supported in GNS3. We will be doing labs for different types of AToM connections. Here are the diagram and tasks:
- Build an MPLS network. Configure OSPF between the service provider devices. Announce their Loopback0 into OSPF. Configure LDP between the SP devices.
- Configure Ethernet over MPLS AToM between CUSTA-R1 and CUSTA-R2. Configure IP addresses and verify connectivity.
- Configure PPP over MPLS AToM between CUSTA-R1 and CUSTB-R2. Configure IP addresses and verify connectivity.
- Configure frame relay over MPLS AToM between CUSTB-R1 and CUSTB-R2. Verify connectivity.
Task 1: Build MPLS network. Configure OSPF between the service provider devices. Announce their Loopback0 into OSPF. Configure LDP between the SP devices.
Let’s verify LDP neighborship and check if PE1 and PE2 have LDP bindings on their Loopback0 IP addresses. It is important to have LDP Bindings for the Loopback IP addresses of PE1 and PE2, otherwise Layer 2 VPN will not work.
We have confirmed that there are label switch paths to reach 126.96.36.199/32 and 188.8.131.52/32. Let’s proceed to do Task 2.
Task 2: Configure Ethernet over MPLS AToM between CUSTA-R1 and CUSTA-R2. Configure IP addresses and verify connectivity.
Now let’s verify what happens to the MPLS forwarding table and then we’ll issue some commands.
When we issue the “show mpls forwarding-table” command, we see that there is a new entry “l2ckt(102).” This is the pseudowire label. Similar to Layer 3 VPN, this pseudowire label makes the connection unique. The “show mpls l2transport vc 102” command indicates that, for VC 102, the traffic needs to go to 184.108.40.206.
Let’s break down the commands we entered above.
pseudowire-class ETHERNET specifies that the pseudo wire class name is ETHERNET.
encapsulation mpls indicates MPLS is the encapsulation. L2TPv3 is another option here.
xconnect 220.127.116.11 102 pw-class ETHERNET is the command that enables Layer 2 VPN on the interface. This basically indicates that all traffic from this interface should be forwarded to PE-R2 18.104.22.168. The configuration on PE-R2 should indicate 22.214.171.124 in the xconnect configuration to establish the Layer 2 VPN connection. 102 is the VC identifier and should be identical on both routers and should be unique on the two PE routers. The pw-class command just calls the pseudowire class ETHERNET. The pseudowire name doesn’t need to match on both routers, as this is locally significant.
Let’s test connectivity between CUSTA-R1 and CUSTA-R2.
Even CDP is showing that CUSTA-R2 is directly connected to CUSTA-R1.
Task 3: Configure PPP over MPLS AToM between CUSTA-R1 and CUSTB-R2. Configure IP addresses and verify connectivity.
Install Ios Xr On Gns3
Configuration is similar to the Ethernet AToM configuration. The only difference here is the encapsulation command. PPP authentication can be added to the customer routers if desired. Verify connectivity.
Task 4: Configure frame relay over MPLS AToM between CUSTB-R1 and CUSTB-R2. Verify connectivity.
The frame-relay Layer 2 VPN configuration will be slightly different from the rest. Instead of declaring a pseudo-wire class, the “connect” command is used. The PE routers will be configured as a frame-relay switch.
Let’s break down these two commands and understand what they are for.
connect R2-R3 Serial1/1 203 l2transport is basically the equivalent for the pseudo wire class. The Se1/1 is the interface where the succeeding xconnect command will be applied. 203 in this case is the DLCI number. The same value should be configured on the corresponding CE router.
Ios Xr Gns3 Specs
xconnect 126.96.36.199 10 encapsulation mpls is basically the same command as with the Ethernet and PPP examples. The number 10 here should match on both PEs.
Ios Xr Gns3 Manual
Let’s now try and check if frame-relay PVCs are active and whether there is IP reachability between the two customer routers.
Let’s check the MPLS forwarding tables and the VC status.
The configured VCs are up and working. That’s it for MPLS Layer 2 VPN. I hope this has been a good read!