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

Similar Messages

Windows Tablet workplace turn on device management failed on auto-discovery without any error

Hi
I am using windows surface pro 3 to test windows mdm function. I set up a CNAME for my test domain and pointed it to my develop desktop. My discovery service uses a publicly signed cert from VeriSign. If I turn off the auto detect server address switch and
input the discovery server manually, everything works well. But if I using the auto-discovery, the enrollment stopped before sending the discovery SOAP request.
Below is the network traffic between my tablet and my server:
step1: https to enterpriseenrollment.mydomain.com and failed for SSL certificate mismatch
step2: http to enterpriseenrollment.mydomain.com and get 302 redirect(my discovery service)
step3: https get to my discovery server and get HTTP 200.
Then the tablet does not send any request any more, it should send a HTTP get again with Content-Type: soap+xml and then a POST with soap but it not.
These work flow is as same as the Windows Intune and Intune works! I don't know why.
Thanks for any help!

Yes, because if you are using the actual hostname in the manual address, something like
https://yourServer/..., and if the SSL Certificate is issued to "yourServer" (CN=yourServer), then there is no certificate name mismatch or SSL errors during certificate validation.
However, when the automatic enrollment happens and the HTTPS request is sent to
https://enterpriseenrollment.yourServer.com/..., then even though the underlying connection is made to yourServer IP Address, the certificate that the server presents is for yourServer, not enterpriseenrollment.yourServer.com.
So there will be a certificate name mismatch and the secure channel establishment will fail.
For this automatic scenario to work properly, the server certificate must be issued to the correct domain - such as a wildcard certificate (*.yourServer.com). That should ensure that there are no secure channel errors and then the enrollment process can
continue further.
You can use the manual address for development/testing purposes, but once you decide to release the solution, you may want to use the automatic discovery for easier end user interaction and use the right SSL certificates - issued to the right CN.
Windows Store Developer Solutions, follow us on Twitter:
@WSDevSol|| Want more solutions? See our blog

Scsi-target auto-poll

SANOS configuration guide mentions the command "show scsi-target auto-poll". It doesn't explain in detail what auto-poll is and how to activate it. It vaguely mentions that it has to do with "CSM or an IPS module is in the chassis". Can someone please clarify? Does this mean that the switch will attempt scsi-target on all IPS ports if it's inserted into the chassis? Because I thought the scsi target discovery can only be done on demand.
thanks

Whenever an IPS or CSM blade is in an MDS, the MDS will login to storage just the same as a real initiator would. We send Inquiry, Report Luns, and read capacity to learn about the storage out on the SAN. This process is done when the storage device comes online or when manually initiated. However, with auto-poll, we will go thru the discovery process every X number of seconds that can be configured.
This is not on the IPS ports but rather on any FC attached device that registers itself as a target. We use the pwwn seen as the result of show scsi-target internal driver. If the storage has any kind of LUN security, this pwwn will need to be permited or our discovery process will fail due to it being denied.

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
========

How to configure Auto Discovery in OEM 12c

Hi
I am new to OEM12c. I need to set up the auto email alerts through OEM 12c. through the Admin guide I have read the procedure.But I am not able to implement it. Can anybody tell me here the detailed procedure to add the managed target in OEM12c. We need to monitor mainly HCM domain form here. Please tell me the prerequisites also. When i try to configure auto discovery of host it asks me for host credentials but i ma not able to get for which credentials it is asking for.
Thanks in Advance

Hi,
Configuring notification rules in 12c is different from earlier releases.
The concept and function of notification rules has been replaced with a two-tier system consisting of Incident Rules and Incident Rule Sets :
1. Incident Rules: Operate at the lowest level granularity (on discrete events) and performs the same role as notification rules from earlier releases.
By using incident rules, you can automate the response to incoming incidents and their updates.
A rule contains a set of automated actions to be taken on specific events, incidents or problems.
The actions taken are for example : sending e-mails, creating incidents, updating incidents, and creating tickets.
2. Incident Rule Set: A rule set is a collection of rules that applies to a common set of objects, for example, targets, jobs, and templates.
To help you to achieve the Notification Rules configuration, refer those notes :
How To Configure Notification Rules in 12C Enterprise Manager Cloud Control ? - Doc ID 1368036.1
EM12c How to Add and Configure Email Addresses to EM Administrators and Update the Notification Schedule ? - Doc ID 1368262.1
EM12c How to Subscribe or Unsubscribe for Email Notification for an Incident Rule Set ? - Doc ID 1389460.1
EM 12c How to Configure Notifications for Job Executions ? - Doc ID 1386816.1
++ Regarding the Auto Discovery in 12c following the document below:
Configure Auto Discovery In 12c - ID 1529868.1
Regards,
Venkat

JBoss 7 auto-discovery on Linux

Hi,
Can anybody confirm that auto-discovery works for JBoss 7 servers on Linux?
We're running JBoss 7 in domain mode on a non-standard HTTP-port (e.g. not on 8080) and it seems that auto-discovery does not work in this scenario.
This is with SCOM 2012 R2 Update Rollup 4 (version 7.1.10226.0) and the MP for JBoss version 7.5.10380. The target host is running RHEL6 and the Unix agent is installed and running (version 1.5.1-138).
We have deployed Beanspy into the appserver runtime and verified that it's working using a browser (it returns an XML response).
Thanks in advance for any input.

Hi,
Based on the document for the management pack, after the management packs for the JEE application servers are imported, the instances of JBoss application servers will be automatically discovered. The discovery interval is set to 4 hours by default so discovery
can take up to that length of time.
On JBoss, an application server must be running for Operations Manager to discover it for the first time. After an instance is discovered, the configuration will be removed only when the application server is uninstalled.
You can monitor instances of the JBoss Application Server by doing the following:
In the Operations console, click Monitoring.
Expand Application Monitoring, expand
Java Monitoring, expand JBoss Application Servers, and select the monitoring folder of interest.
On JBoss, the application state is not monitored because applications can only be discovered when they are running. If an application is stopped, or deployed but not started,
it will disappear from the JBoss application state view.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Oem auto discovery does not discover

Hello, DBAers; RHEL 5 x64, Oracle Enterprise Manager 12.1.0.3 - trying to discover an unmanaged host using auto discovery and following the instructions spelled out here
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/discovery.htm#EMADM13119
and the auto discovery is not discovering.
I can "ssh <usrname>@<hostname>" and connect to the unmanaged target from the machine running the management server and ping the target server from same, so it does not appear to be a firewall issue. But OEM cannot see it through auto-discovery. Do any of you have any thoughts?
Humbly,

To be able to run auto-discovery,
the Sudo Privilege Delegation must be set on the Management Agent host that will perform the scan. The named credential that will be used must be configured to run as root.
Because it used nmap (port scanner). Have you checked that sudo privilege delegation is set?

Why does Google auto-complete fail in Firefox 17.0.1 when I type something in the search field there is no pull down list of options as I type?

When I type a word or term into the Google search bar the auto-complete fails; there is no pull down list of options for my search, only what I have completely typed in. I have to type in the complete word or term that I am searching for and then press return to get the results. I'm using a MacBook and OS X 10.7.5 Please help! This is so frustrating!

Note that websites may be using autocomplete=off to prevent Firefox from saving and filling autocomplete data as I posted above.
Did you check for that?
You can remove autocomplete=off with a bookmarklet.
* http://kb.mozillazine.org/User_name_and_password_not_remembered
If a site uses autocomplete="off" then look at this article for a bookmarklet to remove the autocomplete attribute.
* http://kb.mozillazine.org/User_name_and_password_not_remembered (bookmarklet)
You can paste this code in the command line in the Web Console (Web Developer > Web Console; Ctrl+Shift+K) and press the Enter key to verify if there is an input field with autocomplete.
*https://developer.mozilla.org/en/Tools/Web_Console
<pre><nowiki>var c=0,e=document.querySelectorAll('input[autocomplete],form[autocomplete]'),T='\n';
for(i=0;E=e[i];++i){T+='['+(++c)+'] '+(E.name||'#'+E.id)+' ('+(V=E.getAttribute('autocomplete').toLowerCase())+')\n';}
console.log('autocomplete: '+c+T);
</nowiki></pre>

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.

Auto-discovery option..

In Weblogic we need to define the managed server in the administration server first for it to be a part of the cluster. Which means that if the administration server is not available for any reason the configuration of the cluster cannot be altered.
          Is there a concept of Auto-Discovery available in weblogic (similar to JBoss) where-in the cluster nodes are automatically converged into a cluster if the partion-name and the multicast IP address and port are the same within the same subnet.

A server can join a cluster if the admin server is not up, but all servers must be configured and the admin server is required for that.
          The usual deployment strategy would be to pre-configure all the servers you may want to run but only boot an initial set. Then there is no requirement for the admin server to be up.
          I'd have some concerns about the auto-discovery approach. We tend to be relatively conservative for production environments and wanting it to be extremely deterministic for admins.
          -- Rob
          WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Auto Discovery in CUOM

I have installed CUOM 2.2 and am trying to monitor a Call manager 4.2 cluster. I have configured all Call Manager servers with the SNMP string and host in windows services.
When I run an Auto Discovery in CUOM with the Publisher as the Seed Device I expected all CCMs, VGs and Phones to be discovered however CUOM discovered the Publisher only.
Can anyone advise what I have missed?
Many Thanks
Pete

I think it seems like SNMP string issues. Please check at both CUOM and Device side for SNMP.
check
1. Network connectivity between CUOM and device
2. Check SNMP are working fine at device side.
3. Check SNMP configuration at CUOM
If there is problem and is fixed, please rediscover the device in CUOM.

Auto-Discovery BlackList Alert

Hi Everyone,
   Is any way to configure the WAAS CM to send a SNMP Trap or Syslog Message when an IP Address start to appears in the
   Auto-Discovery BlackList Server Table..
   I wanna to alert the NOC when the traffic to a specific server be not optimized cause the BlackList Reason
Thanks in Advanced
Andre Lomonaco

Do i need to package my tag handler in a jar file?no.
If
i put the full qualified uri in the jsp file like
this
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page"
xmlns:bmw="urn:jsptld:/WEB-INF/bmw-taglib.tld"
version="1.2">
it works perfectly, but i don't want to hard-code my
tld path in the jsp files or in the web.xml.you have two options:
1. you do not put anything about the taglib into web.xml. then you must use the path to the tld as URI. the path is relative to the root of the application. i think in your case you would have to use "/WEB-INF/bmw-taglib.tld" as URI and not "/test-taglib".
2. you introduce the taglib in the web.xml and then you are free what URI you use.
The specification in section JSP7.4.3 ("Implict Map
Entries from TLDs") sais, that an <uri> tag in the tld
is sufficient and a corresponding entry in the web.xml
is generated automatically.yes, option 1.
robert

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.

Target Auto Discovery fails

Similar Messages

Maybe you are looking for