Cisco Nexus 5000 Series Switch CLI Software Configuration Guide (OL-16597-01, July 2009)

Distribution = ONDistribution = OFFActionsScenario
configuration database =
{A,B, E}
Not applicable3. You issue a commit.
active database = {A,B,
E, C*, D*}
pending database = empty
configuration database =
{A,B}
configuration database =
{A,B}
1. You activate the port
security database and
enable auto-learning.
A and B exist in the
configuration database,
activation is not done and
devices C,D are logged
in.
active database = {null}
pending database = {A,B
+ activation to be
enabled}
active database = {A,B,
C*, D*}
configuration database =
{A,B}
configuration database =
{A,B}
2. You disable learning.
active database = {null}active database = {A,B,
C, D}
pending database = {A,B
+ activation to be enabled
+learning to be disabled}
configuration database =
{A,B}
Not applicable3. You issue a commit.
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
Port Security Database Merge Guidelines
A database merge refers to a union of the configuration database and static (unlearned) entries in the active
database.
When merging the database between two fabrics, follow these guidelines:
• 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.
If you do not follow these two conditions, the merge will fail. The next distribution will forcefully
synchronize the databases and the activation states in the fabric.
Caution
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
648 OL-16597-01
Configuring Port Security
Port Security Database Merge Guidelines