Home Forums OS X Server and Client Discussion Questions and Answers LOM – Lights Out Management 10.5.3 – Network Status always “Down”

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #372952
    samoir
    Participant

    Hi there
    Im running an Intel XServe 2008, 10.5.3, and have it setup utilising dual ethernet ports and LOM.
    On my local Mac Pro im using Server Admin Tools (10.5.3) as the management interface, and also Terminal sometimes.

    Everything works fine, with Server Monitor and Server Admin, EXCEPT FOR ONE THING : Under the Network tab of Server Monitor the “Link Status” is always stated as “Down”, even though the server is transmitting and receiving perfectly normally.

    Eth0 is used for the primary machine IP, LOM is running on Port2 using a unique LOM IP for the machine.

    Does anyone know why the link status shows down all the time??? It seems a minor but fairly annoying “glitch” given the machine is working normally, id rather this information is accurate. Id be greatful if anyone could help.

    thanks in advance, samoir

    #373756
    drstaind
    Participant

    Hi there,

    I am having an identical issue with an Intel XServe 2008, now running 10.5.4.

    Dual Ethernet – eth0 Primary | eth1 LOM

    Machine appears to function perfectly, aside from the same glitch that samoir has mentioned.

    Somoir – is this still an issue for you or did you find a resolution?

    Cheers,

    W

    #373760
    samoir
    Participant

    no relief yet, i still have the same issue, even after upgrading to 10.5.4 : Link Status: Down

    Seems really weird as using Server Admin its polling the Network throughput, but Server Monitor seems like everything else is correct except for this on the Network Tab.

    Frustrating.

    #373774
    Dave Hagan
    Participant

    I have two new Intel Xserve 2008 models. I do not have dual ethernet ports setup. I read here or on Apple Discussions that having two ethernet ports configured each with their own IP address in the same subnet would reduce performance? I was looking on Friday for this information to see if I read that right. Anyway, I’m interested in trying this out. I am a Cisco shop and found that Cisco’s LACP (link aggregation protocol) was a little different than I thought it work…are you running your Xserves on Cisco switches? Another annoying glitch — at least I think it’s a glitch — is that Server Monitor shows “Invalid user name or password” on the Xserve itself using localhost or 127.0.0.1. If I use Server Monitor on another server with the Xserve’s lights out IP address, it give me the status no problem. Strange!

    #373775
    samoir
    Participant

    hi
    Our setup is not via a Cisco router.
    However we are using dual ethernet ports, one for network connectivity (en0), one for LOM (en1)
    The 1st IP, the actual IP of the machine (en0) is on 210.XXX.111.XXX, subnet 255.255.255.224, etc.
    The 2nd IP, for LOM (en1), on a different subnet and IP range, as 192.168.XXX.XXX, under 255.255.255.0

    You might find the above useful, i dont know.
    this was what i understood to be the best configuration for LOM, as there would be conflicts if done any other way.

    #375774
    ThaboZ
    Participant

    On different sources I’ve read that unplugging the power from the xserve for about 30 seconds will reset the LOM chip and solve any LOM related issues.
    Please note that you will have to shutdown the server before unplugging the power leads and you will have to setup LOM under server monitor again.

    #376024
    cyapple
    Participant

    😮

    Has this been resolved? I am seeing this too. Does the unplug/reset work? and is it the only way?

    Thanks.

    CY

    #376046
    tlarkin
    Participant

    LOM on the Xserves uses a specific port that needs to be open for it to work.

    623 UDP Lights-Out-Monitoring – Used by Intel Xserves’ Lights-Out-Monitoring (LOM)

    source:

    http://support.apple.com/kb/TS1629?viewlocale=en_US

    #376532
    samoir
    Participant

    @tlarkin – LOM is working. THe post is about the Network Status being incorrect, (the error is being viewed by Server Admin Tools interfaces – and everything else is working as it should, apart form the network interfaces error.)

    #376533
    samoir
    Participant

    The network interfaces error has been fixed now. Both show as “UP”.

    Well at least after applying the software update. My system is running the following at both ethernet interfaces show as up:
    OS X Server 10.5.7, XServer LOM Firmware Update 1.2, and using Server Admins Tools 10.5.7

Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.

Comments are closed