| > Can I poll several agents simultaneously and update an alarm window
> on configuration and status changed,error and throughput threshold
> exceeded.
The basic Alarms package will handle traps, configuration changes
and "canned alarm rules" for DEChubs and their modules. It will
poll multiple hubs simultaneously and report events to an alarm
viewer. The viewer will be able to display both current and past
events. The user will be to control which agents have these events
enabled so that any or all hubs can be selected.
For the first release there is no easy way to write customized
alarm rules. However, the user could edit the rules file provided to
add new rules as it is an ascii file.
I'm not sure what specific traps will be available from the DEChub
modules.
Hope this helps,
Bob
|
| > what does "basic alarming" mean in hubwatch V3.
>
> Can I poll several agents simultaneously and update an alarm window on
> configuration and status changed,error and throughput threshold exceeded.
>
>
I'll let one of the HubWatch folks answer this these, but realize that these
questions are completely independent of your next question:
> Do you plan to update the module firmware to send some specific traps?
Yes. We plan to support the Remote Monitoring MIB's (aka RMON, aka rfc1271)
alarm and event groups (aka RMON a&e). RMON a&e will be in the March release
of the Management Agent Module Firmware. It will also be put into other
900 products - though none have made schedule commitments to adding it.
Using RMON a&e you can configure the agent to log an event, send an enterprise
specific Trap when an event occurs, or both.
RMON a&e on the Management Agent will allow you to alarm on *any* supported
object which resolves to an integer type. (For example, you can monitor
INTEGERs, Counters, Gauges, and TimeTicks. You can not monitor OCTET STRINGs,
DisplayStrings, or OBJECT IDENTIFIERS.)
RMON a&e on the Management Agent will allow a limited number of alarms to
be configured. (The limiting factor is the amount of non-volatile memory
we want to devote to this feature. This number is TBD.)
The Management Agent will ship with some alarms enabled. So far we have
default alarms which log and Trap when:
- a module is inserted into or removed from the hub,
- an environmental warning or failure is detected (i.e.
a module's fan(s) fail, a module reports a temperature
warning or failure, etc.)
- a power supply is added or removed,
- redundant power becomes available or unavailable,
- a backplane connection is created or deleted,
- the MAM's non-volatile memory fails,
- and others.
(Of course, until it ships, these are subject to change without notice. ;-)
Users can mess with the default alarms, turning them off, changing the
polling interval, selecting logging only, etc.
As you can see, RMON would migrate really well to repeaters, bridges, and
concentrators. You could alarm on ports partitioning, interfaces going
down, security violations, etc.
-Shawn
|
| Is there a chance to trigger a script file on the operating system as
an option, and supply parameters to it.
(at real Multitasking OS only of course !)
This would be very helpful for a lot of Customer situations
In the moment we would need MCC or NetView to do this, and very often
Hubwatch is used standalone.
Guenter
|