Domain Agents and E6900 with multiple NICs.
Hello,
I have some issues configuring Sun management Center 3.6 (and 3.6.1) on a network with this characteristics:
2 x E6900 (with 2 Domains each one)
1 x v210
The Server Component of Sun Management Center is installed on the v210. In this machine are installed the Platform Agents of the 2 System Controllers of the 2 E6900.
Each domain has installed de Sun Management Center Agent.
The network configuration of the Domains is this:
Each domain has 3 NIC on 3 different network interfaces, and each NIC has its own hostname. One of this NIC is destinated to the administration network to be used for the Sun Management Center. This nic, as I said before, has its own hostname but it its different of the nodename (the node name is the same as the public interface of the domain, not the administration interface).
The Domains does not use DNS, and the information included on the /etc/hosts is related to local NICs and the NICs of the other Domains, but anyone contains the NIC of the admin interface of other domain nor the NIC of the v210.
The v210 does not has DNS neither, and has only their own information on /etc/hosts.
All Domains has Solaris 9, and v210 has Solaris 10.
Basically the problem is:
"The Domain Agents cannot communicate with SunMC Server", when I manually add each agent. The discovery process doesn't work neither.
I checked the domain-config.x of one domain and it shows:
agent = {
agentServer = "venwas1"
logicalAddressMode = "ip"
snmpPort = "1161"
}
"venwas1" is the hostname of the public interface, nor the administration interface.
I changed the value for the hostname of the administration interface with no success; then changed for the ip address of the administration interface; and no success neither.
The default platform agent works, but does not appers with the corrent icon on the SunMC console. Its appears like a folder icon, and the documentation said that the Platform Agents is represented with a specific Icon.
Please, anyone can help me ?
Thanks in advance.
# 1
Hi Alejandro,
> I checked the domain-config.x of one domain and it
> shows:
>
> agent = {
> agentServer = "venwas1"
> logicalAddressMode = "ip"
> snmpPort = "1161"
> nwas1" is the hostname of the public interface, nor
> the administration interface.
>
> I changed the value for the hostname of the
> administration interface with no success; then
> changed for the ip address of the administration
> interface; and no success neither.
If you just change the hostname or IP, but don't do anything else, it won't work as the Agent has already created security keys for that old entry and needs to be reseeded. Change the entry to the IP that's on the same network as your SunMC Server, then run this command on the Agent while it's turned off:
/opt/SUNWsymon/sbin/es-run base-usm-seed.sh -s <SEED> -c agent
..replacing <SEED> with the same seed/password you used on your SunMC Server. Then start the Agent back up, wait for it a couple minutes, and try to make an icon for it again.
> The default platform agent works, but does not appers
> with the corrent icon on the SunMC console. Its
> appears like a folder icon, and the documentation
> said that the Platform Agents is represented with a
> specific Icon.
If the icon is incorrect then your SunMC Server is missing some files (or you've found a bug). You'll want all these addons installed on your Server:
Dynamic Reconfiguration for Sun Fire High-End and Midrange Systems
Sun Fire Midrange Systems Platform Administration
Sun Fire Midrange Systems Domain Administration
If you think you may be missing some (look in /var/opt/SUNWsymon/install/install.[timestamp] to see how you answered questions during your last install) you can run /opt/SUNWsymon/sbin/es-inst again and point it to your distribution media and it will only ask about packages that may be missing. If you do end up adding in some of the Midrange addons then a simple Console restart should refresh your Platform icons.
Regards,
Mike.Kirk@HalcyonInc.com
http://www.HalcyonInc.com
# 2
Hello Mike,
Thank you very much for your support.
Your solution solves my problems but let me a new one.
Currently the Platform Agents Icon and Domain Agents Problems was solved.
I have 2 Platform Agents installed. The default for one 6900 and a second instance for other 6900. Both was working before (with bad icon); but now, the aditional instance stop working.
I found this on the cfgserver.log associated with the Platform Agent Instance:
"Agent needs to be resseded with correct password."
Using your suggestion for ressed didn't work for this case. I deleted and recreate the instance again but without success.
I have a question: The SEED value that I'm using has 11 characters (client requirement). This works fine for the default platform agent and all domain agents; but I don't know if this could be a problem for the platform instance.
Please can you help me.
Again, thanks for your support.
Bets Regards,
Alejandro Galue
