Lost or delayed heartbeats - Veritas Cluster Server

This is a discussion on Lost or delayed heartbeats - Veritas Cluster Server ; Hi there I was wondering if anyone has seen anything like this before - continuously echoing to the console on one of the servers in a two-node cluster? One of the other symptoms is that when one server has the ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Lost or delayed heartbeats

  1. Lost or delayed heartbeats


    Hi there

    I was wondering if anyone has seen anything like this before - continuously
    echoing to the console on one of the servers in a two-node cluster?

    One of the other symptoms is that when one server has the public network
    pulled on it, the other goes offline too.

    Any advice appreciated.

    Feb 19 23:41:10 host-db1a unix: LLT:10023: lost 48 hb seq 58488 from 2 link
    1
    Feb 19 23:41:10 host-db1a unix: LLT:10019: delayed hb 2450 ticks from 2 link
    0
    Feb 19 23:41:10 host-db1a unix: LLT:10023: lost 48 hb seq 58488 from 2 link
    0
    Feb 19 23:41:20 host-db1a unix: LLT:10019: delayed hb 950 ticks from 2 link
    1


  2. Re: Lost or delayed heartbeats


    Did you ever receive a solution to this problem?

    Craig

    "Graeme Hay" wrote:
    >
    >Hi there
    >
    >I was wondering if anyone has seen anything like this before - continuously
    >echoing to the console on one of the servers in a two-node cluster?
    >
    >One of the other symptoms is that when one server has the public network
    >pulled on it, the other goes offline too.
    >
    >Any advice appreciated.
    >
    >Feb 19 23:41:10 host-db1a unix: LLT:10023: lost 48 hb seq 58488 from 2 link
    >1
    >Feb 19 23:41:10 host-db1a unix: LLT:10019: delayed hb 2450 ticks from 2

    link
    >0
    >Feb 19 23:41:10 host-db1a unix: LLT:10023: lost 48 hb seq 58488 from 2 link
    >0
    >Feb 19 23:41:20 host-db1a unix: LLT:10019: delayed hb 950 ticks from 2 link
    >1
    >



  3. Re: Lost or delayed heartbeats


    The reason for this is that two of your heartbeat connections are sharing
    the same ethernet segment. All heartbeats must be completely separate (i.e.
    separate hubs/switches or VLANs) with no cross-pollination at all.

    As to the "when one server has the public network pulled on it, the other
    goes offline too" I think this may have to do with the NetworkHosts attribute
    of the NIC resource being set to the IP address of the opposite host.

    "Craig Storm" wrote:
    >
    >Did you ever receive a solution to this problem?
    >
    >Craig
    >
    >"Graeme Hay" wrote:
    >>
    >>Hi there
    >>
    >>I was wondering if anyone has seen anything like this before - continuously
    >>echoing to the console on one of the servers in a two-node cluster?
    >>
    >>One of the other symptoms is that when one server has the public network
    >>pulled on it, the other goes offline too.
    >>
    >>Any advice appreciated.
    >>
    >>Feb 19 23:41:10 host-db1a unix: LLT:10023: lost 48 hb seq 58488 from 2

    link
    >>1
    >>Feb 19 23:41:10 host-db1a unix: LLT:10019: delayed hb 2450 ticks from 2

    >link
    >>0
    >>Feb 19 23:41:10 host-db1a unix: LLT:10023: lost 48 hb seq 58488 from 2

    link
    >>0
    >>Feb 19 23:41:20 host-db1a unix: LLT:10019: delayed hb 950 ticks from 2

    link
    >>1
    >>

    >



+ Reply to Thread