H3C Technologies H3C S5830V2 Series Switches - Manual (Page 102)

91
3. The manager switch sends an SFC request to all managed switches. The SFC request carries data
to be synchronized, including the active zone set and zone database information. After receiving
the SFC request with zone database information, the managed switch determines whether the total
number of zones, zone sets, and zone aliases exceeds the limit after its local zone database is
replaced.
{
If the limit is not exceeded, the managed switch replies with an ACC packet.
{
If the limit is exceeded, the managed switch replies with an RJT packet.
4. The manager switch notifies managed switches by sending a UFC request to replace their local
data with the received data only after receiving ACC packets from all managed switches.
Otherwise, it notifies managed switches to release the change authorization state by sending an
RCA request.
5. After receiving the UFC request, the managed switch updates its local zone database. It replies
with an ACC packet for a successful update and with an RJT packet for a failed update.
6. The manager switch notifies managed switches by sending an RCA request to release the change
authorization state after receiving ACC packets from all managed switches.
7. After receiving the RCA request, the managed switch releases its change authorization state and
replies with an ACC packet.
8. The manager switch releases its change authorization state after receiving ACC packets from all
managed switches.
Zone merge
When two fabrics are merged, both the active zone set and zone database might exist in each fabric. In
this case, zone configuration information needs to be merged.
The following merge types are provided:
• Complete merge—Merges both the active zone sets and zone databases.
• Incomplete merge—Merges only the active zone sets.
When initiating a merge process, the merge-originating switch checks its local merge type:
• If it is configured with complete merge, it sends packets with both the active zone set and zone
database.
• If it is configured with incomplete merge, it sends packets with only the active zone set.
The merged switches merge all received data, regardless of the their merge types.
NOTE:
The pWWN is a preferred choice over FC addresses to identify zone members, because FC addresses
might change at fabric merge and the merge result might not be as expected by users.
Zone merge process
When a switch discovers a new neighbor (the link layer module discovers neighbors and notifies the
zone module), it starts a merge process with the neighbor. If the data changes after merging, the switch
sends the changed data to neighbor switches until all switches in the fabric update their data.
During the merge, the switch sends Merge Request Resource Allocation (MRRA) requests to negotiate the
size of data transmitted and then Merge Request (MR) packets containing data to be merged to neighbor
switches.