LMS 4.0 discovery issue

Dear All,
           I have a question, can i discover a device with more than one IP address, as i need to discover my remote site router with both of it is IP addresses, as i have two different connections to this router with two different service providers, and i want to make sure that if there is a failure at one provider i still can discover the device using the second IP address ,
Note: i would not like to router LAN through both connections and i would not like to add loopback to my router
Is there is a way to do this
Please help                    

Dear All,
Please help, does anyone has any idea how this solution can be implemented

Similar Messages

  • LMS 3.1 Device Discovery issue

    Hello,
    I have been getting myself familiar with LMS, but can't figure out why I am having issues seeing some devices. I can't find any solution to my problem on other posts.
    I have a server farm connected to my core switch, both can see each other via CDP, and the SF can ping the LMS server. However, I have 'device unreachable' on device discovery and CiscoView. SNMP community strings are the same on each device, and are configured on LMS.
    Any suggestions? Thanks in advance!

    Hi,
    LMS tries to contact each device directly via SNMP. If it can talk directly to the device, the device is added into DCR as Reachable. If it cannot talk directly to the device, the device is deemed as Unreachable and it is not added into DCR to be managed by LMS.
    If LMS is unable to communicate it could be due to any number of things including timeout, incorrect community string, snmp-server view, firewall or access list.
    A definitive way to determine the issue would be to perform a packet capture during discovery to see the SNMP transaction between LMS and an 'unreachable' device.
    You can also try increasing the timeout value.
    Thanks.

  • LMS Discovery Issue

    We have a customer with an issue with LMS discovery.
    It will discover new devices but will fail to update them to the  DCR, because it does not match the credential set policy when the  credential set is defined by Device name and an SNMP OID is used.
    They have different devices and depending on the type  they use different credentials, Wireless AP’s for example use different  credentials to Routers.
    They can match on other fields to get a large amount of devices discovered however are still missing the majority.
    With little knowledge of this product, can anyone tell me if this is supported?
    Thanks
    Colin

    Hi Colin,
    Credentials set policy has nothing to do with the devices getting updated in DCR.
    while configuring the device discovery settings do not select any DCR credentilas set.
    One thing that you need to make sure is that devices are SNMP reachable and the Community string that you are using in the device disocvery settings should be CORRECT.
    Thanks
    Afroz

  • LMS 4.2 discovery failure

    Hi
    I have Cisco LMS 4.2 installed i was using SNMP V2c for polling my devices. After i turned on SNMPv3 all devices are reachable and even when i make credentials check it's ok, but the issue when i access any device from search pane it shows me in the collector status " Discovery failure"
    Steps i made to troubleshoot but not succeeded :
    1. Rediscover Devices
    2. Modify SNMP timeout & retry settings
    Devices: Catalyst 2960 , Catalyst 3560
    I've attached a snapshot of collector error
    Please help
    Thanks

    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 4.0 DFM issue

    Hi Experts, Recently I have installed LMS4.0 and we are facing issues with DFM. All devices are in DFM in known state. recently our link from HQ to branch went down and all branch devices were unreachable but we did not receive a sinlge alert from DFM and when I go to DFM to see if alerts are there but I dont see any alerts related to reachability..its only showing interface up/down message....even though i checked the availability report in HUM and uptime report in HUM it does not show there as well that device was not reachable or some downtime....
    attached is the version of applications installed in LMS4.0... Please help me to resolve this issue ?

    MDF isn't something that needs to be configured.  It is an architectural component of LMS.  The most likely reason you cannot create VLANs is that LMS does not know what your read-write community string is.  Discovery only populates DCR with the read-only string.  Go to Inventory > Add/Import/Manage Devices and edit the credentials for your switches.  Add the proper read-write community string, and then you should be able to configure the VLANs.

  • 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.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 4.2 Endhost Issue

    Hi,
    I have LMS 4.2 and switches 3560X, 3750X running IOS 15.0(1)SE3. I have enabled Energywise on them but the Energywise Dashboard is not showing some endhosts.
    When I enter to the switches and enter "sh energywise children" the endhosts are displayed, but on the Energywise Dashboard (Configure Energywise Attributes on Endpoints) it apperas as if the switch has no endhosts connected.
    I have erased and added the switches, verified the SNMP, SSH connection and check that cdp is enabled. On the Device Center, the IP Phones are shown as simple Endhosts and it is not possible to troubleshoot them through ping or traceroute. I'm not sure if it is a problem of the Energywise Work Center or the General LMS.
    Thanks for any help on this.

    Hi,
    I got exact the same problem with LMS 4.2.3.
    I can see ip phone when issue command "show energywise children".
    and I have added CUCM just like document describe.
    Then I manually trigger data collection and can see ip phone in report.
    But I can't see any endpoint on energywise page.
    Does any one know how to do?

  • LMS 4.2 discovery does not resolve hostname

    Hi,
    I'm trying automatic discovery with Ping on sweep module. I'm using the following configuration (you can also see it in the attached file):
    discovery module - ping on sweep
    global seed device - 192.168.6.35
    preferred DCR display name - DNS resolvable hostname
    The LMS server has its hostfile populated with the device ip/hostname that i'm testing with and resolving from the server works in both directions. Nevertheless, after discovery proccess is finished, the device is added in DCR with its IP address as dispaly name (screenshot in the attached file).
    I've tried the same method in CiscoWorks 4.0.1 and it works fine.
    I'm attaching the debug log files from discovery test. The LMS is running on Windows Server 2008 standard
    Please advice,

    Hi,
    I'm trying automatic discovery with Ping on sweep module. I'm using the following configuration (you can also see it in the attached file):
    discovery module - ping on sweep
    global seed device - 192.168.6.35
    preferred DCR display name - DNS resolvable hostname
    The LMS server has its hostfile populated with the device ip/hostname that i'm testing with and resolving from the server works in both directions. Nevertheless, after discovery proccess is finished, the device is added in DCR with its IP address as dispaly name (screenshot in the attached file).
    I've tried the same method in CiscoWorks 4.0.1 and it works fine.
    I'm attaching the debug log files from discovery test. The LMS is running on Windows Server 2008 standard
    Please advice,

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

  • SQL Discovery issue

    Hello everyone,
    I have different issue for SQL DB Engine discovery, for one of the Clustered SQL instance the discovery is not happening and I followed all the steps specified in SQL MP guide and below is the configuration made in general
    1) Installed the agent on cluster nodes and enabled the proxy for those agents.
    2) Configured the Run as account and liked them to specific SQL profiles as mentioned in SQL MP guide.
    3) Necessary permission for low privilege environment has been provided at SQL Nodes, cluster and Database.
    when logged on the cluster nodes to investigate further I see different versions of the SQL server is installed (2008 and 2012) on the same node and just wondering whether our SQL MP is capable of discovering these type of nodes?
    Any comments or any suggestion how to monitor this type of SQL environment. Thanks in Advance!
    Regards,
    Bhaskar K

    Hi,
    Based on my experience, the MP is able to discovery the two versions of SQL instances.
    System Center Management Pack for SQL Server
    https://www.microsoft.com/en-us/download/details.aspx?id=10631
    Are there any errors in the operations manager event log?
    Or any errors in the SQL Server error logs on the one of instance?
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Discovery Issues with OnCommand Plug-in 4.1 for SCOM 2012 R2

    I have a customer who has a NetApp cluster with FAS8040s running 8.2.1 in cluster-mode. The have SCOM 2012 R2 UR6 and the OnCommand 4.1 SCOM plug-ins. I can do an initial discovery of the cluster and it pulls back the SVM, but no other objects are discovered...no LIFs, no Nodes, no Volumes etc. I've been over the install doc many times and have not found where I might be doing something wrong. I've also searched on the interwebs and found a few suggestions, but none have changed the outcome. I've ensured the overrides are appropriate and to be sure its not a rights thing, I'm using "the" admin account. I see no indication of issues in:- The OnCommand Event Log- The OC.SCOM.logs (even in debug mode)- The SCOM task status Any help would be greatly appriciated.

    We are now using a Domain account and I still can't get any further. Below are the only indications of issues I can find. ******************************************************************************** Log Name:      Operations Manager
    Source:        Health Service Modules
    Date:          8/3/2015 6:27:00 PM
    Event ID:      22406
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SCOM_SERVER
    Description:
    The PowerShell script failed with below exception
    System.Management.Automation.MethodInvocationException: Exception calling "CreateDomain" with "3" argument(s): "The specified user does not have a valid profile.  Unable to load 'Microsoft.EnterpriseManagement.HealthService.Internal, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=121212121212121212'."At line:40 char:12
    +     return [AppDomain]::CreateDomain("OC.Cluster.OM.Powershell.NonDefaultAppDoma ...
    +            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
       at System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception exception, Type typeToThrow, String methodName, Int32 numArgs, MemberInfo memberInfo)
       at CallSite.Target(Closure , CallSite , RuntimeType , String , Object , Object )
       at System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3)
       at System.Management.Automation.Interpreter.DynamicInstruction`5.Run(InterpretedFrame frame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
    Script Name:    Monitoring.ps1
    One or more workflows were affected by this.  
    Workflow name: DataONTAP.Cluster.Monitoring.GetDataProtectionLagTimePerformanceData.Rule
    Instance name: Storage virtual machine SVM_NAME.
    Instance ID: {UUID_STRING}
    Management group: MG
    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          8/3/2015 6:28:00 PM
    Event ID:      4666
    Task Category: Application Generated
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:      SCOM_SERVER
    Description:
    An application attempted an operation:
    Subject:
        Client Name:        OC_ACTION_ACCOUNT
        Client Domain:        DOMAIN
        Client Context ID:    111122222333
    Object:
        Object Name:        IsUserAdministrator
        Scope Names:        50585907-7858-4488-ab9c-13e0eaac08be
    Application Information:
        Application Name:    Microsoft System Center
        Application Instance ID:    22350934216
    Access Request Information:
        Role:            Role
        Groups:            Group
        Operation Name:    User_IsAdministrator__Check (142)
    Log Name:      Security
    Source:        MOMSDK Service Security
    Date:          8/3/2015 6:28:00 PM
    Event ID:      26401
    Task Category: (3)
    Level:         Information
    Keywords:      Classic,Audit Failure
    User:          DOMAIN\OC_ACTION_ACCOUNT
    Computer:      SCOM_SERVER
    Description:
    Data access operation: User_IsAdministrator__Check
    Data access method: IsUserAdministrator
    User name: DOMAIN\OC_ACTION_ACCOUNT
    sessionId: uuid:UUID_STRING;id=NUM
    ********************************************************************************

  • Multiple primary site - Discovery issue

    Hi,
    I am working on a scenario where there is 1 CAS and 3 Primary sites(PS1,PS2,PS3). At PS1 site, Active directory system Discovery is only configured and all the OU for all the sites are added. On the other two Primary sites this discovery was not configured.
    Now I wanted to ask is there any issue due to this , or should I have to configure this discovery on both sites??
    Thanks
    Pallavi

    no, you can still control that. Site Assignment is either based on an AD Query or you hard coding the site code during the install process. Client deployment depends on the method, in this process content boundary Groups and DP's are being used.
    Kent Agerlund | My blogs: blog.coretech.dk/kea and
    SCUG.dk/ | Twitter:
    @Agerlund | Linkedin: Kent Agerlund |
    Mastering ConfigMgr 2012 The Fundamentals

  • Ciscoworks LMS 3.2 DCR issue

    Dear Cisco,
    We are still encountering problems when incorporating a new device type (Cisco Catalyst 3560C-8PC-S Switch) into Ciscoworks common services.
    Yesterday, we installed the latest DeviceData.xml 3.6) file, and now the OID 1.3.6.1.4.1.9.1.1466 is in the file !! nevertheless the device stays in the unknown section. When we ask device identity in DRM the device type is known, but it is not classified under device type groups.
    Any ideas how to tackle this issue ?
    Many thanks!
    Lieven Stubbe
    Belgian Railways

    I hope you're running LMS 3.2.1. If not, please update. Also, please check if you're using the latest mdf package for Common Services. Common Services brings the latest matadata for the devices.
    This seems to be strange that even after the device has an identity/icon selected it still shows under unknown.
    As a test, if you try to add any device manually with any test ip, say - 10.10.10.1 and use device type as - Cisco Catalyst 3560C-8PC-S Switch and see if that shows under unknown? This is just to verify if it is some specific issue with this device in DB.
    -Thanks
    Vinod
    **Encourage Contributors. RATE Them.**

Maybe you are looking for