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
If someone is doing something similar, please send me a note.
Thanks for any information.
Jorge A. Jiles
Academic Information and
Communication Technologies (AICT)
Phone: (780) 492-9168
University of Alberta
"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."