Percantage of packet loss on link

I am working with Cisco routers and i need somehow to find out packet loss percentage for each link (actual). I was trying to use ICMP Jitter IP SLA operation, which unfortunately returns only the number of dropped packets. So i need to get via SNMP the number of transferred packets on line to calculate the percentage. Which OID should i use to obtain this information?

Be careful, by definition a 10 Mbit half-duplex connection is equivalent to a single T1 of bandwidth, nothing even close to 6 Mbit of bandwidth. If you are running QoS (assuming CBWFQ and LLQ), based on a shaped parent policy equal to 6 Mbit you will definitely oversubscribe the 10 Mbit half-duplex connections by a significant margin.
The reason for this is that a T1 is 1.536 Mbit full-duplex (over 3 Mbit of bandwidth). A 10 Mbit half-duplex connection maxes out of usable bandwidth at about 30% utilization, with almost 100% packet loss (due to excessive collisions) at 40% utilization. As you can see, 40% utilization on a half-duplex 10 Mbit connection is equal to about 4 Mbit of bandwidth and a single T1 is over 3 Mbit of bandwidth. Again, not anywhere close to 6 Mbit of bandwidth.
Assuming you are shaping at 6 Mbit with a child CBWFQ and LLQ policy (you are shaping, right?), you will not be able to guarantee that rate of bandwidth which will crush your audio/video call.
Let me know if you have any questions/comments...

Similar Messages

7613 Router - Packet-loss on a LAN link between 6704 and ES 2T

Hi
After connecting two ends of a 10 Gig LAN Link from a 6704 on one 7613 to a ES 2T on another 7613 , then we have packet loss on that link beyond a specific traffic limit !
Please note that after changing both boards to ES 2T we have no problem and LAN/WAN mode is also checked .

Ash wrote:
It's dropping pings, you can see that clearly from the above. It's intermittent. Whilst a drop in pings isn't the definitive sign of packetloss, the way in which it's doing it is.
If it was going to drop it through flooding it simply wouldn't respond at all after the first few. It it was configured to not respond, it simply wouldn't.
Pings to any external source - (not to the device itself) are also failing intermittently. This indicates that a device along the traffic path is having issues.
I can screenshot a nice disconnection plug in games, but there's no real need.
The evidence is there if you know how to interpret it. This needs to be investigated.
A question for you then!
What happens when your router gets repeated pings from the same source?
Does it not block them as a possible DDOS attack?
The more gamers try this tactic the worse their traces will get & it will more than likely also affect other gamers interested in low latency through these same nodes!
Check the timings between the true source & destination by all means but please do not
unnecessarily stress individual points on the main ISP network backbones!
"I have this awful feeling someone is watching every move I make (one of my pet hates is router location tagging)." Marvin (A paranoid Android)

Terrible Packet Loss in Game- Please help!

Computing statistics for 100 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Sam-PC.home [192.168.1.5]
0/ 25 = 0% |
1 2ms 0/ 25 = 0% 0/ 25 = 0% Wireless_Broadband_Router.home [192.168.1.1]
1/ 25 = 4% |
2 13ms 1/ 25 = 4% 0/ 25 = 0% L100.WASHDC-VFTTP-126.verizon-gni.net [173.66.228.1]
0/ 25 = 0% |
3 11ms 1/ 25 = 4% 0/ 25 = 0% G1-5-0-4.WASHDC-LCR-21.verizon-gni.net [130.81.213.68]
0/ 25 = 0% |
4 20ms 1/ 25 = 4% 0/ 25 = 0% so-12-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.151.230]
0/ 25 = 0% |
5 12ms 1/ 25 = 4% 0/ 25 = 0% 0.xe-8-0-0.BR2.IAD8.ALTER.NET [152.63.38.129]
0/ 25 = 0% |
6 34ms 1/ 25 = 4% 0/ 25 = 0% ae17.edge1.washingtondc12.level3.net [4.68.62.137]
0/ 25 = 0% |
7 33ms 2/ 25 = 8% 1/ 25 = 4% vl-3503-ve-117.ebr1.Washington12.Level3.net [4.69.158.26]
0/ 25 = 0% |
8 29ms 3/ 25 = 12% 2/ 25 = 8% ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
0/ 25 = 0% |
9 30ms 2/ 25 = 8% 1/ 25 = 4% ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]
0/ 25 = 0% |
10 50ms 1/ 25 = 4% 0/ 25 = 0% ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
1/ 25 = 4% |
11 56ms 2/ 25 = 8% 0/ 25 = 0% ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
0/ 25 = 0% |
12 54ms 2/ 25 = 8% 0/ 25 = 0% ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
0/ 25 = 0% |
13 54ms 2/ 25 = 8% 0/ 25 = 0% 4.59.197.34
1/ 25 = 4% |
14 50ms 3/ 25 = 12% 0/ 25 = 0% 64.25.32.9
0/ 25 = 0% |
15 --- 25/ 25 =100% 22/ 25 = 88% 64.25.32.26
0/ 25 = 0% |
16 48ms 3/ 25 = 12% 0/ 25 = 0% 64.25.39.1
These are the results of a test I ran, but I don't know how to solve the problem. The game is unplayable because of the amount of packet loss. I know it is an issue of connection between the game and my router, so should I get a new router if mine is old?

The router I would imagine to be okay for the first bit, but for the sake of things, reboot the router and also try giving your ONT a reboot by unplugging it from AC power and then disconnecting the battery. Re-connect it after 30 seconds by connecting the battery and then plugging it back into AC power.
Also, see if the packet loss takes place during specific times of the day. If your router has a WAN connection over Coax (rather than an Ethernet connection) to your ONT, also consider checking your MoCa speeds based on this FAQ. Poor MoCa speeds can suggest shoddy coaxial causing some issues, too: https://secure.dslreports.com/faq/verizonfios/3.2_MOCA#16569
========
The first to bring me 1Gbps Fiber for $30/m wins!

Packet loss when flood pinging a Mac

I had some trouble transferring large files between my iMac and my MBP the other day and so started a bit of investigation. Mistake really - here is what I found:
All mac targets are running up-to-date Leopard and use intel processors.
The home network has a linksys wireless router - all devices connected by copper.
flood ping tests with command 'sudo ping -f <target>:
from iMac to MBP shows 30% packet loss
from MBP tp iMac shows 33% packet loss
from iMac to windows laptop 0% packet loss
from iMac to linksys router 0% packet loss
from iMac to Freecom NAS box 0% packet loss
from MBP to windows laptop 0% packet loss
from MBP to linksys router 0% packet loss
from MBP to Freecom NAS box 0% packet loss
I took the macbook to work and picked targets on another site, several busy switch hops away.
from MBP to windows desktop 0% packet loss
from MBP to another iMac 26% packet loss
from MBP to mac mini 28% packet loss
from MBP to linux server 0% packet loss
from linux server to MBP 32% packet loss
The firewall is off on all the targets.
Seem clear enough - Mac machines can't handle high ping loads. It is no good telling me they don't have to. If they can answer a ping at all, they should be able to handle the load. It is a perfectly acceptable way of stress testing the link. File transfers are generally not an issue but now I want to know...
Why can't the macs handle the ping floods?
Is this indicative of any other weakness in the IP stack?
Pete

I had a suspicion of packet loss on my internet connection but could not be certain it was the ISP at fault. The fact that I had been having trouble transferring large files between my machines led me to look for possible local problems.
Network fault finding should always examine the hardware first so I wanted to see if there was anything about the cabling or the router which might be causing packet loss.
Actually copying data about the network is a pretty poor way to test things because you have several additional layer of complexity that can colour the results.
When I had narrowed down the flood ping packet loss to the macs, I went hunting on the 'net. There were plenty of people who were reporting various kinds of packet loss. Enough of them that I wondered if there was something more to it. Some of them were talking about similar symptoms to mine. The respondents usually answered a question other than the one asked so I thought I would put up some tests and see if there was actually a problem anywhere.
Now I know it is a 'feature' rather than a fault, I can work around it.
Thanks anyway
Pete

What can I do about Packet Loss?

Hey Verizon Community,
As the title says, what can I do about packet loss?
I have been having network spike issues in the video game Starcraft II, and Blizzard support told me to run a pathping to their servers (pathping pasted below). Upon doing that, I discovered that in hop 4, also known as G0-5-4-5.BLTMMD-LCR-22.verizon-gni.net [130.81.191.214], there was 2% packet loss. What can I do about this? Who can I contact to try and get this resolved?
PATHPING TO BLIZZARD SERVERS:
Tracing route to 12.129.202.154 over a maximum of 30 hops
0 Mitch-PC [10.0.0.2]
1 10.0.0.1
2 Wireless_Broadband_Router.home [192.168.1.1]
3 L100.BLTMMD-VFTTP-40.verizon-gni.net [96.244.79.1]
4 G0-5-4-5.BLTMMD-LCR-22.verizon-gni.net [130.81.191.214]
5 ae1-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.238]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Mitch-PC [10.0.0.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% L100.BLTMMD-VFTTP-40.verizon-gni.net [96.244.79.1]
0/ 100 = 0% |
4 11ms 2/ 100 = 2% 2/ 100 = 2% G0-5-4-5.BLTMMD-LCR-22.verizon-gni.net [130.81.191.214]
0/ 100 = 0% |
5 23ms 0/ 100 = 0% 0/ 100 = 0% ae1-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.238]
Trace complete.

Actually it means nothing since its in the middle of the tracert. Probably the server supports the ping, but at a very low priority so the packets are being counted as lost. Many servers don't even respond to tracert.

Packet loss, full strength connection

So, just recently I have found that my connection to webpages times out. In firefox i will get the can't connect to site page, then i press try again and usually it works. When I use terminal and ping www.apple.com for example i will get ping times of 900ms and then maybe 80ms, after 15 pings i will get a report saying i have packet loss between 15 and 25%. Does anyone have any ideas why this is happening? It's totally out of the blue. I'm using a D-link DIR-625 wireless N router. I've never had these problems before. My Windows pc that is connected wirelessly to the router has no problems connecting to any pages.

May be a bit late, but I have found this tool to be helpful with diagnosing my wireless network faults :
AP Grapher - http://www.chimoosoft.com/
I have all sorts of problems with my wireless. Even things like someone opening the sliding door can cause my network to drop out. If as you say this is a recent problem, have you recently purchased cordless phones? Well check the tool and see if there is any noise coming across on the signal and try and work back from there.

Packet Loss between ASA and 871

We are running a Cisco ASA 5505 and remote clients are 871's. We currently use a EasyVPN configuration between the single ASA and our 13 871's.
Today (1) out of the (13) tunnels is experiencing packet loss. I have power cycles the broadband router on the 871 end and the 871 and the situation still exists.
Does anyone know what would cause this and how to troubleshoot it?
Thanks,
Jason

Have you contact broadband provider on the 871 side to rule out any issues on the link? what broadband ADSLAM pppoa? start first rulling out physical issues WAN interface, LAN interface stats and work your way up, is this is something that suddenly developped? from what you post indicates it seems this tunnel have been fine, it could be broadband link issues but fist investigate with provider to go the next step.
what do you see in 871 router logs in terms of links, turn on logging informational before staring debugg proceedures.
HTH
Jorge

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.

EEM- Email alert with IP SLA Based on Packet Loss

hi joseph,
i need your advise, i want to get alert email based on IP SLA Packet loss
the scenarion as below :
1. If the traffic hit threshold packet loss greater than 20% as long 15 minutes --> send email
2. If reset condition packet loss eq 0% as long 15 minutes --> send email again
I don't know how to configure it condition. could you help me to verify my configuration below?
ip sla logging traps
ip sla 1
icmp-jitter 10.216.0.105 source-ip 10.216.0.107 num-packets 100 interval 40
frequency 50
ip sla schedule 1 life forever start-time now
ip sla reaction-configuration 1 react Packetloss threshold-value 3 1 threshold-type immediate action-type trapOnly
ip sla enable reaction-alerts
event manager applet TEST
event syslog pattern "IP SLAs$1$: Threshold exceeded"
action 2.0 mail server "10.240.0.10" to "[email protected]" from "[email protected]" subject "Alert for Intermittent Link" body "link intermittent in x %"
thank you

What's you have could work with a few modifications. First, increase that threshold-value of 3 to 20. You can leave the falling threshold value of 1. You'll need to add another applet to match the falling threshold syslog message. Not sure exactly what that one will look like.
The first applet will look like this:
event manager environment q "
event manager applet ipsla-threshold-exceeded
event syslog pattern "IP SLAs$1$: Threshold exceeded"
action 001 cli command "enable"
action 002 cli command "config t"
action 003 cli command "no event manager applet ipsla-healthy"
action 004 cli command "event manager applet ipsla-unhealthy"
action 005 cli command "event timer countdown time 900"
action 006 cli command "action 1.0 mail server $q 10.240.0.10$q to $q [email protected]$q from $q [email protected]$q subject $q Alert for Intermittent Link$q body $q link intermittent in 20 %$q"
action 007 cli command "action 2.0 cli command enable"
action 008 cli command "action 3.0 cli command $q config t$q"
action 009 cli command "action 4.0 cli command $q no event manager applet ipsla-unhealthy$q"
action 010 cli command "action 5.0 cli command end"
action 011 cli command "end"
And the second applet (the one where you'll need to fill in the appropriate syslog pattern) will look like:
event manager applet ipsla-threshold-normal
event syslog pattern "FALLING THRESHOLD PATTERN HERE"
action 001 cli command "enable"
action 002 cli command "config t"
action 003 cli command "no event manager applet ipsla-unhealthy"
action 004 cli command "event manager applet ipsla-healthy"
action 005 cli command "event timer countdown time 900"
action 006 cli command "action 1.0 mail server $q 10.240.0.10$q to $q [email protected]$q from $q [email protected]$q subject $q Link is stable$q body $q Link has been stable for 15 minutes$q"
action 007 cli command "action 2.0 cli command enable"
action 008 cli command "action 3.0 cli command $q config t$q"
action 009 cli command "action 4.0 cli command $q no event manager applet ipsla-healthy$q"
action 010 cli command "action 5.0 cli command end"
action 011 cli command "end"

Ping Packet Loss across MPLS TE Tunnels

Hello...Please Help,
I have a Single Area OPSF network running across 4 main routers via GigEth Ckts. The OSPF Network is working correctly. I recently implemented MPLS TE creating two Tunnels - One Explicit Path and One Dynamic Path. Two of the Routers also have a T1 Frame Relay Link over which the Explicit path is configured. It is up and woking but I am experiencing 50-60 percent packet loss when pinging between these PE routers. When I force it to the dynamic tunnel it follows the same FR path and experiences the same packet loss. There is no packet loss anywhere else in the network.
This is a Lab environment w/three LAN's Two 7206VXR & Two 3745 routers and Three 3550 Switches - one per LAN
Suggestions?

Thank You for your response. The problem may not be an MPLS TE problem.
But would my "path-option" and "priority" being set the same for the Dynamic and Explicit Tunnels cause one tunnel to come up and the other go down and cease to signal. Right now I have one or the other working when viewed w/the "show mpls traffic-eng tunnels" command. If I take one down the other works.
The IPs are 10.1.101.1 & 2/30 respectively for the FR Link. That was a Typo...I have corrected it.
The FR interfaces are not SubInt's as the Serial Interface holds the IP address. These are strictly Point to Point but I have the "IP OSPF Network Broadcast" command set and OSPF going across them.
I have SubInt's set on the Gi0/3 Interface.
Gi0/3.1 & 3.10 for VLAN's 1 & 10
There are not any drops when pinging from Within the routers "Interface to Interface".
But when I ping the LAN Node to Node or from within the Router "if" I do not specify an "interface source" I receive the drops.
The result is the same from either side of the Network on both of the 7206 Routers.
Thanks, Kevin

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.

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

90% Packet Loss while online gaming. Almost sure i...

I have been experiencing heavy packet loss for about 3 months now, hoping it would disappear at some point.
Now that I realise it won't go away, I have contacted BT and all they've done is "turn off my ping latency" which is complete bull, and refer me to the BT experts, which I'm also sure are useless.
I've been trying ping, pathping and tracert commands to the servers I connect to. Ping shows 0% packet loss, tracert has request timeouts, and pathping doesn't even go past the 1st hop.
I don't even know what to do now, this wasn't an issue before, it just popped up suddenly and I can't fix it.
After using the ping -t command to my gateway address, I am 100% sure it is a BT routing issue that needs to be fixed.

Hi neve1176,
Thanks for posting. Can you post up the results of your tracert and one from the BBC site for comparison and we'll take a look.
Cheers
David
BTCare Community Mod
If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)

50% Packet loss

Hi,
This is my 1st time using these forums, I hope you can help me.
3 weeks ago I moved house, since then I have reported 2 faults on the line both due to very low IP profiles (0.14).
4 days ago the BT faults team (over the phone) managed to reset my profile and all has been great up until tonight.
My current profile seems fine, however when I ping bbc.co.uk I end up with lots of time outs and around 50% packet loss.
I did a pathping to bt.net and also ping tested Hop 3 and it seems to be here where my problem is (full results below)
Please advise on a course of action, I tried to can BT faults but was on hold for 2hrs and eventually gave up... as you would.
I am also from Western Scotland (Isle of lewis)
Please help
C:\Users\Xoranium>pathping bt.net
Tracing route to bt.net [193.113.211.125]
over a maximum of 30 hops:
0 Xoranium-PC.home [192.168.1.64]
1 BTHomeHub.home [192.168.1.254]
2 217.47.106.122
3 217.47.106.193
4 213.1.69.166
5 31.55.165.102
6 31.55.165.43
7 31.55.165.107
8 * acc1-10GigE-9-2-0.mr.21cn-ipp.bt.net [109.159.250.100]
9 core1-te0-14-0-3.ealing.ukcore.bt.net [109.159.250.5]
10 core1-pos1-0.birmingham.ukcore.bt.net [62.172.103.81]
11 iar1-gig5-4.birmingham.ukcore.bt.net [62.6.196.94]
12 62.172.57.218
13 * * *
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Xoranium-PC.home [192.168.1.64]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% BTHomeHub.home [192.168.1.254]
0/ 100 = 0% |
2 42ms 0/ 100 = 0% 0/ 100 = 0% 217.47.106.122
20/ 100 = 20% |
3 --- 100/ 100 =100% 80/ 100 = 80% 217.47.106.193
0/ 100 = 0% |
4 54ms 26/ 100 = 26% 6/ 100 = 6% 213.1.69.166
0/ 100 = 0% |
5 54ms 23/ 100 = 23% 3/ 100 = 3% 31.55.165.102
0/ 100 = 0% |
6 --- 100/ 100 =100% 80/ 100 = 80% 31.55.165.43
0/ 100 = 0% |
7 54ms 26/ 100 = 26% 6/ 100 = 6% 31.55.165.107
0/ 100 = 0% |
8 64ms 25/ 100 = 25% 5/ 100 = 5% acc1-10GigE-9-2-0.mr.21cn-ipp.bt.net [109.159.250.100]
0/ 100 = 0% |
9 62ms 20/ 100 = 20% 0/ 100 = 0% core1-te0-14-0-3.ealing.ukcore.bt.net [109.159.250.5]
6/ 100 = 6% |
10 64ms 32/ 100 = 32% 6/ 100 = 6% core1-pos1-0.birmingham.ukcore.bt.net [62.172.103.81]
0/ 100 = 0% |
11 72ms 26/ 100 = 26% 0/ 100 = 0% iar1-gig5-4.birmingham.ukcore.bt.net [62.6.196.94]
8/ 100 = 8% |
12 67ms 34/ 100 = 34% 0/ 100 = 0% 62.172.57.218
Trace complete.
Solved!
Go to Solution.

if you try this link you will see there were problems last night in western Scotland https://www.bt.com/consumerFaultTracking/public/faults/tracking.do?pageId=31
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

Serious packet loss creating roaming network over Ethernet.

Comcast Business Gateway modem/router with static addressing provides one address for an externally accessible web/mail server on one of its four RJ45 LAN ports. The second RJ45 LAN port provides a second external address with NAT & DHCP to an internal private 10.1.10.x network connected to a 24-port Netgear gigabit switch. The Netgear is our home's primary switch, with most of the ports going to different jacks thrpughout our house. We have various PCs and Macs, a home server and other similar devices hardwired through the house jacks back to the Netgear receiving DHCP assignments from the Comcast router.
We've had (1) Airport Extreme base station (last generation, not the tall one) connected to the network, also receiving a DHCP IP address from the Comcast box. It's set to bridging mode, cabled from its WAN port by CAT5e to the Netgear switch and offering a Wi-Fi SSID with WPA2 PSK. NAT/DHCP etc is disabled. IPv6 is set to link-local only. No disks attached. Wireless channels set to Automatically.
At this point we have fairly smooth network performance, everything connects immediately (iOS devices, Android devices, utility boxes, computers, etc) and 0% apparent packet loss.
We have some weak Wi-Fi coverage on the far side of the house and I'd like to establish a roaming network, with a new Airport Express (most recent gen) plugged into a wall jack on that side of the house, cabled by Ehternet back to the Netgear, and set up identically. Same SSID and PSK. But when I activate this, I'm finding the network gets anywhere from 88% to 98% packet loss pinging the Comcast router and going outbound. And none of the iOS devices I tried could establish a functional network connection.
I tried replacing the Airport Express with another similar Airport Express, to same effect. I set the Airport Express to create a second SSID and that seemed to work OK, but then I had two distinct networks instead of a roaming network. I also tried disabling DHCP on the Comcast router and enabling it on the Airport Extreme Base Station, but still had the same packet loss. I also tried setting one, the other, and then both Airport boxes to static addressess bypassing the DHCP for their LAN-side connections (although still bridging) and still too much packet loss. No matter what I do, I can't seem to establish a functional Ethernet-connected roaming network with both Airport boxes.
Any ideas?

Thank you for the reply. The Netgear switch I'm using is a GS724T -- it has management features which I'm working through, but all the ports are set to auto-negotiate and the port the Airport Express is on is lit for 100baseT. I didn't see any way to set the MTU in the Airport Utility menus/buttons.
When I join the Airport Express to the network, it sets up the roaming network as intended. But then performance all across the switch goes downhill -- even when pinging from a PC attached to one of the switch ports to the Comcast router I get 90% packet loss or worse, so that nothing seems to get out or in until I disconnect the Airport Express.. It's that dramatic a difference. It doesn't make sense to me that a wireles roaming network across the two Airport boxes should kill performance through the router...

Percantage of packet loss on link

Similar Messages

Maybe you are looking for