LLT Error messages - Veritas Cluster Server

This is a discussion on LLT Error messages - Veritas Cluster Server ; LLT is used to carry GAB messages as well as heartbeat (to tell the node in the cluster is alive). If the machine is very busy, and LLT does not get the opertunity to heartbeat, you will see those messages. ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: LLT Error messages

  1. Re: LLT Error messages

    LLT is used to carry GAB messages as well as heartbeat (to tell the node
    in the cluster is alive).

    If the machine is very busy, and LLT does not get the opertunity to
    heartbeat, you will see those messages. It is also possible that the
    link might be too busy (some people use the links to plumb up IP
    addresses to carry normal IP traffic as well)

    Sandip wrote:
    > We are keep on getting following error messages in our syslog file. What could
    > be the main reason. We are using SP3 and using HP-UX 11.11.
    >
    > May 11 14:46:30 viking1 vmunix: LLT:10019: delayed hb 6600 ticks from 1 link
    > 1 (
    > lan1)
    >
    > May 11 14:46:30 viking1 vmunix: LLT:10023: lost 131 hb seq 321849 from 1
    > link 1
    > (lan1)
    >
    > May 11 14:46:30 viking1 vmunix: LLT:10019: delayed hb 6600 ticks from 1 link
    > 0 (
    > lan0)
    >
    >


  2. LLT Error messages


    We are keep on getting following error messages in our syslog file. What could
    be the main reason. We are using SP3 and using HP-UX 11.11.

    May 11 14:46:30 viking1 vmunix: LLT:10019: delayed hb 6600 ticks from 1 link
    1 (
    lan1)

    May 11 14:46:30 viking1 vmunix: LLT:10023: lost 131 hb seq 321849 from 1
    link 1
    (lan1)

    May 11 14:46:30 viking1 vmunix: LLT:10019: delayed hb 6600 ticks from 1 link
    0 (
    lan0)



  3. Re: LLT Error messages


    Also be sure that all NICs (and ports if using switches) are forced to 100FDX
    unless using gig ethernet. Allowing autoneg on 100fdx links can cause this
    kind of behaviour as well.

    Me wrote:
    >LLT is used to carry GAB messages as well as heartbeat (to tell the node


    >in the cluster is alive).
    >
    >If the machine is very busy, and LLT does not get the opertunity to
    >heartbeat, you will see those messages. It is also possible that the
    >link might be too busy (some people use the links to plumb up IP
    >addresses to carry normal IP traffic as well)
    >
    >Sandip wrote:
    >> We are keep on getting following error messages in our syslog file. What

    could
    >> be the main reason. We are using SP3 and using HP-UX 11.11.
    >>
    >> May 11 14:46:30 viking1 vmunix: LLT:10019: delayed hb 6600 ticks from

    1 link
    >> 1 (
    >> lan1)


    >>
    >> May 11 14:46:30 viking1 vmunix: LLT:10023: lost 131 hb seq 321849 from

    1
    >> link 1
    >> (lan1)


    >>
    >> May 11 14:46:30 viking1 vmunix: LLT:10019: delayed hb 6600 ticks from

    1 link
    >> 0 (
    >> lan0)


    >>
    >>



+ Reply to Thread