This eG agent will automatically report metrics to the eG manager from which the agent package was downloaded. Also, the hostname of such an agent is automatically set as its nick name. In a multi-tenant setup, a hostname may not be unique across tenant environments. To avoid nick name duplication, eG Enterprise automatically employs the following algorithm when assigning nick names:.
If this nick name is also taken, then eG will increment the number 0, which suffixes the hostname, by 1, and will try to assign the resultant string to the eG agent,. This way, eG will keep incrementing the number suffix until an unused string is found. Such a string will finally be assigned to the agent as its nick name. If you are downloading an agent for installation on an imaging system e. If this is done, then after the agent so downloaded is installed, setup will stop that agent.
In such a case, you need to do the following:. Privacy Policy Terms of Use. Account Settings Logout. All Files. Submit Search. You are here:. You can download the tar file and iAgent script from the eG web site , and manually run the iAgent script on the target Linux host to install the eG agent. This approach is ideal if you want to deploy AIX agents for a single organization - i. The eG agent software for AIX is provided as a packaged application.
You can download the agent package for AIX from the eG manager console , extract the contents of the package to any folder in the target host, and silently run a setup script on that host to install and configure the agent at one shot - i. If you are deploying eG Enterprise for SaaS , then it is mandatory that your tenants use this approach to install and configure the eG agents in their environment. Both these approaches are discussed in this section. You can download the tar file and installation script from the eG web site.
To know how, refer to the eG Quick Installation Guide. Note: The agent installation must be performed from a super-user account. The name of the super-user should not exceed 8 characters.
Enter the name of the eG user [egurkha]: Note: If the agent is being installed on the same system as the manager, the eG user configured for the agent should be the same as that used for the manager. Enter the group to which the eG user is to be associated [egurkha]: Next enter the path to the directory in which the eG agent will reside. Would you like the eG agent to auto-restart on system boot-up? These components must be installed for the agent to function properly. Following this step, the eG agent components are extracted and stored.
For that, the administrator should do the following: Login to the system hosting the eG manager. Each zip file is an agent package that corresponds to every operating system on which an eG agent can be installed. The tenant can now proceed to install the eG agent using the procedure discussed hereunder: Using a browser, connect to the URL of the eG management console. Login to the eG management console using the credentials you used corporate email ID and password to register with eG Enterprise for SaaS.
Figure 22 : eG's internal agent packages available for download from the eG manager console Note: Though the eG management console lists the packages meant for agent-less, agent-based, and external monitoring in separate pages, the procedure to download and install these packages remains the same across monitoring approaches. If the host to which you have downloaded the package is the target AIX host for agent installation, then login to that AIX host as super-user.
On the other hand, if you want to install the eG agent on a host different from the one on which the package has been downloaded, then first copy the agent package to any location on the target AIX host.
Then, login to that host as a super-user. If that tenant later logs into the eG management console using the registered credentials email ID and password and downloads the agents, each agent so downloaded is automatically tagged with that UAID.
The downloaded agents, once installed and configured, will automatically start discovering applications on their respective hosts. To avoid nick name duplication, eG Enterprise automatically employs the following algorithm when assigning nick names: At the time of setting the hostname of an agent host as its nick name, eG first checks if that hostname has already been assigned to any existing agent.
If it finds that the hostname has already been taken, then it will attempt to assign the FQDN - the fully qualified domain name - of the agent host as the nick name. In the process, if eG finds that the FQDN is also in use, then it will break-down the FQDN into smaller strings, and try to assign each of these strings, one after another, to the agent. If all these FQDN strings have already been assigned to other agents, then the eG agent will suffix the hostname of the agent host with the number 0, and try to assign this as the nick name of the eG agent.
For instance, if the hostname of the eG agent host is winpc, then the nick name assigned to that agent will be winpc0.
Note: In a SaaS deployment, if a tenant manually adds components to be monitored by an eG agent, then you should only assign that agent's nick name to each of the components it monitors. Check to see if the Nick parameter in that file is set to any value.
On the other hand, if the Nick parameter has a value, it indicates that a nick name was set for the eG agent. Also, stop the eG agent. Did you mean:. Sign In. Netbackup Client installation on AIX 7.
Go to solution. Hello Experts! Has anything changed from the perspective of Netbackup client installation on AIX 7. I am installing agent from a HPUx Master server. All forum topics Previous Topic Next Topic. Accepted Solutions. Marianne Moderator. Handy NetBackup Links. Thank you. Post Reply. Preview Exit Preview. You must be signed in to add attachments. Additional options Associated Products. You do not have permission to remove this product association. Related Content.
0コメント