Re: [nv-l] Wireless Network Management and cisco mibs

[ray.smith@clorox.com]

yep that one came up.

The dup detect rules are based on slot values and these are based on the varbind arguments that are forwarded.  Since the subtree 224.1.x.x.x does not parse into slots the dup does not see them as separate events.



Ray Smith
IS Engineer
The Clorox Services Company
925-425-4363

James Shanks <jshanks@us.ibm.com> Sent by: owner-nv-l@lists.us.ibm.com 03/18/2004 10:39 AM Please respond to nv-l

To:        nv-l@lists.us.ibm.com         cc:                 Fax to:                 Subject:        Re: [nv-l] Wireless Network Management and cisco mibs

I'm not certain but I think the solution to your problem is in TEC.  Now my TEC skills are not hot, but they have a duplicate detection thing going on over there, which is configurable.  Have you asked them about turning it off?  If memory serves me, then somewhere in your TEC rules  you can say dup_detect = no and then the events are treated as individual just like they were sent. 

Anyone else? 

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

ray.smith@clorox.com
Sent by: owner-nv-l@lists.us.ibm.com

03/18/2004 01:26 PM

Please respond to
nv-l

To	nv-l@lists.us.ibm.com
cc
Subject	[nv-l] Wireless Network Management and cisco mibs

go easy I have only been using NV for 6 months. 


I am attempting to Configure the Cisco's Wireless LAN Solution Engine to forward traps to NetView and then have NetView forward Events to the TEC Console. 
NV 7.1.3 fp02 on Solaris,  TEC 3.7,   WLSE release 2.5fcs which manages the 1150 and 1200 series access points. 

I searched the archives and found entries for monitoring access points dated 2001.  These entries referenced the 350 ap's and spoke of 802.11 mibs.  This unfortunately did not shed light on my problem. 

The wlse refers to cisco-device-exception-reporting-mib.my.  This creates the oid .1.3.6.1.4.1.9.9.224 ciscoMgmt.  I was having trouble running mib2trap and opened a pmr.  Support guided me thru extracting the 224. trap from the mib and enlightened me on how wonderful cisco mibs are. 

The Problem is; 
wlse appliance options allow you to identify and forward events of interest to a north-bound trap receiver.  Everything from rogue ap detection to RF thresholds.  These can be setup with a P1, P2, P3 and so on.  When these event traps are forwarded they all come under the ciscoMgmt 224 oid.  (This is where I am learning, be kind) The ?varbind? arguments? for the additional 224.1.x.x.whatever that allow one to parse the ?varbind? trap ? arguments ? for the different P1 threshold, P1 rogue ap detect, P1 clients associated. All come under the top level 224. trap. 

This is fine if the staff were only looking at the NV event browser.  Since I am forwarding these events to TEC what happens is the duplicate arguments do not work since all the messages come from wlse and the 224ciscoMgmt oid.  So every event that comes after the first one overwrites the previous. 

Is there another way to do this?  Or shall I take Cisco TAC up on there offer to work with NetView Support and identify and then creating a more complete mib that parses the varbind arguments for the WLSE Appliance? 

Any Ideas?  Or am I totally off base here and someone is about to take me to school?  (which I probably need) 


Ray Smith
IS Engineer
The Clorox Services Company
925-425-4363