| .1 answered your first question.
> How to select another communities than "public" when you want receive
> only the Trap for bunch of 90 modules hooked in Differents Dechub90's ???
> appears that's in Decagent90 for Trap address you can't select the
> community ,but in Snmp Message the field Community is present for trap
> message. any clue ??
The community field in the SNMP message is the TRAP community (not your
read/write or read-only community). For each module you can set a
specific trap community. This means that when a trap is issued the
message will be sent with this community instead of the read/write community.
There is no way to specify a trap community which would only signify
traps from a subset of modules. Especially for the DECagent 90, which sends
traps for the modules. You wouldn't be able to say for slots 1,3,5 use
trap community xyz and for slots 2,4,6,7,8 use trap community abc.
But, if you had several "sets" of communities in a DECagent 90 (ie you
are managing several DEChub 90's or 90 standalone modules with different
communities) you can give each community "set" its own trap community.
A set being the read/write, read-only, and trap community for a module/hub.
You can not set this from within HUBwatch or from the console, you'd
have to use a generic tool.
> In My Favorite Dechub900 i have plugged a 900FP , my Ip services Modules
> is a DECBridge900MX.
> all modules have ip address, trap address , Gateway address,
> i received all traps (cold,warm start) from Hubmanager , but anything
> from Decbridge900 or 900FP.
>
> as omitted something or traps no works correctly on this Modules ??
It turns out that there was a bug with the DECrepeater firmware when trying
to send the specific trap rptrResetEvent this will be fixed in the 60 day
upgrade. There was also a problem when you inserted a 900FP, 900GM and
sometimes a 900TM that you would not receive the coldStart (and for
certain modules the linkUp) trap. This problem can be seen (fairly
regularly with the 900FP) if your workstation is connected into the hub
through the thinwire channel. I.e. you have your thinwire going into
a Repeater 90C port.
What is happening is the repeater is coming up and sends the traps out
before the hub management agent has connected the repeater to the
thinwire. If you were connected into the hub through the front of the
900FP you would see the trap. The repeater firmware folks are putting
a delay in so that the repeater will wait a fixed amount of time before
sending out the trap(s).
I believe the same problem may occur when you plug in a DECbridge 900MX
since all ports will be out the front of the module and unless your station
is connected through one of these ports you won't see the trap.
Well, I think that covers it. I'll let you know if I find out anything
else about the bridge.
Karen
|
|
Karen
Thanks for your explanation
>> There was also a problem when you inserted a 900FP, 900GM and
>> sometimes a 900TM that you would not receive the coldStart (and for
>> certain modules the linkUp) trap. This problem can be seen (fairly
>> regularly with the 900FP) if your workstation is connected into the hub
>> through the thinwire channel. I.e. you have your thinwire going into
>> a Repeater 90C port.
>> What is happening is the repeater is coming up and sends the traps out
>> before the hub management agent has connected the repeater to the
>> thinwire. If you were connected into the hub through the front of the
>> 900FP you would see the trap. The repeater firmware folks are putting
>> a delay in so that the repeater will wait a fixed amount of time before
>> sending out the trap(s).
As this problem has already escaladed in Engeenering group ??
for me, any documentations explain this restriction, seems to be a serious
problem in your firmware.
are you agree with that statment ???
for the 60 day upgrade , when begins 60 day ??
from last Distributed Firmware Consolided kit release or another date ??
thanks for any comments
Jean-Yves
|
| re .3
Jean-Yves,
The fix has already been made by the repeater firmware engineers and will
be available to all in the 60-day upgrade.
I don't know that I'd call it a serious problem with the firmware but
it definitely was a problem that we (HUBwatch and the Repeater folks)
identified and fixed. It was after all still sending the traps when it
should have, just before
Thanks for bringing it to our attention. At about the same time our
internal system test group also notified us about this issue.
Karen
|