| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 665.1 | Server must have an IP address | LEVERS::SWEET | | Wed Jan 26 1994 12:47 | 5 |
| The server must have its own IP address for its agent to be managed.
You have not missed anything.
Bruce
|
| 665.2 | Management via the hub is optional | QUIVER::SLAWRENCE | | Thu Jan 27 1994 09:01 | 21 |
|
.1 sums it up in this case, but I thought a little background might be
of interest...
A hub module communicates with the Management module over the backplane
serial management channel. There are a number of things that can
happen over that channel; one of them is that the device may allow
access to all of its SNMP MIBs (as opposed to a small required subset
that the hub uses to identify the device). If the device supports this
access, then the IP address of the Hub can be used to manage the device
using the community string for the slot (which is the community string
for the hub with '-N' appended, where N is the slot number).
Most new modules will support this access so that the number of
required IP addresses for the hub can be kept to a minimum. This is
one of the things to watch for when you read new hub module
announcements and you should let product managers know how important
(or unimportant) you believe this feature to be.
The DECservers do not support management through the hubs IP address.
Feedback on that is best sent to product management for the DECservers.
|
| 665.3 | More management questions | ARRODS::HAWESJ | John Hawes | Thu Jan 27 1994 11:37 | 45 |
| Thanks for the replies,
Summing up reply .2
"The IP address of the Hub can be used to manage a
device using the community string for the slot (which is
the community string for the hub with '-N' appended,
where N is the slot number). However the DECservers do
not support management through the hubs IP address. "
___________ __________________________
| | | DEChub 900 |
| HUBwatch | SLIP | |
| |---------------|OBM |
| | |16.14.2.2 |
|16.14.2.1 | | |
___________ __________________________
DEChub 900 with DECserver 900TM
(16.14.2.3) and two DECrepeater 900TM's
Therefore in the above configuration only the remote
DECrepeater 900TM's would be manageable.
OK I understand now.
The customer will be using the OBM SLIP port as a backup
method of managing the hubs, in the event of the
management station's network connection going down.
It would be inconvenient if the DECservers were not
manageable via the OBM port, but not a show stopper.
However it could be a big problem if the new DECrepeater
900FP, DECbridge 900MX and DECconcentrator 900MX modules
were not manageable via the OBM port.
Does anyone have a list of which modules support
management via the DEChub's IP address, including the
new modules above.
Thanks
John
|
| 665.4 | | QUIVER::SLAWRENCE | | Thu Jan 27 1994 13:04 | 10 |
|
Your analysis is correct; the big difference is that a module that
cannot be managed via the hub cannot be managed via the hubs OBM
connection when the net is down. Exactly why we created the feature.
All the xxx 900 modules (including those mentioned in -.1) _except_ the
DECservers support management via the hub. For management of 90
modules through the hub, see 519.0
|