| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 55.1 | management of remote DEChubs | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Sat Aug 22 1992 19:32 | 18 |
| WANrouter 90- you're dealing with unannounced stuff...
HUBwatch uses SNMP. SNMP is a routable protocol and will manage remote
sites.
the SNMP Am will coexist with HUBwatch and it looks like HUBwatch can
easily run on the ULTRIX version of MCC. Any SNMP manager will coexist
with HUBwatch.
You need a DECagent and a DECbridge for each of the remote sites to
manage repeaters there. Only a DECagent is needed if you are not
planning to manage repeaters. If the remote sties are on the same LAN
(does not sound like this) 4 DEChub 90s can be managed by one agent.
Stand alone device limit is 63 devices. See
EMDS::MANAGEMENT:MSU_SALES_UPDATE.TXT for more information. The new
WANbrouter for the DEChub will be able to take the place of the agent
and the bridge for repeaters. The 90TL has its own agent and does not
need the DECagent (or bridge) once it supports SNMP SETs.
|
| 55.2 | WANbrouter 90 wil replace DECagent? | ISKATE::BILLD | | Mon Aug 24 1992 13:01 | 42 |
|
You stated that can manage the remote locations with HUBwatch at the
central WAN location since it uses SNMP. Since SNMP is a service under TCP/IP
and not DECnet, I will have to run TCP/IP over my WAN for remote management of
the remote routers. I was designing DECnet into the WAN for alternate pathing and
load balancing. I have no problem running TCP/IP and DECnet over the WAN if
TCP/IP is used primarily for WAN management. With a already configured
DEC WANrouter 500 and DEC WANrouter 250, TCP/IP should be no problem. I have
proposed the PC based HUBwatch for this central site along with the DECagent and
DECbridge in a local DEChub.
Now for the remote sites. I had proposed putting a DEC WANrouter 90 at
each of these remote sites and manage these from the central site. And from the
verbiage in the above paragraph, this ocnfiguration should work fine.
As for the management of the remote DEChub based DECrepeater 90 Ts and
Cs and DECserver 90TLs BY THOSE REMOTE SITES, it appears that I will require a
DECbridge 90 and DECagent along with HUBwatch - If I want to propose HUBwatch
throughout this project. From what you said, can I replace the DEC WANrouter 90
with another unrealeased product, the DEC WANbrouter 90, and be able to aleviate
the need for both the DECbridge and DECagent at each remote site? = save $$$$$.
You need to understand, ultimately we could have in excess of 70 of
these remote sites. We have only so much money for the overall project and if
we can design in some savings per remote site, then we can save the overall
project a good bit of cach.
Assuming that I was to Configure the WAN with the DEC WANbrouters instead
of the DEC WANrouters and...
....if the central site was to purchase the remote routers for
each of these remote sites, then each remote site would purchase their own LAN
equipment along with the PC based version of HUBwatch to manage the local
DECrepeaters and DECservers, I would have a good co-management environment.
Do you agree...?
Regards,
Bill
|
| 55.3 | a choice of solutions | MEMIT::FORREST | | Mon Aug 24 1992 17:23 | 10 |
| Per my understanding of DEC WANbrouter 90 (cisco firmware) capability, it
will be able to manage the repeaters in the same hub, so you would not need
the DECagent 90 unless you want to manage DECbridge 90s or DECserver 90L+s
on that remote LAN.
We are also planning a firmware upgrade to the DECagent 90 to manage
repeaters in the same hub as the DECagent 90, without the need for the
DECbridge 90.
jack
|
| 55.4 | Is Agent needed to manage WANbrouter 90? | GLDOA::MORRISON | Dave | Thu Jan 14 1993 13:53 | 6 |
| To close the loop - can I also manage the WANbrouter 90 in remote sites
by connecting to a i.e., NIS 600 routed lines (I will have 60 brouters
in remote and do NOT need to bridge between them - only route TCP), and
in turn have the NIS connected to the same enet as a HUBwatch PC or
Ultrix station, thus having only a 90T repeater and WAnbrouter 90 in
the remote sites tied together with thinwire?
|
| 55.5 | Agent not need to manage brouter | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Sun Jan 17 1993 20:56 | 5 |
| The brouter has an integral SNMP agent, so no DECagent is needed to
manage it. It can be managed anywhere on a WAN as SNMP is a routable
protocol. The brouter will also be able to proxy for 90Ts in the same
hub. To have the thinwire connection you need a new repeater with its
own integral SNMP agent. I hope to have one by this fall.
|
| 55.6 | Managing remote 90Ts with no hub? | TROFS::WEBSTER | I joined AA...Acronyms Anonymous | Thu Feb 11 1993 16:04 | 13 |
|
What about management of remote repeaters (90Ts) that are not
installed in DEChubs?
If a WANbrouter 90 or DECagent 90 (Vx.x)/DEMSB combination is
used, will the modules be manageable?
We are working on a proposal to install DECrepeater 90Ts at 58
locations, 46 which will have hubs. 12 sites will need management in non-hub
configs.
-Larry Webster
|
| 55.7 | From the DECagent 90's perspective... | KALI::GAUDET | | Fri Feb 12 1993 13:55 | 6 |
| Repeaters (e.g. 90T) that are not installed in a hub are not
manageable. And those that are in a hub need a bridge in the same hub.
I can't speak for the DECbrouter 90.
...Roger...
|
| 55.8 | Repeaters can be managed by Brouter | EMDS::SEAVER | Bill Seaver, HUBwatch Mktg | Fri Feb 26 1993 10:56 | 9 |
| 90T repeaters in a hub with a DECbrouter 90 will be managable without
bridge or agent.
Futures: Next version of DECagent 90 (summer 93) will not need an
bridge to manage repeaters. Also, in late 93 we expect to comeout with
a new 8 port repeater that has a native agent and thus does not need a
hub or anything else to be manageable. I would appreaciate any
comments peope may have on either of these options--EG would you really
sell them?
|