Brocade Communications Systems Network Advisor 12.3.0, User Manual

Page: 105 / 1940

Brocade Network Advisor SAN User Manual 53
53-1003154-01
SAN Seed switch
3
SAN Seed switch
The seed switch must be running a supported Fabric OS version and must be HTTP-reachable.
Sometimes, the seed switch is auto-selected, such as when a fabric segments or when two fabrics
merge. Other times, you are prompted (an event is triggered) to change the seed switch, such as in
the following cases:
•
If, during fabric discovery, the Management application detects that the seed switch is not
running a supported version, you are prompted to change the seed switch.
•
When one or more switches join the fabric or if the switch firmware is changed on any of the
switches in the fabric, the Management application checks to make sure that the seed switch
is still running a supported version. If it is not, then you are prompted to either upgrade the
firmware on the seed switch or to change the seed switch to a switch running a supported
firmware.
If a fabric of switches running only Fabric OS 5.X or later is created due to segmentation, the
Management application continues to monitor that fabric, but if any switch with a later Fabric OS
version joins the fabric, an event is triggered informing you that the seed switch is not running the
latest firmware and you should change to the seed switch running the highest firmware.
ATTENTION
If a seed switch is segmented or merged, historical data such as offline zone DB, profile and reports,
and Firmware Download Profile can be lost. Segmentation of a seed switch does not result in
formation of a new fabric. If a merge occurs, the historical data is lost only from the second fabric.
You can change the seed switch as long as the following conditions are met:
•
The new seed switch is HTTP-reachable from the Management application.
•
The new seed switch is a primary FCS.
•
The new seed switch is running the latest Fabric OS version in the fabric.
This operation preserves historical and configuration data, such as performance monitoring and
user-customized data for the selected fabric.
ATTENTION
If the seed switch firmware is downgraded from Fabric OS 5.2.X to an earlier version, then all
RBAC-related data is discarded from the Management application.
If, during the seed switch change, the fabric is deleted, but the rediscovery operation fails (for
example, if the new seed switch becomes unreachable using HTTP), then you must rediscover the
fabric again. If you rediscover the fabric using a switch that was present in the fabric before the
change seed switch operation was performed, then all of the historical and configuration data is
restored to the rediscovered fabric. If you rediscover the fabric using a switch that was added to the
fabric after the fabric was deleted, then the historical and configuration data is lost.
If multiple users try to change the seed switch of the same fabric simultaneously, only the first
change seed switch request is executed; subsequent requests that are initiated before the first
request completes will fail.
If another user changes the seed switch of a fabric you are monitoring, and if you have provided
login credentials for only that seed switch in the fabric, then you lose connection to the seed
switch.