To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | [nv-l] Mib2trap alcatel AOS devices |
From: | "Christopher J Petrina" <cjp8@meadwestvaco.com> |
Date: | Tue, 13 Jan 2004 10:40:51 -0500 |
Delivery-date: | Tue, 13 Jan 2004 15:48:47 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
I saw a couple people out there with this issue but no resolution. We have some new Alcatel devices that do not look like they support the old xylan mib structure. mibbrowsed to the ojectID and it returns 1.3.6.1.4.1.6486.800 on the new one where the old alcatels built off the xylan structure were 1.3.6.1.4.1.800. we have old one s as well. The xylan mibs contain NOTIFICATION-TYPE and TRAP-TYPE information, however a mib2trap will not work. They always report errors. Anyone else using alcatel devices especially those running the AOS 5.1.4. The only MIBS I have found for those are V2 MIBS that use the MODULE-IDENTITY structure that is not supported in the xnmloadmib file. it only works in the xnmloadmib2 which as we all know are not able to create traps for trapd to understand. 2nd question: I created in xnmtrap an enterprise identification of Alcatel and the enterpriseID of 1.3.6.1.4.1.6486.800 -> with just that and the devices configured to send traps I should at least receive a trap fromt he device should I not? even if I get the FMT no format for trap found? Thanks Chris Petrina |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] CPU monitoring on routers/switches, CMazon |
---|---|
Next by Date: | [nv-l] A plea for anyone who used the old Tivoli Manager for Network Connectivity product, Van Order, Drew \(US - Hermitage\) |
Previous by Thread: | [nv-l] CPU monitoring on routers/switches, Mario Behring |
Next by Thread: | Re: [nv-l] Mib2trap alcatel AOS devices, James Shanks |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web