HP Cisco Nexus 5000 Cisco Nexus 5000 Series Switch CLI Software Configuration - Page 694

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