| Title: | Server_works |
| Moderator: | PCBUOA::IS_SYSTEM |
| Created: | Fri Jun 30 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 291 |
| Total number of notes: | 1063 |
Is the MYLEX GAM MIB file compilable with ManageWorks 2.2?
I have tried the MIB file from the GAM disks in our ServerWORKS kit.
I have tried the newer v2.05 GAM kit from the MYLEX Web server.
I have tried removing comments and blank lines.
But I always get (right after starting the compiler)
"Internal Application Error"
and the compiler hangs and has to be crashed.
Any hints?
- Risto
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 207.1 | SUTRA::16.36.2.177::Bats | Speeding, speeding, I'm always speeding | Mon Feb 10 1997 16:11 | 6 | |
If you use ServerWorks v2.2 it already has them compiled for you. Pjotrr | |||||
| 207.2 | MIB compiler hangs V2.2 | TRLIAN::COFFIN | Mon Apr 21 1997 20:03 | 9 | |
I have seen the same "Internal Application Error"
followed by a hang of the MIB compiler with ManageWORKS 2.2
when trying to compile our private MIB. Are there any patches
or workarounds?
Thanks,
Barry
| |||||
| 207.3 | ANy incremental information/ | PCBUOA::WHITEC | Parrot_Trooper | Tue Apr 22 1997 14:28 | 9 |
What version of GAM Are you trying to install? We are at kit 1.05
and Mylex GAM 2.0. Nothing past this has been passed to us for
being officially qualified....
I have found the directions on the akin40.ako.dec.com Digital
ServerWORKS section, kits, ServerWORKS V2.2 README.TXT
chet
| |||||
| 207.4 | MIB compiler hangs! | TRLIAN::COFFIN | Tue Apr 22 1997 15:11 | 16 | |
We have our own private MIB which I am trying to compile (ASN.1 syntax).
This is the MIB Compiler under the ManageWORKS SNMP MIB Enroller. The
MIB compiler hangs.
I installed the ManageWORKS V2.2 and ServerWORKS V2.2 from the
~theworks/kits/sw22ssb_web/ area. I did not install any Mylex
GAM kit.
We need to get our MIB compiled. Is this a known problem?
Barry
Barry
| |||||
| 207.5 | reasons in help do not seem to apply | TRLIAN::COFFIN | Tue Apr 22 1997 20:13 | 15 | |
I saw the "Troubleshoot MIB Compiler Errors" section of the
help and it seems that the possible reasons for "Internal
Application Error" stated in that section do not apply to this
case. The MIB file was copied through ftp(ASCII) and has the
CR/LF's. The file is not read only and there is plenty of disk
space. Are those cases where the MIB compiler also hangs or does
it print out an error message?
Whats the next step on debugging this? Is there a later version of
the MIB Compiler?
Thanks,
Barry
| |||||
| 207.6 | Can you post it? | PCBUOA::WHITEC | Parrot_Trooper | Tue Apr 22 1997 20:47 | 8 |
Can you post the MIB......The last instance of this involved a
bogus mib. Engineering will take a look if it can be posted.
Other thoughts, is the MIB local to the disk with Manageworks.
This is a MUST. (Problem with file open call not working remotely)
chet
| |||||
| 207.7 | ok, heres the MIB | TRLIAN::COFFIN | Wed Apr 23 1997 13:00 | 205 | |
Yes the MIB is local to the disk with ManageWORKS. The MIB compiles
fine with NetView. The IPFM MIB follows:
IPFM-MIB DEFINITIONS ::= BEGIN
-- IPFM - IP Fault Manager MIB extension
IMPORTS
enterprises
FROM RFC1155-SMI
DisplayString
FROM RFC1213-MIB
OBJECT-TYPE
FROM RFC-1212;
-- This MIB Module uses the extended OBJECT-TYPE macro as
-- defined in [9].
dec OBJECT IDENTIFIER ::= { enterprises 36 }
ema OBJECT IDENTIFIER ::= { dec 2 }
sysobjectids OBJECT IDENTIFIER ::= { ema 15 }
ipfm OBJECT IDENTIFIER ::= { sysobjectids 25 }
-- All alarms will have an ASCII discription associated
-- with them.
AlarmType ::= DisplayString
-- General information about this product and alarms.
ipfmProductID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of this object is the registered
object identifier for this product. A value
of (0,0) should be returned if unsupported."
::= { ipfm 1 }
nodeDescr OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A textual description of the particular node
within the IP system."
::= { ipfm 2 }
nodeNumAlarms OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current number of alarms on this particular
IP node."
::= { ipfm 3 }
nodeStatus OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The alarm condition status of this node."
::= { ipfm 4 }
-- The Alarm Table. There is one entry in the table
-- for each alarm recorded for each node in the IP system.
alarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF AlarmEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The conceptual table of alarms for all nodes which
live in this IP system."
::= { ipfm 5 }
alarmEntry OBJECT-TYPE
SYNTAX AlarmEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A conceptual entry for each alarm recorded for the
particular node."
INDEX { alarmIndex }
::= { alarmTable 1 }
-- the alarm entries may need additional fields added depending
-- on the info we want to monitor with them
AlarmEntry
::= SEQUENCE {
alarmIndex INTEGER,
alarmSeverity AlarmDesc,
alarmDescript AlarmDesc,
alarmStatus INTEGER,
alarmTimestamp AlarmDesc
}
alarmIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique value for each AlarmEntry. This
object may be set during row addition only.
Values of this object range from 1 to
NodeNumAlarms."
::= { alarmEntry 1 }
alarmSeverity OBJECT-TYPE
SYNTAX AlarmType
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The severity of the particular alarm CRITICAL,
MAJOR, or MINOR in ASCII text."
::= { alarmEntry 2 }
alarmDescript OBJECT-TYPE
SYNTAX AlarmType
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The ASCII test descriptive notation describing
the particular alarm."
::= { alarmEntry 3 }
alarmStatus OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Status of this alarmEntry. May be set to a
value of Delete only."
::= { alarmEntry 4 }
alarmTimestamp OBJECT-TYPE
SYNTAX AlarmType
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The ASCII test descriptive notation containing
the timestamp of this particular alarm event."
::= { alarmEntry 5 }
ipfmCritTrap TRAP-TYPE
ENTERPRISE ipfm
VARIABLES {
alarmSeverity,
alarmDescript,
alarmStatus }
DESCRIPTION
"This is the IPFM critical alarm trap, it
contains the severity, description, and
status of a critical alarm condition."
::= 199
ipfmMajorTrap TRAP-TYPE
ENTERPRISE ipfm
VARIABLES {
alarmSeverity,
alarmDescript,
alarmStatus }
DESCRIPTION
"This is the IPFM major alarm trap, it
contains the severity, description, and
status of a major alarm condition."
::= 200
ipfmMinorTrap TRAP-TYPE
ENTERPRISE ipfm
VARIABLES {
alarmSeverity,
alarmDescript,
alarmStatus }
DESCRIPTION
"This is the IPFM minor alarm trap, it
contains the severity, description, and
status of a minor alarm condition."
::= 201
ipfmAlarmInfoTrap TRAP-TYPE
ENTERPRISE ipfm
VARIABLES {
alarmSeverity,
alarmDescript,
alarmStatus }
DESCRIPTION
"This is the IPFM alarm information trap, it
contains the severity, description, and
status of an alarm condition which has
changed its status."
::= 202
END
| |||||
| 207.8 | Bad news, and good news? | PCBUOA::WHITEC | Parrot_Trooper | Wed Apr 23 1997 18:53 | 11 |
You are correct, this MIB does not compile under ManageWORKS 2.2.
engineering is evaluating the problem, but don't expect a fix.
The good news is that the MIB DOES compile with ServerWORKS Manager V3.
It is available as a fieldtest kit on akin40.ako.dec.com open Digital
ServerWORKS and look for Version 3 fieldtest link.
Understand that it is not officially supported.
Chet
| |||||
| 207.9 | thanks | TRLIAN::COFFIN | Wed Apr 23 1997 19:20 | 5 | |
Thanks for checking it out. I'll try it with the fieldtest kit.
Barry
| |||||
| 207.10 | When will version 3.0 be released | TRLIAN::COFFIN | Wed Apr 23 1997 19:52 | 5 | |
When is version 3.0 set to be officially released?
Barry
| |||||
| 207.11 | PCBUOA::WHITEC | Parrot_Trooper | Thu Apr 24 1997 14:06 | 6 | |
oct-emb-uary! ;^)
I believe it will be sometime in May/June.
Chet
| |||||