Packetloss after update [Freenas 9.3]

[jimmyboy_101]

Hi guys,

Started having issues with packetloss after updating my freenas version on my HP G8 Proliant micro server

Its a pretty standard network wise. its only using 1 port with no aggregation. When it isnt experiencing packet loss the speeds are good, and it was working reasonably well with minimal loss until i updated it on monday night.

I really dont know where to start but at the moment its making life difficult as Im actually in the process of migrating away from freenas as im not using half the features however this has made getting data off the box very difficult!

any help or ideas would be great!

the ifconfig looks like this

[root@freenas] ~# ifconfig
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c0099<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE>

ether 10:60:4b:92:e9:14
inet 192.168.1.25 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active

bge1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>

ether 10:60:4b:92:e9:15
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
ipfw0: flags=8800<SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=9<PERFORMNUD,IFDISABLED>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 02:98:8a:cb:01:00
nd6 options=9<PERFORMNUD,IFDISABLED>
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 13 priority 128 path cost 2000
member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 12 priority 128 path cost 2000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 11 priority 128 path cost 2000
member: bge0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 2 priority 128 path cost 20000
epair0a: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:a5:d0:00:0b:0a
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair1a: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:6a:e0:00:0c:0a
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair2a: flags=8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:d5:c7:00:0d:0a
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

and pings to the box look like

Jims-MacBook-Air:~ jimandlex$ ping 192.168.1.25
PING 192.168.1.25 (192.168.1.25): 56 data bytes
64 bytes from 192.168.1.25: icmp_seq=0 ttl=64 time=13.242 ms
Request timeout for icmp_seq 1
64 bytes from 192.168.1.25: icmp_seq=2 ttl=64 time=7.815 ms
64 bytes from 192.168.1.25: icmp_seq=3 ttl=64 time=10.845 ms
64 bytes from 192.168.1.25: icmp_seq=4 ttl=64 time=12.115 ms
64 bytes from 192.168.1.25: icmp_seq=5 ttl=64 time=15.156 ms
64 bytes from 192.168.1.25: icmp_seq=6 ttl=64 time=13.016 ms
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
64 bytes from 192.168.1.25: icmp_seq=11 ttl=64 time=1.572 ms
64 bytes from 192.168.1.25: icmp_seq=12 ttl=64 time=2.645 ms
64 bytes from 192.168.1.25: icmp_seq=13 ttl=64 time=13.515 ms
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
64 bytes from 192.168.1.25: icmp_seq=18 ttl=64 time=2.123 ms
64 bytes from 192.168.1.25: icmp_seq=19 ttl=64 time=5.235 ms
--- 192.168.1.25 ping statistics ---
20 packets transmitted, 11 packets received, 45.0% packet loss
round-trip min/avg/max/stddev = 1.572/8.844/15.156/4.896 ms

 

[depasseg]

10+ms point times for a LAN seen high. Also, what is your network setup? The adapters look like 1Gb but the media looks like 10gb. Of course maybe that is a formatting issue since in reading this on my phone.

First blush is a loose cable or switching loop.

 

[cyberjock]

You are using Broadcom NICs. They're not the most recommended brand and have been known to have issues ranging from minor inconveniences to major issues that make it unusable.

 

[jimmyboy_101]

sorry the 10ms is because I was using wifi when I provided the results.

when i when connected to the same switch with Ethernet I was still seeing the same pattern with dropouts. (but with <1ms response times inbetween)

will try a different cable and switch to rule that out tonight but i dont think thats the problem, ill go through the parts bin at work today and look for an intel NIC. dont really want to buy one if i dont have to but if thats going to be the only option to get the data off the server then ill go from there.

If its a incompatabilty with the broadcom nic's then that would suck! I would say a lot of users here would be using the G8 Microservers onboard nics.