Skip to main content

Installing Sonic Network Switch in EVE-NG


Installing Sonic Network Switch on EVE-NG

Latest eve-ng has template for sonic switch., at path /opt/unetlab/html/templates/intel/sonicsw.yml

If you do not have template in this folder you can download one and paste in the folder path as above

https://github.com/ercintorun/MsSonicEveNG/blob/main/mssonic.yml

I assume you already have template in folder as mentioned above, with name sonicsw.yml

Create a folder at below path with version number that you will download in the next step

/opt/unetlab/addons/qemu/sonicsw-210216

Download the sonic switch image from below link

https://sonic.software/

Upload eve-ng at this path /opt/unetlab/addons/qemu/sonicsw-210216/

Navigate to the above path and gunzip the image

gunzip /opt/unetlab/addons/qemu/sonicsw-210216/sonic-vs.img.gz

after this you get the file with name sonic-vs.img

now change the the file name to virtioa.qcow2, with below command

mv /opt/unetlab/addons/qemu/sonicsw-210216/sonic-vs.img /opt/unetlab/addons/qemu/sonicsw-210216/virtioa.qcow2

fix the permission with below command

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

And you are good to go now

Below is the image of my sonic switch installed with above steps, and I was able to make the lab as can be seen in the same snapshot



Default username and password for Sonic switch is as below

SONiC Login prompt. Use username admin and password YourPaSsWoRd to login for the first time.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.
1 comment
Read more

BGP Local Preference Controlling Outbound Traffic in BGP

In BGP, Local Preference is used to control the outbound traffic path. It helps you decide which egress point (exit point) should be used when you have multiple connections to external networks, such as ISPs. Local Preference is an attribute that is local to your AS and is shared with all iBGP peers but not with eBGP neighbors. Higher Local Preference = More preferred outbound path. Example Scenario : You have two external links: ISP1 (via CE1) and ISP2 (via CE2). You want traffic to prefer ISP1 for all outbound traffic. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Higher Local Preference) : Create a route map to set the local preference to 200 for routes learned from CE1: route-map SET_LOCAL_PREF permit 10 set local-preference 200 In the BGP configuration for CE1, apply this route map to the neighbor: router bgp 65001 ne...
Post a Comment
Read more

BGP MED: Managing Inbound Traffic with Multi-Exit Discriminator

The Multi-Exit Discriminator (MED) is used in BGP to control inbound traffic into your AS. It tells a neighboring AS which entry point into your network it should prefer when there are multiple links between your AS and the neighboring AS. The lower the MED value , the more preferred the path. MED is only honored between the same neighboring AS . Example Scenario : You are connected to ISP1 via two routers, CE1 and CE2 , and want to control which router ISP1 uses to send traffic into your AS. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP1): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Lower MED, More Preferred) : Create a route map to set the MED to 50 for CE1: route-map SET_MED permit 10 set metric 50 Apply this route map to the neighbor in the BGP configuration for CE1: router bgp 65001 neighbor 10.0.1.1 remote-as 65000 neighbor 10.0.1.1 route-map SET_MED out Configuratio...
Post a Comment
Read more