[nsp] Packet loss 7204
Tim Devries
zsolutions@cogeco.ca
Thu, 28 Nov 2002 12:35:13 -0800
This is a multi-part message in MIME format.
------=_NextPart_000_004B_01C296DA.990231D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
I am experiencing some weird packet loss with a customer who is running =
on a 7204. I have a VPN connected to them on a 2621 using GRE tunnels =
and BGP as the routing protocol. Looks like this:
Segment
_____
|
7204
Tun1 | | Tunnel 2
| |
2621
|
-----
Segment
Basically our configuration was working for weeks until they rebooted =
their router. At that point all of our hosts lost connectivity over =
the VPN even though routes were still being advertised via bgp. Then by =
black magic two of our hosts started working again 3 days later, but one =
host is still not able to connect to them. A trace from this host shows =
it is transiting the tunnel and makes it at least as far as their vpn =
endpoint (sometimes it makes it further into their backbone).
Both of our route tables are correct, and access-lists have been ruled =
out.
Now, no one has made any config changes, and I've reviewed their =
configuration and it looks to be correct. So I guess what I am =
wondering is if anyone is aware of any issues with the 7204 running =
12.1.9E (I believe) doing crypto/BGP/OSPF+FW feature set?
------=_NextPart_000_004B_01C296DA.990231D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am experiencing some weird packet =
loss with a=20
customer who is running on a 7204. I have a VPN connected to them =
on a=20
2621 using GRE tunnels and BGP as the routing protocol. Looks like =
this:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial=20
size=3D2> =20
Segment</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2> =20
_____</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p; =20
|</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p;=20
7204</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tun1 =20
| | Tunnel 2</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =20
| |</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p;=20
2621</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p; =20
|</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p;=20
-----</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p;=20
Segment</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Basically our configuration was working =
for weeks until they rebooted their router. At =
that point=20
all of our hosts lost connectivity over the VPN even though routes were =
still=20
being advertised via bgp. Then by black magic two of our hosts =
started=20
working again 3 days later, but one host is still not able to connect to =
them. A trace from this host shows it is transiting the tunnel and =
makes=20
it at least as far as their vpn endpoint (sometimes it makes it further =
into=20
their backbone).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Both of our route tables are correct, =
and=20
access-lists have been ruled out.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Now, no one has made any config =
changes, and I've=20
reviewed their configuration and it looks to be correct. So I =
guess what I=20
am wondering is if anyone is aware of any issues with the 7204 running =
12.1.9E=20
(I believe) doing crypto/BGP/OSPF+FW feature set?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML>
------=_NextPart_000_004B_01C296DA.990231D0--