Re: [nv-l] Correlation of Cisco WDS1030 traps

[ray.smith@clorox.com]

Jorge,

We worked with the WLSE a couple of years ago and found it a challenge to integrate from the ap's > wlse > netview > up to tec.  It seemed the ap to wlse was a suited tool as you would expect.  And the wlse as you indicate was suited for trouble shooting and fat client management.

But to integrate up from the wlse to netview and on to tec, was easier said than done.  It turned out at that time, the wlse modified the trap and placed all of the info about the ap into $4. (not good)  Perhaps if we had gone straight from the ap to netveiw then the ap mibs and traps would have worked differently for us, but for security we only wanted the wlse to speak with the ap's.  Since the wlse was in the loop and the all of the information that was relevant to the ap and its health was kept in the one varbind of $4 in the trap.  We had to take a different road.

The approach we took, where 3rd level assisted us was;

parse the wlse cderMIBNotifications {1.3.6.1.4.1.9.9.224.2} into a new trap and turn the original 7 varbinds into 16.  This allowed us to slot for tec each varbind so tec could understand what he was being sent.  Otherwise whatever tec slot was created for $4 was simply overwhelmed with information.


The mib for the wlse you are looking for is;
cisco device exception reporting mib (cderMIBNotifications {1.3.6.1.4.1.9.9.224.2})



Ray Smith
"Chi fa falla, e chi non fa sfarfalla"

Justin Eagleson <justin_eagleson@gulfsoft.com> Sent by: owner-nv-l@lists.us.ibm.com 03/10/2006 03:38 PM Please respond to nv-l

To:        nv-l@lists.us.ibm.com         cc:        (bcc: Ray Smith/US-Corporate/Clorox)         Fax to:                 Subject:        Re: [nv-l] Correlation of Cisco WDS1030 traps

I've never worked with WLSE, but you should be able to load your 
standard device MIBs into WLSE, load the mib(s) for WLSE into Netview (I 
believe WLSE can forward snmp to a destination for monitoring, and WDS 
talks to WLSE). When you say "read the trapd.log", it makes me think you 
want to further integrate upstream with Netview. You can use addtrap to 
add the trap defs from WLSE and take the trap further, or integrate with 
TEC from there. HTH

Jorge Jiles wrote:
>
> As part of a wireless pilot project we have installed 50 access points 
> (Cisco aironet 1231G) in a couple of buildings. The real project once 
> approved could scale to over a 1000 units. We are also trying a Cisco 
> WDS1030 with the WLSE management tool. The WLSE seems to be a good 
> configuration and troubleshooting tool. To keep things simple for our 
> computer center operators we would like to send the traps we configure 
> in WLSE to our Netview server as snmptraps to be displayed as alarms. 
> Sending the traps is simple, but which would be the right procedure to 
> correlate these traps in Netview??? I don't want to just read the 
> trapd.log and react on the information there, instead I would like to 
> have more flexibility by using the correlation facilities from Netview 
> which is the way we are alarming on snmptraps send by different type 
> of devices with network connectivity (ups, environmental units, 
> sensors, switches, servers, routers, etc)
>
> I like the centralized approach of using WDS devices to monitor 
> several access points at once and send snmptraps from just a device 
> instead of 50 access points.
>
> In summary I would like to know:
>
> Which snmp mibs/traps need to be loaded in Netview to process the 
> traps sent by the WDS unit???
>
> Once I load the traps, I guess I can correlate based on the trap ID 
> the same way I'm correlating other traps.
>
> If there is no a particular mib/trap ID for the traps sent by the WDS, 
> How can I then correlate them once the reach the Netview server????
>
> If someone is doing something similar, please send me a note.
>
> Thanks for any information.
>
> Jorge A. Jiles
>
> Network Analyst
>
> Academic Information and Communication Technologies (AICT)
>
> Phone: (780) 492-9168
>
> University of Alberta
>
> Edmonton, Alberta
>
> Canada
>
> "This communication is intended for the use of the recipient to which 
> it is addressed, and may contain confidential, personal, and/or 
> privileged information. Please contact us immediately if you are not 
> the intended recipient of this communication. If you are not the 
> intended recipient of this communication, do not copy, distribute, or 
> take action on it. Any communication received in error, or subsequent 
> reply, should be deleted or destroyed."
>

-- 

Justin Eagleson

Gulf Breeze Software - www.gulfsoft.com <http://www.gulfsoft.com/>

Gulf Breeze Blog - www.gulfsoft.com/blog <http://www.gulfsoft.com/blog>





This e-mail (including any attachments) may contain information confidential to The Clorox Company and is intended only for the use of the intended recipient(s).  If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited.  If you have received this message in error, please delete this message and notify the sender immediately.