[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

33.0. "Public directory on DEChub 90 management" by --UnknownUser-- () Mon Mar 02 1992 17:55

T.RTitleUserPersonal
Name
DateLines
33.1list of files on public directoryEMDS::SEAVERLENAC Net Mgnt Mktg 223-4573Thu May 28 1992 16:2164
As of 28 May 1992, the following files are on the public directory
EMDS::$1$DUA4:[SMART_HUB90.MANAGEMENT].  This directory is updated frequently.
Please address any questions to Bill Seaver at  EMDS::SEAVER.

FILES

AGENT_DETAIL= Screen on HUBwatch for Windows(TM) used to control the DECagent
	90 (DEMNA).
AGENT_LOAD.TXT= How to load current micro-code on agent
AGENT_MANUAL.PS= Draft DECagent 90 manual- good on out of band port
BRIDGE_LOAD.TXT= How to load new micro-code on bridge
BUYERS_GUIDE.PS = Draft Buyer's Guide article
CABLETRON.TXT= Cabletron's design has throughput problems.
COMPETITON.TXT= How to sell DEChub management against the competition and
	price comparisons.  NOTE= most other hubs have a single point of 
	failure!
DEChub.MIB= ACSII file (long) defining MIB in detail.
DEC.EXE= HUBwatch for Windows demo program.  Read 
	WINDOWS_DEMO_INSTRUCTIONS.TXT for instructions.
HOW_AGENT_WORKS.PS = Diagram of how agent translates protocols.  Most customers
        ask this question.
INTEREST.DIS = DEChub 90 management interest list.  Contact EMDS::SEAVER if you
	want to add names.
MSU_MANUAL.PS= Draft HUBwatch for DECmcc MSU manual- good on screen detail
MSU.SPD= Draft HUBwatch for DECmcc MSU SPD
OCT91_Q_AND_A.TXT = Question and answers sent out for Oct 91 program
	announcement covering the David agreement and and overview of 
	management functionality to be provided.
MORE_Q_AND_A.TXT = detailed questions about repeater screen, alarm thresholds,
	and ASCII input/output, etc.
PID_BACKGROUND.TXT= management section only.
PRESENTATION.PS on management of the DEChub 90.  To be used with customers.
READ_ME.TXT = this file.
* REPEATER_DETAIL= Screen on HUBwatch for Windows used to control the 
	10baseT	repeater (DETMR).
SALES_UPDATE.TXT = PRELIMINARY Sales Update article
STATUS.TXT= mid-month status on development of hub management products
WHAT_CAN_BE_MANAGED_ON_REPEATERS.TXT 
WINDOWS_DEMO_INSTRUCTIONS.TXT= instructions for running HUBwatch for 
	Windows demo.
* WINDOWS_ERROR_SCREEN= Screen of hub with one of each module on it as seen 
	on HUBwatch for Windows.  Screen also shows various error 
	conditions and naming options for ports and modules.
WINDOWS_HELP_SCREENS= Describes fields in the Windows screens.
WINDOWS_MANUAL.PS= Draft HUBwatch for Windows manual
* WINDOWS_REPEATERS= Screen of hub full or 10baseT repeaters as seen 
	with HUBwatch for Windows.  This would be a typical screen for 
	a customer with many PCs connected.
WINDOWS.SPD= Draft HUBwatch for Windows SPD
WISH_LIST.TXT= requests for future enhancements...let me know if you want to
	add to this list.

* These screens are available as color foils.  Send mail to EMDS::SEAVER with
	you mail stop if you want a set.

NOTE ON FILE EXTENSIONS:
BMP= DOS bit map, can be imported into paint package or printed on printer 
      connected to PC (original is in color).
PS = Postscript- I can only get black and white out of this although original 
      BMP files are in color.

NOTE: most screen .PS files can only be mailed by using the SEND/FOREIGN
command.