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

Similar Messages

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

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 !

LMS 3.2 DFM-all devices QUESTIONED-SNMP Timeout

I imported 26 devices to DFM. All devices became QUESTIONED, error is SNMP timeout. Here are the troubleshooting steps that I tried:
1. rediscovered devices
2. deleted and rediscovered devices
3. increase snmp timeout settings
4.re-entered snmp strings in device credentials
But I still get the same result.I noticed that devices become questioned so fast.Any advise on this?

Hi,
What version of SNMP you are using on these 26 devices ?Try to do the following:
- Go to Device Center
- Select one device for test
- click on "check device credentials", select SNMP according to the version you are using.
- See the results.
May be you get more technical and detailed information about the SNMP timeout error. I have already experienced some problems using SNMP v3. The problem was resolved when I configured the SNMP v2c instead of v3.
Also, I suggest you to try do "SNMP walk" test in the Device Center. If you get some results reading, for example, the value of "sysObjectId", just verify the Credentials Settings in DCR. You can edit the Credentials trhough the Device Center -> Edit device credentials.
Regards,
Wando N. Rocha

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: 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 & 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

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

LMS 4.0 Fault discovery snmp timeout

Hi all,
I am running LMS 4.0 on windows 2008 SP2 64-bit.
I have the problem that all devices from dcr stay in the questioned State with error state snmp timeout.
I have done a credential verification and snmpwalk to the devices and this works correctly.
regards
Joerg

Joerg,
What kind of devices are they that are being questioned?
Make sure Fault Management in 4.0 supports the devices.
Rob

WLSE Configuration archive download SNMP timeout

HI, I´m new to WLSE. My AP´s are already discovered and managed, but when I try to download the configuration archive from them, the Job Always fail with a SNMP timeout error message. This problem occur in the upgrade firmware job too.
Whe I go to reports, device center, I can see the AP configuration, but in the configuration>archives>view archive I have nothing.
I appreciate your help

You can configure the timeout value by selecting Firmware > Advanced Parameters. From this option you can change the "Per device job operation timeout value" to a higher value

Error DCNM WEB Client EventType 30: # 1095

Hi,
I am entering the DCNM Web Client 6.2, in the menu bar, Admin> Collections throws me the following error: EventType 30: # 1095
Someone you should know?

Hello,
Base on the HTTP error that I see HTTP-502, the error come from your proxy/firewall configuration . You are using Microsoft ISA server and it looks you need to change it sonfiguration to allows SSL with the port you have chosen (1024).
Also be sure when you have done that you have configure correctly the client and added the client certificate to your application to allow a successful SSL handshake.
Regards
Tugdual Grall

JCO Client idel timeout

Hi,
Do anyone know how to set the jco.client.idle_timeout value for a ESS WebDynpro application.
Thanks
Kiran

Hi Gena,
so, it's now clear, the jco client simply uses the dialog processes and not something smarter/more flexible
Well, that's a feature of the underlying RFC protocol: All RFC calls are executed in dialog work processes, thus also the runtime limitations for dialog processes apply.
My question is, ho to entice the jco client call to run without runtime timeout and take as long time as necessary. If the only possibility is, to use the tRFC, does anybody have an example for tRFC usage from JCo Client?
The JCo client cannot do anything about it, it's a profile parameter in SAP, i.e. rdisp/max_wprun_time. But as this parameter applies to all dialog processes (so dialog users and RFC calls), so it shouldn't be changed to make a single RFC application work. Anyhow, tRFC won't help you in this case, because all RFC calls are processed in a dialog process no matter of the type of RFC.
Once again, we want to run the JCo client calls unlimited time (as long as needed) without the annoying dialog process timeout.
Impossible without making any changes in SAP. In theory one could modify the RFC function so that it resets the "runtime counter" and thus having the capability to run longer than rdisp/max_wprun_time. I'd recommend though not to do that, especially since a very long running RFC seems rather questionable. Long running tasks should be processed in background.
Cheers, harald

ABAP Client Proxy Timeout

Dear all,
A ABAP Client proxy has been generated to connect non-SAP web service. It runs successfully except it may time out when the web service method is running too long (over 1 minute).
We know timeout/keepalive value can be set at the ICM timeout parameter by using Tcode RZ11. However, can we set it at ABAP code? It is more convenient to override server settings.
Thanks!
Regards,
Thomas

Hi,
do changes as below
In SXMB_ADM
go to Configure Integration server
in change specific identifiers Set Runtime parameter: HTTP_TIMEOUT and then restart XI server, changes will be updated.
Regards,
Sukarna.

How to make VPN client auto timeout when it still idle?

How to make VPN client auto disconnect when it still idle?
Hi,I found some user still connected the VPN evenif they dose not use the VPN resouse.
I try to set a "idle timeout" for the VPN configuration.
We use PIX515 8.0.3 and CISCO ACS 4.2 for the VPN's connection and authentication,and the user use cisco vpn client for the connection.
I have tried many methods,but all failured.
First,I configed "vpn-idel-timeout 5" on PIX.It can not worked.
so,I add Radius(CISCO VPN 3000/ASA/PIX 7.0+) attribute "[026/3076/050] Authenticated-User-Idle-Timeout" on CISCO ACS,It still not worked.
And I also add IETF RADIUS Attributes "[028] Idle-Timeout" on group setting on ACS,it always not worked.
i found in vpn client's statistics,it always has some byte sended or received, i thought it maybe IPsec keepalive message or Radius message.
This maybe the reason because the PIX or ACS think the vpn user is keep working.
Can someone tell me how to make a "idle time out"?
best regard.
Roger

here is the configuration on PIX,
group-policy DfltGrpPolicy attributes
wins-server value 10.0.0.67 10.0.0.68
dns-server value 10.0.0.67 10.0.0.68
vpn-simultaneous-logins 20
vpn-idle-timeout 5
split-tunnel-policy tunnelspecified
split-tunnel-network-list value vpn-acl
default-domain value mydomain.com
address-pools value vpnpool group-policy DfltGrpPolicy attributes
wins-server value 10.0.0.67 10.0.0.68
dns-server value 10.0.0.67 10.0.0.68
vpn-simultaneous-logins 20
vpn-idle-timeout 5
split-tunnel-policy tunnelspecified
split-tunnel-network-list value vpn-acl
default-domain value want-want.com
address-pools value vpnpool

DCNM SAN Client - SNMP Timeout

Similar Messages

Maybe you are looking for