AP SSO WISM2 WLC 7.4.121

HI everyone,
I'm currently doing a proof of concept on the AP SSO feature running on WLC 7.4.121.
The first thing I would like be sure is that client SSO is not avalaible in 7.4.X release, i need to upgarde to 7.5.X, Am I right ?
The second thing I would like to share and investigate with you is about AP SSO not currently working in my topology.
I have 2 seperate C6500 (SUP720-3B) switches with 1 WISM2 in each and both switches interconnected trough a 10G port.
I enable AP SSO on both WLC that synchronize themselves trough the 10G port on a special redundancy VLAN.
They both synchronize, and everything is working (both AP database on primary and standby WLC).
What I can't understand is when forcing switchover on the primary (redundancy force-switchover command), the fallback is doing great to the standby WLC but the AP still get into CAPWAP DISCOVER state because of a timeout with the following logging message
*Feb 14 15:36:37.727: %CAPWAP-3-ERRORLOG: Sequence number (0) mismatch in request messageDeleting clients for centrally switched wlan 1Deleting clients for centrally switched wlan 1Sending hreap clients to wlc on HA eventAP1cdf.0f66.90b4#% Cannot enable CDP on this interface, since CDP is not running% Cannot enable CDP on this interface, since CDP is not running., 5)14 15:37:22.934: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST*Feb 14 15:37:22.934: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
So the SSID is unavalaible for a certain period of time as it would be with N+1 redundancy.
I also saw that some documentation said that tle WLC needs to be run on a VSS (
http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/113681-high-availability-dg-00.html) and some other say the contrary (http://www.cisco.com/c/en/us/products/collateral/wireless/aironet-1130-ag-series/qa_c67-714540.html)
Did you manage to get AP SSO working and did you ever have this issue ?
Thank for you help !

HI Max,
The first thing I would like be sure is that client SSO is not avalaible in 7.4.X release, i need to upgarde to 7.5.X, Am I right ?The second thing I would like to share and investigate with you is about AP SSO not currently working in my topology.
Yes you need 7.5 version on WLC for Client SSO.
I never seen this tiype of error, You must contatc TAC and tell them about this issue.
Regards
Dont forget to rate helpful posts

Similar Messages

WISM1 (WLC 6.0.182) to WISM2 (WLC 7.2.115.1) migration

Hi all,
I plan to replace 2 x WISM1 (WLC 6.0.182) by 2 x WISM2 (WLC 7.2.115.1). One WISM in each Catalyst 6500. I am sorry it is a little long but I have no lab and I need your advice.
Summarized migration plan is the following :
Upgrade of the 4 WLC (WISM1) from 6.0.182 to 7.0.240
AP pre-download from the 4 WLC (WISM1)
Transfert WLC 7.0.240 image to the 4 WLC (last compatible version)
Transfert WLC 7.0.240 image from the 4 WLC to AP and swap AP primary and secondary image
So, AP primary image is 7.0.240, AP secondary image is 6.0.182
Scheduled reboot of the 4 WLC
So, 4 WLC (WISM1) and AP are running WLC 7.0.240
Move AP from the 2 WLC of the1st WISM1 to the 2 WLC of 2sd WISM1 Swap AP primary and secondary controller with NCS
Backup the configuration file
of one WLC of the 1st WISM1
of one WLC of the 2st WISM1
Replace the 1st WISM1 by one WISM2
WISM2 upgrade from the current WLC version to 7.0.240
Import the saved configuration file (WISM1) to WISM2 (7.0.240)
Check the configuration via HTTPS
Move AP from the 2 WLC of the 2sd WISM1 to the 1st WISM2 Swap AP primary and secondary controller with NCS
Replace the 2sd WISM1 by one WISM2
WISM2 upgrade from the current WLC version to 7.0.240
Import the saved configuration file (WISM1) to WISM2 (7.0.240)
Check the configuration via HTTPS
Upgrade WISM2 from 7.0.240 to 7.2.115.1
AP pre-download etc.
etc.
Please, what do you think about this migration plan ?
Do you have a better/simplier solution ?
Thanks

Also you would enable Authorize MIC APs against auth-list to avoid AP's fallback to the WiSM1. So, if I understand you, it would be enable on WISM1. This way AP's trying to fallback to the WISM1 will be refused and reconnect to the WISM2 that's right ?
Yes... this will prevent access point from joining the WiSM1... AP's that are already on WiSM1 will stay, it just prevents any AP's that has already been migrated to WiSM2 to fail to WiSM1.
How can I get the configuration from WiSM1 to the WiSM2 ?
Well you would backup your config and open it up in a text editor... then you would edit the file, by changing the hostname and ip address, etc. Make sure you have a trailing space at the end of each command that you change. This is important or else the config will not take. Also you will have to edit the password for the management since it is encrypted in the backup config. replace it with:
config mgmtuser password
Save the config and do a restore on the WiSM2 and verify that the setting are okay prior to moving all the ap's over. I would move one to test your wlans and make sure its fine before moving more.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

WiSM2 WLC 7.2 Maximum Allowed Clients under Global Parameters 802.11a/n b/g/n

Hello everyone,
Just loaded the 7.2.103.0 software onto the brand new WiSM2. Going throught the options and have found that under the global parameters for 802.11a/n, 802.11b/g/n radios is now the "Maximum Allowed Clients" option. The allowed setting is from 1 - 200 clients.
Does that mean only 200 clients will be allowed to associate to the WLC on that radio at a maximum?
Doesn't seems to make sense... I have the 500 AP license on this WiSM2... I know this option used to be an optional setting under a WLAN in previous releases.
Any ideas?
Regards,
Sasha.

Does that mean only 200 clients will be allowed to associate to the WLC on that radio at a maximum?
As what Scott has responded, this means 200 clients per WAP.
If you do exceed 200 clients per WAP (or whatever value you put in there) the clients will just get a nag and the system will let you in eventually.

WiSM2/WLC design

Hi experts,
We are in middle of deploying WiSM2s on our network, from a design point of view i am confused on where to position the WiSM2s. We have 2 DCs and from best practice architecture view WLCs should not be placed on the Data Centre segment, but it seems that is the only option i have.
DCs host 6509s, i am planning to host 1 WiSM in each DC, all clients will be on seperate subnet. Do you foresee any issues with this deployment or any security issues?
authentications are followed as per cisco recommendation, clients authenticated against AD through ACS so it is fairly secure. Will appreciate any advice.
Cheers
AP

Amar,
Since you are going to install the WISM2 you will be limited to where your chassis is physically installed. If we are operating under the assumption that all, or at least most, of the traffic sent to the WISM2 will eventually hit the data center I do not se a reason to move them. On the other hand if you have a lot of peer to peer wireless traffic such as voice calls and pages you may want to consider some HREAP configuration. Placement of the WISM2 will not have any affect on the authentication/encryption that you will use. Ideally when planning a new WLC/WISM(2) deployment I like to use all local mode APs with a WLC/WISM(2) at each site as well as a WLC in the DMZ to use as a mobility anchor. If you provide more specific details such as client type, traffic path, and number of clients per location I can help you with something more specific to your design.
Thanks,

Setting management interface WLC 7.4.121.0

Hello.
I have a problem setting Management interface IP in new controller 5508. I get the error "Error in setting management interface IP".I can not place a management controller IP.
Starting IPv6 Services: ok
Starting Config Sync Manager : ok
Starting Hotspot Services: ok
Starting PMIP Services: ok
Starting Portal Server Services: ok
Starting mDNS Services: ok
Starting Management Services:
Web Server: CLI: ok
Secure Web: Web Authentication Certificate not found (error). If you cannot access management interface via HTTPS please reconfigure Virtual Interface.
License Agent: ok
(Cisco Controller)
Welcome to the Cisco Wizard Configuration Tool
Use the '-' character to backup
Would you like to terminate autoinstall? [yes]: -
Invalid response
Would you like to terminate autoinstall? [yes]: no
System Name [Cisco_bf:dd:c4] (31 characters max):
AUTO-INSTALL: process terminated -- no configuration loaded
Enter Administrative User Name (24 characters max): admin
Enter Administrative Password (3 to 24 characters): ********
Re-enter Administrative Password : ********
Service Interface IP Address Configuration [static][DHCP]: none
Service Interface IP Address: 1.1.1.1
Service Interface Netmask: 255.255.255.0
Enable Link Aggregation (LAG) [yes][NO]: no
Management Interface IP Address: 192.168.10.1
Management Interface Netmask: 255.255.255.0
Management Interface Default Router: 192.168.10.10
Error in setting management interface IP
Management Interface IP Address: 10.10.10.1
Management Interface Netmask: 255.255.255.0
Management Interface Default Router: 10.10.10.100
Error in setting management interface IP
Management Interface IP Address:
Does anyone faced this issue?
Thanks.

Hi,
Try these:
1. With the WLC, Please set flow control(in SecureCRT or hperterminal) to none. Once the changes are made, CLI will start working as usual.
2. Another common reason can be related to the virtual interface configuration of the controller. In order to resolve this problem, remove the virtual interface and then re-generate it with this command:
WLC>config interface address virtual 1.1.1.1
Then, reboot the controller. After the controller is rebooted, re-generate the webauth certificate locally on the controller with this command:
WLC>config certificate generate webauth
In the output of this command, you should see this message: Web Authentication certificate has been generated.
Now, you should be able to access the secure web mode of the controller upon reboot.
3. Try to use some diff IP address for service interface don't use 1.1.1.1.
Regards
Dont forget to rate helpful posts

WLC restarting on its own.

Hi all,
We've got a pair of WiSMs installed in our Cat6K, running VSS.
From time to time, the primary WiSM will suddenly fail and secondary will take over.
Unfortunately when the secondary takes over, NO APs will associate with the WLC. What is the reason? And why would the WiSM just suddenly fail on its on?
Running version 7.4.121.0 for both, in AP SSO redundancy.
Switchover History[9]:
Previous Active = 172.24.x.x, Current Active = 172.24.x.x
Switchover Reason = Active controller failed, Switchover Time = Wed Jan 28 22:26:54 2015
Switchover History[10]:
Previous Active = 172.24.x.x, Current Active = 172.24.x.x
Switchover Reason = User initiated, Switchover Time = Wed Jan 28 22:35:45 2015
edit : I can verify that after the secondary WiSM takes over, the licenses also gets adopted by the secondary, but no APs will associate.

There are multiple BUGs which you can refer :
https://tools.cisco.com/bugsearch/bug/CSCuo94185
Symptom:
WiSM2 on code 7.4.121.0 in HA SSO crashes causing the controllers to constantly fail over and fail back between active and standby controllers.
Crash seen due to Task Name: nmspRxServerTask
System Stack
Frame 0: 0x10012c20 create_crash_dump+7156
Frame 1: 0x10011a18 create_crash_dump+2540
Frame 2: 0x10007ab8 sigsegv_handler+6168
Frame 3: 0x45d803b0 license_xos_thread_create+871837312
Frame 4: 0x11bdab48 MD5_Update+168
Frame 5: 0x11bae424 tls1_mac+340
Frame 6: 0x11baafb0 ssl3_read_bytes+1624
Frame 7: 0x11ba7f90 ssl3_read+120
Frame 8: 0x1029a638 doSSLRecvLoop+464
Frame 9: 0x1029aff0 NetReceiveLoop+424
Frame 10: 0x1029b3dc locpRxSocket+540
Frame 11: 0x10b0e858 osapiTaskAppKeySelfSet+304
Frame 12: 0x120292b0 license_xos_thread_create+2211200
Frame 13: 0x12089c4c license_xos_thread_create+2606876
Conditions:
WiSM2 in HA SSO on code 7.4.121.0
Workaround:
None.
Controller reboots and comes up on its own
Further Problem Description:
This is a hospital network
Issue was first noticed when customer tried to restart services on the primary MSE in the network (MSE in HA)
This caused a flood of error messages on the controller (error logs attached). It took about two hours for MSEs to come up and stabilize. Shortly after this the active controller crashed, failing over to standby. After some time, the standby WLC crashed failing back to active
Customer setup has 4 WiSM2's in HA SSO and crash has occured multiple times on two of the controller pairs.
https://tools.cisco.com/bugsearch/bug/CSCui35807

AP wont change primary WLC w/o re-boot.

Hi all!
I have som problem with a WiSM2-wlc running 7.3.101.0. We have APs that should be moved to an other WLC and we want to to it as smooth as possible. But when changing the primary WLC for an AP, the AP will not move to newly configured WLC. As for moving a AP to the WiSM2, its not a problem, they move to within minutes.
I have tried some different scenarios, move from and to:
WiSM2(7.3.101.0) -> WiSM2 (7.3.101.0)
WiSM2(7.3.101.0) -> WiSM (7.0.240.0)
and also tested with differnt AP-models, AP1142, AP2602 and AP3602, but same "problem" with all AP-models. I thinik that there is something wrong with this WLC, we have re-booted it but there is no differnce.
Anyone have a clue where to continue the trouble shooting?
Thanks!

You´re right! For the 2602 and 3602 I only have tested WiSM2->WiSM2
So what's the problem again?
WiSM2 are running different firmware than the WiSM1.
So when your 1140, 2600 and 3600 falls back from WiSM2 to WiSM1, only the 1140 and 3600 will go across. When the APs go across, they will download the firmware for WiSM1 and reboot.
Same holds true with the APs return back to the WiSM2.
Besides, what you are doing now is about to become obsolete due to High Availability, Stateful Switch Over (AP SSO) for WiSM2.

WLC AP failover

I'm doing a software and FUS upgrade on a set of 5508's in HA- mode (Primary and Standby) and do not want the AP's to fail over to another controller in the mobility group during the software upgrade, but I want them to during the FUS upgrade.
Do I just take the controller out of the mobility group to do this during the software upgrade, then put the controller back in the mobility group just before the FUS upgrade so the AP's will fail over?
I've heard that the AP's will still fail over to another controller on the network even if it's not in the mobility group.. is this true.

If I'm right, you are already running an HA SSO pair but with other WLC's mobility members in the same mobility group. If so, all the joined access-points will automatically receive the management IPv4 address of the other WLC's within the same group. This is not the case when other WLC's are in a different mobility group (and still configured in the mobility list of the HA SSO pair WLC).
There are also some other methods for the AP to learn about other WLC's:
- The configured primary, secondary and tertiary WLC on the AP itself
- Globally configured backup WLC
- If there is still no WLC to go to, the AP will go back to normal discovery process to find other WLC's.
You can verify which WLC's your access-point knows off on the access-point itself:
AP#show capwap client config
mwarName <- Name and IPv4 address of the configured primary WLC on the AP
mwarIPAddress 0.0.0.0
mwarName <- Name and IPv4 address of the configured secondary WLC on the AP
mwarIPAddress 0.0.0.0
mwarName <- Name and IPv4 address of the configured tertiary WLC on the AP
mwarIPAddress 0.0.0.0
<< >>
Configured Switch 1 Addr x.x.x.1 <- Currently joined WLC
Configured Switch 2 Addr x.x.x.2 <- The next WLC from the mobility list with in the same mobility group as the currently joined WLC
AP#show capwap client ha
primaryBackupWlcIp      0x0 <- IPv4 address and name of the first global backup WLC
primaryBackupWlcName
secondaryBackupWlcIp    0x0 <- IPv4 address and name of the secondary global backup WLC
secondaryBackupWlcName
So to make sure your access-points wont go to other controllers when you are upgrading you need to make sure they don't know about the other ones and the can't learn about them either (like layer 3 broadcast, DHCP option 43, DNS).
Depending on your infrastructure maybe something like an temporary ACL is less time consuming and less complex as well to get the same result in the end.

PI 2.1 and WLC 7.6 / MSE 7.5 code

Just got my PI 2.0 upgraded to 2.1
I was reading through the release notes and was wondering if PI 2.1 can be used with a 5508 running 7.6.120.0 code. Currently we are running 7.4.100.60 and haven't put any new code on due to PI requirements.
Same goes for our 3555 MSE: wondering if 7.6.120.0 code will work. Currently we are running 7.4.100.0 and are holding off upgrading due to PI requirements.
Any help is appreciated.
Thanks,
Dan

Hi,
I think answer can be found here:
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html#pgfId-148422
Prime Infrastructure 2.1 allows you to manage Cisco WLC Releases 7.5.102.0 and 7.6.x with the features of Cisco WLC 7.4.121.0 and earlier releases. Prime Infrastructure 2.1 does not support any features that are introduced in Cisco WLC Releases 7.5.102.0 and 7.6.x except the new access point platforms and the new mobility feature.
HTH
Pavel

WLC 5760 centralized mode Flexconnect support?

Hi all,
I am currently digging through the documentation about the 5760 WLC and converged access mode and found one particular information, which I need more clarification for.
This is the link
http://www.cisco.com/en/US/prod/collateral/wireless/ps6302/ps8322/ps12598/qa_c67-726507.html
And here the specific snippet:
Q. What deployment modes can the Cisco 5760 WLC and Cisco Catalyst 3850 support?
A. The Cisco 5760 WLC can operate in centralized mode (also known as local mode) as well as converged access mode, whereas the Cisco Catalyst 3850 operates in converged access mode. At this time, there is no support for office-extend access points, indoor or outdoor mesh, or FlexConnect access points on the Cisco 5760 WLC and Cisco Catalyst 3850.
Now my questions are:
Does this apply to the converged access mode only or also centralized mode?
Do 5508/WiSM2 WLCs still support APs in the specified modes even when using the new mobility architecture?
When is it planned to add support for the new platforms, if at all?
Hoping for some answers!
Regards,
Patrick

Hi Patrick,
Why not post your question here;
https://supportforums.cisco.com/thread/2220448
There's an open forum Converged Access Q&A session on the go direct with Cisco...
Richard

WISM2 7.2

We've recently recieved a couple of WISM2 WLCs and upgraded them to 7.2.110.0 since it increases throughput and maximim APs. I've now checked and each WISM2 has 2 10Gb interfaces and one port channel.
Am I wrong to expect both 10Gb interfaces to be within the port channel (like the WISM1 port channel had 4 1Gb interfaces in it)?
Both 10Gb ports in each WISM2 have traffic going over them with the port not in the port channel having slightly less traffic.

#Initial System Configuration with Sup 720
Complete these steps:
    Upgrade the Cat 65XX with the Cisco IOS® Software Release 12.2(33)SXJ2 provided on Cisco.com.
    Note: If upgrading from WiSM-2 1DP to WiSM-2 2 DP, first you need to upgrade the Cat65XX to 12.2(33)SXJ2 before upgrading the WiSM2 to the 7.2.103.0 code to enable DP2. Also, vice versa if downgrading the Cat 65XX to below 12.2(33)SXJ2 you need to downgrade the WiSM-2 2DP to a WiSM-2 1DP image.
    Only after upgrading the Catalyst IOS software the system will recognize the WiSM-2 2DP blade.
#Initial System Configuration with Sup 2T
Complete these steps:
    Upgrade the Cat 65XX with the Cisco IOS Software Release 15.0(1)SY1 provided on Cisco.com.
    Note: If upgrading from WiSM-2 1DP to WiSM-2 2 DP, first you need to upgrade the Cat65XX to 15.0(1)SY1 before you upgrade the WiSM2 to the 7.2.103.0 code to enable DP2. Also, vice versa if downgrading the Cat 65XX to earlier than 15.0(1)SY1 you need to downgrade the WiSM-2 2DP to a WiSM-2 1DP image.
    Only after upgrading the Catalyst IOS software the system will recognize the WiSM-2 2DP blade.

Change prim and sec Controller IP from WISM or Prime

Hi all,
we have a Cisco Prime 2.2.0 and a redundant (SSO) WISM2 pair (8.0.110.0) and about 700 APs.
After conversion to redundancy of WISMs and because of different local configurations of some APs we have to change the IP
of the primary and secondary controller of nearly all 700 APs.
Is it possible to change the addresses of all APs from the WISM or Prime web interface ?
It would be very hard to configure each AP individually.
Thank you.

Hello to all,
Did you find at the end what was the cause which generate the problem and the messages???
The WLC or something on the network and hte messages were the consequence???
Many Thanks for a feedback
Omar

Anyone got the AIR-CT2504-HA-K9 to work on N+1 Redundancy ?

Hi Guys,
Seems like the new Part #AIR-CT2504-HA-K9 needs some kinda licensing...to work... otherwise the redundancy is same as it was ealier with mobility groups.
The documentation seems to be wrong in the case of 2504, i cannot find the redundancy button in the Wireless tab too, When i apply the Evaluation license redundancy is working.... did anyone else face the same Issue ?
Regards,
Vinu

i cannot find the redundancy button in the Wireless tab too
You mean AP SSO?
WLC 2500 will not support this feature.

Java.text.ParseException: Unparseable date: "2008-12-16 00:00:00"

Dear All WebLogic Guru,
Need your help about the error in our WebLogic Apps Server. Below is the related logs. Hope to hear from you soon.
========
Log snippet:
========
[15:48:02 ] [INFO] [NumberFormatException in TimesheetAddHandler:] null [delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAddHandler.perform(TimesheetOperatorAddHandler.java:77)]
java.text.ParseException: Unparseable date: "2008-12-16 00:00:00"
at java.text.DateFormat.parse(DateFormat.java:337)
at ejb.sessionBeans.gbms.bulkcrg.timesheet.TimesheetOperatorEJB.getOpsDttm(TimesheetOperatorEJB.java:1647)
at ejb.sessionBeans.gbms.bulkcrg.timesheet.TimesheetOperator_vn72b_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at ejb.sessionBeans.gbms.bulkcrg.timesheet.TimesheetOperator_vn72b_EOImpl.getOpsDttm(Unknown Source)
at delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAddHandler.perform(TimesheetOperatorAddHandler.java:383)
at delegate.RequestManager.perform(RequestManager.java:85)
at delegate.FrontController.processRequest(FrontController.java:241)
at delegate.FrontController.doPost(FrontController.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at sg.com.jp.framework.sso.SingleSignOnFilter.doFilter(SingleSignOnFilter.java:121)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at sg.com.jp.util.xss.XssFilter.doFilter(XssFilter.java:57)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:153)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
[15:48:02 ] [INFO] [ScreenManager] Screen ID [TimesheetOperatorViewSvlt] mapped to [JSP/gbms/bulkcrg/timesheet/TimesheetOP_details.jsp] [delegate.ScreenManager.nextScreen(ScreenManager.java:60)]
[15:48:02 ] [INFO] Next Screen is : /JRPA(or ServletContext@27549577[app:47jrpa module:JRPA path:/JRPA spec-version:null],WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 Oracle WebLogic Server Module Dependencies 10.3 Thu Oct 28 06:03:12 PDT 2010 Oracle WebLogic Server on JRockit Virtual Edition Module Dependencies 10.3 Thu Sep 23 15:02:15 PDT 2010 )/JSP/gbms/bulkcrg/timesheet/TimesheetOP_details.jsp [delegate.FrontController.processRequest(FrontController.java:322)]
[15:48:02 ] [DEBUG] 2nd funcName in doFilter = TimesheetOP_details [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:83)]
[15:48:02 ] [DEBUG] #########new admin framework ########## Function Code = [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:92)]
[15:48:02 ] [DEBUG] Function Code = [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:108)]
Status :S
[15:48:03 ] [DEBUG] Contains Function: true TimesheetOperatorSuperAmend [tags.ACLTag.doAfterBody(ACLTag.java:132)]
[15:48:03 ] [DEBUG] Contains Function: true TimesheetOperatorSuperDelete [tags.ACLTag.doAfterBody(ACLTag.java:132)]
[15:48:03 ] [DEBUG] Contains Function: true TimesheetOperatorClose [tags.ACLTag.doAfterBody(ACLTag.java:132)]
[15:48:31 ] [DEBUG] 2nd funcName in doFilter = TimesheetOperatorSuperAmend [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:83)]
[15:48:31 ] [DEBUG] Function Code = F27052 [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:108)]
[15:48:31 ] [DEBUG] Logged In?: true [delegate.helper.System.AuthenticationHandler.valid(AuthenticationHandler.java:571)]
[15:48:31 ] [INFO] [RequestManager] Request ID [TimesheetOperatorSuperAmend] mapped to [delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler] [delegate.RequestManager.perform(RequestManager.java:77)]
[15:48:31 ] [INFO] [RequestManager] delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler Created [delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler@66d4bf] [delegate.RequestManager.perform(RequestManager.java:82)]
[15:48:31 ] [INFO] performing request delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler@66d4bf [delegate.RequestManager.perform(RequestManager.java:84)]
[15:48:31 ] [INFO] [NumberFormatException in TimesheetAddHandler:] null [delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler.perform(TimesheetOperatorAmendHandler.java:96)]
[15:48:31 ] [ERROR] java.lang.StringIndexOutOfBoundsException: String index out of range: 2
at java.lang.String.substring(String.java:1934)
at delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler.perform(TimesheetOperatorAmendHandler.java:110)
at delegate.RequestManager.perform(RequestManager.java:85)
at delegate.FrontController.processRequest(FrontController.java:241)
at delegate.FrontController.doPost(FrontController.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at sg.com.jp.framework.sso.SingleSignOnFilter.doFilter(SingleSignOnFilter.java:121)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at sg.com.jp.util.xss.XssFilter.doFilter(XssFilter.java:57)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:153)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
[delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler.perform(TimesheetOperatorAmendHandler.java:526)]
[15:48:31 ] [INFO] errorMessage ::: There are some error with your request. Please contact administrator if problem persists. [delegate.FrontController.processRequest(FrontController.java:311)]
=================
Application Server Specs:
=================
OS: Solaris10 x86
cat /etc/release
Oracle Solaris 10 9/10 s10x_u9wos_14a X86
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Assembled 11 August 2010
RAM: 8GB
HDD: 70GB
Apps Server: WebLogic Server Version: 10.3.4.0
Thank you and have a blessed day.
Best regards,
Albert

Hi,
Try this
The reason for this error is that the time format entered is not correct. It should be a date and 24-hour format expressed as mm/dd/yy hh:mm:ss. For example: 07/15/10 14:30:00.
The WebLogic Server 11g documentation gives instructions for Date/Time format. For details, please refer to
http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/pagehelp/Diagnosticsdiagnosticsviewmetricslogtabletitle.html
Solution
However, since you cannot open the Domain Log page again because the console hangs or reports a "Redirect Loop" error, you cannot modify this wrong time format on the console. To resolve this issue, please follow these steps:
Stop WebLogic Server.
Go to directory <Domain>/servers/<Server_Name>/data/console
Either open ConsolePreferences.xml and modify the value of startrange (and/or endrange) to a correctly formatted time, e.g. 07/15/10 14:30:00
OR
Delete ConsolePreferences.xml entirely.
Start Weblogic Server again.
Regards,
Kal

Cisco AP1142N won't join controller

Hi
When upgrading one of our WISM controller cards a problem occurred with some AP1142N.
The can’t join controller with 7.6.120.0, upgrading was from 7.4.121.0
When CLI into the AP I got this messages:
Reboot and tries to connect to the WISM2 with 7.6.120.0, but it fails.
Then tries to connect to another WISM2 with 7.4.121.0 and this work
But then the image on the AP is not correct (have a 7.6.120.0 image)
Downgrading AP to 7.4.121.0 image
Reboot and are back to number 1.
*Mar 1 00:01:09.564: %CAPWAP-3-ERRORLOG: Selected MWAR 'JKP-WISM-02-I '(index 0).
*Mar 1 00:01:09.564: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Sep 10 11:25:00.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.16.25 peer_port: 5246
*Sep 10 11:25:29.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!
Translating "CISCO-CAPWAP-CONTROLLER.net.yyyy.se"...domain server (xxx.xxx.xxx.xxx) [OK]
*Mar 1 00:00:59.550: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar 1 00:01:09.564: %CAPWAP-3-ERRORLOG: Selected MWAR 'JKP-WISM-02-I '(index 0).
*Mar 1 00:01:09.564: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Sep 10 11:25:00.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.16.25 peer_port: 5246
*Sep 10 11:25:29.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!
*Sep 10 11:25:59.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.17.16.25:5246
*Sep 10 11:26:00.000: %CAPWAP-3-ERRORLOG: Selected MWAR 'JKP-WISM-02-I (index 0).
*Sep 10 11:26:00.000: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Sep 10 11:25:00.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.16.25 peer_port: 5246
*Sep 10 11:25:30.000: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!
examining image...
extracting info (292 bytes)
Image info:
    Version Suffix: k9w8-.124-23c.JA8
    Image Name: c1140-k9w8-mx.124-23c.JA8
    Version Directory: c1140-k9w8-mx.124-23c.JA8
    Ios Image Size: 4915712
    Total Image Size: 5110272
    Image Feature: WIRELESS LAN|LWAPP
    Image Family: C1140
    Wireless Switch Management Version: 7.0.250.0
Extracting files...
c1140-k9w8-mx.124-23c.JA8/ (directory) 0 (bytes)
extracting c1140-k9w8-mx.124-23c.JA8/T5.bin (23836 bytes)
*Sep 10 11
extracting c1140-k9w8-mx.124-23c.JA8/8001.img (174932 bytes):25:59.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.17.16.25:5246

With a WISM, you have by definition an etherchannel between your controller & APs. Try setting the load balancing algorithm on the switch housing the WISM to src-dst-mac before connecting the AP. There is/was an issue that shows itself rarely where other load balancing mechanisms interfere with an AP's initial join to a controller. The problem declined significantly over the years, but you may be running into it.
Once the AP joins, you can reset your load balancing and you shouldn't have the problem even if the AP reboots later. It usually impacts APs that have never joined your controller. Don't know why. Since this was an upgrade it may not be your problem, but it won't hurt to try.

AP SSO WISM2 WLC 7.4.121

Similar Messages

Maybe you are looking for