[comp.dcom.sys.cisco] v.8.2 EGP problem

lcrosby@STL-08SIMA.ARMY.MIL (Linda J. Crosby) (05/03/91)

Reference msg from Benzi Misrahi, 25 Apr.  Problem is also occurring with
EGP.  When we installed 8.2(3) we could no longer communicate with our
EGP neighbor gateways, thus losing all routing information!

After several hours phone hassle, a Cisco technician finally found a reference
somewhere that showed this problem was known.  Unfortunately, there will 
be no fix forthcoming until after the 1st of June.

Our solution was to yank the update, and return to v. 8.1(19).




Linda J. Crosby
Technical Liaison
USAMC SIMA 
<LCROSBY@ST-LOUIS-EMH2.ARMY.MIL>
<LCROSBY@STL-08SIMA.ARMY.MIL>

Tony Li <tli@cisco.com> (05/03/91)

Linda,

The problem that Benzi Mishrahi found is independent of your EGP
problem.  The EGP problem is an interoperability problem with the
Milnet cores and is critical only for Milnet sites.  The symptom is
that we will reach the DOWN state but never transition to the UP
state.  

The fix for this problem will be available in 8.2(4).  If this is an
emergency, I will be happy to provide you with a beta image that you
can netboot or beta ROMs.  

Tony Li

lcrosby@STL-08SIMA.ARMY.MIL (Linda J. Crosby) (05/04/91)

Tony,

"beta image"? ... no thank you!  We've had enough problems the last 72 hrs.
We'll wait until the actual 8.2(4) ver. is released; and check for any
additional bugs before installing it!

If the EGP problem is not the same as the BGP problem; I would very much
like to know what the BGP problem is.  Since there is talk of transitioning
MILNET to BGP; we need to know about it too.


Linda J. Crosby
Technical Liaison
USAMC SIMA 
<LCROSBY@ST-LOUIS-EMH2.ARMY.MIL>
<LCROSBY@STL-08SIMA.ARMY.MIL>

tli@cisco.com (Tony Li) (05/04/91)

   If the EGP problem is not the same as the BGP problem; I would very much
   like to know what the BGP problem is.  Since there is talk of transitioning
   MILNET to BGP; we need to know about it too.

The BGP bug is a much more subtle design flaw.  Suppose that you learn
about a route through an external BGP session and that this route is
redistributed via IGRP as a default network.  Other BGP speakers in
the AS will discard the IGRP information and also discard the
designation of it being a default network.

Clearly IGP information needs to supersede internal BGP information
for internal routing decisions.  We are still discussing what the
correct behavior should be.

Tony