Configuring LAGs on Appliances

This section provides information on how to configure Link Aggregation Groups (LAGs) for Solace PubSub+ appliances. LAGs can be used for management and network interfaces on the Network Acceleration Blade (NAB)—a hardware line card used by the appliance for receiving and processing messages.

Configuring LAG Active/Backup Mode on MGMT Ports

To manually configure the two physical management network interface ports (that is, eth1 and eth2 on Solace PubSub+ 3530s and 3560s) as a LAG in active/backup mode perform the following steps using the Solace CLI:

  1. Create the chassis/lag1 interface and designate it as mode active-backup.

    Only a single LAG numbered 1 is supported. A LAG can not be deleted if IP interfaces reference it.

    solace# configure
    solace(configure)# create interface chassis/lag1 active-backup
    solace(configure/interface)#
  2. Assign both of your Management ports as members of the LAG interface, and then designate one of them as the “primary” member (this is the link that is active on startup). 
    solace(configure/interface)# member eth1
    solace(configure/interface)# member eth2
    solace(configure/interface)# primary-member eth1
  3. Start the LAG interface in active/backup mode. 
    solace(configure/interface)# no shutdown

    There is no special configuration required on the terminating Layer 2 devices. Configure them as normal individual ports.

  4. View the status and configuration of the LAG in active/backup Mode.
    solace> show interface chassis/lag1
    Interface: chassis/lag1 
  MAC address: 00:15:17:4d:25:f0
  Mode: Active-Backup
  Enabled: yes
  Rx pkts:           329217        Rx bytes:         24240418
  Tx pkts:          2463932        Tx bytes:         432977869

  Configured members:  eth1, eth2 
  Available members:   eth1, eth2 
  Operational members: eth1 
  Primary member:      eth1

Changing the MGMT VRF Config on Working MGMT Port LAGs

Management connectivity can be lost when changing the Management VRF interface configuration on working management port LAGs. Solace recommends performing these changes manually from the appliance CLI within a maintenance window to prevent service interruption.

To manually change the working LAG configuration of the two physical management interface ports (that is, eth1 and eth2 on Solace PubSub+ 3530s and 3560s) from using an eth1 configuration on the Management VRF to one using a chassis/lag1 configuration, whereby the appliance uses the same IP address as before, do the following:

  1. Start the eth2 interface: 
    solace# configure
    solace(configure)# interface eth2
    solace(configure/interface)# no shutdown
  2. Shutdown the eth1:1 interface on the Management VRF: 
    solace(configure)# ip vrf management
    solace(configure/ip/vrf)# interface eth1:1
    solace(configure/ip/vrf/interface)# shutdown
    Changing management addresses or default routes may leave the appliance unreachable over a network connection. As well changing management addresses will result in newly unreachable routes being deleted.
    Do you want to continue (y/n)? y
  3. Remove the eth1:1 interface configuration: 
    solace(configure/ip/vrf/interface)# exit
    solace(configure/ip/vrf)# no interface eth1:1
    solace(configure/ip/vrf)# exit

    This automatically removes the default route.

  4. Assign both of your management ports as members of the LAG interface, and designate one of them to be the “primary” member (this is the link that is active on startup): 
    solace(configure)# create interface chassis/lag1
    solace(configure/interface)# member eth1
    solace(configure/interface)# member eth2
    solace(configure/interface)# primary-member eth1
  5. Start the LAG interface: 
    solace(configure/interface)# no shutdown

    There is no special configuration required on the terminating Layer 2 devices. Configure them as normal individual ports.

  6. Add the new chassis/lag1 interface to the Management VRF, and start the LAG: 
    solace(configure)# ip vrf management
    solace(configure/ip/vrf)# create interface chassis/lag1:1 static
    solace(configure/ip/vrf/interface)# ip 192.168.129.83/22
    solace(configure/ip/vrf/interface)# no shutdown
  7. If required for your network, configure the default IP route for the Management VRF: 
    solace(configure/ip/vrf/interface)# exit
    solace(configure/ip/vrf)# route default 192.168.128.1 chassis/lag1:1
  8. Verify the status and configuration of the Management VRF: 
    solace> show ip vrf management
    VRF: management      
Number of interfaces: 1

Status Flags:   R=Redundancy,  A=Admin,  P=Physical
Status Values:  U=Up,  D=Down,  N=Not Applicable
 
			Status
Interface       V Router  IP Address          R  A  P
--------------  --------  ------------------  --------
chassis/lag1:1  static    192.168.129.83/22   N  U  U   
 
Number of global routes: 1
 
Destination       Gateway           Network Mask      Interface
----------------  ----------------  ----------------  ----------
default           192.168.128.1     0.0.0.0           chassis/lag1:1

To change the working LAG configuration of the two management interface ports (that is, eth1 and eth2 on Solace PubSub+ 3530s and 3560s) from using an eth1 configuration on the Management VRF to one using a chassis/lag1 configuration, whereby the appliance uses the same IP address as before, do the following:

  1. Enter the setup CONFIG command, and follow the on-screen command prompts. 
    solace# setup
    Please enter the hostname []: 
Do you want to place the 2 management interfaces in an active-backup LAG? (y/n)
[N]: y
Choose primary interface for the management LAG (eth1, eth2) []: eth1
Please configure the management VRF interface (chassis/lag1:1):
Enter the IP/Netmask in CIDR form [192.168.129.83/22]: 
Please enter the default gateway [192.168.128.1]: 
Please configure the msg-backbone VRF interface (1/1/lag1:1):
Enter the IP/Netmask in CIDR form []: 192.168.164.183/19
Please enter the default gateway [192.168.160.1]: 
Please enter the local time zone (? for help) [Canada/Eastern]:
Do you want to synchronize time with an NTP server? (y/n) [Y]:
Please enter the NTP server by IP [192.168.1.203]:
Please enter DNS server(s) by comma separated IP []:
Please enter the desired power redundancy (e.g. "2+1", "2+2") [2+2]:
 
You have entered the following information:
 
Primary interface (chassis/lag1):       eth1
Create interface:                       chassis/lag1:1
IP Address (chassis/lag1:1):            192.168.129.83/22
Default Gateway (management):           192.168.128.1
IP Address (1/1/lag1:1):                192.168.164.183/19
Power Redundancy:                       2+2
Please verify that this information is correct.
Do you want to continue (y/n)? y

Changing management addresses or default routes may leave the appliance unreachable over a network connection. 
As well changing management addresses will result in newly unreachable routes being deleted.
Do you want to continue (y/n)? y
  2. Enter the following show command to verify the status and configuration of the Management VRF: 
    solace> show ip vrf management
    VRF: management      
Number of interfaces: 1
 
Status Flags:   R=Redundancy,   A=Admin,   P=Physical
Status Values:  U=Up,  D=Down,  N=Not Applicable
 
			Status
Interface       V Router  IP Address          R  A  P
--------------  --------  ------------------  --------
chassis/lag1:1  static    192.168.129.83/22   N  U  U   
 
Number of global routes: 1
 
Destination       Gateway           Network Mask      Interface
----------------  ----------------  ----------------  ----------
default           192.168.128.1     0.0.0.0           chassis/lag1:1

Configuring LAG Active/Backup Mode on Two NAB Ports

To configure two physical network interface ports on a NAB as a LAG in active/backup mode on appliances, perform the following steps:

  1. Create a LAG interface with an active-backup mode. For more information, refer to IP Interface Configuration for Appliances.

    Only a single LAG numbered 1 is supported. A LAG cannot be deleted if IP interfaces reference it, and a LAG cannot be created on a slot which does not contain a NAB.

    solace# configure
    solace(configure)# create interface 1/1/lag1 active-backup
    solace(configure/interface)#
  2. Assign two of your NAB ports as members of the LAG interface and designate one of them to be the “primary” member (this is the link that is active on startup). For more information, refer to Configuring Appliance IP Interfaces. 
    solace(configure/interface)# member 1/1/1
    solace(configure/interface)# member 1/1/2
    solace(configure/interface)# primary-member 1/1/1
  3. Start the LAG interface and in turn the active/backup mode. For more information, refer to Configuring Appliance IP Interfaces. 
    solace(configure/interface)# no shutdown

    There is no special configuration required on the terminating Layer 2 devices. Configure them as normal individual ports.

  4. Manually force a switch to the backup member. (For more information, refer to Manually Switching Activity Between LAG Members.) 
    solace(configure/interface)# exit
    solace(configure)# exit
    solace# admin
    solace(admin)# interface 1/1/lag1
    solace(admin/interface)# switch-active
  5. View the status and configuration of the LAG in Active/Backup Mode. 
    solace> show interface 1/1/lag1
    Interface: 1/1/lag1 
  MAC address: 00:50:c2:44:c0:ba
  Mode: Active-Backup
  Enabled: yes
  Rx pkts:              204        Rx bytes:            13818
  Tx pkts:                0        Tx bytes:                0
 
  Configured members:  1/1/1, 1/1/2 
  Available members:   1/1/1, 1/1/2 
  Operational members: 1/1/1 
  Primary member:      1/1/1

Configuring LACP LAGs in Active/Backup Pairs

To configure two LACP LAGs as an Active/Backup pair and bond them together using a third LAG, perform the following steps:

  1. Create one LACP LAG interface , assign two of your NAB ports as members, and then start the interface. 
    solace# configure
    solace(configure)# create interface 1/6/lag2 lacp
    solace(config-interface)#

    solace(config-interface)# member 1/6/1
    solace(config-interface)# member 1/6/2

    solace(config-interface)# no shut
    solace(config-interface)# exit
  2. Create a second LACP LAG interface , assign two more NAB ports as members, and then start the interface. 
    solace(configure)# create interface 1/6/lag3 lacp
    solace(configure/interface)#

    solace(configure/interface)# member 1/6/3
    solace(configure/interface)# member 1/6/4

    solace(configure/interface)# no shut
    solace(configure/interface)# exit
  3. Create a third LAG interface with an active-backup mode to bond the other two LAGs. 
    solace(configure)# create interface 1/6/lag1 active-backup

    solace(configure/interface)# member 1/6/lag2
    solace(configure/interface)# member 1/6/lag3
    solace(configure/interface)# primary-member 1/6/lag2

    solace(configure/interface)# no shut
    solace(configure/interface)# end
  4. View the status and configuration of the bonding LAG in Active/Backup Mode. 
    solace> show interface 1/6/lag1
    Interface: 1/6/lag1 
  MAC address: 00:50:c2:44:c0:ba
  Mode: Active-Backup
  Enabled: yes
  Rx pkts:             4836        Rx bytes:           436867
  Tx pkts:                6        Tx bytes:              768
 
  Configured members:  1/6/lag2 1/6/lag3 
  Available members:   1/6/lag2  1/6/lag3
  Operational members: 1/6/lag2 
  Primary member:      1/6/lag2