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.

Similar Messages

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

  • WVC80N - Internet Gateway UPnP discovery failure message \ unable to view over the internet

    I have the WVC80N.  I recently got the new Comcast modem \ wifi but the Wifi is junk and had a lot of problems (loss connection, range etc) so I had Comcast "bridge" it so I just use my old wifi (LinkSys E1200).   I have TZO to handle remote viewing.  Everything was working great for about two weeks and we had a power outage.  Since then, I have been getting UPnP discovery message (in the status tab of the WVC80N camera site) and I am unable to view over the internet.  I get a 502 error usually but today I got extra info: "The socket connection to www.dfgehring.mylinksyscam.com failed.
    ErrorCode: 10060.  A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."
    I had Comcast do a "repair / reset" transmission to the modem and still get the problem.
    I found these step on the forum:
      1. Home Wirless Rounter administration page, find the UnPn settings and Turn off UnPn and save it. Wait for atleast 30 sec  and go the same page and Turn it back on.
      2. On your wireless camera Adminstraion page, go to "Options" and find the UnPn if it is already disabled go ahead and "enable" it also "enable" the "Alternate web connection" and save it. If it was already enable please disable it save the settings and enable back on.
     The above 2 steps resolved my issue and I could able to view my camera from outside of my home network.
    Still no luck.  Tried it several times.
    Could the power outage reset something on the modem or router to change this? 
    Thanks
    Darren

    That's what I thought. The power outage may have set the modem, router or camera settings back to factory defaults causing it to loose connection. First thing first, call comcast and check if the modem is still on bridge mode. The modem may have been set back to a modem/router mode due to power outage.
    You may test if the remote access is properly set up in the network by going to http://ping.eu. In that site, you will see your internet ip address, take note of that. Click on port check, enter your internet ip address and the port number you used in the alternate web access port then click Go. If it says closed, there something wrong in the settings of either the router or camera. In that case, I suggest you reset the router and camera and then reconfigure them.
    I found these articles online which could help you reconfigure your router and camera settings:
    How to set up your router
    How to set up router wireless setting
    Connecting camera to wireless network
    How to set up remote access on linksys camera
    How to set up TZO on the linksys camera
    Hope these helps.

  • Device discovery failure in ANM

    Anyone familiar with this error:
    Device discovery failed: For input string:"1/0"
    I am receiving it when attempting to import a new chassis into ANM. All of the credentials are correct.

    Number one error with ANM 1.1 installs has been not having SSHv2 configured on the Supervisor (and the subinterfaces ANM may use to reach that module). Since ANM is managing the ACE, which in turn is often managing e-commerce applications with SSL and SSH connections, not having the control interfaces at the same level of security was undersirable.
    ANM 1.2 is being updated to allow the operator to start off without SSHv2, though this will be strongly discouraged for production operations.
    DK

  • 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

  • LMS 4.0 Discovery,

    Hello,
    I have enabled PING and CDP for discovery, I ran a discovery and found swithes through CDP but i can't find firewall and branch routers through ICMP the seed devices for icmp module is the first devices (switch) which i added manually and it is seen in  DCR. Then i thought of doing alternate i.e.For firewall and branch Routers i added them manually they are successfully added but they are seen found by system not by icmp. WHY ?????????????????
    All devices are pingable and all devices are reacheable through SNMP,
    Thanks

    The Discovery ping sweep module will do unicast pings of a subnet (based on your address ranges), then contact each reachable node with SNMP.  Those nodes that are SNMP reachable are added to DCR.  When you say you add them manually and it works, what exactly do you mean?  You can add any device to DCR manually, and it should succeed.  DCR does not contact devices.  The real test is if you can run an inventory report on the devices and see data.  If that works, then Discovery must not be able to ping the devices (or they are not responding quickly enough).
    See https://supportforums.cisco.com/docs/DOC-9005#Troubleshooting_CSDiscovery .  If you enable debugging for the Ping Sweep and System modules, the ngdiscovery.log should indicate why the firewalls are not being discoverd.

  • Oracle VM 3 : Server Discovery Failure. Any ideas?

    Hi.
    I've installed OVM 3.0.1 Server and Manager on two machines. Both machines are pinging as expected. Everything seemed to go smooth during the install.
    As soon as I try to discover the OVM server from the OVM Manager, as described here (http://download.oracle.com/docs/cd/E20065_01/doc.30/e18549/qstart.htm#CACJEGHD), it fails with the error posted below.
    Any clues are to what is going on would be appreciated.
    Cheers
    Tim...
    Job Construction Phase
    begin()
    Appended operation 'Discover Manager Server Discover' to object 'OVM Foundry : Discover Manager'.
    commit()
    Completed Step: COMMIT
    Objects and Operations
    Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
    Operation: Discover Manager Server Discover
    Job Running Phase at 22:29 on Tue, Aug 30, 2011
    Job Participants: []
    Actioner
    Starting operation 'Discover Manager Server Discover' on object 'OVM Foundry : Discover Manager'
    Setting Context to model only in job with id=1314739747770
    Operation 'NTP Service Configure' in non-job running context, not adding it to object 'a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27'.
    Operation 'NTP Service Configure' in non-job running context, not adding it to object 'a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27'.
    Operation 'NTP Service Configure' in non-job running context, not adding it to object 'a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27'.
    Operation 'NTP Service Configure' in non-job running context, not adding it to object 'a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27'.
    Operation 'Server Set Statistic Interval' in non-job running context, not adding it to object 'a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27'.
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6055E Discover target: ovm-server1.localdomain, Discover failed with error: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.RangeCheck(ArrayList.java:547)
    at java.util.ArrayList.get(ArrayList.java:322)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.processSMBIOSData(ServerHardwareDiscoverHandler.java:482)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.processProcessorData(ServerHardwareDiscoverHandler.java:591)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.process(ServerHardwareDiscoverHandler.java:338)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:55)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:433)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:418)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:403)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:211)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Tue Aug 30 22:29:10 BST 2011
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:448)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:418)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:403)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:211)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    FailedOperationCleanup
    Starting failed operation 'Discover Manager Server Discover' cleanup on object 'OVM Foundry : Discover Manager'
    Complete rollback operation 'Discover Manager Server Discover' completed with direction=OVM Foundry : Discover Manager
    Rollbacker
    Objects To Be Rolled Back
    Object (CREATED): [Processor] Processor (1) in a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27
    Object (CREATED): [XenHypervisor] Hypervisor in a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27
    Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
    Object (CREATED): [Server] a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27 (ovm-server1.localdomain)
    Object (CREATED): [LocalStorageInitiator] storage.LocalStorageInitiator in a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27
    Object (CREATED): [InternalPort] network.InternalPort (1) in a7:9e:51:d0:7b:f1:44:c1:90:f5:60:d2:af:62:be:27 (network.InternalPort (1) in ovm-server1.localdomain)
    Completed Step: ROLLBACK
    Job failed commit (internal) due to OVMAPI_6055E Discover target: ovm-server1.localdomain, Discover failed with error: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.RangeCheck(ArrayList.java:547)
    at java.util.ArrayList.get(ArrayList.java:322)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.processSMBIOSData(ServerHardwareDiscoverHandler.java:482)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.processProcessorData(ServerHardwareDiscoverHandler.java:591)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.process(ServerHardwareDiscoverHandler.java:338)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:55)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:433)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:418)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:403)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:211)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Tue Aug 30 22:29:10 BST 2011
    com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6055E Discover target: ovm-server1.localdomain, Discover failed with error: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.RangeCheck(ArrayList.java:547)
    at java.util.ArrayList.get(ArrayList.java:322)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.processSMBIOSData(ServerHardwareDiscoverHandler.java:482)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.processProcessorData(ServerHardwareDiscoverHandler.java:591)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.process(ServerHardwareDiscoverHandler.java:338)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:55)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:433)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:418)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:403)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:211)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Tue Aug 30 22:29:10 BST 2011
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:448)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:418)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:403)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at sun.reflect.GeneratedMethodAccessor657.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:211)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    End of Job
    OK
    -----------------------------------------------------------------------------------------------------------------------------------

    Hello,
    TimHall wrote:
    I've installed OVM 3.0.1 Server and Manager on two machines. Both machines are pinging as expected. Everything seemed to go smooth during the install.
    Tue Aug 30 22:29:10 BST 2011
    com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6055E Discover target: ovm-server1.localdomain, Discover failed with error: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.RangeCheck(ArrayList.java:547)By the error displayed here (IndexOutOfBoundsException) it seem that you try to install the Oracle VM Server 3.0.1 inside of VirtualBox or another virtualization tool. Maybe this is not the case, but if you did this then let me tell you that this is not posible.
    This thread talk about this problem Re: OVMAPI_6055E Discover target: myfancyovmserver (Oracle VM Manager 3.0)
    Please let us know if this was not your scenario.
    Harim Márquez

  • OVM 3.0.2 - Server discovery failure

    Has anybody seen this error when adding OV server to manager? Thanks
    Job Construction Phase
    begin()
    Appended operation 'Discover Manager Server Discover' to object 'OVM Foundry : Discover Manager'.
    commit()
    Completed Step: COMMIT
    Objects and Operations
    Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
    Operation: Discover Manager Server Discover
    Job Running Phase at 03:53 on Thu, Nov 24, 2011
    Job Participants: []
    Actioner
    Starting operation 'Discover Manager Server Discover' on object 'OVM Foundry : Discover Manager'
    Setting Context to model only in job with id=1322128407284
    Operation 'NTP Service Configure' in non-job running context, not adding it to object '2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1'.
    Operation 'NTP Service Configure' in non-job running context, not adding it to object '2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1'.
    Operation 'Server Set Statistic Interval' in non-job running context, not adding it to object '2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1'.
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: discover_hardware to server: 2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1 failed. OVMAPI_4004E Server Failed Command: discover_hardware, Status:
    Thu Nov 24 03:53:30 CST 2011
    Thu Nov 24 03:53:30 CST 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:474)
    at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:426)
    at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:368)
    at com.oracle.ovm.mgr.action.ActionEngine.sendDiscoverCommand(ActionEngine.java:291)
    at com.oracle.ovm.mgr.action.ServerAction.getHardwareInfo(ServerAction.java:101)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:316)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:46)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:50)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:435)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:420)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:405)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:223)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: discover_hardware, Status:
    Thu Nov 24 03:53:30 CST 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:752)
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:470)
    ... 30 more
    FailedOperationCleanup
    Starting failed operation 'Discover Manager Server Discover' cleanup on object 'OVM Foundry : Discover Manager'
    Complete rollback operation 'Discover Manager Server Discover' completed with direction=OVM Foundry : Discover Manager
    Rollbacker
    Objects To Be Rolled Back
    Object (CREATED): [InternalPort] network.InternalPort (1) in 2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1
    Object (CREATED): [XenHypervisor] Hypervisor in 2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1
    Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
    Object (CREATED): [Server] 2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1
    Object (CREATED): [LocalStorageInitiator] storage.LocalStorageInitiator in 2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1
    Completed Step: ROLLBACK
    Job failed commit (internal) due to OVMAPI_4010E Attempt to send command: discover_hardware to server: 2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1 failed. OVMAPI_4004E Server Failed Command: discover_hardware, Status:
    Thu Nov 24 03:53:30 CST 2011
    Thu Nov 24 03:53:30 CST 2011
    com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: discover_hardware to server: 2d:c7:6f:cf:ac:17:36:13:b0:b4:a3:a4:f2:db:f4:a1 failed. OVMAPI_4004E Server Failed Command: discover_hardware, Status:
    Thu Nov 24 03:53:30 CST 2011
    Thu Nov 24 03:53:30 CST 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:474)
    at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:426)
    at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:368)
    at com.oracle.ovm.mgr.action.ActionEngine.sendDiscoverCommand(ActionEngine.java:291)
    at com.oracle.ovm.mgr.action.ServerAction.getHardwareInfo(ServerAction.java:101)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:316)
    at com.oracle.ovm.mgr.discover.ovm.ServerHardwareDiscoverHandler.query(ServerHardwareDiscoverHandler.java:46)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:50)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:435)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:420)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:405)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:366)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:353)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:265)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:191)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:257)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1019)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:223)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:395)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:453)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: discover_hardware, Status:
    Thu Nov 24 03:53:30 CST 2011
    at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:752)
    at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:470)
    ... 30 more
    End of Job

    890391 wrote:
    Has anybody seen this error when adding OV server to manager? ThanksWhat hardware are you running Oracle VM Server on? Are there any firewalls between the Server and Oracle VM Manager?

  • Personal Hotspot discovery failure

    My iPhone 5 on ios 6.1.2 shows Personal Hotspot is now discoverable, but it does not show up on my iPad 2 also on ios 6.1.2.  I have previously used my iPhone to share Internet to my iPad. This just happened out of nowhere. Help anyone?

    Happens to me all the time when I try to connect my old iphone 4 to my iphone 5.
    If I turn hotspot off and on again, wait 30 seconds it will usually show up and connect

  • Device Collection Failed ON LMS4.1

    Dear all,
                  I add 4510 and 4507 in zhe  LMS ,but fault discovery failure.
                 Can  somebody help me
               And  the job Inventory Collection also failed on 4500 and nexus ,Error message as shown below:
    Thank you

    Try to increase the SNMP timeout to 50-100 and try to run the inventory once. Also try to re-add the device once after increasing timeout.
    There is no known issue for 45xx for invenotry as such, it should be fixed. If it still fails, you need to enable debug for ICServer and share NMSROOT/log/IC_Server.log.
    -Thank

  • Cisco Prime LMS device unreachable dont know why

    Hi
    Currently running Cisco Prime LMS v4.2
    I am trying to get some Nexus 7K Switches to work and become reachable.
    They are running  kickstart: version 6.2(2)
                                 system:    version 6.2(2)
    Now as far as I can see i have 2 identical switches but one is unreachable and the other is reachable.
    When i use my snmp tester they both work with the correct V3 auth/priv passwords and the correct ssh
    works on the switches.
    When i go to monitor/Troubleshooting Tools/Troubleshooting Workflows
    Then for the non working one  i get the following fails.... 
    Device Information   Device availability  x
    Collector Status
    Data Collection  Failure
    User Tracking    Failure
    Fault discovery   Failure
    On the working one The above all are a Success.
    Also
    Reachability Details
    Both ping and traceroute work fine on both switches 
    For the life of me I cannot see any difference in the configuration of the two devices.
    Has anyone come across this before ?
    I have attached a copy of the snmp config.
    Thanks
    Steve

    What is the server OS? Windows/Linux or Unix?
    From the server to ping and poll device for SNMP and see if both device works fine?
    SNMP walk is available under :
    Windows : NMSROOT/objects/jt/bin
    Linux/unnix/: /opt/SCOpx/objects/jt/bin
    Example:
    NSROOT/objects/jt/bin/snmpwalk -v2c -c public <ip_add> <OID>
    Try to configure the problematic device for SNMP v2 and try to add it from there and test if it works fine.
    -Thanks
    Vinod

  • CIFS accelerator keepalive failure

    Software Release 4.4.5
    WAVE-294-K9
    Alert:
    cceAlarmHistModuleId= 1000  cceAlarmHistCategory= 3  cceAlarmHistInfo= Raise-Alarm: CIFS accelerator keepalive failure.   cceAlarmHistTimeStamp= 3539553200
    I got the following alert.
    Does anyone know where I can find the log files or the CIFs accelerator keepalive failure counter?
    I wanted to know the best way to clear the counter statistics and make sure that if this hits up again I can at least get a better
    idea of how frequent it is happening.
    I ran the following command and was curious if the "sessions timeout" is related to this keepalive failure?
    show statistics accelerator cifs detail
    CIFS:
    Global Statistics
    Time Accelerator was started: Wed Sep 25 08:51:51 2013
    Time Statistics were Last Reset/Cleared: Wed Sep 25 08:51:51 2013
    Total Handled Connections: 15293
    Total Optimized Connections: 166
    Total Connections Handed-off with Compression Policies Unchanged: 13638
    Total Dropped Connections: 0
    Current Active Connections: 0
    Current Pending Connections: 0
    Maximum Active Connections: 9
    Number of local reply generating requests: 166596
    Number of remote reply generating requests: 217438
    The Average time to generate a local reply (msec): 4
    Average time to receive remote reply (ms): 92
    Policy Engine Statistics
    Session timeouts: 13, Total timeouts: 121
    Last keepalive received 00.0 Secs ago
    Last registration occurred 19:03:18:36.6 Days:Hours:Mins:Secs ago
    Hits: 1218122, Update Released: 142074
    Active Connections: 18, Completed Connections: 821832
    Drops: 0, Pre-Resource Counter: 0
    Rejected Connection Counts Due To: (Total: 254198)
    Not Registered : 3, Keepalive Timeout : 65
    No License : 0, Load Level : 0
    Connection Limit : 0, Rate Limit : 0
    Minimum TFO : 254130, Resource Manager : 0
    Global Config : 0, TFO Limit : 0
    Server-Side : 0, DM Deny : 0
    No DM Accept : 0
    Auto-Discovery Statistics
    Total Connections queued for accept: 487511
    Connections queuing failures: 0
    Socket pairs queued for accept: 487511
    Socket pairs queuing failures: 0
    AO discovery successful: 741192
    AO discovery failure: 6

    Hi,
    The accelerator is failing to perform a wellness update within the allotted time. That is
    why we see keepalive failures. The implications are that some connections may not be
    getting optimized properly by the AO, and thus optimization performance may be reduced.
    I don't think there is any counter for number of keep alive failure messages you get but you can
    see if Keepalive Timeout counter is increasing.
    You can find this counter under "policy engine statistics".
    Keepalive Timeout : 65--->You can check if this value is increasing during the time you get this message.
    Regards,
    Kanwal

Maybe you are looking for

  • Error while creating sales order thru IDoc

    Hi,   While using FM IDOC_WRITE_AND_START_INBOUND, I am getting an error 'Customer not found with DUNS number from IDoc' and the application document is nor posted. I am passing valid customers in the ship to party and sold to party segments but stil

  • Color Range command in Photoshop CS6 13.0.4 no longer works after update

    I just updated to 13.0.4 at the end of last week.  Today I went to use the Color Range command and it will not select any colors.  The Eyedropper tool works fine.  Adjusting the fuzziness and other options doesn't make a difference.  Nor does selecti

  • Select option restriction to particular rows

    Dear Gurus, I have searched the form for this but couldn't find the particular solution. my scenario is i need to enter only 5 plants in the select options it should not exceed  it, for this i have done  like select options :S_PLANT FOR  G_PLANT NO I

  • I need to re-download Aperture

    ...But all I can find are updates to 3.0. I had to do a clean install of Mavericks, so I'm having to redownload a lot of software.  All of the Aperture updates require a base installation of 3.0 but I can't find it anywhere. I defintitely don't want

  • BB Q10 empty message through Groupwise Mobility Service

    Hello forum members! We have an issue with an smartphone BlackBerry Q10 (OS version 10.1.0.4181) using Groupwise Mobility Service version 2.0.1 revision 53, installed on Suse Linux Enterprise Server 11 patchlevel 3. When the user replies to an extern