🚀 go-pugleaf

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Ticket Number: ACOnet.980625.1900    Ticket Status: CLOSE
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: 980625.1900	     Problem Starts: 30-JUN-1998 18:00 MET-DST
                                     Scheduled End:  30-JUN-1998 21:00 MET-DST
       Closed: 980701.0830                   Ended:  30-JUN-1998 23:35 MET-DST
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Close.980701.0830:	

	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 

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:	scheduled 3h max
    		actually it took 5:30 until system crashed

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