Agent on Solaris 10
Hello,
we are running SunMC 3.5up1 on Solaris 9. I installed a new server with Solaris 10 and the SunMC 3.5up1a Agent in the global zone. The agent starts fine, but I can't connect from SunMC server. I only got warnings on snmp-reports in agent.log.
How can I debug this problem in a more detailed way ?
Is it possible to run this SunMC release combination ?
Many thanx for any hint,
cu
David
PS: I have to run the agent on Port 1161 - the installer don't let me choose 161, also if this port isn't in use.
[558 byte] By [
dferch_de] at [2007-11-26 5:59:31]
# 1
Hi David,
This sounds like a standard security problem:
a) are you sure you specified the same "seed" string as you use on your 351 Solaris 9 Server?
b) is this new Sol10 system on a different network?
c) can you make a "SNMP Ping" type icon for it?
> I can't connect from SunMC server. I only got
> warnings on snmp-reports in agent.log.
You should see a SNMP Report in agent.log from "esmaster" like this, a few minutes after starting the Agent:
SNMP Report: <IP>:<N>-<N>-<N>-<N>-esmaster- (rest of line deleted)
If you don't see the line with "esmaster" in it, your Agent did not sync security with your Server, so you will not be able to make a regular icon for it.
> Is it possible to run this SunMC release combination
> ?
351 and 351a are very similar other than a patch set and Solaris 10 support (from what I can see). But it's still possible that it's not forwards compatible... I haven't tried it myself.
> PS: I have to run the agent on Port 1161 - the
> installer don't let me choose 161, also if this port
> isn't in use.
As long as you remembered to specify port 1161 when you made the Solaris 10 Agent icon you should be fine. Is there any chance that the port is blocked by a firewall?
Regards,
Mike Kirk
# 2
Hello Mike,
> a) are you sure you specified the same "seed" string as you use on your 351 Solaris 9 Server?
Yes, it's the same one.
> b) is this new Sol10 system on a different network?
Yes, it is. No NAT is used, but it's a firewall between server and agent.
> c) can you make a "SNMP Ping" type icon for it?
I'll check this tomorrow.
> SNMP Report: <IP>:<N>-<N>-<N>-<N>-esmaster- (rest of line deleted)
>
> If you don't see the line with "esmaster" in it, your
> Agent did not sync security with your Server, so you
> will not be able to make a regular icon for it.
As you wrote I found two entries of this line (with esmaster and espublic) in all other agent logs after first connection to/from server layer. These agents (Solaris 8/9) are using port 161 - not the new 1161.
> 351 and 351a are very similar other than a patch set
> and Solaris 10 support (from what I can see). But
> it's still possible that it's not forwards
> compatible... I haven't tried it myself.
I hoped so, because I also could run 3.5 server with 3.5.1 agents before upgrading to 3.5.1 server.
> As long as you remembered to specify port 1161 when
> you made the Solaris 10 Agent icon you should be
> fine. Is there any chance that the port is blocked by
> a firewall?
I entered the port 1161 on adding the agent through the console. Maybe the firewall is responsible for the problem, but the traffic passes because of the logfile entries. I'll check to add an explicit new udp service tomorrow.
> Regards,
> Mike Kirk
Thank you for explaining the snmp report stuff,
cu
David
# 3
Hello Mike,
> As long as you remembered to specify port 1161 when
> you made the Solaris 10 Agent icon you should be
> fine. Is there any chance that the port is blocked by
> a firewall?
That was the problem: I forgot to define a new allowed udp-service - after doing so, it works fine.
> Regards,
> Mike Kirk
cu
David
# 4
When I try to install the agent in my global zone I get the following error message:
XML shared object library not accessible
Exiting Sun Management Center installation.
I have installed the solaris 9 SunMC patches on my server (SunMC update3.5.1a)
Any ideas?
Thanks
Steve
