To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Avaya G3 Monitoring (resolved) |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Fri, 5 Nov 2004 16:03:54 -0500 |
Delivery-date: | Fri, 05 Nov 2004 21:04:20 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <OF105BC293.2676FE9B-ON85256F43.006B3F46-85256F43.006B851E@lnotes-gw.ent.nwie.net> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
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
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 |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] Object Turn Red after Ping, Barr, Scott |
---|---|
Next by Date: | Re: [nv-l] Avaya G3 Monitoring (resolved), James Shanks |
Previous by Thread: | Re: [nv-l] Avaya G3 Monitoring, James Shanks |
Next by Thread: | Re: [nv-l] Avaya G3 Monitoring (resolved), James Shanks |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web