| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 498.1 | Slot Number for In Band Management | QUIVER::SLAWRENCE | | Tue Nov 16 1993 09:04 | 21 |
| The agent module does not have any connection of its own to the
backplane LANs; in order to receive IP from the networks (as opposed to
its own OBM port), it needs a module that can recieve them and forward
them over the serial management channel. This module function is
called 'IP Services'.
The configuration question you were asked when configuring the In-Band
address was 'Which module will perform the IP Services function for the
hub manager?'.
At present, the only shipping module that has that function implemented
is the DECrepeater900TM (DETMM). Most modules that we ship from now on
will support this feature, so the configuration restriction will get
less cumbersome.
You can manage the hub without an IP Services module by using the OBM
port; you can either connect your NMS to it directly, or you can use a
terminal server as a SLIP router. I'll post the configuration commands
for the DECserver 90TL, 90M, and 900TM in another note (so the title
will be more visible).
|
| 498.2 | Thanks | GUCCI::DMCCLOUD | Dennis McCloud - Eastern Client/Server Consultant | Tue Nov 16 1993 11:26 | 1 |
|
|
| 498.3 | SIMPLE MANAGEMENT of COMPLICATED HUB | BACHUS::VANDENBERGHE | | Fri Nov 26 1993 12:56 | 26 |
| Can we find somewhere on the network a detailed description of how
a DECHUB900 is managed.
Marketing doc is very confused about it so I can imagine that there is
something tricky.
Questions out of my mind:
What is exactelly the In-band management support, how does it work on
the DECHUB900?
What is the role of the HUB manager and the SNMP Agent in the different
modules, is there a master?
How do we manage such a hub if a DEChub Agent 90 is connecetd to it?
How will it be managed if on top of that we place a Token-Ring Agent.
Will we have to run 3 Hubwatch sessions to see the whole stuff?
What about the management of a HUB using a generic SNMP manager such as
DECmcc and the MIB access to all those Agents?
How many IP addresses will it requires.
Can we use the Agent/Manager/IP service/ of a DECHUB900 to Manage
standalone Modules.
If somebody wants to reply on this ... thanks in advance
Robert
|
| 498.4 | | QUIVER::SLAWRENCE | | Mon Nov 29 1993 09:58 | 48 |
| > What is exactelly the In-band management support, how does it work on
> the DECHUB900?
In-band management refers to exchanging SNMP messages over the network
interface of some module plugged into the hub (as opposed to via the
hub managers own OBM port). See .1
> What is the role of the HUB manager and the SNMP Agent in the different
> modules, is there a master?
Some modules have built-in agents; those modules will accept management
commands from the hub management module as though they were coming from
an NMS with the read-write community string, but the hub manager only
sets objects used for internal management of hub functions (not visible
to an NMS).
> How do we manage such a hub if a DEChub Agent 90 is connecetd to it?
If you configure an IP address for the Hub Manager, then it will not
allow a DEChub90 module to manage the hub (send management commands to
other modules). If you don't give the Hub manager its own address,
then it operates in '90 mode' for backward compatibility and will allow
a bridge (or V2.0 DENMA, when it comes out) to manage the hub.
The DENMA can be in a hub without managing it, and in fact if you are
using a 900 as the backbone for a number of 90 hubs then putting the
DENMA in the 900 is a good idea (if you put it in one of the 90s and
the bridge in that 90 dies you loose management of all the others).
> How will it be managed if on top of that we place a Token-Ring Agent.
There is no Token-Ring Agent (cancelled; some of its management
capability will be in the DTMAX).
> What about the management of a HUB using a generic SNMP manager...?
The DEChub900 MIBs are compilable by all the compilers we've tried; we
would like to hear about any problems you encounter so that we can fix
them...
> Can we use the Agent/Manager/IP service/ of a DECHUB900 to Manage
> standalone Modules.
If the module has its own agent then you don't need it; if not the hub
manager is no help...
|