[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

3277.0. "90TS managing 90M & non PUBLIC community" by PTOJJD::DANZAK (Pittsburgher �) Wed Feb 14 1996 09:04

    A customer has the following configuration:
    
     - DEChub 90
     - DECrepeater 90TS (latest rev)
     - DECserver 90M (DNAS 1.5)
    
    TO be secure, they set up their community as "secret".  WHen they do
    this they can not manage the 90M via the 90TS.  However if they leave
    the PUBLIC community as in the 90M and read/write, they can manage it.
    If they put the 90M in the 900hub, they have no management problem via
    the "secret" community.
    
    They can select the 90M with the SECRET community and manage it stand
    alone.
    
    THey have entered the 90M in the agent table with the IP address etc.,
    
    Any thoughts on what could be wrong?  Is this a bug?
    
    Thanks,
    j
    
    p.s. can the 90TS manage the 90M?? duuh????
T.RTitleUserPersonal
Name		DateLines
3277.1it should worksULYSSE::YLOUPC::LOUISWed Feb 14 1996 10:389
hello Jon,

There is no reason to disrupt the access to the 90M when
using a different community on the agent, even if the agent
is a 90TS (v2.0).
The setup you described works fine.
The DECserver90M use its own IP address and community.
it's realy strange...