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

    Hi, T G, and welcome to the UTM Community!

    Is there anything in the high availability log that looks suspicious?

    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

    The HA logs just show what I assume is a standard health check, they don't specify why it fails.  See below:

    2016:03:02-12:56:39 fw-2 ha_mode[20761]: calling check

    2016:03:02-12:56:39 fw-2 ha_mode[20761]: check: waiting for last ha_mode done
    2016:03:02-12:56:39 fw-2 ha_mode[20761]: check_ha() role=SLAVE, status=UNLINKED
    2016:03:02-12:56:39 fw-2 ha_mode[20761]: check done (started at 12:56:39)
    2016:03:02-13:16:38 fw-1 ha_daemon[3943]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 643 38.522" name="Executing (wait) /usr/local/bin/confd-setha mode master master_ip 198.19.250.1 slave_ip 198.19.250.2"
    2016:03:02-13:16:38 fw-1 ha_daemon[3943]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 644 38.744" name="Executing (nowait) /etc/init.d/ha_mode check"
    2016:03:02-13:16:38 fw-1 ha_mode[31863]: calling check
    2016:03:02-13:16:38 fw-1 ha_mode[31863]: check: waiting for last ha_mode done
    2016:03:02-13:16:38 fw-1 ha_mode[31863]: check_ha() role=MASTER, status=ACTIVE
    2016:03:02-13:16:38 fw-1 ha_mode[31863]: check done (started at 13:16:38)

Reply
  • 0 in reply to BAlfson

    The HA logs just show what I assume is a standard health check, they don't specify why it fails.  See below:

    2016:03:02-12:56:39 fw-2 ha_mode[20761]: calling check

    2016:03:02-12:56:39 fw-2 ha_mode[20761]: check: waiting for last ha_mode done
    2016:03:02-12:56:39 fw-2 ha_mode[20761]: check_ha() role=SLAVE, status=UNLINKED
    2016:03:02-12:56:39 fw-2 ha_mode[20761]: check done (started at 12:56:39)
    2016:03:02-13:16:38 fw-1 ha_daemon[3943]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 643 38.522" name="Executing (wait) /usr/local/bin/confd-setha mode master master_ip 198.19.250.1 slave_ip 198.19.250.2"
    2016:03:02-13:16:38 fw-1 ha_daemon[3943]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 644 38.744" name="Executing (nowait) /etc/init.d/ha_mode check"
    2016:03:02-13:16:38 fw-1 ha_mode[31863]: calling check
    2016:03:02-13:16:38 fw-1 ha_mode[31863]: check: waiting for last ha_mode done
    2016:03:02-13:16:38 fw-1 ha_mode[31863]: check_ha() role=MASTER, status=ACTIVE
    2016:03:02-13:16:38 fw-1 ha_mode[31863]: check done (started at 13:16:38)

Children
No Data
Unfiltered HTML