🚀 go-pugleaf

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Ticket Number: ACOnet.980803.1130    Ticket Status: CLOSED
Ticket Type:   SCHEDULED             Ticket Source: ACOnet
Ticket Scope: Router                 Site/Line: Service.ACO.net
Ticket Owner: Christian Panigl       Problem Fixer: VUCC/ACOnet/Cisco
Ticket Opened: 980803.1130	     Problem Starts:  3-AUG-1998 13:00 MET-DST
       Closed: 980804.1100                   Ended:   4-AUG-1998 09:40 MET-DST
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Close.980804.1100 of Ticket ACOnet.980803.1130:

	Also with 11.2(15)P, we had severe performance problems on our
	router Service.ACO.net since ~3:00 MET-DST after ~14:00 hours uptime
	on both high-speed interfaces: FE and ATM.  

	Router just slowed down, SW didn't crash -> again no dump.
	Cisco TAC & engineering helpless :-(
	
	Stepped back to stable 11.2(11)P


Re-Open Ticket ACOnet.980716.1645 as ACOnet.980803.1130:

	Re-trying this time with newest 11.2P release: 11.2(15)P


===============================================
Re-Open Ticket ACOnet.980625.1900 as ACOnet.980716.1645
	closed  20-JUL-1998 12:30 MET-DST without new findings.

===============================================
Close.980701.0830 of Ticket ACOnet.980625.1900:

	Problem did not show up in exactly the same shape as in April, 
	however, finally ~23:30 the system 11.2(12)P was "reloaded by bus
	error".  Cisco engineer is now working on the stack trace.  Router
	is now running 11.2(11)P again which was previously running stable
	for more than 2 months.
	
Problem Description:

	In late April we have reported a problem with 11.2(12)P on a
	C4700/ATM/FE/6E configuration (Service.ACO.net) and stepped back to
	11.2(11)P.  Because Cisco engineering was not yet able to reproduce
	the problem in their lab we offered them to try it "real-time" again
	on Tuesday, 30.6.98 and again for the weekend 17./18./19.7.98

Affected:	After reload to 11.2(12)P the router is expected to
    		misbehave and probably even crash.  Therefore in the given
		timeframe all Services behind "Service.ACO.net" might be
		degraded, specifically Newsfeeds, access to ns2.univie.ac.at
		and some WEB pages (aco.net, nic.at, vix.at ...)

Actions:	Reload to 11.2(12)P and wait for problems/crash.
    		Reload to known stable 11.2(11)P afterwards.

Time to fix:	unknown

==============================================================================