S-Series Virtual Switch Bonding chassis replacement procedure

[FAQ_User]

Article ID: 14688

Products
S-Series
Standalone (SSA) systems, firmware 7.61.01.0005 or higher
Chassis-based systems, firmware 7.71.01.0010 or higher

Goals
Replace a failed chassis, one of a pair of chassis running Virtual Switch Bonding (VSB) to form a single unified system, without loss of VSB configuration.

Solution
It will be necessary to largely configure VSB on the replacement chassis, so the first step is to determine some of the ongoing VSB settings. Do not attach the VSB interconnect cable(s) yet, between the still-functioning VSB peer chassis and the replacement chassis.

* Collect VSB information from the functioning peer chassis *

Assuming that the failed VSB chassis is unuseable and there is no saved copy of the full VSB configuration, gain management access to the functioning peer VSB chassis - via serial (12453), Telnet, or SSH session - and collect information as follows:

Using the '

code:

show config bonding

' command, access VSB configuration commands which include the currently functioning chassis instance (either

code:

1

or

code:

2

), the configured system-id value, and the number of 10-gig ports being used as bonding interconnects.

code:

Bonded SSA Chassis(su)-

>

show config bonding

code:

This command shows non-default configurations only.

code:

Use 'show config all' to show both default and non-default configurations.

code:

begin

code:

!

code:

# ***** NON-DEFAULT CONFIGURATION *****

code:

!

code:

!

code:

# Chassis Firmware Revision: 07.71.01.0010

code:

!

code:

# bonding

code:

set bonding

chassis 2

system-id 1

code:

serial-number 11536214686C

code:

set bonding

port tg.2.1

code:

enable

code:

set bonding enable

code:

!

code:

end

code:

Bonded SSA Chassis(su)-

>

Here, chassis instance

code:

2

is functioning (meaning that the replacement chassis will be configured as instance 1), the system-id is "

code:

1

" and must be replicated, and one 10-gig port (presumably

code:

tg.1.1

but this may as desired be changed) will need to be configured for VSB on the new chassis 1.

Using the '

code:

show config license

' command, access the VSB license commands:

code:

Bonded SSA Chassis(su)-

>

show config license

code:

This command shows non-default configurations only.

code:

Use 'show config all' to show both default and non-default configurations.

code:

begin

code:

!

code:

# ***** NON-DEFAULT CONFIGURATION *****

code:

!

code:

!

code:

# Chassis Firmware Revision: 07.71.01.0010

code:

!

code:

# license

set license vsb "0001:SSA-EOS-VSB:1:4c804c0c:0:Enterasys Networks GTAC:0:80862a4d:p8bhDiSOEtY3dxhw1O6BX7lZjK56gLV9twGBChA/UMDcBnF3uS4ah9DMnXFJMzw8cXaBpNoz6o9D/vnprn3XtQ==" chassis 1

code:

set license vsb "0001:SSA-EOS-VSB:1:4c804bb7:0:Enterasys Networks GTAC:0:80862a4d:raxhEcEU3OFzDr7G1cSncFXgwg2Erl49rbe4B3nNJ6OUcf2j/DPhg2VVP2GwKOBc1570GcxPEY6TntI8E6XnCw==" chassis 2

code:

!

code:

end

code:

Bonded SSA Chassis(su)-

>

Since the replacement chassis will be configured as VSB instance 1, it is only necessary that the license command for chassis 1 be captured.

Now using the '

code:

show config outfile

' command, save the full system configuration to an available slot on the still-functioning chassis instance 2. Here, working with SSA standalone units, that would be slot 2:

code:

Bonded SSA Chassis(su)-

>

show config outfile slot2/fullConfig.cfg

* Configure VSB on the replacement chassis *

Close the management session to the functioning VSB peer chassis, and open a new management session to the replacement chassis - then configure it as (in this case) VSB chassis 1:

code:

SSA Chassis(su)-

>

set license vsb "0001:SSA-EOS-VSB:1:4c804c0c:0:Enterasys Networks GTAC:0:80862a4d:p8bhDiSOEtY3dxhw1O6BX7lZjK56gLV9twGBChA/UMDcBnF3uS4ah9DMnXFJMzw8cXaBpNoz6o9D/vnprn3XtQ==" chassis 1

code:

SSA Chassis(su)-

>

set bonding chassis 1 system-id 1

code:

SSA Chassis(su)-

>

set bonding port tg.1.1 enable

code:

SSA Chassis(su)-

>

set bonding enable

code:

This command will reset the system and clear the current running configuration.

code:

Are you sure you want to continue? (y/n) ?

y

code:

SSA Chassis(su)-

>

Then, connect the VSB cable(s) to join the two chassis. Here is the console output from chassis 2, showing chassis 1 successfully joining:

<

code:

165

>

code:

May 30 16:56:09 0.0.0.0 LinkTrap[2]Interface tg.2.1 is Up.

<

code:

165

>

code:

May 30 16:56:22 0

.

code:

0

.

code:

0

.

code:

0 Bonding[2]Bond Link added port tg.2.1

<

code:

165

>

code:

May 30 16:56:23 0.0.0.0 Bonding[2]Chassis 00:1f:45:a1:18:0a added as a new member of bonded chassis 00:1f:45:fb:78:75 at index 0 slot 1.

<

code:

165

>

code:

May 30 16:56:33 0

.

code:

0

.

code:

0

.

code:

0 Bonding[2]Bond Link removed port tg.2.1: probe loss

code:

Bonded SSA Chassis(su)-

><

code:

165

>

code:

May 30 16:57:44 0

.

code:

0

.

code:

0

.

code:

0 Bonding[2]Bond Link added port tg.2.1

<

code:

163

>

code:

May 30 16:57:55 0.0.0.0 System[2]Module in slot 1 was replaced with a board of the same type. MAC=001f45a11809

<

code:

165

>

code:

May 30 16:57:58 0.0.0.0 System[2]Requesting a copy of the non-volatile store for slot 1.

<

code:

163

>

code:

May 30 16:57:59 0.0.0.0 System[2]Copying of slot 2's non-volatile storage to 1 complete.

<

code:

165

>

code:

May 30 16:57:59 0.0.0.0 System[2]The board in slot 1 of the chassis is operational.

<

code:

163

>

code:

May 30 16:57:58 0.0.0.0 System[1]Finished receiving a copy of slot 2's store.

<

code:

163

>

code:

May 30 16:57:59 0.0.0.0 System[1]Copying of slot 1's non-volatile storage to 2 complete.

<

code:

163

>

code:

May 30 16:57:59 0.0.0.0 System[2]Finished receiving a copy of slot 1's store.

The '

code:

show bonding

' and '

code:

show config

' commands will be helpful to view the recovering VSB system.

At this point, bonding should come up and be functional, but no configuration will be present on the replacement chassis other than the license/bonding lines just added.

Reload the full system configuration onto both bonded chassis. To prevent having to reboot the system, use the configure command with the append option. While some configuration lines will error out because they are already applied to chassis 2, this operation should allow the entire config to get pushed to the replacement unit (chassis 1) so that the bonded system can begin functioning normally.

code:

Bonded SSA Chassis(su)-

>

configure slot1/fullConfig.txt append

For more detailed instructions and VSB background, please refer to the Enterasys Virtual Switching Technology Brief, CLI Reference Guide, and Configuration Guide; all available from the

code:

Documentation

tab on the S-Series downloads page.
Also see this HowTo Video which walks the user through initial VSB configuration.