How to Build 25G Network?

Driven by the boosting global data traffic, data center networks need better scalability, instant bandwidth provisioning, and application agility. Well, 25G is able to provide low-cost and high-efficiency for today’s network. Therefore, many suppliers provide various 25G devices such as 25G SFP28 for 25G network deployment. Well, how to build 25G network and what do you really need for its deployment? This post will offer you some clues.

Why Need 25G?

25G Ethernet, or 25 Gigabit Ethernet (25GbE), is developed by IEEE 802.3 Task Force P802.3by. The IEEE 802.3by standard uses technology defined for 100 Gigabit Ethernet implemented as four 25 Gbps lanes (IEEE 802.3bj). Actually, 40G and 100G have already existed before the emergence of 25G. However, 25G Ethernet can provide a more convenient path to Ethernet speeds of 50G, 100G and beyond. With 25G, network operators are no longer to use 40G Ethernet (using four lanes of 10G) to migrate to 100G,  but using 4 lanes of 25G. For more information about 25G network upgrade, read this article: 10G-25G-100G Network Upgrade: An Inevitable Roadmap for Future Data Centers.

What Do You Need for 25G Network Deployment?

To build a 25G network, several components are indispensable: 25G SFP28 transceiver, DAC/AOC cable, 25G adapter, and 25G Ethernet switch. Here will introduce a series of 25G products to guide your purchase.

25G Switch

The 25GbE switch is one of the most important 25G devices and the most popular type of 25GbE switch is the 25G 48-port switch. Nowadays, there is a variety of 25G switches from different suppliers in the market like Cisco, Juniper, and Mellanox. The following figure shows some 25GbE switches with 100G uplinks.

48-port 25GbE switches

Figure 1: 48-port 25GbE switches from FS, Cisco, Mellanox and Edgecore

25G Server Adapter

25G server adapter, also called 25G network interface card (NIC), is a printed circuit board that provides network communication capabilities. It is commonly used as a separate adapter card, which can be inserted into the server’s motherboard expansion slot. Usually, the NIC is built with an interface in the side plate. Some NICs such as FS NIC even have two or more network interface. As the 40G network card is costly and too large for the server, 25G NIC is definitely a proper one for today’s network.

25G Transceiver

SFP28 is designed for 25G signal transmission. It usually contains SFP-25G-SR, SFP-25G-LR and CWDM SFP28. The SFP-25G-SR is used for short distance transmission (up to 100m over MMF). While the SFP-25G-LR and CWDM SFP28 are applied for long distance transmission (up to 10 km over SMF). You can choose an appropriate one based on your need.

25G DAC/AOC Cables

For interconnections in Ethernet switches, applying 25G DAC/AOC cables may be a more suitable and cost-effective solution than using 25G transceivers. However, 25G DAC/AOC cables only for short transmission distance. 25G SFP28 DAC cables can transmit less than 5m, and 25G SFP28 AOC cables transmit up to 30m.

How to Build 25G Network?

After choosing the suitable 25G devices, here we can start to build 25G network.

When deploying 25G network, ToR/spine-leaf switching architecture is often applied. The spine-leaf architecture includes two layers – the spine layer and the leaf layer. The spine layer is the backbone of the network and the leaf layer interconnects with every spine switch. In this deployment, 25G switches are usually deployed as ToR/leaf switches in the leaf layer or the top of each cabinet. Through point-to-point cabling, these switches can connect directly to the 25G servers in all the cabinets. And you can use 25G DAC/AOC cables or 25G SR transceiver and fiber patch cables to connect the switch ports and 25G servers. In addition, you should insert a 25G NIC in each 25G server.

25g sfp28

Figure 2: 25G ToR/spine-leaf architecture deployment


This article presents some basic information about 25G Ethernet, how to build 25G network, and the devices needed for 25G network deployment like 25G SFP28 transceiver, DAC/AOC cable, 25G NIC, and 25G Ethernet switch. If you are considering to build 25 network, reliable suppliers like FS provide all the components mentioned above such as 25G SFP28. For more details, please visit

发表在 Enterprise Network | 标签为 , , | How to Build 25G Network?已关闭评论

Transceiver Modules for FS N-series Switches with Cumulus Linux

In response to the expansion of open source networking, FS released N-series switches combining with Cumulus Linux. FS N-series switches, as hot-pluggable I/O devices, allow interconnections between multiple devices by using various transceivers modules. To provide more convenience and good experiences, FS also supplies a wide variety of transceiver modules, which are compatible with these switches for users to meet different deployment requirements. This post will make an introduction of FS N-series switches with Cumulus Linux and FS transceiver modules for these switches.

Overview of FS N-series Switches with Cumulus Linux

FS N-series switches with Cumulus Linux, including N5850-48S6Q switch, N8000-32Q switch, and N8500-32C switch, allow customers to configure their desirable network switches. They possess Broadcom switching chip, Intel CPU, and other advanced configurations. What’s more, all of these switches enjoy a 5-year hardware warranty. Armed with Cumulus Linux network operating system, FS N-series switches can provide users with more advanced functions such as MLAG, NCLU, EVPN, VxLAN, SNMP, etc. These switches are ideal for the traditional or fully virtualized data center. In a word, FS N-series switches with Cumulus Linux help users to deploy fast, high-capacity fabrics, simplified network automation and consistent tools, and help lower operational and capital expenditures.

Cumulus Linux

Figure 1: FS N-series switches with Cumulus Linux

Supported Transceivers N-series Switches with Cumulus Linux

According to your real needs, you can choose different FS N-series switches with Cumulus Linux and suitable transceivers for these switches.

N5850-48S6Q Switch

The N5850-48S6Q switch is a Top-of-Rack (TOR) or Leaf switch. It delivers excellent low latency and power efficiency in a PHYless design. It also offers high reliability features such as hot-swappable power supplies and fans in forward and reverse airflow configurations. In addition, N5850-48S6Q switch provides 48 SFP+ 10GbE ports and 6 QSFP+ 40GbE ports, and each 40GbE port can be configured as 4x10GbE up to a total system limit of 72 10GbE ports. Therefore, it can use 10G SFP+ and 40G QSFP+ to connect with other network devices. The following table lists FS transceiver modules and Twinax cables supported by N5850-48S6Q switch.

N8000-32Q Switch

The N8000-32Q switch is ideal for data center environments in either Leaf or Spine deployments. It delivers a rich choice of interface speed and density, which can be deployed in a wide range of open networking solutions including layer 2 and layer 3 cloud designs, overlay networks, virtualized or traditional enterprise data center networks. What’s more, N8000-32Q switch provides 32 QSFP+ ports, and each port can be configured as 4x10GbE with individual link LEDs, up to a total system limit of 104 10GbE ports. Here are QSFP+ transceivers and Twinax cables for N8000-32Q switch.

N8000-32Q switch
N8500-32C Switch

Designed for high performance and programmable data center environments, N8500-32C switch offers line-rate, high-bandwidth switching, filtering, and traffic queuing without delaying data. Due to the redundant power and fans along with lots of high availability features, it is usually available for business-sensitive traffic. Moreover, the N8500-32C switch provides 32 ports 100GbE QSFP28 modules. To meet various deployment demands, FS also supplies multiple optical transceivers and Twinax cables compatible with this switch.

N8500-32C Switch


FS N-series open networking switches with Cumulus Linux offer flexibility, efficiency and cost effectiveness in data center networks. Any requirements for FS N-series open networking switches and the supported transceiver modules, welcome to visit FS.COM.

Related Article: Optics Solutions for FS.COM 100G Switches

发表在 Enterprise Network | 标签为 , , | Transceiver Modules for FS N-series Switches with Cumulus Linux已关闭评论

OVS vs Linux Bridge: Who’s the Winner?

The battle between the OVS (Open vSwitch) and Linux Bridge has lasted for a while in the field of virtual switch technologies. Someone hold that the Open vSwitch owns more functions and better performance, which plays the most important role in virtual switch now. While others consider that the Linux Bridge has been used for years, which is matured than OVS. So OVS vs Linux Bridge: who’s the winner?

OVS vs Linux Bridge: What Are They?


Open vSwitch (OVS) is an open source multilayer virtual switch. It usually operates as a software-based network switch or as the control stack for dedicated switching hardware. Designed to enable effective network automation via programmatic extensions, OVS also supports standard management interfaces and protocols, including NetFlow, sFlow, CLI, IPFIX, RSPAN, LACP, 802.1ag. In addition, Open vSwitch can support transparent distribution across multiple physical servers. This function is similar to the proprietary virtual switch solutions such as the VMware vSphere Distributed Switch (vDS). In short, OVS is used with hypervisors to interconnect virtual machines within a host and virtual machines between different hosts across networks.


Figure 1: OVS

Linux Bridge

As mentioned above, the Open vSwitch is a multilayer virtual switch, which can work as a Layer 2 or Layer 3 switch. While the Linux bridge only behaves like a Layer 2 switch. Usually, Linux bridge is placed between two separate groups of computers that communicate with each other, but it communicates much more with one of the computer groups. It consists of four major components, including a set of network ports, a control plane, a forwarding plane, and MAS learning database. With these components, Linux bridge can be used for forwarding packets on routers, on gateways, or between VMs and network namespaces on a host. What’s more, it also supports STP, VLAN filter, and multicast snooping.

OVS vs Linux Bridge: Advantages And Disadvantages of OVS

Compared to Linux Bridge, there are several advantages of Open vSwitch:

  • Easier for network management – With the Open vSwitch, it is convenient for the administrator to manage and monitor the network status and data flow in the cloud environment.
  • Support more tunnel protocols – OVS supports GRE, VXLAN, IPsec, etc. However, Linux Bridge only supports GRE tunnel.
  • Incorporated in SDN – Open vSwitch is incorporated in software-defined networking (SDN) that it can be driven by using an OpenStack plug-in or directly from an SDN Controller, such as OpenDaylight.

Despite these advantages, Open vSwitch have some challenges:

  • Lacks stability – Open vSwitch has some stability problems such as Kernetl panics, ovs-switched segfaults, and data corruption.
  • Complex operation – Open vSwitch itself is a complex solution, which owns so many functions. It is hard to learn, install and operate.

OVS vs Linux Bridge: Strengths And Limitations of Linux Bridge

Linux Bridge is still popular mainly for the following reasons:

  • Stable and reliable – Linux Bridge has been used for years, its stability and reliability are approved.
  • Easy for installation – Linux Bridge is a part of standard Linux installation and there are no additional packages to install or learn.
  • Convenient for troubleshooting – Linux Bridge itself is a simple solution that its operation is simpler than that of Open vSwitch. It is convenient for troubleshooting.

However, there are some limitations:

  • Fewer functions – Linux Bridge doesn’t support the Neutron DVR, the newer and more scalable VXLAN model, and some other functions.
  • Fewer supporters – Many enterprises wanted to ensure that there was an open model for integrating their services into OpenStack. However, Linux Bridge can’t ensure the demand, so it has fewer users than that of Open vSwitch.

OVS vs Linux Bridge: Who’s the Winner?

OVS vs Linux Bridge: who’s the winner? Actually, both of them are good network solutions and each has its appropriate usage scenarios. OVS has more functions in centralized management and control. Linux Bridge has good stability that is suitable for Large-scale network deployments. All in all, The winner is the right one that meets your demands.

Related Article: OpenStack vs OpenDaylight vs OpenFlow vs OpenvSwitch: What’re Their Relations?

发表在 Enterprise Network | 标签为 , , , | OVS vs Linux Bridge: Who’s the Winner?已关闭评论

OpenStack vs OpenDaylight vs OpenFlow vs OpenvSwitch: What’re Their Relations?

Recently, open source technologies such as OpenvSwitch, OpenDaylight, OpenFlow, and OpenvSwitch have become more and more popular. Though they have been introduced for a while, they still confuse people in some aspects, especially their relations with each other. Here we will cover the topic on OpenStack vs OpenDaylight vs OpenFlow vs OpenvSwitch.

OpenStack vs OpenDaylight vs OpenFlow vs OpenvSwitch: What Are They?


Openvswitch or openvSwitch (OVS) is an open-source OpenFlow switch, which works as a virtual switch in the virtualized environments. It is also used as a multilayer software for interconnecting virtual devices in the same host or between different hosts across networks. OVS can support standard management interfaces and protocols, including NetFlow, sFlow, CLI, IPFIX, RSPAN, LACP, 802.1ag. In addition, it can support transparent distribution across multiple physical servers. This function is similar to the proprietary virtual switch solutions such as the Cisco Nexus 1000V. For more information, please read Open Switch vs Openvswitch: What’s the Difference?


OpenFlow is a communications protocol standard for SDN. It empowers a network switch or a router to access the forwarding plane over the network. What’s more, it can serve as a specification of the logical structure of the network switch functions. It facilitates remote management of switches from a centralized control plane or controller. Therefore, OpenFlow has gained achievements in hardware and software support since its release. Branded vendors such as Cisco and Juniper have launched network equipment like 10GB Ethernet switch, router, and wireless access point which support OpenFlow.

OpenStack vs OpenDaylight vs OpenFlow vs OpenvSwitch

Figure 1: OpenFlow


OpenDaylight (ODL) is an open source project within the Linux Foundation. As an SDN controller, it provisions the network policies as specified and sends that information to the HYpervisor. It allows the users to programmably manage OpenFlow capable Gigabit Ethernet switches. Though ODL owns a large set of features and compatible north bound applications, it has many alternatives such as Floodlight, RYU SDN framework, NOX, etc.


OpenStack is an open source cloud computing platform, which combines several major components to accomplish specific tasks. It can not only use all the above-mentioned technologies to provide the user with more programmatic control over the infrastructure, but also work independently without any of them. OpenStack is convenient and reliable with strong compatibility and adaptability, gaining support from many vendors.

OpenStack vs OpenDaylight vs OpenFlow vs OpenvSwitch: What’re Their Relations?

OpenvSwitch vs OpenDaylight vs OpenFlow

OpenvSwitch, OpenDaylight, and OpenFlow are all used for SDN application. OpenFlow is one of the first SDN standards. OpenvSwitch is an OpenStack SDN component. OpenDaylight is an SDN controller. As to their relations, OpenFlow is a protocol and OpenvSwitch and OpenDaylight are packages or software packages using that protocol. In other words, the protocol used by OpenvSwitch or OpenDaylight is OpenFlow.

OpenvSwitch vs OpenDaylight vs OpenStack

OpenStack covers many aspects like network, virtualization, operation system, and server. When OpenDaylight and OpenvSwitch perform network resource management, OpenStack is often used with them together to allow for end-to-end automation and orchestration. Moreover, OpenStack has hooks within it that allow integration of OVS/ODL and this interaction is achieved via southbound API.


OpenStack vs OpenDaylight vs OpenFlow vs OpenvSwitch, these four terms are of significance in the networking system. With these technologies, the network performance has become better and it is also more convenient for you to do network management in enterprises and data centers. In fact, open source technologies are still developing. This article may be the first step that helps you know them and there are still lots of things to be explored.

发表在 Enterprise Network | 标签为 , , , | OpenStack vs OpenDaylight vs OpenFlow vs OpenvSwitch: What’re Their Relations?已关闭评论

No Switchport Command: How Much Do You Know?

When working with switches, you may meet some interface configuration mode commands such as swtichport mode access, no switchport, etc. Well, do you know what the no switchport command is? Could it be supported by Layer 2 switch or Layer 3 switch? How to use no switchport command? In this article, we will share some insights and help solve the above questions.

What Is a No Switchport Command?

To understand the no switchport command, we’d better get to know Layer 2 switch and Layer 3 switch first. The Layer 2 switch is a network switch that forwards traffic based on layer 2 information of the OSI model. It functions by keeping a table of media access control (MAC) addresses. Moreover, it can assign VLANs to specific switch ports, which in turn are in different Layer 3 subnets. So the communication with other LANs, or VLANs, needs the function of Layer 3. And the Layer 3 switch combines some features of Layer 2 switch and some of the router. That is to say, it can switch packets by checking both IP addresses and MAC addresses.

The no switchport command is provided by the interface on a Layer 3 capable switch. This command can convert a Layer 2 port into a Layer 3 port and makes the port operate like a router interface rather than a switch port. So this port is also called routed port. What’s more, the routed port isn’t joined to any VLANs and do not support VLAN subinterfaces. However, you can apply an IP address directly to the port and more IP configuration options are available after running the no switchport command.

How to Use No Switchport Command?

As mentioned above, the no switchport command is mainly used to configure routed ports. This helps Layer 3 switch reach the default router during the configuration of VLAN. In terms of the configuration of the routed port, you can get into interface configuration mode of a switch and issue the command no switchport. This prohibits Layer 2 capabilities and enables Layer 3. Then you can assign an IP address to the routed port.

no switchport command

Figure 1: An example of a routed port configuration

No Switchport Command on Layer 3 Switch

The no switchport command plays an important role in configuring VLAN on the Layer 3 switch. With the no switchport command, you can get access to the Web Interface. Then, you can simply configure VLAN via the Web Interface. The following is the configuration guide.

  • 1.Connect your computer to the switch.
  • 2.Run the SecureCRT software on the computer, and enter the command #configure terminal to enter the global configure mode.
  • 3.Choose the “http” file, and enable the “http” service.
  • 4.Enter the command #show interface eth-0-1 to check the state of eth-0-1 port on the switch.
  • 5.Enter the command #interface eth-0-1 to enter the eth-0-1 port.
  • 6.Enter the command #no switchport to put the eth-0-1 port in L3 mode to make it the routed port.
  • 7.Assign an IP address to the eth-0-1 port and enter the command #no shutdown to activate the eth-0-1 port.
  • 8.Set the IP address of the computer to make sure it’s in the same network with the eth-0-1 port.
  • 9.Ping the IP address on the computer to check whether there is any mistake in the steps above. (If there were no mistake in the Ping result, you could log in with the username and password of your account to enter the Web Interface.)
  • 10.Add or delete the VLAN in the Service Management.


This post has explained what the no switchport command is, the steps to configure no switchport command, and how to use it on Layer 3 switch. So have you got all the answers to the questions at the beginning? Well, FS provides various high-quality network switches. Welcome to contact us if you have any needs about it.

Related Article: Layer 2 vs Layer 3 Switch: Which One Do You Need?

发表在 Enterprise Network | 标签为 , , | No Switchport Command: How Much Do You Know?已关闭评论