Committing Changes

Detailed Steps

You can commit changes for a specified feature by setting CFS > Config Action to commit for that feature.

To commit changes for CFS-enabled features, follow these steps:

  1. Choose the feature you want to enable CFS for. For example, choose Switch > Clock > NTP.

    2. The Information pane shows that feature with a CFS tab.

  2. Click the CFS tab to display the CFS state for each switch in the fabric for that feature.
  3. In the Feature tab, click the NTP General tab and change any configuration. Click the Apply Changes icon to apply the configuration to the local switch. The change remains at the pending database at the local switch until further CFS commit is applied.
  4. Click Pending Differences to check the configuration of this feature on this switch as compared to other switches in the fabric or VSAN that have CFS enabled for this feature.
  5. Click the CFS tab, right-click the value in the Config Action column of the master switch that is selected and select an option from the drop-down menu. (commit, clear lock, abort). For example, right-click the value in the Config Action column and select commit to commit the CFS pending changes for that feature and distribute the changes through CFS.

DCNM-SAN 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:

  1. Choose the feature you want to enable CFS for in Device Manager. For example, choose Admin > NTP.
  2. In the Feature tab, click the NTP General tab and change any configuration. Click the Apply Changes icon to apply the configuration to the local switch. The change remains at the pending database at the local switch until further CFS commit is applied.
  3. Choose Admin > CFS (Cisco Fabric Services).
  4. In the CFS table, click Pending Differences to check the configuration of this feature on this switch as compared to other switches in the fabric or VSAN that have CFS enabled for this feature.
  5. For each applicable feature, set the Command column to commit to commit the configuration changes for that feature and distribute the changes through CFS, or set it to abort to discard the changes for that feature and release the fabric lock for CFS for that feature.

    6. Device Manager retrieves the status of the CFS change and updates the Last Command and Result columns.

    Caution    

    If you do not commit the changes, they are not saved to the running configuration.


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