| I'm not sure what you're asking, so I'll use the scatter-gun approach.
There's no HUBwatch alarm for backplane connection/disconnection, or port
connection/disconnection - yet.
The Management Agent Module, however, has a built-in RMON alarm on backplane
connection changed. A trap is sent whenever the 900TP hops on/off a
backplane LAN.
The 900TP can also send traps when port media becomes available/unavailable.
The trap is enabled by default.
You only get traps if you've given the device sending the trap an IP address,
and specified one or more trap-sinks (destination IP address for trap
messages).
Can you tell us about the security concern?
-Shawn
|
|
Most (all?) DECrepeater900's support intrusion protection and eavesdrop
protection. There are options on what to do in the event of a security
violation (i.e. partition the port). Intrusion and eavesdrop protection
address your customer's spoofing and promiscuous mode concerns. HUBwatch
screens support both forms of repeater security.
Most DECrepeater900's also support RMON Alarms and Events. By default,
when a 10Base-T repeater port is connected or disconnected, an SNMP trap
is sent, and a log entry is created in the RMON Log Table. (The idea
being that since traps are unreliable, the Log Table should be polled
regularly.)
Right now, you can't use HUBwatch to modify/create/delete RMON Alarm
and Event entries - which is probably okay in your case since the alarms
are created by default. Neither can you look at the Log Table through
HUBwatch. You'll have to use a generic SNMP MIB browser to do that
for now.
Other than the missing HUBwatch RMON support, I think we have a pretty
good story around security in our repeater products.
-Shawn
|