Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 7 subscribers
  • Views 18048 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

SG 135 HA 'Unlinked'

TG1

The slave node in one pair of our SG135s regularly shows as Unlinked, even though it's fully cabled up to match the master.  Is there a way to determine why it's in the unlinked state?  Which interface it's (incorrectly) identifying as down?  Any help would be appreciated!

Edit - we're running 9.355-1 if that matters.



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to TG1

    Just hide the proprietary information.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Alright, pardon my poor MSpaint censoring.  Here's the dashboard:

  • 0 in reply to TG1

    Looking at your dashboard, all I can say is that it looks perfect (at the time when screenshot was made).

    1. How did you connect eth3 interfaces, directly with crossover cable or via switch device ?
    2. How often do you see "status=UNLINKED" message in HA log file ?

  • 0 in reply to vilic

    1) The HA ports (eth3) are directly connected, no intermediary devices.

     2) Every couple of minutes the slave reports 'Unlinked' in the HA log,  No details, just status messages like this:

    2016:03:07-11:33:25 fw-2 ha_mode[21110]: calling check

    2016:03:07-11:33:25 fw-2 ha_mode[21110]: check: waiting for last ha_mode done
    2016:03:07-11:33:25 fw-2 ha_mode[21110]: check_ha() role=SLAVE, status=UNLINKED
    2016:03:07-11:33:25 fw-2 ha_mode[21110]: check done (started at 11:33:25)
Unfiltered HTML