[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
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

3402.0. "Can a DECserver 90M be Managed by a DECrepeater 90TS?" by SVCVAX::GAMBARDELLA (Gamby Gumba) Mon Mar 25 1996 20:51

Greetings,

I am having trouble managing a Decserver 90M in a Dechub 90 chassis using a 
Decrepeater 90TS as the agent.  I am running Hubwatch for windows 4.1.1. The
DR90TS is at f/w 2.0.0 and the DS90M is at v1.5.  My problem is that from the
main hub90 window I can not double click into the DS90M.  I get the error 
message "No agent specified for the MAC address - please check log messages 
in the HUBwatch Message Box window".  The Message Box window has the error 
message "snmp:request has no agent defined {slot=2}".

The DS90M is in the agents table and I can manage it from there.  The problem 
is the customer wants to manage all the modules from the main hub window.  Can
this be done?  I read the DR90TS v2.0 release notes and saw the restrictions 
on Decbridges and on Decserver90TLs, 90Ls, & 90L+s, but did not see anything 
about the DS90M.  I think I have the DR90TS configured correctly as I can 
manage a DR90C and a DR90T that are also in that hub.  It is set up with bus 
mastership enabled in a single Dechub 90 configuration and it is the only 
module in that hub set up as an agent.  

Thanks in advance for any help,

Mike (Gamby) Gambardella
T.RTitleUserPersonal
Name		DateLines
3402.1Any reply?PTOJJD::DANZAKPittsburgher �Wed Apr 10 1996 18:054
    (i'm also waiting with bated breath for a reply to this one...any
    takers?)
    
    j
3402.2Not possible ...SNOFS1::KHOOJEANNIESun Apr 14 1996 23:478
    As far as I know, the DS90M is only manageable using its own IP
    address, and similarly with the DS90TL.
    
    If it's in a DEChub 900, you would be able to double click on
    the DECserver without having to go through the Community Manage Table,
    which you have to do with the DEChub 90 or MultiStack.
                                                                        
    Jeannie
3402.3Is This Restriction Documented?SVCVAX::GAMBARDELLAGamby GumbaMon Apr 15 1996 08:348
Re -1 Thanks, I was feeling all alone out here.  That's what I thought but 
the VAR involved in the sale specifically sold a Decserver 90M to give the 
customer the ability to manage the hub from the main window.  Is this 
restriction documented anywhere or was it omitted from the DR90TS release 
notes?  I have a feeling the customer/VAR is not going to like this and I 
would like to be prepared.

Thanks
3402.4DNAS V1.6 different?JULIET::HARRIS_MASales Executive IIMon Apr 15 1996 12:245
    I think the answer to this question is affected after the DNAS V1.6
    code gets released later this year. I think I heard they weer doing
    some significant IP Services work in the servers themselves...
    
    Mark
3402.5DECrepeater 90TS can't manage DECserver 90MNETCAD::RHODESWed Aug 07 1996 15:358
Re: .1 and .3

The DECserver 90TS cannot manage the DECserver 90M.  It was omitted
from the DECserver 90TS' release notes.  As far as manageability, the
DECserver 90M is the same as the DECserver 90TL.

regards,
Ann Marie