Wlcs 3.5 vs wlcs in portal suit 4.0

Hi All,
I need the following information urgently:
1. What is the version of weblogic commerce server in portal suit ? Is the commerce
server given with portal server is same as weblogic commerce server 3.5 sp2 ? If
not, how is it different from wlcs 3.5 sp2 ?

Sudarson,
The commerce components in WLP 4.0 are pretty much the
same as in WLCS 3.5 SP2 except for the following:
1) Tax and payment services have been converted to Web Services.
2) The commerce templates were updated to use the new Webflow
and Pipeline architecture.
3) WLP 4.0 introduced a new deployment model more inline with
J2EE Enterprise App and Web Apps. As a result, some components
were updated to work with application management tools and
application-level scoping of resources.
Hope this helps,
Michel.
"sudarson" <[email protected]> wrote in message news:3cc6b7bc$[email protected]..
>
Hi All,
I need the following information urgently:
1. What is the version of weblogic commerce server in portal suit ? Is the commerce
server given with portal server is same as weblogic commerce server 3.5 sp2 ? If
not, how is it different from wlcs 3.5 sp2 ?

Similar Messages

  • 5760 WLC and 5760 HA WLC question

    Hi everyone,
    I assume this information must exist... I just cannot locate it. Customer purchasing two 5760 WLCs:
    1     AIR-CT5760-500-K9
    1     AIR-CT5760-HA-K9
    I am looking for info on how to configure these 2 WLCs to work together.  How do you inform the production WLC that a HA WLC is available to sync with? Do WLCs have to be L-2 adjacent, or will HA operate at L-3?  How does this HA setup work? etc.
    Any help would be really appreciated.

    Hi,
    Any news regarding this issue?
    We've have the same scenario:
    1     AIR-CT5760-500-K9
    1     AIR-CT5760-HA-K9
    Both running
    IOS XE 03.03.01SE
    I've activated Global AP Failover Priority in both WLC and from a total of 47 APs, i've configured 8 with Priority Critical, 7 APs with Priority High and  3 APs with Priority Medium.
    We've issued an reload to the primary WLC and it took 7 minutes for the APs recover from the Secondary to the Primary
    13:14 - reload issued on the primary WLC
    13:15 - service granted by the secondary WLC (required an shut/no shut to the "Network Status" of the radio interfaces)
    13:22 - service recovered to the primary WLC
    Edit - Forgot to mention that the priority values mentioned above didn't show much improvement in the AP recovery time...

  • CWA/ISE/WLC - client timeout when redirected to portal.

    Problem: When connecting to the CWA ssid, the client gets redirected to: https://lab-ise01.lab.local:8443/guestportal/gateway?sessionId=3c02a8c00000000878430a51&action=cwa
    but the link times out.
    I'm currently following this guide: https://supportforums.cisco.com/docs/DOC-26442
    Any thoughts or suggestions are appreciated.
    Info: ISE 1.1.1 and vWLC 7.3.101.0 is installed on vmware. Identity Source: Internal Users. AP is in FlexConnect mode. MAC filtering enable, no layer 3 security. Allow AAA Override enabled. Radius NAC enabled.
    Topology:
    Win7/iPad -  -  - AP----labswitch-----switch-----switch-----VMware
    (Traffic does not pass through FW and there are no ACL on the switches.)
    ACL on WLC:
    Client on WLC

    Hi all.
    Accoding with this behaviour, I have a similar problem with the renew of the IP address. In a similar scenario (ISE1.1.2 + vWLC 7.3.101. + CWA + DVLAN assigment); for test purposses I need to use the AP in flexconnect mode with central control and traffic data due to vWLC does not support APs in a local mode.
    Applying WCA in a SSID with a "non-routed" interface and two interfaces for both different profiles. Client passes CWA profile in "non route" subnet when redirected;  after a successful web authetication ISE sends to WLC the new attributes including the new VLAN, new ACL and the access-accept, but the client is not trying to change the IP address through DHCP.
    I use two rules for authentication
    First: Guest Redirection; condition "Wireless MAB" then "WLC-CWA" (central authentication - ACL-POSTURE-REDIRECT)
    Second (This rule above the first) Guest Traffic; Condition "Network access: UseCase EQUALS GuestFlow) then "Guest Permit Access"(with includes new vlan assigment in function of the role based - new ACL asigment - Termination-Action=0)
    WLC shows me the data correctly, it changes the interface, the ACL and changes the client status to RUN but maintains the IP address belonging to the old VLAN (non-routed vlan)
    Could be possible that this bug will be hitting me?
    Are there any Radius Attribute to force a DHCP IP procces for this devices?
    Thanks in advanced.
    Best Regards.

  • WLCS 3.1 + WLS SP 9 --*** PORTALS Not WORKING!!!!

    After applying WLS SP 9.0 our portals not working.
    Can anybody throw some light, PLEASE !!! **URGENT**
    We are getting the following Error:
    Sun May 06 21:24:44 GMT+03:00 2001:<E> <ServletContext-General> Servlet failed
    with Exception weblogic.servlet.jsp.JspException: (line -1): Error in tag library
    at: 'wl': The Tag class 'weblogi x.jsp.tags.CacheTag' has no setter method corresponding
    to TLD declared attribute 'async', (JSP 1. spec, 5.4.1) at java.lang.Throwable.fillInStackTrace(Native
    Method) at java.lang.Throwable.fillInStackTrace(Compiled Code) at java.lang.Throwable.<init>(Compiled
    Code) at java.lang.Exception.<init>(Compiled Code) at java.lang.RuntimeException.<init>(Compiled
    Code) at weblogic.servlet.jsp.JspException.<init>(Compiled Code) at weblogic.servlet.jsp.JspException.<init>(Compiled
    Code) at weblogic.servlet.jsp.StandardTagLib.jspException(Compiled Code) at weblogic.servlet.jsp.StandardTagLib.processTag(Compiled
    Code) at weblogic.servlet.jsp.StandardTagLib.processTagElements(Compiled Code)
    at weblogic.servlet.jsp.StandardTagLib.<init>(Compiled Code) at weblogic.servlet.jsp.JspLexer.loadTagLib(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(Compiled Code) at
    weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(Compiled Code) at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(Compiled Code) at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code) at weblogic.servlet.jsp.JspLexer.parse(Compiled
    Code) at weblogic.servlet.jsp.JspParser.doit(Compiled Code) at weblogic.servlet.jsp.JspParser.parse(Compiled
    Code) at weblogic.servlet.jsp.Jsp2Java.outputs(Compiled Code) at weblogic.utils.compiler.CodeGenerator.generate(Compiled
    Code) at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code) at weblogic.servlet.jsp.JspStub.prepareServlet(Compiled
    Code) at weblogic.servlet.jsp.JspStub.checkForReload(Compiled Code) at weblogic.servlet.internal.ServletStubImpl.getServlet(Compiled
    Code) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(Compiled Code) at com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(Compiled
    Code) at com.beasys.commerce.foundation.flow.FlowManager.service(Compiled Code)
    at javax.servlet.http.HttpServlet.service(Compiled Code) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
    Code) at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
    at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code) at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled Code) at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code) at weblogic.socket.MuxableSocketHTTP.execute(Compiled
    Code) at weblogic.kernel.ExecuteThread.run(Compiled Code)

    I have gotten it to work by replacing the sp9 weblogic-tags-510.jar with
    the sp8 weblogic-tags-510.jar. We haven't experienced any problems with
    our app after using this workaround. However, we haven't completely
    tested it either.
    psimon wrote:
    You should use sp6 or sp8 instead of sp9
    Pascal
    Nadeem a écrit :
    After applying WLS SP 9.0 our portals not working.
    Can anybody throw some light, PLEASE !!! **URGENT**
    We are getting the following Error:
    Sun May 06 21:24:44 GMT+03:00 2001:<E> <ServletContext-General>
    Servlet failed
    with Exception weblogic.servlet.jsp.JspException: (line -1): Error
    in tag library
    at: 'wl': The Tag class 'weblogi x.jsp.tags.CacheTag' has no setter
    method corresponding
    to TLD declared attribute 'async', (JSP 1. spec, 5.4.1) at
    java.lang.Throwable.fillInStackTrace(Native
    Method) at java.lang.Throwable.fillInStackTrace(Compiled Code) at
    java.lang.Throwable.<init>(Compiled
    Code) at java.lang.Exception.<init>(Compiled Code) at
    java.lang.RuntimeException.<init>(Compiled
    Code) at weblogic.servlet.jsp.JspException.<init>(Compiled Code) at
    weblogic.servlet.jsp.JspException.<init>(Compiled
    Code) at weblogic.servlet.jsp.StandardTagLib.jspException(Compiled
    Code) at weblogic.servlet.jsp.StandardTagLib.processTag(Compiled
    Code) at
    weblogic.servlet.jsp.StandardTagLib.processTagElements(Compiled
    Code)
    at weblogic.servlet.jsp.StandardTagLib.<init>(Compiled Code) at
    weblogic.servlet.jsp.JspLexer.loadTagLib(Compiled
    Code) at
    weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(Compiled Code)
    at
    weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(Compiled Code) at
    weblogic.servlet.jsp.JspLexer.mDIRECTIVE(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled
    Code) at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code) at
    weblogic.servlet.jsp.JspLexer.parse(Compiled
    Code) at weblogic.servlet.jsp.JspParser.doit(Compiled Code) at
    weblogic.servlet.jsp.JspParser.parse(Compiled
    Code) at weblogic.servlet.jsp.Jsp2Java.outputs(Compiled Code) at
    weblogic.utils.compiler.CodeGenerator.generate(Compiled
    Code) at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code) at
    weblogic.servlet.jsp.JspStub.prepareServlet(Compiled
    Code) at weblogic.servlet.jsp.JspStub.checkForReload(Compiled Code)
    at weblogic.servlet.internal.ServletStubImpl.getServlet(Compiled
    Code) at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
    Code)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(Compiled
    Code) at
    com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(Compiled
    Code) at
    com.beasys.commerce.foundation.flow.FlowManager.service(Compiled
    Code)
    at javax.servlet.http.HttpServlet.service(Compiled Code) at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled
    Code) at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
    Code)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled
    Code) at
    weblogic
    servlet.internal.ServletContextManager.invokeServlet(Compiled Code)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code) at
    weblogic.socket.MuxableSocketHTTP.execute(Compiled
    Code) at weblogic.kernel.ExecuteThread.run(Compiled Code)

  • Login changes from WLCS 3.2 vs WLCS 3.5

    I am upgrading my current prototype using WLCS3.2 to 3.5. I use the
    exampleportal demo and plug in a few JSP's from my web application.
    In 3.2, after you enter your login information the request object that all
    portlets have access to contains 3 parameters: loginAction, username and
    password. I use this information in order to log into my application which
    allows me to have a single signon.
    In 3.5, things have changed and the only parameter that I have access to
    through the request object is 'dest' which has the path to
    /something/loginSuccess.jsp. How do I now get access to login information
    from the portal similar to what was available to me in 3.2?
    thank you
    shane

    Peter,
    Thanks for the quick reply. I'll let you know how I make out.
    thanks
    shane
    "Peter Laird" <[email protected]> wrote in message
    news:[email protected]...
    >
    Shane,
    Excellent question. Let me point you to some reading:
    1. There is a brand new security guide for 3.5 athttp://edocs.bea.com/wlcs/docs35/secguide/index.htm
    >
    2. Read the Security chapter of the Servlet 2.2 spec, found athttp://java.sun.com/products/servlet/index.html
    >
    >
    Realize that the 3.2 portal's implementation of the security mechanismpredated
    the standard J2EE declarative security model. The 3.5 release of portalreimplemented
    security to adhere to the standard. So the missing attributes is aside-effect
    of this change.
    In 3.2, the portal was responsible for doing its own user authentication.Therefore
    the username and password was available to the portal code. In 3.5, theservlet
    container (WLS) performs the authentication on behalf of the portal. Asyou see
    in the Servlet spec, the methods available to a servlet afterauthentication allow
    you to get the username via request.getUserPrincipal(). But there is nostandard
    way to get the password. So if you require the password to propagate theidentity
    to another application, you are out of luck.
    All is not lost though. I can think of three avenues for you.
    1. Reread section 11.6 of the Servlet 2.2 spec. It declares that thecontainer
    must maintain authentication at the container-scope, and not the web-appscope.
    Know that the portal is deployed as a webapp. If your secondaryapplication can
    be deployed as a J2EE web-app on the same server, authentication can bemaintained
    across web-apps.
    2. If you cannot deploy your app as a web-app, there is still anotheroption.
    WLS supports an "Authentication Filter" which is invoked both immediatelyprior
    and immediately after the j_security_check authentication mechanism. Thisallows
    you to provide a callback which accepts the HttpRequest. Therefore, youshould
    be able to stash the j_password into the Session before WLS clears it outof the
    Request. I don't have time to try this today, but if you do please postyour results!
    Read here for more info on the AuthFilterhttp://e-docs.bea.com/wls/docs60//javadocs/weblogic/servlet/security/AuthFil
    ter.html
    >
    >
    3. If the above options don't work for you, you may wish to implement acustom
    WLS security realm which will provide passwords for users upon request.
    Post back to the newsgroup with your thoughts/results.
    PJL
    "Shane Daniels" <[email protected]> wrote:
    I am upgrading my current prototype using WLCS3.2 to 3.5. I use the
    exampleportal demo and plug in a few JSP's from my web application.
    In 3.2, after you enter your login information the request object that
    all
    portlets have access to contains 3 parameters: loginAction, username
    and
    password. I use this information in order to log into my application
    which
    allows me to have a single signon.
    In 3.5, things have changed and the only parameter that I have access
    to
    through the request object is 'dest' which has the path to
    /something/loginSuccess.jsp. How do I now get access to login
    information
    from the portal similar to what was available to me in 3.2?
    thank you
    shane

  • Is it possible to use a 5500 WLC and a 2500 WLC as failover?

    I am curious to know if there are any technical issues with this design. The 5500 WLC would be the primary and 2500 WLC would be the secondary. The only need for the secondary would be in the event of failure of the primary, and support needs when doing maintenance such as code upgrades.
    We would use the same version of code on each controller and apply the necessary amount of AP licenses on each. The controllers would have identical configurations and host multiple SSID's, including offering guest services. Does the 2500 support guest network services?

    Yeah, believe the 2500 only does multicast-multicast mode.  Which isn't that big of a deal usually.  MM being the preferred method.
    the 2504 also has that 300M backplane limitation.  SO if you are going to use the 2504 I would recommend HREAP so you don't have to worry about that.
    Not supported on 2504.
    •Support for wired guest access.
    •Cisco 2500 Series Controller cannot be configured as an auto anchor controller. However you can configure it as a foreign controller.
    •Supports only multicast-multicast mode.
    •Bandwidth Contract feature is unsupported.
    •Access points plugged directly into the WLC.
    •Service port support
    •Apple Talk Bridging
    •LAG
    •Wired Guest
    Steve

  • Upgrading from WLC 4402-50 to WLC 5508-250

    I am planning to upgrade my WLC 4402-50 (HA) to WLC 5508-250 (HA). I also have some really old 1020 Access points that I will be replacing with 1142's. Once I have completed the upgrade to the 5508s, I will repurpose the 4402's as Mobile Anchor controllers to support Guest Wireless.
    Does anyone have any actual experience with this sort of upgrade? Any practical suggestions or ideas??
    Thanks,

    Hi,
    Are you still facing this issue? if yes try checking the link if that helps
    http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008064a991.shtml
    thanks,
    Vinay

  • WLC 4406 Migration to WLC 5508

    I have to make a migration from a controller to oher.We have now in production a WLC 4406 with 90 AP in local mode and HREAP mode, and we have to change the WLC to other new model 5508.
    Do somebody know which one could be the best method to do that???
    Thanks for your HELP and Time....

    Ths is true Salil, but very few companies are running the VPN module in the 4400.  thankfully it was EOL'd shortly afte Cisco bought Airespace.
    and the upload check that runs, will alert you to any config that is wrong.
    HTH,
    Steve
    Please remember to rate helpful posts or to mark the question as answered so that it can be found later.

  • Another 5760 WLC and 5760 HA WLC question

    Hi all,
    I have two 5760 Controllers, one licensed and one a HA SKU Controller. I have configured them for N+1 fail-over. They are configured to be in the same L2 management network and in the same Mobility Group. The customer had an issue and tried to fail-over the APs to the secondary controller at the weekend but only about 15 out of 185 APs actually failed-over. Does anyone have any thoughts as to why they all didn't fail-over. The controllers are both running 3.3.3SE code and High Availability under Global AP Configuration is set on bot the primary and secondary.
    Thanks

    Refer the document :
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/5700/software/release/3e/high_availability/configuration_guide/b_ha_3e_5700_cg.pdf

  • Can I use ASA to be a DHCP Server use in WLC wireless Client

    I want to use ASA to be a DHCP Server for Wireless Client not it can't.
    I check the debug log in WLC, I confirm the WLC have send the request to ASA.
    In the ASA, it don't have any hits in the rule when the WLC send the DHCP relay request.
    I have try don't use dhcp relay in WLC but don't success. Anybody have the same case with me? And Is the ASA can't support DHCP relay agent to request to get the IP Addr.
    P.S. In the Network Design limitation so I can't use WLC to be DHCP Server.
    Equipment:
    ASA5510
    WLC4402
    How can I fix it.
    Thank you very much

    The issue is that the ASA doesn't accept DHCP requests from a relay agent, only broadcast DHCP requests. In the 4.2 version for the controllers there is now an option so you can change the way the controller forwards DHCP requests so that it is sent as a broadcast and not from a relay agent.

  • How can I add a new WLC on my network

    Hi there,
    I have a WLC4404(v4.0.219.0) and several APs on my network.
    Those APs are belonged to a couple of vlans.
    I planed to add a new WLC4404(v5.0.148.0) on same network with a old one.
    I configured the new WLC4404 as a primary controller of the APs and the old on as a secondary.
    I noticed some APs could be registered only on same vlan with the managemnet interface of the WLC.
    How can I register the APs on different VLANs with Mgmt. of the WLC?
    Let me know if you have a any idea.
    Thanks
    Jongkwan Lee

    Well since the ap's only know of the existing WLC, the only way they will join, is if you remove the existing wlc and let the ap's find the new wlc. When you configure the mobility group, that info is pushed to the ap, so that it knows of the new wlc. This way you can set the primary ap to the new one and the second wlc to the existing wlc.... make sure ap fallback is enabled so that the ap will try to join the new wlc. If you still have issues, I would console into the ap and capture the log when you faile the existing wlc.

  • WLC 5508 - AP 1600 serie's are conecting with WLC but unable to regester with WLC and country is US no matter what I do, i can't change it

    Hello everyone!
    I have a controller of the 5508 series and Ap 1602.
    Ap manage to obtain IP addresses from the DHCP server that is the 5508 controller.
    but the Rev fail to register, please I really vesoin help.
    Below are some show:
    1.  AP:  sh version
    AP0006.f6d5.ea9c#sh version
    Cisco IOS Software, C1600 Software (AP1G2-RCVK9W8-M), Version 15.2(2)JB, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Tue 11-Dec-12 04:52 by prod_rel_team
    ROM: Bootstrap program is C1600 boot loader
    BOOTLDR: C1600 Boot Loader (AP1G2-BOOT-M) LoaderVersion 15.2(2)JAX, RELEASE SOFTWARE (fc1)
    AP0006.f6d5.ea9c uptime is 38 minutes
    System returned to ROM by power-on
    System image file is "flash:/ap1g2-rcvk9w8-mx/ap1g2-rcvk9w8-mx"
    Last reload reason:
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    cisco AIR-CAP1602E-E-K9    (PowerPC) processor (revision A0) with 98294K/32768K bytes of memory.
    Processor board ID FGL1709Z6PC
    PowerPC CPU at 533Mhz, revision number 0x2151
    Last reset from power-on
    LWAPP image version 7.4.1.37
    1 Gigabit Ethernet interface
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 00:06:F6:D5:EA:9C
    Part Number                          : 73-14508-04
    PCA Assembly Number                  : 000-00000-00
    PCA Revision Number                  :
    PCB Serial Number                    : FOC17020MTR
    Top Assembly Part Number             : 800-38553-01
    Top Assembly Serial Number           : FGL1709Z6PC
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-CAP1602E-E-K9
    Configuration register is 0xF
    2.  AP:  sh ip interface brief
    Interface                  IP-Address      OK? Method Status                Protocol
    BVI1                       unassigned      YES DHCP   up                    up
    GigabitEthernet0           unassigned      NO  unset  up                    up
    GigabitEthernet0.1         unassigned      YES unset  up                    up
    3.  AP:  sh inventory
    ---nothing---
    4.  WLC:  sh sysinfo
    (Cisco Controller) >show sysinfo
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller
    Product Version.................................. 7.3.101.0
    Bootloader Version............................... 1.0.1
    Field Recovery Image Version..................... 6.0.182.0
    Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
    Build Type....................................... DATA + WPS
    System Name...................................... WLC-EEML
    System Location..................................
    System Contact...................................
    System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
    Redundancy Mode.................................. Disabled
    IP Address....................................... 10.10.10.1
    Last Reset....................................... Software reset
    System Up Time................................... 1 days 1 hrs 13 mins 37 secs
    System Timezone Location.........................
    Configured Country............................... US  - United States
    Operating Environment............................ Commercial (0 to 40 C)
    Internal Temp Alarm Limits....................... 0 to 65 C
    Internal Temperature............................. +39 C
    --More-- or (q)uit
    External Temperature............................. +25 C
    Fan Status....................................... OK
    State of 802.11b Network......................... Enabled
    State of 802.11a Network......................... Enabled
    Number of WLANs.................................. 1
    Number of Active Clients......................... 0
    Burned-in MAC Address............................ E0:2F:6D:5D:7D:C0
    Power Supply 1................................... Present, OK
    Power Supply 2................................... Absent
    Maximum number of APs supported.................. 25
    5.  WLC:  sh time
    Time............................................. Fri Jan  3 12:21:37 2014
    Timezone delta................................... 0:0
    Timezone location................................
    NTP Servers
        NTP Polling Interval.........................     86400
         Index     NTP Key Index     NTP Server      NTP Msg Auth Status
    also, I'm in africa but
    I can not change the country or the time zone
    thank you in advance for your help

    Hi,
    By CLI:
    Before change the country code on wlc , You must disable
    WLC > config 802.11a disable network
    WLC  >config 802.11b disable network
    WLC  >config country SA (...or wtever country u are in)
    And then enable both network again.
    WLC  >config 802.11a enable network
    WLC  >config 802.11b enable network
    By GUI:
    First disable both network 802.11a and 802.11b
    Follow these steps to disable the 802.11a and 802.11b/g networks as follows:
    a.          Choose Wireless> 802.11a/n > Network.
    b.          Unselect the 802.11a Network Status check box.
    c.          Click Apply to commit your changes.
    d.          Choose Wireless > 802.11b/g/n > Network.
    e.          Unselect the 802.11b/g Network Status check box.
    f.          Click Apply to commit your changes.
    Change country code on WLC now:
    Choose Wireless > Country
    after changing the country code please enable both networks(802.11a and 802.11b)
    Hope it helps.
    Regards
    Dont forget to rate helpful posts.

  • Not able to form EoIP tunnel with anchor WLC

    Hi all,
    I have a WLC at a remote site that is supposed to form an EoIP tunnel with 2 anchor WLCs located at a data center. From the site WLC and the anchor WLCs, the mobility show UP on both ends. Also I can ping to the mobility peers from each end. However, when I look into the client details on the remote site WLC, there is no Mobility Anchor IP address, which tells me that the EoIP tunnel between the site and anchor controller is not forming for some reason. Any idea what I could be missing?
    (WOHW-WC01) >show client detail 0c:3e:9f:ab:db:ed
    Client MAC Address............................... 0c:3e:9f:ab:db:ed
    Client Username ................................. N/A
    AP MAC Address................................... 0c:68:03:b9:44:70
    AP Name.......................................... WOHW-LAP016
    Client State..................................... Associated
    Client NAC OOB State............................. Access
    Wireless LAN Id.................................. 66
    Hotspot (802.11u)................................ Not Supported
    BSSID............................................ 0c:68:03:b9:44:72
    Connected For ................................... 1469 secs
    Channel.......................................... 6
    IP Address....................................... Unknown
    Gateway Address.................................. Unknown
    Netmask.......................................... Unknown
    IPv6 Address..................................... fe80::1c1a:e07c:dd48:bc7e
    Association Id................................... 3
    Authentication Algorithm......................... Open System
    Reason Code...................................... 1
    Status Code...................................... 0
    Session Timeout.................................. 0
    Client CCX version............................... No CCX support
    QoS Level........................................ Bronze
    802.1P Priority Tag.............................. disabled
    CTS Security Group Tag........................... Not Applicable
    KTS CAC Capability............................... No
    WMM Support...................................... Enabled
      APSD ACs.......................................  BK  BE  VI  VO
    Power Save....................................... ON
    Current Rate..................................... m7
    Supported Rates.................................. 9.0,12.0,18.0,24.0,36.0,48.0,
        ............................................. 54.0
    Mobility State................................... None
    Mobility Move Count.............................. 0
    Security Policy Completed........................ No
    Policy Manager State............................. STATICIP_NOL3SEC
    >>> No Mobility peer IP address <<<<
    (WOHW-WC01) >show mobility anchor wlan 66
    Mobility Anchor Export List
     WLAN ID     IP Address            Status
     66          137.183.242.149       Up                              
     66          137.183.242.150       Up                              
    (WOHW-WC01) >show mobility sum           
    Mobility Architecture ........................... Flat
    Mobility Protocol Port........................... 16666
    Default Mobility Domain.......................... WOHW_ENT1
    Multicast Mode .................................. Disabled
    Mobility Domain ID for 802.11r................... 0x9cbf
    Mobility Keepalive Interval...................... 10
    Mobility Keepalive Count......................... 3
    Mobility Group Members Configured................ 3
    Mobility Control Message DSCP Value.............. 0
    Controllers configured in the Mobility Group
     MAC Address        IP Address       Group Name                        Multicast IP     Status
     bc:16:65:f9:18:60  137.183.242.150  CIN_GUEST1                        0.0.0.0          Up
     e0:2f:6d:7c:42:20  143.27.201.52    WOHW_ENT1                         0.0.0.0          Up
     f8:72:ea:ee:a0:00  137.183.242.149  CIN_GUEST1                        0.0.0.0          Up

    It works now. I changed the NAC state to "Radius-NAC". Now the mobility hand-off is occurring. 
    (WOHW-WC01) >show wlan 66 
    WLAN Identifier.................................. 66
    Profile Name..................................... PGGuest
    Network Name (SSID).............................. PGGuest
    Status........................................... Enabled
    MAC Filtering.................................... Enabled
    Broadcast SSID................................... Enabled
    AAA Policy Override.............................. Enabled
    Network Admission Control
      Client Profiling Status ....................... Disabled
       DHCP ......................................... Disabled
       HTTP ......................................... Disabled
      Radius-NAC State............................... Enabled

  • WLC 5508 7.4.X - N+1

    Hi,
    I don't undestand this document
    http://www.cisco.com/c/en/us/td/docs/wireless/technology/hi_avail/N1_High_Availability_Deployment_Guide/N1_HA_Overview.html
    How can the third 5508 (suport max 500 AP) backup all other WLC ? n+1 how ?
    With secondary wlc configured in HA-SKU (without AP SSO) the 500 licenze are permanent ?
    who can explain me.. this is a document bug ??

    What they're describing is HA N+1, not HA 1:1 AP SSO.  This option, which is "NON-AP-SSO", allows you to use an HA-SKU or > -50-k9 SKU coverted, to operate as a dedicated +1 WLC in HA.  When using this configuration, this WLC allows the use of the "hardware maximum" of the device: Thus 500 APs for WLC 5508, or 1000APs for a WISM2 (as an example).  Since this WLC can wait as a backup to multiple WLCs, that's why it's not capable of the AP SSO, which requires a 1:1 pairing of the HA WLC with an Active HA WLC.
    When using the HA N+1 the WLC acts the same as the pre AP-SSO "HA" concept; where you had Primary, Secondary Tertiary configs on your APs (which you may still have).  All it is saying is that the N+1 HA WLC can act as one of these Secondary/Tertiary WLCs, much like a WLC you had licenesed for 250 or 500 APs could do previously.
    In the past you would use, lets say a 250 WLC AP as this backup WLC.  Many people were frustrated that they had to have a $60,000 WLC just sitting there "waiting for something to fail".  But that's what it did.  If a WLC failed, lets say one with 100 APs, this backup WLC would take on the APs and use 100 of it's 250 AP license count.  If additional WLCs failed, the process continued until this backup WLC was filled.
    The idea of using the HA-SKU in an N+1 is that while yes, you don't get the 1:1 AP SSO configuration, you are getting more bang for your buck in that this WLC can sit as a backup (as it did in the past) but it can accept up to the maximum it's hardware can handle in terms of AP count, not only what it was permanently licensed for.  Rather than spending $100,00 on a 500 AP count WLC to backup your 2x250 AP count WLCs, why not look at a $50,000 HA-SKU that can "handle" up to 500 APs.
    So given this scenario, this WLC is "backuping up all other WLCs" for whom it is a Secondary/Tertiary WLC backup.
    As far as the HA-SKU "licenese", it's not "permanent" per se.  With an HA SKU in N+1 you have a 90 day timer which will then "nag you" (via console) that this HA WLC is not truly intended to permanently house these APs.  The idea is that if the Primary WLC failed, you would get it back online and then move your APs back to where they belong and return the HA N+1 WLC back to 0 APs.

  • AP1142N doesn't join his WLC (5508)

    Hello,
    My APs 1142N don't join their WLC. APs and WLC management interface are in the same vlan (WLC can ping all the APs). It is strange because it doesn't seem like they are trying to contact the WLC.
    What's strange is that I have other AP 1142N which joined this WLC without any problem.
    (Cisco Controller) >show sysinfoManufacturer's Name.............................. Cisco Systems Inc.Product Name..................................... Cisco ControllerProduct Version.................................. 7.0.98.214Bootloader Version............................... 1.0.1Field Recovery Image Version..................... N/AFirmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27Build Type....................................... DATA + WPS ...
    ap#show versionCisco IOS Software, C1140 Software (C1140-K9W7-M), Version 12.4(21a)JA1, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2009 by Cisco Systems, Inc.Compiled Wed 16-Sep-09 18:09 by prod_rel_teamROM: Bootstrap program is C1140 boot loaderBOOTLDR: C1140 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA6, RELEASE SOFTWARE (fc1)ap uptime is 43 minutesSystem returned to ROM by power-onSystem image file is "flash:/c1140-k9w7-mx.124-21a.JA1/c1140-k9w7-mx.124-21a.JA1" ...cisco AIR-AP1142N-E-K9     (PowerPC405ex) processor (revision A0) with 98294K/32768K bytes of memory.Processor board ID FCZ1649D2U0PowerPC405ex CPU at 586Mhz, revision number 0x147ELast reset from power-on1 Gigabit Ethernet interface2 802.11 Radio(s)32K bytes of flash-simulated non-volatile configuration memory.Base ethernet MAC Address: E0:2F:6D:A5:AA:F6Part Number                          : 73-12836-06PCA Assembly Number                  : 800-33767-06PCA Revision Number                  : A0PCB Serial Number                    : FOC164732R2Top Assembly Part Number             : 800-33775-05Top Assembly Serial Number           : FCZ1649D2U0Top Revision Number                  : A0Product/Model Number                 : AIR-AP1142N-E-K9
    Regards,

    Ok thank. I didn't notice that it was an autonomous image.
    It seems that I can't use this guide (http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp157147) to upgrade them to lightweight (can't install software on windows seven).
    Regards

Maybe you are looking for

  • How can i move my contacts into different contact groups on my ipad

    i have created contact groups on my ipad through icloud, i now want to move contacts into different groups, but can't work out how to do it!! any help would be appreciated.

  • Repeated prompts to install with "Installation Failed" error - ANNOYING

    I've been experiencing the same issue for the better part of July and August.  I have tried several recommended strategies in the hopes of getting Adobe Flash Player (AFP) to install and perform correctly; however, none of my attempts have led to AFP

  • Exporting a custom menu template from DVD Studio Pro

    So I recently developed a custom template in DVDSP that my company wants to use on all our DVDs.  Is there any way to export or share this template with my coworkers, or am I stuck with DVD duty?

  • How To Pass the value from JSP to Applet

    plz reply how can we pass the value from the JSP to Applet ...the applet is embedded in JSP page....

  • Data view issue

    I'm not able to see the node attributes in data view of adobe designer in SAP GUI 710. In my other computer I have SAPGUI 640, I can see the attributes of the node and I can map it. I'm using same Interface/form and connecting to the same backend exc