1. Manuals
  2. Brands
  3. Extreme Networks Manuals
  4. Accessories
  5. BlackDiamond 6800
  6. User manual

Extreme Networks BlackDiamond 6800 User Manual

Extreme blackdiamond 6800: supplementary guide
Hide thumbs Also See for BlackDiamond 6800:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Installation Manual
Hitless Failover and
Hitless Upgrade User Guide
This guide describes hitless failover and hitless upgrade, including:
T-sync is a term used to describe the hitless failover and hitless upgrade features available on the
BlackDiamond
®
Management Switch Module 3 (MSM-3). In simple terms, hitless failover transfers switch
management control from the master MSM-3 to the slave MSM-3 without causing traffic to be dropped.
Hitless upgrade allows an ExtremeWare
®
software upgrade on a BlackDiamond 6800 series chassis
without taking it out of service or losing traffic.
To configure hitless failover or hitless upgrade, you must install MSM-3 modules in your BlackDiamond
chassis; MSM64i modules do not support hitless failover or hitless upgrade.
If you enable T-sync and normally use scripts to configure your switch, Extreme Networks recommends
using the
command instead.
download configuration incremental
NOTE
To use the T-sync features available on the MSM-3 modules, you must install and run ExtremeWare
7.1.1 or later and BootROM 8.1 or later.

Causes and Behaviors of MSM Failover

This section describes the events that cause an MSM failover and the behavior of the system after
failover occurs.
The following events cause an MSM failover:
• Operator command
Part Number: 121071-00 Rev 01
1

Advertisement

Table of Contents
loading

Related Manuals for Extreme Networks BlackDiamond 6800

Summary of Contents for Extreme Networks BlackDiamond 6800

  • Page 1: Table Of Contents

    To configure hitless failover or hitless upgrade, you must install MSM-3 modules in your BlackDiamond chassis; MSM64i modules do not support hitless failover or hitless upgrade. If you enable T-sync and normally use scripts to configure your switch, Extreme Networks recommends using the command instead.
  • Page 2 If you hard-reset the master MSM-3 (using the recessed reset button on the MSM-3), all of the master’s switch programming is lost. As a result, traffic that the I/O module forwards to the master is also lost. Hitless Failover and Hitless Upgrade User Guide...

  • Page 3: Summary Of Supported Features

    After a failover occurs, the new master reprograms the “reset” MSM-3’s switch fabric and the switching logic of both MSM-3s is available again. In this case, the “Cause of last MSM failover” displayed by the command indicates “removal,” and a “partial” hitless failover has occurred.
  • Page 4 To save your changes after a hitless failover, use the NOTE If you have a BlackDiamond 6816 switch populated with four MSM-3 modules, the MSMs in slots C and D provide extra switch bandwidth; they do not participate in switch management functions.

  • Page 5: Configuring Hitless Failover

    You can also configure ESRP hitless failover behavior. See “Configuring ESRP for Hitless Failover” on page 8 for more information. To use the hitless failover feature, you must have a BlackDiamond 6800 series chassis installed with MSM-3 modules running ExtremeWare 7.1.1 or later and BootROM 8.1 or later.
  • Page 6 Configuring Hitless Failover For more information about this command, see the following chapters: • “Status Monitoring and Statistics” in the ExtremeWare Software User Guide • “Commands for Status Monitoring and Statistics” in the ExtremeWare Command Reference Guide Inheriting the Master’s Software Configuration To enable the slave MSM-3 to inherit the software configuration from the master MSM-3, use the following command: configure msm-failover slave-config [inherited | flash]...

  • Page 7: Configuring Timers

    Configuring Timers For switch management functions to hitlessly transition between the master and the slave, timer expiration is required. When you initiate hitless failover, the failover timer begins. The failover timer configures the time it takes from when hitless failover begins until the relearned layer 3 databases are linked to the FDB.

  • Page 8: Configuring Esrp For Hitless Failover

    After a reboot or insertion of a slave MSM-3, use this command to ensure that the slave is ready before initiating a hitless failover. Configuring ESRP for Hitless Failover Extreme Standby Router Protocol (ESRP) operates at both the layer 2 and layer 3 levels. An ESRP instance has the following states: • Neutral—The initial state when ESRP is enabled.
  • Page 9 OSPF, BGP, RIP IP Route Ping For more information about ESRP and ESRP tracking, see the chapter “Extreme Standby Routing Protocol” in the ExtremeWare Software User Guide. Hitless Failover and Hitless Upgrade User Guide —Specifies that ESRP behaves as if —Specifies that an ESRP master notifies the standby nodes of...

  • Page 10: Overview Of Hitless Upgrade

    As described previously, when you install two MSM-3 modules in a BlackDiamond chassis, one assumes the role of master and the other assumes the role of slave. The master executes the switch’s management function, and the slave acts in a standby role. Hitless upgrade (a component of T-sync) is a...

  • Page 11: Performing A Hitless Upgrade

    D provide extra switch bandwidth; they do not participate in switch management functions. To use the hitless upgrade feature, you must have a BlackDiamond 6800 series chassis installed with MSM-3 modules running ExtremeWare 7.1.1 or later and BootROM 8.1 or later.
  • Page 12 • You configured the system for hitless failover operation (see “Configuring Hitless Failover” on page 5 for more information) NOTE If you have an active Telnet session and initiate a hitless failover on that switch, the session disconnects when failover occurs. To failover to the same, new software image, do the following: 1 Download the new software image to the primary image space using the following command: download image [<hostname>...
  • Page 13 • You configured the system for hitless failover operation (see “Configuring Hitless Failover” on page 5 for more information) NOTE If you have an active Telnet session and initiate a hitless failover on that switch, the session disconnects when failover occurs. To failback to the previous software image, do the following:...

  • Page 14: Troubleshooting

    Troubleshooting If you encounter problems during a hitless upgrade, this section may be helpful. If you have a problem not listed here or in the release notes, contact your Extreme Networks Technical Support representative. MSM-3 Initialization If the slave MSM-3 does not initialize properly, you can restart the MSM hardware, including the switch...
  • Page 15 Each subsystem classifies its messages between the master and slave. If the slave does not recognize a message classifier, an error occurs. comm error This error message is currently not in use. If you see this message, contact Extreme Networks Technical Support. no xh support This error message is currently not in use.
  • Page 16 Performing a Hitless Upgrade Table 2: Descriptions of failover reason codes (continued) Reason Code Description config failed This error message is currently not in use. If you see this message, contact Extreme Networks Technical Support. keepalive Contact Extreme Networks Technical Support. watchdog Contact Extreme Networks Technical Support.

This manual is also suitable for:

Msm-3Hitless failoverHitless

Table of Contents