| > 1- Is posible to manage a remote Hub90 from a Decmcc in a configuration
> like this :
>
> MCC -- enet segment -- WR90 -- WR90 -- enet segment -- DEChub 90
> (HUBwatch)
Can the WR90 route IP? If it can, HUBwatch will run in the
setup you've diagrammed.
If it can't, you could try running HUBwatch on the remote LAN while
displaying the front panel locally (remote x display: lotsa traffic,
but it would probably work).
>
> 2- Can I view the front panel of the remote Hub with HUBwatch-am ?
>
Remote management of DEChub 90's can be accomplished with the DECagent 90
(hardware) and the HUBwatch Application (not Hubwatch-am). The HUBwatch
Application will "launch" from MCC or MSU.
Since the DECagent 90 "speaks" SNMP (over UDP/IP), MSU or MCC's SNMP AM
could also be used to manage the Hub. No pretty GUI, though...
>
> 3- Is possible to manage a Hub90 when the DECagent is in other segment
> of an extended LAN (i.e. link with a LANbridge, for example)?
>
Yes. DECagent talks to DECbridge 90 (and thus Repeaters as well) using
ELMS protocol. DECagent talks to TermServers using MOP RC. As long as
these LAN specific protocols are not filtered, you should be able to
have the DECagent on a different segment .
Chris
|