| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
I have a customer who is receiving Unsolicited Resets on Decbridge 610
and DECconcentrator 500's. This is not the unsolicited reset issue
that was discussed earlier in this notesfile that was cured by a patch
to SUN OS systems. Sun's are in the network but are not at the rev
level necessary for the patch. The 610's are V1.3 and the 500's are at
V 3.2 of the microcode.
In the DEC ELANEXT MIB V2.7 the variable "esysStatus 2"
esysDeviceBrokenReason (OID 1.3.6.1.4.1.36.2.18.1.2.2.2) always returns
"none" even though it is not supposed to.
Quoting from the MIB "The reason that the Device State is Broken. If
current state is not broken and the Unsolicited Resets counter is
nonzero this object show reason for last failure."
The device is not broken and the unsolicited reset counter is nonzero
and still it returns none. Would prefer to see:
"selftestfail (2)"
"onlinediagfail (3)"
"firmwarefail (4)"
so the problem could be diagnosed.
Any ideas? Did the method of handling ECM Path Tests change in DEC
concentrators and bridges change with the latest microcode?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1062.1 | DECconcentrator V3.3 | PROXY::TAYLOR | Mon Aug 23 1993 11:25 | 8 | |
I don't have any comments on the setting of the status but we did
fix a problem in the DECconcentrator code where an IP packet of
greater than 1500 bytes to the box may cause an unsolicited reset.
Please refer to note 837.6 in this conference for the location of
the DECconcentrator V3.3 savesets.
| |||||