Filter
Top Products
160 PowerConnect B-Series FCX Configuration Guide
53-1002266-01
More about IronStack technology
5
• Active Controller
• Standby Controller
• Stack member
Active Controller
The Active Controller contains the saved and running configuration files for each stack member.
The configuration files include the system-level settings for the stack, and the interface-level
settings for each stack member, as well as MIB counters and port status. The Standby Controller
also has a synchronized copy of the Active Controller startup config file for use in the event the
Active Controller fails.
When a stack is formed, the console function for each stack member is automatically redirected to
the Active Controller console. The Active Controller console port handles all stack management
functions, as well as ping, Telnet sessions, and tftp image downloads for every stack member. If
you connect to the console port on a stack member that is not the Active Controller, you are
automatically directed through the console of the Active Controller.
The Active Controller synchronizes its start-up configuration with the Standby Controller and the
rest of the stack members. You can recover the previous flash configuration of the Standby
Controller and the stack members by issuing the stack unconfigure command. For an example of
this command and the output generated, refer to “Unconfiguring an IronStack” on page 130.
The Active Controller may reset the rest of the stack members, if necessary. However, if the Active
Controller itself must be reset because of a role or ID change, you must issue the reset command.
If the Active Controller fails, the Standby Controller waits 30 seconds, and then takes over as Active
Controller, resetting itself and all other stack members. If the old Active Controller becomes
operational, it may or may not resume its role as Active, depending on the configured priorities.
Standby Controller
In addition to the Active Controller, another stack member is elected as the Standby Controller.
After a default interval of 30 seconds, the Standby Controller takes over if the Active Controller
fails.
NOTE
Because it can take as long as 20 seconds to age out a neighbor, the Standby takeover period may
last up to 50 seconds. Refer to “Port down and aging” on page 159.)
The Standby Controller synchronizes its configuration with the Active Controller at each reset.
Bootup role
When a stack unit boots, it boots in a particular role, such as standalone, Active Controller, Standby
Controller, or stack member. When the bootup role is Standby Controller or stack member, the CLI
available to the unit is limited to show and stack commands. A unit in the role of Standby or stack
member will not act without instructions from the Active Controller. To convert a Standby Controller
or stack member into a standalone device, use the stack unconfigure me command, (refer to
“Unconfiguring an IronStack” on page 130).
The last line of the show version output identifies the unit role unless the unit is in standalone
mode.