Auto Discovery in SNMP

How to get 'Auto Discovery' feature from SNMP? Auto Discovery means get all IP addresses in LAN. Thanks in advance.

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.

Similar Messages

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

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/

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

2012 R2 DirectAccess multi domain forest: Is it possible Limit Auto-discovery of domain controllers?

I've just successfully implemented Multisite server 2012 R2 DirectAccess in a child domain of a global company with numerous sub domains. I'd like to limit the scope of the auto discovery of management servers in 2012 R2 DA is anyone aware of
any way of doing this?
During the default initial configuration of DirectAccess Auto-discovery of domain controllers is performed for all domains in the same forest as the DirectAccess server and client computers.
In my scenario the number of sub domains and multinational nature of the company means that the DA servers cannot contact all DCs for every child domain in the forest.
This means the Operations Status page in the Remote Access Management console always shows the status of the Domain Controller check as "critical" leaving a red X amongst my nice green ticks. It's untidy and at first glance it looks like there
are major problems with the service.
The DA servers, Client machines and users are in a single sub domain so we have no need to contact the other child domain DCs.
I looked into using the Remove-DAMgmtServer PowerShell cmdlet however this is not applicable since it cannot be used to remove automatically configured management servers such as DCs.
Also the child domain DCs don't actually appear in the management servers list.

Hi, a colleague of mine had the same problem in a DirectAccess deployment in a large organization tat have a multi-domain forest. He had no choice to open network flow to have at least one domain controller per domain in the forest.
BenoitS - Simple by Design http://danstoncloud.com/blogs/simplebydesign/default.aspx

Android Email Policy - Username Auto Discovery

Is there a way to set the Username in Email Profile for Samsung KNOX Standard policy to
User Principal Name? Right now it is set to Auto Discovery and the email policy does not go through, but if I manually setup the email it will push through correctly when using the setting that would apply if I could select User Principal Name.
Thanks.

The Username field is fixed at "Auto discovered" and this cannot be changed. Intune automatically populates this field with the user principal name. This is different in iOS where you must choose between Primary SMTP and UPN.
Source:
https://technet.microsoft.com/en-us/library/dn800672.aspx
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Auto-Discovery of Tag Libraries

Has anyone of you got the auto-discovery thing of tlds running? Well, i have problems with it.
My tld resides in the WEB-INF directory and contains the following:
<taglib>
<tlib-version>1.0 EA2</tlib-version>
<jsp-version>1.2</jsp-version>
<uri>/test-taglib</uri>
</taglib>
-[eof]---------------------------------------
And the jsp page contains the following.
<%@ taglib uri="/test-taglib" prefix="test" %>
<test:getActive/>
-[eof]---------------------------------------
The same thing in XML sytax (Sun calls this JSP document :o).
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" xmlns:bmw="urn:jsptld:/test-taglib" version="1.2">
<test:getActive/>
</jsp:root>
-[eof]---------------------------------------
In both cases Tomcat 4.01 reports an error, when i try to invoke the jsp: org.apache.jasper.JasperException: File "/test-taglib" not found
Am i missing something?
regards,
dani3l

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

Auto-discovery for TLD files in WEB-INF

The auto-discovery mechanism in JSP 1.2 can scan through the WEB-INF directory structure for files with .tld exntension and find all <uri> definitions in them, so we can use a symbolic name to map to the actual location of the tld file by using:
<%@ taglib prefix="test" uri="mytaglib" %>
in a JSP page.
My colleague and I did not have luck in making this work. I got the following error message:
"500 Internal Server Error
OracleJSP: oracle.jsp.parse.JspParseException: Line # 1, <%@ taglib prefix="test" uri="kltaglib" %>
Error: java.io.FileNotFoundException: C:\oc4j\j2ee\home\applications\myapp\myapp-web\mytaglib (The system cannot find the file specified) "
The symbolic name was not recognized. Is this a limitation in OC4J? Has anyone make this work? However, another way of auto-discovery by META-INF in JAR files works for me.
Thanks.

The auto-discovery mechanism in JSP 1.2 can scan through the WEB-INF directory structure for files with .tld exntension and find all <uri> definitions in them, so we can use a symbolic name to map to the actual location of the tld file by using:
<%@ taglib prefix="test" uri="mytaglib" %>
in a JSP page.
My colleague and I did not have luck in making this work. I got the following error message:
"500 Internal Server Error
OracleJSP: oracle.jsp.parse.JspParseException: Line # 1, <%@ taglib prefix="test" uri="kltaglib" %>
Error: java.io.FileNotFoundException: C:\oc4j\j2ee\home\applications\myapp\myapp-web\mytaglib (The system cannot find the file specified) "
The symbolic name was not recognized. Is this a limitation in OC4J? Has anyone make this work? However, another way of auto-discovery by META-INF in JAR files works for me.
Thanks.

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

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

Disabling service auto-discovery

a client has a 10.5.x server that was "converted" to an advanced config from standard.
it seems whatever determines service auto-discovery for clients is still active, and i need to disable this feature. so, for instance, when a user logs into client machine, ichat, ical, and mail automatically configure themselves with accounts, even though the details may not be correct.
how do i disable this?
thanks for any help.

replying to myself…
i think this might be it, but can anyone confirm?
in wgm, there's a ServiceConfiguration record. the relevant bit looks like this:
<dict>
<key>IsStandardConfig</key>
<true/>
i'm guessing changing that key to false will prevent clients from automatically discovering and configuring services, correct?

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?

Detailed Discovery with SNMP

I'm working with vADM 6.2.1.
I am having issues with SNMP trying to discover IBM iSeries servers. I can use snmpwalk from windows machines and get a response from the iSeries server, but when I use snmpwalk from the vADM VM collector all I get is a timeout. My policy is also failing to connect to the host. The iSeries sysadmin believes that the problem may be that the response is coming back on a different port than 161 (See the document below). If the fact that the iSeries server is responding back on a different port, or a port above 5000, then I don't quite understand why other implementations of snmpwalk are capturing mib information but the vADM Fedora version is not. I'm not sure what else to try to get it to work. I have validated that the vADM collectors (all of them) are registered as management hosts on the iSeries server and I know there are no firewals intervening.
Document Title
The IBM iSeries Family of Servers SNMP Agent Responds on an Ephemeral Port Rather Than Port 161
Document Description
The user finds that when a request is made to the IBM iSeries family of servers SNMP Agent on port 161, the iSeries family responds on a port above 5000. Why is the iSeries so different from VM or IBM MVS systems that will receive and respond on the same SNMP port? Many customers have a firewall and don't want to open all ephemeral ports above port 5000. Is there a work-around to this?
This is working as designed. There is no current configuration you can use to force SNMP to respond on port 161. The semantics they are looking for are mostly identified with TCP - connection oriented (statefull) sessions. SNMP uses UDP (connectionless) protocols, and the most common way to send datagrams with UDP is by using an ephemeral port.
The original SNMP developers said that there are separate jobs: a receiver job to receive all requests from all managers, and the sender job responsible for the accessing the MIB database and actually responding to the request(s). The receiver job passes off the requests to the sender job and goes back to listening for new requests. Because both jobs cannot bind to port 161 (this was written in V3R1 when mechanisms like spawn were unavailable), the receiver job uses 161 and the sender job uses a random port.

I don't believe that platform is supported for vADM Detail Discovery.
If I were to troubleshoot this, I'd try to see if stopping the iptables firewall allows this to work -just as a test. If this does work, then you'll need to configure the IP Tables firewall settings to allow for higher-numbered incoming ports from the expected IP Addresses or ranges where you think you'll be probing. I would not continue running with IP Tables down.
While you're testing this it might be a good idea to run tcpdump to see if the Collector/Single-box system is sending/receiving traffic from the target.

Auto Discovery in SNMP

Similar Messages

Maybe you are looking for