| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Does Hubwatch produce auditable traps. Is there such a thing
defined in SNMP?
I have a customer whom has three Network Command Centers. He is
starting to purchase DEChubs and Hubwatch. He has not standardized
on a Enteprise Network Mgmt platform as trap receivers, but the for
runners are HP OV and Sun Net Mgr.
If a change is made on a DEChub via Hubwatch is there any way of
knowing where that change came from?
As I understand it- Hubwatch uses SNMP which is based on UDP -
so if a trap is not generated upon the the receipt of the set request
than there is no way of knowing where the set came from. So guess the
real question is -- is/could the source address of the element manager
(hubwatch) as well as the event (a successfully set) be sent as a trap?
Thanks in advance,
Jim
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1755.1 | NETCAD::SLAWRENCE | Mon Dec 05 1994 09:28 | 5 | ||
There is a group in the DEChub Public Common mib that can be used to
control what addresses (address & mask) are allowed to perform sets,
but no traps are sent for successfull sets.
| |||||
| 1755.2 | Not in SNMP, but is in SNMPv2. | NETCAD::GALLAGHER | Mon Dec 05 1994 10:36 | 21 | |
Your customer can use pcomSnmpAuth objects in the "DEChub900 Public Common MIB" to ensure that only the three Network Management Stations (NMS) are allow set access. (As described in .1.) What your customer really wants is SNMPv2 on the NMS. SNMP Version 2 contains the "Manager to Manager" MIB. It allows the three NMS to communicate changes made to a device. (There are no plans to support SNMPv2 in HUBwatch, but maybe HP and Sun will provide a solution.) The next version of the Hub Management Agent Module (MAM) will contain RMON Alarms and Events. If your customer uses the MAM for all sets to line-cards in the hub, RMON A&E can be used to monitor key objects which indicate that the hub has undergone a change. RMON A&E can be set up to send an SNMP trap when changes occur. The addresses of the three NMS should be set as "trap sinks" via the MAM's console, or via the pcomSnmpAuth group. Only a limited number of objects can be monitored (say 20). For example, the MAM could be configured to send traps to the three NMS when the Hub's backplane configuration changed. (There is no HUBwatch support for RMON A&E [and none is planned] so setting this up is only useful for very sophisticated SNMP users.) -Shawn | |||||
| 1755.3 | Look foward to it. | ODIF11::LICATA | Mon Dec 05 1994 13:29 | 4 | |
Thanks for the response. It was right on target.
Jim
| |||||