Snmp master agent won't start

I'm using Web Server 7.0U1 on Solaris 10U4. I'm trying to start the SNMP master subagent. On my Linux test platform, this works fine. But on the Solaris host, 'magt' hangs forever at startup and does nothing. This happens both when using the web console and wadm start-snmp-master-agent command.
How do I make magt work?

The SNMP master agent fails to start on Solaris 10U2 (and higher) due to the TCP fusion feature added in Solaris 10U2. (TCP fusion is a protocol-less data path for loopback TCP connections). One of the possible workarounds for this issue is to disable TCP fusion by adding the following line in /etc/system:
set ip:do_tcp_fusion = 0x0
The Sun Info Doc 86046 available on sunsolve explains the various TCP fusion related tunables.

Similar Messages

SNMP subagent with SMUX SNMP master agent

I'm looking for the smux agent configuration for ucp-snmp to be able to use it as the master agent on a Linux/Solaris server. The subagent would be the LDAP instance snmp sub-agent. According to the documentation, if I have a master agent that I can't get rid of and is smux compliant, I can use it instead of the Netscape SNMP Master agent.
Even by configuring the ucp-snmp master agent as per the Netscape Directory Server documentation, the subagent is not starting. I always get the following error: "Unexpected error" in the console 4.2 window.
I'm using a Netscape Directory Server 4.16
Can anybody help me on what should be the smux configuration and then how to start the LDAP instance subagent?

Hi,
Iplanet does not support for it's products being installed on linux or snmp for linux.

Intelligent agent won't start

We renamed the windows 2000 host on which Oracle lives and now the intelligent agent won't start. I cleared snmp_rw etc and rebooted but still no go any ideas?
thx in advance.

Thx Pete but the emca will effect the OEM repository I am looking for reconfig of the intelligent agent to reflect the new hostname.
Daryl thx for the reminder. My DB is 9.2.0.1 on XP but the same rules apply as Unix. It turns out I missed deletion of one of the .q files which was enough to block auto-create on atleast one .q file and leave me hanging.
These are the steps I took to fixit:
1) shutdown the agent
2) shutdown the listener
3) delete snmp* files under network/admin
4) delete .q files and services.ora under network/agent
5) restart listener
6) restart agent
7) re-acquire DB through OEM discovery (success)
Obviously the change of hostname has to be picked up by the IA's files. If the files do not exist at IA startup the IA creates them using current information from the host.
thx to all.

Dbsnmp unable to connect to SNMP master agent

DBSNMP for 32-bit Windows: Version 9.2.0.1.0 - Production on 13-JAN-2006 10:58:24
Copyright (c) 2002 Oracle Corporation. All rights reserved.
System parameter file is C:\oracle\ora92\network\admin\snmp_ro.ora
Log messages written to C:\oracle\ora92\network\log\dbsnmp.log
Trace information written to C:\oracle\ora92\network\trace\dbsnmp_728.trc
Trace level is currently 0
NMS-00001: Warning: dbsnmp unable to connect to SNMP master agent
I get the above message as dbsnmp.log every day in my testdb.. wat is the purpose and meaning
oracle_home\network\log

Hmmmmm.
Using the online error code lookup facility in the Oracle documentation, I see the following:
NMS-00001: Warning: service unable to connect to SNMP master agent.
Cause: An SNMP Master Agent is used to communicate with a third party SNMP monitoring console. The specified service could not contact the SNMP master agent. The master agent supported by Oracle for this platform is not installed, or has not been started. Messages specific to this platform follow.
This is a warning and does not prevent the agent from communicating with the console. If Oracle Enterprise Manager is the only monitoring console accessing this agent, the NMS-00001 error can be considered informational and should be ignored. Configuration of the SNMP Master Agent is not reguired for the Oracle Enterprise Manager Console.
Action: Consult Oracle documentation for your platform; then, make sure that the correct SNMP master agent is installed and started. The SNMP Master Agent and the Oracle Intelligent Agent must be configured correctly before the Oracle Intelligent Agent can communicate over SNMP to the Master Agent.
The Oracle Intelligent Agent needs to be configured. The 7.3.2.x agent required an SNMP.ORA file. All later versions of the Oracle Intelligent Agent are self-configuring and do not reguire the creation of an snmp.ora file.
Solution Explanation
1. The Oracle Intelligent Agent needs to be configured. The 7.3.2.x agent required an SNMP.ORA file. All later versions of the Oracle Intelligent Agent are self-configuring and do not reguire the creation of an snmp.ora file.
2. The SNMP Master Agent needs to be configured and started.
There is even more. Especially in the are of 'how to configure and start'. Can wee look that up for you as well?

Dialog between the SNMP Master Agent and a SNMP SubAgent

I have developped a SNMP SubAgent. The Master Agent uses the static method to register the SubAgent. In the Registration File of the SubAgent, I have specified the UDP port number (example: port = 1234). When the SubAgent is started (by the MasterAgent), it must open the UDP port specified in the Registration File. The dialog works fine between the SubAgent and the Master Agent.
I would prefer not to specify the UDP port number in the Registration File so that the Master Agent chooses itself a free UDP port number. But the SubAgent needs to know this UDP port number to dialog with the Master Agent. I thought the SubAgent could read it in the Status File of the Master Agent. BUT in fact, when the Master Agent invokes the SubAgent, its Status File isn't yet updated with the right port number value.
How may the SubAgent know the UDP port number chosen by the Master Agent ?
NB: I haven't use the SunOS SNMP toolkit to develop the SubAgent.

Hi ,
Good question.
The subagent only communicates via the port 161 with the master agent as per my understanding. It only listens for SNMP request on the port number mentioned in the <<agentname>>.rsrc file or the port assigned by the master agent. Please start the subgent with no options "-d 4" and then you can confirm the behaviour. Enclosed below is a snippet of that output for reference. Also the UserGuide at the following link will be helpful.
http://www.sun.com/software/entagents/docs.html
Thanks
Sujeet
<pre>
./init.snmpdx start
PDU:
version: 0
community: public
type: SET_REQ_MSG (0xa3)
request id: 0
error status: noError(0)
error index: 0
name: 1.3.6.1.4.1.42.2.15.5.0
type: OCTET STRING (0x4)
length: 8
value: snmpdemo ( 73 6e 6d 70 64 65 6d 6f )
PACKET:
30 30 02 01 00 04 06 70 75 62 6C 69 63 A3 23 02
01 00 02 01 00 02 01 00 30 18 30 16 06 0A 2B 06
01 04 01 2A 02 0F 05 00 04 08 73 6E 6D 70 64 65
6D 6F
sent 50 bytes to sump.161<< received 50 bytes from sump.161
PACKET:
30 30 02 01 00 04 06 70 75 62 6C 69 63 A2 23 02
01 00 02 01 00 02 01 00 30 18 30 16 06 0A 2B 06
01 04 01 2A 02 0F 05 00 04 08 73 6E 6D 70 64 65
6D 6F
PDU:
version: 0
community: public
type: GET_RSP_MSG (0xa2)
request id: 0
error status: noError(0)
error index: 0
name: 1.3.6.1.4.1.42.2.15.5.0
type: OCTET STRING (0x4)
length: 8
value: snmpdemo ( 73 6e 6d 70 64 65 6d 6f )
</pre>

Server Intelligence Agent won't start after repair of Business Objects 4.0

I migrated our company's business objects contents and documents from previous BO 3.1 server to new BI 4.0 server using standard BI tools. (That is, using the export wizard in BO 3.1 to create BIAR file and using upgrade management tool to import this biar file to new BI 4.0 server).
After that, everything looks fine, I can log in to launch pad and can see all the folders, reports, etc have been moved over.
But Life Cycle Management stopped working. I guess the reason is, when I created the biar file from source 3.1 server, I basically included everything that may include LCM folder as well, and this folder overwrite the LCM folder in BI 4.0 server. In order to fix this issue, I did "repair" of BI platform. After this, the Server Intelligen Agent won't start.
Tried to log on to cmc, got error message
"Error: Server SERVERTest:6400 not found or server may be down (FWM 01003) null"
Tried to start the Server Intelligence Agent from "services", got message:"windows could not start the server intelligence agent (servertest) from local computer..." Checked the event log, no much useful information.
Can anyone please give me some ideas? what might have caused this issue? where should I look to? I hope we don't have to go through uninstall/reinstall.
thanks.

Hi,
check the Task Manager if you have running the processes running "SIA.exe" ans "cms.exe"
Regards
-Seb.

Re: Wls agent as subagent to Sun's Snmp Master Agent

I have successfully configured the WL SNMP agent as subagent to
Sun's (Solaris 7 in my case) master SNMP agent.
Sun's Solstice Enterprise Agent documentation under docs.sun.com
is a bit confusing but serves as a reference if not a step-by-step guide.
Here are the general steps that I took:
1) Modify the shipped startSNMPAgent.sh for your system password
and community (I wouldn't use "public"!).
Add some if-then-fi code to check for the $1 command line parameter,
so Sun's master agent can pass in the dynamically allocated port number
that the agent will listen to. I also changed the ownership of this
script so only root can see it, as it contains the WL admin password.
2) Go to the /etc/snmp/conf directory (default Solaris 7 install).
Create the files weblogic.rsrc and weblogic.reg using the mibiisa.*
files as templates.
3) In the weblogic.reg file, add the lines
"macros = { bea = enterprise.140 }" before the "agents" line.
This defines the weblogic agent's starting OID point.
Then, change the subtree line to "bea".
4) In the .rsrc file, change the command used to spawn the
agent to "/weblogic/startSNMPAgent.sh $PORT".
Be aware that this spawn command is visible through Sun's master
agent MIB, so don't put anything sensitive in there (like a
community name or password).
5) Finally, there is a timing condition that you should be aware of.
WebLogic's SNMP agent will only bind to an active WL server.
Sun's master agent will only bind to an active subagent.
Therefore, you should ensure that
WebLogic server is started first (and the server comes completely
up), then Sun's master agent is started. I setup my /etc/rc3.d
startup files to run weblogic before snmpdx. I had to insert a
sleep command to make sure that WL was completely up before
snmpdx was run. This is because my startup script runs java in
the background, so if you don't sleep then WL won't be up before
snmpdx spawns the subagent and tries to bind to it.
Finally, Sun's mib files can be found under /var/snmp/mib.
Easier to find than NT's mib files!
Hope that helps -
Tom
"Sanjeev Chopra" <[email protected]> wrote:
>
Robert Prakash <[email protected]> wrote in message
news:[email protected]...
Hi Sanjeev
My Wls agent is working fine as Master agent with Sun's Snmpdx as subagentto it.
There is no problem with that.
But can I make WLS agent, subagent to Sun's Snmp Agent.For that I needWls
SubAgent resource
files to be included in the configuration directory of Sun's Snmp Agent.The last time i checked, Sun's master agent is more "loosely coupled"
with
other agents it needs to co-ordinate with. I haven't tried it, however
i
beleive it should work. Because the master agent doesn't rely on built-in
protocol for interaction with other agents. (much like -otherAgents option
in the wls agent).
You just need to specify in SUN's syntax (resource files...) where the
wls
agent is running, what is its community, which MIBs it supports , what
should be the timeout and such ...
Good Luck!
If you run into any problem let me know.
Is this possible in the first place and if so how do I do it. I sawyour
response on the same issue for
Windows NT. I am mailing to find out if its different on Solaris(orUnix).
Thanks
Robert

Hello:
I created exactly as you specified. I.e weblogic.reg, weblogic.rsrc, weblogic.acl. But the issue I have is My weblogic snmp agent is listening on port 8061. Snmp demon on 161. So when I request the Snmp demon with OID of weblogic object. I am not getting the result also call is not reaching weblogic agent. Instead I am getting no such name or OID. So I am wondering why snmp demon is not forwarding the request to snmp demon.
Also Could you please explain the execution sequence of snmp demon and where you think I need to look at. Also please explain the constructs used in reg/acl/rsrc files.
Note:
I am using wls 6.1 sp2. So just my starting admin server. The enabled snmp gets started. Also I configured snmp demon so that when ever it gets started the weblogic server also starts. Also there is no issue in receiving traps.
Thanks in Advance.
Vijay

ODBC server & agent won't start - J2EE install

Hi all,
I have installed the developer edition of CFMX7. I have
tomcat running on my windows2000 server, so I downloaded the
windows installer and chose the J2EE-war option. It runs just fine.
I also installed the ODBC server, because I want to connect
to MS Access databases with my developer edition. For that, I tried
this:
http://www.bpurcell.org/blog/index.cfm?mode=entry&entry=860.
First problem was that after tomcat automatically deployed the war
file, the folder 'SequeLink Setup' did not exist in the web-inf\db
folder. So I renamed the war to zip, and checked - the file
is present in the war. So I manually extracted the zip to a
new directory. I ran the cfm script with the reference to this new
directory, and the ODBC services were installed - hurray!
But now the services do not want to start. I first got the
error that the file was not found. It referenced to a slserver52
folder, which had only two directories called 'logging' and
'tracing', but no bin files whatsoever. There is however a
slserver54 folder, which contains all kind of stuff. So I started
regedit and changed all the references to 52 in 54, and rebooted
the server. Still no luck: now I get a 1067 error on the server and
an unknown error on the agent.
Any ideas??

That is just what I did, but that didn't help. The installer
creates services that point to the slserver52 folder, but that
should be slserver54. When I change the directory in the registry,
the services won't start. The ODBC Agent sais:
"Could not start the ColdFusion MX ODBC Agent service on
Local Computer. The service did not return an error. This could be
an internal Windows error or an internal service error. If the
problem persists, please contact your system administrator."
The ODBC Service returns the exact same error.

Wls agent as subagent to Sun's Snmp Master Agent

Hi Sanjeev
My Wls agent is working fine as Master agent with Sun's Snmpdx as subagent to it.
There is no problem with that.
But can I make WLS agent, subagent to Sun's Snmp Agent.For that I need Wls SubAgent resource
files to be included in the configuration directory of Sun's Snmp Agent.
Is this possible in the first place and if so how do I do it. I saw your response on the same issue for
Windows NT. I am mailing to find out if its different on Solaris(or Unix).
Thanks
Robert

Robert Prakash <[email protected]> wrote in message
news:3a002079$[email protected]..
>
Hi Sanjeev
My Wls agent is working fine as Master agent with Sun's Snmpdx as subagentto it.
There is no problem with that.
But can I make WLS agent, subagent to Sun's Snmp Agent.For that I need WlsSubAgent resource
files to be included in the configuration directory of Sun's Snmp Agent.The last time i checked, Sun's master agent is more "loosely coupled" with
other agents it needs to co-ordinate with. I haven't tried it, however i
beleive it should work. Because the master agent doesn't rely on built-in
protocol for interaction with other agents. (much like -otherAgents option
in the wls agent).
You just need to specify in SUN's syntax (resource files...) where the wls
agent is running, what is its community, which MIBs it supports , what
should be the timeout and such ...
Good Luck!
If you run into any problem let me know.
>
Is this possible in the first place and if so how do I do it. I saw yourresponse on the same issue for
Windows NT. I am mailing to find out if its different on Solaris(or Unix).
Thanks
Robert

Ports used for Intelligent agent and snmp master agent

I could not find any documentation regarding which ports are used for communication between master and intelligent
agent. Moreover which port has to be mentioned if I use snmpget for the master agent. Please let me also know if I use a
management platform like CA-Unicenter with which port I have to send the traps and where to configure.
Thanks
Pragati Awasty

John Ross Hunt (guest) wrote:
: Once libtcl7.5.a is built and copied to the
: $ORACLE_HOME/network/lib directory, can the rest of the
: installation in /usr/local be deleted?
Yes, all that Oracle needs is the library to link in.
- Phil
null

Sourcefire AD user agent won't start

I have tried to install the user agent on a server 2008 vm and it won't run. I only get an error that says "SF AD user agent Configuration has stopped working"
I have configured the server settings in Policies, User, User Agents on my Defense Center. This is a domain server so the firewall is not on by policy. The event logs are pretty cryptic and don't really say much. The agent never starts so I can't configure it.
There is not much documentation out there for it.

Refer the link : http://www.cisco.com/c/dam/en/us/td/docs/security/firesight/user-agent/FireSIGHT-User-Agent-Configuration-Guide-v2-2.pdf

SQL Agent won't start

Hi,
I tried to start the SQL Agent on my SQL 2008 Server but got this error:
TITLE: Microsoft SQL Server Management Studio
Unable to start service SQLSERVERAGENT on server ACHSQL12. (mscorlib)
ADDITIONAL INFORMATION:
The SQLSERVERAGENT service on ACHSQL12 started and then stopped. (ObjectExplorer)
BUTTONS:
OK
Is there anything I should check?
Regards
Paul

You see the article for getting update :
Before you can start to use FILESTREAM, you must enable FILESTREAM on the instance of the SQL Server Database Engine. Enabling/configuring FILESTREAM is a bit different from configuring other SQL features because it involves making machine wide changes
and not only SQL instance changes. Also, FILESTREAM configuration has been changed for the February CTP to properly separate the Windows Built-in administrator and SQL administrator roles. In the November CTP, enabling/disabling FILESTREAM required Built-in
Admin privilege. Enabling FILESTREAM is now made up of 2 admin layers:
1-
The Windows configuration layer handles Windows related setup changes required for FILESTREAM. This requires built in administrator privilege. FILESTREAM settings in the SQL Configuration Manager (SQL-CM) represent this admin layer.
2-
The SQL configuration layer handles the setup changes required within the boundaries of the SQL instance. The SQL Admin can now use sp_configure/RECONFIGURE to handle this FILESTREAM configuration.
http://blogs.msdn.com/b/sqlserverstorageengine/archive/2008/03/03/filestream-configuration-and-setup-changes-in-sql-server-2008-february-ctp.aspx
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

My Management Agent Won't start

Hi Guys
I am installing Enterprise Manager management Agent ( 10.2.0.2.0) on Windows XP Professional (Service Pack2). The installation and configuration is successfull but the agent service does not start.
When I go to the command prompt to manually start the agent I get the following error:
C:\OraOemAgent\agent10g\BIN>emctl start agent
Oracle Enterprise Manager 10g Release 10.2.0.2.0.
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
The Oracleagent10gAgent service is starting..
The Oracleagent10gAgent service could not be started.
A service specific error occurred: 2.
More help is available by typing NET HELPMSG 3547.
Can anyone help ?

Check log/trace files ( http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/logging.htm#i1023926 )
'A service specific error occurred: 2.' basically means, one or more files couldn't be found. Issue 'net helpmsg 2'.
Werner

SNMP Solstice Master agent

Hi All,
I have a Subagent that talks with SNMP Solstice Master Agent on solaris 8. For the set requests sent by the Command line or Manager the Master Agent breaks the PDU into multiple set requests and then sends them one by one(with 1 variable at a time) to my Subagent.How can I avoid this break up of PDU at SNMP Master agent.
Thanks
Priya

Hello:
I created exactly as you specified. I.e weblogic.reg, weblogic.rsrc, weblogic.acl. But the issue I have is My weblogic snmp agent is listening on port 8061. Snmp demon on 161. So when I request the Snmp demon with OID of weblogic object. I am not getting the result also call is not reaching weblogic agent. Instead I am getting no such name or OID. So I am wondering why snmp demon is not forwarding the request to snmp demon.
Also Could you please explain the execution sequence of snmp demon and where you think I need to look at. Also please explain the constructs used in reg/acl/rsrc files.
Note:
I am using wls 6.1 sp2. So just my starting admin server. The enabled snmp gets started. Also I configured snmp demon so that when ever it gets started the weblogic server also starts. Also there is no issue in receiving traps.
Thanks in Advance.
Vijay

OEM Agent will not Start

Hello,
We have a OMS 11.1.0.1.0 environment running on Linux.
We have performed a Fresh Install (using OEM) of a 10.2.0.5.0 Agent to a HPUX server. We have tried 'emctl stop', 'emctl start' and 'emctl secure' commands. They all fail. We have performed a new discovery on that agent. We have removed the agent and performed a 2nd and 3rd Fresh Install. Nothing works.
We have a 15+ server environment that is working great.
Any ideas on why this agent won't start?
Thanks,
Bob Larsen

It didn't product a .trc file, need to adjust options in emd.properties
Do you see any problems below ?? Thanks ...
emctl.log
13849 :: Tue Feb 7 14:32:43 2012::AgentLifeCycle.pm: Processing start agent
13849 :: Tue Feb 7 14:32:43 2012::AgentLifeCycle.pm: EMHOME is /oemagenthome/agent10g
13849 :: Tue Feb 7 14:32:43 2012::AgentLifeCycle.pm: service name is
13849 :: Tue Feb 7 14:32:43 2012::AgentLifeCycle.pm:status agent returned with retCode=0
13849 :: Tue Feb 7 14:32:51 2012::AgentLifeCycle.pm:Watch dog processs id: 13856 exited with an exit code of 0
13849 :: Tue Feb 7 14:34:46 2012::AgentLifeCycle.pm: Exited loop with retCode=0
emagent.nohup
EMHOME ================== /oemagenthome/agent10g
--- Standalone agent
### Tue Feb 7 14:32:48 2012::agentTZRegion already exists in /oemagenthome/agent10g/sysman/config/emd.properties. ###
### Tue Feb 7 14:32:48 2012::agentTZRegion successfully validated. ###
----- Tue Feb 7 14:32:48 2012::Agent Launched with PID 13874 at time Tue Feb 7 14:32:48 2012 -----
----- Tue Feb 7 14:32:48 2012::Time elapsed between Launch of Watchdog process and execing EMAgent is 5 secs -----
--EMAGENT_MEMCHECK_HOURS=1
--EMAGENT_RECYCLE_DAYS=0
--EMAGENT_TIMESCALE=1
--EMAGENT_RECYCLE_MAXMEMORY=512
--EMAGENT_MAXMEM_INCREASE=1
### Tue Feb 7 14:32:48 2012::EMWD. Monitoring 1 Components. ###
### Tue Feb 7 14:32:48 2012::Env changes prior to agent launch recorded in /tmp/emctl.env.13837.diff2 ###
### Tue Feb 7 14:32:51 2012::EMWD Checking component processes... 1 ###
### Tue Feb 7 14:32:51 2012::EMWD. Checking Status for EMAgent 13874 ###
### Tue Feb 7 14:32:51 2012::waitpid(13874) reaped=13874, processStatus=0 ###
### Tue Feb 7 14:32:51 2012::reapChild pid=13874, status = 1, 0
### Tue Feb 7 14:32:51 2012::Status for 13874 : (1, 0), 99 ###
----- Tue Feb 7 14:32:51 2012::Checking status of EMAgent : 13874 -----
----- Tue Feb 7 14:32:51 2012::EMAgent exited at Tue Feb 7 14:32:51 2012 with return value 0. -----
----- Tue Feb 7 14:32:51 2012::EMAgent was shutdown normally. -----
----- Tue Feb 7 14:32:51 2012::Exiting watchdog loop

Snmp master agent won't start

Similar Messages

Maybe you are looking for