UCCX 5.0 - 8.0 using pre-upgrade tool

Hi,
We're upgrading from 5.0(2) to 8.0. We've used the Pre-Upgrade Tool to create a TAR file on the production UCCX. From the replacement server we've selected "Upgrade from a previous UCCX release". The Pre-Upgrade Tool ran without issue and the log file shows no errors.
The status message shows: "Enter a valid backup file"
We know the sftp server is setup correctly and the user credentials are correct.
Any feedback welcome.Many thanks.

The Pre-Upgrade Tool also have the option to verify the backup file. Try running the verification and see if it works:
(page 16 - Upgrade guide)
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_8_0/installation/guide/uccx801ig.pdf
Also what are the exact UCCX versions 5.0(2) SR? and going to 8.0(1) or 8.0(2)? there is one upgrade tool for 8.0(1) and another for 8.0(2), make sure you are running the right one.
Pablo

Similar Messages

  • CCX 7.0 pre-upgrade tool ERROR

    Dear ALL,
    I'm planning to upgrade my CCX 7.0 to the latest version,  I know that  I need to  take the backup  with pre-upgrade tool,
    But When  I enter  details of SFTP and  click to take a  backup  I'm getting this error:
    Cisco Unified CCX backup pre-check operation failed. Check the pre-upgrade tool log for more details.
    Please see below  the log file.
    May 4, 2015 2:12:07 PM com.cisco.ccx.w1.log.PUTLogger getLogger
    INFO: ############# Cisco Unified CCX W1 Pre-Upgrade Tool Logger #############
    May 4, 2015 2:12:07 PM com.cisco.ccx.w1.export.ui.PreUpgradeTool main
    INFO: Creating the Pre Upgrade Tool (1.0 Build 108)
    May 4, 2015 2:12:08 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane init
    WARNING: Pre-Upgrade Tool status colors C8D2DC, F3F3FF
    May 4, 2015 2:12:08 PM com.cisco.ccx.w1.export.ui.PreUpgradeTool initStatus
    INFO: Initializing the status windows
    May 4, 2015 2:12:29 PM com.cisco.ccx.w1.export.ui.WelcomeScreen jButton0ActionActionPerformed
    INFO: CCX Version is 7.0(1)_Build168
    May 4, 2015 2:15:49 PM com.cisco.ccx.w1.export.ui.SFTPScreen jButton0ActionActionPerformed
    INFO: Checking the SFTP connection. Server = 10.100.0.93 , UserName = cisco, Password = 0c52000a73
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ui.ProgressScreen startBackup
    INFO: Starting the backup process ...
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ui.ProgressScreen startBackup
    INFO: Initializing the Export manager thread.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ui.SFTPScreen jButton0ActionActionPerformed
    WARNING: Closing the SFTP connection.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager <init>
    INFO: W1 Pre-Upgrade Tool version is 1.0 Build 108
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager <init>
    INFO: Instantiating the W1 Upgrade ExportManager.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager execute
    INFO: Starting the W1 Upgrade backup operation.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager execute
    INFO: ExportManager arguments are, {BackupLocation [Server = 10.100.0.93, Path = \, UserName = cisco, password = *******, Type = SFTP], StatusListener = com.cisco.ccx.w1.export.ui.W1StatusListener@d57bcb }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.CCXUtil printRuntimeInfo
    INFO:
    ===========================
    Available Processors = 2
    JVM Max Memory = 493.06 MB
    JVM Total Memory = 106.94 MB
    JVM Free Memory = 83.61 MB
    ===========================
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager init
    INFO: W1 Config contents [ ConfigMap : {$$Backup Data Type=W1 Pre Upgrade Backup, JRE Version=1.6.0_13, PUT Version=1.0 Build 108, OS Version=Windows 2003,x86,5.2, Backup Start Time=Mon May 04 14:15:57 AZST 2015, User Name=Administrator}
     ParamMap : {}
     AppProperty : {com.cisco.ccx.w1.proxy.enabled=true, w1.stage.alarm=config\alarm, w1.put.instance.nwerr.skip=true, w1.stage.logs=logs, w1.stage.recordings=recordings, com.cisco.ccx.w1.put.retry=5, com.cisco.ccx.w1.put.colors=C8D2DC,F3F3FF, com.cisco.ccx.config.mgr.args=, w1.put.instance.port=13403, com.cisco.ccx.w1.put.lnf=com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel, w1.stage.jtrace=config\jtapi, w1.stage.database=db, w1.stage.config=config, com.cisco.ccx.w1.config.properties=CustomFileClasspath.properties,currency.properties,SubsystemRmCm.properties,TTSProvider.properties,CustomStep.properties,CustomSubsystem.properties,SubsystemEDBS.properties,locale.properties,application.MIVR.properties,system.properties, com.cisco.ccx.w1.cl.timeout=120, com.cisco.ccx.w1.stage.dir=C:\W1-STI, w1.stage.license=7xLicense, w1.stage.calabrio=cl}
     Backup dir : C:\W1-STI ]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager isDefaultLocale
    INFO: checking if the locale is set to the default locale en_US)
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager isDefaultLocale
    INFO: The current locale is ...en_US
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager isCCXVersionSupported
    INFO: CCX version  = 7.0(1)_Build168
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator <init>
    INFO: CVDCommunicator default constructor.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator getCVDPort
    INFO: Default CVD port set as 994
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator getCVDPort
    INFO: Querying  WIN registry on localhost to get the CVD Master listener port.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator getCVDPort
    INFO: CVD Master listener port string returned from registry = 994
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator getCVDPort
    INFO: Returning CVD Master listener port : 994
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator <init>
    INFO: ccxHost = /127.0.0.1 port = 994
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator openCVDSession
    INFO: Getting the socket input and output stream.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator openCVDSession
    INFO: Sending a CVD Open Session request.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendOpenSessionReq
    INFO: Sending {Req = OPEN_REQ, versionNbr = 1 , invokeID = 123 }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator openCVDSession
    INFO: Waiting for a CVD Open Session response.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 4 , Msg Type : OPEN_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processOpenSessionResponse
    INFO: Invoke ID : 123
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator openCVDSession
    INFO: Got the CVD Open Session response.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager initCVDCommunicator
    INFO: Initialized the CVDCommunicator
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendSvcSnapshotReq
    INFO: Sending {Req = ENABLE_SNAPSHOT_REQ,  service = CRS Cluster View Daemon }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 42 , Msg Type : ENABLE_SNAPSHOT_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Requested service : CRS Cluster View Daemon, service in response : CRS Cluster View Daemon
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Total service count : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.4, state : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.5, state : 0
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendSvcSnapshotReq
    INFO: Sending {Req = ENABLE_SNAPSHOT_REQ,  service = CRS Engine }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 29 , Msg Type : ENABLE_SNAPSHOT_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Requested service : CRS Engine, service in response : CRS Engine
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Total service count : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.4, state : 6
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.5, state : 0
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendSvcSnapshotReq
    INFO: Sending {Req = ENABLE_SNAPSHOT_REQ,  service = Cisco Desktop Recording Service }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 50 , Msg Type : ENABLE_SNAPSHOT_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Requested service : Cisco Desktop Recording Service, service in response : Cisco Desktop Recording Service
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Total service count : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.4, state : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.5, state : 0
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendSvcSnapshotReq
    INFO: Sending {Req = ENABLE_SNAPSHOT_REQ,  service = Cisco Desktop VoIP Monitor Service }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 53 , Msg Type : ENABLE_SNAPSHOT_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Requested service : Cisco Desktop VoIP Monitor Service, service in response : Cisco Desktop VoIP Monitor Service
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: Total service count : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.4, state : 2
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processSnapshotResponse
    INFO: IP Address : 172.30.30.5, state : 0
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkMaster
    INFO: Querying engine master and DB  publisher node.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendRegMasterListener
    INFO: Sending {Req = REG_MASTER_LISTENER, masterName = CRS Engine }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 16 , Msg Type : REG_MASTER_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processMasterResponse
    INFO: Master service name in the response : CRS Engine
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processMasterResponse
    INFO: Master IP address in the response : 172.30.30.4
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendRegMasterListener
    INFO: Sending {Req = REG_MASTER_LISTENER, masterName = CRS SQL Server - Historical }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 33 , Msg Type : REG_MASTER_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processMasterResponse
    INFO: Master service name in the response : CRS SQL Server - Historical
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processMasterResponse
    INFO: Master IP address in the response : 172.30.30.4
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkMaster
    INFO: Engine master node = 172.30.30.4, DB publisher = 172.30.30.4
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkLicense
    INFO: Validating the license info.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendChkoutLicenseRequest
    INFO: Sending {Req = CHECKOUT_LICENSE_REQ,  license = IVR_ENHANCED }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 18 , Msg Type : CHECKOUT_LICENSE_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicChkoutResponse
    INFO: Requested license : IVR_ENHANCED, License in response : IVR_ENHANCED
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicChkoutResponse
    INFO: License checkout : true
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendLicenseRequest
    INFO: Sending {Req = GET_LICENSE_REQ,  license = PRE_SEAT }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 14 , Msg Type : GET_LICENSE_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicenseResponse
    INFO: Requested license : PRE_SEAT, License in response : PRE_SEAT
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicenseResponse
    INFO: License Count : 5
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendChkoutLicenseRequest
    INFO: Sending {Req = CHECKOUT_LICENSE_REQ,  license = WARM_STANDBY }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 18 , Msg Type : CHECKOUT_LICENSE_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicChkoutResponse
    INFO: Requested license : WARM_STANDBY, License in response : WARM_STANDBY
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicChkoutResponse
    INFO: License checkout : true
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator sendLicenseRequest
    INFO: Sending {Req = GET_LICENSE_REQ,  license = IVR_PORTS }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processResponse
    INFO: Response header is :  { Msg Len : 15 , Msg Type : GET_LICENSE_CONF }
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicenseResponse
    INFO: Requested license : IVR_PORTS, License in response : IVR_PORTS
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator processLicenseResponse
    INFO: License Count : 10
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkLicense
    INFO: License Package = Cisco Unified CCX Premium, SeatCount = 5, HA = true, IVR Ports = 10
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkLicense
    INFO: ## License package is Express
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.cvd.CVDCommunicator close
    INFO: Closing the CVD connection.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.export.ExportManager checkProxy
    INFO: Checking the proxy configurations.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isManualProxyEnabled
    INFO: Proxy Enable Reg Value : dword:00000000
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isManualProxyEnabled
    INFO: Manual proxy NOT enabled.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isAutoProxyEnabled
    INFO: Proxy Auto Config URL : null
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isAutoProxyEnabled
    INFO: Proxy Auto Config NOT enabled.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Checking the Java proxy settings.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "http"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "https"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "ftp"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "gopher"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Querying applicable proxies for the protocol => "socket"
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Applicable Proxies : [DIRECT]
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.util.proxy.ProxyUtil isJavaProxyEnabled
    INFO: Java Proxy NOT enabled.
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter <clinit>
    INFO: Cisco Unified CCX root directory : c:\progra~1\wfavvid
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter isMMStarted
    INFO: Manager Manager is NOT started
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Creating the Windows URL classloader params
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter createParams
    INFO: Raw URLClassloaderParams : "Editor Class Loader";{0}\CiscoManagerManagerImpl.jar;com.cisco.manager.impl.ManagerManagerImpl;-property;{1};{2};{3};{4};-rootdir;{5};com.cisco.ccx.w1.config.mgr.MMInitLock
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: URLClassloaderParams : "Editor Class Loader", c:\progra~1\wfavvid\lib\CiscoManagerManagerImpl.jar, com.cisco.manager.impl.ManagerManagerImpl, -property, application.MCET.properties, -nokeepalive, -rootdir, c:\progra~1\wfavvid, com.cisco.ccx.w1.config.mgr.MMInitLock
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Redirecting the ManagerManagerImpl output
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Invoking the ManagerManagerImpl using the URLClassloader
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.URLClassLoader main
    INFO: Invoking the URLClassLoader
    May 4, 2015 2:15:57 PM com.cisco.ccx.w1.config.mgr.URLClassLoader convertToURL
    INFO: *** Adding classpath: c:\progra~1\wfavvid\lib\CiscoManagerManagerImpl.jar, URL = file:/c:/progra~1/wfavvid/lib/CiscoManagerManagerImpl.jar
    May 4, 2015 2:15:58 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: ManagerManagerImpl initialization completed and waiting for the MMInitLock(Startable class to get invoked)
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.config.mgr.MMInitLock start
    INFO: Inside the startable class
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.config.mgr.MMInitLock start
    INFO: Notifying the object waiting for the mutex
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Config framework started completely.
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.config.mgr.ConfigManagerStarter initMM
    INFO: Restoring the Outputstream if -redirect is enabled
    May 4, 2015 2:15:59 PM com.cisco.ccx.w1.export.cl.CLMigration getAllNodeIPs
    INFO: Cluster IP addresses are, 172.30.30.5, 172.30.30.4
    May 4, 2015 2:16:00 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: CCX Node with IP address 172.30.30.5 is reachable.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: CCX Node with IP address 172.30.30.4 is reachable.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: Getting the node config for UCCX1
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: Local node config is NodeConfig[schema=NodeConfig,time=Mon Nov 09 12:55:40 AZT 2009,recordId=-668476853,desc=,node id=1,computer name=UCCX1,ip addresses=172.30.30.4,model=7816I02,nodeGuid={BDF658EF-26F2-4871-8FE4-C508A8AD387E},osArchitecture=X86-based PC,osName=Microsoft Windows Server 2003,osVersion=502,vendor=IBM,installtime=Mon Nov 09 12:55:03 AZT 2009,upgrade time=Mon Nov 09 12:55:03 AZT 2009,ccm colocated=false,deployment type=1,harddisk size=236472,install path=C:\Program Files\wfavvid\]
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: Getting all engine node ids.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager startConfigManager
    INFO: Engine node ids = 2,1
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getInstance
    INFO: Creating the DB Util instance.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: Loading the net.sourceforge.jtds.jdbc.Driver
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: DB Publisher IP is 172.30.30.4
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: DB CRA Url =  jdbc:jtds:sqlserver://172.30.30.4:4433/db_cra
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: DB CRA Repository Url =  jdbc:jtds:sqlserver://172.30.30.4:4433/db_cra_repository
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil <init>
    INFO: FCRasSvr Url =  jdbc:jtds:sqlserver://172.30.30.4:4433/FCRasSvr
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Getting connection for jdbc:jtds:sqlserver://172.30.30.4:4433/db_cra
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Obtaining new Connection.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getDbSpaceUsed
    INFO: DB Spaced used for db_cra is 479117312 bytes
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager checkSpace
    INFO: Max allowed DB space=10.00 GB, Used db_cra space=456.92 MB
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Getting connection for jdbc:jtds:sqlserver://172.30.30.4:4433/db_cra_repository
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Obtaining new Connection.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getDbSpaceUsed
    INFO: DB Spaced used for db_cra_repository is 9175040 bytes
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Getting connection for jdbc:jtds:sqlserver://172.30.30.4:4433/FCRasSvr
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getConnection
    INFO: Obtaining new Connection.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.db.util.DatabaseUtil getDbSpaceUsed
    INFO: DB Spaced used for FCRasSvr is 6938624 bytes
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager checkSpace
    INFO: Estimating the recording file size.
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.cl.CLMigration getAllNodeIPs
    INFO: Cluster IP addresses are, 172.30.30.4, 172.30.30.5
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.cl.CLMigration getRecordingFolder
    INFO: Recording file location for the node 172.30.30.4 is C:\Program Files\Cisco\Desktop_Audio
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.cl.CLMigration getRecordingFolder
    INFO: Recording folder UNC path for node 172.30.30.4 is \\172.30.30.4\C$\Program Files\Cisco\Desktop_Audio
    May 4, 2015 2:16:01 PM com.cisco.ccx.w1.export.ExportManager getRecSpace
    INFO: Recording folder (*.Raw) size for IP 172.30.30.4 is 0.00 Bytes
    May 4, 2015 2:16:43 PM com.cisco.ccx.w1.export.ExportManager preCheck
    SEVERE: Error while doing Cisco Unified CCX backup pre-check
    com.cisco.lang.IllegalArgumentException: errCode=-1; nested exception is:
        com.ice.jni.registry.RegistryException: Registry API Error 53, '' - 'RegConnectRegistry()'
        at com.cisco.util.RegistryProperties.<init>(RegistryProperties.java:474)
        at com.cisco.util.RegistryProperties.<init>(RegistryProperties.java:408)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRegHandle(CLConfigUtil.java:300)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRecordingsLocation0(CLConfigUtil.java:221)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRecordingsLocation(CLConfigUtil.java:183)
        at com.cisco.ccx.w1.export.cl.CLMigration.getRecordingFolder(CLMigration.java:493)
        at com.cisco.ccx.w1.export.ExportManager.getRecSpace(ExportManager.java:926)
        at com.cisco.ccx.w1.export.ExportManager.checkSpace(ExportManager.java:995)
        at com.cisco.ccx.w1.export.ExportManager.preCheck(ExportManager.java:593)
        at com.cisco.ccx.w1.export.ExportManager.process(ExportManager.java:371)
        at com.cisco.ccx.w1.export.ExportManager.execute(ExportManager.java:263)
        at com.cisco.ccx.w1.export.ui.ProgressScreen$1.run(ProgressScreen.java:80)
        nested stack trace is:
        com.ice.jni.registry.RegistryException: Registry API Error 53, '' - 'RegConnectRegistry()'
        at com.ice.jni.registry.RegistryKey.connectRegistry(Native Method)
        at com.cisco.util.RegistryProperties.<init>(RegistryProperties.java:441)
        at com.cisco.util.RegistryProperties.<init>(RegistryProperties.java:408)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRegHandle(CLConfigUtil.java:300)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRecordingsLocation0(CLConfigUtil.java:221)
        at com.cisco.ccx.w1.export.cl.CLConfigUtil.getRecordingsLocation(CLConfigUtil.java:183)
        at com.cisco.ccx.w1.export.cl.CLMigration.getRecordingFolder(CLMigration.java:493)
        at com.cisco.ccx.w1.export.ExportManager.getRecSpace(ExportManager.java:926)
        at com.cisco.ccx.w1.export.ExportManager.checkSpace(ExportManager.java:995)
        at com.cisco.ccx.w1.export.ExportManager.preCheck(ExportManager.java:593)
        at com.cisco.ccx.w1.export.ExportManager.process(ExportManager.java:371)
        at com.cisco.ccx.w1.export.ExportManager.execute(ExportManager.java:263)
        at com.cisco.ccx.w1.export.ui.ProgressScreen$1.run(ProgressScreen.java:80)
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ExportManager destroy
    INFO: Cisco Unified CCX Backup destroy called.
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ExportManager destroy
    INFO: Final W1 Config contents [ ConfigMap : {License Seat Count=5, Unified CCX Engine Master=172.30.30.4, Unified CCX Engine Count=2, PUT Run On=172.30.30.4, Engine Node IDs=2,1, PUT Version=1.0 Build 108, OS Version=Windows 2003,x86,5.2, Node ID=1, User Name=Administrator, License Package Type=Cisco Unified Express, Unified CCX Rec Nodes=172.30.30.4, 172.30.30.5, IVR Port Count=10, License Package=Cisco Unified CCX Premium, $$Backup Data Type=W1 Pre Upgrade Backup, JRE Version=1.6.0_13, Unified CCX Mon Nodes=172.30.30.4, 172.30.30.5, Unified CCX Nodes=172.30.30.4, 172.30.30.5, Backup Start Time=Mon May 04 14:15:57 AZST 2015, Host Name=UCCX1, Unified CCX DB Publisher=172.30.30.4}
     ParamMap : {Unified CCX Engine Count=2, node.id=1, IVR Port Count=10}
     AppProperty : {com.cisco.ccx.w1.proxy.enabled=true, w1.stage.alarm=config\alarm, w1.put.instance.nwerr.skip=true, w1.stage.logs=logs, w1.stage.recordings=recordings, com.cisco.ccx.w1.put.retry=5, com.cisco.ccx.w1.put.colors=C8D2DC,F3F3FF, com.cisco.ccx.config.mgr.args=, w1.put.instance.port=13403, com.cisco.ccx.w1.put.lnf=com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel, w1.stage.jtrace=config\jtapi, w1.stage.database=db, w1.stage.config=config, com.cisco.ccx.w1.config.properties=CustomFileClasspath.properties,currency.properties,SubsystemRmCm.properties,TTSProvider.properties,CustomStep.properties,CustomSubsystem.properties,SubsystemEDBS.properties,locale.properties,application.MIVR.properties,system.properties, com.cisco.ccx.w1.cl.timeout=120, com.cisco.ccx.w1.stage.dir=C:\W1-STI, w1.stage.license=7xLicense, w1.stage.calabrio=cl}
     Backup dir : C:\W1-STI ]
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ExportManager execute
    SEVERE: Cisco Unified CCX Backup operation failed. ProcessResult = false
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane saveStatus
    INFO: Saving the PUT backup status and logs.
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane createZip
    INFO: Getting the PUT log files from C:\
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane createZip
    INFO: Creating the log archive file C:\PUTLog04-May-15#14-16.zip
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.export.ui.JHTMLEditorPane saveStatus
    INFO: PUT logs backup completed.
    May 4, 2015 2:16:50 PM com.cisco.ccx.w1.util.CCXUtil printRuntimeInfo
    INFO:
    ===========================
    Available Processors = 2
    JVM Max Memory = 493.06 MB
    JVM Total Memory = 118.88 MB
    JVM Free Memory = 90.53 MB
    ===========================

    The primary reason for this error is when a codec is not installed on the box that your running Windows Media Player from (that is the common knowledge part)...a possible reason for this could be that some wav files are being saved in different formats than others. A quick check to see if there are different CTI port groups configured to use different codec would prove that out. Also...can you play the files on another computer or in a different player like VLC?
    Peace,
    Michael Clendening

  • Cannot upgrade an AP1242 to LWAP using the upgrade tool 3.4

    I have installed the tool on an XP laptop.
    If I configure the tool to use an external tftp server then I get upgrade failed.
    "Unable to Load  the LWAPP Recovery Image on to the AP"
    If I use the built in tftp server I get a msgbox with "C:\Program Files\Cisco Systems\Upgrade Tool\images\c1240-rcvk9w8-tar.123-11JX1.tar - LWAPP Recovery Image is not a valid one".
    This is the log output
    2011/03/15 15:52:57 DEBUG   10.10.10.5   Validating IP address
    2011/03/15 15:52:57 DEBUG   10.10.10.5   Opening a telnet connection to the AP
    2011/03/15 15:53:00 INFO   10.10.10.5   User  has  Full privilege
    2011/03/15 15:53:00 INFO   10.10.10.5   Getting  AP Name
    2011/03/15 15:53:00 DEBUG   10.10.10.5   Verify if APs image is 12.3(07)JA or greater
    2011/03/15 15:53:00 INFO   10.10.10.5   AP  has 12.3(7)JA Image or greater
    2011/03/15 15:53:00 DEBUG   10.10.10.5   Identifying the AP Type
    2011/03/15 15:53:00 INFO   10.10.10.5   Term Length configured.
    2011/03/15 15:53:00 INFO   10.10.10.5   Upgrade Tool supported AP
    2011/03/15 15:53:00 DEBUG   10.10.10.5   Check whether AP has supported Radio
    2011/03/15 15:53:01 INFO   10.10.10.5   AP has two radios
    2011/03/15 15:53:01 DEBUG   10.10.10.5   AP has Supported Radio
    2011/03/15 15:53:01 INFO   10.10.10.5   AP has Supported Radio
    2011/03/15 15:53:01 DEBUG   10.10.10.5   Verifying Station Role
    2011/03/15 15:53:01 INFO   10.10.10.5   Station role is  Root AP
    2011/03/15 15:53:01 DEBUG   10.10.10.5   Check whether AP has  MIC Certificate
    2011/03/15 15:53:01 INFO   10.10.10.5   MIC is already configured in the AP
    2011/03/15 15:53:01 DEBUG   10.10.10.5   Getting Ethernet MAC address
    2011/03/15 15:53:01 INFO   10.10.10.5     Hardware is PowerPCElvis Ethernet, address is 001f.ca28.973a (bia 001f.ca28.973a) 
    2011/03/15 15:53:01 DEBUG   10.10.10.5   Getting the Radio Status
    2011/03/15 15:53:01 DEBUG   10.10.10.5   Entering Configuration mode
    2011/03/15 15:53:02 INFO   10.10.10.5   Inside Shutdown function
    2011/03/15 15:53:04 INFO   10.10.10.5   Shutdown the Dot11Radio1
    2011/03/15 15:53:06 INFO   10.10.10.5   Shutdown the Dot11Radio0
    2011/03/15 15:53:06 DEBUG   10.10.10.5   Getting Current System Time
    2011/03/15 15:53:07 INFO   10.10.10.5   Updating the AP with Current System Time
    2011/03/15 15:53:07 DEBUG   10.10.10.5   Entering Configuration mode
    2011/03/15 15:53:07 DEBUG   10.10.10.5   Executing show run
    2011/03/15 15:53:08 INFO   10.10.10.5   Saving the configuration into memory
    2011/03/15 15:53:08 INFO   10.10.10.5   Getting  AP Name
    2011/03/15 15:53:08 DEBUG   10.10.10.5   Loading the LWAPP Recovery Image on to the AP
    2011/03/15 15:53:09 DEBUG   10.10.10.5   Checking the Upload Status
    2011/03/15 15:53:11 ERROR   10.10.10.5   Unable to Load  the LWAPP Recovery Image on to the AP
    2011/03/15 15:53:18 INFO   10.10.10.5   Dot11Radio0 is up now
    2011/03/15 15:53:18 DEBUG   10.18.227.10   Opening a telnet connection to the Controller
    2011/03/15 15:53:19 DEBUG   10.18.227.10   Telnet connection to the Controller opened
    I see from other posts that JX image is required but it is not working for me. Can anyone help?

    If I try to extract the tar file direct to flash I get this:
    Loading c1240-rcvk9w8-tar.123-11JX1.tar from 10.1.1.1 (via BVI1): !
    %Tar checksum error in fd 0
    ERROR: Failed to extract from archive file tftp://10.1.1.1/c1240-rcvk9w8-tar.123-11JX1.tar
    Maybe the files are damaged but I have dowloaded them all from cisco.com yesterday.

  • EBS database  pre-upgrade tool

    Hi All,
    I am upgrading EBS database from 10.2.0.3 to 11.2.0.3
    OS - RHEL 5
    EBS - 12.1.3
    While running pre-upgrade too , utl112i.sql am getting some warning. Please help me what step I can follow for this warning.
    WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
    .... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
    .... USER APPS has dependent objects.
    Thanks,

    Srini,Hussein.
    Thanks for the update. I have gone through the mentioned link and doc - http://docs.oracle.com/cd/E11882_01/network.112/e16543.pdf.
    I didn't understand properly. And we haven't implement LDAP/AD inegration to EBS. And this DB need a connection other database thorugh DBLINK.
    When I query : select * from dba_dependencies where referenced_name IN ('UTL_TCP','UTL_SMTP','UTL_MAIL','UTL_HTTP','UTL_INADDE','DBMS_LDAP') and owner NOT IN('SYS','PUBLIC','ORDPLUGINS'); Getting a long output. Sorry to put the below.
    APPS OKS_MAIL PACKAGE PUBLIC UTL_SMTP SYNONYM HARD
    APPS MTH_EVENT_PKG PACKAGE BODY PUBLIC UTL_SMTP SYNONYM HARD
    APPS IBY_BANKACCXFR_PUB PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS JTF_DIAGNOSTIC_COREAPI PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS OKS_MAIL PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS WSH_OTM_HTTP_UTL PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS HZ_HTTP_PKG PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS IBY_NETUTILS_PVT PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS IBY_PAYMENT_ADAPTER_PUB PACKAGE BODY PUBLIC UTL_TCP SYNONYM HARD
    APPS IBY_BANKACCXFR_PUB PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS JTF_DIAGNOSTIC_COREAPI PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS OKS_MAIL PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS WSH_OTM_HTTP_UTL PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS HZ_HTTP_PKG PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS IBY_NETUTILS_PVT PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    APPS IBY_PAYMENT_ADAPTER_PUB PACKAGE BODY APPS UTL_TCP NON-EXISTENT HARD
    OWNER NAME TYPE REFERENCED_OWNER REFERENCED_NAME REFERENCED_TYPE REFERENCED_LINK_NAME DEPE
    APPS FND_OID_PLUG PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_SSO_REGISTRATION PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_LDAP_UTIL PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_SSO_REGISTRATION PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_LDAP_USER PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_OID_PLUG PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_OID_UTIL PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS WF_OID PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS WF_LDAP PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_OID_UTIL PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_LDAP_UTIL PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS WF_OID PACKAGE APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_OID_DIAG PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS FND_LDAP_USER PACKAGE BODY APPS DBMS_LDAP NON-EXISTENT HARD
    APPS WSH_U_CSPV PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
    APPS MSC_E1APS_UTIL PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
    APPS BIS_CORRECTIVE_ACTION_PVT PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
    APPS HZ_LOCATION_SERVICES_PUB PACKAGE APPS UTL_HTTP NON-EXISTENT HARD
    APPS OKS_MAIL PACKAGE BODY APPS UTL_HTTP NON-EXISTENT HARD
    APPS BIS_PMV_PMF_PVT PACKAGE BO
    Am getting total - 166 rows selected
    Kndly suggest me what I need to do here before upgrade and after upgrade. In the document, need to do some action after upgrade to 11.2.0.3. But I didn't get a clarity what I need to do. I know this showing my lack in security knowledge.
    How important this one and What step I can follow for this output. Do I need to check/consider for this warnings. ?
    Thanks and sorry to ask these problems.

  • Is it possible to use the upgrade tool to generate SSC's anymore?

    I have a hand few of really old 1130's, manufactured prior to when MICs were installed. In anycase I wanted to convert a few of them to lightweight for use in a remote location with a 4400 we have laying around. Long story short, during the upgrade process I see an error on access point. I looks like one of the airespace certs that is copied over has expired back in April of this year. After the upgrade the access point fail to join the controller. I see an error on the access point and it seems there is a problem with it accepting the certificate on the controller. I see several posts were it seems that some people are having the same problem, I have not seen a solution.
    I think that if I got it to connect the first time it wold be good to go. I'm wondering if configuring the conversion tool with a date prior to expiration would get the certificate on the access point and maybe at that point it would work.

    Sounds like 2 issues. First need to make sure you have ssc check boxed under allowed. Then when the ap tries to join do the following debug to get the hash for the ap cert ..
    (Cisco Controller) > debug pm pki enable
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles: getting (old) aes ID cert handle...
    Mon May 22 06:34:10 2006: sshpmGetCID: called to evaluate
    Mon May 22 06:34:10 2006: sshpmGetCID: comparing to row 0,
    CA cert >bsnOldDefaultCaCert<
    Mon May 22 06:34:10 2006: sshpmGetCID: comparing to row 1,
    CA cert bsnDefaultRootCaCert<
    Mon May 22 06:34:10 2006: sshpmGetCID: comparing to row 2,
    CA cert >bsnDefaultCaCert<
    Mon May 22 06:34:10 2006: sshpmGetCID: comparing to row 3,
    CA cert >bsnDefaultBuildCert<
    Mon May 22 06:34:10 2006: sshpmGetCID: comparing to row 4,
    CA cert >cscoDefaultNewRootCaCert<
    Mon May 22 06:34:10 2006: sshpmGetCID: comparing to row 5,
    CA cert cscoDefaultMfgCaCert<
    Mon May 22 06:34:10 2006: sshpmGetCID: comparing to row 0,
    ID cert >bsnOldDefaultIdCert<
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles: Calculate SHA1 hash on
    Public Key Data
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data 30820122 300d06092a864886 f70d0101
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data 01050003 82010f003082010a 02820101
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data 00c805cd 7d406ea0cad8df69 b366fd4c
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data 82fc0df0 39f2bff7ad425fa7 face8f15
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data f356a6b3 9b87625143b95a34 49292e11
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data 038181eb 058c782e56f0ad91 2d61a389
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data f81fa6ce cd1f400bb5cf7cef 06ba4375
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data dde0648e c4d63259774ce74e 9e2fde19
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data 0f463f9e c77b79ea65d8639b d63aa0e3
    Mon May 22 06:34:10 2006: sshpmGetIssuerHandles:
    Key Data 7dd485db 251e2e079cd31041 b0734a55
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles:
    Key Data 463fbacc 1a61502dc54e75f2 6d28fc6b
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles:
    Key Data 82315490 881e3e3102d37140 7c9c865a
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles:
    Key Data 9ef3311b d514795f7a9bac00 d13ff85f
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles:
    Key Data 97e1a693 f9f6c5cb88053e8b 7fae6d67
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles:
    Key Data ca364f6f 76cf78bcbc1acc13 0d334aa6
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles:
    Key Data 031fb2a3 b5e572df2c831e7e f765b7e5
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles:
    Key Data fe64641f de2a6fe323311756 8302b8b8
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles:
    Key Data 1bfae1a8 eb076940280cbed1 49b2d50f
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles: Key Data f7020301 0001
    Mon May 22 06:34:14 2006: sshpmGetIssuerHandles:
    SSC Key Hash is 9e4ddd8dfcdd8458ba7b273fc37284b31a384eb9
    !--- This is the actual SSC key-hash value.
    Mon May 22 06:34:14 2006: LWAPP Join-Request MTU path from
    AP 00:0e:84:32:04:f0 is 1500, remote debug mode is 0
    Mon May 22 06:34:14 2006: spamRadiusProcessResponse:
    AP Authorization failure for 00:0e:84:32:04:f0
    Then add the ap to the Mac filter ..
    Sent from Cisco Technical Support iPad App

  • Cannot upgrade an AP to LWAP using the upgrade tool on Windows 7

    Hello,
        I have two Windows 7 computers and neither one will successfully upgrade a 1242 AP to LWAP.  However, I go to a coworker's XP machine and run the tool without issues.  On Windows 7 I keep receiving the error message of ACL or Firewall is blocking.  I have added rules and then even tried disabling the firewalls completely on both computers and still no success.  Help!
    Thanks,
    Kristen Woodard
    Network Engineer II

    As an aside here, if the AP are newer, manufactured after 6/2005(Has a MIC and not a SSC), you can do a normal archive download command to run the upgrade to the recovery image.  Can even be scripted to run multiple times via shell/cron
    HTH,
    Steve
    Please remember to rate helpful posts or to mark the quesiton as answered so that it can be found later.

  • UCCX 7.0.1SR5 to 8.0 upgrade while also adding LDAP integration for CUCM - what happens to agents and Historical Reporting data?

    Current State:
    •    I have a customer running CUCM 6.1 and UCCX 7.01SR5.  Currently their CUCM is *NOT* LDAP integrated and using local accounts only.  UCCX is AXL integrated to CUCM as usual and is pulling users from CUCM and using CUCM for login validation for CAD.
    •    The local user accounts in CUCM currently match the naming format in active directory (John Smith in CUCM is jsmith and John Smith is jsmith in AD)
    Goal:
    •    Upgrade software versions and migrate to new hardware for UCCX
    •    LDAP integrate the CUCM users
    Desired Future State and Proposed Upgrade Method
    Using the UCCX Pre Upgrade Tool (PUT), backup the current UCCX 7.01 server. 
    Then during a weekend maintenance window……
    •    Upgrade the CUCM cluster from 6.1 to 8.0 in 2 step process
    •    Integrate the CUCM cluster to corporate active directory (LDAP) - sync the same users that were present before, associate with physical phones, select the same ACD/UCCX line under the users settings as before
    •    Then build UCCX 8.0 server on new hardware and stop at the initial setup stage
    •    Restore the data from the UCCX PUT tool
    •    Continue setup per documentation
    At this point does UCCX see these agents as the same as they were before?
    Is the historical reporting data the same with regards to agent John Smith (local CUCM user) from last week and agent John Smith (LDAP imported CUCM user) from this week ?
    I have the feeling that UCCX will see the agents as different almost as if there is a unique identifier that's used in addition to the simple user name.
    We can simplify this question along these lines
    Starting at the beginning with CUCM 6.1 (local users) and UCCX 7.01.  Let's say the customer decided to LDAP integrate the CUCM users and not upgrade any software. 
    If I follow the same steps with re-associating the users to devices and selecting the ACD/UCCX extension, what happens? 
    I would guess that UCCX would see all the users it knew about get deleted (making them inactive agents) and the see a whole group of new agents get created.
    What would historical reporting show in this case?  A set of old agents and a set of new agents treated differently?
    Has anyone run into this before?
    Is my goal possible while keeping the agent configuration and HR data as it was before?

    I was doing some more research looking at the DB schema for UCCX 8.
    Looking at the Resource table in UCCX, it looks like there is primary key that represents each user.
    My question, is this key replicated from CUCM or created locally when the user is imported into UCCX?
    How does UCCX determine if user account jsmith in CUCM, when it’s a local account, is different than user account jsmith in CUCM that is LDAP imported?
    Would it be possible (with TAC's help most likely) to edit this field back to the previous values so that AQM and historical reporting would think the user accounts are the same?
    Database table name: Resource
    The Unified CCX system creates a new record in the Resource table when the Unified CCX system retrieves agent information from the Unified CM.
    A Resource record contains information about the resource (agent). One such record exists for each active and inactive resource. When a resource is deleted, the old record is flagged as inactive; when a resource is updated, a new record is created and the old one is flagged as inactive.

  • Oracle Upgrade --  Pre-Upgrade 10.2.0.4 to 11.2.0.1

    Hello,
    I want to do an Oracle Upgrade to version 11.2g!
    At this point I did some things (in Windows Server 2003 X64):
    1-) Install Oracle 10.2.0.1 (DVD Media);
    2-) Installation of Oracle patchset 10.2.0.4 (note 871735);
    3-) Installation of interim / last generics patch (note 1137346);
    4-) Installation of SAP ECC 6.0 SR3 by SAPInst
    5-) After SAP installation I did all the corrections in Oracle parameters as it mentioned in note 830576.
    As you see above, all the SAP system was well installed!
    But now I want to do the Oracle Upgrade process to the last version, Oracle DB 11.2g  (11.2.0.1)... and so I´m following the Upgrade guide "Upgrade to Oracle Database 11g Release 2 (11.2) Windows.pdf" with some SAP notes for Upgrade process.
    So I´m at this point in planning chapter where is recommended to check so things in actual database, one of this checks are running some SQL-scripts to perform an Oracle database upgrade with DBUA to release 11.2 (as mentioned in note 1431793 - Oracle 11.2.0: Upgrade Scripts)
    I ran two Pre-Scripts, the @pre_upgrade_status.sql and @pre_upgrade_tasks.sql but both outputs showed some warnings and they are worrying me... so what I ask to you is some kind of help in analyse of them and tell me if this issues are relevant for the upgrading process and if so, what you recommend me to do to correct their!
    Next I will post here this two log scripts... they are long!!!

    PRE_UPGRADE_TASKS.log:
    SQL> @pre_upgrade_tasks.sql
    PRE-UPGRADE Tasks: === START ===
    2010-08-05 18:24:13                                                                               
    Recompiling invalid objects
    This reduces the number of invalid objects as much as possible.
    COMP_TIMESTAMP UTLRP_BGN  2010-08-05 18:24:13                                                      
    DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
    DOC>   objects in the database. Recompilation time is proportional to the
    DOC>   number of invalid objects in the database, so this command may take
    DOC>   a long time to execute on a database with a large number of invalid
    DOC>   objects.
    DOC>
    DOC>   Use the following queries to track recompilation progress:
    DOC>
    DOC>   1. Query returning the number of invalid objects remaining. This
    DOC>       number should decrease with time.
    DOC>          SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
    DOC>
    DOC>   2. Query returning the number of objects compiled so far. This number
    DOC>       should increase with time.
    DOC>          SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
    DOC>
    DOC>   This script automatically chooses serial or parallel recompilation
    DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
    DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
    DOC>   On RAC, this number is added across all RAC nodes.
    DOC>
    DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
    DOC>   recompilation. Jobs are created without instance affinity so that they
    DOC>   can migrate across RAC nodes. Use the following queries to verify
    DOC>   whether UTL_RECOMP jobs are being created and run correctly:
    DOC>
    DOC>   1. Query showing jobs created by UTL_RECOMP
    DOC>          SELECT job_name FROM dba_scheduler_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>
    DOC>   2. Query showing UTL_RECOMP jobs that are running
    DOC>          SELECT job_name FROM dba_scheduler_running_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>#
    COMP_TIMESTAMP UTLRP_END  2010-08-05 18:24:15                                                      
    DOC> The following query reports the number of objects that have compiled
    DOC> with errors (objects that compile with errors have status set to 3 in
    DOC> obj$). If the number is higher than expected, please examine the error
    DOC> messages reported with each object (using SHOW ERRORS) to see if they
    DOC> point to system misconfiguration or resource constraints that must be
    DOC> fixed before attempting to recompile these objects.
    DOC>#
                      0                                                                               
    DOC> The following query reports the number of errors caught during
    DOC> recompilation. If this number is non-zero, please query the error
    DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
    DOC> are due to misconfiguration or resource constraints that must be
    DOC> fixed before objects can compile successfully.
    DOC>#
                              0                                                                        
    Purging Recyclebin
    This reduces the time needed for upgrading the database.
    Truncating SYS.AUD$
    This reduces the time needed for upgrading the database.
    Gathering Oracle Dictionary Statistics
    This reduces the time needed for upgrading the database.
    Running Pre-Upgrade-Information Tool utlu112i.sql
    This is a mandatory task for manual database upgrades.
    This tool is also run in pre_upgrade_status.sql.
    Oracle Database 11.2 Pre-Upgrade Information Tool 08-05-2010 18:24:45                              
    Script Version: 11.2.0.1.0 Build: 003                                                              
    Database:                                                                               
    --> name:          PRD                                                                             
    --> version:       10.2.0.4.0                                                                      
    --> compatible:    10.2.0                                                                          
    --> blocksize:     8192                                                                            
    --> platform:      Microsoft Windows x86 64-bit                                                    
    --> timezone file: V4                                                                               
    Tablespaces: [make adjustments in the current environment]                                         
    --> SYSTEM tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 905 MB                                                                 
    --> PSAPUNDO tablespace is adequate for the upgrade.                                               
    .... minimum required size: 84 MB                                                                  
    --> SYSAUX tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 210 MB                                                                 
    --> PSAPTEMP tablespace is adequate for the upgrade.                                               
    .... minimum required size: 61 MB                                                                  
    Flashback: OFF                                                                               
    Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]                                
    Note: Pre-upgrade tool was run on a lower version 64-bit database.                                 
    --> If Target Oracle is 32-Bit, refer here for Update Parameters:                                  
    -- No update parameter changes are required.                                                       
    --> If Target Oracle is 64-Bit, refer here for Update Parameters:                                  
    WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB                           
    Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]                               
    -- No renamed parameters found. No changes are required.                                           
    Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]                   
    --> remote_os_authent            11.1       DEPRECATED                                             
    --> background_dump_dest         11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    --> user_dump_dest               11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    Components: [The following database components will be upgraded or installed]                      
    --> Oracle Catalog Views         [upgrade]  VALID                                                  
    --> Oracle Packages and Types    [upgrade]  VALID                                                  
    Miscellaneous Warnings                                                                             
    WARNING: --> Database is using a timezone file older than version 11.                              
    .... After the release migration, it is recommended that DBMS_DST package                          
    .... be used to upgrade the 10.2.0.4.0 database timezone version                                   
    .... to the latest version which comes with the new release.                                       
    Recommendations                                                                               
    Oracle recommends gathering dictionary statistics prior to                                         
    upgrading the database.                                                                            
    To gather dictionary statistics execute the following command                                      
    while connected as SYSDBA:                                                                               
    EXECUTE dbms_stats.gather_dictionary_stats;                                                                               
    Oracle recommends removing all hidden parameters prior to upgrading.                                                                               
    To view existing hidden parameters execute the following command                                   
    while connected AS SYSDBA:                                                                               
    SELECT name,description from SYS.V$PARAMETER WHERE name                                        
            LIKE '\_%' ESCAPE '\'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    Oracle recommends reviewing any defined events prior to upgrading.                                                                               
    To view existing non-default events execute the following commands                                 
    while connected AS SYSDBA:                                                                         
      Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2                           
          WHERE  UPPER(name) ='EVENT' AND  isdefault='FALSE'                                                                               
    Trace Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2                           
          WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    PRE-UPGRADE Tasks: === FINISHED ===
    SQL> spool off

  • Upgrade Tool Problems

    v\:* {behavior:url(#default#VML);}
    o\:* {behavior:url(#default#VML);}
    w\:* {behavior:url(#default#VML);}
    .shape {behavior:url(#default#VML);}
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-parent:"";
    mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin:0cm;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:10.0pt;
    font-family:"Times New Roman","serif";}
    Hello,
    I’m having problems using the Upgrade tool, using the internal TFTP server try as I might I can’t persuade that there isn’t a firewall or ACL blocking TFTP:
    -          I’ve tried using v3.2 and v3.4
    -          I’ve tried using different machines
    -          I’ve turned off all firewalls and removed all ACLs from the APs
    -          I’ve traced the route across the network and can’t see any reason why any traffic would be blocked between the two
    -          I can confirm from the TACACS server that the upgrade tool is authenticating
    ===============================================================================================================
    Using the external TFTP Server I can’t persuade it to work as there seems to be a fault in the script that the upgrade tool tries to run, I’ve looked throught the log the important bit seems to be below where it tries to answer exit to a yes/no question:
    KCHCam.Gnd.Ap1130.4(config)#crypto ca enroll CISCO_IOS_SSC_Cert
    The router has already generated a Self Signed Certificate for
    trustpoint TP-self-signed-3298014188.
    If you continue the existing trustpoint and Self Signed Certificate
    will be deleted.
    Do you want to continue generating a new Self Signed Certificate? [yes/no]: yes
    % The fully-qualified domain name will not be included in the certificate
    Generate Self Signed Router Certificate? [yes/no]: exit
    % Please answer 'yes' or 'no'.
    Generate Self Signed Router Certificate? [yes/no]:  test ssc enable
    % Please answer 'yes' or 'no'.
    Generate Self Signed Router Certificate? [yes/no]: show crypto ca certificates
    % Please answer 'yes' or 'no'.
    Generate Self Signed Router Certificate? [yes/no]:
    The failure message is below:
    2010/08/10 11:17:50 ERROR       172.16.130.154  Unable to Get Root Certificate Status
    Any help would be greatly appreciated.
    Thanks
    Chris

    Have you try remove domain configuration on your autonomous ap? or just write erase and try again.

  • Lightweight Mode Upgrade Tool

    I have installed the latest version of the tool, 3.4, and installed it on an XP SP2 box. Everything looks good, but when I start it returns "C:\Program Files\Cisco Systems\Upgrade Tool\images\c1310-rcvk9w8-tar.124-10b.JA3 - LWAPP Recovery Image is not a valid one".
    I have verified that the file exists and is named correctly. I have also downloaded a new copy of the application and image and installed on a different computer and got the same results. Any ideas?

    Hi EMKF,
    I don't think the problem is with the tool it is with this image "c1310-rcvk9w8-tar.124-10b.JA3" I don't know why they have linked this in the Software Downloads to the LWAPP Upgrade image but I'm pretty sure it is wrong.
    As far as I know all recovery images are JX (not JA etc.)
    I would try this image instead;
    12.3(11)JX1.
    Note This release must only be loaded onto access points at the factory or by using the Autonomous to Lightweight Mode upgrade tool. Your access point might become inoperable if you install this software without using the upgrade tool.
    Release Notes for Cisco Aironet 1100, 1130, 1200, 1230, 1240, and 1300 Series Access Points for Cisco IOS Release 12.3(11)JX1
    http://www.cisco.com/en/US/docs/wireless/access_point/ios/release/notes/b311jx1.html
    c1310-rcvk9w8-tar.123-11JX1.tar
    Here is the link;
    http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=12.3(11)JX1&mdfid=279141937&sftType=Autonomous%20To%20Lightweight%20Mode%20Upgrade%20Image&optPlat=&nodecount=3&edesignator=null&modelName=Cisco%20Aironet%201310%20Access%20Point/Bridge&treeMdfId=278875243&treeName=Wireless&modifmdfid=null&imname=null&hybrid=Y&imst=N&lr=Y
    Check out these notes (no mention of LWAPP Upgrade image)
    Release Notes for Cisco Aironet Access Points and Bridges for Cisco IOS Release 12.4(10b)JA3
    http://www.cisco.com/en/US/docs/wireless/access_point/ios/release/notes/12_4_10b_JA3rn.html
    Hope this helps!
    Rob

  • AP-to-LWAPP-Upgrade-Tool won't install

    I have downloaded 3 versions, 3.0, 3.2 and 3.4.... all of them hang after extracting the files and launching setup.exe....
    I have tried on several different Win XP machines... same result
    Don't know if it matters at this point, but the intended WAP is an AIR-AP1252G-A-K9...
    any ideas?

    You can't use the tool for that:
    Here is direction from a member on this forum:
    It took me a while to get this information, so thought I'd share. Here it is:
    You cannot use the upgrade tool to do the IOS to LWAPP for the 1250 APs.
    Here is a method to do the conversion.
    *Method 1 : ( Mode Button )*
    1. Install an external TFTP tool such as tftpd32 tool from http://tftpd32.jounin.net/
    2. Assign IP address in the range 10.0.0.2 - .254 ( Ex : 10.0.0.3) to the tftp server (your laptop or pc).
    3. Download the IOS to lwapp image onto the tftp's root directory. Use http://www.cisco.com or
    http://tools.cisco.com/support/downloads/go/IPCheck.x?defAdv=N&sftAdv=N&image=c1250-rcvk9w8-tar.124-10b.JA3&filepath=/swc/esd/02/crypto/3DES/281235915/guest&filename=c1250-rcvk9w8-tar.124-10b.JA3&advUrl=null&isk=Y&defInd=N&mdfid=281235915&sftType=Autonomous%20To%20Lightweight%20Mode%20Upgrade%20Image&optPlat=&relVer=12.4(10b)JA3&fileId=271159&treeMdfId=278875243&treeName=Wireless
    4. Rename c1250-rcvk9w8-tar.124-10b.JA3 to c1250-rcvk9w8-tar.default
    5. Make sure you set the IP address on the BVI interface of the AP if not set. Set it in the 10.0.0.x range. Default is 10.0.0.1.
    6. Connect the Ethernet port on AP to your TFTP Server ( Laptop )
    7. Hold the mode button and power off the AP.
    8. Power back the AP while continually holding the mode button for 20-30
    seconds.
    *Method 2 : ( Archive Command )*
    1. Install an external TFTP tool such as tftpd32 tool from http://tftpd32.jounin.net/
    2. Assign IP address in the range 10.0.0.2 - .254 ( Ex : 10.0.0.3) to the tftp server (your laptop or pc).
    3. Download the IOS to lwapp image onto the tftp's root directory. Use http://www.cisco.com or
    http://tools.cisco.com/support/downloads/go/IPCheck.x?defAdv=N&sftAdv=N&image=c1250-rcvk9w8-tar.124-10b.JA3&filepath=/swc/esd/02/crypto/3DES/281235915/guest&filename=c1250-rcvk9w8-tar.124-10b.JA3&advUrl=null&isk=Y&defInd=N&mdfid=281235915&sftType=Autonomous%20To%20Lightweight%20Mode%20Upgrade%20Image&optPlat=&relVer=12.4(10b)JA3&fileId=271159&treeMdfId=278875243&treeName=Wireless
    4. Make sure you set the IP address on the BVI interface of the AP if not set. Set it in the 10.0.0.x range. Default is 10.0.0.1.
    5. Connect the Ethernet port on AP to your TFTP Server ( Laptop )
    6. On AP, type archive download-sw /overwrite /force-reload tftp:///c1250-rcvk9w8-tar.124-10b.JA3
    Going the other way (lwapp to autonomous)
    http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp161272
    If you need to manually "prime" the LWAPP:
    AP#lwapp ap ip address
    AP#lwapp ap ip default-gateway
    AP#lwapp ap controller ip address
    AP#lwapp ap hostname
    (optional)
    Hope someone finds this useful!

  • 11i-R12 upgrade and MOS 954704.1 (pre-upgrade

    I am performing the 11.5.10.2 -> R12.1.1 Upgrade using the Maint Wizard (v2.19) on Linux x86.
    I am at this step:
    Cat - Upg to Rel 12.1.1
    ProdFamily - Perform the Upgrade
    Task - Apply Preinstall Patches
    Step - Check for critical pre-upgrade patches for Financials
    Action - Follows MOS note 954704.1 to apply pre-upgrade patches
    I would like to know whether I need to use any special options/parameters to adpatch when applying these R12 patches.
    Thanks

    I don't understand. I haven't applied ANY R12 patches (except OAS 10.1.2.3) yet since I am still at a "pre-upgrade" step.
    So the R12 patch cannot be in AD_BUGS.
    The R12.AD.A.delta.4 patch is 6510214. Don't I need to know whether it is in the Rapid Install upgrade driver u6678700.drv?Sorry, I thought you are asking how to find if it is applied or not later after the upgrade.
    Just follow the same logic we did with Patch 6856840, search MOS for (R12.AD.A.DELTA.4, Patch 6510214) and you will get the list of patches that includes this patch (according to MOS website, I can see that this patch is only included in R12.AD.A.DELTA.6).
    Thanks,
    Hussein

  • What is the Difference  Between the  Pre-Upgrade and Post-upgrade in UMT in SAP BO

    Could anyone give me details.

    UMT is used to upgrade and migrate from older version to newer version.
    There is no pre or post migration terms used for UMT.
    Check the guide for more information.

  • Pre Upgrade Project details Required

    Hi Experts,
    Could anyone please explain in detail with sufficient links/materials as to what kind of a role does an Abapper Play in Pre Upgrade Project.
    What kind of Problems one can face and solutions to it if possible.
    Thanks in Advance.
    Regards
    Ullas

    Hi Ullas,
    please check this link
    abaper role in Upgradation project
    SAP Upgrade project
    Regarding the Steps involved in Upgrade Project
    First it will be to find objects whcih are impacted by upgrade. Now most of the solution providers have tools to do this work automatically with less human involvement. These tools give you a list of custom developments that will be impacted by upgrade which need correction in higher version. Each object in the list will be distributed to a person in team for fix. It is the responsibity of the Abaper to find out the error and fix the error in a given program and make it error free. This is checked by testing the object after the correction is completed. For exapmle a screen number has changed in higher version for a particular transaction. This implies a correction to all custom programs where this screen is used in BDC. Another example may be an obsolete function module which is not available in higher version and it is the responsibility of Abaper to find out suitable replacement for this.
    But prior to this activity there is one more activity. If there are any changes to standard SAP developments like user exits or changes to standard code or changes to data dictionary, then they will not be reflected automatically after upgrade. There are transaction SPAU for workbench objects and SPDD for data dictionary objects. Abaper has to analyse the changed done to standard programs and dictionary objects and has to decide whther these are required in higher version. If they are required then correct them through these transaction codes.
    There is a document given by SAP on roles played by different people in an upgrade project. I suggest you to read that.
    Best regards,
    raam

  • Custom Report using pre-defined template

    In 2012, How to create custom report using pre-defined reports template in below format?
    Column1 :- Device Name
    Column2 :- When installed (Date & Time)
    Column3 :- Success (Date & Time)
    Column3 :- Failed (Date & Time - With which error code)
    Column4 :- Not Installed
    Regards,
    Onkar.

    Here is what you need to do.
    Start by writing the SQL query that you want.
    Clone one of the existing report
    Replace the SQL query with the new query.
    Update the columns with what you need.
    http://www.enhansoft.com/

Maybe you are looking for