LMS4 UT ping sweep questions

On the Admin > Collection Settings > User Tracking > Ping Sweep page, subnets that may be excluded from the ping sweep is presented.  How does CM populate this list?  In my environment I have some foreign subnets listed (don't know what these are or how they got there) and I have several valid subnets missing.
I know that in LMS 2 ping sweeps were limited to Class C (254 hosts or < in size).  Since I see subnet masks in this mysterious list defining networks that are larger than that I have to assume LMS 4 does not have this limit.  However, help and documentation states that "User Tracking does not perform Ping Sweep on large subnets, for example, subnets containing Class A  and B addresses."  For example?  So what is the limit?
Thanks,
-Jeff

Hello Michael,
This discussion was not intended for the completeness of L3 resolution for the end hosts in UT, but that what you called “something else”: why is this single device is unreachable for UT although its managed by all other LMS moduls and its IP is ping/snmp-able.
Yes in this network we have also the problem, that the L3 device is none Cisco (not manageable in LMS) and I tried to improve (after Joes hints) the L3 quality of UT with:
1. DHCP-Snooping => we had to remove because it had slow down the network (don’t know why but after removing DHCP-Snooping, the performance was coming back)
2. Ping ip in switches kron => no improvement and I cant understand why only a little part of the filled Switch-ARP table will get into UT. IP routing as a prerequisite that LMS will ask the switches ARP-table is enabled at this L3-switch.
3. I will try today: rollout of UTLite to the clients
But for this part of problem I created a separate discussion in the past.
Steffen
Von: michel.hegeraat
Gesendet: Dienstag, 12. Juli 2011 18:35
An: Neuser, Steffen
Betreff: New message: "LMS4.0.1 - UT Aquisation complains about reachability of some devices"
Cisco Support Community
Re: LMS4.0.1 - UT Aquisation complains about reachability of some devices
created by Michel Hegeraat in Network Management - View the full discussion

Similar Messages

  • Cisco Prime - Can I ping sweep devices to wake them up before the devices are acquired in User Tracking

                     I have some devices on my network (printers and security cameras) that go to sleep and do not show up in the ARP table under I ping them.  Is there any way in Cisco Prime (before User tracking is acquired) to do some sort of ping sweep?  If I do not "wake up" these devices in some way, then they do not show up in User Tracking.

    Just set up the connection and it should not effect your connection to your pc
    If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
    If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

  • 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.

  • Ping Sweep on specific IP range

    Hello!
    I have a question concerning Ping Sweep On IP Range function in LMS 3.2.
    The costumer have MPLS cloud so CDP discovery is not functional.
    There are more then 400 branches.
    I would like to set the specific ip Range like following because the B class mask is to large for discovery process ( ~7,5 day )
    10.31.1-50.0 / 255.255.255.0
    10.32.1-50.0 / 255.255.255.0
    10.33.1-50.0 / 255.255.255.0
    10.34.1-50.0 / 255.255.255.0
    10.35.1-50.0 / 255.255.255.0
    10.36.1-50.0 / 255.255.255.0
    10.37.1-50.0 / 255.255.255.0
    10.38.1-50.0 / 255.255.255.0
    10.39.1-50.0 / 255.255.255.0
    What is the right syntax in this case ?
    Regards,

    Hi,
    i tried the following syntax in ping sweep seed devices.
    10.39.[1-50].240      255.255.255.240
    The log shows the following
    [Feb 26  12:29:02] FATAL  [PingSweepDiscoveryModule : main initialize]  : getting seed device ipaddress failed10.31.[1-200].240: 10.31.[1-200].240
    [Feb 26  12:29:02] FATAL  [PingSweepDiscoveryModule : main initialize]  : getting seed device ipaddress failed10.32.[1-50].240: 10.32.[1-50].240
    [Feb 26  12:29:02] FATAL  [PingSweepDiscoveryModule : main initialize]  : getting seed device ipaddress failed10.33.[1-50].240: 10.33.[1-50].240
    [Feb 26  12:29:02] FATAL  [PingSweepDiscoveryModule : main initialize]  : getting seed device ipaddress failed10.34.[1-50].240: 10.34.[1-50].240
    [Feb 26  12:29:02] FATAL  [PingSweepDiscoveryModule : main initialize]  : getting seed device ipaddress failed10.35.[1-50].240: 10.35.[1-50].240
    [Feb 26  12:29:02] FATAL  [PingSweepDiscoveryModule : main initialize]  : getting seed device ipaddress failed10.36.[1-50].240: 10.36.[1-50].240
    [Feb 26  12:29:02] FATAL  [PingSweepDiscoveryModule : main initialize]  : getting seed device ipaddress failed10.37.[1-50].240: 10.37.[1-50].240
    [Feb 26  12:29:02] FATAL  [PingSweepDiscoveryModule : main initialize]  : getting seed device ipaddress failed10.38.[1-50].240: 10.38.[1-50].240
    [Feb 26  12:29:02] FATAL  [PingSweepDiscoveryModule : main initialize]  : getting seed device ipaddress failed10.39.[1-50].240: 10.39.[1-50].240
    How can i strict the ping range for the discovery process???
    Thanks in advance!

  • Having issues running terminal ping sweep on Yosemite

    After upgrading to Yosemite I am no longer able to run a ping sweep using the terminal command:
              for i in {1..254}; do ping -c 1 -W 1 192.168.1.$i | grep 'from'; done
    It returns:
              -bash: syntax error near unexpected token 'do'
    Any ideas?

    I still get the error...
    cyclops-mac:~ banchee$ $ for i in {1..254}; do ping -c 1 -W 1 192.168.1.$i | grep 'from'; done
    -bash: syntax error near unexpected token `do'
    cyclops-mac:~ banchee$

  • LMS4.1 Template Center Question

    Hello,
    Is it possible to access global variables (current device and current port) in the CLI commands and what are there names?
    The customer wants to run the "default interface gi x/y/z" command before deploying customized commands, but it is not inside the interface context and need to be parametrisized, for example:
    <cli name="edgeConfig">
        <clicommand>
    default interface ${current_port?}
    switchport access vlan ${access-vlan-id}
    switchport mode access
    switchport voice vlan ${voice-vlan-id}
        </clicommand>
    </cli>
    Steffen

    Hi Jo,
    Thx for the variablename, but the 2nd part of problem with differnt command level in one template is left:
    default interface ${current_port?}
    belongs at global level and the remaining statements at interface level.
    Please see, why it is not working below. Have you got an idea to get this working?
    Results for Device Sw01234
    Device Deployed
    Pre Device Execution Message:
    Post Device Execution Message:
    Update Startup Not Attempted
    Results of Deploy:
    Message: Deploy command partially failed
    defaultdefault
    % Incomplete command.
    Sw01234(config)#
    interface Gi2/0/43Sw01234(config-if)#
    switchport access vlan 20Sw01234(config-if)#
    switchport mode accessSw01234(config-if)#
    switchport voice vlan 152Sw01234(config-if)#
    Sw01234(config-if)#

  • LMS 3.2.1 sending more pings than thought usual

    Hi,
    I'm looking for some assistance or tips with troubleshooting LMS 3.2.1 and the ping/ICMP traffic it transmits.
    A lot of my devices are receiving a lot more pings from LMS than I would have anticipated.
    I don't run PING sweeps in Device Discovery or CM-UT. I've even disabled DFM polling in a hope to trace the source of these PINGs.
    Does anyone have a list of which modules use PINGs so I can turn them off and track down the offender.
    I really only want to manage the known devices I already have via SNMP alone. I don't require LMS to be PINGing for discovery or reachability purposes.
    Any help is appreciated.
    Kind Regards
    David

    Hi Gaganjeet,
    Not quite correct.
    DFM was still pinging after I disabled ALL polling parameters and saved/applied. I had not restarted the daemon. I didn't believe I had to.
    After that I tried to delete all the devices from DFM (Auto-allocation was also disabled) but they would not delete.
    (I have another LMS server where DFM will not learn devices from DCR and comes up with the 'TreeManager' error but all fixes in Forum failed. Could this be the same bug?)
    After this I restarted daemon manager (LMS) and it stopped pinging.
    Is this normal operation for DFM?
    I'm interested in the script if you can send it to me. Basically my management loopbacks are in one or two subnets only and we have no desire for the user vlans to be pinged. Besides loopbacks will never go down unless the switch does.
    Basically the distribution-switch cpu reaches 100% utilisation as all its SVIs are pinged simultaneously. Changing the time intervals extends the polling but this has the negating effect of delaying alerts and warnings, etc.
    I'm trying to find the happy balance but DFM is not very flexible. It's all or nothing.
    Many thanks for your help. Please let me know how I can get that script.
    David

  • LMS 3.1 is Pinging huge number of weird IP addresses?!

    Our security group is reporting Ping_sweep events from our LMS 3.1, (windows 2003) system to huge range of internal and public IP subnets, I am unable to locate this IP address range within the LMS application. I am wondering why  LMS is actuallying pinging this IP address range? and how can I stop it?
    Thanks,
    Muhannad

    Hi Michel,
    This didn't work out, i have added this IP address and still the LMS sending the Ping sweep to this IP address.
    I have turned off the DFMserver process and kept the  DFMserver1, this stopped the ping sweep to all the weird IP addresses but i am wondering if this will impact the DFM operations or i can use it as a workaround?
    Also i read about a DFM patch that should stop the DFM ping sweep and make it work only with the SNMP polling: http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/faq/dfm_faq.html#wp1023696
    Please can you confirm it and advise me about the proper patch to download, your help will be appreciated.
    Regards,
    Muhannad

  • [SOLVED] Finding the IP of a device

    Alright, so I installed arch on a computer and set sshd to run in the background. At the moment, the computer doesn't have a monitor, and the other computer in my room is a laptop (so no screen switching). I want to be able to log into the monitorless computer via ssh.
    Anyway, both computers have a wired ethernet connection to a switch in my room (which is needed to get any connection at all by my university). They both get a dhcp-leased IP that is NOT on a subnet, meaning every device shows up as an independent IP when queried.
    So, my question is this: is there a way I can figure out the IP of the monitorless server running ssh, so I can log into it? I know the hostname, if that helps.
    Last edited by Ferrenrock (2010-02-10 13:09:23)

    Sorry about the wait--I took mdickinson's advice and did a ping sweep with the cord unplugged. Originally, I had done it for all 255 addresses in the subnet and it had been impossible to figure out anything.
    raf_king, fumbles: My wording was awful, partially due to the fact that half of what I said was wrong: what I meant to say was that every IP is a <b>public</b> IP (and not behind any sort of NAT), and while the switch in my dorm room might physically be a subnet of its own, address-wise the fourth octet corresponds to a subnet consisting of multiple rooms. Perhaps this will explain it:
    [root@xaiwos ~]# ifconfig eth0 | grep inet
    inet addr:130.126.66.100 Bcast:130.126.67.255 Mask:255.255.254.0
    [root@xaiwos ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    130.126.66.0 0.0.0.0 255.255.254.0 U 202 0 0 eth0
    0.0.0.0 130.126.66.1 0.0.0.0 UG 202 0 0 eth0
    [root@xaiwos sampo]# nmap -sP 130.126.66.1-255
    Starting Nmap 5.21 ( http://nmap.org ) at 2010-02-10 05:56 CST
    Nmap scan report for uiuc-tri-net.gw.uiuc.edu (130.126.66.1)
    Host is up (0.0017s latency).
    MAC Address: 00:15:C7:24:7C:00 (Cisco Systems)
    .......(blah blah blah 20 IPS)........
    Nmap scan report for tri0752.urh.uiuc.edu (130.126.66.100) <--my laptop
    Host is up.
    Nmap scan report for tri0764.urh.uiuc.edu (130.126.66.112) <--my xbox
    Host is up (0.00010s latency).
    MAC Address: 00:22:48:77:74:AA (Microsoft)
    .....(one hundred more IPs).....
    But when I unplugged the switch from everything else, I got
    [root@xaiwos sampo]# nmap -sP 130.126.66.1-255
    Starting Nmap 5.21 ( http://nmap.org ) at 2010-02-10 06:25 CST
    Nmap scan report for 130.126.66.100
    Host is up.
    Nmap scan report for 130.126.66.112
    Host is up (0.00010s latency).
    MAC Address: 00:22:48:77:74:AA (Microsoft)
    Nmap scan report for 130.126.66.150
    Host is up (0.00013s latency).
    MAC Address: 00:E0:4C:39:9B:08 (Realtek Semiconductor)
    Nmap done: 255 IP addresses (3 hosts up) scanned in 29.16 seconds
    After that, the answer was pretty clear which one was the mystery computer.
    And now I just remembered that I forgot to change the hosts.allow file on that other computer....crap....

  • How to resolve hostname in Common Service 3.3 ?

    hi guys!
    i have a problem when discover my devices in ciscoworks common service 3.3.
    i discovered use module setting cdp and ping sweep , preferred dcr name is hostname, and update dcr display name is checked.
    i hope the hostname is show in display name but there is ip address.
    i search this problem is bug CSCsq54877 and CSCsv65933 but its resolved in common service 3.3.
    my question:
    there is any problem in my discover settings or is still a bug.?
    could anyone help me to preferred show hostname than ip address ?

    i make a trick.
    i use hosts.etc in windows server where the ciscoworks installed

  • Non CISCO unknown devices are being discovered in LMS

    Hi!
    I have had no problem with discovery which was used on cdp basis so far.
    Now the CDP packets do not arrive via new MPLS backbone network.  I have to use the "ping sweep feature in IP range" feature. I had to enter more than 400 subnet from file before there are more than 400 branches. ( etc. 10.31-9.1-50.252 255.255.255.252 )
    I have experienced two problems
    1. The discovery never end ( now this is not important ) :-)
    2. The common services -- device management shows discovered unknown devices whose ip addresses out side the range what are entered by me in the ping sweep range and theirs OID is not CISCO.
    (  1.3.6.1.4.1.2001.1.1.1.1  ,  1.3.6.1.4.1.11.2.3.9.1  ,  1.3.6.1.4.1.674.10892.2  , 1.3.6.1.4.1.18334.1.1.1.2.1.7.1.2 and even more )
    Due to more than 300 unknown devices the LMS device number is beyond the license number!!!!!
    Our questions.
    Why does lms add the unknown devices ( non cisco devices ) to the inventory ?
    How could lms discover  these devices ??? ) ( theirs IP are out of ping sweep range and non cdp capable devices )
    Thanks in advance!

    Thank you!
    The unknown devices were in unreachable state and they were added to DCR.
    I don't use include or exclude filter what were referred by bug.
    In spite of i use seed device list from file the LMS ping sweep debug log shows that LMS try to ping other IP addresses!!!!
    You're right, it is not normally operation may be TAC will be needed to  solve it.
    ( whether who tested it ?)
    Regards,

  • LMS 4.1 User Tracking

    Does someone know if or what is the best way to do a acquistion on ip address on devices that appear to be dead until ping before LMS4.1 reports onn them. For example we run acquistion on a branch we do not see 172.20.12.51, howver we ping it from my desktop and then run user tracking and then it shows up.

    One option when setting up discovery is to do ping sweep of the target subnet(s). It has pros and cons. Reference page 5 of the LMS 4.1 (not just) for Dummies Guide.
    OTOH if an device appears inactive until pinged, it must not be typically generating traffic to its default gateway (or that gateway is not managed by LMS) as that would be the normal source of information about the host (ip-mac correlation anyhow) in a default discovery type.
    Hope this helps.

  • Viewing devices by hostnames in DCR

    Dear Friends,
    Just one quick question:
    Is there a possibility to see the display name of the devices as the hostnames?
    I am right now seeing only IP addresses.
    The settings i chose are "Preferred DCR Display Name" being "Hostname" and the "Preferred Management IP" being "None".
    I dont have a DNS to do the name to ip resolution for the devices.
    But i still thinking if there is a possibility to see the hostnames instead of IP addresses in the DCR as the hostnames appear more readable.
    Please advise.
    Thanks a lot
    Gautam

    Dear Jason,
    I have two loopback addresses per device viz. private and public loopback.
    So i believe that discovery by sysname should be better.
    I have discovered these devices using ping sweep module with the ip range being on their private loopbacks.
    So i hope they would have been added to the DCR with their private loopbacks only. I dont have a chance to check it now but tomorrow morning i will check it again.
    I will add to the local dns file and see how it goes. But should i do a rediscovery again or will the dcr get updated automatically?
    Just one more question out of curiosity, if i could go beyond the scope of my original question.
    When i discovered with ping sweep, i was prompted with the seed devices and the include/exclude filters.
    When i gave the seed device and the include address filters, i noticed (wireshark capture) that the ping sweep was only happening on the seed device and not on the include address filters.
    When i removed the original seed device ip address and just put in the ip addresses (which i put earlier in the include filter), then i was able to see that it was doing a ping sweep and also a snmpget to the device.
    I am not sure why you need a seed device for ping sweep module? It seems to make sense for cdp module but i dont see why you need seed device for ping sweep module.
    Thanks a lot
    Gautam

  • Catalyst 4507R plus E Switch Discovery Issue

    Hi,
    I am having issues doing automatic discovery for Cisco Catalyst 4507R plus E Switch IOS 12.2(54)SG, I am using IP ping sweep to discover devices on my network.
    When i first setup LMS4.0 with few devices on the network, i discover the C4507 without a problem together with other devices i have on the network but for some reasons now its failing to discover C4507. I have large numbers of WS-C3560X and C4507 on the network, WS-C3560X always discovered just fine.
    I tried to use SolarWinds network device monitor I installed on the server to check if there's any SNMP or connectivity issues. I can discover C4507 using Solarwinds without a problem, so im suspecting it could be LMS configuration issue.
    Is there any special settings I need to tweak to make this working?

    A newer version of IOS should generally be fine.
    It's generally the SNMP sysObjectID that LSM keys into. As noted in the table you cited, it should be 1.3.6.1.4.1.9.1.1286 for the 4507R+E.

  • LMS 4.0.1 - DFM issue

    HI,
    I installed the LMS 4.0.1 and I'm facing a problem with DFM. None Fault is showed.
    The Fault Discovery Process never finishes, it is always Running, according attached file.
    I checked the LMS Process MAnagement and 4 process are as "Transient Terminated". The  process are: CSDiscovery, DCRDevicePoll, FHPurgeTask,UTMajorAcquisition. I started all process but 2 minutes later the process goes to "Transient Terminated".
    All Windows Services related with CiscoWorks are UP.
    Someone knows this issue?
    Thanks for your help.
    Luis

    Hi duong,
    I'm using the ping sweep. not using the "Use DCR as Seed List" as there were more than 5000 devices.
    Earliar LMS pick the devices. once the discovery was running for a long time . to stop the same we have restarted
    the CSDiscovry process. After this we are facing the issue.
    Channa

Maybe you are looking for