UCE 1.0 to 1.0.3 upgrade procedure?

Anyone know how to upgrade the UCE product from version 1.0.0 to version 1.0.3? Once the sds is upgraded then how do you do the clients?
Thanks

Hi Ellen,
I think you may already have this, assuming it's the same Ellen :) , but for everyone else the procedure is pretty much as follows -
1. Backup the SDS first by going into /usr/local/uce/install/ and executing ./backup.sh - !!!!!!!VERY IMPORTANT!!!!!!!
2. Upgrade the SDS in-place by taking the 1.0.3 tarball, opening it, and running ./ezInstall - select option 1 to Install (it will upgrade in place)
3. During the ezInstall process, UCE will generate brand new agent, console, cli and proxy install packages (will be in /usr/local/uce/install/ too with the date of the upgrade)
4. Next, you'll need to upgrade any CLI's or Consoles you have deployed - this piece is manual - take console-<date>.tar.gz, expand it, and then run "./Install -i" on top of any existing console/cli
5. Expand the new agent-<date>.tar.gz package
6. Open the new console, and load the new agent pkgs/rpms into the SDS with the following procedure:
- From the top of the console, select a "channel" (for example you will see a SOLARIS8_SPARC item, etc)
- In the top-middle panel of the console (inventory), select and expand "Local" and then select "Local PKGs" (or Local RPM's for linux channels)
-Right click on "Local PKGs", and drill down in the right-click menu until you see "Add"
-In the file browser, go to /usr/local/uce/install/uce_agent/rpms/ and select the appropriate rpm/pkg, and load into the SDS
-repeat this process for all other channels
7. Close the uce_console
8. Next, we'll open the console in a special "upgrade mode" by executing "uce_console -update_director_mode true"
9. login as "admin"
10. for each "channel" group of systems, select the new version of the agent (1.0.3) and select Install.
11. Repeat step #10 for each channel
12. Once all upgrades are complete, run a few jobs (i.e. installing a patch or sunfreeware in simulate mode to ensure that all downloads, etc are still working)
13. finally, take a 2nd backup with the backup.sh script found in /usr/local/uce/install/

Similar Messages

Upgrade procedure from 4.6c to ECC 6.0

Hi
I had gone through SAP solution browser tool and observed the differences for 4.6C and 6.0
Can u please let me know How to start and end the upgrade project i.e sequence of activities.
1) should the configuration be done in ECC 6.0 same as 4.6C?
2)master data upload?
3)Z-objects movement from 4.6C to 6.0....?
4)Open PO's and stock upload......in ECC 6.0 ?
5) what are the precautions to be taken before Go-live?
Please send any links for upgrade procedure from 4.6C to 6.0 i.e sequence of activities.........
Thanking you
Deepak

Hi,
About your questions:
1) should the configuration be done in ECC 6.0 same as 4.6C?
The configuration (if you mean how the system is configured from the Basis point of view) will be almost the same as you had in 4.6C. Of course you will find new aspects you don't have in the old version (for example the integrated ITS, ICM, etc.), but you will have the system running after the upgrade.
2)master data upload?
Master data will be adapted to new version during the upgrade. Unless you need fresh data, you won't need to reload master data.
3)Z-objects movement from 4.6C to 6.0....?
Z objects are not touched by the upgrade process. It's your responsibility to keep them running after the upgrade.
4)Open PO's and stock upload......in ECC 6.0 ?
Same as question 2). Business data remains in the system after the upgrade.
5) what are the precautions to be taken before Go-live?
It is recommended to carry out functional tests, as well as connection tests with external interfaces. In any case, you shouldn't take any special precaution, at least not so different from those you would take in a normal installation.
Regards
Francisco

What is the upgradation procedure

In orion we have autoupdate.jar which gives seemless update of the server. Is there any such functionality with OC4J?

Hi,
the autoupdater.jar is Orion specific and has been removed from OC4J. My best guess is that the upgrade of OC4J will follow the normal upgrade procedure for Oracle products.
//Andy

Recommended Solaris package upgrade procedure

We would like to know the recommended Application Package upgrade procedure. We followed the procedure as defined in the Application Packaging Developer's Guide.
Currently we followed the following procedure during upgrade:
1. Check if old version is available.
2. If it is available execute the pkgrm command to remove the old package as indicated in the Application Packaging Developer's Guide. But since the package names are same and we are executing the pkgrm command from the preinstall script, in some systems it's not allowing to remove the old package since it's executed from pkgadd command scope. The following error message is displayed while package verifying step is executed
[ verifying class <none> ]
pkgadd: ERROR: missing entry in contents file for </opt/XXXXxxxx/jre>
3. We cannot manually remove the old package first since it will completely wipe out the file. We need to migrate some of the files from old release to new. So we need the old files during upgrade.
Please suggest a suitable procedure to handle this.
Some more details about the OS:
1. uname -a
SunOS rduipv6 5.10 Generic_142900-03 sun4u sparc SUNW,UltraAX-i2 Solaris

Hi.
I can't say how Oracle recomend. But I see that for update main part of Sun Product used two ways:
1) Documentation say that user should remove all previos version of product by hand.
2) Used extarnal installation tool that do it automaticaly, but not as part package installation script (pre/postinstall ).
Regards.

Photoshop upgrade procedure

I've been moaning about this since photoshop 6 days. Why is there no automatic upgrade procedure in the photoshop installer?
WOuld it bee too difficult for the installer to ask you whether you wanted to import brushes, gradients, patterns, actions, presets, workspaces...?
If there is a quick way of doing this other than using the presets manager, I'm all ears.
(ditto: illustrator, indesign). If dreamweaver can do it...

That's a bit extreme. Photoshop CS5 is actually VERY compatible with actions from past versions.
-Noel

GSS OS upgradation procedure

Hi,
Could any one send the document for GSS os upgradation procedure.

Take a look here:
GSS - Upgrade Instructions:
http://tools.cisco.com/squish/f8f0B
GSS - 3.1(x) Release Notes
http://tools.cisco.com/squish/0b60c
GSS Software Download Site:
http://tools.cisco.com/squish/7b4337
Joel Lamousnery
TAC Customer Support Engineer

Upgradation procedure for ALE/IDOCS

Can anyone let me know what is the upgradation procedure for ALE/IDOCS and what are the steps needs to be checked out during technical remediation part of version upgrade(lower version to ECC6.0)?

IDocs are backwards compatible, so I don't think you need any special procedures for them, just a regular test, to make sure everything stull works fine. If you've had extended any standard IDocs, that part will need to be reviewed, as any other custom development.
However, there might be a newer version of the IDoc type available in ECC 6.0, which you didn't have in the previous release. You might want to see if there would be any benefits in switching to the newer version.
I'm sure you'll find all the information on the Upgrade page on SAP's [web site|http://service.sap.com/upgrade]. Also there is an SAP Press book on the subject.

NM-CE-20 Content module - upgrade procedure and ftp help

Our netmodule has been successfully installed and working. Its currently running 4.2.3 and we would like to upgrade it the latest 5.1.9.5 rev. I cannot find a working procedure for doing this. When I attempt to ftp into the module's IP I get a error stating it can't set guest priviledges. When telneting into the module and doing a "DIR" I get: nothing. Anyone help me out? Is upgrading to the 5.x supported?
Brian

To see if the version you want is supported with this hardware, check the release note
http://www.cisco.com/en/US/products/sw/conntsw/ps491/prod_release_note09186a00802664f0.html#wp107167
Looks like the 20G module is not listed.
However it is supported in 5.0.15
http://www.cisco.com/en/US/products/sw/conntsw/ps491/prod_release_note09186a0080234dcc.html#wp42371
The upgrade procedure is the same for any ACNS device.
So, follow the procedure described at :
http://www.cisco.com/en/US/products/sw/conntsw/ps491/products_configuration_guide_chapter09186a0080131e84.html#1041204
Regards,
Gilles.

Help with cisco ISE 1.1.2.145 patch-3 to ISE 1.2.0.899-2-85601 upgrade procedure

Need help from ISE experts/gurus in this forum.
Due to a nasty bug in Cisco ISE (bug ID CSCue38827 ISE Adclient daemon not initializing on leave/join), this bug will make the ISE stopping working completely and a reboot is required (very nice bug from cisco) . This leaves me no choice but to upgrade to version 1.2.0.899-2-85601.
Scenario:
- 4 nodes in the environment running ISE version 1.1.2.145 patch 3
- node 1 is Primary Admin and Secondary Monitoring - hostname is node1
- node 2 is Secondary Admin and Primary Monitoring - hostname is node2
- node 3 is Policy service node - hostname is node3
- node 4 is Policy service node - hostname is node4
Objective: Upgrade the ISE environment to ISE version 1.2 with patch version 1.2.0.899-2-85601.
My understand is that I have to upgrade the existing environment from ISE version 1.1.2.145 patch 3
to ISE version 1.1.2.145 patch 10 (patch 10 was released on 10/04/2013) before I can proceed with
upgrading to ISE version 1.2 and patch it with 1.2.0.899-2-85601.
Can I patch my exsiting environment from 1.1.2 patch 3 to patch 10 prior to upgrading to version 1.2.0.899-2-85601?
I look at Cisco website and patch 10 was released on 10/04/2013 while version 1.2 was released back in 07/05/2013.
I am trying to get a definite answer from Cisco TAC but it seems like they don't know either.
Question #1: How do I proceed with upgrading the current ISE environment from 1.1.2.145 patch 3 to 1.1.2.145 patch 10?
Propose solution:
step #1: make ISE node1 to be both Primary Admin and Primary monitoring. ISE node2 is now Secondary Admin and Secondary Monitoring.
         Then go ahead and apply ISE version 1.1.2.145 patch 10 to ISE node2 via the GUI,
step #2: Once ISE node2 patch 10 is completed, make node2 Primary Admin and Primary Monitoring. At this point, apply ISE 1.1.2.145 patch 10
         to ISE node1 via the GUI,
step #3: Once ISE node1 patch 10 is completed, make node1 Primary Admin and Secondary Monitoring and node2 Secondary Admin and Primary Monitoring,
step #4: apply ISE 1.1.2.145 patch 10 to ISE Policy Service node3. Once that is completed, verify that node2 is working and accepting traffics,
step #5: apply ISE 1.1.2.145 patch 10 to ISE Policy Service node4. Once that is completed, verify that node2 is working and accepting traffics,
Question #2: How do I proceed with upgrading the current ISE environment from 1.1.2.145 patch 10 to ISE version 1.2 with patch version 1.2.0.899-2-85601?
Propose solution:
step #1: Make ISE node1 the Primary Admin and Primary monitoring. At this point ISE node2 will become Secondary Admin and Secondary Monitoring
step #2: Perform upgrade on the ISE node2 via the command line "application upgrade <app-bundle> <repository>". Once ISE node2 upgrade is completed, it will
          form a new ISE 1.2 cluster independent of the old cluster,
step #3: Perform upgrade on the ISE Policy Service node3 via the command line "application upgrade <app-bundle> <repository>". After the upgrade the ISE
          Policy Service Node3 will automatically joins the ISE node2 which is already in version 1.2
step #4: Perform upgrade on the ISE Policy Service node4 via the command line "application upgrade <app-bundle> <repository>". After the upgrade the ISE
          Policy Service Node4 will automatically joins the ISE node2 which is already in version 1.2
step #5: At this point the only node remaining in the 1.1.2.145 patch 10 is the ISE node1 Primary Admin and Primary Monitoring
step #6: Check and see if there are any more PSN's registered in ISE node1 (there should not be any)
step #7: Perform the upgrade on the ISE node1 from command line "application upgrade <app-bundle> <repository>"
step #8: Once upgrade on ISE node1 is complete, ISE node1 will automatically join the new ISE 1.2 cluster,
step #9: Make ISE node1 Primary Admin and Secondary and ISE node2 Secondary Admin and Primary Monitoring,
Question #3: How do I proceed with upgrading the current ISE environment from 1.2 patch0 to 1.2.0.899-2-85601?
Propose solution:
step #1: make ISE node1 to be both Primary Admin and Primary monitoring. ISE node2 is now Secondary Admin and Secondary Monitoring.
         Then go ahead and apply ISE 1.2.0.899-2-85601 to ISE node2 via the GUI,
step #2: Once ISE node2 1.2.0.899-2-85601 is completed, make node2 Primary Admin and Primary Monitoring. At this point, apply 1.2.0.899-2-85601
         to ISE node1 via the GUI,
step #3: Once ISE node1 patch 10 is completed, make node1 Primary Admin and Secondary Monitoring and node2 Secondary Admin and Primary Monitoring,
step #4: apply ISE 1.2.0.899-2-85601 to ISE Policy Service node3. Once that is completed, verify that node2 is working and accepting traffics,
step #5: apply ISE 1.2.0.899-2-85601 to ISE Policy Service node4. Once that is completed, verify that node2 is working and accepting traffics,
does these steps make sense to you?
Thanks in advance.

David,
A few answers to your questions -
Question 1: My recommendation is to follow vivek's blog since most fixes and upgrade steps are provided there - I would recommend installing the patch that was release prior to the 1.2 release date since the directions to "install the latest patch" would put you at the version of when the ISE 1.2 was released
https://supportforums.cisco.com/community/netpro/security/aaa/blog/2013/07/19/upgrading-to-identity-services-engine-ise-12
You do not have the ability to install ISE patch through the GUI on any of the "non-primary" nodes (you can use the cli commmand to achieve this), the current patching process was designed so you can install the patch on the primary admin node and it will then roll the patches out to the entire deployment (one node at at time). I painfully verified this by watching the services on each node and when a node was up and operational the next node would start the patching process. First the admin nodes then the PSNs.
Every ISE upgrade that I have attempted as not been flawless and I can assure you that I have done an upgrade on 1.1.2 patch 3 and this worked fine, however I used the following process. You will need the service account information that is used to join your ISE to AD.
I picked the secondary admin/monitoring node and made it a standalone node by deregistering (much like the old procedure) in your case this will be node2.
I backed up the certificates from the UI and the database from the CLI (pick the local disk or ftp-your choice).
I reset the database and ran the upgrade script (since I did not have access to the vsphere console or at the location of the non UCS hardware [for a 1.1.4 upgrade]).
Once the upgrade was completed I then restored the 1.1.x database, ISE 1.2 now has the ability to detect the version of the database that is restored and will perform the migration for you.
Once the restore finished, I then restored the certificate and picked one of the PSNs
backup the cert,
Had the AD join user account handy
reset-db,
and run the upgrade script.
Once that is done I then restore the cert
Join the PSN to the new deployment
Join both nodes to AD through primary admin node
Monitor for a few days (seperate consoles to make sure everything runs smooth)
If anything doesnt look or feel right, you can shut down the 1.2 PSN and force everything through the existing 1.1.2 setup and perform some investigation, if it all goes smooth you can then follow the above step for the other two nodes, starting with the last PSN and the the last admin node.
Thanks and I hope that helps,
Tarik Admani
*Please rate helpful posts*

Upgrade procedure for multiple WLCs without N+1

Hello, I would like to discuss another method of a bulk controller upgrade and see what other engineers take on this upgrade path would be.
Say I have an instance of 8 4404s with 50 APs each, In this case I have N+1 redundancy where I can follow the normal proceedure
Normal Proceedure
Move all APs to controllers 1-4
Preload all APs with the new code version
Upgrade and reboot empty controllers 5-8 to new code version
Move all APs to 5-8 with new code versoin
Upgrade empty 1-4
Move all APs back home
Now take the same scenario only chage it to 80 APs per controller. I've now lost my N+1 and cannot do it quite as smoothly.
As opposed to trying to follow the normal proceedure and have an extended window of "brown outs" How about doing it all at once.
Black-out accelerated proceedure:
Preload new code on all controllers
Preload new image on all APs on all controllers
Reboot all 8 controllers at the same time.
Allow time for APs to connect back and load the new image
I assume with this proceedure that I might see around 15-30 minutes of actual downtime to the site but it seems like that could be preferable to two-three hours of brown outs.
What are your thoughts, and do you feel that 15-30 minutes is

Michael,
Welcome to CSC!
I have 40+ WLCs and like you looked at this very closely. In my environment I do a predowload and reboot them all. Ive tried the surgical approach and in my case if you get aps bouncing back and forth on WLCs they will upgrade then downgrade etc.
Also note -- If you are on 7.0.98.0 code, predownload "may" have a bug. I noticed an issue during a recent upgrade in mu network and later someone commented about the same issue here on CSC.

Upgrade procedure Logic 8 - 9 with Lion, how does it work?

Hi,
so I have Logic 8 (yes, bought) and I find it doesn't work with Lion. The known workaround doesn't work neither because I got myself a new iMac with Lion on it, and Logic setup says I may not install. That's not cool.
So I wonder what happens if I buy the Logic 9 upgrade. Will I be able to install all the stuff (somehow) or do I need to buy the complete Logic 9 retail version?
Thanks in advance.
sgbrl

Before you install on each computer, put the dongle in first then run the installation routine.
You may install Logic Studio on up to two computers but you may not run it on more than one at a time. In fact, if the two computers are networked, you won't be able to run them on both at the same time.
Yes, you may swap as often as you like - there's no limitation, except that you must close down Logic on one before you start the other.
Pete

[asr9k cluster upgrade procedure]

Dear CSC (and hopefully Xander):
What is the proper way of upgrading an asr9k cluster?
Do i have to break the cluster and upgrade both 9ks separately? then rebuild the cluster?
Or you just treat the cluster as one box and when you upgrade one of them, both are upgraded simultaneously?
(is there a document that describes this procedure for a cluster specifically?)
Thanks in advance!
c.

Hello Carlos,
you can proceed with the following Cisco's recommendations thanks to Lenin Pedu:
https://supportforums.cisco.com/docs/DOC-34114#13_Cluster_RackByRack_Upgrade_
HTH,
Michel.

Upgrade procedure for apex to 4.1 on 10.2.0.4

Hi all.
Don't know if this is the right place to post this, but any way....
This is my current configuration:
- Oracle Database 10.2.0.4 on OL for 64 bits:
[oracle@VM1 OPatch]$ ./opatch lsinventory
Invoking OPatch 10.2.0.4.2
Oracle Interim Patch Installer version 10.2.0.4.2
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Oracle Home : /home/oracle/app/OraDb10g
Central Inventory : /home/oracle/app/oraInventory
from : /etc/oraInst.loc
OPatch version : 10.2.0.4.2
OUI version : 10.2.0.4.0
OUI location : /home/oracle/app/OraDb10g/oui
Log file location : /home/oracle/app/OraDb10g/cfgtoollogs/opatch/opatch2012-07-18_07-31-12AM.log
Lsinventory Output file location : /home/oracle/app/OraDb10g/cfgtoollogs/opatch/lsinv/lsinventory2012-07-18_07-31-12AM.txt
Installed Top-level Products (3):
Oracle Database 10g 10.2.0.1.0
Oracle Database 10g Products 10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 3 10.2.0.4.0
There are 3 products installed in this Oracle Home.
Interim patches (2) :
Patch 8350262 : applied on Tue Jul 17 12:15:07 EDT 2012
Created on 14 Sep 2010, 04:59:44 hrs PST8PDT
Bugs fixed:
8350262
Patch 7580744 : applied on Tue Jul 17 12:10:56 EDT 2012
Created on 10 Dec 2008, 23:06:23 hrs PST8PDT
Bugs fixed:
7580744
OPatch succeeded.
[oracle@VM1 OPatch]$
I have been working with Apex 4.1 on my local 11G XE database and now want to export / import some applications to production (10.2.0.4).
As far as I know this would be the procedure:
- Install Companion CD and select then HTMLDB installation type. Do this installation uses and different ORACLE_HOME?. I understand this would install Oracle HTTP Server and the PL/SQL Cartdrige.
- Upgrade the Apex Schema to 4.1
- Import Applications developed using 11g XE al EPG.
Question:
Is this the correct way to go ...?
Also, please notice, companion CD is on 10.2.0.1, so i have to patch this ORACLE_HOME sometime. When do i do this ...?

Hi.... Any feedback on this one ...?
Really need to get this thing clear up, before proceeding ...!
Regards, Luis ...!

Upgrade procedure CPI 1.2.1.012 to 1.3.0.020

My question is simple:
Why isn't a GUI upgrade possible instead of CLI initiated upgrade?
Is this (GUI) only for patch upgrades or is it a valid upgrade path to use the Cisco Prime's GUI (Administarion; Software Update) in order to upload update file. Check for updates gives no results though successful login to Cisco.com.
Thanks in advance.
Mats

Thanks Marvin.
It's jgood to know becuse we had some issues using the CLI and fetching the file with FTP. (working now )
I was looking for at least an alternative of downloading the file to DefaultRepo and then use the CLI for the upgrade.
Where would the file be downloaded using the GUI - defaultRepo?
Sincere Regards
Mats

Regarding BR Tools Upgrade procedures

Hi Techies,
While Upgrading the BR Tools iam having the following doubts:
1.Kernel Upgrade from 640 to 700 includes BR Tools.exe also upgraded ,this is ok or
2.Any Other wat to upgrade BRTools separately.(from the current version to marketplace existing version)640 to 700
can any one suggest me the better soltuion in upgrading the BRTools with the procedures and prerequisites
solutions awarded for sure!
regards,
eksrKumar

Hi ESR Kumar
The BR*Tools 7.00 can be used for all SAP releases that run with an Oracle 10g database, or an Oracle 9.2 database after installing the Oracle Instant Client 10g on the Oracle 9.2 database server.
For more information, see Note 849483.
Best Wishes.
Kumar

UCE 1.0 to 1.0.3 upgrade procedure?

Similar Messages

Maybe you are looking for