How to Uplink Multiple AC-MXNET-10G-SW12C Switches

How to: Uplink Two AC-MXNET-10G-SW12C Switches

Introduction

This article guides you through the various methods of uplinking (stacking) the AC-MXNET-10G-SW12C network switch, providing connection diagrams, configuration files, and other relevant information.

NOTE: Due to bandwidth constraints, it is only recommended to stack, at maximum, two AC-MXNET-10G-SW12Cs, otherwise, signal issues are extremely likely to occur.


The SW12C switch has six SFP28 ports located on the front panel and can be used for stacking.

Stacking cables are sold separately, the below recommended cables from AVPro Edge are available for purchase for stacking a SW12C switch to another SW12C:
     
      AC-25G-AOC-01 1 Meter 25G SFP28 Active Optical Cable (AOC)
      AC-25G-AOC-02 2 Meter 25G SFP28 Active Optical Cable (AOC)
      AC-25G-AOC-03 3 Meter 25G SFP28 Active Optical Cable (AOC)

SFP28 25Gbps Passive Direct Attach Cables (DAC) can also be used, but performance can only be guaranteed with the cables listed above.

Depending on your installation, one or more stacking cables will be required to uplink the switches. Be sure to follow the diagrams exactly for the number of connections between the switches.

For installation, follow these steps:
1. Check the number of switches, endpoints, and connections in each section.
2. Choose your preferred stacking method.
3. Physically connect the switches accordingly.
4. Download the switch configuration file(s) located at the bottom of this page and apply their
    configuration settings to the switches. For more details on how to configure the switches, see
    this KB Article.
5. (Optional) Review the terms and descriptions that pertain to this article for further clarification.

IMPORTANT! Endpoint Connections when Stacking the SW12C Switch

For configuring load-balancing and port-groups when stacking the SW12C, it's important to note that this switch operates differently from the other switches (SW24Q and SW48Q). Here's how it works:
  1. SFP28 Port 13 will transmit the data from Switch 1 to Switch 2, and vice versa from the 10G RJ-45 Ports 1 and 2 on the SW12C.
  2. Port 14 handles data transmission for Ports 3 and 4.
  3. Port 15 handles data transmission for Ports 5 and 6.
  4. Port 16 handles data transmission for Ports 7 and 8.
  5. Port 17 handles data transmission for Ports 9 and 10.
  6. Port 18 handles data transmission for Ports 11 and 12.
If you are not using all the SFP28 ports, it is imperative to plug the encoders/decoders into the designated ports listed above, based on which SFP28 connections are made. If you do not follow this configuration, you WILL run into issues.

Daisy Chain (Uplink) Two SW12C Switches by using Six 25Gbps SFP28 Ports per Switch


See attachment at the bottom of this page for the switch configuration file:
      AC-MXNET-10G-SW12C-6port-1group.cfg
The above configuration file must be applied to both switches for full operation.



See attachment at the bottom of this page for the switch configuration file:
      AC-MXNET-10G-SW12C-6port-1group.cfg
The above configuration file must be applied to both switches for full operation.


Daisy Chain (Uplink) Two SW12C Switches by using Two 25Gbps SFP28 Ports per Switch


See attachment at the bottom of this page for the switch configuration file:
      AC-MXNET-10G-SW12C-2port-1group.cfg
The above configuration file must be applied to both switches for full operation.


Daisy Chain (Uplink) Two SW12C Switches by using Three 25Gbps SFP28 Ports per Switch


See attachment at the bottom of this page for the switch configuration file:
      AC-MXNET-10G-SW12C-3port-1group.cfg
The above configuration file must be applied to both switches for full operation.

Example Photos




Terms and Descriptions

Daisy Chain Topology

Daisy chain topology is a type of network topology in which the devices are connected to each other in a linear fashion, like the links in a chain. In a daisy chain network, each device is connected to the next device in a series, with the last device in the chain being connected back to the first.

This topology is sometimes also called a linear bus topology. It is often used in small networks or as a secondary topology within a larger network.

One of the key advantages of a daisy chain topology is that it is simple to set up and requires fewer cables than other topologies. However, it can also be prone to congestion, as data must pass through each device in the chain in order to reach its destination. Additionally, if any device in the chain fails, the entire network can be disrupted.

Port Group

In networking, a “port group” is a logical grouping of physical switch ports into a single virtual entity, typically for the purpose of managing network traffic and applying network policies.

A port group can consist of one or more physical ports on a network switch, and the ports in the group are configured to function as a single logical unit. Traffic that enters any port in the group is treated the same as traffic that enters any other port in the group, and the network policies that are applied to the port group are applied uniformly to all ports in the group.

Port groups are often used to implement network segmentation and manage traffic flow in complex networks. For example, in a virtualized environment, a port group can be used to provide connectivity between virtual machines on the same physical host, or between virtual machines on different hosts that are connected to the same virtual switch.

Port Channel

In networking, a port channel is a technique for combining multiple physical switch ports into a single logical channel, in order to increase bandwidth and provide redundancy. A port channel is also known as a “link aggregation group” (LAG) or a “bonded interface”.

When ports are aggregated into a port channel, they are treated as a single logical interface, and traffic is distributed across the member ports in a way that balances the load and provides redundancy. This means that if one of the member ports fails or is disconnected, traffic can still flow across the remaining member ports.

Port channels are often used to provide high-bandwidth connections between switches or between a switch and a server, as well as to provide redundancy in case of link failure. They are also used in other network applications where high availability and load balancing are important.

Port Group and Port Channel

The key difference between port groups and port channels is that port groups are logical groupings of switch ports that are managed as a single entity, while port channels are physical links that combine multiple switch ports into a single logical channel. Port groups are typically used for traffic management and policy enforcement, while port channels are typically used for bandwidth aggregation and redundancy.

Another difference is that port groups are typically used to manage traffic within a single switch or virtual switch, while port channels are used to aggregate links between multiple switches or between a switch and a server.

In summary, while port groups and port channels have some similarities in terms of their ability to combine multiple physical ports into a logical entity, they serve different purposes and are used in different network applications. Port groups are used for traffic management and policy enforcement within a switch or virtual switch, while port channels are used for bandwidth aggregation and redundancy between switches or between a switch and a server.

Load-balance ingress-port

“Load-balance ingress-port” is a switch configuration option that determines how incoming traffic is distributed across multiple uplink ports.

In a network with multiple uplink ports, incoming traffic from different devices can be directed to different uplink ports, which can help to balance the network load and prevent congestion. Load-balancing can be done in several ways, including using the source or destination MAC address, IP address, or protocol, as well as by using a combination of these factors.

When the “load-balance ingress-port” option is enabled, the switch will use the ingress port as a factor in determining how to distribute incoming traffic across the uplink ports. This means that traffic from each port will be directed to a different uplink port, which can help to balance the load and prevent congestion.

For example, if a switch has four uplink ports and the “load-balance ingress-port” option is enabled, incoming traffic from devices connected to port 1 will be distributed across one or more of the four uplink ports, while traffic from devices connected to port 2 will be distributed a cross a different set of uplink ports, and so on.

The specific load-balancing algorithm used by the switch may vary depending on the switch model and firmware version, and there may be additional configuration options to fine-tune the load-balancing behavior.

Enabling “load-balance ingress-port” can be a useful way to improve network performance and prevent congestion in networks with multiple uplink ports, especially when traffic patterns are unpredictable or unevenly distributed across devices.





    • Related Articles

    • AC-MXNET-CBOX ~ V2.71 ~ 9/18/24

      NOTICE: If your CBOX is reading firmware as a version of V4.XX, please navigate to this page here: https://support.avproedge.com/portal/en/kb/articles/ac-mxnet-cbox-b-firmware Note: Please update the CBOX first, before attempting updates on the ...

    • AC-MXNET-1G-DV2-C ~ V3.00 ~ 11-07-23

      NOTICE: Please update the CBOX first before attempting an update on any endpoints. If your DV2 device is showing as AC-MXNET-1G-DV2-B/showing a firmware version of V2.XX, please navigate to this article here: ...

    • How To: Using the MXNET API ~ V1.21.1

      Kevin Wang, Director of Product Management, goes through using the MXNET API to control and configure the MXNet CBOX Direct. Current API Version: V1.21.1 Control Box Version: 2.71 and above Instructions and API attached

    • MXNet Network Switches - Basic Operation Configuration Guide

      This article provides a comprehensive overview of basic diagnostic and configuration commands for MXNet network switches, including instructions for making the necessary physical connections. The switches covered in this article are operating on ...

    • AC-MXNET-1G-EV2-C ~ V3.02 ~ 09/18/24

      NOTICE: Please update the CBOX first before attempting an update on any endpoints. If your AC-MXNET-EV2 device is listed as an AC-MXNET-1G-EV2-B or showing firmware as V2.XX, please navigate to this article here: ...