| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1531.1 | The slot table knows all | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Oct 05 1994 18:00 | 6 |
| HUBwatch learns the positions of devices in the hub by querying the DECagent for
information from a data structure which is indexed by slot called the slot
table. Each entry in the slot table contains a great deal of information about
the device in that slot, including some form of identification of the device.
...Roger...
|
| 1531.2 | How is this index populated? | CUJO::HILL | Dan Hill-NetConsultant-Denver-553-3624 | Wed Oct 05 1994 18:29 | 8 |
| Hi, Roger,
I know the index can be populated by polling or by manual entry. What
is the mechanism by which a DECagent 90 (not in the hub) determines
slot position when I move a module from (for example) slot 1 to slot 3?
Thanks,
Dan
|
| 1531.3 | In-band to out-of-band and back to in-band | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Oct 05 1994 19:01 | 13 |
| There is a serial management channel in the hub backplane over which the
DECagent "speaks" a management protocol known as Left Hitchcock. This protocol
allows the DECagent to request "WhoAreYou" information from each slot. Devices
which support the protocol respond with identification information, including
which slot they are in.
In a hub which does not contain a DECagent, you need to have a DECbridge
90/90FL. This device also "speaks" Left Hitchcock and can convey the slot
information to a DECagent upon request. In this scenario, the bridge is the hub
master and the DECagent uses RBMS to request the slot information from the
bridge.
...Roger...
|
| 1531.4 | A bit more info, please. | CUJO::HILL | Dan Hill-NetConsultant-Denver-553-3624 | Tue Oct 11 1994 11:36 | 15 |
| Hi, Roger,
I understand what you are saying. Thanks very much.
This is how I can use a DECagent 90 _standalone_ to manage multiple
DEChub 90s with a DECbridge 90 in each hub. What are the
limitations of using the DECbridge 90 to manage repeaters in the
same hub as opposed to using a DECagent 90?
Sorry to keep asking these questions, but I don't have
standalone DECagent to try this.
Thanks,
Dan
|
| 1531.5 | What you can manage is exactly the same (it's just done differently) | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Oct 11 1994 12:23 | 8 |
| There aren't any limitations when using a DECbridge in the hub as the device
which manages the repeaters in that hub. Having the DECagent standalone simply
means that you have N+1 communities, where N is the number of hubs with
DECbridges in them and the +1 is the DECagent itself in its own community.
All the things you can do to manage the repeaters if you were doing so with a
DECagent in the hub can be done in a remote hub with a DECbridge.
...Roger...
|