Deploy the Agent Via OEM GC

Similar Questions

• How to deploy the agent SNMP trap receiver

  How to deploy the agent SNMP trap receiver

  The integrations cartridge contains a SNMP Trap Receiver. You can search edocs.quest.com for 'receive snmp' where there are good to work with the agent explanations.

  David Mendoza

• Deploy the agent OS shell package?

  All,

  Is there a way to deploy the agent to the shell operating system package?

  for example

  We have puppets copy through and the installation of the fglam and it fits perfectly. I was hoping to copy down the bundle of BONES and also set up so I don't have to connect to the GUI.

  I figured it would be something fmscmd? But I had no luck yet.

  Thank you

  -Daniel

  Hello

  You can use fglcmd to do this. The command you are looking for is agent: deploy

  The following example would be deploying the package of the OS on a host named yourhost.yourdomain.

  ./fglcmd.sh cmd - agent: deploy - regex - host «yourhost.*' - «OSCartridge.*» IDPack

  You can then use the agent: create the possibility of creating the agent, then agent: activate to start.

  Details with all the different options for the cmdlets above are in

  http://eDOCS.quest.com/Foglight/56/doc/wwhelp/wwhimpl/common/HTML/frameset.htm?href=core/commandline-ref/index.php

  Thank you

  Chris.

• Deploy the agent EM12C initialization of the phase error sending software agent

  During the deployment of EM12C in the initialization stage - software agent agent sent to the error of host target
  The file to the SGD/m02 / midd/WHO/sysman/agent / 12.1.0.2.0 AgentCore226. Zip is copied to the host/m01 ADATMP_2013 on 192.168.165.83 - 03-28 _11-01-33 - error failure AM message: PROV - 16011: Auth fail
  Exit code: 0
  (1) the user authentication is oracle
  (2) the target users oracle sudo ls-l/root this command
  (3) the em can SSH connection to the target host

  Why are you using "-ignorePrereqs" parameter? You should not use this parameter to this than recommended by Oracle support or running in some soaps question. It will ignore any pre - req check and it is not recommended to ignore any failure pre - req controls, that can cause more problems with agent later.

  one) from ping target machine omshost
  Ping
  (b) of the Agent machine, run the below

  wget http://:/empbs/genwallet
  or
  wget https://:/empbs/genwallet
  Someone at - he of the foregoing should be connected to the machine of the WHO.

  Above two work then try installing the agent with on the "-ignorePrereqs" parameter and look in the more detailed error log file: agent_home/cfgtoollogs/agentdeploy/*.*

• How to deploy the agent for solaris

  I have download for Windows Server and the Agent for Solaris.
  The server for windows successfully installed, but how to install the agent for solaris?
  
  The downloaded file is hyperic-hq-agent-3.1.4-EE-504-sparc-solaris.gz
  and when I unzip, it's just hyperic-hq-agent-3.1.4-EE-504-sparc-solaris.
  
  Any help is greatly appreciated.

  Hi Nemesis

  The file extension must be tgz, gz not, maybe your browser has changed.
  You can use this command:

  tar - zxvf hyperic-hq-agent-3.1.4-504-sparc-solaris.tgz

  Then use «./hq-agent.sh setup' to start and configure the agent.

• Failed to deploy the agent packages.

  Hello

  I install the Fglam on one of the Sun solaris box, but unable to deploy agent packages on this box, that is to say - could not build an Agent of the packages.

  I'm trying to deployment package JavaEE_5_8_2_5.8.2 - 20121206 - 1602.gar

  Please suggest what measures need to take here?

  Thank you

  Vivek

  Additional and similar issues specified in the support site

  User Account Control problem https://support.software.dell.com/foglight/kb/86955

  Deployment with corrupt files https://support.software.dell.com/foglight/kb/114458

  I hope it's one of these use cases and you can resolve the issue under the KB articles

  https://support.software.Dell.com/Foglight/KB/114458

  Golan

• Deploy the model via command line

  Hi all,

  Is possible the deply a model via command line and set hostname and network?

  Thanks for your help

  PS: Do not forget a gift for the ghetto script repository

  You try to create a model of an existing VM using the CLI or the cloning of a virtual machine from a template?

  =========================================================================

  William Lam

  VMware vExpert 2009,2010

  VMware VCP3, 4

  VMware VCAP4-DCA

  VMware scripts and resources at: http://www.virtuallyghetto.com/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  VMware developer community

  If you find this information useful, please give points to "correct" or "useful".

• Agent deployment of MS 12.1.0.2 to pre - req Linux by the agent checks

  Deploying the agent software from EM to a Linux host running Oracle Enterprise Linux version 5.8 I am one of the sine qua non default check which indicates that the root / does not belong to the root. Since the Setup log
  
  INFO: --------------------------------------------------------------------------------
  INFO: Checking AgentBaseDirCheck
  It is a prerequisite to check if the agent home directory belongs to the user to install, all parent directories belong either installation user or root user and the root directory (i.e. "/") is the property of the root user.
  INFO: The value of AGENT_BASE_DIR is: / opt/EM_Agent.
  INFO: The value of ORACLE_HOME is:/opt/EM_Agent/ADATMP_2012-12-10_09-37-31-AM/prereq_stage/core/12.1.0.2.0
  INFO: The command get executed under this prereq is:/opt/EM_Agent/ADATMP_2012-12-10_09-37-31-AM/prereq_stage/core/12.1.0.2.0/perl/bin/perl /opt/EM_Agent/ADATMP_2012-12-10_09-37-31-AM/prereq_stage/core/12.1.0.2.0/sysman/install/CheckDirPermission.pl/opt/EM_Agent
  NEWS: Check the appropriate property on the base directory of the agent.
  INFO: Check if the base directory of the agent is owned by the oracle user agent and that its parent directory is owned by the agent user or root.
  INFO:...
  INFO: User name is: oracle & file owner is: oracle
  INFO:...
  INFO: ERROR: the root directory is not owned by the root user.
  INFO: The full version. The result of this review is: failure of < < < <
  
  INFO: --------------------------------------------------------------------------------
  
  Don't know how the / can not be owned by the root.
  
  Size of filesystem used Avail use % mounted on
  / dev/map/VolGroup00-LogVol00
  220G 63 146 G 30%.
  / dev/sda1 99M 23 M 72 M 24% / Boot
  tmpfs 2.0 G 620 M 1.4 G 32% / dev/shm
  
  
  [Mapper root@tomintoul] # ls - al
  Total 0
  drwxr-xr-x 2 root root 100 4 Dec 11:42.
  drwxr-xr-x 13 root root 7180 Dec 10 06:59...
  CRW - 1 root root 10, 62 4 Dec 11:42 control
  BRW - rw - 1 root disk 253, Dec 4 0 11:42 VolGroup00-LogVol00
  BRW - rw - 1 root disk 253, 1 Dec 4 11:42 LogVol01 VolGroup00
  
  
  Any help would be appreciated.

  Hello

  Please follow the provided below document that explains the problem.

  EM 12: Agent Installation fails with the error "the root directory is not owned by root user" (Doc ID 1380296.1)

  Kind regards
  Vincent

• Deployment Management Agent error

  
  Hi all

  I am agent deployment of management through the OEM console to the remote host.

  SGD is installed in the Linux machine while I'm deployment agent on UNIX machine. During this operation, I am getting error of authentication failure rather than give correct credentials (as below).

  "Make sure that the provided user name and password are correct. Make sure that the property that PasswordAuthentication is set to 'Yes' in the SSHD configuration file. »

  Could guide you please if there is another approach to deploy the Agent to management on the remote host?

  Thank you

  Dev
  

  -

  SSH user equivalence verification fails during the Installation of the Agent

  The most common reasons for verification of equivalence SSH user to fail are:

  • The server settings in /etc/sshd/sshd_config file do not allow ssh to user $USER .
  • The server may have disabled public key authentication.
  • The public key of the client on the server may be outdated.
  • You may not have spent the -shared option for shared remote users, or perhaps had this option for non-shared remote users.

  Check the setting of the server and re-run the script to set up the SSH user successfully equivalence.

  Alternatively, you can deploy the agent using the silent method. Please visit the doc Installation Oracle Management Agent in silent Mode

• Do I have to deploy the module plugin?

  Hi all.

  I install EM12cR3 and discover exadata & db.

  so I was sent on the db node agent.

  now, I'll try to discover exadata and db.

  so should I deploy xd & db module plugin on agent?

  Thanks in advance.

  Kind regards.

  By default, the Oracle Exadata (oracle.sysman.xa) and the database Oracle (oracle.sysman.db) plug-ins are deployed on your WHO during the installation of the WHO, and parts of the plug-ins needed to discover targets types are deployed to an agent when you install / deploy the agent. So, normally it is not necessary to manually deploy the plug-ins to an agent.

  You can ensure that your CMS has the latest versions of the plug-ins Oracle Exadata and database Oracle before discovering targets. From now on, the most recent version of these two plug-ins is 12.1.0.5.

  Note: The current version of Oracle Exadata Healthchecks plugin, which is optional, is 12.1.0.4.

  Related documentation:

  - Management of Plug-Ins

  - Discovered Exadata Database Machine

  Kind regards

  -Loc

• deploy the ear - invalid file file

  Hello
  I'm trying to deploy an ear file using ANT wldeploy tasks.
  
  The file contains
  -ejb (jar separate customer interfaces)
  -jpa persistence
  -webapp.
  
  The application server is 10.3.3
  
  Can I deploy the ear via eclipse with no problem on my local server.
  
  When I try and publish/deploy on a remote server I get an error [caused by: weblogic.deployment.EnvironmentException: duplicate units of persistence with name...]
  
  That's why agrees it to depoy via ant match. This method fails even on my local server. Say the (ear) file is not valid.
  It seems that the action "publish" in eclipse is making changes on the ear that the simple file-> export-> does not ear in eclipse.
  
  I then tried to pack the environment in the structure of directories of split (so far, I used just the standard eclipse - projects java/j2ee configuration).
  This attempt failed at the wlappc stage. ArrayIndexOutofRange exception.
  
  Any ideas?
  
  Thank you
  Michael

  Thanks for this stacktrace, it helps a lot.

  It seems that WLS is certainly see both persistence.xml files and reports the error.

  Caused by: weblogic.deployment.EnvironmentException: duplicate units of persistence with the name myapp_persistence in the field of myapp application.

  Then it is to point out the locations of the PUs in double, is to see (it's very useful diagnostics, I have not seen this before):

  First location of CENTRAL unit: file:/var/opt/oracle/middleware/user_projects/domains/ecm_domain/servers/AdminServer/tmp/_WL_user/myapp/upzgei_/lib/myapp_persistence.jar_.
  Second place Pu: file:/var/opt/oracle/middleware/user_projects/domains/ecm_domain/servers/AdminServer/tmp/_WL_user/myapp/upzgei_/APP-INF/lib/myapp_persistence.jar_

  For me, it looks like the packaging step in Eclipse, is updated the same module in two separate places within the file EAR - one being the standard Java EE 5 app library directory (/ lib) and the second being the application owner WLS directory library (/ APP-INF/lib).

  Look at how you have your setup of library/project in Eclipse dependencies - WLS fully supports the standard directory/lib to Java EE 5, so you can put some bookstores application level, you want to share between the modules of your application in there and be confident that it will work - so that you only have a single present myapp_persistence.jar in the EAR file.

  Hope that helps.

  see you soon
  -steve-

• Deploy the fglam and agents using puppets?

  Hello

  I was wondering everyone deployed fglam or other agents through puppets?

  Any information you share will be great.

  Thanks in advance

  GS

  Hey, GSA,

  Sorry I'm more the Foglight person in my company I only get to see come to the forums to help out a colleague.

  Yes, we have entirely puppets running for our fglams and Wssf. It was boring, you're linux Debian or company founded? Quest unfortunately does not support standard deb/RPM, perferring an installer of owner. If you need make your own. I am happy to send you a copy of our 64 bit RPM. It's about 120 megs. Just throw it in your rest and you should be good to go. Ideally if you need to build your own to make sure that you can keep up-to-date with the latest agents and pieces of fglam.

  Discover this - http://blog.yo61.com/building-rpms-from-ruby-gems-with-fpm.html

  I recommend the staging of your cartridges in advance when you build the RPM. For us, it was worth the extra space in the RPM to compensate for the time that should be a cartridge via the script on the network. Using this method I have cartridge legacy/IC/Apache and customized all in place so I can save some deploy times. It is somewhat important in larger environments due to a problem known in Foglight on the deployment of wagons/creation and activation of agents the time it can take is VERY random.

  In our tests, we had 500 machines archive on a clean server FMS (5.6.4 at the time). Some would take 2-3 minutes to complete, some would take 20! PSO went to dev and they have never been able to understand why delays random when you start the agent script check in the back to the rear. But since you can't count on it fill inside your run time of the puppets you should reduce the time it takes.

  Don't forget that Foglight is not updated with the scale/config friendly management. They store a lot of config data in databases and use IDS in their configuration files that are made by ther FMS. Thus, it can be difficult to handle most things. You end up having to write a lot of execs once. Glad you sent a copy of our manifesto if you wish. I have just to sanatize it. I found it easier to do was run as a 'touch' inside a folder in the % fglam % of indiecate installation directory which have executed elements.

  One thing you might want to, is your vm.config scheduled start at the fglam. Then will happen. Otherwise you; He's eventually do custom made for your ID Agent Foglight who ends up being a nightmare. You can apply your logic of setting JVM at the time of installation. It won' just manageable tbe.

  You can create custom providers to exploit different groovy scripts, but honestly this isn't worth it unless you might be working for Quest PSO. Be sure to place a 'idea' to get Foglight more user-friendly automation, configuration management and scaling tools. If enough of us let them know that these scalabiltiy is a factor for us they could get it in next Foglight.

  Another thing to remember as you automate you must ensure your FMS travels and erase data from all machines on its own topology. In my first POC run, I forgot about it and after about a month, the FMS ran terrible everything by supporting only 5000 guests. After I cleaned the topology and reset, there great. Since then, I just rule the kickoff to 4 hours to clean up the obsolete data and it has worked great since I did that.

• problem with credentials named during the agent deployment

  Hi gurus.

  Yesterday, I have deployed an agent on a host of test server and it worked like a charm.

  Except that...

  I used the oratest user under the name of credentials... This meant (I think) that when it came to detect different targets on the host to monitor, OEM could not see that those who belonged to oratest (couldn't see oratest database).

  It was not ideal because it is has several databases I want to monitor on this server.

  So I uninstalled everything and now trying to deploy an agent once again, using this https://docs.oracle.com/cd/E24628_01/install.121/e22624/install_agent.htm#EMBSC184

  However, I am now stuck on the choice of a credential named... which user should I choose for this? I need to create a separate, "oem" user to do all this? I'm not even sure that the choice of the user oratest was a mistake... I'm more than a little confused and would appreciate some advice kindly.

  Version: 12.1.0.4.0

  RHEL 6.5

  Thank you

  CAI

  ALL THE:

  I learned that in addition to plugins, make sure (for the discovery of the db) that your Oracle home must be located in the oratab

  In addition, if you have sort of a default location for your listener.or according to the $TNS_ADMIN, then it must be placed in your agent owner bash_profile.

  Above and outside.

• Impossible to mount the persistent drive - trying to deploy the first pool of offices and do not. -View composer agent initialization failed

  Hi all

  Complete errors:

  Discover the State of the agent (22) composer initialization error: cannot mount the persistent drive. Please check the VM parent if an existing drive uses the same drive letter. (expected 0 seconds)

  State matching: matching...

  By:xxx.xxx.xxx.local set up

  Attempted theft by:

  Error commissioning took place for Machine xxx: View Composer agent initialization failed

  I am currently deployment of VMWare view for the first time in a test environment and have hit a problem I have not been able to get around despite several searches on google and trial and error.

  Hoping that someone here could suggest something.

  View the VMWare versions are all 6.0.1.

  vCenter is on a device.

  VMWare view connection manager is on a 2012 R2 VM server.

  VMWare view dial is on a separate server 2012 R2 VM.

  I have a 2012 SQL on a separate server 2012 R2 VM Server installation.

  SQL databases have been set up for the composer to be able to reach it, it uses ODBC 64-bit via SQL Server Native Client 11.0.

  I tried troubleshooting by exchanging 32-bit, but this is not connected, it seems so 64 bit is correct.

  I have a windows 7 64-bit Enterprise Edition VM under my Golden image. There are VMWare tools on it and the VMWare agent on it.

  The virtual ipconfig/release performed top machine, he was then stop and a snapshot taken as my source.

  The problem is that when I go to deploy a pool of offices, I get the above error.

  If I connect to the VM created via vCenter readers persistent and temporary show very well.

  Based on the error, I tried different settings such as change the path for the reader of DVD VMs of D: to Z:, spread unique persistence and the temporary disks on multiple data-stores or data stores and even remove the drive of DVD of VMs completely. I have also looked at newspapers under composer view but find nothing to explain the behavior.

  SQL Server seems to work for configuration through the error logs and virtual machines are created and added to AD as expected.

  I must point out that the virtual machines are as linked clones.

  Can anyone offer a clue as to the cause or something, I can check it please, did everything I can think and Googling the error does not come to the top with something useful so far.

  Thank you

  IF you use an Agent 6.0.2 Please downgrade 6.0.1 agent and let me know the results

• Deploy the OEM of XP to several PC image

  Hi people,

  I have a Dell PC with XP PRO OEM installed on it. I have another 9 PCs (same model), all of which have their own XP PRO OEM stickers on the side.

  It's ok for me to:
  The first PC from Dell using a freeware tool, imaging image to deploy the image on all other Dell PC, then use the tool from Microsoft to change the product key OEM to that respective on the side of the case, and then reactivate it?

  I must point out that the first Dell does not have a Dell factory install XP, but one that I made myself (using the button on the side of the case and my own XP Pro OEM CD)

  Thank you

  Hi Jonnytabpni,

  Using the sysprep in XP utility, you can deploy the image on several PC. You should have no problem using an OEM installed OS on other OEM computers and enter the product key manually on install. However if you sysprep a key retail and attempt to push than to machines OEM and OEM keys, you will encounter issues.

  I hope this helps. Let us know if you have any additional questions.

  Shawn - Support Engineer - MCP, MCDST
  Microsoft Answers Support Engineer
  Visit our Microsoft answers feedback Forum and let us know what you think