Server Monitor not working

[orris]

Seen this several times, but all suggestions I’ve seen are ineffective…and not related to 10.4.9

Server Monitor works on a local server ONLY with 127.0.0.1 or localhost
Using the ip address or hostname gets “Failed to contact server”…

Any hints?

Not a DNS problem…DNS is fine…else LDAP and Kerberos would be throwing fits!

[orris]

Yep.

But I should also say that I’ve had it on a G5 and a G4 and it never worked there either…..

Curious….

[dblezard]

I have the same issues. Server Monitor will only work on the Xserve itself when talking to 127.0.0.1.

Server Monitor on the new Intel Xserves seems to be tied to the Lights Out Management somehow. See [url]http://docs.info.apple.com/article.html?artnum=304897[/url].

I’m trying to get some answers from Apple on how this is now supposed to work since I don’t really want the LOM features at the moment, just working Server Monitor.

[deemery]

Isn’t this new Apple note relevant?

http://docs.info.apple.com/article.html?artnum=106830

dave

[nob]

I have another problem with LOM remote. Server Monitor gets connected to all LOM IPs (using same Interface as for Server-IP) only in the same Network-Subnet. If i try to connect outside from another subnet, the LOM didn´t answer. Gateway IP in LOM – Settings is right, same as for the Server itself.

Strange Software…

[orris]

Sorry to have missed all the chatter…Been busy and there are so many other problems

I cannot connect with the server monitor to a machine with a working DNS using anything other than 127.0.0.1.
I would assume that that machine would know who it was and had a FQDN with reverse lookup.
I’ll be honest, in my last 15 months experience with the Xserve, nothing has worked as advertised. This has been especially true of the GUI apps. Without web sites such as AFP548, and their help, everything would work about as well as the Server Monitor.

But I digress…

from
http://docs.info.apple.com/article.html?artnum=106830

“The reason for this is that Server Monitor requires either:
that the IP address of a server be resolved using a DNS name assigned to the server’s IP address,

or
that one of several other specific actions be taken, which include using “localhost” as the server’s hostname or making modifications to NetInfo.”

Are they claiming here that Netinfo needs to be modified? In my case, clearly the first of these claims did not work.

[orris]

OK Folks….
Here’s the problem….

As Joel had pointed out in his article on LOM, you MUST install the Server Admin tools from the DVD’s.
DO NOT THINK THAT THE SERVER ADMIN TOOLS THAT WERE PRE-INSTALLED WILL WORK!!!!
Furthermore, you need to have a FQDN (which can be local) on the subnet for the LOM ethernet address.

Why does Apple like to waste our time?!?
One would think that at least a WORKING COPY would be installed at the factory!

Thanks again for the site

Regards

[hdjong]

On the apple discussions forum are a few postings about this problem. The Lights Out Management and Server monitor works if configured correctly (local on Xserve and remote) but after a certain time it is not possoble to connect to the LOM from remote connection (TCP IP). It only works on the local Intel Xserve with localhost server setting in the Server Monitor. After a shutdown, disconnect of the powercord for more than 10 sec. and turn on the Xserve, it is possible to connect to the LOM (for a few hours). See next thread.
[url]http://discussions.apple.com/thread.jspa?threadID=940740&tstart=0[/url]
I think it is a problem in the LOM module. It looses network connection.

[Author]

Posts