Brocade Network Advisor SAN + IP User Manual v12.1.0 - Manual (Page 145)

78 Brocade Network Advisor SAN + IP User Manual
53-1002949-01
Logical chassis cluster mode discovery
4
• Uses the IP address of any member of the logical chassis cluster for discovery.
• Sets the cluster IP address to the IP address of the principal node.
NOTE
You can change the principal node for the cluster by running the logical-chassis
principal-priority command from the NOS prompt. For more information, refer to the Network
OS Command Reference.
• Principal-switch failover does not occur if the cluster is unstable (for example, if the chassis
had been disabled for maintenance) because refresh collection will fail.
• If the cluster is configured with a virtual IP address before its discovery, and then discovery is
initiated, the cluster IP displays the virtual IP address instead of the IP address of the principal
node.
• If the cluster is configured with a virtual IP address after it is discovered by the Management
application, the virtual IP address is collected and saved in the database for the next lazy
polling or next adaptive collection.
• If another switch becomes the principal switch, the Management application sets the cluster IP
address to that of the new principal switch at the next lazy polling or next adaptive collection.
• The State column in the Discover Setup - IP dialog shown in Figure 12 applies only to nodes
that are in logical chassis mode. Possible states are:
- Online—A node that is currently connected and operational.
- On discovery, only online members are considered active cluster members. The
Management application server collects the device, port, and LAG information of active
cluster members. The the Management application client displays the member node as a
cluster member in the Ethernet Fabrics topology.
- Offline—A cluster member node that cannot be reached by the primary cluster node.
- On refresh, if the member was an active member of a cluster and is now offline, the
member is marked as missing. If the member is not online after three consecutive short
ticks, auto-discovery gets initiated. If auto-chasing fails, the member remains missing.
- Rejoining—A node that is in the process of rejoining its cluster.
- On refresh, if the member was an active member of the cluster and is now rejoining, then
the member is marked as missing. If the member is not online after three consecutive
short ticks, auto discovery gets initiated. If auto chasing fails, the member remains
missing.
- Replacing—A node that is being replaced.
- On refresh, if a member node is in the Replacing state, the member is shown as missing.
- If the member is in the Replacing state for more than three consecutive short ticks,
auto-discovery gets initiated. If auto-chasing fails, the member remains missing.