No Fabric Manage license available in DCNM

[Richard Foote]

Hi All.

I have DCNM-SAN 7.1(1) and Java 1.70.0_72. installed on a server running Windows 2012 R2.

I have four SAN fabrics discovered by DCNM and manage them one at a time. Often when I try to switch from managing one fabric to another, either by exiting DCNM and restarting the application or using the "Open" button/menu option and choosing a different fabric, I get the following error in a dialog box:

"No Fabric Manager license available for Fabric_XXXXX (where XXXX is the fabric name).

Multiple connected users require a fabric license.

Use Web Client to close all other connected users and try again."

This is a major roadblock to getting work done. Often it is necessary to wait 1-4 hours or longer - sometimes overnight - for the condition to clear itself, during which time none of the fabrics can be managed via DCNM. So I have the following questions:

1) Is the method referred to in the above error message a valid way to resolve the condition? If so, how does one access the Web Client for DCNM version 7.x? I have checked the manual but can find no reference to the web client. Actually, I have heard this web client functionality no longer exists in DCNM version 7. Can anyone confirm this either way?

2) Is there another way that is perhaps more reliable and faster to clear this error condition?

3) Is there a better or recommended way to switch between fabrics? When switching fabrics, I usually exit the application and wait 20 minutes before starting the DCNM application again and choosing a second fabric to work with. This is often enough of a delay but sometimes it is not long enough and I have to wait several hours.

I would appreciate user community experiences or official Cisco advice on this problem, as it really slows down the work I can do each day.

Thanks.

Richard

[cwiley2566]

I am having this exact same problem too.

[meelos001]

I am having the same issue as the OP. Thank you Jim for the workaround, though I do still seem to get sporadic results when even following your steps. Sometimes it works, sometimes it still takes time, etc. 

Does anyone know what the status is of this issue? I found what I believe to be the bug report, but it says it was fixed back in April. I am still experiencing this issue. It appears that all of your posts in this thread were before April, so I'm curious....is this still an issue for the OP, or anyone else that was having this issue?

https://tools.cisco.com/bugsearch/bug/CSCut35929/?referring_site=bugquickviewclick

[jihicks]

The fix for CSCut35929 is in 7.1(2) available on Cisco Online.

Best  regards,

Jim

[meelos001]

Aha, published only 11 days ago. Perfect. Thanks again!

[jihicks]

Hi Richard,

To gain access to the Web Client, open a browser and put in the IP address of the DCNM server.

The userid/password is the same as you use to log into the DCNM-SAN Client.

Now go to Admin >> Clients and log off all clients except the one you are using on the Web Client ( DCNM won't let you end this one ).  You mark the box next to the connection and then click on the red "X" to force the user off.

Finally Logout of the Web Client using the "admin" pull down ( notice the small "a" ).

Now you can go back and open a different fabric.

I verified number 1) in the lab, this is a bug and Cisco will be working to resolve it.

I have been unable to find a shorter workaround, but this one at least works.

Best regards,

Jim

[Richard Foote]

Hi Jim. Thanks for your response.

I have used the web client in earlier versions of DCNM where the web client functionality existed. Can you confirm for me if it still exists in version 7.1(1)?

I have tried out the method you describe to browse to the web client and all I get is an HTTP 404 error - Page Not Found. I've tried both HTTP and HTTPS - same result. So at present I cannot access the web client and am still locked out temporarily when I change fabrics. Is there something else perhaps that I need to set or enable in DCNM server to open up the web client functionality?

Looking forward to your response.

Richard

[jihicks]

Hi Richard,

Yes it is still present:

I verified the workaround several times before suggesting it.   When you install DCNM, the installer tries to find an open port.  Got to the server, typical windows location "C:\Program Files\Cisco Systems\dcm\dcnm\config" and check to see what port is here " DCNM_SAN_WEB_PORT=80".  Port 80 is the standard HTTP port.  If this is different try that. If not, maybe the connection is being blocked by a firewall or Windows Firewall. 

Best regards,

Jim