Port Security Database Merge Guidelines
Scenario
A and B exist in the
configuration database,
activation is not done and
devices C,D are logged
in.
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
If you do not follow these two conditions, the merge will fail. The next distribution will forcefully
Caution
synchronize the databases and the activation states in the fabric.
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
648
Actions
3. You issue a commit.
1. You activate the port
security database and
enable auto-learning.
2. You disable learning.
3. You issue a commit.
2000.
Distribution = OFF
Distribution = ON
Not applicable
configuration database =
{A,B, E}
active database = {A,B,
E, C*, D*}
pending database = empty
configuration database =
configuration database =
{A,B}
{A,B}
active database = {A,B,
active database = {null}
C*, D*}
pending database = {A,B
+ activation to be
enabled}
configuration database =
configuration database =
{A,B}
{A,B}
active database = {A,B,
active database = {null}
C, D}
pending database = {A,B
+ activation to be enabled
+learning to be disabled}
Not applicable
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
Configuring Port Security
OL-16597-01