🚀 go-pugleaf

Subtitle: Gosh darn it Cisco, ya build these damn things too robustly!

Y'all might find this interesting:  

Background: 1 AGS, 1 CGS in two different cities, connected by 2 parallel
T1's routing IP, Appletalk, and bridging Decnet.  

Last weekend I upgraded the AGS to 8.2(4).  Monday rolls around and
all the Appletalk between cities is down.  Appletalk routes between ethernets
but not via the serial lines.  So I call cisco support, I try upgrading to
8.2(4) at the CGS end, still no good.  

The Problem: crossed serial lines (Thanks Cisco Support!)


	 ------         -----     t1     -----         ------
	 |    |---   ---|CSU|------------|CSU|---------|    |
	 |    |   \ /   -----            -----         |    |
         |AGS |    x                                   |CGS |
	 |    |   / \   -----     t1     -----         |    |
	 |    |---   ---|CSU|------------|CSU|---------|    |
	 ------         -----            -----         ------

Who would ever suspect that this stuff would run for over 9 months and
2 upgrades when the two ends of the serial lines aren't connected to their
respective networks.  The only reason it even broke at all was the fact that
in 8.2(4) the software pays attention to the appletalk addresses on the serial 
interfaces and the mismatched addresses prevented routing information from
being transmitted.  
Hey Cisco, to heck with my expensive T1's.  I'm gonna
try plugging an interface card in to the 110v socket.  PG&E rates are much
better that Pac Bell.  Hmmm, Cisco routes over 15,000 watts per second....


Tim Tessin - Cirrus Logic Inc.
tjt@cirrus.com
uunet!cirrus.com!tjt
-- 
Tim Tessin 
tjt@cirrus.com
uunet!cirrus.com!tjt