🚀 go-pugleaf

The problem (see attached) may be related to the level of
Token-ring microcode you are running. I have a case opened
with cisco dating back to February, case number 15766. They
have not come up with a resolution yet. When I tried to
upgrade from SBEMON 2.0(112) to 3.0(1) I had trouble on
the 4Mb rings that were highly utilized to the point where
the cisco would crash on a bus error. Prior to the crash I
received reset failed messages for the interface. I am
currently running my 16Mb rings on the 3.0 code and my
4Mb rings on the 2.0 code. I just hope the problem doesnt
surface on the 16Mb ring when my users are able to push
it to 90+ %.


Bill Rippon         Phone: 914-784-7479
IBM Watson Research Center     Email: bjripp@watson.ibm.com

------- Forwarded Message

Date:    Mon, 31 Aug 92 20:11:08 +0700
From:    Peter Hakanson <peter@cyklop.volvo.se>
To:      cisco@spot.colorado.edu
Subject: TR-3-RESETFAIL: Unit 0, reset failed, error code 00007F32.

since you guys out there so rapidly answers my questions,
we have an acute problem with an AGS+ and t/r 16 Mbit board.
(AGS+ 8.3(3), CSC-R16 in 4Mbit mode, 5 4E4T boards in box)

After power on we get :
%TR-3-RESETFAIL: Unit 0, reset failed, error code 00007F32.
- -Traceback= 97F98 97D0E 970B6 96FD2 9C5FC 12766 37F8 1D1E

and the manual states : 'if message recurs, contacr Cisco Systems.'

I did this, now i've waited the hour they said and noone has called me yet.

Does anyone out there knows what to do ?
- --
Peter Hakanson  VolvoData Dep 2230 phone +46 31 66 74 27

------- End of Forwarded Message