Managing Servers with IP in different environments
M
Mike Tompkins
started a topic
over 9 years ago
In a managed services kind of environment, often different environments/customers may have
the same private IP addresses. In this case, how does the eG manager function?
Best Answer
A
Administrator
said
over 9 years ago
The
eG manager can use the "nick name" provided at the time of installation
of the agents for this purpose. Agents installed on the systems with the same
IP addresses must have different nick names assigned to them. When adding these
systems for monitoring, the nick name as mentioned on the eG agent must be specified in the eG admin
console.
By default, the eG manager automatically does a reverse mapping of IP
address to nicknames, so just assigning different nicknames for the agents is
NOT sufficient for the eG manager to be able to differentiate between these
systems.
Go to Admin -> Settings
->Manager ->General Settings.
Select Yes for the “Automatically map IP address of agents to nick names”.
1 Comment
A
Administrator
said
over 9 years ago
Answer
The
eG manager can use the "nick name" provided at the time of installation
of the agents for this purpose. Agents installed on the systems with the same
IP addresses must have different nick names assigned to them. When adding these
systems for monitoring, the nick name as mentioned on the eG agent must be specified in the eG admin
console.
By default, the eG manager automatically does a reverse mapping of IP
address to nicknames, so just assigning different nicknames for the agents is
NOT sufficient for the eG manager to be able to differentiate between these
systems.
Go to Admin -> Settings
->Manager ->General Settings.
Select Yes for the “Automatically map IP address of agents to nick names”.
Mike Tompkins
In a managed services kind of environment, often different environments/customers may have the same private IP addresses. In this case, how does the eG manager function?
The eG manager can use the "nick name" provided at the time of installation of the agents for this purpose. Agents installed on the systems with the same IP addresses must have different nick names assigned to them. When adding these systems for monitoring, the nick name as mentioned on the eG agent must be specified in the eG admin console.
By default, the eG manager automatically does a reverse mapping of IP address to nicknames, so just assigning different nicknames for the agents is NOT sufficient for the eG manager to be able to differentiate between these systems.
Go to Admin -> Settings ->Manager ->General Settings.
Select Yes for the “Automatically map IP address of agents to nick names”.
Administrator
The eG manager can use the "nick name" provided at the time of installation of the agents for this purpose. Agents installed on the systems with the same IP addresses must have different nick names assigned to them. When adding these systems for monitoring, the nick name as mentioned on the eG agent must be specified in the eG admin console.
By default, the eG manager automatically does a reverse mapping of IP address to nicknames, so just assigning different nicknames for the agents is NOT sufficient for the eG manager to be able to differentiate between these systems.
Go to Admin -> Settings ->Manager ->General Settings.
Select Yes for the “Automatically map IP address of agents to nick names”.
-
Finding eG Agent version
-
Delete and Acknowledge alarms
-
Updating nick names
-
Changing IP address of a monitored component
-
Changing IP address of remote agent and external agent
-
Inside view metrics are not collected by eG
-
Error 1067
-
Agent stopped running
-
eG agent auto-startup
-
Remote agent connection issue
See all 77 topics