Roaming issue

Users complain that wireless device would lost wireless network connection when they moved from one AP coverage to another AP coverage.  They have to reconnect to the wireless network again.
In our wireless environment, all APs are connecting to a single loacl controller which anchor to two remote controllers.  WLC 5508 with 7.2.11.3.
Thanks,

Configuring Client Roaming
The Cisco UWN Solution supports seamless client roaming across lightweight access points managed by the same controller, between controllers in the same mobility group on the same subnet, and across controllers in the same mobility group on different subnets. Also, in controller software release 4.1 or later releases, client roaming with multicast packets is supported.
You can adjust the default RF settings (RSSI, hysteresis, scan threshold, and transition time) to fine-tune the operation of client roaming using the controller GUI or CLI.
CCX Layer 2 Client Roaming
The controller supports five CCX Layer 2 client roaming enhancements:
•Access point assisted roaming—This feature helps clients save scanning time. When a CCXv2 client associates to an access point, it sends an information packet to the new access point listing the characteristics of its previous access point. Roaming time decreases when the client recognizes and uses an access point list built by compiling all previous access points to which each client was associated and sent (unicast) to the client immediately after association. The access point list contains the channels, BSSIDs of neighbor access points that support the client's current SSID(s), and time elapsed since disassociation.
• Enhanced neighbor list—This feature focuses on improving a CCXv4 client's roam experience and network edge performance, especially when servicing voice applications. The access point provides its associated client information about its neighbors using a neighbor-list update unicast message.
• Enhanced neighbor list request (E2E)—The End-2-End specification is a Cisco and Intel joint program that defines new protocols and interfaces to improve the overall voice and roaming experience. It applies only to Intel clients in a CCX environment. Specifically, it enables Intel clients to request a neighbor list at will. When this occurs, the access point forwards the request to the controller. The controller receives the request and replies with the current CCX roaming sublist of neighbors for the access point to which the client is associated.
For more information you can refer the following link-
http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70ccfg.html#wp1098538

Similar Messages

  • L2 Roaming issue with Avaya wireless phone on WISM -V6.0.196.0

    Hello Friends,
    I am facing Layer2 roaming issue with Avaya Wirless phone 3620 which are configured WPA / Pre-shared key auth with a SSID1 and face a cut or delay in the voice.
    But when i use Cisco Wireless phones and try to roam between one LWAP to other i dont face a cut or delay in the vocie which are
    Configured with 802.1x +CCKM auth .
    Then i configured new SSID 3 with 802.1x+CCKM settings for  the new Avaya wireless module 3631 , but still face cut and delay while doing Layer 2 roaming.
    While i was using these AP in WDS mode i never faced this Layer 2 roaming issue with Avaya wireless phones.
    In  current WISM all the LWAPs are supporting properly to the Cisco phone and Wirelss laptop clients.
    I request you to please let me know how do i proceed further to solve the issue and please let me know if anybugs or incompatibilty for WISM with Avaya wireless phones.
    Appreciate your response.
    Regards,
    KA.

    Hello ,
    Can any body please respond to my above Query.
    Thanks,
    KA.

  • Client roaming issue

    I am trying to track down some performance issues on my wireless network, and hope someone out there will help educate me!  My environment:
    Access Points are all 1231, 1242, and 1252
    The 802.11g radios are active
    All APs are configured to use Channel 4
    WEP security (I know, I know ...)
    Clients are either laptop users (mostly Dells) or Intermec vehicle-mounted terminals with Prism NICs
    Clients are VERY active as far as moving around the building
    Here is what I *think* is happening:
    The clients don't "roam" as quickly as I think they should - in other words, they remain associated to the active AP too long.  Their signal gets too low before they pick up another AP.
    I wonder if I need to adjust the data rates on the APs (like maybe disable the lowest ones).  For example, if I disable the 1.0, 2, and 5.5 Mb/sec rates, does that mean that a client will look for another AP when the "speed" drops below 6 Mb/sec?  If so, then by disabling the lowest data rates, the client would be forced to find another AP before the data rates drops to nothing, right?
    I also don't understand the power ratings - I've just left them at the default settings - does this affect performance as well?
    Thanks in advance ...

    Hi Susan,
    How are you doing today ... Sounds like you have a little mess on your hands. Lets sort through some of these issues. It also sounds like you are open to feedback, that is always great to hear!
    First. I need to point out your channel selection and this could be a the likly cause for your roaming issue. Follow along and let me explain why.. There is a BIG miss understanding when doing wifi that folks think that all the AP needs to be on the same channel. In fact, you should only use channels 1,6 and 11. When you use the same channel off channels like 4 you cause interference.
    Let me explain why with a real world example. Think back to the late 80s when cordless phones were hitting the market. Do you remember when you would pick up the phone and you would hear your neighbor's conversation? Well that is becuase you were on the same channel you shared the same freq. Now what happens when 4 people (on 2 calls) try to all talk at the same time!? It becomes a mess, right. "Can you say that again", "I didnt hear you", "What was that !?".
    Well the same holds true with WiFi. If all the aps are on the same channel you have one big cordless phone call going, for exmaple.So the first thing we need to do is correct the channel issue before you do anything else. It WiFi channel uses 22 MHz of RF. Thus what you can only use 1,6,11. You also want to make sure you dont put like channels close together. For example, don't line up a hallway with all channel 1... here is some reading
    http://www.cisco.com/en/US/docs/wireless/technology/channel/deployment/guide/Channel.html

  • Layer 3 roaming issue

    Hi all,
    i have two wireless networks with two subnet (see the attached drawing) , all controllers run v4.2 access points type is 1020 .
    the first network in hall 1 have 4 wlc in subnet 172.16.40.X  , the security is WEP key for wireless phone
    the second network in hall two have one WiSM in subnet 172.26.40.Y the security is WEP key for wireless phone also
    all controllers and WiSM in same Mobility group .
    the issue is  ,when   wireless phone roaming from hall one to hall two or from hall two to one it dropped the connection and not working
    please advice

    Examples :
    WLC1 has management as 192.168.1.2
    WLC2 has management as 192.168.1.3
    WLC1 has the SSID "employees" linked to interface "emp_int" which has ip 192.168.50.2
    WLC2 has the SSID "employees" linked to interface "employee_int" which has ip 192.168.80.2
    In this case, we have layer 3 roaming. Meaning that normally the client would need to change its ip from 192.168.50.x to 192.168.80.x but thanks to mobility anchoring mechanism, the WLC2 forwards all traffic back to WLC1 so that the client can keep its ip address in 192.168.50.x
    If the situation was that both employee interfaces were in the 192.168.50.x on both WLCs, then we would have layer 2 roaming. Meaning the client entry is simply moved to WLC2 and WLC2 handles all the traffic. WLC1 has nothing to do anymore with this client.
    conclusion : the ip addresses of the management interfaces don't matter to decide if it's layer 2 or 3 roaming, it's the ip of the dynamic interface of SSID which matters
    Nicolas
    ===
    Don't forget to rate anwers that you find useful

  • IP Phone 7921 / 7925 roaming issues after WLC upgrade from Version 7.2 to 7.3 and / or 7.4

    Hi,
    We have a customer which is using a Cisco WLC 5508 and 3502I APs. As he used the 7.2.103 release, There were no issues with VoWLAN. Now he needed new APs and ordered the 2602I. To use them he needed to upgrade the WLC to a 7.3 or later release. After the upgrade, he now encounters problems while roaming with the phones. The phones were tested with FW 1.4.1, 1.4.2 and 1.4.3.
    Configuration is set according to wireless voice design guides (VoWLAN DG 4.1, 7921 Deployment Guide). A Cisco TAC is also in progress, but they seem to be uncertain whether it is a wireless or CUCM issue, but I don't see a reason why it should be the CUCM when the only thing changed is the WLC Software Version.
    Is there anybody who is aware of such issues and can offer help?
    Thank you in advance.
    Best regards,
    Patrick

    Hi,
    we had a TAC ticket open with this customer and after some time, the TAC gave us the advise to use this release and the problems are now solved.
    So for others having the same issue: If you only need to support the 2600 APs, stay with the latest 7.2 release as there are some issues with the 7.3 and 7.4 release. If the customer requires HA, AVC or any of the new features + wireless voice, be very careful as it seems that the newer releases are having problems with that. I hope that Cisco will fix this very soon.
    regards,
    Patrick

  • 802.1X authentication and roaming issues

    Hi there,
    I have installed about 2 days ago one Cisco WCS 2504 and 11 APs. Everything is doing well regarding to WEP authentication. But I have a Radius Server that is alson running with some issues on wireless:
    - Unless I open network settings and click connect on that config I cannot obtain a valid IP Address;
    - Roaming is not working also;
    FYI the certificate (on radius) has expired
    TY

    Not all these are radius issues
    - WPA2 Wlan still ok (144Mbit), but dont know when roaming works (how can I know/change these settings?);
    Look at the client adapter as there is usually a roaming aggressiveness option on these devices. Play around with that.
    - Radius autenticated with 802.11 Data Encryption on 40 bits Key size connects always at 54Mbps (g) and auto authenticate but dont know when roaming works (how can I know/change these settings?);
    802.11n only supports open authentication or WPA2/AES. WEP is not supported so that why you get up to 54mbps.
    - Radius with 802.11 Data Encryption with none key size, doesnt authenticate connects 144Mbit but doesnt acquire IP Address
    You have a configuration issue either in the WLC or the switch.
    Sent from Cisco Technical Support iPhone App

  • Intel 3945 roaming issues

    I have some 1242 AP's set up with Cisco Fast roaming. My 3945 clients roam fine, but after a few seconds, they lose their IP address. If I have a constant ping going, my ping will drop for about 3 seconds, then replys will go for about 4 seconds. It will continue to do this about three times until stabilizing and then it works great until roaming again. Anyone have any ideas? TAC blames Intel. Intel says to work with Dell. Dell has no clue. Any help would be appreciated.

    Hi Allan,
    Have you tried tweaking Roaming Aggressiveness in the Intel PROSet client utility? You may also want to try turning off Auto-RF just to see if it makes any difference.
    I had costumers which had problems with the ProSet Utility. We deinstlled ad used the Windows XP Wireless Zero configuration.
    The Intel Wireless NIC have actual some issues with the Cisco environment.
    Some examples from the forum:
    http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd73e2f
    http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=Security%20and%20Network%20Management&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.ee95e05
    Please check if the wireless clients you use are specified in the "Cisco Compatible Client Devices" list:
    http://www.cisco.com/web/partners/pr46/pr147/partners_pgm_partners_0900aecd800a7907.html
    The mentioned versions can be found here:
    http://www.cisco.com/warp/public/765/ccx/versions_and_features.shtml
    Best regards,
    Frank

  • Roaming issue - Layer 2 switch CAM table updates

    Hi,
    We have a setup with 2 WLC2500  and 10 1041 LAP distributed on various sites (3 or 2 per site), using HREAP (local switching, central auth) and AP Groups, for grouping the APs on each site.
    On one site everything works fine, roaming was correctly done, and client could communicate inmediatly after the roaming process, but on other site we found that if we roam between the 2 APs found out that even the client get conected to the AP it takes about 300 second (5 minutes) for the client to get traffic forwarding.
    Here i´m attaching the debug session for client and l2roam:
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d Association received from mobile on AP 50:06:04:2a:4a:10
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d 192.33.1.251 RUN (20) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1626)
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d Applying site-specific IPv6 override for station 9c:02:98:8e:c6:5d - vapId 3, site 'PRUVIA', interface 'management'
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d Applying IPv6 Interface Policy for station 9c:02:98:8e:c6:5d - vlan 0, interface id 0, interface 'management'
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d Applying site-specific override for station 9c:02:98:8e:c6:5d - vapId 3, site 'PRUVIA', interface 'management'
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d 192.33.1.251 RUN (20) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1626)
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d STA - rates (8): 2 4 11 22 164 48 72 108 12 18 24 96 0 0 0 0
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d STA - rates (12): 2 4 11 22 164 48 72 108 12 18 24 96 0 0 0 0
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d Processing WPA IE type 221, length 22 for mobile 9c:02:98:8e:c6:5d
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d apfMsRunStateDec
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d apfMs1xStateDec
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d 192.33.1.251 RUN (20) Change state to START (0) last state RUN (20)
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d 192.33.1.251 START (0) Initializing policy
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d 192.33.1.251 START (0) Change state to AUTHCHECK (2) last state RUN (20)
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d 192.33.1.251 AUTHCHECK (2) Change state to 8021X_REQD (3) last state RUN (20)
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d 192.33.1.251 8021X_REQD (3) DHCP required on AP 50:06:04:2a:4a:10 vapId 3 apVapId 1for this client
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d Not Using WMM Compliance code qosCap 00
    *apfMsConnTask_2: Jun 13 11:27:59.198: 9c:02:98:8e:c6:5d 192.33.1.251 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 50:06:04:2a:4a:10 vapId 3 apVapId 1
    *apfMsConnTask_2: Jun 13 11:27:59.199: 9c:02:98:8e:c6:5d apfPemAddUser2 (apf_policy.c:223) Changing state for mobile 9c:02:98:8e:c6:5d on AP 50:06:04:2a:4a:10 from Associated to Associated
    *apfMsConnTask_2: Jun 13 11:27:59.199: 9c:02:98:8e:c6:5d Scheduling deletion of Mobile Station:  (callerId: 49) in 1800 seconds
    *apfMsConnTask_2: Jun 13 11:27:59.199: 9c:02:98:8e:c6:5d Sending Assoc Response to station on BSSID 50:06:04:2a:4a:10 (status 0) ApVapId 1 Slot 0
    *apfMsConnTask_2: Jun 13 11:27:59.199: 9c:02:98:8e:c6:5d apfProcessAssocReq (apf_80211.c:5237) Changing state for mobile 9c:02:98:8e:c6:5d on AP 50:06:04:2a:4a:10 from Associated to Associated
    *dot1xMsgTask: Jun 13 11:27:59.247: 9c:02:98:8e:c6:5d Creating a PKC PMKID Cache entry for station 9c:02:98:8e:c6:5d (RSN 0)
    *dot1xMsgTask: Jun 13 11:27:59.247: 9c:02:98:8e:c6:5d Initiating WPA PSK to mobile 9c:02:98:8e:c6:5d
    *dot1xMsgTask: Jun 13 11:27:59.247: 9c:02:98:8e:c6:5d dot1x - moving mobile 9c:02:98:8e:c6:5d into Force Auth state
    *dot1xMsgTask: Jun 13 11:27:59.247: 9c:02:98:8e:c6:5d Skipping EAP-Success to mobile 9c:02:98:8e:c6:5d
    *dot1xMsgTask: Jun 13 11:27:59.247: 9c:02:98:8e:c6:5d Starting key exchange to mobile 9c:02:98:8e:c6:5d, data packets will be dropped
    *dot1xMsgTask: Jun 13 11:27:59.247: 9c:02:98:8e:c6:5d Sending EAPOL-Key Message to mobile 9c:02:98:8e:c6:5d
       state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.316: 9c:02:98:8e:c6:5d Received EAPOL-Key from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.316: 9c:02:98:8e:c6:5d Received EAPOL-key in PTK_START state (message 2) from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.316: 9c:02:98:8e:c6:5d Stopping retransmission timer for mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.317: 9c:02:98:8e:c6:5d Sending EAPOL-Key Message to mobile 9c:02:98:8e:c6:5d
       state PTKINITNEGOTIATING (message 3), replay counter 00.00.00.00.00.00.00.01
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d Received EAPOL-Key from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d Received EAPOL-key in PTKINITNEGOTIATING state (message 4) from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d apfMs1xStateInc
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d 192.33.1.251 8021X_REQD (3) Change state to L2AUTHCOMPLETE (4) last state RUN (20)
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d 192.33.1.251 L2AUTHCOMPLETE (4) DHCP required on AP 50:06:04:2a:4a:10 vapId 3 apVapId 1for this client
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d Not Using WMM Compliance code qosCap 00
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d 192.33.1.251 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 50:06:04:2a:4a:10 vapId 3 apVapId 1
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d apfMsRunStateInc
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d 192.33.1.251 L2AUTHCOMPLETE (4) Change state to RUN (20) last state RUN (20)
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d Mobile 9c:02:98:8e:c6:5d associated
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d 192.33.1.251 RUN (20) Reached PLUMBFASTPATH: from line 4918
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d Stopping retransmission timer for mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d Key exchange done, data packets from mobile 9c:02:98:8e:c6:5d should be forwarded shortly
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.375: 9c:02:98:8e:c6:5d Sending EAPOL-Key Message to mobile 9c:02:98:8e:c6:5d
       state PTKINITDONE (message 5 - group), replay counter 00.00.00.00.00.00.00.02
    *ccxL2RoamTask: Jun 13 11:27:59.376: 9c:02:98:8e:c6:5d Mobile 9c:02:98:8e:c6:5d has unsupported CCX version 0 in [l2roamProcessClientAssociation]
    *spamApTask1: Jun 13 11:27:59.418: 9c:02:98:8e:c6:5d Sent EAPOL-Key M5 for mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.486: 9c:02:98:8e:c6:5d Received EAPOL-Key from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.486: 9c:02:98:8e:c6:5d Received EAPOL-key in REKEYNEGOTIATING state (message 6) from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:27:59.486: 9c:02:98:8e:c6:5d Stopping retransmission timer for mobile 9c:02:98:8e:c6:5d
    *ccxL2RoamTask: Jun 13 11:28:16.823: Neighbor List for LRAD 50:06:04:2a:db:80,  Slot 1 not found in [l2roamGetNeighborListForSlot].
    *ccxL2RoamTask: Jun 13 11:28:16.823: 00000000: 00 36 33 81 84 a6 c8 ac  d7 71 50 06 04 2a db 80  .63......qP..*..
    *ccxL2RoamTask: Jun 13 11:28:16.823: 00000010: 28 11 50 06 04 2a db 80  0b 00 06 01 06 ab 11 11  (.P..*..........
    *ccxL2RoamTask: Jun 13 11:28:16.823: 00000020: 03 b8 02 28 11 50 06 04  2a 4a 10 01 00 07 01 06  ...(.P..*J......
    *ccxL2RoamTask: Jun 13 11:28:16.823: 00000030: ab 10 11 03 b8 02                                 ......
    *ccxL2RoamTask: Jun 13 11:28:47.441: Neighbor List for LRAD 50:06:04:2a:e0:40,  Slot 1 not found in [l2roamGetNeighborListForSlot].
    *ccxL2RoamTask: Jun 13 11:28:47.442: 00000000: 00 49 33 81 00 23 14 84  0d 64 50 06 04 2a e0 40  .I3..#...dP..*.@
    *ccxL2RoamTask: Jun 13 11:28:47.442: 00000010: 28 11 50 06 04 2a e0 40  0b 00 06 01 06 ab 11 11  (.P..*.@........
    *ccxL2RoamTask: Jun 13 11:28:47.442: 00000020: 03 b8 02 28 11 50 06 04  2a de 70 01 00 07 01 06  ...(.P..*.p.....
    *ccxL2RoamTask: Jun 13 11:28:47.442: 00000030: ab 10 11 03 b8 02 28 11  50 06 04 2a 47 20 06 00  ......(.P..*G...
    *ccxL2RoamTask: Jun 13 11:28:47.442: 00000040: 07 01 06 ab 10 11 03 b8  02                       .........
    *ccxL2RoamTask: Jun 13 11:29:27.832: Neighbor List for LRAD 50:06:04:2a:db:80,  Slot 1 not found in [l2roamGetNeighborListForSlot].
    *ccxL2RoamTask: Jun 13 11:29:27.832: 00000000: 00 36 33 81 84 a6 c8 ac  d7 71 50 06 04 2a db 80  .63......qP..*..
    *ccxL2RoamTask: Jun 13 11:29:27.832: 00000010: 28 11 50 06 04 2a db 80  0b 00 06 01 06 ab 11 11  (.P..*..........
    *ccxL2RoamTask: Jun 13 11:29:27.832: 00000020: 03 b8 02 28 11 50 06 04  2a 4a 10 01 00 07 01 06  ...(.P..*J......
    *ccxL2RoamTask: Jun 13 11:29:27.832: 00000030: ab 10 11 03 b8 02                                 ......
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d Reassociation received from mobile on AP 50:06:04:2a:db:80
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d 192.33.1.251 RUN (20) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1626)
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d Applying site-specific IPv6 override for station 9c:02:98:8e:c6:5d - vapId 3, site 'PRUVIA', interface 'management'
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d Applying IPv6 Interface Policy for station 9c:02:98:8e:c6:5d - vlan 0, interface id 0, interface 'management'
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d Applying site-specific override for station 9c:02:98:8e:c6:5d - vapId 3, site 'PRUVIA', interface 'management'
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d 192.33.1.251 RUN (20) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1626)
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d STA - rates (8): 2 4 11 22 164 48 72 108 12 18 24 96 0 0 0 0
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d STA - rates (12): 2 4 11 22 164 48 72 108 12 18 24 96 0 0 0 0
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d Processing WPA IE type 221, length 22 for mobile 9c:02:98:8e:c6:5d
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d 192.33.1.251 RUN (20) Deleted mobile LWAPP rule on AP [50:06:04:2a:4a:10]
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d Updated location for station old AP 50:06:04:2a:4a:10-0, new AP 50:06:04:2a:db:80-0
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d apfMsRunStateDec
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d apfMs1xStateDec
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d 192.33.1.251 RUN (20) Change state to START (0) last state RUN (20)
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d 192.33.1.251 START (0) Initializing policy
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d 192.33.1.251 START (0) Change state to AUTHCHECK (2) last state RUN (20)
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d 192.33.1.251 AUTHCHECK (2) Change state to 8021X_REQD (3) last state RUN (20)
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d 192.33.1.251 8021X_REQD (3) DHCP required on AP 50:06:04:2a:db:80 vapId 3 apVapId 1for this client
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d Not Using WMM Compliance code qosCap 00
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d 192.33.1.251 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 50:06:04:2a:db:80 vapId 3 apVapId 1
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d apfPemAddUser2 (apf_policy.c:223) Changing state for mobile 9c:02:98:8e:c6:5d on AP 50:06:04:2a:db:80 from Associated to Associated
    *apfMsConnTask_3: Jun 13 11:29:32.375: 9c:02:98:8e:c6:5d Scheduling deletion of Mobile Station:  (callerId: 49) in 1800 seconds
    *apfMsConnTask_3: Jun 13 11:29:32.376: 9c:02:98:8e:c6:5d Sending Assoc Response to station on BSSID 50:06:04:2a:db:80 (status 0) ApVapId 1 Slot 0
    *apfMsConnTask_3: Jun 13 11:29:32.376: 9c:02:98:8e:c6:5d apfProcessAssocReq (apf_80211.c:5237) Changing state for mobile 9c:02:98:8e:c6:5d on AP 50:06:04:2a:db:80 from Associated to Associated
    *apfMsConnTask_3: Jun 13 11:29:32.409: 9c:02:98:8e:c6:5d Updating AID for REAP AP Client 50:06:04:2a:db:80 - AID ===> 2
    *dot1xMsgTask: Jun 13 11:29:32.418: 9c:02:98:8e:c6:5d Creating a PKC PMKID Cache entry for station 9c:02:98:8e:c6:5d (RSN 0)
    *dot1xMsgTask: Jun 13 11:29:32.418: 9c:02:98:8e:c6:5d Initiating WPA PSK to mobile 9c:02:98:8e:c6:5d
    *dot1xMsgTask: Jun 13 11:29:32.418: 9c:02:98:8e:c6:5d dot1x - moving mobile 9c:02:98:8e:c6:5d into Force Auth state
    *dot1xMsgTask: Jun 13 11:29:32.419: 9c:02:98:8e:c6:5d Skipping EAP-Success to mobile 9c:02:98:8e:c6:5d
    *dot1xMsgTask: Jun 13 11:29:32.419: 9c:02:98:8e:c6:5d Starting key exchange to mobile 9c:02:98:8e:c6:5d, data packets will be dropped
    *dot1xMsgTask: Jun 13 11:29:32.419: 9c:02:98:8e:c6:5d Sending EAPOL-Key Message to mobile 9c:02:98:8e:c6:5d
       state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.475: 9c:02:98:8e:c6:5d Received EAPOL-Key from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.475: 9c:02:98:8e:c6:5d Received EAPOL-key in PTK_START state (message 2) from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.475: 9c:02:98:8e:c6:5d Stopping retransmission timer for mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.475: 9c:02:98:8e:c6:5d Sending EAPOL-Key Message to mobile 9c:02:98:8e:c6:5d
       state PTKINITNEGOTIATING (message 3), replay counter 00.00.00.00.00.00.00.01
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.514: 9c:02:98:8e:c6:5d Received EAPOL-Key from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.514: 9c:02:98:8e:c6:5d Received EAPOL-key in PTKINITNEGOTIATING state (message 4) from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.514: 9c:02:98:8e:c6:5d apfMs1xStateInc
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.514: 9c:02:98:8e:c6:5d 192.33.1.251 8021X_REQD (3) Change state to L2AUTHCOMPLETE (4) last state RUN (20)
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d 192.33.1.251 L2AUTHCOMPLETE (4) DHCP required on AP 50:06:04:2a:db:80 vapId 3 apVapId 1for this client
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d Not Using WMM Compliance code qosCap 00
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d 192.33.1.251 L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 50:06:04:2a:db:80 vapId 3 apVapId 1
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d apfMsRunStateInc
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d 192.33.1.251 L2AUTHCOMPLETE (4) Change state to RUN (20) last state RUN (20)
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d Mobile 9c:02:98:8e:c6:5d associated
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d 192.33.1.251 RUN (20) Reached PLUMBFASTPATH: from line 4918
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d Stopping retransmission timer for mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d Key exchange done, data packets from mobile 9c:02:98:8e:c6:5d should be forwarded shortly
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.515: 9c:02:98:8e:c6:5d Sending EAPOL-Key Message to mobile 9c:02:98:8e:c6:5d
       state PTKINITDONE (message 5 - group), replay counter 00.00.00.00.00.00.00.02
    *ccxL2RoamTask: Jun 13 11:29:32.516: 9c:02:98:8e:c6:5d Mobile 9c:02:98:8e:c6:5d has unsupported CCX version 0 in [l2roamProcessClientAssociation]
    *spamApTask5: Jun 13 11:29:32.558: 9c:02:98:8e:c6:5d Sent EAPOL-Key M5 for mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.601: 9c:02:98:8e:c6:5d Received EAPOL-Key from mobile 9c:02:98:8e:c6:5d
    *Dot1x_NW_MsgTask_5: Jun 13 11:29:32.601: 9c:02:98:8e:c6:5d Received EAPOL-key in REKEYNEGOTIATING state (message 6) from mo

    Already check everything you said, but no luck. Also check on another site and found out that could be a mac learning/updating issue with HP procurve 2510 switches. When a client roams from AP1 to AP2, on the switch the mac table entry for the client does not update to the port where AP2 is. After the mac-aging-time on the HP Procurve switch ends, the mac updates correctly and the traffic start going fine. Any ideas on how can i deal with this issue? Any configuration help for the WLC controller or APs? HP switches are configured as default (out-of-the-box).

  • AppData Roaming Issues

    Hi - I have a policy that redirects AppData folder separate from the user's Documents, Desktop, Favorites, etc. Each folders are separated from each other so redirection happens on all folders when users login into TS server. The issue with AppData is when
    the user logs in to a local laptop as themselves, it also does roaming locally to the laptop which causes the following scenario:
    1. Local AppData streams over a slow bandwidth link (vpn, ptp, dsl). 
    2. Local AppData settings (i.e. user personalized settings, task bar shortcuts, etc.) doesn't work when the user is not plugged in to the domain network.
    Question:
    1. I was wondering if there's a way to create a policy that will detect if the user is on a slow link network (i.e. remote, vpn, etc).
    2. Is there a way to leave AppData cache when user is not in the domain network leaving user's personalized settings in their laptops?
    Please kindly advise.
    Cheers - DB 

    Hi,
    For using Folder Redirection to redirect Appdata, only Appdata roaming can be redirected.
    Besides, Folder redirection applies only to applications that use the Windows shell APIs to redirect common folder paths. For example, if an application writes a file to %USERPROFILE%\AppData\Roaming,
    the file is written to the local profile and not redirected to the network location.
    Regarding Folder Redirection, the following article can be referred to for more information.
    Folder Redirection Group Policy Settings
    http://pubs.vmware.com/view-50/index.jsp?topic=/com.vmware.view.administration.doc/GUID-784A7FB5-033A-4541-A30A-43C9E5D16650.html
    >>
    1. I was wondering if there's a way to create a policy that will detect if the user is on a slow link network (i.e. remote, vpn, etc).
    Yes, we can use Group Policy to configure slow link threshold.
    Regarding slow link detection, the following article can be referred to for more information.
    GPOs and Slow Link Detection
    http://blogs.technet.com/b/musings_of_a_technical_tam/archive/2012/02/27/gpos-and-slow-link-detection.aspx
    >>2. Is there a way to leave AppData cache when user is not in the domain network leaving user's personalized settings in their laptops?
    Usually, Folder Redirection is used together with Offline Files which is enabled by default.
    Offline Files makes network files available to an end user when a network connection to the server is unavailable or slow.
    Regarding Offline Files and Folder Redirection, the following article can be referred to for more information.
    Offline Files and Folder Redirection
    http://technet.microsoft.com/en-us/library/gg277982(v=ws.10).aspx
    What's New in Offline Files
    http://technet.microsoft.com/en-us/library/ff183315(v=WS.10).aspx
    Best regards,
    Frank Shen

  • 7925g - roaming issue using a band only

    We have a small deployment of 7921g and 7925g phones. The 7925g phones while stationary when set to use the a band roam (while idle or in call) to distant APs with much weaker signal strength. That of course impacts negatively the quality of the call. The 7921 phones do not exhibit this behavior.
    Additional data:
    Access points and coverage:
    Meraki MR14 & MR24 set to select their own channels (channel spreading) and auto reduce power according to the RF environment to avoid co-channel interference. Currently the APs transmit on channels 1, 6, 11 and 36, 44, 149 and 157.
    Coverage has sufficient overlap for seamless roaming but it is really irrelevant in this case since the 7925 phones roam while stationary.
    Phone firmware:
    Initially 1.4.2 now the 7925s run 1.4.2ES.1
    The phones have been configured to continuously update the AP list (CUCM setting) and channels on which the APs do not transmit have been excluded (through the web interface of the phones)
    SR 618866317

    Since you are seeing unexpected roaming and you believe that  is the reason for the choppy audio, we need to gather phone logs as well  as correlated WLAN sniffer traces.
    The phone should have Kernel, WLAN Driver, WLAN manager set to DEBUG level.
    You can increae the # of files and file size to 10 /250 kb or enable syslog via USB.
    Be  aware that with this increased logging, audio quality can be impacted,  but since we are troubleshooting unexpected roaming it should be ok.
    Just want to be sure you don't enable this debug level on many phones / production user phones, where we make things worse.
    Once you get the logs, attach them to the case by replying to your SR thread with [email protected] copied.
    For the comment about 7921 and 7925 RSSI, they are different chipsets (although same vendor) and different antenna type.
    So will not be 1 to 1 exactly.
    Will need to ensure that the 7925 downstream RSSI is -67 dBm or better as well as the upstream signal (from 7925 to the AP).
    But since the issues don't seem signal related, let's not focus here, but instead focus on the unexpected roams.
    So yes we need all 3 modules enabled at DEBUG level as mentioned above.
    Get that info and attach it to the SR and let your assigned TAC engineer know.
    I already reached out to the TAC engineer assigned to your case.

  • 7921 roaming issues

    I have noticed an issue with 7921 roaming. If the phones are set to prefer 802.11a & they roam to 802.11b, they do not appear to ever roam back.
    Does anybody have any similar experiences?

    If you have set the mode to Auto-a, this means it will associate to 5 GHz when it first boots assuming the configured network is present. If not will try 2.4 GHz.
    To move to a new band, will have to exhaust the current signal.
    So if you have 5 GHz indoor and 2.4 GHz outdoor for instance, would have to exhaust 5 GHz signal before scanning 2.4 after associated to 5 GHz.
    This is only for fallback mode.
    If in the less preferred band due to failover, then there is no checking to move back to preferred band as the phone is not scanning the preferred band at this time.
    Ther are up to 14 channels in 2.4 GHz and 20 in 5 GHz.
    So a few suggestions, ensure the less preferred 2.4 GHz network doesn't have the configured SSID where you want to use 5 GHz.
    If using the WLAN controller, can not apply SSID based on AP, so would have to separate the APs onto different controllers, where the SSID is set only for 5 GHz on one and only for 2.4 on the other. Associate the APs to the controllers as necessary.
    The roaming across bands is still not seamless.
    But ultimiately the solution here is to ensure 5 GHz is available everywhere you plan to use the phone.

  • 7925g phones static/hissing and roaming issues

    Hello,
    We've been having an issue for several months now with our over 200 7925g phones.  Nurses are complaining that the phones have static and will drop the voice of the other caller and several times need to repeat the conversation.  We have confirmed several scenario's.  It occurs when both callers are on 7925g inside the coverage areas in the hospital; between 7925g and 7940 desk phone; 7925g and Nortel desk phone.  We've tested on 802.11a and 802.11b/g.  I do see a difference when on 802.11b/g however still get a hissing when connecting to a different AP.
    4 - 4400 controllers,  6.0.202 firmware
    1 - 5508 controller, 6.0.202 firmware
    234 - LAP1131AG AP's
    6 - AP1131AG AP's
    7 - LAP1142N AP's
    3 - LAP1310G AP's
    AP's are on 6.0.202.0 firmware
    7925g's all are on 1.3.3 firmware but we have a select few that we are testing at both hospitals with the newest firmware 1.4.1 and still same results.
    235  - 7925g phones.
    We have followed the 7925g setup & deployment guide, WLC Config Analyzer and made sure all checks were made.  The only setting we plan on testing this week is changing the CCKM authentication change which was recommended.  Currently we are WPA TKIP
    We have disabled the higher rates (36-54) on the 802.11a.
    We also have AirMagnet VoFi analyzer which is showing issues when roaming from AP.  The alarms indicate a one-way audio issue and points to the AP's and phones power not matching.  We have our Tx power level on the controller to automatic, Max Power Level at 30 dBm, Min. at -10 dBm, power Threshold at -70 (WLC Config Analyzer recommendation).  The phone TX Power is set at 8 dBm.  Call Power Save Mode has been tested with both None and U-APDS/PS-Poll.
    We have a case open with Cisco TAC and she has requested debugs from our controllers.  I have sent over 7 and she is not coming back with anything solid and not much help so far.
    Our tests between 802.11a and 802.11b/g (RSSI setting on phone Auto-a and Auto-bg) have shown better with the bg mode but still static and/or hissing.
    Any help would be greatly appreciated!  Thanks.

    Thanks!
    We finally had an awesome Cisco Engineer on our SR.  We straightened out the code and now have the correct 1.4.1.1.1.7 ES image and also configured CCKM.
    We are currently testing with about 20 phones before we deploy it to over 200 phones. 
    Below are the steps we took and so far the tests have resolved the issue.
    1. Downloaded & installed the 1.4.1.1.1.7 code on the 7925g's.
    2. Changed the Scan Mode on the device in Call Manager to 'continuous'
    3. On the Controllers, configured & implemented CCKM on the voice WLAN only.
    4.  Set the Radio Policy for the Voice WLAN to 802.11a only.
    5.  Only using channels 36, 40, 44, 48, 149, 153, 157, 161 on 802.11a
    6.  Disabled the 6,9,36,48 & 54 Mbps rates for 802.11a only
    7. Configured the phone with the new voice SSID with CCKM, Security Mode as EAP-Fast, & 802.11 Mode = Auto-a.
    We are following up with these test users next week so I will post if this fixes our issue.
    Thanks for all the assistance everyone!

  • Internatio​nal Roaming Issue... Please Help!!

    Hello,
    I have the TELUS Tour 9630, I have activated international calling and checked with TELUS customer service before I left to make sure everything was working on their end.  However I have arrived in Italy and the phone does not work at all.  I am not able to use the phone or data.  I have the network options on "global" and the sim card is inserted. 
    Does anyone have any troubleshooting tips since the TELUS international roaming guide was no help.
    Thank you in advance.

    I believe that you will need to contact Telus technical support and have them provision the GSM SIM card properly.  I had to  do a similar thing with the 8830 on  the Sprint network.

  • Roaming issues

    Hi,
    I bought my iPhone 3G in Boston, but am spending a month in Dublin, Ireland. Ever since I have been here I have had the usual issues with 3G and signals getting dropped, battery draining etc... However, the biggest problem I have is that I cannot make a call!
    Whenever I try to make a call (either locally or a call back to the States) it immediately says "call failed" and stops. Its fairly immediate so that makes me believe its not that the network is causing the problem. And this is when I have a decent signal.
    It seems to be able to receive calls fine.
    Also, the voicemail feature keeps asking me for a password - however, there was never a password before! So I dont know what to type in and therefore have no voicemail..!
    Any ideas?
    Eric

    Hi Scott, thank you for answer.
    I've just tested with WPA2/AES and the issue is still happening.
    I tried without authentication and still occur.
    At this moment I have 525 Rogue APs listed on WLC... May I disable A/B/G/N low data rates, is this a possible issue?
    Thanks

  • What version of code will prevent Roaming Issues?

    I have three 1230G AP's in an Emergency Room environment and have wireless carts that move throughout the area. The Three APs are running 12.3(2)JA2, are on channels 1, 6, & 11, and the clients are using the Cisco 350 cards. Only WEP is enabled.
    We setup a constant ping to a device in the same subnet and our problem occurs as we move the cart and it roams to a new AP, we get four "Destination not Found" errors everytime, with each cart.
    We have enabled WDS and have even taken WEP off to ensure a trouble-free connection and it still occurs. Is this a result of the version of code they have on the AP's or the clients? Has anyone else had this experience?
    Thanks in advance for any insight.

    With Normal roaming what you are seeing is the expected behaviour. Try out fast secure roaming. For more information on this have a look at the following document, which explains what Fast Secure Roaming is and how it can be configured.
    http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_guide_chapter09186a0080341d2d.html#wp1052156

  • CCKM, WPA, fast roaming issues

    I have a 4404 LAN controller with 1131a/g light AP's. Clients are Cisco a/b/g cards using WPA2, PEAP MSCHAPv2 and the Odyssey supplicant.
    Sometimes my clients roam between access points without losing a single packet, but other times they lose connectivity for up to 15 seconds while the client reauthenticates. Obviously, I would like to improve roaming time.
    On the WLAN controller I have WPA2 configured with AES and "auth key managment" set to 802.1x. I just upgraded to the latest (4.0) code on the controller and noticed there is a new "auth key management" setting called 802.1x + cckm.
    After much research on cckm tonight, I seem to have more questions than answers.
    Can/should cckm be used WITH WPA2?
    If not, can both WPA2 and cckm be supported on the same WLAN?
    Which auth key management setting should I be using, 802.1x or 802.1x + cckm?
    Does cckm require support of both supplicant and NIC?
    Is there anything else I can do to make roaming more seamless?

    Is it possible to use
    WPA1 + TKIP + Auth Key Mgmt="CCKM"
    or
    WPA1 + TKIP + Auth Key Mgmt="802.1x + CCKM"
    My WLC have Software Version 4.0.179.8.
    With this configuration I will need client card CCX v4 ??
    Thanks

Maybe you are looking for

  • Drag and drop to public folder

    I have an Intel Mac Mini running 10.4.9 connected to a windows domain & MS Exchange Server 2003 in a corporate environment. My problem: using Mail.app, I can read items within the public folders; however, I cannot drag-and-drop messages from my inbox

  • AGV 7.5

    I have the BEFW11S4 router, the problem I am having is that I can not use the my lap top if I have my anti virus along with the fire wall on line at the same time. How do I get them to work together. Thanks in advance for any help you can give me. fc

  • OLE Download to existing Excel file

    Hi, I am using OLE functions to download data to an existing excel file but facing problem in opening the existing file. I am using the following code to open an existing file   CREATE OBJECT h_excel 'EXCEL.APPLICATION'.   SET PROPERTY OF h_excel 'Vi

  • Message record list

    Hi Experts, is there a T.code or Table to list all the message record for a output type? Thanks, Emily

  • OSB: Is it possible to change throttling settings with WLST?

    Hi all, I am trying to find a solution to change the throttling settings of a business service with WLST, since it is not possible to set it in the customization file. I already know the parameter alsbImportPlan.setPreserveExistingOperationalValues(b