T.R | Title | User | Personal Name | Date | Lines |
---|
1356.1 | DETMI is managed through its own SNMP agent | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Aug 29 1994 11:18 | 10 |
| Ole...
If by "agent" you mean the DECagent 90, then it is not necessary. The DETMI
has its own internal SNMP agent which you can address directly from HUBwatch.
The DECagent 90 does not manage the DETMI at all. The only thing a DECagent
buys you if you have a DETMI in the same hub is the auto-discovery feature for
displaying the hub view (provided you specify the DECagent from HUBwatch instead
of the DETMI).
...Roger...
|
1356.2 | | BIGUN::WULFF | | Mon Aug 29 1994 21:28 | 11 |
| Re: .1
Thanks for the reply.
I understand that the DETMI has its own SNMP agent, and so do the DEChub900 modules,
but whilst the DEChub900 modules are plugged in the DEChub900 backplane they are
managed by the HUB agent and when using Hubwatch you can get a view of all the modules
in the hub. How would I achieve the same functionality if I was to use a dechub90 that
had DETMI's and DEFMI's installed in the backplane.
Thanks.
|
1356.3 | DECagent 90 has it now! | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Aug 30 1994 15:03 | 12 |
| Ole...
Using HUBwatch V3.0 or higher, you can get the same functionality in the DEChub
90 using a DECagent 90 running V2.1.3 code. Simply insert the 90TS and 90FS
modules into their desired slots, assign each an IP address via their setup port
INSTALLATION MENU, and bring up HUBwatch using the DECagent's IP address. You
can then double click on the 90TS and 90FS from the HUBwatch hub view and
HUBwatch will use the on-board agent to manage the device. It will probably
take 20 seconds or so for the DECagent to "learn" the IP addresses from the 90TS
and 90FS after you assign them, but after that you should be off and running.
...Roger...
|