[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 |
2940.0. "DS90M Commun. Public only works!!" by ZUR01::ACKERMANN () Wed Nov 01 1995 07:55
Hello all,
The Management of the DECserver 90M seems to be changed
from Hubwatch 3.1 to 4.0 or 4.1.
It is not possible any more, to manage a DECserver 90M
in a DECHub900 with Community other then "Public" !
An Entry in the Community Table as an Agent is done. When you
do a "make Current" from the DS90M Agent alone, it works.
But just in the display with the whole Hub klick on the
DS90M (Community for Exampl: "sup90m") then you get the
Error Message: "No Agent Specified for the Slot MAC-Address"
FW Versions: Hubwatch: 4.1.1/Hub900 Mgnt Module: 4.1.0 and
DS90M: NAS 1.5 BL95-32.
This happens in our Commun. HUB in MCS Network Support
and on the Customer Site.
So, ist this a known Bug, i think the Problem must be
known as in Note: 2776.* but there is no Answer about
this problem!
So please, if it is known, is there a Bugfix
for it in future or in Hubwatch 5.0 ?
Thanks
Daniel
T.R | Title | User | Personal Name | Date | Lines
|
---|