- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2013 10:16 PM - edited 07-04-2021 12:19 AM
Hi All ,
I was trying to configure the SNMP on WLC 5508 with version 7.4.100.0 When creating the SNMP settings and IP address , I have given the mask of 255.255.255.255 . But it says that it is invalid mask. If i am giving 255,255,255,252 or other mask it is taking.
We have other controller with mask 255.255.255.255 configured for SNMP . But here i am not able to configre. Plz help
Thanks,
TS.
Solved! Go to Solution.
- Labels:
-
Wireless Network Management
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2013 10:20 AM
Here is the bug information for this. You have to get bug fixed version given below to resolve it. 7.4 MR2 (7.4.111.x) would be the ideal code if you want to stay in the 7.4 release.
https://tools.cisco.com/bugsearch/bug/CSCud09069
Symptom:
unable to create SNMP Community with IP Mask 0_0_0_0 or 255_255_255_255
Conditions:
S/W : 7_4_100_0, 7_4_100_60, 7_4_110_0
Workaround:
none
Known Fixed Releases
8.0(50.52)
8.0(50.51)
7.5(102.0)
7.4(110.6)
7.4(111.9)
7.4(110.17)
Here is another post related to the same query.
https://supportforums.cisco.com/thread/2248107
HTH
Rasika
**** Pls rate all useful responses ****
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2013 10:41 PM
I had the same problem a few days ago and was told it's a known bug and should be fixed in the next version. I'm running with 255.255.255.254 netmask now, that's not too bad as workaround until this is fixed...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2013 01:47 AM
Hello,
I am also facing the same issue. Can u share the bug details if you have..?
Thanks
KVS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2013 09:12 PM
As well in the 7.4.100.60 verion , the issue persists.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2013 07:46 AM
In version 7.4.110.0, the issue persists :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2013 10:20 AM
Here is the bug information for this. You have to get bug fixed version given below to resolve it. 7.4 MR2 (7.4.111.x) would be the ideal code if you want to stay in the 7.4 release.
https://tools.cisco.com/bugsearch/bug/CSCud09069
Symptom:
unable to create SNMP Community with IP Mask 0_0_0_0 or 255_255_255_255
Conditions:
S/W : 7_4_100_0, 7_4_100_60, 7_4_110_0
Workaround:
none
Known Fixed Releases
8.0(50.52)
8.0(50.51)
7.5(102.0)
7.4(110.6)
7.4(111.9)
7.4(110.17)
Here is another post related to the same query.
https://supportforums.cisco.com/thread/2248107
HTH
Rasika
**** Pls rate all useful responses ****
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2013 05:29 AM
Thanks Rasika for the information...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2018 04:39 AM
Seems this old bug has been reinvented!
I'm running a WLC 2504 with SW 8.5.135.0
Wondering this will be fixed in 8.5.xxx MR4 ...
Harald
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2019 12:08 PM - edited 01-15-2019 06:52 AM
Also running 8.5.135.0 and experiencing this bug via the GUI.
However, adding the community via the CLI functions correctly:
config snmp community create COMMUNITY config snmp community accessmode {ro | rw} COMMUNITY config snmp community ipaddr IPADDR 255.255.255.255 COMMUNITY config snmp community mode enable COMMUNITY
Note that you will still get the "Invalid Ip Mask" error if you try to modify the community via the GUI. Modifications work correctly via the CLI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 09:58 AM
8.5.171.0 the bug is still present. Amazing.
