SunMC agent on a multihomed machine, how to configure agent?
hi,
I have a sun bladed machine with four networks cards. I Need that the agent listen for one IP, but i read that the only way to do this is changing the name of a machine with "uname -s name_of_my_ip_interface", because the agent only listen in miultiip machines for the ip that have the name of the machine.
for example in my /etc/hosts
10.11.22.33name1
172.33.22.3name2
162.235.44..11 name3
Result of "uname -n"
name1
I need that my agent listen for the 172.33.22.3, ok, if i read the sun management center documentation, i need to make:
1-. Stop agent
2-. uname -s name2
3-. Strart agent
Is this the only form?, i don磘 change the machine name because there are other services that depend for it.
Hoe can i make it?
Thansk from spain
[828 byte] By [
kerulea] at [2007-11-26 15:35:30]
# 1
what we do is put the hostname of the interface we want to use in /var/opt/SUNWsymon/cfg/domain-config.x. domain-config.x should contain entries with "name1" and we replace that with "name2"
we have automated this process to first do a traceroute to the SunMC server, catching the warning message of multiple interfaces found. There he says which interface he's going to use, we'll match that in /etc/hosts and we then use the hostname in domain-config.x. After that we need to reseed the SNMP security keys.
# 2
Thank Quiksilver,
We try to do like this.
Please, one question more that i cant resolv it. In a sun blade 2500, i am trying to install Sun MC agent layer, after that the es-inst, i run a es-validate and obtain:
Sun Management Center Processes:
-
SUNMC SERVICESTATUS
-
Sun Management Center AgentRunning.
Platform AgentNot Running.
Platform instance Inueva Not Running.
-
and orders things. Because this, my Sun MC server that is running in other machine cant communicate whit this machine.
I dont know why my platform Agent is not running, how cant i resolv this problem?, which log must i read? any ideas?
very, very thanks and sorry for my poor english
# 3
A platform agent is to remote manage/monitor the SNMP agent on another host (like a E10K/E25K etc). The problem you are facing is not because of your platform agent not running.
If your SunMC agent is runnin fine, then you should be able to create that SunMC agent object in the console.
U need to look at the topology.log under /var/opt/SUNWsymon/log as well as the server.log and the cfgserver.log.
Also check to see if you are giving the right port during the creation of this agent object in console.
As a test try to create this SB2500 object as a simple ping object which will assure you that the network connectivity between the server and this host is fine. Then try to modify the same to a SunMC agent host and see the above mentioned logfiles for clues about what the actual problem could be,
