| 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 |
A customer purchased a 900 hub with the db900mx as its IP
services module. I have found that port 3 is the only port
that can connect to the internal thinwire and it points out
by default. (note 1059.1)
How can the user connect to the HUB manager to configure the
hub if the only IP services module has its port(s) out by
default ?
The user has a DB90 that connects a thinwire run with the
hubwatch station to the dechub 900.
Larry Morse
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1633.1 | KAOFS::S_HYNDMAN | Acronym Decoder Ring Architect | Fri Oct 28 1994 18:15 | 10 | |
You could connect a thinwire MAU (the new one, not a desta) to one of
the AUI ports on the front pannel of the DECbridge 900 (don't use the
DB90). Give the HUB its ip address from the setup port. Give the
DB900MX its address by choosing the redirect option from the Hub
manager. Now you can access the hub via HUBwatch to point port 3 to
the thinwire channel.
Scott
| |||||
| 1633.2 | NETCAD::ANIL | Mon Oct 31 1994 21:40 | 6 | ||
You do not need to connect anything to the backplane for IP services.
The MAM does NOT communicate with a module via the thinwire or any
other backplane LAN -- it does so via a dedicated serial line
connection to every slot.
Anil
| |||||
| 1633.3 | NETCAD::SLAWRENCE | Wed Nov 02 1994 14:30 | 4 | ||
.-1 is correct so long as the NMS is connected to the db900mx somehow.
.-2 suggests one way to do that (and eliminate the need for db90)
| |||||
| 1633.4 | NETCAD::ANIL | Wed Nov 02 1994 22:18 | 36 | ||
I don't understand the problem..
> .-1 is correct so long as the NMS is connected to the db900mx somehow.
Why would the NMS not have a path to the db900mx (unless they are
using OBM in which case no IP service is needed).. is it because there
are two unconnected networks, one bridged by the DB90 and one by
the DB900? If so, then one definitely should not solve the
connectivity problem by connecting the DB900 thinwire into the hub
backplane since this would overwhelm the DB90's workgroup
side learning capacity. The right way to have them coexist is
to connect them through their external ports.
> .-2 suggests one way to do that (and eliminate the need for db90)
The typical customer would probably not toss a DB90 when they get
a DB900. Even if they did, they wouldn't need to connect the DB900 to
the thinwire backplane for IP services.
I've talked with more than one field person who assumed that modules
talk to the MAM via backplane LANs.. it needs to be clarified that
this is not the case.
The only confusing case is when you bring in the external connection
through a repeater (which by default connects to the thinwire) and
the NMS is connected to the repeater but the repeater is not wired
to the bridge externally (assuming that this is a first-time setup).
Then the NMS can't talk to the bridge which makes it hard for
it to provide IP services. The solution of course is to
connect the repeater to the bridge externally (at least during setup),
or to connect the NMS into the bridge. The latter is good practice
anyway because it's best to have IP services be provided by the closest
possible hub module.. thus reducing the chances of losing management
connectivity due to a module, or LAN path, in between going down.
Anil
| |||||