
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2016 05:03 AM
Hello SNTC Users !
I am using SNTC successfully for almost 2 years.
Recently we performed an Access Point renew and we realize that SNTC portal is not updating the Access Point devices.
We can successfully managed the WLC through the Collector. SNMPv3 and SNMPv2 checked and OK.
The WLC is a 7500 with code 8.0.133.
Our Collector version is 2.6 and the SNTC portal.
I checked this forum before and all the suggestions using snmpwalk did not change the situation.
Attached there is the error print reading:
2. AIRESPACE-WIRELESS-MIB_bsnAP
_AIRESPACE_SWITCHING_MIB
Error:
[ com.google.gwt.user.client.rpc.InvocationException ]
Please, if anyone has a previous workaround for this issue we will be glad to hear.
Regards, Klaus
Solved! Go to Solution.
- Labels:
-
Smart Net Total Care
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2016 03:49 PM
Hello SNTC Users.
Following a thread about this same problem we decided to perform a collection inventory against the physical IP of our HA WLC implementation.
The error was happening when we tried the VIP.
Now the collection inventory worked fine and all APs are updated inside the SNTC Portal.
Cheers,

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2016 10:08 AM
Hi Klaus,
The error you are getting is actually usually related to the browser or java version. Could you try using a different browser or accessing the GUI from a different machine to see if it makes a difference?
Thanks,
Lynden
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2016 10:35 AM
Hello Lynden.
Many thanks for your support.
We have already tested with 3 different browsers and the same problem.
In fact we are less worried about the error [ com.google.gwt.user.client.rpc.InvocationException ] and more about the fact that the CSPC Collector is not updating the Access Point list in the SNTC Portal.
We are running Collections successfully and the WLC appears without problem. But the lists of CAPWAP APs is not changing since 6 months ago.
We are know thinking that the CSPC 2.6 collector as a bug with CAPWAP APs.
Many thanks for your help.
Regards,

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2016 11:15 AM
When was the date/time of the last successful inventory? The APs are collected during the inventory, so even if the WLC was discovered, it may not have picked up the APs. If the inventory ran successfully, then the problem is probably on the portal as opposed to the collector.
Thanks,
Lynden
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2016 12:02 PM
Hello Lynden.
Thanks again for your reply.
You mean the Inventory Collection ?
We run the collection and upload once a week.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2016 03:49 PM
Hello SNTC Users.
Following a thread about this same problem we decided to perform a collection inventory against the physical IP of our HA WLC implementation.
The error was happening when we tried the VIP.
Now the collection inventory worked fine and all APs are updated inside the SNTC Portal.
Cheers,

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2016 01:24 PM
Got ya, thanks for the update!
-Lynden
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2016 12:08 PM
What we think is the following:
- The WLC is discovered correctly.
- The collection (inventory is processed) - we believe that it cannot retrieve the CAPWAP APs.
- The Upload works ok.
The following thread is about the same problem:
https://supportforums.cisco.com/discussion/13041496/wlc-collection-failure-no-running-config-no-aps
But there is no clear solution.
We are now running a collection over the physical IP address of the controller to see if it worked.
Regards,

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2017 01:01 PM
Hello SNTC Users.
I am reopening this thread because the issue was not solved at all.
Regards,
