Cisco N5010P-N2K-BE, Software Configuration Manual

Page: 630 / 704

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
45-14
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
OL-16597-01
Chapter 45 Configuring Port Security
Database Merge Guidelines
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 ).
Database Merge Guidelines
A database merge refers to a union of the configuration database and static (unlearned) entries in the
active database. See the
“CFS Merge Support” section on page 21-6 for detailed concepts.
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.
Table 45-3 Scenarios for Activation and Auto-learning Configurations in Distributed Mode
Scenario Actions Distribution = OFF Distribution = ON
A and B exist in the
configuration
database,
activation is not
done and devices
C,D are logged in.
1.
You activate the port
security database and
enable auto-learning. configuration database = {A,B}
active database = {A,B, C
1
, D*}
1. The * (asterisk) indicates learned entries.
configuration database = {A,B}
active database = {null}
pending database = {A,B + activation to
be enabled}
2.
A new entry E is
added to the
configuration
database. configuration database = {A,B,
E}
active database = {A,B, C*, D*}
configuration database = {A,B}
active database = {null}
pending database = {A,B, E + activation
to be enabled}
3.
You issue a commit. Not applicable configuration database = {A,B, E}
active database = {A,B, E, C*, D*}
pending database = empty
A and B exist in the
configuration
database,
activation is not
done and devices
C,D are logged in. 1. You activate the port
security database and
enable auto-learning. configuration database = {A,B}
active database = {A,B, C*, D*}
configuration database = {A,B}
active database = {null}
pending database = {A,B + activation to
be enabled}
2.
You disable learning. configuration database = {A,B}
active database = {A,B, C, D}
configuration database = {A,B}
active database = {null}
pending database = {A,B + activation to
be e
learning to be disabled}
3.
You issue a commit. 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