
Port Mirroring for SONiC in Verity
One of the new capabilities we have in our latest release 6.4, is the ability to create SPAN, or Switch Port Analyzer, also known as Port Mirroring configurations. This gives you the ability to duplicate one or more source interfaces to a destination interface on a switch, and then have a collector or another server, or even another network be the destination of this duplicated packet information.
In this blog, I will show how to setup a Mirror session, select the destination, and view this traffic all through BE Networks Verity.
So lets say I have the following network topology:

I want to duplicate the traffic coming from my Ubuntu Server to my Windows server. Ubuntu server is connected to port 30 on my SONiC switch and the Windows Server is on port 40 of the SONiC switch. My monitoring server, which I want the duplicate packets to go to is on port 37 of the switch.
In Verity, under the Topology View, when you zoom in on the switch you want to create the Mirror on, there is a new box near the top called Traffic Mirrors:


We can add multiple rows with the icon and adjust priority with the
icon.
The first thing we do is click icon to create a row. Then click the Pencil icon in the top right corner to go into Edit mode. From here, select Enable, and then from the Source Port drop down menu, select port 30, which is the port that the Ubuntu server is connected to. Next select direction. We want both so we select both inbound and outbound boxes. Last, for destination, we select the interface on the switch connected to our monitor server, which is port 37 in this example:

Next, click the Check in the top right corner to save the mirror session.
The switch will turn green, letting you know that it is sending the configuration to the switch and that it is in the process of updating. Once the switch is back to normal, you will see your session in the box:

You can see that the Current Count and Active count now both say 1 showing that the device is currently configured and mirroring traffic from port 30 to port 37.
On my monitoring Server, I can now see the packets coming in from the server and see the communications between the Ubuntu and Windows Server. It’s as simple as that.
To remove this configuration, all I have to do is go in and disable the row, and then I can delete it by using the icon to clear the data, and then use the
to clear any disabled rows.
It’s as easy as that. Way easier than logging into the switch manually, and then running the risk of configuring it wrong via the CLI!

루크 윌리엄스
제품 리드
IT 분야에서 30년 이상의 경력을 쌓은 루카스가 보지 못한 것은 많지 않습니다. 16세 때 고향인 아이오와주에서 지역 ISP를 운영한 것부터 2012년 미국에서 두 번째로 큰 신문 미디어 회사에서 네트워크 및 서버 관리를 담당한 것, Canonical에서 근무하면서 IoT 솔루션 및 네트워킹 NOS를 개발한 것까지, 그는 끊임없이 새로운 기술을 배우고 시도하며 시장과 기업의 요구를 충족하기 위해 새로운 기술을 개발하고 있습니다. 현재 개방형 네트워킹 및 SONiC를 전문으로 하는 비욘드엣지 네트웍스의 제품 책임자로 일하고 있습니다.