Modify MASTER switch for device-alias database

[DrPepper1234]

In my fabric there is one MDS9513, and some 9124e (modules in Blade Enclosure).

I don't know the reason, but DCNM is using one of those 9124e as "master" for device-alias database.

I want to use the 9513 as master... how do I change the master switch for that?

I tried to tick the box "master" in the row that corresponds to MDS9513 and then commit changes, but this didn't change the master switch.

[Walter Dey]

I don't see that you have selected the feature, that CFS is used for ?

Note When using CFS with features like 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 using Fabric Manager, follow these steps:

---

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

The Information pane shows that feature including a CFS tab.

Step 2 Click the CFS tab to display the CFS state for each switch in the fabric for that feature.

Step 3 Check the Master column check box for the switch to act as the merge master for this feature.

Step 4 Click the Apply Changes icon to select this switch as master for future CFS distributions.

[DrPepper1234]

Dear Walter,

I already found that procedure on Cisco Documentation, but:

1) It's for Fabric Manager. Here I'm using DCNM, it's slightly different.

2) As I wrote in my first post (check also attached picture) this procedure does not work.

I check the box "master" for the switch that I want to act as the master; then I click on "Apply Changes". When I refresh the view, the master switch is still the old one.

I tried also to look for a procedure to modify the master switch via CLI, but I didn't manage to find anything.

[dakester · Accepted solution]

Hi Doc,

I experienced the same behavior a few years ago and here is what I learned.

The CFS merge master is:

1. the lowest swwn in the fabric
2. not configurable
3. only used for merges (ISL trunk for the VSAN coming up),
4. not used for commits.

The "Master" column in DCNM

1. means, "use this switch to commit the configuration".
2. is not an ideal name
3. and is not sticky, so it will revert back to the lowest swwn.

Your DCNM is not broken and is working as designed.

There is not yet a strong business case to change this behavior.

Regards,

Davd

[DrPepper1234]

Hi dakester

Although I don't like the answer, it seems that you're right.

"Master" switch is the one with lowest WWN, and it's not configurable.

Thanks