T.R | Title | User | Personal Name | Date | Lines |
---|
2414.1 | oui | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Thu Jun 22 1995 14:09 | 1 |
| yes
|
2414.2 | | BANZAY::DEQUAL | | Thu Jun 22 1995 14:27 | 1 |
| OK merci
|
2414.3 | Only repeaters | NETCAD::FORINO | | Thu Jun 22 1995 14:39 | 5 |
| Be a bit careful here. Remember that the DETMI (90TS) and DEFMI (90FS)
can act as agents only for other repeaters. If you have other types
of devices in your hub the DETMI and DEFMI are not DECagent 90
replacements.
John
|
2414.4 | Hub master limited ?? | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Fri Jun 23 1995 05:48 | 8 |
|
>>>If you have other types of devices in your hub
John,
should you little more precise , do you think about Terminal Server L and L+
jean-yves
|
2414.5 | | SLINK::HOOD | Maine State Bird: The black fly | Fri Jun 23 1995 11:04 | 3 |
| Stacks are repeaters only.
Not John, but I play him on TV
|
2414.6 | CNN on LKG | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Fri Jun 23 1995 11:39 | 8 |
|
Which program on TV ??
OK for Stacks but for Dechub90 ??
jean-yves
|
2414.7 | So we don't give the wrong impression ... | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Jun 23 1995 14:06 | 8 |
| Yes, the 90TS and 90FS will be able to manage repeaters in the DEChub 90, but
only the repeaters. The point here is that for those people who have DEChub 90s
with repeaters AND other devices like DECbridge 90/90FL and DECserver 90L/L+,
they can't just yank the DECagent and put in a 90TS/90FS and expect the same
management capabilities. They will still need the DECagent somewhere on the
same LAN to manage those devices.
...Roger...
|
2414.8 | oubli | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Fri Jun 23 1995 14:23 | 2 |
|
Forget mop and RBMS code ??
|
2414.9 | Another example of a device doing things beyond it's originally intended design | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Jun 23 1995 14:45 | 7 |
| If by that statement you are asking if RBMS and MOP management were accidentally
omitted from the 90TS/90FS, the answer is no, they were left out on purpose (or
more precisely they were never designed in). These devices were never intended
to completely replace the DECagent 90. After all, they're REPEATERS, not
multi-protocol management AGENTS!
...Roger...
|
2414.10 | Hum... it's reality just a technical point of view... | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Fri Jun 23 1995 15:26 | 4 |
|
Beautiful response Roger...
Jean-Yves
|
2414.11 | The rules for 90 management?? | PTOJJD::DANZAK | Pittsburgher � | Wed Jun 28 1995 09:32 | 40 |
| So, if I can sum this all up - (and note that SOMEHTING like this
should appear in the CUSTOMER guides!!!!) - anybody care to audit this
for errors:
1.) A DECagent 90 may manage up to 64 devices and 16 hubs in the
LAN - note that this does not typically pass beyond a router.
Elsewhere in the LAN may be located stand-alone or in a DEChub 90.
2.) In order to manage a DEChub 90 you must have a DECbridge 90 or
DECagent 90 in the hub itself to provide management services.
When using a DECbridge 90 only in the hub for management services
a DECagent 90 must be present elsewhere in the LAN to assist the
DECbridge 90 with management services. Note that a DECbridge 90 and
DECagent 90 may be co-located in the same hub if convenient.
3.) A DEChub 90 with populated with only DECrepeaters may be managed
by a DECrepeater 90TS or DECrepeater 90FS running firmware version
(x.x) or greater. The "TS" and "FS" series of repeaters can
provide management services for other repeaters - but not other
non-repeater hub modules. To manage a hub with non-repeater
modules rule 2 still applies in spite of the capabilities of the
DECrepeater 90TS and DECrepeater 90FS.
4.) The only DEChub 90 modules which may be managed stand alone are
the DECrepeater 90TS, DECrepeater 90FS, DECagent 90. A DECbridge
90 may be managed stand alone when a DECagent 90 is present in the
LAN. (????did I miss any othersi.e. decbrouter? etc.?)
Digital advantages to this approach:
1.) Utilizing a DECbridge provides both management and traffic
isolation - management in the DEChub 90 is not a pure overhead
function.
2.) The DECagent 90 manages multiple hubs, offering a savings in
cost of management modules.
ttfn
j
|
2414.12 | | SLINK::HOOD | Maine State Bird: The black fly | Wed Jun 28 1995 10:49 | 8 |
| > 4.) The only DEChub 90 modules which may be managed stand alone are
> the DECrepeater 90TS, DECrepeater 90FS, DECagent 90. A DECbridge
> 90 may be managed stand alone when a DECagent 90 is present in the
> LAN. (????did I miss any othersi.e. decbrouter? etc.?)
The DECbrouter 90's, DECserver 90TL, and DECserver 90M are all self-managed
modules. They have their own built-in SNMP agent, and the only thing the
DECagent 90 does is recognition of these modules in a hub.
|
2414.13 | See CONFIG.TXT | NAC::FORREST | | Thu Jun 29 1995 12:20 | 5 |
| Also see CONFIG.TXT or HUBWATCH.TXT (includes CONFIG.TXT) in the
public directory - NAC::NIPG:[MANAGE]
for more manageability rules.
|
2414.14 | What? Makes a hub unmanaged? | PTOJJD::DANZAK | Pittsburgher � | Mon Jul 03 1995 10:03 | 5 |
| So if I buy a new 16 port module and have managed hubs today with a
bridge in each hub and an agent in the lan, my hub becomes unmanaged?
What an upgrade!? (aarugh)
j
|
2414.15 | Firmware rev. for 90TS | DRAC::LEFERNANDEZ | LUIS ELOY FERNANDEZ | Mon Jul 31 1995 07:47 | 12 |
|
Hi,
what is the minimum firmware revision for the 90TS to act as bus
master on a DEChub 90 ?
Thanks,
Luis Eloy Fernandez
DECsite Barcelona (SPAIN)
|