IDS discovery fails

I have a small number of IDS's that fail discovery.
The fail description is:
"Fail to discover policy for signatureDefinition component. Detail: Error encountered while generating
policy IpsSignaturefor instance sig0."
I have scaled down the polices to discover from the default ones of Inventory/ Platform settings/ and IPS
and still no luck. Devices have also been rebooted multiple times with no luck. Any quick fix or is a reimage in
order?
Thanks...

I think you are hitting a bug
may be
CSCtg23806
CSM discovery fail when Signature ID 50000 or later is modified
Please open a case with cisco TAC to get the right support.
Sachin

Similar Messages

Untrusted Forest Discovery failed

I'm having a issue with remote untrusted forest. Forest Discovery fails, but I can publish site server information to this forest.
ERROR: [ForestDiscoveryAgent]: Failed to connect to forest domain.com. This can be because of disjoint DNS namespaces, network connectivity or server availibility issue. Error Information The specified forest does not exist or cannot be contacted.
Entering function ReportForestConnectionFailureStatusMessage()
Calling ReportStatus, keys= SMS_AD_FOREST_DISCOVERY_MANAGER, -2147474744, 2
I have configured conditional forwarders between forests and name resolution works. There shouldn't be any firewall issues either and I tested SRV records via nslookup with this method
Type nslookup, and then press ENTER.
Type set type=all, and then press ENTER.
Type _ldap._tcp.dc._msdcs.<var>Domain_Name</var>, where <var>Domain_Name</var> is the name of your domain, and then press ENTER.
Nslookup lists correct domain controllers from remote forest.
Any ideas what could be causing this? I think it's AD related problem.

LDAP://DCNAME.domain.com/OU=Computers,DC=domain,DC=com
I tested this last week and this works. Now I can discover computer objects from untrusted forest. There must be something wrong with the ad/dns infrastructure becasue
normally you dont need to specify domain controller directly because it should find it with srvlookup.

Discovery Failed: VNI-4026: Discovery failed: Error while transfer**URGENT*

Hi Fellows,
I had a server with one database only. It was discovered and running fine in OEM using Oracle Management Server. I created one more database in this server and created a service. Now I can see this database when I use OEM with stand alone option. But when I try OEM Oracle Management Server and I try to discover new database, it gives me the following error:
Discovery Failed: VNI-4026: Discovery failed: Error while transferring services.ora
I ping agent and it is okay. I checked the status of Listner which is fine too. If listner is not fine I should not be able to connect.
Note: the database which I already had on the server is working absolutely fine.
Any help will be highly appreciated.
Thanks
Ghulam Mustafa Butt

Hi,
I was out of office yesterday. Sorry for the link.
Here is the content of that link:
goal: How to confirm DNS hostname resolution
fact: Generic Platform
fix:
1. Find the hostname of the box:
     % hostname
2. Perform nslookup on hostname
     % nslookup <hostname>
     Type in the hostname exactly as it is displayed in step 1
     nslookup returns 4 or more lines of information in this format:
          Server: <hostname.domain of the dns server>
          Address: <ip address for the dns server>
          Name: <hostname.domain for this box>
          Address: <ip address for this box>
3. Perform nslookup on host IP address
     % nslookup <ip addr>
     Use the ip address found on the 4th line in step 2
     Exactly the same lines of info as in step 2 should be returned
4. Perform nslookup on host name of target system
     % nslookup <hostname>
     Exactly the same 4 lines should be returned as though nslookup were done on
the other box
5. Perform nslookup on IP address of target system
     % nslookup <ip addr>
     Exactly the same 4 lines should be returned as though nslookup were done on
the other box
NOTE ROLE:
The Network Administrator is responsible for adding servers to DNS

Device discovery failed in ANM

Hi,
I've got the following error message when I want to import a 6506 in 12.2(33)SXI2 with an ACE module.
I've tried in ANM 2.2 and 3.0 = same problem.
Can someone help me ?
Device discovery failed: Exception occured for model:VlanModel
Exception occured for model:InterfaceModel
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort.
Thanks,
Greg.

Hi Greg,
The error message you are seeing is likely triggered by some un-expected configuration on the cat6k.
It is likely your cat6k configuration has an interface defined as a switchport which has a subinterface defined on it.
This is usually not allowed on most sup versions that we have seen and hence is not modeled/ cannot be discovered in ANM.
We have bug id CSCtd94658 opened for this issue.
You could try to have your customer remove the subinterface indicated above and then try the import into ANM.
Also, they could maybe add back that interface if really required after the initial import.
Since Cat6k configs are not auto-sync'ed in ANM, they will be okay until they do a manual sync.
This workaround in also documented in the release notes of CSCtd94658.
Thanks
Sujatha
========

WCF application discovery failed

Hi,
I am using SCOM 2012 R2.
APM was configured.
The following events are raising for APM (only for 3 servers):
Description:
WCF application discovery failed because of the following exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Mom.Common, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
The system cannot find the file specified.
File name: 'Microsoft.Mom.Common, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at Microsoft.EnterpriseManagement.Modules.Apm.Discovery.Wcf.IIS2008WcfApplication.GetSCOMDiscoveryClassInstance(String computerName)
at Microsoft.EnterpriseManagement.Modules.Apm.Discovery.Wcf.WcfApplicationCollection.GetDiscoveryData(String computerName, DiscoverySourceType type, Guid discoverySourceId, Guid discoverySourceMEId)
at Microsoft.EnterpriseManagement.Modules.Apm.Discovery.Wcf.WcfDiscoveryProbe.ProcessDataItem(DataItemBase dataItem, DataItemAcknowledgementCallback acknowledgedCallback, Object acknowledgedState, DataItemProcessingCompleteCallback completionCallback, Object
completionState
I searched the web, but nothing about APM.
Thanks in advance!

Hello SCCMadmin09,
Is there anything special about those failing agents? E.g. version of the agents is a bit different from the others?
I remember something about removing dependency on Microsoft.Mom.Common a while back, so if a workflow from old version tries to execute on the box with new version without this dependency - it'll fail.
You can check the presence of this file in C:\Windows\Assembly and in C:\Program Files\Microsoft Monitoring Agent - if it's not there, then agent is of a version where it was already removed.
If the issues is indeed in the versioning - then the fix should be a matter of a proper update of Agent-SCOM combination and/or maybe some MPs.
That's all theories, of course... I hope this helps at least a bit.
Dmitry Matveev

Discovery Failed: VD-4564 error

Hi,
I have installed Oracle 9i Server in my machine. While installing, I checked the option to create a database using database configuration assistant, and to create a separate new repository for management server.
The installations were successful, and here are the database details:
=== Database created using database configuration assistant details ===
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=incdw2k062)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ORCL)))
=== Management Repository database details ===
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=incdw2k062)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=OEMREP.systechin.com))
The problem i am facing is described here:
I was able to view both the databases in the Oracle Enterprise Manager Console, Standalone.
However, I am not able to view the same in the Oracle Enterprise Manager Console, Administrator:SYSMAN, Management Server:incdw2k062.systechin.com
I tried to add the database through discover node option. But, it failed. I am getting the error: "Discovery Failed: VD-4564"
Please help me in resolving this issue. I am a newbie to ORACLE.
Thanks and Regards,
Deepak Natarajan.

Hi,
I couldn't get it. I am not pretty sure of how I configured it.
All I know is, it took my system name in the network as my host id. Once again I am giving the configuration details below:
=== Database created using database configuration assistant details ===
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=incdw2k062)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ORCL)))
=== Management Repository database details ===
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=incdw2k062)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=OEMREP.systechin.com))
Please tell me in steps to resolve the problem.
Regards,
Deepak Natarajan.

Active Directory service discovery failed

Hi forum user,
I have integrated my SGD with AD.
I saw the following error in jserver log file:
# more jserver2698_error.log
2007/07/24 15:25:22.626 (pid 2698) server/ldap/error #1185261922626
Sun Secure Global Desktop Software (4.31) ERROR:
Active Directory service discovery failed: Failed to find any valid Site objects.
Looking up Global Catalog DNS name: gc.tcp.telbru.com.bn. - HIT
Looking for GC on server: Active Directory:ts1.telbru.com.bn:/172.25.11.96:3268:Up - HIT
Checking for CN=Configuration: DC=telbru,DC=com,DC=bn - MISS
Checking for CN=Configuration: CN=Configuration,DC=telbru,DC=com,DC=bn - HIT
Looking up domain root context: DC=telbru,DC=com,DC=bn - HIT
Looking up site context: CN=Sites,CN=Configuration
Searching for sites: (&(objectClass=site)(siteObjectBL=*)) - HIT
Looking up addresses for peer DNS: portal.telbru.com.bn - HIT
Failed to discover Active Directory Site, Domain and server data.
This might mean LDAP users cannot log in.
Make sure the DNS server contains the Active Directory service
records for the forest. Make sure a Global Catalog server is available.
Why the error occurred ?
What is the resolution to this error ?
Appreciate any help. Thanks.

This error message is telling you that SGD failed to find any site objects in your AD tree. This should not stop users from logging in, it will just mean that SGD will not be able to work out which AD site is local to the SGD server.
If you are not using sites in your AD setup, then you do not need to worry about this.
Hope this helps,
DD

"Discovery failed to null" error message when starting up Oracle Management

hey folks,
i am trying to get the Oracle Enterprise Manager to work and i get an error message. Here is what i've done so far.
1. Installed Oracle service. It is started (under Start>...>Services it says "Started").
2. Created a Listener for the Oracle service via Net8 Assistant. It is also started.
3. Created a Service Name in Net8 Assistant listening to the above mentioned Listener. When i tested it, it said "test successfull".
4. Created an ODBC Data Source via the ODBC Administrator.
5. Created a repository for the Oracle service using the Enterprise Configuration Assistant.
so now i am trying to start the Oracle Management Server and when i click on "start service", a command window opens and the following is on it:
"OEMCTRL for Windows NT: Version 2.1.0.1.0
Copyright (c) 1998, 1999 Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...VXA-3008 : Starting OMS Services, Wait.
[xxxxxxxxxx.ou.edu-DiscoveryThread][2003-11-20:11:9:26:765] Discovery of xxxxxxxxxxxx.ou.edu failed due to null
The OMS is now started and ready."
where xxxxxxxxxxxxxxx is the name of my machine. The status for the OracleManagementServer under Services is "Started", but when i go to the Oracle Enterprise Manager console and try to log in, it just locks up.
any ideas?
Thanks.

if you are getting connection to the OEM you have to choose if you get connect in STANDALONE MODE or OMS MODE.
if you choose the first you have to get connection as a
user that has granted sysdba role
if you choose the second you have to get connection as a
user called sysman or another user stablished for the repository.
Joel P�rez

Exadata Discovery - Failed to launch process: Algorithm negotiation fail

Trying to discover an Exadata box. We’ve installed the latest EM (BP1) and deployed the agents successfully to the compute nodes. When we come to use the discovery wizard, it fails on the monitoring credential page. We input the cell root passwords and click test connection which fails with the error messages:
sxa1cel01 - Failed to launch process: Algorithm negotiation fail
sxa1cel02 - Failed to launch process: Algorithm negotiation fail
sxa1cel03 - Failed to launch process: Algorithm negotiation fail
Not much info available about this. Looking at the agent log just shows the same error message coupled with a Java error and not much else. Googling around, it seems it might be something to do with JSch.
Any help or pointers would be greatly appreciated.

The root cause of this issue are additional security changes made in the latest Exadata release. Enterprise Manager Cloud Control 12c will be moving to this standard as well in an upcoming patchset.
Workaround to the problem:
The current workaround for existing installations is to add the ciphers listed in the step below back to the sshd_config files on all cells and compute nodes if the customer is running Exadata Storage Server version 11.2.3.1.0. The work around steps for this situation are listed below. For each storage cell and compute node, edit the /etc/ssh/sshd_config file as listed below:
1) ssh to the cell node as root
2) cd /etc/ssh/
3) back up sshd_config
4) add aes128-cbc,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc,blowfish-cbc to the Cipher line in sshd_config
5) Restart the ssh daemon (as the root user):
# service sshd restart
Edited by: user484103 on Apr 23, 2012 11:45 PM
Edited by: user484103 on Apr 23, 2012 11:50 PM

Server discovery failed

when I tried to install new UCS B200M4 the discovery of the blades failed as shown in the attached images
but when inserting B200M3 it discovered automatically in the chassis as in fig. error 3

Seems like you are not running 2.2.3a (or later) for UCSM The release notes: http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/ucs_2_2_rn.html#pgfId-238846 under "New Hardware Features in Release 2.2" shows that is the version that will make UCSM recognize the new M4 servers.
If this is the answer to your issue, please mark it as such for future users to find their answer as well.
-Kenny

SCOM Linux discovery failed with "The user name or password is incorrect" error

Hi every one .
In our test environment when I want to discover a new linux computer system , discovery process fails with this error message :
Unexpected DiscoveryResult.ErrorData type. Please file bug report.
ErrorData: Microsoft.SystemCenter.CrossPlatform.ClientLibrary.Common.SDKAbstraction.TaskInvocationException
Task invocation failed with error code 1326. Error message was: The user name or password is incorrect.
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.SystemCenter.CrossPlatform.ClientActions.DefaultDiscovery.InvokeWorkflow(IManagedObject managementActionPoint, DiscoveryTargetEndpoint criteria, IInstallableAgents installableAgents)
But I m sure that this username and password is correct and I can logon to this computer with this credential.
how do I find root cause of this issue ?

I have been enabled logging before doscovery process .
in temp directory :
0: 02/10/15 20:03:22 : Enter SCXNameResolverProbe constructor
0: 02/10/15 20:03:22 : Leave SCXNameResolverProbe constructor
1: 02/10/15 20:03:22 : Enter SCXNameResolverProbe::DoInit
1: 02/10/15 20:03:22 : XML_INIT_CALL
1: 02/10/15 20:03:22 : Check WSAStartup
1: 02/10/15 20:03:22 : Exit SCXNameResolverProbe::DoInit
2: 02/10/15 20:03:22 : Enter SCXNameResolverProbe::DoProcess()
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess passed initial arguments checking
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess input: 192.168.7.62
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess - Input is an IP-address
3: 02/10/15 20:03:22 : Enter SCXNameResolverProbe::GetName(): 192.168.7.62
3: 02/10/15 20:03:22 : Resolve IPv4 address to host name
3: 02/10/15 20:03:22 : Leave SCXNameResolverProbe::GetName(): SUSE11
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns name: SUSE11
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns ip: 192.168.7.62
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns errorcode: 0
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns errortext:
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns xml: <NetworkName>SUSE11</NetworkName><IPAddress>192.168.7.62</IPAddress><StatusCode>0</StatusCode><StatusMessage></StatusMessage>
2: 02/10/15 20:03:22 : Enter initDataHolder
2: 02/10/15 20:03:22 : Enter initDataType
2: 02/10/15 20:03:22 : initDataType initializing output datatype
2: 02/10/15 20:03:22 : Leave initDataType
2: 02/10/15 20:03:22 : Leave initDataHolder
2: 02/10/15 20:03:22 : Leave SCXNameResolverProbe::DoProcess
4: 02/10/15 20:03:22 : Enter SCXNameResolverProbe destructor
4: 02/10/15 20:03:22 : SCXNameResolverProbe destructor - FreeLibrary failed: 0
4: 02/10/15 20:03:22 : Leave SCXNameResolverProbe destructor
with debug viewer I have this message after discovery :
[7448] A management object with display name SUSE11 could not be found.

Active Directory Discovery fails to bind to OU

I am continuously receiving the following error:
Active Directory System Discovery Agent failed to bind to container
LDAP://OU=DOMAIN CONTROLLERS,DC=MYDOMAIN,DC=COM. Error: The specified directory service attribute or value does not exist.
Not sure what to check at this point. I have checked permissions on the OU, Server has read permissions. Here is screenshot of properties:

Have you tried discovery of the entire forest, not just a single OU? If that works then it has to be permissions to that OU. If it fails, then it would be no permissions to the forest.
I'd also consider using a user account (just as a test). Personally I've always used the site server computer account, but you could also try a user account for this to ensure that it's not something else.
Wally Mead

Target Auto Discovery fails

Hi,
I have EMC12 installed on WinServer2008 R2 SP1. Cygwin ssh deamon started and configured. Agent is running on local account (LA) with administrative privileges and additional setting configured according to docs. OMS is running on local system account.
When I start target auto discovery I get following error:
Status          Failed
     Exit Code          4
     Step ID          1022
     Started          01-Jun-2012 11:06:54 GMT+02:00
     Ended          01-Jun-2012 11:06:54 GMT+02:00
     Step Elapsed Time          0 seconds
     Management Service          OracleEM.Myhost:4889_Management_Service
Output Log
Host discovery job failed. Exception: Unable to create directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst
Even I had created such directory manually it stills shows the same error. I have also verified that LA account has full control to C:/MiddlewareHome/agent/agent_inst directory.
Cygwin doesnt have sudo option installed (not needed according to docs on Windows, although job credentials require sudo delegation - what for?).
Any ideas?
Thanks,
JP

Logs show following:
[2012-06-04T15:40:46.267+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.Util.class] [tid: [ACTIVE].ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: SYSMAN] [ecid: d70f67283c055146:772f8397:137b7b1143f:-8000-0000000000000252,0] [APP: emgc] oracle.sysman.core.discovery.uimodel: MissingResourceException: nlsid=OSB_DISCOVERY_TEXT, rb=oracle.sysman.db.rsc.ob
[2012-06-04T15:41:27.281+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand] [tid: RemoteJobWorker 1931] [userId: SYSMAN] [ecid: 0000JUrgIZnFKA05zzK6yW1FnBYO000001,1:26629:3] [APP: emgc] Exception occurred while creating discovery directory under:C:/MiddlewareHome/agent/agent_inst:java.security.PrivilegedActionException: oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: Cannot run program "mkdir": CreateProcess error=2, The system cannot find the file specified
[2012-06-04T15:41:27.281+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand] [tid: RemoteJobWorker 1931] [userId: SYSMAN] [ecid: 0000JUrgIZnFKA05zzK6yW1FnBYO000001,1:26629:3] [APP: emgc] Unable to create discovery directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst
[2012-06-04T15:41:27.312+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand] [tid: RemoteJobWorker 1931] [userId: SYSMAN] [ecid: 0000JUrgIZnFKA05zzK6yW1FnBYO000001,1:26629:3] [APP: emgc] executeNMapCommand: Exception: Unable to create directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst[[
java.lang.Exception: Unable to create directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst
     at oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand.executeNMapCommand(RunNMapCommand.java:633)
     at oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand.executeCommand(RunNMapCommand.java:337)
     at oracle.sysman.emdrep.jobs.CommandStepExecutor.execute(CommandStepExecutor.java:153)
     at oracle.sysman.emWebservices.inbound.jobs.worker.ConsoleJobStepExecutor.execute(ConsoleJobStepExecutor.java:316)
     at oracle.sysman.emWebservices.inbound.jobs.worker.ConsoleJobStepExecutor.executeStep(ConsoleJobStepExecutor.java:182)
     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 oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:369)
     at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:201)
     at oracle.j2ee.ws.server.jaxws.JAXWSRuntimeDelegate.processMessage(JAXWSRuntimeDelegate.java:479)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
     at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:1089)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.security.Security.runAs(Security.java:61)
     at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
     at oracle.security.jps.internal.jaas.AbstractSubjectSecurity.executeAs(AbstractSubjectSecurity.java:138)
     at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:304)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1096)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:581)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:232)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:192)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:484)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:315)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:555)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.caching.filter.AdfFacesCachingFilter.doFilter(AdfFacesCachingFilter.java:129)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
That seems strange as mkdir is WinSrvr system command.
JP

OVM server Discovery fails

When I attempt to discover one of my OVM servers I'm getting a python(?) error during the storage discovery phase.
Anyone have any ideas how to resolve this?
Thanks!
warning icon
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 12:43 on Thu, Sep 15, 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=1316119397274
Operation 'NTP Service Configure' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
Operation 'NTP Service Configure' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
Operation 'NTP Service Configure' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
Operation 'NTP Service Configure' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
Operation 'Server Set Statistic Interval' in non-job running context, not adding it to object '08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec'.
Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: discover_hardware to server: 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec failed. OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
AttributeError: 'NoneType' object has no attribute 'search'
Runtime errors occured [1]
Thu Sep 15 12:43:18 AKDT 2011
Thu Sep 15 12:43:18 AKDT 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: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)
Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
AttributeError: 'NoneType' object has no attribute 'search'
Runtime errors occured [1]
Thu Sep 15 12:43:18 AKDT 2011
at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:748)
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 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec
Object (CREATED): [LocalStorageInitiator] storage.LocalStorageInitiator in 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec
Object (CREATED): [Server] 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec
Object (IN_USE): [DiscoverManager] OVM Foundry : Discover Manager
Object (CREATED): [XenHypervisor] Hypervisor in 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec
Completed Step: ROLLBACK
Job failed commit (internal) due to OVMAPI_4010E Attempt to send command: discover_hardware to server: 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec failed. OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
AttributeError: 'NoneType' object has no attribute 'search'
Runtime errors occured [1]
Thu Sep 15 12:43:18 AKDT 2011
Thu Sep 15 12:43:18 AKDT 2011
com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: discover_hardware to server: 08:00:20:ff:ff:ff:ff:ff:ff:ff:00:21:28:75:71:ec failed. OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
AttributeError: 'NoneType' object has no attribute 'search'
Runtime errors occured [1]
Thu Sep 15 12:43:18 AKDT 2011
Thu Sep 15 12:43:18 AKDT 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: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 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: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)
Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: discover_hardware , Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ERROR 0 @ 144 add_all_block_data() Doom: Traceback (most recent call last):
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_directives.py", line 141, in add_all_block_data
populate_blk_dev_info_dict( vi_errorAndLog_obj, diskInfo_DICT, blkdev_LIST, mpConf_default_callout, mpConf_blacklistInfo, mpConf_blacklistExceptionsInfo, mpConf_devSpec_LIST )
File "/usr/lib64/ovs-storage-utils/vi_discover/storage_discover/sd_blkDevInfoUtils.py", line 235, in populate_blk_dev_info_dict
if not mpConf_blkLstWWID.mWWID_cmpldRegEx.search( wwid ): # match() assumes '^' anchor in pattern
AttributeError: 'NoneType' object has no attribute 'search'
Runtime errors occured [1]
Thu Sep 15 12:43:18 AKDT 2011
at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:748)
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:470)
... 30 more
End of Job
----------

This is usually due to either of the following issues (not enough information to determine if this is your problem):
1. The IP addresses you are using as the IPs for the Oracle VM servers being discovered are somehow incorrect. For instance, I sometimes typo one of the octets in the IP address IE: I meant to type 10.11.12.100, but instead messed up the third octet by typing a "21" instead of a "12" (just an example).
2. The password you provided for the "Oracle VM Agent Password" in the discovery dialog is incorrect. There are several reasons this may be happening, but the way to ensure the ovs-agent has the same password you think it should is by logging into each Oracle VM server and changing the ovs-agent password for BOTH "admin" AND "oracle" users. This is done using the following command on each Oracle VM server:
/usr/sbin/ovs-agent-passwd admin
/usr/sbin/ovs-agent-passwd oracle
Both of the above will prompt for a password - use the same password for both and ensure you do this on all your Oracle VM servers.
Here is how you verify that the passwords you just changed work:
/opt/ovs-agent-3.0/utils/do_rpc.py https://admin:<new passwd>@<your OVM server>:8899 echo ""
/opt/ovs-agent-3.0/utils/do_rpc.py https://oracle:<new passwd>@<your OVM server>:8899 echo ""
The above commands will return the following if the passwords are correct (anything else, no matter what error it returns means the password is not what you expect it to be):
echo [''] =>
success:echo=
Hope this answer helps...
-Greg

Oracle VM disaster recovery network meta file discovery fails.

I am using the Oracle White Paper "Oracle VM 3: Integrating Oracle VM into a Disaster Recovery Solution using SAN"
http://www.oracle.com/technetwork/server-storage/vm/ovm3-disaster-recovery-1872591.pdf
The problem I am facing is that during the server discovery process in part 2 step 8 the meta network config files from the Primary site are not being recognized by the servers at the DR Site.
I received no errors during the DR Site server discoverer process which should have picked up the meta network config files brought over from the Primary Site OVM servers. I have rediscovered the servers and I have restarted the servers with no success. I am stuck any help or guidance would be appreciated.
Thank you, Russell

After working with Greg King the Author of "Oracle VM 3: Integrating Oracle VM into a Disaster Recovery Solution using SAN" and Sairam Thota from Oracle support, we have come to the conclusion that this is a bug. We did upgrade to OVM 3.2.6 from OVM 3.2.1 with no success on resolving this issue. However, Greg did get the network config files working on the DR site but he had to do it manually. The SR with Oracle that I created is still open and I am awaiting a bug number to be assigned for this issue.
Thank you, Russell

IDS discovery fails

Similar Messages

Maybe you are looking for