[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

380.0. "help in a LAN-WAN configuration" by ROM01::CENCI (nec metus nec spes) Tue Sep 07 1993 06:44

    Hello,
    I'll have to face competition at a prospect customer. 
    I haven't got a thorough knowledge of our hub products offering;
    your help is thus welcome.
    
    The customer wants to install 8 Ethernet LANs; all the LANs are remote 
    to one another as they are located in different cities.
    
    On every Ethernet there will be few SCO-UNIX PCs. Internet protocols
    will be used to transfer files, emulate terminals, etc.
    
    Every LAN will be connected via 2 leased lines to 2 remote LANs via 
    TCP/IP, in a ring-like configuration (for redundancy).
    
    They'll have to do basic network management (from an help desk on one
    of the LANs), for example, they'll need to check if a remote router is 
    working well, and take appropriate action should any router fail (the
    help desk operator could open a call).
    
    Winning the bid of course implies our being able to keep costs low.
    
    What do you suggest? The problem I have to face is that they don't
    want to buy load hosts at each site, and keep on using their PCs.
    
    If I offered them a DEChub 90, with 2 DECwanrouter 90s per site (they need
    two WAN ports as I said before), and a DECserver 90M per site with a
    FLASH memory for the UNIX PCs, I would still need 8 load hosts for the 
    routers. Am I wrong?
    
    
    And what about a simple and cheap network management solution for 
    such a limited network? They want a centralized workstation to set
    up an help desk, so that an operator gets a warning when a router's
    state change.
    
    
    Thanks a lot for any suggested configuration.
    
    
    Fabio
    
    
    
T.RTitleUserPersonal
Name
DateLines
380.1TMAWKO::PRESSLEYpin heads are people too...Thu Sep 09 1993 17:194
Use the decbrouter 90.  It does not require a download and comes with two WAN
ports.

Use hubwatch for the pc for network management of the hub products.
380.2ROM01::CENCInec metus nec spesFri Sep 10 1993 05:5916
    Thanks. Would you please tell me what the advantages of using Hubwatch
    for Windows are in controlling local and remote routers?
    If I am not wrong, the DECbrouter 90s support SNMP and can be kept
    under control simply by connecting via TELNET to the router's console.
    
    The HUBwatch gives you a graphical interface, but does it require
    some skills to check whether a line or a router are experiencing faults
    of any sort?
    
    And... do you need DECagent 90 as well (how many cards for 8 hubs?)
    
    
    Thanks for your help
    
    
    Fabio
380.3Telnet, HUBwatch, and DECagent needsNAC::FORRESTFri Oct 29 1993 09:1715
	HUBwatch for Windows does not currently support Telnet. You would 
	probably have to use another package to get Telnet and reboot the 
	PC each time you wanted to switch.

	It does require some skills to troubleshoot the fault. If you add 
	the DECbrouter to the HUBwatch map, then it will turn red if you 
	lose connectivity to it. But if one path to it is still active, 
	then the icon will remain green. I'm not sure if the DECbrouter 
	will send a link down trap, but that could help too.

	You need 1 DECagent 90 per 8 single (non-daisy-chained) hubs, 
	assuming they are all on the same LAN. I would recommend 1 
	DECagent per remote site, unless there are more than 8 hubs 
	at the site.