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?
The problem is that - although negotiated in global discovery settings - Prime appends domain name to the device name so that all switches (not routers) have "confusing names". The domain name is not required in device name. What can i do?
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 ?
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 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.?
we are running CiscoPrime LMS 4.1 and I have the following problem.I have configured SNMP Settings as shown below (the order of the targets is exactly as it is configured on the server):As can be seen we use three different read community strings. I also have exluded a bunch of IP ranges and IPs from the filter settings. When I manually start discovery everything works fine, meaning that all devices in the above ranges that need to be discovered are discovered as "reachable". The problem appears in the scheduled discovery (happens once daily). In that case only the devices with Read Community snmp1, get discovered as "reachable". All other devices with Read community snmp2 & snmp3, as well as those that are excluded in the filter settings, are discovered as "unreachable".The discovery uses DCR as seed and seed devices are also configured.I also have a problem with PingSweep in the discovery, but I will open another discussion so that I don't complicate this one too much.
I´m getting started on ciscoworks and i trying to configure a device discovery to start but i have some questions about how configure this tool exist 5 parameters that i have to configure to start the device discovery.
I want to add devices that found neighbors via CDP son in the configuring discovery module setting i choice that option In the configuring seed device setting i choose DCR as seed device that means those devices already in the DCR start discovering from those devices but you can add more seed devices how i can add a seed device ? with ip addres or something like this? and this device have to be in the DCR already or not? The configuring SNMP settings, this community correspond to what device? the devices that i want to add ? and in the field target name what ip adders have to be? and if i have different community of snmp in my devices what device and snmp community have to configure in this parameter
I use the Edit Identity option to change the "Display Name" from an IP to a station name, it is overwritten when a discovery has been done. I have checked the discovery settings and tried using the update DCR Display name setting to prevent this from happening, but it makes no difference.Is there something i am missing? This is on LMS 3.2?
we use LMS 3.2 in our network. We have a couple of 6509-V-E Switches with mutiple interfaces (VLAN interfaces and Layer 3 interfaces) The problem is, campus manager discovers the switch by a interface randomly...one time its a lay3 Interface and another one its a vlan interface which none of them are in DNS hence no name resolution can be made.
Is there a way to "tell" CM to us for instance the VLAN Management IP of the switch?
I have a very special usecase with migrating devices from LMSv2.6 to v4.1 using DCR bulk import that was maintained manualy, not by discovering.The special thing is each device has its own SNMP-community and its about 1500 devices.RME discovery works fine, but I get the devices not discovered by DCR (CSDiscovery), because I need a minimal DCR discovery configration containing Seed and SNMP-settings. So I activated DCR as seed, but cant skip SNMP settings without an entry. But in this case I would need 1500 SNMP-lines that would be very unhandy. is in CSDiscovery-Settings a possibility to can leave SNMP settings untouched so it takes the credentials from the DCR, to can start DCR discovery?
I have problem in recently installed LMS 4.1 Device discovery will not start when launched manually. When i hit the button, it doesn't even give a popup window saying that the discovery is started and that email will be sent... If I schedule it is launched, runs and finishes correctly. All proceses are started and it seems that application is working ok. LMS is installed on Win 2008 R2.
is there anyway to change the IP address of a device without data lost? I saw an option in to change it in Inventory > Device Administration: Add / Import / Manage Devices > Edit identity but from what I read I can get a data lose,
We are currently running Cisco prime 4.1 and want to make sure there is a backup of the configurations from our switches and routers. The VLANconfig is not collected according to the devicestatus dashboard. i am aware there were a known issue with LMS running on a virtual server and vlan not being able to be collected, is this issue resolved? i have tried the various workarounds with TAC support and it hasnt worked. We have the running and startup config collected for our devices when looking at the device status dashboard. does this mean if a switch crashes we can restore the config to a new switch immediately?
i saw there is a version 4.2. maybe this version resolves the issue with LMS on a virutal server? i cannot find the download to upgrade to 4.2 in the support section though.
I am trying to figure out why the Device view has no systlogs in Cisco Prime 4.1.I have everything configured, the switch is sending debugging level logs to the IP of the Prime Server. I am fairly certain it is reporting because it has alot of other information in the server.
We have a Prime LMS and a Prime NCS instance running. At the moment, instead of having the 2 systems do device discovery independantly, I thought a good way to set things up would be for LMS to do all of the discovery, and then export the DCR from LMS into NCS.
Now doing this manually in a cinch, but I'd like to automate the process. LMS has some nice scripting features that allows me to easily use the 'dcrcli' script to export a CSV file of the all of devices and credentials, which can be put in a format that NCS can bulk import. I plan to do this on a regular basis using a cron entry.
What I can't seem to find is any documentation on how I might be able to achieve the import piece of the puzzle on the NCS box. Are there command line utilities as with LMS that would allow me to import devices, and put the scripting into a cron file to do on a regular basis?
I have problems with setting the snmp retry / timeout parameters for our devices. I managed to import our devices with bulk import , but after it I realized that for some devices the snmp retry / timeout values were different ( created the bulk file with 3 retries and 30 sec timeout , but in the system the appear with 2 retries and 1 sec timeout). I tried to change it manually , but after a while it goes back to the wrong values.
We have LMS Prime 4.2. I know how to view the running config on a single device. How do I run a report that will pull all the running configs of all my devices in one report? I'd be able to same them as one big pdf or text file. ]
before I open a TAC case: How does Cisco Prime NCS handle the device licenses for stack of 3750 switches? Just one device license for the stack or a license for every physical switch in the stack? I can't find a answer on the Cisco website, but maybe one of you knows it from a deployment you have done..
We're currently evaluating Cisco Prime LMS 4.2.Something we've been trying to achieve for the past couple of days is to have LMS notify us when a Microsoft Host is Unreachable, and then to notify us once that alarm has cleared (the Microsoft Host is Reachable again).
We're at the point where the Microsoft Host was discovered, LMS incorrectly identified it as a Cisco Call Manager, so we changed it's identity to non-cisco device > microsoft host > microsoft host. LMS currently has the device listed as being in the 'Questioned' state. SNMP timeout has been set to 15 seconds, and the SNMP community is correct.
Being new to LMS Prime, and having not received any training on the product to this point, we turned to the admin guide, but we couldn't find anything that goes into detail for how to manage the notification for non-Cisco devices.
Is what we're trying to achieve possible with Cisco Prime LMS 4.2? We just want to be able to receive simple 'host unreachable' notifications for Microsoft servers, and the corresponding 'cleared' notifications once the server is back online.
I'm currently running CiscoWorks LMS 4.0.1 on Windows 2003 under VMware and just got upgrade licensing for Prime Infrastructure 1.2. I am assuming that I will need to upgrade the current server to Prime LMS 4.2 in order to ensure that data migration to Prime Infrastructure goes well. I am planning to follow Cisco's recommendation to run Prime LMS and Prime Infrastructure in parallel for a time and migrate individual functions.
My real question is about Syslog handling. All of the managed devices are currently sending Syslog data to LMS. As a last step in the migration, is it possible to change the IP address of the Prime Infrastructure server to replace the Prime LMS server so that the Prime Infrastructure server will just start getting all the Syslog data, or do I need to go change hundreds of managed devices to point to a new address?
What is the relation between: cisco NCScisco Prime LMSCisco Prime infrastructure.As i orderd a Cisco Prime infrastructure from a Cisco Partner and what i got is :
x2 cisco NCS appliances x1 DVD cisco prime infrastructure x1 DVD Cisco prime 4.2
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".
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.
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 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.
