| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| 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 |
Questions on DEChub 900 installation/configuration:
(1) A DEChub 900MS with only one DECconcentrator 900MX. The front panel
FDDI A/B ports will be used for dual FDDI ring connection.
(2) A DEChub 900MS with 2 x DECbridge 900MX and 2 x DECrepeater 900TM.
A FDDI dual ring is formed by 2 x DECbridge 900MX via front panel A/B
ports, or front-A back-B back-A front-B ports. One Ethernet on ThinWire
or a flexible channel is formed from all four modules.
Is HUBwatch needed to at all install/configure the above environments?
We will ask the customer to buy HUBwatch for other reasons, we want to
know whether it is needed during setup/configuration.
Faraday
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 866.1 | HUBwatch not needed, BUT... | SLINK::HOOD | I'd rather be surfing | Mon Mar 28 1994 13:50 | 23 |
There are two answers to your question:
(1) No, you do not *need* HUBwatch to configure or manage anything in a DEChub,
or to config or manage any DEChub module. Everything is SNMP-manageable,
and if you have a good SNMP tool, you can do it all without HUBwatch. All
the MIBs are publicly available.
(2) Yes, you need HUBwatch. Managing the concentrator, bridge, backplane, et
al, is an awful lot easier if you use the SNMP tool that was developed
specifically to do that job. With HUBwatch, you do not need to understand
the nuances of the MIBs. You do not need to know about side effects. You
don't have to try to guess which variables (groups of variables) do what
you want. You just do the configuration with a tool that's orders of
magnitude easier to use than a generic SNMP browser.
With your configuration, backplane management and port ligo types (to
allow A in front and B in back) is enough of a headache that just using
the MIBs alone would be painful. With HUBwatch, your customer can get that
configuration up within a day. Without it, they'd spend a lot of manpower
reading through MIBs and playing around trying to get what they want.
Tom Hood
HUBwatch
| |||||
| 866.2 | Do not sell a HUB without HUBwatch | ZUR01::SCHNEIDERR | Mon Mar 28 1994 13:51 | 13 | |
For any configuration on the DEChub, you need HUBwatch. It is not recomended to do configurations direct via a MIB-browser. We told to our sales "Do not sell HUB900 without HUBwatch!!!!!!" On the HUB itself, you have only a configuration port, to setup the SNMP agent (address, community, .....). All configuration, like backplane channels creation, you have to do over HUBwatch. You can run the HUB without HUBwatch because all modules are by default connected to the THINWIRE channel. Except FDDI channels of course. Roland | |||||
| 866.3 | UFP::LARUE | Jeff LaRue: U.S. Network Resource Center | Thu Apr 14 1994 18:06 | 10 | |
...but be aware that the current version of Hubwatch does not support
the configuration of the 900MX concentrator. Also both the hub and
the currently shipping 900MXs will need a firmware update inorder to
support the configuring of the backplane A & B ports of the 900MX.
This will be available in hte May '94 timeframe...according to the
letter that is shipping with the 900MXs.
-Jeff
| |||||