Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 1 subscriber
  • Views 14659 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Clients appearing offline in SEC 5.1

Tommy123

Hi All,

I have recently installed SEC 5.1 with 10 clients on in preperation for an upgrade from 4.7 later this year. 

For some reason some clients after a period of time get a little red cross on them, these can be virtual and physical machines. The machines are not turned off and are still getting updates from the SEC.

To get them back green I can either reboot them, restart the client message router or re protect them.

Anyone else had this issue?

Thanks

Tom

:39143


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    Worth noting that SEC 5.2 is out so it might be worth testing that.

    As for the disconnected state: the management servcice will disconnect clients if the last message time is older than 24 hours.  It runs this job every 24 hours.  So you may want to check in SEC the last message time of the clients in this disconnected state.  If it is older than 24 hours then this could be the reason.

    The last message time is updates whenever the client sends in an event message or status message.  So you'd expect if the client updates every 4 hours with a new IDE that this should be OK.

    The other method for a client to become disconnected is if the parent message router doesn't hear from the client, within around 30 minutes.  The client polls the server for messages roughly every 15 minutes.  The server expects to hear from the client within 2 polls, so around 30 mins.  If it doesn't then it logs the client off, this action is recorded in the server router log.  As a communication timout.


    Hope it helps.

    Regards,

    Jak

    :39161
Reply
  • 0

    Hi,

    Worth noting that SEC 5.2 is out so it might be worth testing that.

    As for the disconnected state: the management servcice will disconnect clients if the last message time is older than 24 hours.  It runs this job every 24 hours.  So you may want to check in SEC the last message time of the clients in this disconnected state.  If it is older than 24 hours then this could be the reason.

    The last message time is updates whenever the client sends in an event message or status message.  So you'd expect if the client updates every 4 hours with a new IDE that this should be OK.

    The other method for a client to become disconnected is if the parent message router doesn't hear from the client, within around 30 minutes.  The client polls the server for messages roughly every 15 minutes.  The server expects to hear from the client within 2 polls, so around 30 mins.  If it doesn't then it logs the client off, this action is recorded in the server router log.  As a communication timout.


    Hope it helps.

    Regards,

    Jak

    :39161
Children
No Data