| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 96.1 | Agent cannot manage across a router | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Tue Dec 08 1992 20:44 | 5 |
| NO. The agent only translates RBMS and MOP into SNMP. RBMS and MOP
are non-routable protocols and thus the agent will only manage hubs on
the SAME LAN. Print out EMDS::MANAGEMENT:HOW_AGENT_WORKS.PS to see a
picture of this.
|
| 96.2 | Bridgeing would work - another perspective | GUCCI::DMCCLOUD | Dennis McCloud - SOA ANC | Wed Dec 09 1992 10:46 | 15 |
| Since the DECnis supports bridging then you can pass RBMS and MOP
between the DECagent and the remote network. If the configuration is
slightly changed to have devices at either end which can bridge
RBMS and MOP then the answer is yes. The WANrouter 90 won't do this
but when a module which fits in the DEChub that supports bridging
and routing (unannounced product) then you could setup a bridged link.
Change the WANrouter at the remote site with a DECnis 500 and you can
bridge the too sites. Another possible configuration would be to
replace the DECnis with another brouter and you can bridge the two
sites.
One kicker for linking brouter to DECnis will be compatability with
the link level protocols on the DECnis which today only bridges across
a high-speed WANcontroller 622 and DEC HDLC. Future link level protocols
will at least give you a shot on connecting the two sites together.
|
| 96.3 | Remote DECagents? | MSAM00::RAJEEVSUNDER | Huber Bach...The Best! | Tue Dec 15 1992 08:35 | 10 |
| You could put an agent at each remote site. Right?
Also, I don't know how much polling the agent does, but I also wonder
if it would take up much bandwidth in an extended LAN.
Anyone know how much polling the agent does?
rajiv
|
| 96.4 | Agent Polling interval | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Wed Dec 16 1992 17:41 | 3 |
| all I know is it polls every 20 seconds (fixed) and proxying does
generate some traffic. Terminal servers are the worst.
|
| 96.5 | DISCO fix it? | GLDOA::MORRISON | Dave | Thu Jan 14 1993 14:21 | 6 |
| Would a WANbrouter 90 tied back to a NIS routing port fix this? I
understand that at least the repeaters (90T, 90C) can be managed
through it if one uses TCP and SNMP as it's service. Is the WANbrouter
90 also manageable from the central site via HUBwatch, aswell as the
repeaters? Are we still looking at end of Q3 to get ship on the DISCO?
Thanks.
|
| 96.6 | brouter manageable anywhere on WAN | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Sun Jan 17 1993 21:04 | 5 |
| Brouter is manageable anywhere on WAN because it has its own SNMP
agent and SNMP is a routable protocol. I expect DISCO shipment to in
Q4, but that is based on gut and nothing official. Check EMDS::ALLEN
for the official word.
|
| 96.7 | DISCO ship date | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Tue Jan 19 1993 10:21 | 36 |
| From: EMDS::ALLEN "STEVE ALLEN - HUB PRD MKTING - 223-3951" 18-JAN-1993 09:40:34.45
To: EMDS::SEAVER
CC:
Subj: RE: Do you have ship date for brouter 96.5
Bill,
currently we are targeted an announcement at Interop 93 with availability
by or before the end of March 93.
Steve
From: EMDS::SEAVER "LENAC Net Mgnt Mktg 223-4573 17-Jan-1993 2104" 17-JAN-1993 21:05:01.69
To: allen
CC: SEAVER
Subj: Do you have ship date for brouter 96.5
<<< EMDS::$1$DUA24:[NOTES$LIBRARY]HUB_MGNT.NOTE;1 >>>
-< Hub Management Conference >-
================================================================================
Note 96.5 Remote management with one DECagent 5 of 6
GLDOA::MORRISON "Dave" 6 lines 14-JAN-1993 14:21
-< DISCO fix it? >-
--------------------------------------------------------------------------------
Would a WANbrouter 90 tied back to a NIS routing port fix this? I
understand that at least the repeaters (90T, 90C) can be managed
through it if one uses TCP and SNMP as it's service. Is the WANbrouter
90 also manageable from the central site via HUBwatch, aswell as the
repeaters? Are we still looking at end of Q3 to get ship on the DISCO?
Thanks.
|