Send documentation comments to mdsfeedback-doc@cisco.com
12-9
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-17256-03, Cisco MDS NX-OS Release 4.x
Chapter 12 Initial Configuration
NTP Configuration
Note A warning displays if you do not enable CFS for all switches in the fabric for this feature.
Step 6 Check the Master check box for the switch that you want to act as the merge master for this feature.
Step 7 Click the switch value in the Config Action column. A drop-down menu appears.
Step 8 Select Commit.
Step 9 Click the Servers tab in the Information pane. You see the configuration for this feature based on the
master switch.
Step 10 Modify the Master configuration as needed. For example, right-click the value in the Master column and
select Create Row to create a server for NTP.
a. Set the ID, and the Name or IP Address for the NTP server.
b. Choose a Mode radio button and, optionally, check the Preferred check box.
c. Click Create to add the server.
Fabric Manager sends the request to the master switch. Click the CFS tab and check the Last Results
column for the new entry. It has a pending status.
Step 11 From the CFS tab, set the Config Action column to commit to distribute the feature change through the
fabric. Fabric Manager only changes the status to running when commit, clear, or abort is selected and
applied.
Note Fabric Manager will not change the status to pending if enable is selected, because the pending
status does not apply until the first actual change is made.
Step 12 Click the Apply Changes icon to commit the configuration changes for that feature and distribute the
changes through CFS, or click Undo Changes to discard the changes for that feature.
Committing NTP Configuration Changes
When you commit the NTP configuration changes, the effective database is overwritten by the
configuration changes in the pending database and all the switches in the fabric receive the same
configuration. When you commit the NTP configuration changes without implementing the session
feature, the NTP configurations are distributed to all the switches in the fabric.
Discarding NTP Configuration Changes
After making the configuration changes, you can choose to discard the changes or to commit them. In
either case, the lock is released.
Releasing Fabric Session Lock
If you have performed an NTP fabric task and have forgotten to release the lock by either committing or
discarding the changes, an administrator can release the lock from any switch in the fabric. If the
administrator performs this task, your changes to the pending database are discarded and the fabric lock
is released.
To Next Page
Loading...
Need help?
General
