Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 27 subscribers
  • Views 13659 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

Frequent Interface Port Up/Down messages in SYSTEM category

Warren Buckles

When I look at my SYSTEM events in the Log Viewer and filter for 'Interface Up/Down' I see frequent pairs of ID 17813 messages.

The text is either "Interface Port2 is Down" or "Interface Port2 is Up"

Here's a sample:

Time               Log         Message                   Message ID
4/3/2018 8:32 Interface Interface Port2 is Up 17813
4/3/2018 8:32 Interface Interface Port2 is Down 17813
4/3/2018 8:32 Interface Interface Port2 is Up 17813
4/3/2018 8:32 Interface Interface Port2 is Down 17813
4/3/2018 1:41 Interface Interface Port2 is Up 17813
4/3/2018 1:41 Interface Interface Port2 is Down 17813
4/3/2018 1:40 Interface Interface Port2 is Up 17813
4/3/2018 1:40 Interface Interface Port2 is Down 17813
4/1/2018 0:23 Interface Interface Port2 is Up 17813
4/1/2018 0:22 Interface Interface Port2 is Down 17813
4/1/2018 0:22 Interface Interface Port2 is Up 17813
4/1/2018 0:22 Interface Interface Port2 is Down 17813

Note the pattern - two instances of Down/Up in a minute+ span of time.

These don't seem to be associated with any other SYSTEM level messages such as DB updates.

I have email reporting ON and these events show up in my monitoring account as well - a bit distracting as they don't seem to materially affect the unit's functionality.

I have looked for this item in the discussion groups and have not been successful - if it's already been addressed please tell me.

Any ideas?



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

    Hi,

    Can you give us more information to Port2?

    WAN / LAN?

    Connected to?

    Auto negotiation? - Static?

     

    Would take a deeper investigation into the physical layer.

     

    Cheers

  • 0 in reply to LuCar Toni

    Hello ManBearPig:

    Thanks for your response.

    Here's a screen shot of Port2's configuration:

    I'm a total NOOB w/t/r Sophos XG firewalls so please excuse dumb questions.

    This exercise is associated with evaluating/learning the Sophos XG firewall series for possible deployment to a number of my IT support clients.  Up to now I have relied on Sonic Wall devices but they seem to be a fading commodity.  I have a number of clients with Sonic Wall devices within 12 months of expiry/renewal.  I can <usually> make a Sonic Wall work but I'm not optimistic regarding the future of the Sonic Wall product.

    So I bought an XG-105 and am trying it out on a sub-section of my personal network (8-10 clients, no server).

    To cut to the chase, 'Port_2' is connected to local Ethernet Port 1 of an ASUS Wireless N router equipped with four Ethernet ports (1-4) and one 'WAN' port.  

    The ASUS router's WAN port is connected to my main network Level 2 switch which is in turn connected via a Sonic Wall SOHO device to my ISP's (cable) modem.

    No other devices are connected to the ASUS router's Ethernet ports but I do use the wireless function to connect to my tablet(s).

    The ASUS Ethernet Port 1 is setup as a DHCP client and picks up its address from the XG-105 as you can see above.

    Does this help?

    wb

  • 0 in reply to Warren Buckles

    Hi,

    i´m just guessing here, so try to change on both sites (asus and XG) auto negotiation to a static value.

    https://en.wikipedia.org/wiki/Autonegotiation

    Sometimes, there is a issue in the hardware layer, in which case both sites cannot come to the correct "which speed should we take?" question.

    https://en.wikipedia.org/wiki/Autonegotiation#Interoperability_problems

    So just try a static value and observe, if the issue still occurs.

    Cheers

  • 0 in reply to LuCar Toni

    Thx

    Will try being a piece of paper.

  • 0 in reply to Warren Buckles

    Changed it to static = stationary = stationery = paper.

    Problem expected to go away.

    DHCP renewal on ASUS unit most likely associated w/Up/Down cycles.  Duh.

    Thx.

    wb

Reply Children
No Data