sting@LAOTSE.CAM.NIST.GOV (s. ting) (12/07/90)
We have a T-1 link to SURAnet. At each end is a p4200. We have had troubles with this serial link for at least a year. It appears nothing can be done to fix the problem. Any advices, suggestions, and comments with regard to the problem would be appreciated very much. The symptom of the problem is that once a while the messages like those listed below would be repeatedly reported by the router: SL: RB uid = 8E0A4 iorbp = 8FF1C SL: RB uid = 90FFC iorbp = 8E0A4 IP.005: pkt trunc 92 pkt ln 0 128.167.34.1 -> 129.6.80.194 SL: RB uid = 91CA4 iorbp = 90FFC SL: RB uid = 8FF1C iorbp = 91CA4 SL: RB uid = 90444 iorbp = 8FF1C. Our SNMP-based monitor would show the link up and down, up and down, ... , until you use the test command of t 5 to reset the link. When this happens, the real effect is that the link is essentially being blocked and very little traffic can get through. This problem used to occur not so frequently, roughly once a month. Lately, it occurs almost daily and sometime more than once a day. If it happens at off working hours or nobody notices it to reset it, then the link is essentially dead, but on the other hand, it's still available according to the rip routing table. This is the worst thing you want. SURAnet said that this problem is caused by the chip 68450 on com-2 board and SURAnet has implemented many fixes proposed by Proteon but the problem still persists. I wonder if anyone has experienced the same problem and has the problem somehow fixed, for example, by replacing the chip, com-2 board, or others. Michael Ting, National Inst of Standards & Technology, (301) 975-3802
enger@seka.scc.com (Robert M. Enger) (12/09/90)
hi the fix is obvious: Cisco Sorry, I couldn't resist, Bob