Stacking and Lag

[WAJDI-S]

Hi all,

I am currently looking to replace existing cisco Core switches with two extreme switches core for redandancy (in stack) ,and replace existing cisco Access switches with the X435 models , and need to know best practice for configuring these Core switches with STP and LAG before connecting them to the network .What STP and LAG configuration schould be set for core switches and the X435.

please find the network design below,
What is the best practice ?

 

[Brent_Addis · Accepted solution]

Hi,

You haven't provided the network design, you might need to attach it?

I would be using an MLAG rather than a stack in a core as this allows you to reboot them separately and would generally be best practice in a core.

I'm going to use two XOS based core switches, and a pair of X435 switches in my example below, you can extrapolate from there.

Setting up an MLAG (Multi-Chassis Link Aggregation) between two Extreme XOS core switches involves several steps. After establishing the MLAG, you can connect edge switches, like the X435s, via LACP. Additionally, configuring SNTP (Simple Network Time Protocol) and ELRP (Extreme Loop Recovery Protocol) is essential for maintaining accurate time synchronization and preventing network loops, respectively.

The ISC (Inter-Switch Connection) is a crucial component of an MLAG (Multi-Chassis Link Aggregation) setup in Extreme Networks switches. The ISC is responsible for providing a communication link between the MLAG peers, allowing them to synchronize state, share MAC address tables, and forward traffic as necessary.

Part 1: Setting Up MLAG on Core Switches

Step 1: Prepare the Core Switches

1. Configure System IPs:

   configure ipaddress <Core_Switch_IP> mask <Subnet_Mask> vlan <Management_VLAN>

• Configure the MLAG Peer IPs:

1. configure mlag peer ipaddress <Peer_Switch_IP> vlan <Management_VLAN>

Step 2: Configure the ISC (Inter-Switch Connection)

1. Create an ISC VLAN:

• create vlan "ISC_VLAN" configure vlan ISC_VLAN tag <ISC_VLAN_ID>

• Add Ports to ISC VLAN:

1. configure vlan ISC_VLAN add port <ISC_Ports> tagged

2. Configure ISC IP Addresses: Assign IP addresses to the ISC VLAN on both switches.

Step 3: Enable MLAG

1. Configure MLAG Ports: Configure the ports that will be part of the MLAG on both core switches.

   shell

• enable sharing <Port_Number> grouping <Port_List> algorithm address-based L3_L4

• Enable MLAG:

1. enable mlag port <MLAG_Port> peer <Peer_Port> id <MLAG_ID>

Part 2: Connecting X435 Switches via LACP

Step 1: Create LAG on X435 Switches

1. Configure LAG:

   shell

1. enable sharing <Port_Number> grouping <Port_List> algorithm address-based L3_L4

2. Assign LAG to VLANs: Assign the LAG to appropriate VLANs as needed.

Step 2: Connect to Core Switches

1. Connect the X435s: Connect the LAG ports from each X435 to the respective core switches.

Part 3: Best Practices

SNTP Configuration

1. Configure NTP Server:

   shell

• configure sntp primary <NTP_Server_IP> enable sntp-client

• Configure Timezone:

  shell

1. configure timezone <Timezone>

ELRP Configuration

1. Configure ELRP for Loop Prevention:

   • Run ELRP on critical VLANs to detect potential loops.
   • Configure ELRP on a per-VLAN basis.
   shell

1. enable elrp-client <VLAN_Name> ports all interval <Interval_Seconds>

General Best Practices

• Firmware: Ensure both switches are running the same firmware version.
• Backup Configuration: Regularly backup the configuration of your switches.
• Monitoring: Implement proactive monitoring for the MLAG, LACP status, and other critical parameters.
• Documentation: Maintain clear documentation of your configuration and any changes made.

This setup provides high availability and redundancy, but it's important to test configurations in a controlled environment before deploying in production. Additionally, always refer to the specific ExtremeXOS documentation for your switch model and firmware version, as commands and capabilities can vary.

[WAJDI-S]

thank you all for return

[markus_of · Accepted solution]

As Brent described it, MLAG is the best solution.

Stacking would also work if you use the topology ring. It is rather the simpler solution.

[Brent_Addis · Accepted solution]

Hi,

You haven't provided the network design, you might need to attach it?

I would be using an MLAG rather than a stack in a core as this allows you to reboot them separately and would generally be best practice in a core.

I'm going to use two XOS based core switches, and a pair of X435 switches in my example below, you can extrapolate from there.

Setting up an MLAG (Multi-Chassis Link Aggregation) between two Extreme XOS core switches involves several steps. After establishing the MLAG, you can connect edge switches, like the X435s, via LACP. Additionally, configuring SNTP (Simple Network Time Protocol) and ELRP (Extreme Loop Recovery Protocol) is essential for maintaining accurate time synchronization and preventing network loops, respectively.

The ISC (Inter-Switch Connection) is a crucial component of an MLAG (Multi-Chassis Link Aggregation) setup in Extreme Networks switches. The ISC is responsible for providing a communication link between the MLAG peers, allowing them to synchronize state, share MAC address tables, and forward traffic as necessary.

Part 1: Setting Up MLAG on Core Switches

Step 1: Prepare the Core Switches

1. Configure System IPs:

   configure ipaddress <Core_Switch_IP> mask <Subnet_Mask> vlan <Management_VLAN>

• Configure the MLAG Peer IPs:

1. configure mlag peer ipaddress <Peer_Switch_IP> vlan <Management_VLAN>

Step 2: Configure the ISC (Inter-Switch Connection)

1. Create an ISC VLAN:

• create vlan "ISC_VLAN" configure vlan ISC_VLAN tag <ISC_VLAN_ID>

• Add Ports to ISC VLAN:

1. configure vlan ISC_VLAN add port <ISC_Ports> tagged

2. Configure ISC IP Addresses: Assign IP addresses to the ISC VLAN on both switches.

Step 3: Enable MLAG

1. Configure MLAG Ports: Configure the ports that will be part of the MLAG on both core switches.

   shell

• enable sharing <Port_Number> grouping <Port_List> algorithm address-based L3_L4

• Enable MLAG:

1. enable mlag port <MLAG_Port> peer <Peer_Port> id <MLAG_ID>

Part 2: Connecting X435 Switches via LACP

Step 1: Create LAG on X435 Switches

1. Configure LAG:

   shell

1. enable sharing <Port_Number> grouping <Port_List> algorithm address-based L3_L4

2. Assign LAG to VLANs: Assign the LAG to appropriate VLANs as needed.

Step 2: Connect to Core Switches

1. Connect the X435s: Connect the LAG ports from each X435 to the respective core switches.

Part 3: Best Practices

SNTP Configuration

1. Configure NTP Server:

   shell

• configure sntp primary <NTP_Server_IP> enable sntp-client

• Configure Timezone:

  shell

1. configure timezone <Timezone>

ELRP Configuration

1. Configure ELRP for Loop Prevention:

   • Run ELRP on critical VLANs to detect potential loops.
   • Configure ELRP on a per-VLAN basis.
   shell

1. enable elrp-client <VLAN_Name> ports all interval <Interval_Seconds>

General Best Practices

• Firmware: Ensure both switches are running the same firmware version.
• Backup Configuration: Regularly backup the configuration of your switches.
• Monitoring: Implement proactive monitoring for the MLAG, LACP status, and other critical parameters.
• Documentation: Maintain clear documentation of your configuration and any changes made.

This setup provides high availability and redundancy, but it's important to test configurations in a controlled environment before deploying in production. Additionally, always refer to the specific ExtremeXOS documentation for your switch model and firmware version, as commands and capabilities can vary.