| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1064.1 | | LEVERS::DRAGON | | Fri Jun 03 1994 10:15 | 20 |
|
Jim,
Once you give the MAM an IP address the DECagent 90 loses its
ability to manage the hub in which it is located. You should
not attempt to manage a hub with both a MAM and a DECagent 90.
In your particular case, I would manage the DEChub 900 via the
MAM. What you could do for demo purposes is to setup the DECagent
90 to manage other remote hubs. These hubs would need to be DEChub
90s or DEChub 900s in 90-style (could also be standalone DECserver
90s and DECbridge 90s). The remote hubs would also need to have a
DECbridge 90 present to be hub master. Note that when a MAM does not
have an IP address set it is in 90-style (operates similiar to a
DEChub 90) and can be managed using a DECagent 90 (90-type modules
present). Once you have 900-type modules you'll need to switch to
900-style (set an IP address on the MAM) in order to manage the
900-type modules.
Hope this helps,
Bob
|
| 1064.2 | Thanks. Another quick question. | EMASS::HEBERTJ | | Fri Jun 03 1994 11:16 | 11 |
|
Bob,
Thanks for your reply. That helps clear things up alot.
ThOne other quick question: Can all 90 and 900 modules be managed
via the hub management or are there certain 90 modules that can
only be managed with the DECagent90 or as standalone? The
documentation isn't real clear about that. Thanks again.
Jim
|
| 1064.3 | It's documented ... somewhere | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Jun 03 1994 11:25 | 9 |
| Actually the documentation is quite clear about this. You're probably looking
at the wrong documentation. :-)
The DEChub 900 Management Agent Module (MAM) can directly manage the 90-style
repeaters (90C, 90T, 90FL, 90FA). The DECagent 90 is required to manage the
DECserver 90L/90L+ and DECbridge 90/90FL, and will directly manage the 90-style
repeaters when it is the hub master (i.e. when the MAM is denied an IP address).
...Roger...
|
| 1064.4 | | LEVERS::DRAGON | | Fri Jun 03 1994 11:36 | 14 |
|
Jim,
You need to have a DECagent 90 in order to manage a DECserver 90L,
DECserver 90L+, DECserver 90L++, DECbridge 90, or DECbridge 90FL.
The DECagent 90 needs to be on the same LAN as the module it is
managing, but does not have to be in the same hub. In this context
the DECagent 90 is managing the module standalone. There's a
section in the HUBwatch Installation and Configuration doc. (Chp 3)
which walks you through what needs to be done to set this up. Its a
bit difficult, but once done you can point and click in HUBwatch and
manage the modules in a straight forward manner.
Bob
|
| 1064.5 | thanks. | EMASS::HEBERTJ | | Fri Jun 03 1994 11:37 | 7 |
|
Roger,
Thanks. I'll check the documentation again. It will probably be
a lot clearer now that I have a better understanding of how the various
modules can be managed.
|
| 1064.6 | When engineers are allowed to write documentation ... | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Jun 03 1994 11:44 | 15 |
| No problem Jim. In fact, the information I was alluding to is conveniently
buried deep within the DECagent 90 release notes.
To quote from the RESTRICTIONS section of those release notes:
>> The DECagent 90 cannot be a hub master in a DEChub 900 backplane until Hub
>> Manager V3.0 is available. The Hub Manager should be used to manage DEChub
>> 90 repeaters in a DEChub 900, or a DECbridge 90 could be used to manage the
>> DEChub 90 repeaters if the Hub Manager is not assigned an IP address. In a
>> DEChub 90, the DECagent 90 can be hub master and fully manage the repeaters.
Not exactly the most in-depth discussion of 90-style versus 900-style management
on the planet, but it does capture the gist of it.
...Roger...
|