Hi,
as I've experienced the same, here's a short comment.
You're unlikely to see 600 Mb/s through a PA-GE, as other posters have
mentioned. 600 Mb/s would completely saturate whichever PCI bus in which
the PA-GE is installed.
One of our 7206VXR crashed probably due to overloading a
Hi everybody,
a customer connected with a 7204VXR (NPE-225), PA-E3 has bandwith-problems. The
maximum
outgoing TCP-throughput amounts only 15Mbit/s instead of 34Mbit/s (measured
with iperf
from the customer-side:
[ 5] 0.0-10.0 sec 17.4 MBytes 14.6 Mbits/sec
Incoming bandwith is ok:
[ 4]
/
Thanks, I'll check that :)
Werner
Ian
-Original Message-
From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-
boun...@puck.nether.net] On Behalf Of Werner Detter
Sent: 15 July 2011 11:03
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] PA-E3 in 7204VXR - low bandwith
Hi
Hi,
it may be the long fat pipe issue
http://bradhedlund.com/2008/12/19/how-to-calculate-tcp-throughput-for-lo
ng-distance-links/
well, the latency is pretty much below 3ms so with a window-size of
64KB i get a calculated result of 174Mbit/s tcp-throughput ...
Any other idea's ?
Thank you,
Hi,
i don't understand why i do have the full TCP-bandwith of 32Mbit/s for
incoming traffic but for outgoing there is max. 19Mbit/s TCP-bandwith
possible? Both tests were processed with the same devices...
regards,
Werner
Am 15.07.11 13:52, schrieb Werner Detter:
Hi Ian,
Is that a TCP test
Hi,
http://xtrmntr.org/techie/ipv6/ipv6gen/
Bye,
Werner
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Hi,
*Mar 18 11:35:04.091: bgp_cpu2timeout: seconds: 3, slot: 3 for 5: 0% and
1: 0%
*Mar 18 11:35:34.875: bgp_cpu2timeout: seconds: 3, slot: 3 for 5: 0% and
1: 0%
%LINK-4-NOMAC: A random default MAC address of .0c82.a9fb has
been chosen. Ensure that this address is unique,
Hi,
today I've upgraded the IOS-Software and the Boot-Image on a Lab-Router
(7206VXR + NPE-G1)
to 12.4(23), since then i can see the following funny messages:
*Mar 18 11:35:04.091: bgp_cpu2timeout: seconds: 3, slot: 3 for 5: 0% and 1:
0%
*Mar 18 11:35:34.875: bgp_cpu2timeout: seconds:
Hi again,
Looks like we tried to read from a valid address.
Thanks you for your comments. I suppose changing the
memory isn't a bad idea.
regards,
Werner
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
Hi again,
crashed due to a bus error (bus error at PC 0x6013C4D8, address 0x64588700).
As described in the Cisco document Troubleshooting Bus Error Crashes [1] I've
tried
to figure out to which memory location the address 0x64588700 corresponds to.
'show region' shows, that the address
10 matches
Mail list logo