Configuring Port Security
All switches in the Cisco MDS 9000 Family provide port security features that reject intrusion attempts and report these intrusions to the administrator.
This chapter includes the following topics:
Information About Port Security
All switches in the Cisco MDS 9000 Family provide port security features that reject intrusion attempts and report these intrusions to the administrator.
Typically, any Fibre Channel device in a SAN can attach to any SAN switch port and access SAN services based on zone membership. Port security features prevent unauthorized access to a switch port in the Cisco MDS 9000 Family in the following ways:
- Login requests from unauthorized Fibre Channel devices (Nx ports) and switches (xE ports) are rejected.
- All intrusion attempts are reported to the SAN administrator through system messages.
- Configuration distribution uses the CFS infrastructure, and is limited to those switches that are CFS capable. Distribution is disabled by default.
- Configuring the port security policy requires the ENTERPRISE_PKG license (see the Cisco MDS 9000 Family NX-OS Licensing Guide).
This section includes the following topics:
Port Security Enforcement
To enforce port security, configure the devices and switch port interfaces through which each device or switch is connected, and activate the configuration.
- Use the port world wide name (pWWN) or the node world wide name (nWWN) to specify the Nx port connection for each device.
- Use the switch world wide name (sWWN) to specify the xE port connection for each switch.
Each Nx and xE port can be configured to restrict a single port or a range of ports.
Enforcement of port security policies are done on every activation and when the port tries to come up.
The port security feature uses two databases to accept and implement configuration changes.
- Configuration database—All configuration changes are stored in the configuration database.
- Active database—The database currently enforced by the fabric. The port security feature requires all devices connecting to a switch to be part of the port security active database. The software uses this active database to enforce authorization.
About Auto-Learning
You can instruct the switch to automatically learn (auto-learn) the port security configurations over a specified period. This feature allows any switch in the Cisco MDS 9000 Family to automatically learn about devices and switches that connect to it. Use this feature when you activate the port security feature for the first time as it saves tedious manual configuration for each port. You must configure auto-learning on a per-VSAN basis. If enabled, devices and switches that are allowed to connect to the switch are automatically learned, even if you have not configured any port access.
When auto-learning is enabled, learning happens only for the devices or interfaces that were not already logged into the switch. Learned entries on a port are cleaned up after you shut down that port if auto-learning is still enabled.
Learning does not override the existing configured port security policies. So, for example, if an interface is configured to allow a specific pWWN, then auto-learning will not add a new entry to allow any other pWWN on that interface. All other pWWNs will be blocked even in auto-learning mode.
No entries are learned for a port in the shutdown state.
When you activate the port security feature, auto-learning is also automatically enabled.
![]() Note |
If you enable auto-learning before activating port security, you cannot activate until auto-learning is disabled. |
Port Security Activation
By default, the port security feature is not activated in any switch in the Cisco MDS 9000 Family.
By activating the port security feature, the following apply:
-
Auto-learning is also automatically enabled, which means:
- From this point, auto-learning happens only for the devices or interfaces that were not logged into the switch.
- You cannot activate the database until you disable auto-learning.
- All the devices that are already logged in are learned and are added to the active database.
- All entries in the configured database are copied to the active database.
After the database is activated, subsequent device login is subject to the activated port bound WWN pairs, excluding the auto-learned entries. You must disable auto-learning before the auto-learned entries become activated.
When you activate the port security feature, auto-learning is also automatically enabled. You can choose to activate the port security feature and disable auto-learning.
![]() Tip |
If a port is shut down because of a denied login attempt, and you subsequently configure the database to allow that login, the port does not come up automatically. You must explicitly issue a no shutdown CLI command to bring that port back online. |
Database Activation Rejection
Database activation is rejected in the following cases:
- Missing or conflicting entries exist in the configuration database but not in the active database.
- The auto-learning feature was enabled before the activation. To reactivate a database in this state, disable auto-learning.
- The exact security is not configured for each PortChannel member.
- The configured database is empty but the active database is not.
If the database activation is rejected due to one or more conflicts listed in the previous section, you may decide to proceed by forcing the port security activation.
About Enabling Auto-learning
The state of the auto-learning configuration depends on the state of the port security feature:
- If the port security feature is not activated, auto-learning is disabled by default.
- If the port security feature is activated, auto-learning is enabled by default (unless you explicitly disabled this option).
![]() Tip |
If auto-learning is enabled on a VSAN, you can only activate the database for that VSAN by using the force option. |
Auto-learning Device Authorization
Table 1 summarizes the authorized connection conditions for device requests.
Condition |
Device (pWWN, nWWN, sWWN) |
Requests Connection to |
Authorization |
---|---|---|---|
1 |
Configured with one or more switch ports |
A configured switch port |
Permitted |
2 |
Any other switch port |
Denied |
|
3 |
Not configured |
A switch port that is not configured |
Permitted if auto-learning enabled |
4 |
Denied ifauto-learning disabled |
||
5 |
Configured or not configured |
A switch port that allows any device |
Permitted |
6 |
Configured to log in to any switch port |
Any port on the switch |
Permitted |
7 |
Not configured |
A port configured with some other device |
Denied |
Authorization Scenarios
Assume that the port security feature is activated and the following conditions are specified in the active database:
- A pWWN (P1) is allowed access through interface fc1/1 (F1).
- A pWWN (P2) is allowed access through interface fc1/1 (F1).
- A nWWN (N1) is allowed access through interface fc1/2 (F2).
- Any WWN is allowed access through interface fc1/3 (F3).
- A nWWN (N3) is allowed access through any interface.
- A pWWN (P3) is allowed access through interface fc1/4 (F4).
- A sWWN (S1) is allowed access through interface fc1/10-13 (F10 to F13).
- A pWWN (P10) is allowed access through interface fc1/11 (F11).
Table 1 summarizes the port security authorization results for this active database. The conditions listed refer to the conditions from #__.
Device Connection Request |
Authorization |
Condition |
Reason |
---|---|---|---|
P1, N2, F1 |
Permitted |
1 |
No conflict. |
P2, N2, F1 |
Permitted |
1 |
No conflict. |
P3, N2, F1 |
Denied |
2 |
F1 is bound to P1/P2. |
P1, N3, F1 |
Permitted |
6 |
Wildcard match for N3. |
P1, N1, F3 |
Permitted |
5 |
Wildcard match for F3. |
P1, N4, F5 |
Denied |
2 |
P1 is bound to F1. |
P5, N1, F5 |
Denied |
2 |
N1 is only allowed on F2. |
P3, N3, F4 |
Permitted |
1 |
No conflict. |
S1, F10 |
Permitted |
1 |
No conflict. |
S2, F11 |
Denied |
7 |
P10 is bound to F11. |
P4, N4, F5 (auto-learning on) |
Permitted |
3 |
No conflict. |
P4, N4, F5(auto-learning off) |
Denied |
4 |
No match. |
S3, F5 (auto-learning on) |
Permitted |
3 |
No conflict. |
S3, F5 (auto-learning off) |
Denied |
4 |
No match. |
P1, N1, F6 (auto-learning on) |
Denied |
2 |
P1 is bound to F1. |
P5, N5, F1 (auto-learning on) |
Denied |
7 |
Only P1 and P2 bound to F1. |
S3, F4 (auto-learning on) |
Denied |
7 |
P3 paired with F4. |
S1, F3 (auto-learning on) |
Permitted |
5 |
No conflict. |
P5, N3, F3 |
Permitted |
6 |
Wildcard ( * ) match for F3 and N3. |
P7, N3, F9 |
Permitted |
6 |
Wildcard ( * ) match for N3. |
About WWN Identification
If you decide to manually configure port security, be sure to adhere to the following guidelines:
- Identify switch ports by the interface or by the fWWN.
- Identify devices by the pWWN or by the nWWN.
- If an Nx port is allowed to log in to SAN switch port Fx, then that Nx port can only log in through the specified Fx port.
- If an Nx port’s nWWN is bound to an Fx port WWN, then all pWWNs in the Nx port are implicitly paired with the Fx port.
- TE port checking is done on each VSAN in the allowed VSAN list of the trunk port.
- All PortChannel xE ports must be configured with the same set of WWNs in the same PortChannel.
- E port security is implemented in the port VSAN of the E port. In this case the sWWN is used to secure authorization checks.
- Once activated, the config database can be modified without any effect on the active database.
- By saving the running configuration, you save the configuration database and activated entries in the active database. Learned entries in the active database are not saved.
Activation and Auto-learning Configuration Distribution
Activation and auto-learning configurations in distributed mode are remembered as actions to be performed when you commit the changes in the pending database.
Learned entries are temporary and do not have any role in determining if a login is authorized or not. As such, learned entries do not participate in distribution. When you disable learning and commit the changes in the pending database, the learned entries become static entries in the active database and are distributed to all switches in the fabric. After the commit, the active database on all switches are identical and learning can be disabled.
If the pending database contains more than one activation and auto-learning configuration when you commit the changes, then the activation and auto-learning changes are consolidated and the behavior may change (see Table 1).
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. |
You activate the port security database and enable auto-learning. |
configuration database = {A,B} active database = {A,B, C1, D*} |
configuration database = {A,B} active database = {null} pending database = {A,B + activation to be enabled} |
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} |
|
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. |
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} |
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 enabled +learning to be disabled} |
|
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 |
![]() Tip |
In this case, we recommend that you perform a commit at the end of each operation: after you activate port security and after you enable auto-learning. |
Database Interaction
Table 1 lists the differences and interaction between the active and configuration databases.
Active Database |
Configuration Database |
---|---|
Read-only. |
Read-write. |
Saving the configuration only saves the activated entries. Learned entries are not saved. |
Saving the configuration saves all the entries in the configuration database. |
Once activated, all devices that have already logged into the VSAN are also learned and added to the active database. |
Once activated, the configuration database can be modified without any effect on the active database. |
You can overwrite the active database with the configured database by activating the port security database. Forcing an activation may violate the entries already configured in the active database. |
You can overwrite the configuration database with the active database. |
Guidelines and Limitations
- Port security is only supported for Fibre Channel ports.
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 2 K.
![]() 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. |
Default Settings
Table 1 lists the default settings for all port security features in any switch.
Parameters |
Default |
||
---|---|---|---|
Auto-learn |
Enabled if port security is enabled. |
||
Port security |
Disabled |
||
Distribution |
Disabled.
|
Configuring Port Security
The steps to configure port security depend on which features you are using. Auto-learning works differently if you are using CFS distribution.
This section includes the following topics:
Configuring Port Security with Auto-Learning and CFS Distribution
To configure port security, using auto-learning and CFS distribution, follow these steps:
Procedure
Step 1 |
Enable port security. See the Enabling Port Security. |
Step 2 |
Enable CFS distribution. See the Enabling Distribution. |
Step 3 |
Activate port security on each VSAN. This turns on auto-learning by default. See the Activating Port Security. |
Step 4 |
Issue a CFS commit to copy this configuration to all switches in the fabric. See the Committing the Changes. At this point, all switches are activated, and auto-learning. |
Step 5 |
Wait until all switches and all hosts are automatically learned. |
Step 6 |
Disable auto-learn on each VSAN. See theDisabling Auto-learning. |
Step 7 |
Issue a CFS commit to copy this configuration to all switches in the fabric. See the Committing the Changes. At this point, the auto-learned entries from every switch are combined into a static active database that is distributed to all switches. |
Step 8 |
Copy the active database to the configure database on each VSAN. See the Copying the Port Security Database. |
Step 9 |
Issue a CFS commit to copy this configuration to all switches in the fabric. See the Committing the Changes. This ensures that the configure database is the same on all switches in the fabric. |
Step 10 |
Copy the running configuration to the startup configuration, using the fabric option. This saves the port security configure database to the startup configuration on all switches in the fabric. |
Configuring Port Security with Auto-Learning without CFS
To configure port security using auto-learning without CFS, follow these steps:
Procedure
Step 1 |
Enable port security. See the Enabling Port Security. |
Step 2 |
Activate port security on each VSAN. This turns on auto-learning by default. |
Step 3 |
Wait until all switches and all hosts are automatically learned. |
Step 4 |
Disable auto-learn on each VSAN. See the Disabling Auto-learning. |
Step 5 |
Copy the active database to the configure database on each VSAN. See the Copying the Port Security Database. |
Step 6 |
Copy the running configuration to the startup configuration This saves the port security configure database to the startup configuration. |
Step 7 |
Repeat #task_1001231__ through #task_1001231__ for all switches in the fabric. |
Configuring Port Security with Manual Database Configuration
To configure port security and manually configure the port security database, follow these steps:
Procedure
Step 1 |
Enable port security. See the Enabling Port Security. |
Step 2 |
Manually configure all port security entries into the configure database on each VSAN. See the Configuring Port Security with Manual Database Configuration. |
Step 3 |
Activate port security on each VSAN. This turns on auto-learning by default. See the Activating Port Security. |
Step 4 |
Disable auto-learn on each VSAN. See the Disabling Auto-learning. |
Step 5 |
Copy the running configuration to the startup configuration This saves the port security configure database to the startup configuration. |
Step 6 |
Repeat #task_1001264__ through #task_1001264__ for all switches in the fabric. |
Configuring Port Security Using the Configuration Wizard
The Port Security Configuration wizard provides step-by-step procedures for setting up the Port Security Policy for a selected VSAN. The Port Security Configuration wizard also supports the central management through CFS, making it possible to complete the entire configuration at one place.
The wizard automatically conducts few essential operations. For example, if you want central management, the wizard conducts operations to check CFS capability, enable CFS, and issue CFS commit at the proper stages.
To manage security at a particular port, you do not need to run through the wizard to configure the port security policy from the VSAN wide, but you can directly edit accesses on the port itself. This operation can be done through the Port Binding dialog box. If the port's belonging switch has not enabled port security yet, the dialog box enables security first. If the port security is enabled, the dialog box will edit the policy database based on user operations.
CFS should be enabled on all switches in the VSAN. A CFS master switch is selected to do all configurations. All changes will be distributed to the VSAN through the CFS commit command.
To configure port security, follow these steps:
Before you begin
The following are the prerequisites:
- Enable port security on the switch.
- Define port security policy either manually by editing bound devices or switches or ports or by using autolearning.
- Activate port security policy.
- Ensure that activated and configured databases are synchronized through copy.
- Copy the activated database to be the startup configuration.
Procedure
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 |
Before launching the Port Security Setup Wizard, DCNM-SAN checks the CFS capability of the switches in the VSAN. |
If VSAN context is not available, the wizard prompts to select VSAN as shown in Figure 1 ![]() This image aem://wemapp-author-prod1a.cisco.com/content/dam/en/us/td/i/200001-300000/240001-250000/242001-243000/242190.jpg is not available in preview/cisco.com |
||
Step 2 |
Select the VSAN from the list and click OK . Do the following in the Select Master Switch page: |
|
||
Step 3 |
Click Next to proceed. |
You see the Edit and Activate Configuration page.
|
||
Step 4 |
Click Insert to create port binding. |
Two types of port binding can be created using the Insert Port Security Devices dialog box:
|
||
Step 5 |
Select the type of port binding by clicking the radio buttons and enter the supporting values. |
|||
Step 6 |
Click OK. |
|||
Step 7 |
Click Close to exit the Insert Port Security window. |
|
||
Step 8 |
Click Finish to complete the Port Security Configuration for the selected switch. |
Enabling Port Security
By default, the port security feature is disabled in all switches in the Cisco MDS 9000 Family.
To enable port security, follow these steps:
Procedure
Step 1 |
Expand a VSAN, and then select Port Security in the Logical Domains pane. You see the port security configuration for that VSAN in the Information pane. |
Step 2 |
Click the CFS tab. |
Step 3 |
Enable CFS on all participating switches in the VSAN by clicking each entry in the Global column and selecting enable . |
Step 4 |
Click Apply Changes to enable CFS distribution for the port security feature. |
Step 5 |
Click the Control tab. You see the port security enable state for all switches in the selected VSAN. |
Step 6 |
Set the Command column to enable for each switch in the VSAN. |
Step 7 |
Click the CFS tab and set the Command column to commit on all participating switches in the VSAN. |
Step 8 |
Click Apply Changes to distribute the enabled port security to all switches in the VSAN. |
Activating Port Security
To activate port security, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. You see the port security configuration for that VSAN in the Information pane. |
||
Step 2 |
Click the Actions tab. |
||
Step 3 |
Click in the Action column under Activation, next to the switch or VSAN on which you want to activate port security. You see a drop-down menu with options. |
||
Step 4 |
Set the Action field you want for that switch. |
||
Step 5 |
Uncheck the AutoLearn check box for each switch in the VSAN to disable auto-learning. |
||
Step 6 |
Click the CFS tab and set the command column to commit on all participating switches in the VSAN. |
||
Step 7 |
Click Apply Changes in DCNM-SAN or Apply in Device Manager to save these changes.
|
Activating the Port Security Forcefully
If the port security activation request is rejected, you can force the activation.
![]() Note |
An activation using the force option can log out existing devices if they violate the active database. |
You can view missing or conflicting entries using the port-security database diff active vsan command in EXEC mode.
To forcefully activate the port security database, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. You see the port security configuration for that VSAN in the Information pane. |
Step 2 |
Click the Actions tab. |
Step 3 |
Click in the Action column under Activation, next to the switch or VSAN on which you want to activate port security and select the forceactivate option. |
Step 4 |
Set the Action field you want for that switch. |
Step 5 |
Click the CFS tab and set the command column to commit on all participating switches in the VSAN. |
Step 6 |
Click Apply Changes in DCNM-SAN or Apply in Device Manager to save these changes. |
Reactivating the Database
![]() Tip |
If auto-learning is enabled, and you cannot activate the database, you will not be allowed to proceedwithout the force option until you disable auto-learning.. |
To reactivate the port security database, follow these steps:
Procedure
Step 1 |
Disable auto-learning. |
||
Step 2 |
Copy the active database to the configured database.
|
||
Step 3 |
Make the required changes to the configuration database. |
||
Step 4 |
Activate the database. |
Copying an Active Database to the Config Database
To copy the active database to the config database, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. You see the port security configuration for that VSAN in the Information pane. |
Step 2 |
Click the Actions tab. You see the switches for that VSAN. |
Step 3 |
Check the CopyActive ToConfig check box next to the switch for which you want to copy the database. The active database is copied to the config database when the security setting is activated. |
Step 4 |
Uncheck the CopyActive ToConfig check box if you do not want the database copied when the security setting is activated. |
Step 5 |
Click the CFS tab and set the command column to commit on all participating switches in the VSAN. |
Step 6 |
Click Apply Changes to save these changes or click Undo Changes to discard any unsaved changes. |
Configuring Auto-learning
This section contains the following topics:
Enabling Auto-learning
To enable auto-learning, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. |
Step 2 |
Click the Actions tab. |
Step 3 |
Click in the Action column under Activation, next to the switch or VSAN on which you want to activate port security. You see a drop-down menu with the following options:
|
Step 4 |
Select one of the port security options for that switch. |
Step 5 |
Check the AutoLearn check box for each switch in the VSAN to enable auto-learning. |
Step 6 |
Click the Apply Changes icon to save these changes. |
Disabling Auto-learning
To disable auto-learning, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. You see the port security configuration for that VSAN in the Information pane. |
Step 2 |
Click the Actions tab. You see the switches for that VSAN. |
Step 3 |
Uncheck the AutoLearn check box next to the switch if you want to disable auto-learning. |
Step 4 |
Click the Apply Changes icon to save these changes. |
Configuring Port Security Manually
This section includes the following topics:
Task Flow for Configuring Port Security
Follow these steps to configure port security on any switch in the Cisco MDS 9000 Family:
Procedure
Step 1 |
Identify the WWN of the ports that need to be secured. |
Step 2 |
Secure the fWWN to an authorized nWWN or pWWN. |
Step 3 |
Activate the port security database. |
Step 4 |
Verify your configuration. |
Adding Authorized Port Pairs
After identifying the WWN pairs that need to be bound, add those pairs to the port security database.
![]() Tip |
Remote switch binding can be specified at the local switch. To specify the remote interfaces, you can use either the fWWN or sWWN-interface combination. |
To add authorized port pairs for port security, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. |
Step 2 |
Click the Config Database tab. |
Step 3 |
Click Create Row to add an authorized port pair. You see the Create Port Security dialog box. |
Step 4 |
Double-click the device from the available list for which you want to create the port security setting. |
Step 5 |
Double-click the port from the available list to which you want to bind the device. |
Step 6 |
Click Create to create the port security setting. |
Step 7 |
Click the Apply Changes icon to save these changes. |
Deleting Port Security Setting
To delete a port security setting from the configured database on a switch, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. |
Step 2 |
Click the Config Database tab. You see the configured port security settings for that VSAN. |
Step 3 |
Click the row you want to delete. |
Step 4 |
Click Delete Row. You see the confirmation dialog box. |
Step 5 |
Click Yes to delete the row, or click No to close the confirmation dialog box without deleting the row. |
Step 6 |
Click the Apply Changes icon to save these changes. |
Configuring Port Security Distribution
The port security feature uses the Cisco Fabric Services (CFS) infrastructure to enable efficient database management, provide a single point of configuration for the entire fabric in the VSAN, and enforce the port security policies throughout the fabric (see Chapter 35, “Configuring IPsec Network Security .’ ).
This section includes the following topics:
Enabling Distribution
For example, if you activate port security, follow up by disabling auto-learning, and commit the changes in the pending database, then the net result of your actions is the same as issuing a port-security activate vsan vsan-id no-auto-learn command.
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. |
![]() Tip |
In this case, we recommend that you perform a commit at the end of each operation: after you activate port security and after you enable auto learning. |
To enable distribution, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. You see the port security configuration for that VSAN in the Information pane. |
Step 2 |
Click the Control tab. You see the switches for that VSAN. |
Step 3 |
In the Command column, select enable or disable from the drop-down menu. |
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.
Committing the Changes
If you commit the changes made to the configurations, the configurations in the pending database are distributed to other switches. On a successful commit, the configuration change is applied throughout the fabric and the lock is released.
Discarding the Changes
If you discard (abort) the changes made to the pending database, the configuration remains unaffected and the lock is released.
Interacting with the Database
![]() Note |
You can overwrite the configuration database with the active database using the port-security database copy vsan command. The port-security database diff active vsa n command in EXEC mode lists the differences between the active database and the configuration database. |
This section includes the following topics:
Copying the Port Security Database
Use the port-security database copy vsan command to copy from the active to the configured database. If the active database is empty, this command is not accepted.
switch# port-security database copy vsan 1
Use the port-security database diff active vsan command to view the differences between the active database and the configuration database. This command can be used when resolving conflicts.
switch# port-security database diff active vsan 1
Use the port-security database diff config vsan command to obtain information on the differences between the configuration database and the active database.
switch# port-security database diff config vsan 1
![]() Tip |
We recommend that you copy the active database to the configuration database issue the port-security database copy vsan command after disabling auto-learning. This action ensures that the configuration database is in sync with the active database. If distribution is enabled, this command creates a temporary copy (and consequently a fabric lock) of the configuration database. If you lock the fabric, you need to commit the changes to the configuration databases in all the switches. |
copy the active database to the configuration database
To copy the active database to the configuration database, follow these steps:
Procedure
Step 1 |
Expand a Fabric , expand a VSAN, and then select Port Security in the Logical Domains pane. |
Step 2 |
Click the Actions tab. You see all the configuration databases. |
Step 3 |
Select the appropriate configuration database and check the Copy Active to Config check box. |
Step 4 |
Click the Apply Changes icon to save your changes. |
View differences between Active DB and Configuration DB
To view the differences between the active database and the configuration database, follow these steps:
Procedure
Step 1 |
Expand a Fabric , expand a VSAN, and then select Port Security in the Logical Domains pane. You see the Port Security information in the Information pane. |
Step 2 |
Click the Database Differences tab. You see all the configuration databases. |
Step 3 |
Select the appropriate configuration database. Select the Active or Config option to compare the differences between the selected database and the active or configuration database. |
Step 4 |
Click the Apply Changes icon to save your changes. |
Deleting the Port Security Database
![]() Tip |
If the distribution is enabled, the deletion creates a copy of the database. An explicit deletion port-security commit command is required to actually delete the database. |
Use the no port-security database vsan command in configuration mode to delete the configured database for a specified VSAN
switch(config)# no port-security database vsan 1
To delete a port security database, follow these steps:
Procedure
Step 1 |
Expand a Fabric , expand a VSAN , and then select Port Security in the Logical Domains pane. You see the Port Security information in the Information pane. |
Step 2 |
Click the Config Database tab. You see all the configuration databases. |
Step 3 |
Select the appropriate configuration database and click the Delete Row button. |
Step 4 |
Click Yes if you want to delete the configuration database. |
Cleaning the Port Security Database
Use the clear port-security statistics vsan command to clear all existing statistics from the port security database for a specified VSAN.
switch# clear port-security statistics vsan 1
Use the clear port-security database auto-learn interface command to clear any learned entries in the active database for a specified interface within a VSAN.
switch# clear port-security database auto-learn interface fc1/1 vsan 1
Use the clear port-security database auto-learn vsan command to clear any learned entries in the active database for the entire VSAN.
switch# clear port-security database auto-learn vsan 1
![]() Note |
The clear port-security database auto-learn and clear port-security statistics commands are only relevant to the local switch and do not acquire locks. Also, learned entries are only local to the switch and do not participate in distribution. |
Use the port-security clear vsan command to clear the pending session in the VSAN from any switch in the VSAN.
switch# clear
port-security session vsan 5
To clear all existing statistics from the port security database for a specified VSAN, follow these steps:
Procedure
Step 1 |
Expand a Fabric , expand a VSAN, and then select Port Security in the Logical Domains pane. You see the Port Security information in the Information pane. |
Step 2 |
Click the Statistics tab. You see all the configuration databases. |
Step 3 |
Select the appropriate configuration database and check the Clear option. |
Step 4 |
Click the Apply Changes icon to save your changes. |
Cleaning the Port Security Database
To clear any learned entries in the active database for a specified interface within a VSAN, follow these steps:
Procedure
Step 1 |
Expand a Fabric , expand a VSAN, and then select Port Security in the Logical Domains pane. You see the Port Security information in the Information pane. |
Step 2 |
Select the Actions tab. You see all the configuration databases. |
Step 3 |
Select the appropriate configuration database and check the AutoLearn option. |
Step 4 |
Click the Apply Changes icon to save your changes. |
What to do next
![]() Note |
You can clear the Statistics and the AutoLearn option only for switches that are local and do not acquire locks. Also, learned entries are only local to the switch and do not participate in distribution. |
Displaying Activated Port Security Settings
To display active port security settings, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. You see the port security configuration for that VSAN in the Information pane. |
Step 2 |
Click the Active Database tab. You see the active port security settings for that VSAN. |
Displaying Port Security Statistics
To display port security statistics, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. You see the port security configuration for that VSAN in the Information pane. |
Step 2 |
Click the Statistics tab. You see the port security statistics for that VSAN. |
Displaying Port Security Violations
Port violations are invalid login attempts (for example, login requests from unauthorized Fibre Channel devices). You can display a list of these attempts on a per-VSAN basis.
To display port security violations, follow these steps:
Procedure
Step 1 |
Expand a VSAN and select Port Security in the Logical Domains pane. You see the port security configuration for that VSAN in the Information pane. |
Step 2 |
Click the Violations tab. You see the port security violations for that VSAN. |
Field Descriptions for Port Security
The following are the field descriptions for port security.
Port Security Actions
Field |
Description |
---|---|
Activation |
|
Action |
|
Enabled |
The state of activation on this VSAN/VLAN. If true, then an activation has been attempted as the most recent operation on this VSAN/VLAN. If false, then an activation has not been attempted as the most recent operation on this VSAN/VLAN. |
Result |
Indicates the outcome of the most recent activation/deactivation. |
Last Change |
When the valid port bindings on this VSAN/VLAN were last activated. If the last activation took place prior to the last re-initialization of the agent, then this value will be N/A. |
CopyActiveToConfig |
If enabled, results in the active port binding database to be copied on to the configuration database on this VSAN/VLAN. Note that the learned entries are also copied. |
AutoLearn |
Helps to learn the valid port binding configuration of devices/ports logged into the local device on all its ports and populate the above active database with the same. This mechanism of learning the configuration of devices/ports logged into the local device over a period of time and populating the configuration is a convenience mechanism for users. If enabled on a particular VSAN, all subsequent logins (FLOGIs) on that VSAN will be populated in the enforced port binding database, provided it is not in conflict with existing enforced port bindings on that VSAN. When disabled, the mechanism of learning is stopped. The learned entries will however be in the active database. |
Clear AutoLearned |
|
Action |
|
Interface |
Specifies the interface(s) on which the port bind auto-learned entries need to be cleared. |
Port Security Config Database
Field |
Description |
---|---|
Interface or fWWN |
Represents the address of the port on the local device through which the device specified can FLOGI.
|
Type |
The mechanism to identify a switch port. |
WWN |
Represents the logging-in device address. |
Available Interface |
Displays the available interface. The interfaces available are:
|
Port Security Active Database
Field |
Description |
---|---|
Interface or fWWN |
The address of a port on the local device. |
Type |
The mechanism to identify a switch port.
|
WWN |
Represents the logging-in device address. |
IsLearnt |
Indicates if this entry is a learned entry or not. |
Port Security Database Differences
Field |
Description |
---|---|
CompareWith |
Specifies the database for the comparison.
|
VSANId |
The ID of the VSAN to compare against. |
Interface/fWWN |
The address of a port on the local device. |
Type |
The mechanism to identify a switch port.
|
WWN |
Represents the logging in device address. |
Reason |
Indicates the reason for the difference between the databases being compared, for this entry. |
Port Security Violations
Field |
Description |
---|---|
Interface |
The fWWN of the port on the local device where the login was denied. |
End Device |
The pWWN of the device that was denied FLOGI on one of the local device's ports. |
Or Switch |
The sWWN of the device (if the device happens to be a switch), that was denied entry on one of the local device's ports. |
Time |
When the login denial took place. |
Count |
The number of times this particular pWWN/nWWN or sWWN has been denied login on this particular local interface. |
Port Security Statistics
Field |
Description |
---|---|
AllowedLogins |
The number of FLOGI requests that have been allowed on this VSAN/VLAN. |
DeniedLogins |
The number of FLOGI requests that have been denied on this VSAN/VLAN. |
Clear |
When set to clear, it results in port bind statistic counters being cleared on this VSAN/VLAN. |