Network errors

I have errors on the following under the interfaces section of the status report from my firewall. What are these interfaces?

sw10 Link encap:Ethernet HWaddr 00:C0:02:12:35:88
UP BROADCAST RUNNING NOARP MULTICAST MTU:1524 Metric:1
RX packets:3649023884 errors:0 dropped:0 overruns:0 frame:0
TX packets:1666163554 errors:6 dropped:0 overruns:685 carrier:0
collisions:0 txqueuelen:1000
RX bytes:916254794 (873.8 MiB) TX bytes:4099243450 (3.8 GiB)
Base address:0x4000

sw11 Link encap:Ethernet HWaddr 00:C0:02:12:35:89
UP BROADCAST RUNNING NOARP MULTICAST MTU:1524 Metric:1
RX packets:669399632 errors:14 dropped:0 overruns:0 frame:0
TX packets:2630977840 errors:15130 dropped:0 overruns:1478080 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3374635079 (3.1 GiB) TX bytes:3532758383 (3.2 GiB)
Base address:0x8000

Comments

  • James_CarsonJames_Carson WatchGuard Representative
    edited June 30

    Hi @NetworkWise

    the sw interfaces are virtual interfaces that move data between the firewall's physical interfaces. Some models have more than one interface module (like the M200/300 where ports 0,1,2 are one, and 3-7 are the other, and the M4600/5600 where there are removable module bays.)

    You'll generally see these show up if the firewall is having trouble transmitting over a lossy interface, or if the interface that is being transmitted to isn't able to send the data fast enough. On firewalls that don't have the virtual switches, the errors will generally manifest on the physical interfaces.

    Traffic on those counters will be cumulative for the time the firewall has been up since last reboot. I'd only suggest worrying about them if the counters are currently going up and you're having trouble sending some type of traffic. If you'd like to reset the counters, rebooting the firewall will accomplish this.

    If you are running into an issue, I'd suggest opening a case so that one of our technicians can look into the issue more closely.

    -James Carson
    WatchGuard Customer Support

  • Okay thanks for the response @James_Carson

Sign In to comment.