James,
Thanks for your reply. I attempted to load g3mib20_asn1 after
I commented out the ISO and received the following error message. I
appreciate your assistance.. Dave
Line 37184: Warning: token longer than allowed maximum, truncating
alarmCritical TRAP-TYPE
ENTERPRISE g3-products
VARIABLES {
g3clientExternalName,g3alarmsProductID,g3alarmsAlarmNu
mber,g3alarmsPort,g3alarmsMaintName,g3alarmsOnBrd,g3alarmsAlarmType }
DESCRIPTION "This trap is defined for future use."
::= 1
Line 37190: Warning: token longer than allowed maximum, truncating
alarmMajor TRAP-TYPE
ENTERPRISE g3-products
VARIABLES {
g3clientExternalName,g3alarmsProductID,g3alarmsAlarmNu
mber,g3alarmsPort,g3alarmsMaintName,g3alarmsOnBrd,g3alarmsAlarmType }
DESCRIPTION "A Major alarm has been issued by the switch. The
MIB variables provide attributes of the alarm. The
information contained in the g3alarmsPort,
g3alarmsMaintName, g3alarmsOnBrd trap variables
differ depending on the kind of alarm. If the
alarm is a voice server alarm these fields
contain, respectively, an equipment location,
maintenance object name, and flag indicating
whether or not the alarm was on-board. For
server platform alarms and messaging alarms these
fields contain, respectively, an alarm description
including the source of the alarm, a string
indicating the resource from which the alarm
was generated, and an event ID associated with that
resource. More details on the contents of these
fields can be found in the appropriate product
maintenance documentation.
::= 2
Line 37213: Error defining TRAP-TYPE: Expected '::=', found 'A'
alarmMinor TRAP-TYPE
ENTERPRISE g3-products
VARIABLES {
g3clientExternalName,g3alarmsProductID,g3alarmsAlarmNu
mber,g3alarmsPort,g3alarmsMaintName,g3alarmsOnBrd,g3alarmsAlarmType }
DESCRIPTION "A Minor alarm has been issued by the switch.
The fields in this trap type has the same
differences, for g3alarmsPort, g3alarmsMaintName,
and g3alarmsOnBrd, as described above for the
alarmMajor trap type."
::= 3
James Shanks
<jshanks@us.ibm.com> T
To: nv-l@lists.us.ibm.com
Sent by: cc:
owner-nv-l@lists.us.ibm
.com bcc:
Subject:
Re: [nv-l] Avaya G3 Monitoring
(resolved)
11/05/2004 04:41 PM
Please respond to nv-l
This is my third response (sigh).
It was pointed out to me that my last append on this subject was not quite
technically correct. The solution I offered, of commenting out the line
iso OBJECT IDENTIFIER ::= { 1 }
does work. But the reason we rejected the MIB was not because iso was the
root of the tree, but because it was incorrectly specified. The actual
root of the international MIB tree is "ccitt", which has the value zero.
So to be completely correct, this MIB has to say,
iso OBJECT IDENTIFIER ::= { ccitt 1 }
and then it will load just fine.
This just shows you the dangers of redefining everything back to the common
parts of the tree. As long as your defs are consistent with what's already
loaded, then all is well. But if you deviate from that , the MIB won't
load. Which is why it's better to start, as most vendors do, with just the
parts they are responsible for. In this case that would be this line, and
everything which follows:
avaya OBJECT IDENTIFIER ::= { enterprises 6889 }
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
James Shanks/Raleigh/IBM@IBMUS
Sent by:
owner-nv-l@lists.us.ibm.com To
nv-l@lists.us.ibm.com
cc
11/05/2004 04:03 PM
Subject
Re: [nv-l] Avaya G3
Please respond to Monitoring (resolved)
nv-l
This is my second response.
I thought at first you were asking about pre-reqs but then I started to
puzzle over that error message and I couldn't see how that related, so just
for grins I downloaded one of these MIBs, g3mib20_asn1, to see what it
looked like. I collect problem MIBs as a sort of hobby. I tried to load
it and got the same error you did about the parent not being defined.
Here's what the MIB looks like at the beginning with lots of definitions,
the first
3-AVAYA-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE, DisplayString
FROM RFC1213-MIB
OBJECT-TYPE, NetworkAddress, IpAddress, Counter, Gauge, TimeTicks
FROM RFC1155-SMI;
-- The following should be defined elsewhere
iso OBJECT IDENTIFIER ::= { 1 }
org OBJECT IDENTIFIER ::= { iso 3 }
dod OBJECT IDENTIFIER ::= { org 6 }
internet OBJECT IDENTIFIER ::= { dod 1 }
private OBJECT IDENTIFIER ::= { internet 4 }
enterprises OBJECT IDENTIFIER ::= { private 1 }
avaya OBJECT IDENTIFIER ::= { enterprises 6889 }
mibs OBJECT IDENTIFIER ::= { avaya 2 }
definity OBJECT IDENTIFIER ::= { mibs 8 }
g3-mib OBJECT IDENTIFIER ::= { definity 1 }
g3proxmib OBJECT IDENTIFIER ::= { definity 2 }
products OBJECT IDENTIFIER ::= { avaya 1 }
def-products OBJECT IDENTIFIER ::= { products 8 }
g3-products OBJECT IDENTIFIER ::= { def-products 1 }
Now what the error message "Line 0: Error defining object ": Parent" not
defined." is trying to tell you is that we don't know where to start
putting all these definitions. That's because we already start at the iso
level and you cannot redefine that. So all you have to do to get this to
load (and any others like this) is to comment out the line which reads
iso OBJECT IDENTIFIER ::= { 1 }
by putting 2 dashes in front of it, like this
- - iso OBJECT IDENTIFIER ::= { 1 }
and it should load just fine. It does for me.
In fact, everything down to the Avaya enterprise is redundant and could
also be commented out. But its re-defining the root of the MIB tree is why
we gave you the error message.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
reamd@Nationwide.com
Sent by:
owner-nv-l@lists.us.ibm
.com To
nv-l@lists.us.ibm.com
cc
11/05/2004 02:34 PM NetView User List
<nv-l@lists.us.ibm.com>,
owner-nv-l@lists.us.ibm.com
Please respond to Subject
nv-l Re: [nv-l] Avaya G3 Monitoring
Thanks Mahesh,
I attempted to load all the G3 mibs and
received error Line 0: Error defining object ": Parent" not defined. I
assume it needs other mibs loaded prior to the G3's.. I have RFC1213-Mib
and RFC1155-SMI mibs loaded.. Thanks, Dave
Mahesh Tailor
<mahesh.tailor@network. T
carilion.com> To: NetView User List
<nv-l@lists.us.ibm.com>
cc:
Sent by:
owner-nv-l@lists.us.ibm bcc:
.com Subject:
Re: [nv-l] Avaya G3 Monitoring
11/04/2004 03:38 PM
Please respond to nv-l
Try this link.
http://support.avaya.com/elmodocs2/MIB/
HTH
Mahesh
On Thu, 2004-11-04 at 15:06, reamd@Nationwide.com wrote:
>
>
> Hi All,
> We are looking to monitor Avaya G3 PBX's with netview. Does
> anyone do this? If so, can you tell me where the mibs are and/or how you
> monitor them.
>
> Thanks, Dave
>
> AIX 5.1
> 7.1.4 FixPack1
--
Mahesh Tailor
WAN/TSM/NetView Administrator
Carilion Health System
Information Services
451 Kimball Avenue
Roanoke, VA 24016
Phone: 540.224.3929
Fax: 540.224.3954
|