Wrong direction of Packet loss

Recently,I capture some RTP packets when user meeting the dialogue jitter and latency.
User A using the 3951 ip phone (IP address is x.x.125.206, and x.x.200.165 is the voice gateway's ip address ) , and user B using a mobile phone.
User A responds to me that she can't hear user B clearly.
This reflect to packets capture result should be packet lost at the in direction.
But the capture result show that packets loss happen at the out direction.
Could any body explain it for me?
Thanks a lot!

Probably you have captured RTP traffic near the voice gateway. Right?
I suppose that you have bidirectional packet loss.
In this case, if you use wireshark near one of the sources you can observe only one direction loss.
You must try to use wireshark in both network segments.
P.S. in the bottom of the your image we can see ip addresses of your net.
Regards.

Similar Messages

  • Bouts of packet loss and complete loss of connection

    Ok forum, I give up! I need your help.
    I have an E1200 and am time out and packet loss issues. The internet connection is fine for 30 seconds to five minuets and then everything times out for 15-20 seconds. Although it’s only a minor incontinence to web browsing, it makes playing games and watching videos a nightmare. “Lost connection to server error.” and the like…
    This is what I have done to remedy the problem.
    I upgraded to a new router, the e1200 I am currently using, from my Tenda 10/100 N. The problems where the same that I am experience currently and the reason I bought it in the firs place.
    When I directly connect to the cable modem, I have no issues and everything is fine.
    I have run a trace route and the second hop, (the router to the modem) is the choke point.
    I have cloned the MAC address
    I have updated the firmware and hard reset
    I have throttled my MTU to automatic, 1500, and 1472. None making any difference.
    I have disabled NAT and all that does is kill my internet connection
    I have disabled all firewalls router and windows, no change.
    I replaced the physical wire from the router to the modem.
    I have disconnected all devices except one computer, and no difference.
    I ran a DNS trace and I have… non routable local internet address 192.168.1.1
    DNS-cac-lb-01.rr.com and DNS-cac-lb-02.rr.com
    I am using windows 7 and my ISP is time Warner so-cal. Help me obiwan, you’re my only hope.

    Sorry friend. I have not had the gaul to load the 1.0 firmware. I am 99% sure I have the 2.0 hardware. I did however unplug my modem for an hour and then try and reconnect. The result was a lossless environment for fifteen to twenty minuets (a long time for me.). But, I am right back still having the same problem. A friend gave me a new netgear router, I am going to try that and I am going to go to Timewarner and have them replace my modem just to make sure there is nothing wrong with the surfboard. I will report back with my findings.

  • Packet loss when pinging from/to a cisco 3560e switch

    I see Packet loss when pinging from/to a cisco 3560e switch. CPU utilization is normal.
    Switches are running with IOS c3560e-universalk9-mz.122-35.SE5.bin.
    Packet loss is observed for all the devices irrespective of directly connected or remote devices.
    If i do self pinging, there are no packet loss.
    I don't see any error on interface.
    Can anyone please help me in resolving this issue.

    TCB       Local Address           Foreign Address        (state)
    03737C48  10.47.0.229.60053       10.41.81.55.49         CLOSEWAIT
    039ACDC4  10.47.0.229.61929       10.41.35.250.49        CLOSEWAIT
    03B316C0  10.47.0.229.27544       10.41.81.55.49         CLOSEWAIT
    038228F0  10.47.0.229.16506       10.41.35.250.49        CLOSEWAIT
    039C3D04  10.47.0.229.15207       10.41.81.55.49         CLOSEWAIT
    039A9BD0  10.47.0.229.52983       10.41.81.55.49         CLOSEWAIT
    0394152C  10.47.0.229.22425       161.61.35.250.49       CLOSEWAIT
    037D811C  10.47.0.229.21117       10.41.81.55.49         CLOSEWAIT
    039C12BC  10.47.0.229.37437       10.41.81.55.49         CLOSEWAIT
    03933B84  10.47.0.229.34085       161.61.35.250.49       TIMEWAIT
    03B32340  10.47.0.229.45729       10.41.81.55.49         CLOSEWAIT
    038247D0  10.47.0.229.32816       10.41.81.55.49         CLOSEWAIT
    039A92D8  10.47.0.229.38680       161.61.35.250.49       CLOSEWAIT
    037370F0  10.47.0.229.13212       10.41.81.55.49         CLOSEWAIT
    037D85F0  10.47.0.229.38728       10.41.81.55.49         CLOSEWAIT
    03B2B284  10.47.0.229.23428       10.41.81.55.49         CLOSEWAIT
    03B2ADB0  10.47.0.229.56836       10.41.81.55.49         CLOSEWAIT
    0394BFF0  10.47.0.229.23257       161.61.35.250.49       CLOSEWAIT
    036604DC  10.47.0.229.44437       10.41.81.55.49         CLOSEWAIT
    0394C700  10.47.0.229.22          192.37.184.211.61639   ESTAB
    039B9A68  10.47.0.229.20543       10.41.81.55.49         CLOSEWAIT
    03739B28  10.47.0.229.15392       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    0392EA48  10.47.0.229.13862       10.41.81.55.49         CLOSEWAIT
    0365E23C  10.47.0.229.27856       10.41.81.55.49         CLOSEWAIT
    03817C0C  10.47.0.229.64929       10.41.81.55.49         CLOSEWAIT
    039357C8  10.47.0.229.22088       10.41.81.55.49         CLOSEWAIT
    037375C4  10.47.0.229.21832       10.41.81.55.49         CLOSEWAIT
    039C20E8  10.47.0.229.18169       10.41.81.55.49         CLOSEWAIT
    03716D08  10.47.0.229.61993       10.41.81.55.49         CLOSEWAIT
    039A74E4  10.47.0.229.62948       10.41.81.55.49         CLOSEWAIT
    03655480  10.47.0.229.14052       10.41.81.55.49         CLOSEWAIT
    039407F0  10.47.0.229.49643       161.61.35.250.49       CLOSEWAIT
    039A53AC  10.47.0.229.13233       10.41.81.55.49         CLOSEWAIT
    03739FFC  10.47.0.229.16605       10.41.81.55.49         CLOSEWAIT
    039B82B8  10.47.0.229.16458       10.41.35.250.49        CLOSEWAIT
    039BEBA4  10.47.0.229.64377       10.41.81.55.49         CLOSEWAIT
    03741980  10.47.0.229.13866       10.41.81.55.49         CLOSEWAIT
    03B3ABF8  10.47.0.229.19365       10.41.81.55.49         CLOSEWAIT
    039B5810  10.47.0.229.24768       10.41.81.55.49         CLOSEWAIT
    03956E48  10.47.0.229.55980       161.61.35.250.49       CLOSEWAIT
    03946820  10.47.0.229.65053       161.61.35.250.49       CLOSEWAIT
    037DBE94  10.47.0.229.15283       10.41.81.55.49         CLOSEWAIT
    039A4854  10.47.0.229.48562       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    03B33320  10.47.0.229.29803       10.41.81.55.49         CLOSEWAIT
    03B3B79C  10.47.0.229.12142       10.41.81.55.49         CLOSEWAIT
    03713C9C  10.47.0.229.63799       10.41.81.55.49         CLOSEWAIT
    039BBECC  10.47.0.229.14763       10.41.81.55.49         CLOSEWAIT
    03656E40  10.47.0.229.16357       10.41.81.55.49         CLOSEWAIT
    0362A73C  10.47.0.229.62450       10.41.81.55.49         CLOSEWAIT
    039B878C  10.47.0.229.64402       161.61.35.250.49       CLOSEWAIT
    03826CFC  10.47.0.229.16108       10.41.81.55.49         CLOSEWAIT
    03B2CA34  10.47.0.229.17634       10.41.81.55.49         CLOSEWAIT
    03AD78D0  10.47.0.229.15249       161.61.35.250.49       CLOSEWAIT
    03AD967C  10.47.0.229.20389       161.61.35.250.49       CLOSEWAIT
    03B2C560  10.47.0.229.37079       10.41.81.55.49         CLOSEWAIT
    039C5128  10.47.0.229.24711       10.41.81.55.49         CLOSEWAIT
    03822F74  10.47.0.229.54866       10.41.81.55.49         CLOSEWAIT
    0372C5FC  10.47.0.229.13298       10.41.81.55.49         CLOSEWAIT
    0372D278  10.47.0.229.12407       10.41.81.55.49         CLOSEWAIT
    039A33D0  10.47.0.229.36573       10.41.81.55.49         CLOSEWAIT
    039BCEF8  10.47.0.229.53853       10.41.81.55.49         CLOSEWAIT
    039C02D8  10.47.0.229.53725       10.41.81.55.49         CLOSEWAIT
    039B5CE4  10.47.0.229.58027       10.41.81.55.49         CLOSEWAIT
    0381866C  10.47.0.229.17100       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    039BB374  10.47.0.229.53148       10.41.81.55.49         CLOSEWAIT
    03AD3634  10.47.0.229.19716       161.61.35.250.49       CLOSEWAIT
    0362DAA4  10.47.0.229.19479       10.41.81.55.49         CLOSEWAIT
    0365AE60  10.47.0.229.62209       10.41.81.55.49         CLOSEWAIT
    0362D5D0  10.47.0.229.41327       10.41.81.55.49         CLOSEWAIT
    037D7C48  10.47.0.229.58283       10.41.81.55.49         CLOSEWAIT
    03955474  10.47.0.229.33810       161.61.35.250.49       CLOSEWAIT
    0373B15C  10.47.0.229.23331       10.41.81.55.49         CLOSEWAIT
    036628D0  10.47.0.229.46856       10.41.81.55.49         CLOSEWAIT
    03819584  10.47.0.229.19861       10.41.81.55.49         CLOSEWAIT
    0394D000  10.47.0.229.64732       10.41.35.250.49        CLOSEWAIT
    0394B760  10.47.0.229.19967       161.61.35.250.49       CLOSEWAIT
    039B6BD4  10.47.0.229.40096       10.41.81.55.49         CLOSEWAIT
    03AD7150  10.47.0.229.65184       10.41.35.250.49        CLOSEWAIT
    039BC3A0  10.47.0.229.64702       10.41.81.55.49         CLOSEWAIT
    03B3A724  10.47.0.229.60399       10.41.81.55.49         CLOSEWAIT
    037145E0  10.47.0.229.43951       10.41.81.55.49         CLOSEWAIT
    03955EDC  10.47.0.229.29015       161.61.35.250.49       TIMEWAIT
    0365FB34  10.47.0.229.13961       10.41.81.55.49         CLOSEWAIT
    03828D54  10.47.0.229.12743       10.41.81.55.49         CLOSEWAIT
    037DB40C  10.47.0.229.23708       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    039AF814  10.47.0.229.15100       10.41.81.55.49         CLOSEWAIT
    0392E344  10.47.0.229.23399       10.41.35.250.49        CLOSEWAIT
    0393DC3C  10.47.0.229.15393       161.61.35.250.49       CLOSEWAIT
    03AD85D0  10.47.0.229.40932       161.61.35.250.49       TIMEWAIT
    039574CC  10.47.0.229.25935       10.41.35.250.49        CLOSEWAIT
    03738B74  10.47.0.229.58656       10.41.81.55.49         CLOSEWAIT
    039AD91C  10.47.0.229.56760       10.41.81.55.49         CLOSEWAIT
    03B3BC70  10.47.0.229.15058       10.41.81.55.49         CLOSEWAIT
    03B2DC54  10.47.0.229.51131       161.61.35.250.49       CLOSEWAIT
    03B393F0  10.47.0.229.11957       10.41.35.250.49        CLOSEWAIT
    039B2610  10.47.0.229.33728       10.41.81.55.49         CLOSEWAIT
    03B311EC  10.47.0.229.18047       10.41.81.55.49         CLOSEWAIT
    039A8E04  10.47.0.229.52022       161.61.35.250.49       CLOSEWAIT
    0365D460  10.47.0.229.12241       10.41.81.55.49         CLOSEWAIT
    03B33E78  10.47.0.229.47640       10.41.81.55.49         CLOSEWAIT
    0372C128  10.47.0.229.60323       10.41.81.55.49         CLOSEWAIT
    03661CD8  10.47.0.229.39923       10.41.81.55.49         CLOSEWAIT
    0393C73C  10.47.0.229.41864       10.41.35.250.49        CLOSEWAIT
    03829584  10.47.0.229.56673       161.61.35.55.49        CLOSEWAIT
    0362AC10  10.47.0.229.31952       10.41.81.55.49         CLOSEWAIT
    039BF078  10.47.0.229.22636       10.41.81.55.49         CLOSEWAIT
    TCB       Local Address           Foreign Address        (state)
    0365CF8C  10.47.0.229.14476       10.41.81.55.49         CLOSEWAIT
    039B443C  10.47.0.229.59226       10.41.81.55.49         CLOSEWAIT
    0393E794  10.47.0.229.56282       10.41.35.250.49        CLOSEWAIT
    03657740  10.47.0.229.25769       10.41.81.55.49         CLOSEWAIT
    03B2F6E8  10.47.0.229.19328       10.41.81.55.49         CLOSEWAIT
    0373AC88  10.47.0.229.25766       10.41.81.55.49         CLOSEWAIT
    039B213C  10.47.0.229.28882       10.41.81.55.49         CLOSEWAIT
    039C07AC  10.47.0.229.38201       10.41.81.55.49         CLOSEWAIT
    03AD8DD0  10.47.0.229.23002       10.41.35.250.49        CLOSEWAIT
    03739048  10.47.0.229.29572       10.41.35.250.49        CLOSEWAIT
    039BA464  10.47.0.229.32273       10.41.81.55.49         CLOSEWAIT
    03B31E6C  10.47.0.229.32521       10.41.81.55.49         CLOSEWAIT
    0365EBE0  10.47.0.229.41319       10.41.81.55.49         CLOSEWAIT
    03938804  10.47.0.229.62841       10.41.35.250.49        CLOSEWAIT
    039A1AF8  10.47.0.229.12758       10.41.81.55.49         CLOSEWAIT
    039B7DE4  10.47.0.229.20921       10.41.81.55.49         CLOSEWAIT
    036549F8  10.47.0.229.51903       10.41.81.55.49         CLOSEWAIT
    03714CC8  10.47.0.229.45145       10.41.81.55.49         CLOSEWAIT
    037425F8  10.47.0.229.56492       10.41.81.55.49         CLOSEWAIT
    03B39D74  10.47.0.229.18174       10.41.81.55.49         CLOSEWAIT

  • White noise, sort of packet loss when talking with...

    Hi,
    For some unknown reason when I talk with one specific person the call doesn't exactly drop out it sort of cuts the audio and gives me white noise (sort of like when you get packet loss when transferring files or gaming), I have 0 idea why it does it. Does it the reverse as well, but only for me and this person. Everyone else thats in the call doesn't get effected and its frustrating me.

    When in a call goto call > Technical info. This will show you various info about the call connection (and a lot of useless info aswell). Amongst the info is packet loss, and relays (if relays = more than 0 you are not directly connected).
    Being on the same Skype, version might help.

  • Packet loss and eventual shutdown of port 80 on RV180

    I have been using my RV180 router for about a year now. I have had very little issues with it overall. I have seperate wireless access points connected and use those for my wireless devices.
    Recently, I started getting very odd connection problems it started as packet loss and then turned into connection loss. The odd part is that it only effects port 80 or the secured port, 880, if I remember correctly. Thats right, everything else on the network works fine. However, I can not access the internet or the RV180 router via it's ip address to check the status. VOIP, other lan networking, gaming, and bitcoin mining is completely uneffected. Direct connection to the modem works without any problems.
    I have tried updating the router firmware but no help.
    Each time I have this issue the problem is cured simply by unplugging the router and plugging it back in. Nothing else works because I can not log into the router. This problem comes along once a week or so. I have also tried enabling the logs but I get absolutly nothing when I reset the router and log back in. I have had similar problems with routers in the past becoming "bent" after about a year of use and requiring a replacement. I sort of thought that this wouldnt be the case with the Cisco because it is a good brand and came with a five year warranty. I have also scanned every PC on the network for viruses and malware but nothing was located. The remainder of the devices are IP cameras and such.
    Can anyone think of anything that could be causing this?

    So I was able to get the logs tonight by repeatedly pinging the router and it would start letting me get traffic in again.
    Wed Dec  4 20:03:02 2013(GMT-0500) [rv180][Kernel][KERNEL] [81097.390000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:02 2013(GMT-0500) [rv180][Kernel][KERNEL] [81097.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:02 2013(GMT-0500) [rv180][Kernel][KERNEL] [81097.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:02 2013(GMT-0500) [rv180][Kernel][KERNEL] [81097.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81101.770000] __ratelimit: 111 callbacks suppressed
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81101.770000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81101.890000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81101.890000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81101.930000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81101.930000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81102.030000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81102.070000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81102.230000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81102.320000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:07 2013(GMT-0500) [rv180][Kernel][KERNEL] [81102.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.020000] __ratelimit: 102 callbacks suppressed
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.020000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.020000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.270000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.320000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.420000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.430000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.520000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:12 2013(GMT-0500) [rv180][Kernel][KERNEL] [81107.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.120000] __ratelimit: 100 callbacks suppressed
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.120000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.310000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.310000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.320000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.500000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:17 2013(GMT-0500) [rv180][Kernel][KERNEL] [81112.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] __ratelimit: 107 callbacks suppressed
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:22 2013(GMT-0500) [rv180][Kernel][KERNEL] [81117.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] __ratelimit: 93 callbacks suppressed
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:27 2013(GMT-0500) [rv180][Kernel][KERNEL] [81122.550000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.560000] __ratelimit: 101 callbacks suppressed
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.560000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.600000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.690000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.750000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.790000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.830000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.830000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:32 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.840000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:33 2013(GMT-0500) [rv180][Kernel][KERNEL] [81127.840000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.140000] __ratelimit: 110 callbacks suppressed
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.140000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.140000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.260000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.300000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.560000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.560000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.560000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.560000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.560000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:38 2013(GMT-0500) [rv180][Kernel][KERNEL] [81133.560000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.290000] __ratelimit: 84 callbacks suppressed
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.290000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:43 2013(GMT-0500) [rv180][Kernel][KERNEL] [81138.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81143.710000] __ratelimit: 126 callbacks suppressed
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81143.710000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81144.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81144.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81144.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81144.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81144.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81144.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81144.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81144.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:49 2013(GMT-0500) [rv180][Kernel][KERNEL] [81144.570000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81149.580000] __ratelimit: 67 callbacks suppressed
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81149.580000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81149.720000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81149.740000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81150.280000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81150.330000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81150.440000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81150.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81150.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81150.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:54 2013(GMT-0500) [rv180][Kernel][KERNEL] [81150.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:59 2013(GMT-0500) [rv180][Kernel][KERNEL] [81154.870000] __ratelimit: 85 callbacks suppressed
    Wed Dec  4 20:03:59 2013(GMT-0500) [rv180][Kernel][KERNEL] [81154.870000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:59 2013(GMT-0500) [rv180][Kernel][KERNEL] [81155.030000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:00 2013(GMT-0500) [rv180][Kernel][KERNEL] [81155.030000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:00 2013(GMT-0500) [rv180][Kernel][KERNEL] [81155.210000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:00 2013(GMT-0500) [rv180][Kernel][KERNEL] [81155.210000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:00 2013(GMT-0500) [rv180][Kernel][KERNEL] [81155.210000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:00 2013(GMT-0500) [rv180][Kernel][KERNEL] [81155.210000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:00 2013(GMT-0500) [rv180][Kernel][KERNEL] [81155.210000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:00 2013(GMT-0500) [rv180][Kernel][KERNEL] [81155.280000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:00 2013(GMT-0500) [rv180][Kernel][KERNEL] [81155.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.100000] __ratelimit: 114 callbacks suppressed
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.100000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.100000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.270000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.330000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.340000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.350000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.350000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:04:05 2013(GMT-0500) [rv180][Kernel][KERNEL] [81160.540000] nf_conntrack: table full, dropping packet.
    Wed Dec  4 20:03:02 2013(GMT-0500) [rv180][Kernel][KERNEL] [81097.390000] nf_conntrack: table full, dropping packet.
    Sat Jan 01 00:00:13 2011 (GMT +0000): [RV180] [IKE] INFO:  IKE started

  • Packet loss after bonding + vlan

    Hi, I am hoping someone may help me with this issue:
    I have a motherboard with 2 Intel NICs.
    I created a bonding interface, mode = 4 (LACP), and assigned no IP to it.
    create one vlan to internet (dhcp)
    another vlan to local network (static)
    both NICs are connected to the same switch, and LACP configured on the ports
    Problem:
    ping from this one to any other pingable hosts gave strange result, more or less half of the packets are lost.
    when I pulled of one cable, the ping returned to normal...
    something is definitively wrong here, tried to connect the ports to two diffrent switches, same result.
    other computers using LACP has no such problem in the same network.
    If someone has any idea, I will be very greatful. otherwise it seems to be a very time consuming problem to solve. (I have tried to google yesterday without success).
    Thanks,
    Last edited by leihuang (2013-09-17 06:19:42)

    I located the issue of the packet loss. I have a security system that uploads FTP images of the cameras and after the reboot of the network, the only computer that wasn't shut down was the security camera PC.
    So I think what happened was after I brought everything back up, it was saturating the outgoing bandwidth, causing packet loss and high latency. Once I determined what it was and shut off the FTP image upload, the pings stabilized and it is working fine now. Trace routes are still not functioning, but I can live without that for now.

  • VoIP Phones - Testing Latency, Jitter, and Packet Loss

    I am having big problems with my VoIP phone connection and I'll try to lay it out clearly here.
    The main telephone system resides at Location A (static IP address - see below - xxx.xxx.206.19), which has a network connection of 50MB down/20MB up (i.e., very fast).  The VoIP phone configured for that system resides at Location B, which has a network connection of 10MB down/1MB up (i.e., also fast, or at least fast enough "on paper" for a quality VoIP connection).  The LAN at Location A uses an Airport Extreme router, which does not have QOS or EF capability. The LAN at Location B uses a D-Link DIR-655 router which does have QOS that is configured properly to direct all traffic to the VoIP phone's IP address.
    The VoIP phone at Location B is having intermittent call quality problems with skipping of words, hollowing out noises, jittery conversations, etc.  All the inquiries I've made to the ISPs and phone system manufacturer (ESI) suggest that my base Internet speeds are not the problem.
    I'm told, instead, that the problem might be latency, jitter, or packet loss between Location A and Location B.  This leads to several questions:
    (1)     Is there any Mac software that can test latency, jitter, and packet loss? I've looked at Network Utility and it seems to only measure a few things. 
    (2)     Does anyone see anything in the following Traceroute and Ping results (done twice from Location B to Location A) that looks problematic to VoIP quality?:
    Traceroute:
    First run: Traceroute has started…
    traceroute to xxx.xxx.206.19 (xxx.xxx.206.19), 64 hops max, 72 byte packets
    1  alfirving (192.168.0.1)  0.569 ms  0.363 ms  0.302 ms
    2  10.72.28.1 (10.72.28.1)  27.567 ms 18.161 ms  22.288 ms
    3  70.125.216.150 (70.125.216.150)  9.841 ms  10.346 ms  9.497 ms
    4  24.164.209.116 (24.164.209.116)  11.042 ms 8.298 ms  9.433 ms
    5  70.125.216.108 (70.125.216.108)  21.068 ms  20.657 ms  12.045 ms
    6  te0-8-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.48)  11.154 ms  11.540 ms  24.495 ms
    7  107.14.17.136 (107.14.17.136)  11.994 ms  14.217 ms  15.816 ms
    8  ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 14.566 ms  32.670 ms  15.947 ms
    9  ix-0-3-2-0.tcore2.dt8-dallas.as6453.net (209.58.47.105)  11.647 ms  12.260 ms  12.386 ms
    10  if-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 10.023 ms  12.285 ms  12.338 ms
    11  209.58.47.74 (209.58.47.74)  17.641 ms 16.741 ms  16.372 ms
    12  0.ae2.xl3.dfw7.alter.net (152.63.97.57)  11.584 ms  12.315 ms  12.890 ms
    13  0.so-6-1-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.90)  13.812 ms
        0.ge-3-0-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.17)  18.831 ms
        130.81.23.164 (130.81.23.164)  14.189 ms
    14  p14-0-0.dllstx-lcr-05.verizon-gni.net (130.81.27.40) 14.561 ms  13.621 ms  15.544 ms
    15  * * *
    16  static-xxx.xxx.206.19.dllstx.fios.verizon.net (xxx.xxx.206.19)  23.125 ms  24.136 ms  22.411 ms
    Second run: Traceroute has started…
    traceroute to xxx.xxx.206.19 (xxx.xxx.206.19), 64 hops max, 72 byte packets
    1  alfirving (192.168.0.1)  0.603 ms  0.420 ms  0.324 ms
    2  10.72.28.1 (10.72.28.1)  40.494 ms 26.625 ms  14.152 ms
    3  70.125.216.150 (70.125.216.150)  9.431 ms  9.660 ms  9.018 ms
    4  24.164.209.116 (24.164.209.116)  16.293 ms  12.339 ms  19.252 ms
    5  70.125.216.108 (70.125.216.108)  15.801 ms  11.438 ms  12.068 ms
    6  te0-8-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.48)  23.221 ms  30.459 ms  17.519 ms
    7  107.14.17.136 (107.14.17.136)  14.611 ms  15.696 ms  15.775 ms
    8  ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209) 17.643 ms  14.812 ms  16.294 ms
    9  ix-0-3-2-0.tcore2.dt8-dallas.as6453.net (209.58.47.105)  11.169 ms  12.374 ms  9.849 ms
    10  if-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 16.453 ms  12.168 ms  12.384 ms
    11  209.58.47.74 (209.58.47.74)  18.015 ms 14.867 ms  16.432 ms
    12  0.ae2.xl3.dfw7.alter.net (152.63.97.57)  11.471 ms  11.993 ms  12.395 ms
    13  0.ge-6-3-0.dfw01-bb-rtr1.verizon-gni.net (152.63.96.42)  14.077 ms  29.153 ms
        0.ge-3-0-0.dfw01-bb-rtr1.verizon-gni.net (152.63.1.17) 17.962 ms
    14  p14-0-0.dllstx-lcr-05.verizon-gni.net (130.81.27.40)  14.629 ms  12.297 ms  12.839 ms
    15  * * *
    16  static-xxx.xxx.206.19.dllstx.fios.verizon.net (xxx.xxx.206.19)  24.976 ms  22.170 ms  22.376 ms
    Ping:
    First Run: Ping has started…
    PING xxx.xxx.206.19 (xxx.xxx.206.19): 56 data bytes
    64 bytes from xxx.xxx.206.19: icmp_seq=0 ttl=242 time=22.814 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=1 ttl=242 time=24.621 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=2 ttl=242 time=24.711 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=3 ttl=242 time=24.109 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=4 ttl=242 time=23.336 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=5 ttl=242 time=25.644 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=6 ttl=242 time=27.755 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=7 ttl=242 time=25.135 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=8 ttl=242 time=22.443 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=9 ttl=242 time=24.635 ms
    --- xxx.xxx.206.19 ping statistics ---
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 22.443/24.520/27.755/1.448 ms
    Second Run: Ping has started…
    PING xxx.xxx.206.19 (xxx.xxx.206.19): 56 data bytes
    64 bytes from xxx.xxx.206.19: icmp_seq=0 ttl=242 time=27.183 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=1 ttl=242 time=24.629 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=2 ttl=242 time=22.511 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=3 ttl=242 time=39.620 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=4 ttl=242 time=26.722 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=5 ttl=242 time=23.183 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=6 ttl=242 time=25.171 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=7 ttl=242 time=24.412 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=8 ttl=242 time=23.837 ms
    64 bytes from xxx.xxx.206.19: icmp_seq=9 ttl=242 time=23.785 ms
    --- xxx.xxx.206.19 ping statistics ---
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 22.511/26.105/39.620/4.713 ms
    (3) Any other ideas on what my call quality problem might be, or how I can tweak it?  For example, would putting a DIR-655 router at Location A and enabling QOS really make a difference?
    Thanks to everyone, and I hope this is not too long or difficult to understand.

    Hey thanks for your reply  Yeah im only getting 1 ro sometimes 2 bars reception so hopefully the antenna will beef things up but I think it is what it is perhaps.  

  • NIC teaming creates packet loss (Windows 2008 R2)?

    I'm experiencing some packet loss to all of our VMs that we didn't have before we made some changes to our Hyper-V implementation (Windows 2008 R2). Most of the VMs also run 2008 R2 - with 3 that run Server 2003.
    The host server is a Dell R610 with three 4 port NICS - two Intel quad port gigabit and a quad port Broadcom. 
    We us the individual ports of the Broadcom for host management and live migration - no problems here. We use the Intel cards for both iSCSI and VM networks. Calling the two intel cards “A” and “B”, and the ports P1-4 we've used AP1, AP2, BP1, BP2 (ports
    1 & 2 of both Intel NICs) for iSCSI connections, and we've created a NIC Team with AP3, AP4, BP3, and BP4 (ports 3 and 4 of both Intel NICs). The team type is "Virtual Machine Load Balancing". We then created a Hyper-V switch based on this team
    for use with all of the VMs created on the host. (as a side note: prior to implementing the NIC team, we just had 4 Hyper-V switches, one associated with each of these 4 ports.)
    The 4 ports of the NIC team are connected to two different Cisco SG200 switches - AP3 and BP3 are connected to switch1, and AP4 and BP4 are connected to switch2 (in an attempt to maximize redundancy). The two Cisco SG200s are simply connected to the rest
    of our network - each to a different switch within the subnet. There is minimal configuration done to the SG200s (for example NO
     link aggregation); spanning tree is enable however.
    My question is: can the network cables be connected to different switches (as they currently are) and if so is there some configuration piece (either on the switch or within Windows) that I'm missing? 
    What are the options here if this configuration is incorrect? The packet loss is in the range of 0.1%, but we've had odd spikes where a VM was essentially unavailable for a brief period (a few minutes) then returned to "normal" (0,1% loss). 
    Pinging a device (like the SG200 itself) or another physical server (for example our domain controller or the hyper-v host itself) results in essentially 0 loss; maybe one or two packets during the course of a 12 hour ping (this was the “normal” ping
    response to VMs before we created the NIC team, so I’m quite sure this has something to do with it).
    Thanks in advance!

    I believe when utilizing the Virtual Machine Load Balancing the ports must be connected to the same switch, stack, or chassis as the arp for the MAC could move.  I believe, although I could be wrong, that the outages you see is when the machine "moves"
    between ports and the arp being updated between the two switches. 
    I believe you are looking for switch fault tolerance teaming which will allow for the failure of adapter, cabling, or switch which will achieve your goal of maximum redundancy.  This is achieved via spanning tree on the switches, which you indicated
    is already configured.
     

  • When upgrading the operating system mac os x 10.5 to 10.6, should i do a back of my computer or if i do it directly i would loss all my music, videos, documents, etc?

    when upgrading the operating system mac os x 10.5 to 10.6, should i do a back of my computer or if i do it directly i would loss all my music, videos, documents, etc?

    Hi ocio,
    First of all, you should always do a backup of your computer before doing an upgrade - always.
    Things can go wrong, and if they do, you will be out of luck without a backup.
    Upgrading should not affect your music, videos, documents, files in general. But don't take any chances in case things go awry....back it all up first!
    Cheers,
    GB

  • IPSLA-ICMP Jitter-Packet loss count

    Hi,
    I wanted to monitor the packet loss in my link using IP SLA. So i configured ipsla jitter and started monitoring it. When i analyze the output i found that ip sla statictics shows heavy drop in my link, but when i ping from the router no drop is observed. Why there is such difference in the out put. I read that normal ping and icmp jitter uses different icmp types messages but now i am confused whether my link proper or not. Which data i should belive.
    Here is my config and statistics:
    ip sla 2166
    icmp-jitter 10.70.194.137 num-packets 100
    frequency 300
    ip sla schedule 2166 life forever start-time now
    Type of operation:              icmpJitter
            Latest RTT: 7 milliseconds
    Latest operation start time: 13:56:49.468 IST Sat Dec 24 2011
    Latest operation return code: OK
    RTT Values:
            Number Of RTT: 92               RTT Min/Avg/Max: 3/7/158
    Latency one-way time:
            Number of Latency one-way Samples: 0
            Source to Destination Latency one way Min/Avg/Max: 0/0/0
            Destination to Source Latency one way Min/Avg/Max: 0/0/0
    Jitter Time:
            Number of Jitter Samples: 89
            Source to Destination Jitter Min/Avg/Max: 1/4/20
            Destination to Source Jitter Min/Avg/Max: 1/1/1
    Packet Late Arrival: 0
    Out Of Sequence: 0
            Source to Destination: 0        Destination to Source 0
            In both Directions: 0
    Packet Skipped: 0
    Packet Loss: 8
            Loss Period Length Min/Max: 1/7
    Number of successes: 1
    Number of failures: 0
    Operation time to live: Forever

    Hello mate !
    For how long you left the IP sla running ? 24 hours ?
    I would disable session time out in your router, set the IP Sla running for 60 minutes for example and in the meantime i would leave a ping running too with high repetition in the background.
    I saw you only had 8 pkt loss....   we need two "tools" running for a good comparison, tried what i proposed and let me know.
    cheers

  • E2000 packet loss (cabled)

    A little back story first.
    A while ago I bought a WRT320N as a trade-in offer, unfortunately I had around 20% packet loss on my connection after I set it up. If running directly through my cable modem I had no connection issues at all.
    I was running the whole setup cabled, and have no peripherals using the wireless connection.
    The router was returned to the retailer for RMA, and in the end I got the purchase credited.
    My setup
    ISP: Dansk Kabel TV (danish provider for internet, TV etc.)
    Modem: Netgear CVD31T  DOCSIS 3.0 compliant Cablemodem (I do not have access to the modem, as it is provided by the ISP.
    I have now bought an E2000, and set it up in the same manner as the previous router.
    This has returned the same problems I had with my previous router.
    Updating the firmware didn't make any difference.
    Using Pingtest.net as my test reference I get results like this.
    when connected directly to the modem I get 0% packet loss, max 20ms ping and jitter is 2-3ms.
    Have I been so unlucky to get 2 faulty routers in  a row, or could there be some problems with Linksys routers and Netgear?
    I have unsuccessfully tried switching cables without any change, tried moving the router "far" away from the modem, monitors etc to see if there could be any interference from the wireless.
    I am really at a loss here - am i looking at yet another return to the retailer - or is there some obscure solution out there ?

    Open the setup page of the router and change the MTU size to 1365. Power cycle the router and see if that makes any difference.
    open the command prompt on your windows computer and type ping yahoo.com and hit enter on your keyboard. Observe the connection.
    You have already upgraded the firmware on your router. After upgrading the firmware on your router, it is recommended that you should reset the router and reconfigure it. Press and hold the reset button on your router for 30 seconds. Release the reset button and wait for 30 seconds. Power cycle the router and reconfigure it.

  • Packet loss

    Hi,
    Going to keep it short and sweet, many of you know about the FIFA/BT/EA problem and the terrible connection online. Here is my latest traceroute to EA, don't know much about this kind of stuff, so are these results normal or is there something distinctly wrong?
    Thanks.

    Ignore the 100% packet loss - it's a red herring. Those hops will be configured to not respond to traceroute type traffic.  If you really did have 100% packet loss, then you'd also get no response from subsequent hops which isn't the case.
    Your "issues" appear to be twofold:
    A significant increase in latency on the transatlantic hop within level3's network.
    Packet loss at EA - possibly (but not necessarily) due to congestion on their network.
    HTH.

  • Security and packet loss problem

    Guys,
    I'm using WRTP54G-NA and I have 2 problems with it...
    First one: is about security, if I access direclty http://192.168.0.1/admin/voice or any other subfolder it doesn't ask me the password...
    The other problem is that I can't let my connetion 100%, It always has packet loss, in both way, wired and wireless (more in wireless), I had already tried to fix the Negotiation to 100Mbps Full duplex, changed the MTU values for different values and there is always packet loss...
    I tried to plug my pc directly to the cable modem and it works perfectly...
    I'm using firmware version 3.1.24, I also tried with 3.1.27, but with 3.1.27 the number of problem increases including now ones...
    Any advice ??
    http://brunozp.com || http://brunozp.com.br
    Solved!
    Go to Solution.

    I don't think that the rotuer will ask you for username & pasword once you login to setup page ... Only once it will show you the same when you are typing http://192.168.0.1 on the browser address bar ...

  • 100% packet loss while trying to update SWTOR

    Hi
    Last few weeks I have been getting only 47kb/s when I download updates that connect to patch.swtor.com. I have asked on there forums and have done a pathping trace and have been told by them that there is a 100% packet loss in hop 3 & 5
    below is the trace
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    pathping cdn-patch.swtor.com
    Tracing route to easwtor.vo.llnwd.net [87.248.210.254]
    over a maximum of 30 hops:
    0 removed
    1 BTHomeHub.home [192.168.1.254]
    2 217.47.72.122
    3 217.47.206.161
    4 213.1.69.42
    5 217.41.169.249
    6 217.41.169.109
    7 109.159.251.201
    8 core2-te0-2-4-0.ealing.ukcore.bt.net [109.159.251.143]
    9 peer2-xe3-3-1.telehouse.ukcore.bt.net [109.159.254.227]
    10 manchester-nasaccess2-fe01.mdip.bt.net [195.99.125.66]
    11 ve5.fr4.lon.llnw.net [69.28.171.138]
    12 cdn-87-248-210-254.lon.llnw.net [87.248.210.254]
    Computing statistics for 300 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 IpowerX20 [192.168.1.64]
    0/ 100 = 0% |
    1 0ms 0/ 100 = 0% 0/ 100 = 0% BTHomeHub.home [192.168.1.254]
    0/ 100 = 0% |
    2 33ms 1/ 100 = 1% 1/ 100 = 1% 217.47.72.122
    0/ 100 = 0% |
    3 --- 100/ 100 =100% 100/ 100 =100% 217.47.206.161
    0/ 100 = 0% |
    4 38ms 0/ 100 = 0% 0/ 100 = 0% 213.1.69.42
    0/ 100 = 0% |
    5 --- 100/ 100 =100% 100/ 100 =100% 217.41.169.249
    0/ 100 = 0% |
    6 40ms 1/ 100 = 1% 1/ 100 = 1% 217.41.169.109
    0/ 100 = 0% |
    7 42ms 4/ 100 = 4% 4/ 100 = 4% 109.159.251.201
    0/ 100 = 0% |
    8 55ms 1/ 100 = 1% 1/ 100 = 1% core2-te0-2-4-0.ealing.ukcore.bt.n
    et [109.159.251.143]
    0/ 100 = 0% |
    9 50ms 0/ 100 = 0% 0/ 100 = 0% peer2-xe3-3-1.telehouse.ukcore.bt.
    net [109.159.254.227]
    0/ 100 = 0% |
    10 54ms 0/ 100 = 0% 0/ 100 = 0% manchester-nasaccess2-fe01.mdip.bt
    .net [195.99.125.66]
    1/ 100 = 1% |
    11 55ms 1/ 100 = 1% 0/ 100 = 0% ve5.fr4.lon.llnw.net [69.28.171.13
    8]
    16/ 100 = 16% |
    12 48ms 17/ 100 = 17% 0/ 100 = 0% cdn-87-248-210-254.lon.llnw.net [8
    7.248.210.254]
    Trace complete.
     SPeed test Below
     Download speedachieved during the test was - 2.71 Mbps
     For your connection, the acceptable range of speeds is 0.6 Mbps-7.15 Mbps.
     Additional Information:
     Your DSL Connection Rate :3.84 Mbps(DOWN-STREAM), 0.45 Mbps(UP-STREAM)
     IP Profile for your line is - 3 Mbps
    ADSL Line Status
    Connection information
    Line state: Connected
    Connection time: 35 days, 17:05:28
    Downstream: 3,840 Kbps
    Upstream: 448 Kbps
    ADSL settings
    VPI/VCI: 0/38
    Type: PPPoA
    Modulation: G.992.1 Annex A
    Latency type: Interleaved
    Noise margin (Down/Up): 11.0 dB / 17.0 dB
    Line attenuation (Down/Up): 47.5 dB / 27.5 dB
    Output power (Down/Up): 20.1 dBm / 12.3 dBm
    FEC Events (Down/Up): 1182413 / 2337
    CRC Events (Down/Up): 1116 / 39
    Loss of Framing (Local/Remote): 0 / 0
    Loss of Signal (Local/Remote): 0 / 0
    Loss of Power (Local/Remote): 0 / 0
    Loss of Link (Remote): 0
    HEC Errors (Down/Up): 15891 / 19
    Error Seconds (Local/Remote): 0 / 0
    Not sure if this information is required but here it is:-
    We have no master socket
    Hub is connected directly to the main phone socket
    no loud noise down the phoneline
    Can this be addressed please as the other week to update the game which was 1.4gigs took me over 6 hours at 0.47kb/s
    below is a link to the post I did in there support section which has extra information
    SWTOR
    this only happens for SWTOR and I also play GW2 but have no issues at all and get 300kb/s which is actually above normal.
    Hope this can be sorted please
    Thanks

    You're not seeing 100% packet loss at those hops. If that really were the case, then you'd get no response from all subsequent nodes.
    The Pathping output is telling you that those nodes aren't responding to 100% of packets addressed to them, but that they are correctly forwarding 100% of packets not addressed to them eg the destination.
    If they were dropping a small percentage of packets it could point to a congested router etc, but the fact that it's 100% tends to suggest that it's more likely that those nodes are simply configured to not respond to ICMP echo requests.
    Of more concern, I would suggest, is the real packet loss within llnw.net

  • TMS reporting - Network Packet Loss

    Hi everyone,
    I am trying to see packet loss reports in TMS but there is no info there.
    My network is : VCS 7.0.2 with movi, c20 and ex60 registered (SIP) to it and a TMS 13.1.2.
    The vcs is a starter pack and the TMS is the demo version. I first registered the endpoint to the vcs and then added the TMS to the network. I the added the endpoints and vcs to TMS. In TMS I see the endpoints and info about them, but unfortunatelly no info in the packet loss report. I made a call between movi and c20 with packet loss but no info was shown in the report.
    I am very new to TMS and I wonder if there is something I should do in order to make the endpoints send packet loss info to TMS.
    I sshed to the endpoints and I can see the info about packet loss and jitter through the api.
    The network described above is my test network on which I can do prety much everything on. I also have the same problem (this time with EX60 endpoints, VCS Control and TMS) on a customer network and on that network I really need to get this working.
    Any help would be much appreciated. Form what I read the endpoints should sent this info through HTTP to TMS. Am I right?
    Thank you for your help.

    Hi Magnus,
    Thank you for your reply. I checked the logs and I get some info over there. I have attached the log.
    Do you know what doc should I check to see if Ex60 is supported?
    10.1.x.y
    TANDBERG Codec C20
    Other type
    Endpoint
    5/8/2012 3:58:51 AM
    Disconnected
    Call id: 3 Port id: 1;
    Remote Number: sip:[email protected] Remote Name: 1853;
    Direction: Outgoing CallProtocol: SIP;
    Bandwidth: 6000 kbps Encryption Mode: Aes128;
    Duration: 00:13:33; Cause Code: Normal call clearing
    10.1.x.y
    TANDBERG Codec C20
    Other type
    Endpoint
    5/8/2012 3:45:19 AM
    Connected
    Call id: 3 Port id: 1;
    Remote Number: sip:[email protected] Remote Name: ;
    Direction: Outgoing CallProtocol: SIP;
    Bandwidth: 6000 kbps Encryption Mode: Off;
    10.1.x.y
    TANDBERG Codec C20
    Other type
    Endpoint
    5/7/2012 6:43:15 AM
    Disconnected
    Call id: 2 Port id: 1;
    Remote Number: sip:[email protected] Remote Name: 1853;
    Direction: Outgoing CallProtocol: SIP;
    Bandwidth: 6000 kbps Encryption Mode: Aes128;
    Duration: 00:14:57; Cause Code: CauseCode_Unknown
    10.1.x.y
    TANDBERG Codec C20
    Other type
    Endpoint
    5/7/2012 6:28:19 AM
    Connected
    Call id: 2 Port id: 1;
    Remote Number: sip:[email protected] Remote Name: ;
    Direction: Outgoing CallProtocol: SIP;
    Bandwidth: 6000 kbps Encryption Mode: Off;
    10.1.x.y
    TANDBERG Codec C20
    Other type
    Endpoint
    5/7/2012 6:28:07 AM
    Got Response
    Got Network Response - TMS will now monitor   the system.;
    System: [email protected] -   10.1.x.y ;
    System Status: No response;
    System Type: TANDBERG C-series   Endpoint;
    Software: s52000 TC5.1.0.280662;
    Hardware: F1AN19D00469 - ;
    System Contact;
    No Contact ();
    Mobile: ;
    Office: ;
    10.1.x.y
    TANDBERG Codec C20
    Other type
    Endpoint
    5/7/2012 6:28:07 AM
    Got Response
    Got Network Response - TMS will now monitor   the system.;
    System: [email protected] -   10.1.x.y ;
    System Status: Idle;
    System Type: TANDBERG C-series   Endpoint;
    Software: s52000 TC5.1.0.280662;
    Hardware: F1AN19D00469 - ;
    System Contact;
    No Contact ();
    Mobile: ;
    Office: ;
    10.1.x.y
    TANDBERG Codec C20
    Other type
    Endpoint
    5/7/2012 6:28:06 AM
    Got Response
    Got Network Response - TMS will now monitor   the system.;
    System: [email protected] -   10.1.x.y ;
    System Status: No response;
    System Type: TANDBERG C-series   Endpoint;
    Software: s52000 TC5.1.0.280662;
    Hardware: F1AN19D00469 - ;
    System Contact;
    No Contact ();
    Mobile: ;
    Office: ;

Maybe you are looking for

  • Using a macbook air?

    Can a macbook air and a external drive work well enough to do basic editing in Fcp? Thanks.

  • How to Migrate EIT security to different Instance

    Hi I have a requirement to migrate the "EIT Security type" information to another instance. Functional Analyst creates an EIT and attaches it to the Responsibility using the following menu. CA Super HRMS Manager Responsibility Security Go to Informat

  • Error 3194  IMPOSSIBLE

    HI I update from 4.3.3 to iOS 5 beta but was Bloopers because I could not properly activation so I restore to 4.3.3 IMPOSSIBLE! it say update failed error 3194

  • Sales retuns should consider in MD04 as Receipts

    Hi, I'm having special requirment, May be you guys faced or have idea; Sales returns Schedule line category checked as " Required/asambly" where as it's creating demand but, I need to created as supply. i.e MD04 should should as +VE Qty for perticula

  • Buy Now paypal buttons for flash 8 basic

    I just bought these buttons off the web and I am trying to use them. Flash says it cannot open the fla files because they contain screens. What does this mean?