> # CFS Example Using DCNM for SAN

> This procedure is an example of what you see when you use DCNM-SAN to configure a feature that uses CFS.

> ## Detailed Steps

> 1. Select the CFS-capable feature you want to configure. For example, 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.

> 2. Click the CFS tab.

> You see the CFS configuration and status for each switch.

> 3. From the Feature Admin drop-down list, select enable for each switch.
> 4. Repeat step 3 for all switches in the fabric.

> Note A warning is displayed if you do not enable CFS for all switches in the fabric for this feature.

> 5. Check the Master check box for the switch to act as the merge master for this feature.

> Note If you click any other tab in the information pane and then click the CFS tab, the Master check box will no longer be checked. DCNM-SAN does not cache the CFS Master information.

> 6. From the Config Action drop-down list, select commit Changes for each switch that you enabled for CFS.
> 7. Click the Servers tab in the Information pane.

> You see the configuration for this feature based on the master switch.

> 8. Modify the feature configuration. For example, right-click the name in the Master column and select Create Row to create a server for NTP.
> 1. Set the ID and the Name or IP Address for the NTP server.
> 2. Set the Mode radio button and optionally check the Preferred check box.
> 3. Click Create to add the server.
> 9. Click the Delete Row icon to delete a row.

> If you make any changes, the status automatically changes to Pending.

> 10. Click the Commit CFS Pending Changes icon to save the changes.
> 11. The status changes to Running.
> 12. From the Config Action drop-down list, select abortChanges for each switch that you enabled for CFS .

> Note DCNM-SAN does not change the status to pending if enable is selected, because the pending status does not apply until the first actual change is made.

> 13. Click the Apply Changes icon to commit the configuration changes for that feature and distribute the changes through CFS.

> Note When using CFS with features such as DPVM and device alias, you must select commit at the end of each configuration. If the session is locked, you must exit the feature by selecting abort.

> To configure the master or seed switch for distribution for each feature, follow these steps:

> 1. Choose the feature that needs a merge master for CFS. For example, expand expand Events and select CallHome from the Physical Attributes pane.

> The Information pane shows that feature including a CFS tab.

> 2. Click the CFS tab to display the CFS state for each switch in the fabric for that feature.
> 3. Check the Master column check box for the switch to act as the merge master for this feature.
> 4. Click the Apply Changes icon to select this switch as master for future CFS distributions.
> .

> Copyright 2010-2013, Cisco Systems, Inc. All rights reserved.