Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 2 replies
  • Subscribers 27 subscribers
  • Views 745 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

SPQ interface flapping

Simon Meijssen

Hi All,

After updating about 10 firewalls to XG18 for one of our customers we had another go at enabling SNMP-traps. (after the abysmal functionality that snmp-traps where in XG17).

I cannot say that it has improved much. some traps are still being sent by an APIPA address and contain 0 information on what the message is supposed to say.

We also noticed that about every once hour we receive a trap that an interface called SPQ is down.

I could not find any reference to what this interface is and if it is problematic in any way for the operation of the firewall.

Anybody know what it is used for?



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

    Hi ,

    Thank you for reaching out to Sophos Community.

    Could you please post a snapshot of the trap message?

  • 0 in reply to FormerMember

    Hi

    RFC1213-MIB::ifIndex.2128 = INTEGER: 2128
    RFC1213-MIB::ifDescr.2128 = STRING: spq
    RFC1213-MIB::ifAdminStatus.2128 = INTEGER: down(2)
    RFC1213-MIB::ifOperStatus.2128 = INTEGER: down(2)
    SNMPv2-MIB::snmpTrapEnterprise.0 = OID: .1.3.6.1.4.1.8072.3.2.10

    We are also getting these message twice. Once from the proper interface IP and once from an apipa address.

    The apipa seem to be bound to the ipsec0 interface of the unit

    ipsec0    Link encap:Ethernet  HWaddr 5E:1F:E0:D9:41:AA
              inet addr:169.254.234.5  Bcast:0.0.0.0  Mask:255.255.255.255
              inet6 addr: fe80::5c1f:e0ff:fed9:41aa/64 Scope:Link
              UP BROADCAST RUNNING NOARP MULTICAST  MTU:16260  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    This apipa seems to be default on all sophos XG units.

Reply
  • 0 in reply to FormerMember

    Hi

    RFC1213-MIB::ifIndex.2128 = INTEGER: 2128
    RFC1213-MIB::ifDescr.2128 = STRING: spq
    RFC1213-MIB::ifAdminStatus.2128 = INTEGER: down(2)
    RFC1213-MIB::ifOperStatus.2128 = INTEGER: down(2)
    SNMPv2-MIB::snmpTrapEnterprise.0 = OID: .1.3.6.1.4.1.8072.3.2.10

    We are also getting these message twice. Once from the proper interface IP and once from an apipa address.

    The apipa seem to be bound to the ipsec0 interface of the unit

    ipsec0    Link encap:Ethernet  HWaddr 5E:1F:E0:D9:41:AA
              inet addr:169.254.234.5  Bcast:0.0.0.0  Mask:255.255.255.255
              inet6 addr: fe80::5c1f:e0ff:fed9:41aa/64 Scope:Link
              UP BROADCAST RUNNING NOARP MULTICAST  MTU:16260  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    This apipa seems to be default on all sophos XG units.

Children
No Data