Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ncar!csn!boulder!daemon
From: ralls@cisco.com
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Status of 8.2(1)
Message-ID: <32123@boulder.Colorado.EDU>
Date: 7 Feb 91 16:47:07 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 25


>We've had a problem with XNS RIP not properly recognizing that serial
>lines are down.  The route still exists in the routing table as
>directly connected, although SHOW INTERFACE correctly says the line is
>down.  This probably also exists in 8.1.  cisco thinks that they have a
>fix.

I don't know of any such problem. There *was* a problem (only in 8.2)
where if a directly connected network went down and the route was
deleted, when that directly connected network came back the entry
in the routing table would be incorrect. This could be repaired
by removing then adding the network i.e. "no xns net <n>"
, "xns net <n>".

This would only happen if a directly connected network was down
long enough to be deleted. The directly connected routes age out
just like other routes so it takes a few minutes for them to be
removed. (This is differant from 8.1 where directly connected routes
were not removed at all.)

If this is not the problem you are refering to please let me know
because I will need to look into it.

Vicki Ralls
cisco Engineering