Brocade FastIron Ethernet Switch Stacking Configuration Guide - Manual (Page 87)

For more information about Syslog messages, refer to the FastIron Ethernet Switch Administration
Guide.
Configuring SNMP for a traditional stack
SNMP server and feature configuration is the same for a traditional stack as it is for standalone units. In
a traditional stack, SNMP gets and sets are processed by the active controller for the standby controller
and all stack members. SNMP traps generated by the standby controller and stack members are
propagated to the configured SNMP server through the active controller. For more information about
how to configure an SNMP server for FastIron devices, refer to the FastIron Ethernet Switch
Administration Guide.
SNMP engine IDs for stackable devices
For Brocade stacking devices, if an engine ID is not manually created or a stack MAC address is not
specified and saved, the stack will lose its engine ID if the active controller fails and the standby
controller takes over, because the standby controller creates a new engine ID at bootup. To prevent this
from happening, you will need to either create a new engine ID or create a new stack MAC address to
ensure that the engine ID is saved to the startup configuration. This should be done before the SNMPv3
user is created.
If a new active controller is elected (for example, the standby controller becomes the active controller)
you will see the following results:
• If you have configured the engine ID saved it to the startup configuration file, the new stack
configuration will use the saved engine ID.
• If you have not configured an engine ID, but a stack MAC address is configured, the new stack
configuration will retain the original engine ID since it is based on the stack MAC address.
• If you have not configured an engine ID, and no stack MAC address is configured, the new stack
configuration will use the default engine ID, which is based on its own management MAC address
of the new active controller. Since the engine ID will have changed, any SNMPv3 Clients will need
to be reconfigured with the new engine ID.
Traditional stack troubleshooting
The most common reason for an unsuccessful stack build is either a software configuration mismatch, a
hardware configuration mismatch, or a combination of both.
The following sections describe common troubleshooting procedures for a traditional stack.
Troubleshooting an unsuccessful stack build
If you are unable to build a stack, (for example, the show stack command does not display any stack
units), perform the following steps.
1. Enter the show run command on each unit to make sure the configuration contains “stack enable.”
If it does not, enter the stack enable command on the unit. Before a stack is formed, you can still
access the console port on each device. Once a stack is successfully formed, you are redirected to
the active controller.
Configuring SNMP for a traditional stack
FastIron Ethernet Switch Stacking Configuration Guide 85
53-1003090-02