Discovery LMS 3.2 By ICMP

Hello,
I have discovererd devices through icmp as i was facing problems with cdp,i was not able to discover, After discovering by ping (icmp) the devices in DCR are updated by IP address instead of hostname. I have records in DNS. I have not put any  records in hosts file of LMS server locally.
What i have to do for proper name display

The most important setting while configuring discovery is the Global Settngs page. In global setting if you need the display of devices in DCR once discovered with hostname, you have to configure Preffered DCR Display Name parameter as Hostname.
Global Settings
Preferred DCR Display Name
  IP Address
  Host Name
  FQDN
DCR Administration Settings
           Update DCR Display Name
Select a Default Credential Set:No Default Policy Configuration
E-mail Notification
  E-mail:
Preferred Management IP
  Use LoopBack Address
  Resolve by Name
  Resolve by SysName
  None
Add Discovered Devices to a Group
Add Discovered Devices to a Group
Group Name:
Rest it should be able to do it itself, if other pre-reqs are fine like DNS configuration, both ways.
-Thanks

Similar Messages

  • Optimize mtu and mss

    Dear all,
    It is about a IPSEC/GRE over WAN...
    Would you please confirm or comment the following in terms of MTU:
    1. On GRE tunnel interfaces "ip mtu" and "ip tcp adjust-mss" is mandatory. "tunnel path-mtu-discovery" is good to have and will allow DF bit to be set in the outer header. If "tunnel path-mtu-discovery" is to be applied, ICMP should not be blocked between routers.
    2. On inside router interfaces "ip tcp adjust-mss" is mandatory and will be the same value as on the tunnel interfaces. This will make sure TCP traffic from inside hosts is OK.
    3. It is mandatory that ICMP messages are not blocked between inside hosts and WAN routers in order for PMTUD for hosts to be working.
    Thanks in advance,
    Mladen

    No you have not mis-read the document - maybe just been lead down a path a little, my answers are based on experiance.
    I have found that tunnel path-mtu-discovery/PMTUD/BlackHole MTUD do not work in 99.999% of the cases where I have had mtu issues - Windows OS has been where the issues lie. I have never encounted a time where the Windows OS has actually taken any notice of the ICMP fragmentation needed message has been recevied.
    Some Cisco platforms cannot use the tcp mss adjust command on transient packets, only packets sourced from the deivce are effected.
    Cisco firewalls, have default configuration in regards to fragementation - the packets will be fragemented prior to encrypting the packet and they copy the DF bit = the packet will be dropped due to being oversized.
    What I do when dealing with GRE/IPSEC tunnels is either:-
    1) Change the MTU of the workstations/servers - works in small enviroments, does not scale.
    2) You do not have to worry about MTU/MSS sizes on internet sites generally, as the remote servers wil 99% negotiate a small MSS.
    3) Use where possible tcp mss adjust on routers and firewalls (this is a great place, especially when you are not using GRE tunnels)
    4) Perform packet captures to determine if an application will send ALL packets with the DF bit set, or as normal just the TCP handshake.
    Below is a good example:-
    http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008081e621.shtml
    HTH>

  • LMS 3.2 discovery problem

    Hi
    I am doing a POC at one of the customer location for LMS 3.2
    Now the problem i am fcaing is that when i have enabled the discovery based on CDP i am only able to discover two to 3 cisoc device only.
    The customer has around 75 cisco devices including routers.
    Its is not able to discovers the MPLS router across WAN however it is discovering the router where peer to peer link is there.
    Am i missing something
    I have enabled CDP in all the devices but still it is not able to discover the devoves.
    I am using the evaluation version.
    Thanks

    Make sure the SNMP credentials you have configured in Discovery are the correct ones, and that the LMS server is capable of polling these missing devices with SNMP.  You can use a sniffer trace filtering on udp/161 traffic to see what Discovery is sending, and whether or not the devices are replying correctly.
    Yes, Discovery will pick up firewalls with the ICMP module provided the firewall allows LMS to ping it, and poll it with SNMP.

  • Ping Sweep and Discovery in LMS 4.1

    Hello Community,
    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 (https://supportforums.cisco.com/docs/DOC-9005) and which is extemely helpful.
    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.
    What could be the problem and how can we further troubleshoot?
    Thanks in advance,
    Katerina

    I would like to update the post...
    The problem was that in Discovery Settings --> Filter Settings I had excluded the IP addresses, which indicated the connected between our routers and the ISP CPE. As a result the Discovery did find the routers in question, but "rejected" them because one of the interface IPs was found in the "exclude filter".
    Everything is working fine now.

  • LMS Discovery

    Hello friends,
    I want to reach remote sites from head quarters LMS,i have a firewall in HQ connecting to mpls router which in turn connecting to all the sites,through MPLS link,i wanna discover some devices on remote location and also after discovery i want to manage them fully,
    I wanna know which ports i have to open on firewall for LMS full functionality throught the country for branch locations, for some basic i know ,SNMP.CDP ICMP,and i think there are many more?????? pls ur inputs are needful
    Thanks

    Just for Discovery?  All you need is SNMP (udp/161) and ICMP (if using the ping sweep module).  For the rest of LMS, you may need to open tcp/23 for telnet and/or tcp/22 for SSH.  You will also need to leave SNMP and ICMP open.

  • LMS 4.2 | discovery based on specific IP Adress

    Hi Netpro
    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 , please advice?
    thanks
    ibrahim

    1. Please refer to the context-sensitive help when you get to this step. It will give you a page with very detailed file formats and fields that are used (see screenshot below from my lab server). That page is also in Chapter 4 of the Inventory Management guide online.
    2. Device adjacencies are determined via a correlation of various MIB variables including CDP neighbor details and other details. I recommend you read through Joe Clarke's document on understanding LMS discovery.
    One thing to note is that is is best to have the IP addresses of the devices in DNS. If that is difficult for whatever reason, the first create a local hosts file with the devices. You will get better results if the device IPs resolve to host names.

  • LMS 3.2 discovery process runs for ever

    Dear friends,
    I am having a problem with discovery on Ciscoworks LMS 3.2. The discovery process runs eternally and does not discover any devices.
    Here are the individual device versions:
    Name   Version   Size   Status   Expiration Date 
    1. CM 5.2 300 Purchased Never
    2. DFM 3.2 300 Purchased Never
    3. HUM 1.0 100 Evaluation Sun Jul 26 12:18:01 GMT+03:00 2009
    4. IPM 4.2 300 Purchased Never
    5. RME 4.3 300 Purchased Never
    6. VNM 1.0 Unlimited Purchased Never
    Please find enclosed the csdiscovery.log which indicates the following error
    1000 [main] DEBUG com.cisco.nm.csdiscovery.CSDiscoveryManager  - FATAL: Exception occured in the start discovery Exception occured during start of discovery in CS.
    Reason : failed to initialize DiscoveryController
    I am also enclosing the CSDiscovery-config.xml under the config directory and the specific job as well.
    ngdiscovery.log shows 0 bytes. I am not sure if it is to be populated only when we initiate some debugging?
    Thanks a lot
    Gautam

    It seems you're missing some critical files.  Under NMSROOT/conf/csdiscovery, you should have the following zip files:
    SharedDiscoveryAUS.zipSharedDiscoveryCluster.zipSharedDiscoveryGeneral.zipSharedDiscoveryIGX.zip
    The casusers group should have full control on all four files.  If these files really are missing, you will need to contact TAC to get new ones, or you will need to reinstall Common Services.

  • LMS 3.2 CS Discovery finding "0" devices

    All of a sudden, after my "friendly" Windows server admin re-booted my LMS 3.2 box (without stopping the daemon!), my Discovery jobs are returning zero devices discovered. Prior to this, I was discovering 135 devices; which is correct for our environment. Tried deleting all the jobs & configuring new ones, but I get the same results. Tried stopping & re-starting the daemon service with no luck. Basically, we use UTT to feed a NAM process which is still showing entries on a daily basis, so I assume the DCR is still functioning; albeit off older network scans. Discovery is just not updating, therefore, I'm missing recent network adds & moves. Jobs are completing as "successful" but only run for 1 or 2 seconds. Anybody ever see anything like this before? Thought I'd try here for a "quick fix" before calling in a TAC case.....
    All LMS modules are the latest. Recently updated to CS 3.3.0 and CM 5.2.1. Also updated RME to 4.3.1. Everything ran great after these updates. Box is an HP/Compaq DL360 G4 running Windows Server 2003 R2 64-bit; dual 3gig processors; 8gig RAM; dual mirrored 72.8gig SCSI Ultra 320 drives.
    Here's a screen shot of the discovery job report:
    Thanks,
    Rick

    The pdshow looks fine and it seems the discovery ran fine today:
        Process= CSDiscovery
        State  = Transient terminated
        Pid    = 0
        RC     = 0
        Signo  = 0
        Start  = 8/20/2010 12:22:55 PM
        Stop   = 8/20/2010 12:24:00 PM
    Campus Manager Data Collection and the discovery process are separate and should not be mixed up.  The discovery log showed this error:
    [ Thu Aug 19 13:32:43 CDT 2010 ] FATAL  [DiscoveryUtil : isDCRServerRunning]  : DCRServer is not running.
    This seems accurate comparing with the pdshow:
        Process= DCRServer
        State  = Running normally
        Pid    = 12136
        RC     = 0
        Signo  = 0
        Start  = 8/19/2010 1:34:04 PM
        Stop   = Not applicable
        Core   = Not applicable
        Info   = DCRServer is up and running
    So it seems this last discovery captured on the logs could not run because indeed the DCRServer was down at that time.
    Please post a screenshot of Common Services > Device and Credentials > Device Discovery.  Do you see 0 devices discovered there?  Check under Common Services > Device and Credentials > Device Management, if you expand "All Devices" do you see devices there?

  • LMS 4.2.3 discovery missing wireless controller serial numbers

    Hi just ran a discovery on a large network and found 49 wireless controllers (5500, 4400 and 2000 series) and none of them are showing the controller serial number. They are all running 7.0.235.0 and I found no bugs that match this issue.

    TAC was able to find the bug and below is the reply.
    "This is bug CSCud66301 - LMS is not returning the serial number for the WLC in any report. This is going to be fixed in LMS 4.2.4 (out in a couple of months) and may be available a bit earlier as a device package update."

  • LMS 4.2.2. Standard vs Custom Discovery - Custom not really working ...

    Hello Forum,
    I did a new install on VM-ware, via LMS4.2.0 OVA file, updated to 4.2.2 and applied latest deviceupdates etc, like MDF and all.
    In general it runs good, but, I have a huge problem with CSDiscovery.
    My discovery only works in when I choose standard discovery.
    Allthough it takes AGES, due to 1000's of Lightwieght AP's hence I need to filter them out.
    Only problem with standard discovery is that I cannot get the routers to be managed via Loopback interface, as this option is only configureable in Custom Discovery, also the CDPID Filters for the AP ONLY applies in Custom Discovery, to make Discover faster.
    So I need Custom Discovery badly ...
    BUT when I run Custom Discovery, with the exact same setting, as in Std Discovery, the discovery skids over seed devices and marks then unreachable !
    It like runs way to fast all over the devices !
    I then enabled debugging on and looked into ngdiscovery.log in /var/adm/CSCOpx/log
    Here I see entries like SNMP timeout on device etc, but this is simply not true, as I can run the same setting when doing std discovery !
    I am deeply puzzled - So I copied the backed up system-config.xml file hence restoring the default settings, and restarted LMS.
    same problem ... std dis work, cust discovery skids over the seed-devices - ie never gets around to discover anything...
    I am so fortunate to have access to a LMS 4.2.1 installation, on OVA too, and I edited the system-config.xml there and added CDPID filtrers for LAP's and ran Cust dis WITH NO PROBLEMS and super fast !
    So I know the settings are right in the xml file ...
    I can reproduce this in my installation - Std works - Cust runs haywire !
    everytime ...
    I am actuall surprised that the CDPID filters are NOT aplied to std dis, via the XML file !
    Only reads XLM file  when doing Cust dis.
    This i can also verify in the Job-specific files in /opt/CSCOpx/objects/csdiscovery/JOBID
    Are there any bugs related to Custom Discovery vs Std in 4.2.2 ??
    I am on the leap to start all over and NOT go to patch 2, staying on 4.2.1 ...
    But my time is running and I am on the clock here ...
    Please advice, aswell as give you feedback on your experience with cust disc in 4.2.2 on OVA (SoftAppliance)
    regrads
    Martin

    Hi Karel,
    Below are the supprted ,  windows OS ,please check if you are installing it on one of them.
    LMS 4.2 supports the following Windows systems:
    •Windows 2008 Standard Edition Release 1 with SP1 and SP2
    •Windows 2008 Enterprise Edition Release 1 with SP1 and SP2
    Note Only 64-bit Operating Systems is supported on the above versions.
    •Windows Server 2008 R2 Standard Edition with SP1
    •Windows Server 2008 R2 Enterprise Edition with SP1
    Note Only 64-bit Operating Systems are supported on the above versions.
    If above is correct then share the Installation.log , it will be under c:/  drive
    Thanks-
    Afroz
    [Do rate the useful post]
    ****Ratings Encourages Contributors ****

  • LMS 4.2.2 Fault Discovery - Network Adapters Limit Exceeded

    Running fault device discovery after adding approx 50 new devices to LMS DCR. It seems I have reached a limit in DFM with regards to how many device components it can manage. The devices are put into questioned mode and the following error is seen in the Question State Device Report
    Network Adapters Limit Exceeded.The number of Network Adapters discovered by Fault Management exceeded the maximum supported limit.Please check on screen help for more information.     
    What is the limit that is being referred to here? Is it independent of the LMS device licence? Where can I see how many "network adapters" LMS is monitoring? I have approx 900 devices being managed by LMS on a 1500 device licence. I am running LMS 4.2.2
    Any light you could shed on this would be appreciated
    Thanks,
    Mark         

    I've come across this a few times. I did not find a solution. It went away with a reinstall.
    What seems to happen is that somehow DFM puts all the device interfaces in a managed state.
    It should not.
    It should only manage the ports and interfaces that connect to another managed device.
    There is a hardcoded limit of 40.000 managed ports in DFM.
    Suspected situations:
    On one server where I found this the system locale that I put to us-english, was somehow put back to be-french. Maybe even during the installation, not sure who or what did this.
    On another server the anti-virus which I  had turned off, was turned back on during installation,probably by a policy server.
    Cheers,
    Michel

  • LMS 4.2.2 Fault discovery stalls, never complete

                      Using LMS 4.2.2 on a network with approx 800 devices. Fault discovery runs for long periods without completion, previously known devices sit in learning state for long long periods. Some devices do become known but this seems random as to which ones. Faults are still reported on devices in a learning state, which means there are often many faults reported which are false. However because devices are in learning state the false positives cannot be weeded out. This problem has been occuring since LMS 4.0 so have not had Fault and event monitoring working properly for some time, however would seriously like to utilise this feature.
    Would appreciate any pointers as to where to start... Mark

    I am having the IP vs. device name issue as well. The funny thing is if you hover over the IP of the device in Fault Monitor, you can see the device name listed. I was on a conference call with Cisco recently and pointed this out. One of the reps said the faults and alerts showing IP address issue should be fixed in version 4.2.3, but I don't know if he was basing this on first-hand knowledge or was just assuming. Does anyone know if this is the case?
    As for throttling alerts. I had a false positive alert from a device that I put in a custom fault group and changed the threshold on to keep them from firing. You probably have already resolved this issue, but I didn't see a resolution listed here. You would have to determine if raising a threshold for a device is adequate for your situation.
    Thank you,
    Mark

  • LMS 4.2 Device Discovery

    I have used every version of LMS since 1.0 and I'm very familiar with the software.  My problem is with the last few versions and the device discovery feature.  It seems that in earlier versions, once the seed device was configured and devices had the appropriate community strings and cdp was enabled, the device was discovered.  With these earlier versions, all of my devices were discovered.  Any new device added to the network was also discovered.  I never had to deal with devices that were "Unreachable" as all my devices were "Reachable". My network has not changed.  I still have the same core switch ip address since version 1.0.  My edge switches are still configured for the network as they always have.  Same community strings.  What has changed is the LMS discovery process.  What's going on with these "modules"?  I have 120 devices on my network and 117 will be "Unreachable".  Even the core switch is unreachable.  I have tried CDP, Global, seed device, DCR as seed.  Still the devices are unreachable.  There are no firewalls or access lists.  The LMS server has complete access to all devices.  Does anybody have any thoughts, comments??? Or am I just being too picky expecting the software to just work?  TIA                  

    Nothing has chnaged as considerable in discovery module since inception. Addition of new modules and algorithm has just made it stronger and smarter.
    If all the devices are unknown there is certainly some issue with communication using snmp. I would request to modify and if you think multiple communities may be there try to configure all and keep the target *.*.*.*.
    Following guide on LMS discovery stands from LMS old versions to till date similar on how it works :
    https://supportforums.cisco.com/docs/DOC-9005
    -Thanks

  • Lms 4.2 Cannot enable End Host Discovery on Trunk

    Hi...
    I have noticed that our LMS does not collect any information about wireless users connected to autonomous access points, although I can see the mac address of the wireless users on the switch (2960) Trunk port connecting to the AP via CLI. I can also get the IP address from the core switch. Even after selecting 'Perform Data Collection' on the AP in the topology, the Wireless End hosts report remains blank.
    I am trying to enable the option 'End host Discovery on Selected Trunks' in the 'Acquisition configuration in Trunk' menu and after selecting the switch where the AP resides and clicking 'show Trunk' I get the message 'there are no trunks in the device(s) selected', although there are several trunk ports on this switch, other than the one connecting to the AP. The switch and the AP are managed by LMS. We are facing this problem with all Autonomus APs. We do not use WLSE. Is there something missing to discover these Wireless hosts ?
    All help is appreciated

    Is it safe to set UTGetVlansWithUserPorts=0 in the NMSROOT/campus/etc/cwsi/ut.properties ? I have seen this in a previous discussion, but thath was related to LMS 3.1, not 4.2
    Regards

  • LMS 4.2.1 Discovery IP instead of hostname

    Hi,
    we use LMS 4.2.1 and we noticed a strange behaviour when starting a discovery.  From aprox. 160 devices some devices are displayed as IP Address instead of hostname. Every device is DNS resolvable and has a value for "hostname"
    I´ve tried every possible option in the global discovery settings but some devices have the IP instead of their hostname
    Can you tell me how to fix this? Thank you.
    Chris

    DNS is often not understood and just as often implemented badly
    When it is working correct you can do 2 things:
    ping hostname
    will start ping towards the IP address of the host.
    ping -a
    will resolve the ip to a hostname if possibe and then start a ping towards the IP address.
    Often only the first works. Reverse lookup is required by LMS as well.
    if you can fix the DNS you can always create a local hosts file
    Cheers,
    Michel

Maybe you are looking for

  • Short dump while using method start_service_direct in GOS

    Hi Friends I am trying to create attachments for a business object from custom program. I have create attachment and view attachments list push buttions on the screen. when I try to create attachment, program dumps with message 'SET_HANDLER_HOBJ_NULL

  • Issue with renaming Dashboard

    Hi Experts, i have one strange issue...can anyone help me pls i have 4 dashboards.. mydashboard, test1, test2,test3.. the test1 dashboard contains 10 reports and that reports contains navigation reports also.. when i renamed the 'test1' dashboard to

  • Java text editor usb

    Hi i am a java student and i dont really know where this question but my question is Is there a java text editor and java programs compiler for a usb drive?

  • Update the database table inside an user exit.

    Hi Experts, I have a issue where i have to update a custom table in an User exit. I am using Lock object for ENQUE/DEQUE. I have tried to use statements like UPDATE/MODIFY inside the user exit. But the problem is that it's not updating the database t

  • Transform Activity in BPEL 10.1.3 (Developers Preview)

    Hi Have you tried to use Transform Activity in BPEL 10.1.3 Developers Preview? Try this simple test: I create a new BPEL process, add a transform, edit the transformation map: connect the two variables (inputVariable and outputVariable), click save a