[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
|
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
1095.0. "MAM reset problems..." by PADNOM::PEYRACHE (Jean-Yves Peyrache Country Support Group France) Thu Jun 09 1994 10:48
hi,
i have tested a very bad result of mis-configuration for FDDI module
in deep:
configure Deconcentrator V2.0 with PORT A and B in the Backplane
create an FDDI lan
put the Deconcentrator on it
configure a DECbrigde900 MX V1.2.1 with port A and B in the BAckplane
tried to put Decbridge900 on the same FDDI LAN that my Deccontrator
(i know it's supported)
afterthat error message appears on the Windows screen "can't communicate
with specified agent"....
of course if, i goes directly in the console port of Dechub900,i see
that the Dechub900 (mam) has crashed (error log ), and the ip address
has deappears and finally , the MAM have losing all configuration (ip
address,trap address,lan interconnect),in fact. i have resetted my Dechub900
with factory setting without selecting this option!!!!!
it's really safe ,even if this kind of configuration is'nt supported
thanks for any comments
Jean-Yves
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1095.1 | | LEVERS::SLAWRENCE | | Mon Jun 13 1994 13:51 | 3 |
| Can you identify the MAM rev (should be V3.0.0), and can you dump the
Error log from the MAM?
|
| 1095.2 | more infos | CLPR01::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Wed Jun 15 1994 13:09 | 45 |
| Follow errorlog from Hub900 V3.0.0
thanks for any feedback
Jean-Yves
Entry = 14
Time Stamp = 0 0
Reset Count = 19
Stop Thrash Cleared Non-Volatile Data.
Dump another entry [Y]/N? y
Entry = 13
Time Stamp = 0 0
Reset Count = 18
Catch VO=07C SR=2000 PC=41F0BE
Dump another entry [Y]/N? y
Entry = 12
Time Stamp = 0 0
Reset Count = 17
Catch VO=07C SR=2000 PC=41F0B6
another entry [Y]/N? y
Entry = 11
Time Stamp = 0 0
Reset Count = 16
Catch VO=07C SR=2000 PC=41F0AC
Dump another entry [Y]/N? y
Entry = 10
Time Stamp = 0 0
Reset Count = 15
Catch VO=07C SR=2004 PC=41F058
Dump another entry [Y]/N? y
Entry = 9
Time Stamp = 0 0
Reset Count = 14
Catch VO=07C SR=2000 PC=41F0BA
|
| 1095.3 | | NACAD2::SLAWRENCE | | Thu Jun 16 1994 10:35 | 11 |
|
The factory reset you got was because the hub had crashed during
initialization several times in a row; this is 'thrash protection'.
Somehow, your non-volatile configuration data had been corrupted such
that it was causing a crash in initialization; the configuration was
cleared so that the hub could initialize. Not very pretty, but better
than a hub you can't use at all.
It looks (at first glance) like a problem that I saw a couple of times
here. Had you just upgraded the MAM to V3.0.0 in the running hub?
|
| 1095.4 | 2 weeks after | PADNOM::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Fri Jun 17 1994 05:18 | 7 |
| >>It looks (at first glance) like a problem that I saw a couple of times
>> here. Had you just upgraded the MAM to V3.0.0 in the running hub?
no upgrade , has been done since 2 weeks
anything else ??
Jean-Yves
|