[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 |
2177.0. "DETMI management" by DECPRG::KUPKA () Thu Apr 06 1995 13:10
HUBwatch for Windows 3.1, DENMA 2.1.3, DETMI 1.1, DEWGB 3.1
I have read 2157,2164. So I understand that even though DETMI is not
manageable via DENMA it looks like it is - The correct slot in HUB90 is
occupied and the module is displayed as expected (DECrepeater90TS).
In my case only some DETMIs are in the hub with DENMA. Others are in
hubs which are registered as "communities of current agent". Those
DETMIs are displayed as UNKNOWN and the only way to manage them is
connect the module as standalone.
Could you please confirm, that this is expected behaviour, or give me
some help (FW upg ...)
Thanks,
Tomas Kupka @chk
DECPRG::KUPKA
T.R | Title | User | Personal Name | Date | Lines |
---|
2177.1 | | ROGER::GAUDET | Because the Earth is 2/3 water | Thu Apr 06 1995 13:36 | 3 |
| That is the expected behavior.
...Roger...
|