| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1037.1 | Nope, it isn't easy.....yet. | QUIVER::GALLAGHER | | Fri May 27 1994 10:46 | 25 |
| Jean-Yves,
You're seeing an "enterprise specific populationChange" trap. This, and
other enterprise specific traps, are defined in the dechub90's private
MIB.
The TRAP-TYPE definition is:
>populationChange TRAP-TYPE
> ENTERPRISE decagent90v1
> VARIABLES { da90CommunityIndex, dh90SlotIndex, dh90SlotObjectID }
> DESCRIPTION
> "A module has been added or discovered, or has been deleted or
> undiscovered. The objects dh90PopulationChange and
> dh90PopulationLastChange have been updated to reflect this change.
> The community index, slot index, and module object id are included in
> the trap PDU."
> ::= 4
Yes, you have to look at the TRAP-TYPE definition to understand what the
trap means. And no, this is not "customer friendly". I suspect future
versions of HubWatch will have more extensive decoding of enterprise
specific traps.
-Shawn
|
| 1037.2 | Suspect or more | PADNOM::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Fri May 27 1994 12:16 | 11 |
| >>Yes, you have to look at the TRAP-TYPE definition to understand what the
>>trap means. And no, this is not "customer friendly". I suspect future
>>versions of HubWatch will have more extensive decoding of enterprise
>>specific traps.
First thanks to reply,
you suspect only ???
i think it's a major feature ,that will be implemented right now !!!
(like other hub vendors).
Jean-Yves
|
| 1037.3 | agree | ZUR01::SCHNEIDERR | | Fri Jun 10 1994 03:00 | 17 |
| > you suspect only ???
> i think it's a major feature ,that will be implemented right now !!!
> (like other hub vendors).
>
> Jean-Yves
I agree comleatrly with Jean-Yves. I had no time to play arround with Alarming.
But this means at the moment not to tell any customer about this feature
because the risk they try it out :-)
Question: Who of our customer would accept such an implementation? Are all the
traps undecoded????
Roland
|
| 1037.4 | If we could do it all right now we would. | NACAD::GALLAGHER | | Fri Jun 10 1994 11:30 | 14 |
| >I agree comleatrly with Jean-Yves. I had no time to play arround with Alarming.
>But this means at the moment not to tell any customer about this feature
>because the risk they try it out :-)
>
Perhaps you should try it. By knowing something about it you can better
decide whether it's a feature that you can or can't tell customers about.
>Question: Who of our customer would accept such an implementation? Are all the
>traps undecoded????
No, only enterprise specific traps are undecoded. Standard traps are decoded.
-Shawn
|
| 1037.5 | Need MORE INFO about ALARMS and TRAPS in V3 | MSDOA::REED | John Reed @CBO, DTN:367-6463, KB4FFE, SouthEast | Fri Sep 02 1994 13:54 | 59 |
|
I have a question about Hubwatch Trap Events. I recently installed
HUBwatch at a customer site, (VAX 4000/90, HUBwatch for VMS (v3),
several DEChub90's) and the tool installed nicely. I upgraded the
DECagent 90 to the new DENMA021 Agent code which was very difficult.
I tried NDU, (which didn't support the DECagent v1.0 firmware) and NCP
trigger and load commands, but they didn't work. I had to get my old
DENMA_LOAD.EXE program from the DENMA011.A kit, and use the control-I
trick to force the agent to request DENMA011.SYS from the load host. I
renamed DENMA021.SYS as 011, and the new V2.1.3 code was loaded. The
DCF010 kit did not contain a DENMA.EXE that requested v021 of DENMA
code. THIS SHOULD BE PART OF THE CONSOLIDATED KIT !!
(Back to my question) After I got the Hubwatch for VMS V3 (from most
recent CD distribution) running, I loaded the IP addresses into the
modules and various agens, and assigned trap addresses and communities.
I opened the ALARMS viewer window, and we tried inserting and removing
modules, and powering off PC's and stations on the various HUB ports.
I received ALARM events in the VIEWER window, but only the Cold Start,
and Generic traps were defined (translated into english). The Module
or "enterprise specific" traps were passed in their lengthy format
1.4.1.15.1.4.3.5.x.y.z = 7 with the word "varbind" occasionally stuck in
there to confuse the user.
IS there some way to compile these long numeric SNMP trap events into
their english equivalent. It sure would be nice to see text that said:
"Agent DECagent3 reported Slot 4, Port 7: Link Down" or something like
that. The customer also asked for ways to show ALARMS that only have
a certain level of importance. He was annoyed that each time I powered
up or powered down a PC, he would receive a TRAP message. This trap
message was VERY SIMILAR in appearance to the trap message that
occurred when I pulled a repeater completed out of the HUB. He wanted
to be flagged in a MORE URGENT way, when a monumental thing such as
removing a module occured. He also wanted to see a message when I
unplugged the DECagent itself (impossible I know, since the DECagent
sends the message) but the POLLER should report "In an obvious way, in
the same ALARM Viewer window" when the device can no longer be polled.
I looked around in the Alarms SETUP, but I got a screen that displayed
the file HUBWATCH$LIBRARY:hubwatch_alarmed_Agents.dat, but the file
itself did not exist. Nor did I find a template for this file. I do
not know how to create it. There were pushbuttons for TRAPS, and
SELECT but I don't know what they do. If I push them, nothing seems
to occur, and If I open the window after defining several modules and
hitting "apply", or "OK", still the window opens without any data...
How do I define permanent pollers, and what is the format of this file?
I told the customer that I would get back to him soon on these issues.
Who should I contact to follow up on this ?
Thanks;
JR
|
| 1037.6 | | LEVERS::SKABO | Expect Nothing: You'll never be disappointed | Fri Sep 02 1994 16:05 | 36 |
| Hello John,
From the HUBwatch V3.0 Release Notes to ensure that the POLLER/VIEWER
is displaing TRAPPS :
o The procedure for starting and stopping the Alarms Poller
should include the following notes:
1. With the exception of DECserver 90M, 90TL,
and 900TM modules, there is no need to
manually set up trap addresses in the
various hub network modules. The terminal
server modules do not allow the setting
of the trap address by means of SNMP; you
must enable traps from the terminal server
console.
For all other network modules, the Alarms
Poller uses both the information from the
Alarmed Agents list box in the Alarms Setup
window, and the IP address of the network
management station to automatically set the
trap addresses.
2. To restart the Alarms Poller after it has
been stopped, you must open the HUBwatch
Alarms Setup Window. (This causes the
HUBwatch alarmed agents file to be read,
and the agents in the file to be registered
with the Event Daemon.)
Hope this helps so TRAPPS are started....
Tom Skabo - DEChub System Test
|
| 1037.7 | Where is ALARMED data file ? | MSDOA::REED | John Reed @CBO, DTN:367-6463, KB4FFE, SouthEast | Fri Sep 02 1994 17:20 | 6 |
| Where is the Hubwatch ALARMED agents file, and what format is it
written in? I could not seem to find this file in the
HUBWATCH$LIBRARY location.
JR
|
| 1037.8 | HUBWATCH$ALARM_FILES location | NACAD::SKABO | Expect Nothing U never disappointed | Tue Sep 06 1994 11:15 | 45 |
| Hello John,
When you did the installation of HUBwatch the question below was
asked:
* System-wide translation for HUBWATCH$LIBRARY: [SYS$LOGIN]:
The logical name HUBWATCH$ALARM_FILES may be defined as the directory
which will be used for writing HUBwatch event polling and alarm
logfiles.
SYS$STARTUP:HUBWATCH$STARTUP.COM will define the system-wide logical
name HUBWATCH$ALARM_FILES as SYS$MANAGER. To assign a different
system-wide translation for HUBWATCH$ALARM_FILES enter it below.
You may also edit SYS$STARTUP:HUBWATCH$STARTUP.COM at a later time.
If you took the default it would be put into SYS$LOGIN, and then when
you added TRAPs to the ALRAM SETUP window, it will create a file
called: HUBWATCH_ALARMED_AGENTS.DAT <-- which is a data file, see below
for an example of the file:
HUBWATCH_ALARMED_AGENTS.DAT
#
# HUBwatch alarmed agents file.
# Created Fri Sep 2 11:35:10 1994
#
HUB_ID : the-hub
IP : 16.20.128.188
COMMUNITY : "public"
POLLING_INTERVAL : 20
NOTIFY_CONFIG_CHANGES : TRUE
NOTIFY_TRAPS : TRUE
#
HUB_ID : dettm...
IP : 16.20.128.195
COMMUNITY : "public"
POLLING_INTERVAL : 20
NOTIFY_CONFIG_CHANGES : TRUE
NOTIFY_TRAPS : TRUE
#
Hope this helps....
Tom Skabo - DEChub System Test
|