| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1083.1 | Try Setting IP Addr. for IPS Module | NACAD2::DRAGON | | Wed Jun 08 1994 09:20 | 12 |
|
Andrew,
I'm assuming here that you are using your DECrepeater 900TM as the
IP Services module. If so, try setting the DECrepeater 900TM's
In-Band IP address as well as the In-band IP address for the MAM
(different IP addresses). I recall running into a problem in which
traps would not be delivered from the MAM unless you gave the
900TM IP Services module an IP address.
Hope this helps,
Bob
|
| 1083.2 | | TKTVFS::NEMOTO | no facts, only interpretations | Thu Jun 09 1994 11:44 | 10 |
|
Isn't the IP Services capable of delivering traps for each module in a HUB900
box?
We have a customer network which includes more than 100 DEChub900s. Remaining
IP address space that has been reserved for network management purpose can be
eaten up quickly in a middle if you start giving IP address to each module..
Thanks,
_Tak
|
| 1083.3 | RMON A&E might help. | NACAD::GALLAGHER | | Fri Jun 10 1994 11:15 | 22 |
| >Isn't the IP Services capable of delivering traps for each module in a HUB900
>box?
Nope. IP Services is capable of delivering IP messages to the Management
Agent Module (MAM). Traps, don't come into the hub.
We do, however, have a backplane protocol which we could use to have modules
send traps to the MAM. We don't currently do this. One of the reasons we
don't do this is architectural. Small solace.
>We have a customer network which includes more than 100 DEChub900s. Remaining
>IP address space that has been reserved for network management purpose can be
>eaten up quickly in a middle if you start giving IP address to each module..
Future versions of the MAM will have RMON Alarm and Event support. Using
RMON A&E the MAM can, among other things, send traps when line cards are
inserted, removed, fail, and restarted. Using RMON A&E you can get traps
on these events without having to give each module an IP address.
I don't have a schedule for when RMON A&E will be released.
-Shawn
|
| 1083.4 | | NACAD::SLAWRENCE | | Mon Jun 13 1994 11:22 | 4 |
| You don't need to give the IP Services module an address of its own,
nor do you need to give one to any module that can be managed through
the hub, BUT you do need to set the Default Gateway Address in the IP
services module.
|
| 1083.5 | | NACAD::WILSON | | Mon Jun 13 1994 13:05 | 25 |
| Re: 1083.0
Andrew,
I think the reason you are not seeing traps from the DEChub 900 manager
is that is does not support the same set of traps that the DECagent 90
supports.
The DECagent 90 supports enterprise specific traps which include traps
that tell you a module has been pulled/inserted, a port has been
enabled/disabled, etc.
The DEChub 900 manager, at the moment, only supports the generic traps
(ie. LinkUp, LinkDown, ColdStart, AuthenFailure).
The documentation or release notes (I don't remember which) states
that you will not receive a trap from a module unless it has it's own
IP address. The management agent for the DEChub 900 does not forward
traps or generate traps for modules which don't have an IP address.
If you followed the same steps in setting up traps for your DEChub 900
that you did for your DECagent 90, you should receive any traps that
are sent. The problem may be that traps just aren't being sent.
Karen
|