[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

2665.0. "Aaargh! 90TS Management Qs" by SNOFS1::KHOOJEANNIE () Wed Aug 23 1995 04:57

    Hi all,
    
    We have pretty much the same situation as that described in Note 2157 -
    a customer has implemented a network with 8 pairs of DEChub 90s, with
    each pair populated with a DECbridge90FL and lots of DECrepeater 90TSs
    (80 DECrepeater 90TSs altogether).  There will be 2 DECagents in
    addition.
    
    This is a management nightmare - it appears that the customer will need
    80+ IP addresses for management, and worse still, cannot view the
    DEChub 90s in their entirety.
    
    
    As I understand it, if he installed a DECagent in each pair of DEChub
    90s then he would be able to view the entire hub, and he could manage
    each repeater by clicking on it, but 80+ IP addresses would still be
    needed.  Is this correct? 
    
    
    Is there a glimmer of hope with the imminent firmware upgrade?
    
    i.e. When the DECrepeater 90TS firmware upgrade is released (and it
    can manage other DECrptrs), does this mean that
    
    - the DECrptr 90TS will understand LH
    
    - one DECrptr 90TS will be able to manage the other DECrptr 90TSs in the
      hub using LH - i.e. only 1 IP address will be needed per pair of
      DEChub 90s?
                              
    Answers and any comments will be very much appreciated,
    Jeannie
T.RTitleUserPersonal
Name		DateLines
2665.1NETCAD::DRAGONWed Aug 23 1995 10:5514
    
    Jeannie,
    
    	The DECrepeater 90TS will be able to manage other DECrepeater 90TS
        and DECrepeater 90FS modules as a proxy agent. This means that
        they will not have to have an IP address of their own. However, the
        DECrepeater 90TS or DECrepeater 90FS as a proxy agent will not
        provide full MIB support. In order to get full MIB support of the
        module, it will have to have its own IP address and be managed
        direct. Features which will not be available via proxy are security, 
        dual port redundancy, and performance (speedo dials).
    
    Regards,
    Bob
2665.2only a repeater managerPRSSOS::PEYRACHEJean-Yves Peyrache Country Support Group FranceWed Aug 23 1995 13:346
 Be careful.

 as far as known, 90TS/FS can't manage DECbridge90

 JYP
2665.3Another 90TS Mgt. queryBRIEIS::BARKER_EEighteen days and counting ...Thu Aug 24 1995 04:5122
    Hi,
    
    	I've got a similar query. We have three DEChub 90's, one has a
    DECagent 90, set up to manage the other hubs.  One of the other hubs
    has a DECbridge 90FL to act as the bus master, in slot 8, a DECserver
    90M in slot 7 and a DECrepeater 90TS in slot 6.  The DECrepeater 90TS
    can be managed standalone via it's own IP address with no problems but
    when the DEChub 90 community that it's in is selected via the DECagent
    I get a blank module in slot 6 that says DECrepeater 90TS with no more
    details, and I can't manage it.  The Message log shows slot 6 with a
    question mark. I have made sure the MAC address of the DECrepeater 90TS
    is entered in the hw_agent.dat file.
    
    	The hub that has the DECagent in has also got DECrepeater 90TS's
    and they can be managed perfectly OK.  Is this situation a reflection
    of the general recommendations now being made to put a DECagent in most
    hub 90's ?
    
    	Any ideas ?
    
    
    	Euan
2665.4NewSWAM2::JACOMB_SCI know enough to be dangerous!!Mon Aug 28 1995 19:013
    Have you looked at the stackables?
    
    	-Scott
2665.5Several ChoicesNETCAD::DRAGONTue Aug 29 1995 09:5026
    RE:3
    
    Euan,
    
    	It is my understanding that DECrepeater 90TS and 90FS in a remote
        DEChub 90 (with DECbridge 90/90FL being managed by a remote DENMA) 
        are only manageable by HUBwatch directly via their own IP address.
    
        When a DECrepeater 90TS and 90FS is present in a non-remote DEChub
        90 (DEChub 90 with DENMA present), HUBwatch actually manages the
        module directly, using IP address information provided by the
        DENMA. This mechanism does not work in the remote DEChub 90s, so
        that it is necessary for the user to manually provide the repeater's 
        IP address to HUBwatch rather than a point and click on the DEChub 90 
        Front Panel Window. Clearly this is not the most desireable behavior. 
        To correct this the user could add a DENMA to the remote DEChub 90, 
        But, this will use up a slot and costs more money.
    
        As was pointed out in .4, the stackables may offer a solution to
        the remote hub problem in some cases in that a repeater which can 
        manage the "previously remote hub" may be added rather than a DENMA, 
        thus not using up a slot and being per port cheaper.
    
    Bob