DCNM-SAN: No fabrics found

Hi,
I have the following problem concerning DCNM-SAN.
I recently upgraded to DCNM 5.2.2c.
We came from a lower DCNM version, where Fabric Manager was not already included in the DCNM package.
I've uninstalled Fabric Manager as it was recommended by an upgrade manual from Cisco.
After some time, it was possible to install DCNM 5.2.2c.
The DCNM-LAN is working, but the DCNM-SAN isn't.
Unfortunately, I'm unable to access our SAN fabrics.
Our environment exists of Cisco MDS switches and a one server where DCNM-LAN and DCNM-SAN are installed.
When we open the DCNM-SAN client and try to login, I can login but I get an "There are no fabrics available for <username>@Radius" error.
With some investigation, I found out that we needed to have the "network-admin" role in ACS 4.2.
We have already had that role configured, so that couldn't be the case.
I also checked if the DCNM-SAN service was running, and it is.
Can somebody please help me out as we are not able to access the fabrics.
With kind regards,
Bart Mars

http://www.cisco.com/en/US/customer/docs/switches/datacenter/sw/5_x/dcnm/release/notes/dcnm_5_2_relnotes.html#wp61633
Supported as of 5.2 per the release notes above. And both can coexist in the same VM.
This is the validation from the release note:
The Cisco DCNM server can run within a virtual machine, and requires one of the supported Windows or Linux operating systems listed in this section.
Specifics for the host OS can be found in the release notes.
Hope that helps,
Cary Cube'
CSE, CISCO

Similar Messages

DCNM v7.1 fabric already exist error message

Hi my friends:
Do you konw where storage san device in dcnm because when i try to add another this show me that the same device exist,but i can found in screen,
I attached the error message.
Thank,
Best regard.
Marco

Hi Marco,
DCNM will discover the entire SAN fabric from a single discovery job. By entering the IP address of an initial seed switch, DCNM finds and adds adjacent switches. It is likely that the .34 switch was found by one of the 2 previous discovery jobs. There are two places in DCNM to determine if the switch has already been discovered.
You can find a list of all devices managed by DCNM, including SAN devices, in the Web GUI under [Inventory > Switches]. Additionally, you can launch the DCNM-SAN java client to view the fabric as well as configure the devices. To launch the SAN client, open the DCNM Web GUI and find the 'DCNM-SAN' button in the upper right corner of the screen. The SAN client accepts the same user credentials as the Web GUI. Once logged into the SAN client, select the discovered fabric and 'open' it to view all of its devices.
-Eric

DCNM-SAN supporting FI

Using DCNM-SAN with UCS (2.1.2a); I created on all FC devices (MDS and N5k) a user "dcnmuser" with netadmin rights. I also created a snmp v3 user "dcnmuser" with UCSM. Then I did a fabric discovery with DCNM-SAN; I see the fabric, MDS, N5k and FI, however, the FI have a red arrow, which means not manageable.
Q. what could be wrong ? or is this really supported ?

Understood, thanks Robert
We only want to monitor UCS-FI with DCNM-SAN.
The release notes 6.1.2
http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/dcnm/release/notes/dcnm_6_1_relnotes.html
are quite misleading:
Introduction
Cisco Data Center Network Manager combines the management of Ethernet and storage networks into a single dashboard to help network and storage administrators manage and troubleshoot health and performance across the following product families that run Cisco NX-OS software:
•Cisco MDS 9500 Series Multilayer Directors and Cisco MDS 9200 and 9100 Series Multilayer Switches
•Cisco Nexus 1000V Series Switches and Cisco Nexus 1010 Virtual Services Appliance
•Cisco Nexus 2000 Series Fabric Extenders
•Cisco Nexus 3000, 4000, 5000, and 7000 Series Switches
•Cisco Catalyst 6500 Series Switches
•Cisco UCS 6100 and 6200 Series Fabric Interconnects
•Cisco FireWall Service Module (FWSM)
Cisco DCNM-SAN Release 6.1(1b) and later releases do not support Cisco Nexus 5000 Series switches and UCS devices running Cisco NX-OS Release 4.1(3) or an earlier release.
However, Table 9 Hardware Features Supported by Cisco DCNM Release 6.1
doesn't show UCS FI !

DCNM SAN 6.2 + Nexus 5500 not using interface mgmt

When trying to discover a newly setup fabric we have set the SVI of one of the Nexus 5500 switches as seed device in DCNM SAN server. Problem do seem to be the same in DCNM 6.2 as in DCNM 5.x, one can not use a SVI.... After adding the seed switch with the IP adress of the SVI it appears in the Admin->Data sources->Fabric with the ip address of the mgmt interface. Thing is that this ip address can not be reached from the DCNM SAN server since we have only used a cross over ethernet cable for peer-keepalive over the mgmt interfaces.
Is there a way in DCNM SAN 6.2 to force SAN management over a SVI instead of the mgmt interface?

Here is the solution:
in the menubar on the top, in the lower one go to Admin > Server Properties
scroll to the middle of the list, locate “fabric.managementIpOverwrite” and set it to false
restart the DCNM Servers

Installing DCNM-SAN as a VSB in Nexus 1010

Hi everyone,
I'm trying to install DCNM-SAN as a VSB in Nexus 1010, as I've read on the release notes that since 5.2.x release the distribution is done via a single image and there's an image available right now for 5.2(2)...
But, although I've tried numerous times (together with reading a lot through the two available documents - Installation and licensing guide and Fundamentals), every time I create a new vsb with these images, it becomes a DCNM-LAN install.
I have yet to have any prior experience with DCNM, so I might be missing something.
Any ideas? What am I missing? Am I trying to do something that is not supported? Or, am I just missing a critical point there?
NOTE: This is currently a lab topology, but I have a customer that's very keen on using DCNM-SAN with their MDS switches. And I feel that having this on a the 1010 as a vsb is the best way to do it, if it can be done, with regards to having network staff not deal with servers etc.
Thanks,
Emre

Andrew,
We are a little frustrated with the VSB version of DCNM-SAN, it does not appear possible to manage fabric without advanced licensing for the switches, in the licensing guides for DCNM it lists essentials capability that should include port, switch, and fabric-level configuration. On the windows version we can manage the fabric unlicensed as long as we do it from the server direcly or in previous versions if we are running stand alone. These options do not appear to exist for the VSB version. Is there any plan to include any essentials capability in the VSB/OVF versions of the DCNM-SAN. If this is not planned, the documentation should be changed to state that essentials functions are only available in the Windows version.

DCNM-SAN & VMware

Hello,
In the release notes for DCNM 5.2, it states that DCNM-LAN can be installed as a virtual machine. However, no where does it state that DCNM-SAN can be installed as a virtual machine. So my question is can DCNM-SAN be run as a VM? It would make sense that this would be allowed since LAN and SAN can now exist on the same box with 5.2 but it wouldn't make sense if SAN was not supported as a VM when LAN is. Thanks.

http://www.cisco.com/en/US/customer/docs/switches/datacenter/sw/5_x/dcnm/release/notes/dcnm_5_2_relnotes.html#wp61633
Supported as of 5.2 per the release notes above. And both can coexist in the same VM.
This is the validation from the release note:
The Cisco DCNM server can run within a virtual machine, and requires one of the supported Windows or Linux operating systems listed in this section.
Specifics for the host OS can be found in the release notes.
Hope that helps,
Cary Cube'
CSE, CISCO

Difference between Cisco DCNM and CISCO Fabric Manager

Hello Everyone,
I am new to Cisco SAN and just would like to know the differences between cisco DCNM and Cisco Fabric manager and which one is latest as of now.
regards
VINAY

Hi Viany,
Fabric Manager was renamed DCNM starting at 5.2.
Fabric Manager only monitors SAN Fabrics, while DCNM 5.2 and above can monitor both SAN Fabrics and Ethernet LANs.
Regards,
David

DCNM SAN Client - SNMP Timeout

Hello Everyone,
right now iam struggling with the configuration of a DCNM SAN Client.
The Installation and licensing (with some trouble) has been finished few days ago.The DCNM LAN Client is working well and there are no problems with connectivity or timeouts. SSH and SNMPv3 are working fine for both Clients (SAN&LAN).
Discovering Fabrics for the DCNM SAN Client is working very well to. But when I start the DCNM SAN Client and open a session to a fabric it looks like this:
If I try to "edit local full zone database" it looks like this:
Tried to troubleshoot this behaviour but at the moment I am not able to figure out the problem.
Maybe someone in this community does?
Best Regards,
Sascha

This can be closed.
I got all answers... For the benefit of others who are searching answers for the same question:
1) I just downloaded the dcnm client for LAN ... is there a seperate client for SAN ? I dont see any download links for SAN... --- Yes .. DCNM SAN has a seperate client. After installation, you can open the DCNM page on http, and you would find the download links on top right corner for DCNM-LAN, SAN and device manager.
2) Is it possible to add brocade switches to DCNM-SAN? Does it require additional licenses? - I dont think this is possible
3) Can we use the fabric manager license "N5000FMS1k9" for DCNM SAN, or do we need "DCNM-SAN-N5K-K9" license for the nexus 5000? - Yes.. Use the same license and generate the PAK file. FMS licenses do work in DCNM-SAN..
Good luck

DCNM-SAN: SAN Health Advisor

Hi there
Could someone please provide a link to download this tool?
We are trying to install the SAN Health Advisor tool, but the instructions do not state where to launch the installer.
The instructions we are following are here:
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/sw/5_2/configuration/guides/fund/DCNM-SAN-LAN_5_2/perfmon.html#wp1302248
Refer to the last section called "Installing the SAN Health Advisor Tool".
Thanks in advance.
John

John,
The SAN Health Advisor tool was integrated into DCNM-SAN in 5.2(1). You can get the same reports and information from DCNM-SAN. Seems that the section in your linked document was not updated. I have contacted the documentation team to update it accordingly.
-Seth

DCNM-SAN as Nexus 1010 VSB

Does anybody know if (and when) DCNM-SAN will be available as a Nexus 1010 VSB, as it is with DCNM-LAN now?
PS: Here is my previous question on how (as I wrongly assumed it was possible, looking at the documentation), which was answered by Padma (a generous and kind Cisco employee).
Thanks,
Emre

Hi Andrew,
Great news, thanks... Looking forward for the release

Nexus 5548 - DCNM - SAN Connectivity

I'm having an issue seeing the switch and managing VSAN's and zoning from within DCNM Fabric Manager. Device Manager and Fabric Manger discover the switches, however, Fabric Manager won't let me configure anything. When I try to edit the local zone database of the active VSAN I get the error message, "SNMP: No Switches are available". The switch in the picture pane has a red line across the switch too.... What am I missing here? Is there configuration inside the 5548 to allow me to manage?
FC ports are setup and active as FC devices show up in Flogi just fine. I'd rather not manage this via CLI!

I am having this issue two in one of my 3 DCNM environments all of a sudden. Everything is the same DCNM version 6.2(3) and the switches are running system software on all switches are 6.2(1) . The only thing that I have done was connect some Cisco Blade NPV switches.

How-to use Cisco DCNM for SAN to manage storage fabric

I recently purchased DCNM for SAN (and LAN), have installed and licensed it. The software is up and running, and I have installed the necessary features & licenses to each of my Nexus 5596UP devices. Unfortunately, I'm not able to make any changes to the fabric from the DCNM SAN client. Am I missing some steps here? Do I need to have fiber connections in place from end points, and the SAN, in order to see/manage the fabric?
Thanks in advance!

Did you do a fabric discovery ? have you setup proper accounts on the N5k ?
see
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/5_2/configuration/guides/fund/DCNM-SAN-LAN_5_2/DCNM_Fundamentals/fmaaa.html

Multiple Fabrics - how many?

Hi,
We are configuring our MDS switches for new storage and there are a couple of options. I am not sure which is the best way to go.
We have 6 x 9124's. Our new storage has plenty of ports. Each of the 6 x 9124's will be connected to 2 ports on the storage (12 connections in total). I am going to treat the 6 x 9124s as pairs - so really it will be 3 pairs, and each pair is essentially a fabric A and B.
So the idea would be that when connecting a host to our SAN, we will pick one of the pairs and connect the host to both switches in that pair and zone it to use the storage ports connected to that same switch. This way, traffic will never actually need to "cross" between switches (and in fact it can't as there are no ISLs) - it will always be from the host to the storage all on the same switch. Each of the pairs of switches is acting as a fabric A and B.
In reality we will have 6 fabrics (as each switch will be a fabric). Connecting a new host to our storage will require configuration on two switches (fabrics), depending on which of the 3 pairs we choose to connect that host to. So really it will be 3 seperate "fabric A and B" setups, one for each pair.
This all sounds reasonable to me and should work quite well.
The only thing I am unsure about is whether there is any benefit in connecting ISLs between each of the "fabric A" switches and each of the "fabric B" switches - which would actually mean we really did have 2 fabrics rather than 6.
I am looking to understand the pros and cons of doing this. We have plenty of ports so the ports lost to the ISLs are not an issue. These ISLs would never be used for "storage traffic" to actually flow between switches as we would still zone it so that hosts always talked to the storage port(s) on the same switch. The only reason to create the ISLs would be to consolidate 6 fabrics down to 2 which may (?) make it easier to manage.
Are there real advantages to connecting the switches to consolidate down to 2 fabrics? I'm thinking that potentially it will be "nicer" to connect to DCNM-SAN and only see 2 fabrics rather than 6. I'm also thinking that the "maps" that DCNM produces will be easier to comprehend when there are only 2 - rather than having to look at 6 different maps to get a good picture of what we have. We will only be using the free DCNM-SAN (Essentials I think it is called).
Hopefully my question makes sense. I'm really looking to understand whether it is better to keep 6 seperate fabrics or whether it might make more sense to use ISLs to consolidate down to 2. Whether we keep 6 or go with 2, the concept would remain the same (each host connecting to a single pair of A/B switches and zones to the "local" storage ports) - so both solutions keep all storage traffic within the same switch. The ISLs would effectively only act as "management" connectors such that it could all be seen together within DCNM-SAN. Is there a disadvantage to connecting them together?
How would you do it?
Cheers,
David

Although I am not a SAN guy I would connect them together from the start. If the need ever arises to use a target on a different switch you would not face a SAN merge. Furthermore the zoning proces will be simpler you simply need to zone on FABRIC A and B and don't need to determine is the fabric A1 A2 or A3 to which the host is connected.

DCNM Performance issues ( postgres ? )

Hello, we are evaluating DCNM-SAN to get an idea of our SAN Switches performances, ( mostly 9513).
Environment :
Physical server ( not under VMW), with 2 x Intel Xeon 5110 processor @1.6 Ghz
12 GB RAM
Local disk.
Windows Server 2008R2 64bit.
We are using a DCNM demo license and discovered 24 MDS ( 20 licensed by the demo lic, 2 already fully licensed and 2 not licensed).
In the same SAN ( 6 fabrics) we do have also 36 Nexus switches connected to the MDS for the FCoE connections to/from the servers; those Nexus are not licensed so we do not collect performances for them.
For all the licensed MDS ( 22) we are collecting performances.
We started with DCNM 6.1.2, and everything was running smooth, then 5 days ago we decided to upgrade to 6.2.1.
From the very first moment after the upgrade, we have noticed an increased load in the CPU, that normally was about 6 to 10 %; now, after 5 days the CPU load is above 80% most of the times, and when opening a page ( i.e. dashboard, performance or inventory section) it takes about 2 minutes to have the page completed with 100% of cpu load, while before the upgrade it took about 5 secs.
I also noticed that when cpu is 100%, it is due to 4-5 "postgres.exe *32" processes chocking it.
I took a peek at the troubleshooting section of the docs, and the only reason for a postgres slowlyness could be the DB > 3 GB, but our is only 185 MB !!
I really don't get it, tryied even a server reboot but with no luck....to my understanding, collecting performances for 24 MDS with this server HW should be ok, not to mention that until we performed the upgrade, everything seemed to run smoothly..
Any help, please ? We are willing to evaluate the acquisition of such licenses, but we're start to having some doubt....
Tnx in advance
Andrea

Hi,
you should analyze the db after you have loaded the tables.
Do you use sequences to generate PKs? Do you have a lot of indexex and/or triggers on the tables?
If yes:
make sure your sequence caches (alter sequence s cache 10000)
Drop all unneeded indexes while loading and disable trigger if possible.
How big is your Redo Log Buffer? When loading a large amount of data it may be an option to enlarge this buffer.
Do you have more then one DBWR Process? Writing parallel can speed up things when a checkpoint is needed.
Is it possible using a direct load? Or do you already direct load?
Dim

SAN Switch Cisco -16Port

Hi,
Any suggestions for SAN Switch 16 Port ( All Active) from MDS series.
Thanks in advance!!

DCNM-SAN-M91-K9 - very nice to have if you want to track switch utilization, manage multiple fabrics at the same time. Not a must have ..but a nice to have.
M9148PL8-8G-SFP - i believe you must purchase this to activate an extra 8 ports to give you a total of 16 ports.
M9100ENT1K9 - if you have requirements for advances features like IVR then you would need this. If you just need to create zones, VSANs ..you don't need that license.
@dynamoxxx

DCNM-SAN: No fabrics found

Similar Messages

Maybe you are looking for