Cisco :: DCNM V5.2(2) / S104 Discovery For 6500s Very Slow
Jan 2, 2012
It's been discovering a 6513 for over 90 minutes. Is this an expected duration or is something likely malfunctioning or is it just the sheer # of interfaces that it must process? The Nexus 5k's that it has discovered progressed fairly quickly.
We have a typicaly environment, access, distribution, core, all switches are 6500s.I have a lab environment where machines should not talk to each other, so I think private vlans would be good for this. The problem is that the access connects to the distribution with a 802.1q trunk, while the distribution connects to the core with an 802.1q trunk. See the attached image for reference.
In this case, I would configure the primary vlan (888) on the two access switches, as well as the isolated (886) and the community (887), and set the associations.
vlan 886 name Isolated_PVLAN private-vlan isloated vlan 887 name Community_PVLAN private-vlan community vlan 888 private-vlan primary private-vlan association 886,887 exit
My question is where to I put the promiscuous port? Is it on the uplink between the access and distribution? And If I configure it as I have below, what about the other VLANs that are needed at the access switch? Do they still pass through the trunk as normal, even with the private-vlan configuration? Or would every other VLAN need to be configured as a secondary private-vlan on the promiscuous port?
Licenses are activated on a total of 31 devices (nexus 5000 and 3000 series), data is being monitored, graphics are drawn. However under the Web user interface of DCNM, under Health, Virtual Port Channels (vPC) no data is shown. Performance, vPC is also empty. No vPC errors/notifications are displayed. The installed advanced-eval licenses should support all the bells and whistles (including vPC), but still- no monitoring is done about vPC-s. vPC-s are up and active. network is discovered and monitored via snmp v2c only. could this be limiting vPC discovery- needing snmpv3/ssh access?
if i have a LMS server the newest version, and i bout Nexus 7K with its DCNM ver 5.2 (DCNM-N7K-K9) can i install the (DCNM-N7K-K9) license on the Cisco Prime LMS 4.1 Base so that i can manage Nexus through LMS?if this works Can I manage all Nexus switches also?
I have installed the new version of DCNM Prime (Version: 6.2(1) and all installation process went well without any error or warning, DCNM SAN client works well I can loggin and manage my MDS and UCS, but I have big issue to run DCNM LAN client after successful logging I have window that freezing and nothing is displayed (see printscreen attachment) I reinstalled several time Java, installed four version different of Java, tried this client from three different PC and still have the same issue.
I have installed DCNM 5.2(2c) on windows box to manage Nexus 7K devices.\ have for the time being one device that i have manage and i see often the following text:Discrepancy in device accounting log,Recommended action: clear the accounting log and discover the device. Device details are not available.How can i delete the accounting log and why do i have this message ?
I've recently installed a Prime DCNM 6.1(2) to a Windows 2008 R2 SP1 64 bit version. It seems to be working fine, apart from the DCNM-LAN client.If I login with the Java client, I got the GUI, however it remains blank - I can see the menu, but no data at all. It seems it cannot cummunicate with the DCNM server. DCNM-SAN client, the WEB client and the Device manager works fine, but I just cannot make this work.Tested it from Win2k3 SP2, Windows 7, and the server itself, with Java 1.6.31, 1.6.37, 1.7.13.
I am unable to discover 2 Nexus 5548 with the SAN client of DCNM 5.2(2e)
These Nexus are used like LAN and SAN switch. Each Nexus is a SAN fabric. I would want to use DCNM in order to configurate the zone/zoneset via GUI. These Nexus 5548 run 5.1(3)N2(1b) release.
The Nexus ARE NOT managed via the Mgmt interface (OOB) but they are managed via an interface vlan (InB)
I could not configure rightly
- the snmp-server user (SNMP user V1/v2 or V3 + group ? ) CLI on Nx
- to configure the discovery in order that DCNM discover each fabric either from web GU interface or java SAN client
I am trying to get our DCNM to discover the 5548. When I put my credentials for that appliance. I get this error .Failed Device x.x.x.x OS Version 5.1(3)N1(1) is not supported . The DCNM version we have is 5.2(1)S74.
we are having trouble logging into the webinterface of our DCNM installation.
(Cisco Prime DCNM 6.1(2), Windows 2008 R2 SP1 64 bit version, US)
Everything seems to be working fine so far, except the login to the webinterface.
When calling https://<SERVER_IP> (we're using 443 and 8443 in our setup), the login page appears. Entering the credentials results in the message "Authentication Failed. Please try again.". We tried that from a remote machine and the server itself and are using local authentication (not RADIUS or LDAP, ...).
On the other hand, when running the DCNM LAN Client (using the same credentials not working for the webinterface), there is a link (see image below: "here") pointing to the webinterface.
if i have just DCNM-N7K-K9 (DCNM for LAN Enterprise License for one Nexus 7000 Chassis) installed on a server, i can manage all nexus switches like 5k and 2k??
We've gotten two Nexus 7009's in and I'm starting to configure them when I found I couldn't add VDCs. I found there was no license installed but the only licenses I found that came with them are "Cisco DCNM for LAN Enterprise Lic for one Nexus 7000 Chassis". So my question is this - do I need to configure a DCNM server to get the license pushed to these two 7009s or should there be another PAK for each chassis that I can register and get my enterprise services?
I am having trouble getting 1142 LAP to find the controller. We are running an ASA 5505 at our main campus where the 5508 is located. Each Of our distribution centers have a PIX501 and from there about 3-5 AP's each. The AP's that were primmed before instalation work great, however we need the ability to get the other ones that were already installed and not finding controller to work with out cycling them through main campus. I have opened up UDP ports 12222-12223 and 5246-5246 with no luck.
we're evaulating the Cisco SM 4.2. After adding my ASA 5520 the Policies are discovered from the device except the RA VPN Policies.I tried to trigger the discovery process manually and i got this errormessage Please verify the device "IP address", "hostname", "domain name" and "port number" are correct, there is network connectivity between the CS Manager server and the device, and the device is configured to accept https connections, the device is running, and then retry this operation.which i don't understand because the other policies were retrieved just fine.
I have a problem discovering some ASA firewalls on a network. I have several ASA firewalls on this /24 network, but some of them I can't discover e.g 149.x.x.107 is discovered ok, but 149.x.x.20 I can't discover. It seems that it's not even trying to discover the devices I have problems with. Nothing is shown in the discovery log.
LMS 4.2, W2K8 R2.I was having an issue with discovery adding devices to with corrupt information (seemingly random strings of characters in several fields). While I was trying to clean this up a scheduled discovery kicked off and further exacerbated the issues I was having. Frustrated, I deleted all entries from the discovery schedule until I could get things cleaned up.
Now I want to go back and troubleshoot the discovery process. Trouble is, I can't get discovery to do anything anymore. I disabled all modules but CDP. I added a single seed IP address under the CDP configuration. This is the address of a 3560V2 switch that is not in DCR. When I started discovery it completed in about 2 seconds and didn't discover anything, including the seed device. So I added another 3560V2 as a seed device under global settings. Same results. Thinking that it had been working using scheduled discovery, I set up a schedule and kicked it off that way. Same results. Finally I added one of these seed devices to DCR and let LMS fully learn about it. Ran another discovery. Still no joy.
I started an SNMP debug on the seed devices before starting discovery. I see the SNMP get coming from LMS, the switches respond and the discovery completes with 0 devices discovered.CS Discovery.log contains no meaningful information. Only messages about "No appenders could be found for logger".
my customer is using Cisco Prime 4.1 as an Upgrade from LMS 4.0 and has made a discovery of a new added Cat 4506E with a Sup 7E and Modules.All the devices have been discovered, excepted the module WS-X4712-SFP+E.Is this card not supported yet ?I could not find any detailled and actual information about the support or not of this module, or about the conditions for the Module support it in Prime 4.1..How ist it possible to proceed to having this module discovered ?
We have just installed LMS 4.0.1 and started to discover parts of the network. After the discovery process finished successfully - 100+ new devices were added to DCR message - I was able to see the devices by clicking on their number but when I go to Inventory-Add/Import/Manage Devices I cannot see any device in the Group that I created.If I restart the CiscoWorks Daemon Manager process the newly discovered devices are added to the custom Group. This seems like a bug as I had a LMS 4.0 evaluation installation a few months ago and device discovery was working fine meaning the devices were added immediately to the Inventory.
i am installing a CWLMS 4.0 and everything was good until i have reached the discovery for the devices, i am dealing with a bank setup and the branches is connected using layer 3 MPLS, branches are located behind the ISP router, so as a cdp neighbor i cant see anything but the ISP router at my Core.
so i cant see the branches routers as neighbors to my (seed Device) Core, and i have tried to use the ping sweep and i could not reach them also. and also to add them manually as we were doing before in the earlier versions of CWLMS, using the Devices and Credintials, this option is removed from the LMS 4.0 as i have red in a document.
1- snmp is configured on all devices. 2- access-list is configured on all devices. 3- i am able to reach the LAN Devices without any problems and the configuration is the same on all of the devices.
We are running CiscoPrime LMS 4.1 and I have a problem with PingSweep in Device Discovery. Our company's branches connect to the main site through GETVPN. Discovery through CDP, Routing Table and ARP cannot be used based on the document written by Joseph Clarke [URL] and which is extremely useful. So the only available option is PingSweep.
The loopback interfaces of all the remote GETVPN devices are in the same IP range, so this was configured in Module Settings --> Ping Sweep in the Discovery.
Unfortunately none of the devices get discovered, even though there is icmp connectivity from the server to the loopbacks.
I am using lms 3.2.where I have added devices manually.Because discovery settings the device are taking some random ip updating the display and hostname.
I am using CISCO PRIME LMS 4.1 for manage my network, i ran a device discovery job using a ping sweep on the ip ranges of my network, ie 192.168.1.0/24, 192.168.2.0/24 and so on... the discovery found all my devices, but it discovered duplicate devices with illegal ip Addresses, i.e.,
ip device 192.168.1.255 S1 192.168.2.0 S1 192.168.2.1 S1 (the real address)
all in reachable status.
I don't understand why the program adds that repeated illegal addresses.. How can I run the device discovery to avoid this problem?
my system's network discovery is always off even when i try to put it on again it goes back off immediately...can it be related to the firewall settings or wat else can be preventing it from coming on?
I have just installed prime 1.3 (brand new install), we have started a discovery job to find one switch (IP address), this job has so far come up with 311 credential failures and appears to be going through every 127.0.0.x IP address it can.Is there a way of stopping this job from running. Clicking on the Red X next to the name has no effect.
I have one questions regarding if C6509 suports "ip tcp path-mtu-discovery" ? apply this command to GRE interface on C6509? if yes, let me know what is the the IOS for that.
I have a client with a 2112 WLC and 1252AG radios. The clients work fine, but an SNMP management server can not reach any of the clients over the wireless. Before the WLC and new AP's were installed, they were running older Cisco Autonomous AP's and had no problems with SNMP. My monitoring system uses SNMP and it can reach the WLC just fine, so there doesnt appear to be any issues on the switched network. What can be blocking the SNMP on the WLC?
I have newly deployed a Prime Infrastructure (PI) in my network, and i want to add my wirless controller in it. I get an error SNMP time out whenever i add my controller to PI through SNMP.
There are default SNMP configurations in the controller and i am simply adding them in PI with their private/public SNMP string.
WLC 5508 is connected to my core switch and PI is connected to another switch which is directly connected to core switch via Layer 3.
Is there any configuration required to be done on the switch side.?
whats the difference between custom and standard discovery? There´s a line on the help page: "The Use Policy Configuration Settings radio button will be enabled only after adding a Default Credential Set Policy."The radio button is not enabled although I´ve two default credential sets and two default credential sets policy configuration.
1)is there any methods to let LMS 4.2 discover Cisco devices based on specific ip like Loopback address ? coz in my Cisco devices i have more than ip address configured?