Database Merge Guidelines - Cisco AJ732A - MDS 9134 Fabric Switch Configuration Manual

Database Merge Guidelines

S e n d f e e d b a c k t o n x 5 0 0 0 - d o c f e e d b a c k @ c i s c o . c o m
If the pending database contains more than one activation and auto-learning configuration when you
commit the changes, the activation and auto-learning changes are consolidated and the resulting
operation may change (see
Table 45-3 Scenarios for Activation and Auto-learning Configurations in Distributed Mode
Scenario Actions
A and B exist in the You activate the port
1.
configuration security database and
database, enable auto-learning.
activation is not
done and devices
C,D are logged in.
2. A new entry E is
added to the
configuration
database.
3. You issue a commit.
A and B exist in the You activate the port
1.
configuration security database and
database, enable auto-learning.
activation is not
done and devices
C,D are logged in.
2. You disable learning. configuration database = {A,B}
3. You issue a commit.
1. The * (asterisk) indicates learned entries.
Database Merge Guidelines
A database merge refers to a union of the configuration database and static (unlearned) entries in the
active database. See the
When merging the database between two fabrics, follow these guidelines:
•
•
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
45-14
Table
Distribution = OFF
configuration database = {A,B}
active database = {A,B, C
configuration database = {A,B,
E}
active database = {A,B, C*, D*}
Not applicable
configuration database = {A,B}
active database = {A,B, C*, D*}
active database = {A,B, C, D}
Not applicable
"CFS Merge Support" section on page 21-6
Verify that the activation status and the auto-learning status is the same in both fabrics.
Verify that the combined number of configurations for each VSAN in both databases does not
exceed 2000.
45-3).
1
, D*}
Chapter 45 Configuring Port Security
Distribution = ON
configuration database = {A,B}
active database = {null}
pending database = {A,B + activation to
be enabled}
configuration database = {A,B}
active database = {null}
pending database = {A,B, E + activation
to be enabled}
configuration database = {A,B, E}
active database = {A,B, E, C*, D*}
pending database = empty
configuration database = {A,B}
active database = {null}
pending database = {A,B + activation to
be enabled}
configuration database = {A,B}
active database = {null}
pending database = {A,B + activation to
be enabled +
learning to be disabled}
configuration database = {A,B}
active database = {A,B} and devices C
and D are logged out. This is equal to an
activation with auto-learning disabled.
pending database = empty
for detailed concepts.
OL-16597-01