I saw the 100 routers in an area and had to share this!
I had an instructor a couple of years ago that worked for IBM-Europe. He
said they
tried to keep European areas for countries. 1 Country = 1 Area. This all
came up when
another student asked, "what is a good measure for the number of rout
Well, I wish it was as easy as saying someone tweaked with the timers on the
server but for some reason all our servers are set the same way and so all
of our routers have to be set the same way as well. Not only that, but if
you look at that TokenRing interface, we are using administrative
mac-ad
Very interesting. I wonder why someone would tweak those values on the
server in the first place. Unless all the devices on a LAN segment are
using the same values, problems are going to arise. From the sounds of
it, someone changed the server settings and didn't bother to let
everyone else kno
Yup, I made the changes on the TokenRing interface itself, not the WAN
interface. The original config I posted listed just one of the routers that
was connected via a serial interface (all T1 lines). There are actually 7
serial connections to this and five token rings. Each interface is its own
IIRC, in the config you posted the intervals were changed on a token
ring interface. Is that how you have the 7204 and 2600 connected? If
so, are they the only devices on the token ring?
John
>>> "Fraasch James" 2/5/02 1:58:02 PM >>>
It is Cisco to Cisco. 7204 to 2600.
'By changing the updat
this should also work:
ipx update interval rip changes-only
ipx update interval sap changes-only
those are on the interface itself
-Patrick
>>> "Fraasch James" 02/05/02 03:58PM >>>
It is Cisco to Cisco. 7204 to 2600.
'By changing the update interval from 1 minute to 5 minutes you are
preventi
It is Cisco to Cisco. 7204 to 2600.
'By changing the update interval from 1 minute to 5 minutes you are
preventing the route and server from flapping and thereby keeping your
connection to the server up.'
This is what the Cisco tech said- AFTER I had already put the command in. I
am not sure why
was it traversing two separate vendors by the time it hit the server?
I know with 3com and cisco, the defaults for rip and sap updates are
different. 3com defaults to update on change only...where cisco's defaults
are timed. When you connect both vendors together, cisco will send updates
but 3c
The server must be set with the non-standard 300 second timer also? That
would be my theory.
Priscilla
At 02:50 PM 2/5/02, Tom Martin wrote:
>Does anyone have any idea why this worked??? Setting the RIP and SAP
>timers on a __LAN__ link should have had no positive effect. It seems
>like the o
Does anyone have any idea why this worked??? Setting the RIP and SAP
timers on a __LAN__ link should have had no positive effect. It seems
like the only perceivable change would be the flapping of remote networks
and servers -- assuming that the timers were not modified on the server
also.
Any
10 matches
Mail list logo
