WLC version compatibility

Dear All,
We plan to upgrade one WLC from the mobility group, code from 7.0.116.0 to 7.0.240.0. Can we upgrade like this when its a part of mobility group?
Shall the latest one supports WCS or NCS..? What and all to be taken into consideration before doing this upgrade..?
Please suggest...

Rule of thumb for WCS is that the WCS should be at equal or higher version than the WLC. This rule changes with NCS and Prime infrastructure. You might want to look at getting a WCS to Prime infrastructure migration while they still have a good pricing for that. WCS was replaced by NCS and NCS is replaced by Prime Infrastructure. PI supports the WLC that you are running.
Sent from Cisco Technical Support iPhone App

Similar Messages

  • WCS & WLC version compatibility

    Are there any compatibility issues between WCS version 7.0.164.0 and WLC version 7.0.116.0?

    Hi Jason,
    Table 1     WCS Versions 
    WCS Version Supported Controller Versions Supported Location Server Versions Supported MSE Versions Release Date Upgrade Supported From Operating System Requirement
    7.0.172.0
    7.0.116.0
    7.0.98.218
    7.0.98.0
    6.0.202.0
    6.0.199.4
    6.0.196.0
    6.0.188.0
    6.0.182.0
    6.0.108.0
    5.2.193.0
    5.2.178.0
    5.2.157.0
    4.2.209.0
    4.2.207.0
    4.2.205.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    6.0.202.0
    7.0.201.0
    April 2011
    7.0.164.3
    7.0.164.0
    6.0.202.0
    6.0.196.0
    6.0.181.0
    6.0.170.0
    6.0.132.0
    5.2.148.0
    5.2.130.0
    5.2.125.0
    5.2.110.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    7.0.164.3
    7.0.98.0
    6.0.202.0
    6.0.199.4
    6.0.196.0
    6.0.188.0
    6.0.182.0
    6.0.108.0
    5.2.193.0
    5.2.178.0
    5.2.157.0
    4.2.209.0
    4.2.207.0
    4.2.205.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    6.0.103.0
    7.0.105.0
    December 2010
    7.0.164.0
    6.0.196.0
    6.0.181.0
    6.0.170.0
    6.0.132.0
    5.2.148.0
    5.2.130.0
    5.2.125.0
    5.2.110.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    7.0.164.0
    7.0.98.0
    6.0.202.0
    6.0.199.4
    6.0.196.0
    6.0.188.0
    6.0.182.0
    6.0.108.0
    5.2.193.0
    5.2.178.0
    5.2.157.0
    4.2.209.0
    4.2.207.0
    4.2.205.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    6.0.103.0
    7.0.105.0
    June 2010
    6.0.181.0
    6.0.170.0
    6.0.132.0
    5.2.148.0
    5.2.130.0
    5.2.125.0
    5.2.110.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    6.0.202.0
    6.0.202.0
    6.0.199.4
    6.0.199.0 (pulled from CCO)
    6.0.196.0
    6.0.188.0
    6.0.182.0
    6.0.108.0
    5.2.193.0
    5.2.178.0
    5.2.157.0
    5.1.163.0
    5.1.151.0
    4.2.209.0
    4.2.207.0
    4.2.205.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    6.0.202.0
    6.0.202.0
    April 2011
    6.0.196.0
    6.0.181.0
    6.0.170.0
    6.0.132.0
    5.2.148.0
    5.2.130.0
    5.2.125.0
    5.2.110.0
    5.1.65.4
    5.1.64.0
    4.2.128.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    6.0.196.0
    6.0.199.4
    6.0.199.0 (pulled from CCO)
    6.0.196.0
    6.0.188.0
    6.0.182.0
    6.0.108.0
    5.2.193.0
    5.2.178.0
    5.2.157.0
    5.1.163.0
    5.1.151.0
    4.2.209.0
    4.2.207.0
    4.2.205.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    6.0.102.0
    6.0.105.0
    15 July 2010
    6.0.181.0
    6.0.170.0
    6.0.132.0
    5.2.148.0
    5.2.130.0
    5.2.125.0
    5.2.110.0
    5.1.65.4
    5.1.64.0
    4.2.128.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    6.0.181.0
    6.0.196.0
    6.0.188.0
    6.0.182.0
    6.0.108.0
    5.2.193.0
    5.2.178.0
    5.2.157.0
    5.1.163.0
    5.1.151.0
    4.2.207.0
    4.2.205.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    6.0.101.0
    6.0.103.0
    17 Feb 2010
    6.0.170.0
    6.0.132.0
    5.2.148.0
    5.2.130.0
    5.2.125.0
    5.2.110.0
    5.1.65.4
    5.1.64.0
    4.2.128.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    6.0.170.0
    6.0.188.0
    6.0.182.0
    6.0.108.0
    5.2.193.0
    5.2.178.0
    5.2.157.0
    5.1.163.0
    5.1.151.0
    4.2.207.0
    4.2.205.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    6.0.97.0
    6.0.97.0
    8 Nov 2009
    6.0.132.0
    5.2.148.0
    5.2.130.0
    5.2.125.0
    5.2.110.0
    5.1.65.4
    5.1.64.0
    4.2.128.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    6.0.132.0
    6.0.182.0
    6.0.108.0
    5.2.178.0
    5.2.157.0
    5.1.163.0
    5.1.151.0
    4.2.205.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    6.0.85.0
    6.0.85.0
    11 June 2009
    5.2.130.0
    5.2.125.0
    5.2.110.0
    5.1.65.4
    5.1.64.0
    4.2.128.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    5.2.148.0
    5.2.193.0
    5.2.178.0
    5.2.157.0
    5.1.151.0
    5.0.148.2
    5.0.148.0
    4.2.207.0
    4.2.205.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    5.2.100.0
    5.2.100.0
    25 June 2009
    5.2.130.0
    5.2.125.0
    5.2.110.0
    5.1.65.4
    5.1.64.0
    5.0.72.0
    5.0.56.2
    5.0.56.0
    4.2.128.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    5.2.130.0
    5.2.178.0
    5.2.157.0
    5.1.151.0
    5.0.148.2
    5.0.148.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    5.2.91.0
    5.2.91.0
    21 Feb 2009
    5.2.125.0
    5.2.110.0
    5.1.65.4
    5.1.64.0
    5.0.72.0
    5.0.56.2
    5.0.56.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    5.2.125.0
    5.2.178.0
    5.2.157.0
    5.1.151.0
    5.0.148.2
    5.0.148.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    5.2.91.0
    5.2.91.0
    10 Feb 2009
    5.2.110.0
    5.1.65.4
    5.1.64.0
    5.0.72.0
    5.0.56.2
    5.0.56.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    5.2.110.0
    5.2.157.0
    5.1.151.0
    5.0.148.2
    5.0.148.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    5.2.91.0
    5.2.91.0
    24 Nov 2008
    5.1.64.0
    5.0.72.0
    5.0.56.2
    5.0.56.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.1
    RHEL 5.0
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    5.1.65.4
    5.1.163.0
    5.1.151.0
    5.0.148.2
    5.0.148.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    5.1.35.0
    5.1.35.0
    9 Jan 2009
    5.1.64.0
    5.0.72.0
    5.0.56.2
    5.0.56.0
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.x
    RHEL 5.x
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    5.1.64.0
    5.1.151.0
    5.0.148.2
    5.0.148.0
    4.2.176.0
    4.2.173.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    5.1.30.0
    5.1.30.0
    21 July 2008
    5.0.56.2
    5.0.56.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    Windows 2003 SP2 32-bit
    RHEL 5.1
    RHEL 5.0
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    5.0.72.0
    5.0.148.2
    5.0.148.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    4.1.185.0
    4.1.171.0
    4.0.38.0
    Not Applicable
    5 Aug 2008
    5.0.56.2
    5.0.56.0
    4.2.62.11
    4.2.62.0
    4.1.91.0
    4.1.83.0
    Windows 2003 SP2 32-bit
    RHEL 5.1
    RHEL 5.0
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    5.0.56.2
    5.0.148.0
    4.2.61.0
    4.1.x.x
    4.0.33.0
    Not Applicable
    14 Apr 2008
    5.0.56.0
    4.2.62.11
    4.2.62.0
    4.1.91.0
    4.1.83.0
    Windows 2003 SP2 32-bit
    RHEL 5.0
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    5.0.56.0
    5.0.148.0
    4.2.61.0
    4.1.x.x
    4.0.32.0
    Not Applicable
    16 Feb 2008
    4.2.62.11
    4.2.62.0
    4.1.91.0
    4.1.83.0
    Windows 2003 SP2 32-bit
    RHEL 5.0
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    4.2.128.0
    4.2.207.0
    4.2.205.0
    4.2.176.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    4.1.185.0
    4.1.171.0
    4.0.216.0
    4.0.206.0
    4.0.179.11
    4.0.179.8
    4.0.155.0
    3.1.43.0
    Not Applicable
    13 May 2009
    4.2.110.0
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    4.1.91.0
    4.1.83.0
    4.0.100.0
    4.0.97.0
    4.0.96.0
    4.0.87.0
    4.0.81.0
    4.0.66.0
    Windows 2003 SP2 32-bit
    RHEL 4.0
    RHEL 5.0 (5.1 and later no supported)
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    4.2.110.0
    4.2.176.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    4.1.185.0
    4.1.171.0
    4.0.216.0
    4.0.206.0
    4.0.179.11
    4.0.179.8
    4.0.155.0
    3.1.42.0
    Not Applicable
    29 Sep 2008
    4.2.97.0
    4.2.81.0
    4.2.62.11
    4.2.62.0
    4.1.91.0
    4.1.83.0
    4.0.100.0
    4.0.97.0
    4.0.96.0
    4.0.87.0
    4.0.81.0
    4.0.66.0
    Windows 2003 SP2 32-bit
    RHEL 4.0
    RHEL 5.0
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    4.2.97.0
    4.2.176.0
    4.2.130.0
    4.2.112.0
    4.2.99.0
    4.2.61.0
    4.1.185.0
    4.1.171.0
    4.0.216.0
    4.0.206.0
    4.0.179.11
    4.0.179.8
    4.0.155.0
    3.1.38.0
    Not Applicable
    3 Jun 2008
    4.2.81.0
    4.2.62.11
    4.2.62.0
    4.1.91.0
    4.1.83.0
    4.0.100.0
    4.0.97.0
    4.0.96.0
    4.0.87.0
    4.0.81.0
    4.0.66.0
    Windows 2003 SP2 32-bit
    RHEL 4.0
    RHEL 5.0
    Windows/RHEL on ESX 3.0.1 and above
    No support for 64 bit
    4.2.81.0
    4.2.99.0
    4.2.61.0
    4.1.185.0
    4.1.171.0
    4.0.216.0
    4.0.206.0
    4.0.179.11
    4.0.179.8
    4.0.155.0
    3.1.36.0
    Not Applicable
    17 Mar 2008
    4.2.62.11
    4.2.62.0
    4.1.91.0
    4.1.83.0
    4.0.100.0
    4.0.97.0
    4.0.96.0
    4.0.87.0
    4.0.81.0
    4.0.66.0
    Windows 2003 SP2 32-bit
    RHEL 4.0
    RHEL 5.0
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    4.2.62.11
    4.2.61.0
    4.1.185.0
    4.1.171.0
    4.0.216.0
    4.0.206.0
    4.0.179.11
    4.0.179.8
    4.0.155.0
    3.1.35.0
    Not Applicable
    25 Jan 2008
    4.2.62.0
    4.1.91.0
    4.1.83.0
    4.0.100.0
    4.0.97.0
    4.0.96.0
    4.0.87.0
    4.0.81.0
    4.0.66.0
    Windows 2003 SP2 32-bit
    RHEL 4.0 Update 5
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    4.2.62.0
    4.2.61.0
    4.1.185.0
    4.1.171.0
    4.0.216.0
    4.0.206.0
    4.0.179.11
    4.0.179.8
    4.0.155.0
    3.1.35.0
    Not Applicable
    9 Nov 2007
    4.1.91.0
    4.1.83.0
    4.0.100.0
    4.0.97.0
    4.0.96.0
    4.0.87.0
    4.0.81.0
    4.0.66.0
    Windows 2003 SP2 32-bit
    RHEL 4.0 Update 5
    Windows/ RHEL on ESX 3.0.1 and above
    No support for 64 bit
    http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN7_0_172.html
    Cheers!
    Rob
    PS: +5 to my friend Leo using the invisible Stars

  • Version compatibility  of 10G Application Server 10.1.2.0.2  with  JDK 1.5.

    hi buddies,
    I want to know that whether
    10G Application Server 10.1.2.0.2 with JDK 1.5. is Version compatibility
    pls do send ur replies if known to you.

    Hi ,
    As far as I know AS 10.1.2.0.2 is Not certified with JDK 1.5.
    Please see below some links where you can double-check this
    1. OC4J with JDK 1.5 JSP compilation error
    2. http://docs.huihoo.com/oracle/docs/B14099_19/web.1012/b14011/chap1.htm
    "Only the JDK 1.3.1 and JDK 1.4 compilers are supported and certified by OC4J. It is possible to specify an alternative compiler by adding a <java-compiler> element to the server.xml file, and this might provide a workaround for the "classes not in packages" issue, but no other compilers are certified or supported by Oracle for use with OC4J."
    3. "Certified JDKs" from
    http://www.oracle.com/technology/software/products/ias/files/as_certification_r2_101202.html
    BR,
    Mihai

  • Version compatibility for installing WLS and ADR for ADF 11.1.2.0

    Hi,
    Can anyone pls let me know what versions of Weblogic server, Application Development Runtime (ADR) is required to install Oracle JDeveloper 11.1.2.0
    B'coz currently I am trying to install Weblogic server, ADR and ADF separately and try to deploy and publish an application in ADF 11.1.2.0 verison.
    I am trying this for the past 4 days, but still can't deploy an application successfully in ADF 11.1.2.0 version. Pls let me know the version compatibility.
    Thanks,
    Aparna

    Hi John,
    Even I saw the link that u had mentioned. From where can I install these ?
    I had downloaded WLS 10.3.5 and ADR 11.1.1.5 separately. But from where do I install the patch ?? I didn't find a proper source to download.
    Pls help.
    Thanks,
    Aparna

  • NWDI version compatibility

    Hi,
    Does anyone know if there are any version compatibility constraints developing Java WebDynpro applications on an NWDI (WAS6.40) for deployment on a WAS7.00 instance (e.g. JDK's)?
    I've yet to find a general recommendation similar to that seen for SLD (i.e. keep in line with the highest WAS version on the estate) or any clear documentation on version compatibility across WAS stacks with respect to NWDI.
    We have a highly complex landscape with multiple component/ product versions, and we'd prefer to have a singel central NWDI instance, but I'm not sure if this is practical and/ or possible.
    Any pointers/ documentation/ comments gratefully received
    Cheers
    Neil

    While I can't remember where I've seen it, SAP does recommend that the DI always be kept patched to the latest levels, regardless of what version your landscape (or pieces thereof ) is at.
    So, as long as your DI is at patched to at least the same level as your most 'advanced' system, you should not have any problem.  You should also match your Developer Studio to the same level as your target system to avoid using any plug-ins that offer features not offered by the eventual runtime system.  Yes, the required libraries will be ok (as long as you configure the SLD and the associated track correctly), but the Developer Studio itself needs to be matched up.
    Hope that makes sense.

  • Photoshop Extended version compatability

    I have Photoshop CS3 Extended on both PC (Windows XP) and Mac (OS X Leopard). I'm able to upgrade the PC to CS5 Extended but not the Mac.
    My questions are:
    1 - Will Photoshop CS5 extended work on Windows XP?
    2 - Are CS3 and CS5 backwards compatible - if I work on a document in PC CS5 will the Mac CS5 version be able to open it? I know there will be some things that would not translate backwards, such as Puppet Warp and some of the newer masking and layers features, but I'd still like to be able to work on more basic functions of masking, cloning, etc. on both computers.
    Thanks for any help,
    Marcy

    Noel Car boni wrote:
    For the most part, a document saved from Photoshop CS5 will be no problem to open in CS3.  There's a "Maximize Compatibility" setting in Edit - Preferences - File Handling section that you'll want to set to "Always".
    -Noel
    My take is that the compatibility setting should be set based on the kind of work one does.  I have it set to  "Never".  When you check this setting ON you tell Photoshop to save along with all your layers another entity, which is a flattened version of the image. This, makes every PSD file you save larger by a non trival amount.
    So this setting should have no effect regarding Photoshop to Photoshop version compatibility. All Photoshop versions understand layers and do not need a flattened version.  It's intended to maximize the compatibility between Photoshop and any other program  that does not know about  layers but reads PSD files. If you have many of your PSD files going to, for example,  Lightroom or Premiere then set it to "Always". If not, you can set it to "Ask" or "Never" and save yourself a lot of storage space.
    Paulo

  • Re: (forte-users) C++ version compatibility question. Fortev30L2 on D

    Dirk:
    I ran into a similar problem. I added an other flag to my fcompile script and
    it seems to be working fine, your mileage may vary. The flag was
    -cflags "-oldcxx only"
    Dwayne Kryger
    "Haben, Dirk" <[email protected]> on 08/25/99 02:09:16 AM
    To: "'Soapbox Forte Users'" <[email protected]>
    cc: (bcc: Dwayne Kryger/SEH)
    Subject: (forte-users) C++ version compatibility question. Forte v30L2 on
    Digital Unix 4 d and C++ version ???
    G'day Folxs
    Just installed Forte as a Simple Server on a Digital UNIX (v4.0d) box (being
    a VMSbot it was much easier than I thought). We want to use it to interface
    with an existing web client. The Forte part is to provide us a scalable
    access path to Oracle DBs on the VMS machine; already running Forte.
    I'm having trouble finding media that contains C++ v5.4.-006 for the Unix
    box. Does anyone know of/has used higher versions of C++ without too much
    drama? How about v5.7 or even v6.1? We will be using extensive C++
    interfacing to existing web pages!
    NB: The current web system client is compiled using EGCS 2.91.66.
    TIA,
    /[:-)irK
    Dirk Haben, Perth WA
    For the archives, go to: http://lists.sageit.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: [email protected]

    Dirk:
    I ran into a similar problem. I added an other flag to my fcompile script and
    it seems to be working fine, your mileage may vary. The flag was
    -cflags "-oldcxx only"
    Dwayne Kryger
    "Haben, Dirk" <[email protected]> on 08/25/99 02:09:16 AM
    To: "'Soapbox Forte Users'" <[email protected]>
    cc: (bcc: Dwayne Kryger/SEH)
    Subject: (forte-users) C++ version compatibility question. Forte v30L2 on
    Digital Unix 4 d and C++ version ???
    G'day Folxs
    Just installed Forte as a Simple Server on a Digital UNIX (v4.0d) box (being
    a VMSbot it was much easier than I thought). We want to use it to interface
    with an existing web client. The Forte part is to provide us a scalable
    access path to Oracle DBs on the VMS machine; already running Forte.
    I'm having trouble finding media that contains C++ v5.4.-006 for the Unix
    box. Does anyone know of/has used higher versions of C++ without too much
    drama? How about v5.7 or even v6.1? We will be using extensive C++
    interfacing to existing web pages!
    NB: The current web system client is compiled using EGCS 2.91.66.
    TIA,
    /[:-)irK
    Dirk Haben, Perth WA
    For the archives, go to: http://lists.sageit.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: [email protected]

  • WAP54G Version compatibility

    I am trying to create a wireless bridge between a network with ip's 198.1.1.xxx (this network has the gateway) to a network with ip's 198.1.2.xxx -  so that it can access the internet thru the gateway).  Both AP's are WAP54G set to bridge mode. Both are configured identically except for the IP numbers.  SSID broadcast disabled and security off.  From everything I have read, I should be able to ping (example 4.2.2.2) from 198.1.2.xxx - but cannot.  The only difference I can see it that one of the WAP54G's is version 2 and the other is Version 3.  Both have firmware 3.0.4.
    Question: Can anyone confirm that I can or cannot create a wireless bridge with differing versions of the same device?
    As a plan B, I have on order a WET200.  Should I have two on order to act as a matched pair as the WAP54G's had to be?
    Thank you.
    Craig

    I work with psd, indd and illu/eps files. I've heard the weird argument that "cause of new features it's not possible to be version compatible, but that's down right silly. Text on top of an image should be readable in any version. Even with a copule of adjustment layers it should be no problems with version compatibility. That Adobe choose to lock and force is another story. I guess I will be sticking to my CS6 version in the years to come. I paid a lot of money for that Master Collection. I also corresponde files with many CS4 users on the client side.

  • WLC version support on 6509 WiSM

    Anyone know what WLC version is supported on a WiSM running in a 6509?
    Currently we are running 4.2.61.0 and i have noticed on the Cisco website that its up to verison 6.x.x.
    How can i find out what version our 6509 will support?

    The WiSM is supported with a sup720 running 12.2(18)SXF2 or higher, any SXH, or any SXI version.  As long as the sup720 is running any of these versions you can run any of the WiSM images posted in the software download page.  Any specific interoperabiltiy issues would be listed in the release notes for the controllers.

  • WCS and WLC versions for Cisco 3600 WAP

    Hi,
    I got a few Cisco Aironet 3602i. The minimum WLC version to support these is 7.1.91.0. I am planning to upgrade to 7.2.103.0. The minimum WCS version to support these WAP is 7.0.220.0 and the next available 7.0.230.0. Checking the release notes for both of these WCS versions, there is no mention of support for WLC versions listed above.
    http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN7_0_230.html#wp152663
    Am I missing something here ? What versions would be required on WCS and WLC to make all the three entities (WLC, WCS, WAP) inter-operable ?
    Thanks,
    Regards, Rashid.

    Thanks Scott.
    Table-5 from your link indicates WCS 7.0.230.0 support for WLC 7.1.91.0, although release notes for WCS fails to mention this. I think thats the only option in the our existing WCS based network then. Other option being to upgrade to NCS.
    The NCS page http://www.cisco.com/en/US/products/ps6305/index.html indicates it will be offered to existing WCS customers when releases. Would we be required to pay for the product or both product and licenses or none ?

  • Is WLC Version 6.0.188.0 Eos/Eol?

    Is WLC Version 6.0.188.0 Eos/Eol?
    I cannot find anything stating that it is or is not.

    Yes, long time ago...
    Only 3 software version is supported at the moment
    7.0.250.0 (7.0MR5)
    7.4.121.0 (7.4MR2)
    7.6.110.0 (7.6MR1)
    https://supportforums.cisco.com/document/12098021/aireos-software-deferrals-february-2014
    HTH
    Rasika
    **** Pls rate all useful responses. Each time you rate a response Cisco will donate $1 to Kiva ****

  • RoboHelp Version Compatibility

    Hello everybody from Greece,
    I want to ask about version compatibility. I've got RoboHelp
    HTML 5.0.2 and my client has RoboHelp HTML 3.1. He asks if I can
    compile his project, but I wnt to know if he will be able to work
    with the project that I will work with in version 5.0.2.
    Is there a way to save the project to an older version?
    Is there a compatibility problem in general?
    Is there going to be a problem if I compile the project in
    the newer version? (Will he see any differences?)
    Any help would be appreciated.
    Thanks in advance.

    Hi Tansou and υποδοχή,
    You should be able to open up the X3.1 in X5.02 without a
    problem. X5 will preserve all the feature used in X3.1. Are you
    compiling HTML Help? My guess is that you won't see any difference
    in the output when you compile.
    However, the problem comes when you try and do this the other
    way around. Robohelp is not backward compatible. So you won't be
    able to pass a modified project back to your client. Rick the
    robowizard has a few tricks to help with backward compatibility if
    you don't mind going under the hood. However, not sure if this
    works with X3.1 jumping to X3.1.
    What type of output are you generating?
    Hope that helps
    Craig

  • AP - WLC - WCS - Compatibility

    I'm upgrading a WLC4124 wireless controller to a WLC4402 - 50 and hope to use the existing AP1030's I have already installed. I have new AIR-LAP1131AG-A-K9 models to add to the existing AP1030's. I also would like to control this with WCS. My question is where do I find compatibility information with regards to what version of WCS, WLC code(?) and AP's / AP modes (L2,L3) work together?

    you can find controller / wcs version in the WCS config document.
    http://www.cisco.com/en/US/products/ps6305/products_installation_and_configuration_guides_list.html

  • Upgrading from Prime 1.2 to 1.3 - What about WLC version?

    If I upgrade to prime v1.3, from v1.2, am I required to upgrade my WLC controllers to v7.4, or will my current version (v7.2) work fine?
    Thanks.

    No upgrade to your WLCs is required. Any v7.0 or later should be fine. See the Release Notes here for details.

  • Adobe Reader version compatability

    I have a PDF that is compatible with Adobe reader 11.0.2 and I have version 11.0.5 currently installed.  Version 11.0.5 won't open the PDF.  How can I open this PDF? Do I need to specifically download version 11.0.2?
    Thanks for any help!

    I can open Reader on its own.  I am trying to download a grant application and when I click on the link that is supposed to open it through Reader it says that Reader is not compatible and that I need to install the latest version of the PDF viewer.  When I click on the link to install the latest version it send me to the Reader installation.  I have installed and tried reinstalling Reader and it hasn't helped.  In the instructions for the grant it only talks about compatability for versions up to 11.0.2 that's why I wasn't sure if maybe the problem is because I have 11.0.5. 

Maybe you are looking for

  • ASA 5505 - 2 Internet Connections, Problems with the Default Route

    Hey there, i have a Problem at a Customer Site at the moment. The customer uses an ASA 5505 with two internet connections attached to it. On the first connection (which is the only one in use at the moment) he has some Static-PAT's from Outside to In

  • Microsoft Report Viewer Print Button is not Displayed in FireFox. Why?

    Hi, I have developed a reporting web site using asp.net. To view the reports I have used the microsoft report viewer. In IE it works fine. But when im goint to run this web site in Fire Fox some buttons (print button, search button) in the ReportView

  • How to embed an image in swf at run time?

    Hi all, I have created an Image component in flash which is having a "imageSource" paramter, where in a user can provide the path of his/her image(both from web or from  harddisk). I want that image to be compiled with the swf. how can i do that?....

  • How to include a 2D Barcode in Powerbuilder 11.1 ?

    Hi All, Our labeling application is in PB11 and we are unable to include the 2D barcode in PB 11. When i searched in google ,it seems like we need to consume the .NET third party dll and runtime dynamically set the font from the third party. Is there

  • Call fails after last update

    Can anyone help me, after the last update from Apple to my iphone 3g I get call fail after call fail. It is getting embarassing at work where I rolled these phone out.