HP Cisco MDS 9216A Cisco MDS 9000 Family Fabric Manager Configuration Guide, R - Page 289

Chapter 13 Using the CFS Infrastructure Locking the Fabric Send documentation comments to [email protected] Locking the Fabric When you configure (first time configuration) a Cisco SAN-OS feature (or application) that uses the CFS infrastructure, that feature starts a CFS session and locks the fabric. When a fabric is locked, the Cisco SAN-OS software does not allow any configuration changes from a switch, other than the switch holding the lock, to this Cisco SAN-OS feature and issues a message to inform the user about the locked status. The configuration changes are held in a pending database by that application. If you start a CFS session that requires a fabric lock but forget to end the session, an administrator can clear the session. If you lock a fabric at any time, your user name is remembered across restarts and switchovers. If another user (on the same machine) tries to perform configuration tasks, that user's attempts are rejected. Committing Changes A commit operation saves the pending database for all application peers and releases the lock for all switches. In general, the commit function does not start a session-only a lock function starts a session. However, an empty commit is allowed if configuration changes are not previously made. In this case, a commit operation results in a session that acquires locks and distributes the current database. When you commit configuration changes to a feature using the CFS infrastructure, you receive a notification about one of the following responses: • One or more external switches report a successful status-The application applies the changes locally and releases the fabric lock. • None of the external switches report a successful state-The application considers this state a failure and does not apply the changes to any switch in the fabric. The fabric lock is not released. You can commit changes for a specified feature by setting CFS > Config Action to commit for that feature. To commit changes using Fabric Manager for CFS-enabled features, follow these steps: Step 1 Step 2 Step 3 Step 4 Choose the feature you want to enable CFS for. For example, expand Switches expand Events then select CallHome from the Physical Attributes pane. The Information pane shows that feature, with a CFS tab. Click the CFS tab to display the CFS state for each switch in the fabric for that feature. Right-click the value in the Config Action column for any switch and select an option from the drop-down menu (Copy, Paste, Export to File, Print Table, Detach Table). Click the Apply Changes icon to commit the configuration changes for that feature and distribute the changes through CFS. Fabric Manager retrieves the status of the CFS change and updates the Last Command and Last Result columns for the feature or VSAN. To commit changes using Device Manager for CFS-enabled features, follow these steps: Step 1 Choose Admin > CFS (Cisco Fabric Services). OL-16184-01, Cisco MDS SAN-OS Release 3.x Cisco MDS 9000 Family CLI Configuration Guide 13-7