Cisco Nexus 5000 Series Switch Fabric Manager Software Configuration Guide, NX-OS 4.0 (OL-16598-01, June 2008)

Send comments to [e-mail]
24-16
Nexus 5000 Series Switch Fabric Manager Software Configuration Guide
OL-16598-01
Chapter 24 Configuring Port Security
Port Security Configuration Distribution
This section contains the following topics:
• Enabling Distribution, page 24-16
• Locking the Fabric, page 24-16
• Committing the Changes, page 24-17
• Activation and Auto-Learning Configuration Distribution, page 24-17
Enabling Distribution
All the configurations performed in distributed mode are stored in a pending (temporary) database. If
you modify the configuration, you need to commit or discard the pending database changes to the
configurations. The fabric remains locked during this period. Changes to the pending database are not
reflected in the configurations until you commit the changes.
Note Port activation or deactivation and auto-learning enable or disable do not take effect until after a CFS
commit if CFS distribution is enabled. Always follow any one of these operations with a CFS commit to
ensure proper configuration. See the “Activation and Auto-Learning Configuration Distribution” section
on page 24-17.
Tip We recommend that you perform a commit after you activate port security and after you enable auto
learning.
To enable distribution using Fabric Manager, perform this task:
Step 1 Expand a VSAN and then choose Port Security in the Logical Domains pane.
You see the port security configuration for that VSAN in the Information pane as shown in Figure 24-4.
Step 2 Click the Control tab.
You see the switches for that VSAN.
Step 3 In the Command column, choose enable or disable from the drop-down list.
Step 4 Click the Apply Changes icon to save the changes.
Locking the Fabric
The first action that modifies the existing configuration creates the pending database and locks the
feature in the VSAN. Once you lock the fabric, the following situations apply:
• No other user can make any configuration changes to this feature.
• A copy of the configuration database becomes the pending database.