To: | nv-l@lists.tivoli.com |
---|---|
Subject: | RE: Cisco 350 Wireless Access Points MIBs |
From: | "Davis, Donald" <donald.davis@firstcitizens.com> |
Date: | Fri, 28 Dec 2001 15:38:00 -0500 |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. James, They are out there regardless of this being only a draft standard. The source in my environment is a Cisco AP340. This is what my trapd.log messages look like after configuring the event(s): ...... A IEEE802dot11 Deauthenticate Frame 2 4 0x00 40 96 2a 23 79 I assume that "Deauthenticate Frame" is similar to an Authentication Failure. You can download the mib from: http://ftp.lucky.net/pub/doc/mibs/v1/IEEE802dot11-MIB-V1SMI.my <http://ftp.lucky.net/pub/doc/mibs/v1/IEEE802dot11-MIB-V1SMI.my> Cisco was NO help on this, they told me to get it from IEEE. Have you ever been to that site :(~ I parsed the following definitions out of that mib file. This can be copy/pasted directly into your trapd.conf Don Davis ################### # # enterprises: # IEEE802dot11 {1.2.840.10036.1.6} # # User added trap formats: # dot11Disassociate {1.2.840.10036.1.6} 6 1 A 3 0 "Status Events" $E Disassociation Frame $1 $2 $3 SDESC The disassociate notification shall be sent when the STA sends a Disassociation frame. The value of the notification shall include the MAC address of the MAC to which the Disassociation frame was sent and the reason for the disassociation. EDESC dot11Deauthenticate {1.2.840.10036.1.6} 6 2 A 3 0 "Status Events" $E Deauthenticate Frame $1 $2 $3 SDESC The deauthenticate notification shall be sent when the STA sends a Deauthenticate frame. The value of the notification shall include the MAC address of the MAC to which the Disassociation frame was sent and the reason for the deauthentication. EDESC dot11AuthenticateFail {1.2.840.10036.1.6} 6 3 A 3 0 "Status Events" $E Authenticate Fail $1 $2 $3 SDESC The authenticate failure notification shall be sent when the STA sends an Authentication frame with a status code other than successful. The value of the notification shall include the MAC address of the MAC to which the Authentication frame was sent and the reason for the authentication failure. EDESC -----Original Message----- From: James Shanks [mailto:jshanks@us.ibm.com] Sent: Friday, December 28, 2001 2:39 PM To: IBM NetView Discussion Subject: RE: [NV-L] Cisco 350 Wireless Access Points MIBs Blaine - Thanks, but can you clarify how you are using these MIBs, especially the IEEE802_11Draft6.txt one? That's a draft MIB and should not be required by any commercial product, at least as I understand how the iso MIB tree is supposed to work. Because it begins, iso(1).member-body(2).us(840) rather than iso(1).org(3).dod(3), it defines a proposed standard, like MIB-II, which when adopted by the ISO, should get moved over under another branch. A commercially available product should either be using standard internet stuff (which is iso(1).org(3).dod(6).internet(1)) or their own private stuff (which is iso(1).org(3).dod(6).internet(1).private(4).enterprises(1)). Most vendor MIBs are in this category, as is the awcVx MIB you sent. That's my understanding at any rate. So what is the draft standard for? It also appears that the copy you have appended has been converted by someone from its original SNMP V2 format into SNMP V1 format, and then heavily edited. I have seen the original out on the Cisco ftp site but am confused about its relevance and usefulness. Can you assist me? James Shanks Level 3 Support for Tivoli NetView for UNIX and NT Tivoli Software / IBM Software Group "Owens, Blaine C - Eastman" <bowens@EASTMAN.COM> Sent by: owner-nv-l@tkg.com 12/28/2001 01:46 PM Please respond to IBM NetView Discussion To: "'IBM NetView Discussion'" <nv-l@tkg.com> cc: Subject: RE: [NV-L] Cisco 350 Wireless Access Points MIBs Okay, here they are (attached): Blaine -----Original Message----- From: James Shanks [mailto:jshanks@us.ibm.com] Sent: Friday, December 28, 2001 1:37 PM To: IBM NetView Discussion Subject: RE: [NV-L] Cisco 350 Wireless Access Points MIBs Blaine -- Given that you had so much trouble getting them, I'd say you should try posting them here, maybe as .txt attachments. Surely others will have the same difficulties. It's either that or tell us in detail where you ftp'd and what files you got. James Shanks Level 3 Support for Tivoli NetView for UNIX and NT Tivoli Software / IBM Software Group "Owens, Blaine C - Eastman" <bowens@EASTMAN.COM> Sent by: owner-nv-l@tkg.com 12/28/2001 01:22 PM Please respond to IBM NetView Discussion To: "'IBM NetView Discussion'" <nv-l@tkg.com> cc: Subject: RE: [NV-L] Cisco 350 Wireless Access Points You need the 802.11 mib plus the Aironet specific mib awcVx.mib. I had an adventure getting these - on the Cisco site there was a link to the Aironet web site to get the mibs. This took you to a page telling you that Aironet had been bought by Cisco and a link to the page to get the mibs. Clicking on this link took you (guess where) - right back to the Cisco page you started from. I wound up getting them via ftp. I can send the mibs to you if you want. Blaine Owens -----Original Message----- From: Scott Bursik [mailto:tivoliesm@HOTMAIL.COM] Sent: Friday, December 28, 2001 12:31 PM To: nv-l@tkg.com Subject: [NV-L] Cisco 350 Wireless Access Points NetView 6.0.2 AIX 4.3.3 I am wanting to load mibs for a Cisco 350 Wireless Access Point. I am not sure what MIBS to load to make this work. Can anyone assist me with this? Thanks in advance. Scott Bursik _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com _________________________________________________________________________ NV-L List information and Archives: http://www.tkg.com/nv-l _________________________________________________________________________ NV-L List information and Archives: http://www.tkg.com/nv-l #### awcVx.txt has been removed from this note on December 28 2001 by James Shanks #### IEEE802_11Draft6.txt has been removed from this note on December 28 2001 by James Shanks ------------------------------------------------------------------------------ This electronic mail and any files transmitted with it are confidential and are intended solely for the use of individual or entity to whom they are addressed. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail. ============================================================================== James,
They
are out there regardless of this being only a draft
standard.
The
source in my environment is a Cisco AP340.
This
is what my trapd.log messages look like after configuring the
event(s):
......
A IEEE802dot11 Deauthenticate Frame 2 4 0x00 40 96 2a 23 79
I assume that "Deauthenticate Frame" is
similar to an Authentication Failure. You
can download the mib from:
Cisco
was NO help on this, they told me to get it from IEEE. Have you ever been to
that site :(~
I
parsed the following definitions out of that mib file. This can be copy/pasted
directly into your trapd.conf
Don
Davis
###################
# # enterprises: # IEEE802dot11 {1.2.840.10036.1.6} #
# User added trap formats: # dot11Disassociate {1.2.840.10036.1.6} 6 1 A 3 0 "Status Events" $E Disassociation Frame $1 $2 $3 SDESC The disassociate notification shall be sent when the STA sends a Disassociation frame. The value of the notification shall include the MAC address of the MAC to which the Disassociation frame was sent and the reason for the disassociation. EDESC
dot11Deauthenticate {1.2.840.10036.1.6} 6 2 A 3 0 "Status Events" $E Deauthenticate Frame $1 $2 $3 SDESC The deauthenticate notification shall be sent when the STA sends a Deauthenticate frame. The value of the notification shall include the MAC address of the MAC to which the Disassociation frame was sent and the reason for the deauthentication. EDESC
dot11AuthenticateFail {1.2.840.10036.1.6} 6 3 A 3 0 "Status Events" $E Authenticate Fail $1 $2 $3 SDESC The authenticate failure notification shall be sent when the STA sends an Authentication frame with a status code other than successful. The value of the notification shall include the MAC address of the MAC to which the Authentication frame was sent and the reason for the authentication failure. EDESC
------------------------------------------------------------------------------ |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: Cisco 350 Wireless Access Points MIBs, James Shanks |
---|---|
Next by Date: | Changing Object Status, Paul Sandler |
Previous by Thread: | RE: Cisco 350 Wireless Access Points MIBs, James Shanks |
Next by Thread: | RE: Cisco 350 Wireless Access Points MIBs, James Shanks |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web