Is R3load used in Upgrade process

Hi all,
During Upgrade in CONFIGURATION PHASE when we select
> MANUAL SELECTION OF PARAMETERS & provide values R3load is by default 3
I am pretty confused where R3load is used in Upgrade process
Why is R3load not mentioned in the Upgrade Guide if it is effectively used
SAP ERP 6.0 Including Enhancement Package 4 Support Release 1 ABAP
Based on SAP NetWeaver 7.0 Including Enhancement Package 1
Pls advice on the following
-Rahul

Hi,
As already mentioned R3load is what will load the database tables during Upgrade process. If you have enough resources you can speed up the downtime Upgrade Process using more R3load parallel processes but this will depend in how many CPU's and memory you have. Usually each R3load process will take around 512Mb of RAM and you can use 1.5 R3load processes per CPU.
I have used this numbers given to us by SAP and did not have any problem at all.
Good luck,

Similar Messages

Hello my OS upgrade process was interrupted due to Internet failure, how may I re-try to upgrade it? I got a message that says I can´t, the serial number can be used only once!

Hello I bought a macbook pro on August this year and got a bonus to upgrade the OS from Lion to Mountain Lion for free. I started the donwload but it was interrupted due to internet failure so the upgrade process was aborted. When I tried to initiated the process again, I got a message that says I can not used the same serial number to download Maountain Lion. What can do in order to upgrade the OS using the "bonus" I received with the purchase?

I have the same problem, only Purchases in the App Store shows nothing. The download NEVER showed up in the App Store only in the Launchpad with a progress icon. The Icon said paused but when clicked, it just disappeared with no download.
How am I supposed to get my free upgrade now?

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

BPC 7.5 upgrade process - Doubts

Hi,
Once we had the confirmation and approval to upgrade the system from SP00 to SP03 (on .NET server components), we noticed that some functional configurations had been made in the meantime. This new scenario where new things had been done from a functional perspective makes me wonder if any of that configuration could be lost while or after upgrading the server component?
Also, after reading Note 1453797 - Planning and Consolidation 7.5 SP03 NW Central Note, section "Before you install" to be more specific it says to uninstall any previous version of the .NET server and client components. Also Scott recommended me that as a best practice. This applies when the upgrade is being done from BPC 7.0 to BPC 7.5 for example or it also applies to my case (uprading BPC 7.5 system from SP00 to SP03)?
Thanks again for your help.
Regards

Hi Ethan,
Thanks for the quick response.
Actually I'm new installing BO BPC and maybe I've not used the correct words to describe that configuration I've detected while trying to install SP03. What I've noticed is that an Initial Application Set has been created. Actually, this is the only thing I have found but I'm not sure if that imply any other configurations either in .NET server or ABAP server that could be lost after upgrading the server component from SP00 to SP03. The same question arises if I decide to uninstall the current installation to perform a fresh one using SP03 directly as its described in note 1453797.
In summary, is there any chance to lost the configuration made on a BPC system (.NET and ABAP servers or client) if any of the above upgrade process is performed?
Hope being clear enough this time thanks so much for your help.
Kind regards

Upgrade Process from SQL 2005 to SQL 2012

Hi All,
I have gone thru multiple threads and would like to understand some steps in detail for me to upgrade SQL 2005 to SQL 2012.
Below is my understanding and questions around it, I would be setting up a new environment with OS 2007/2008 with SQL 2012:
Environment Readiness - Ensure new environment is ready with Win 2007/2008 with SQL 2012 Server
Run Upgrade Advisor on the new environment and point to SQL 2005 instance
Find the breaking/discontinued changes to be done before or After Upgrade
<Question>: Over here I would like to know what should be our approach to make the required changes
<Question>: Obviously I should not be making changes directly on the Production SQL 2005 server, then in that case should I take a backup/restore on the new SQL Server 2012 and then make the required changes to the database objects
like (Table schema(changing column names/datatypes etc.), Stored Procedure, Functions & Views)
<Question>: When I do a backup/restore I would also get the data along with it, so is this a recommended approach or should we only run/use the table schema creation scripts, fix the issues identified by UA and then do an Table to Table import,
any thoughts on this ?
<Question>: If I have to do a table to table Import then I should ensure there's a downtime during the Import or would I have any other better approach
So, basically my questions are around the approach of fixing the issues identified by UA and moving the database to SQL Server 2012 environment, I have around 300 databased to me upgraded.
Please do let me know what should be a good/proven approach ? Pl. do let me know if you would need any more details from me.
---Umesh

Thanks all for the replies.
I am trying summarize what I have understood here:
Document SQL Server 2005 environment details, Is there any tool which could give us all relevant details
I would take the backup from the SQL Server 2005 Production environment and then restore the same in a test environment which again has SQL Server 2005 and Run Upgrade Advisor on that
Probbaly run SQL Profiler as well to find out the deprecated changes to be done
I should fix all the breaking, discontinued changes on the Test system identified by UA
I should fix all the deprecated changes on the Test system identified by SQL Profiler
Steps 3 & 4 should give me the changed scripts for all database objects (i.e. Table Schema, Stored Procedures, Functions & Views)
<Question> Perform test, I understand this acitivity test can be captured by having SQL profiler running in the background on the SQL Server 2005 production environment where we can identify some days in a week or a month where maximum activity is
expected to ensure we cover most the scenarios, let me know is this approach looks fine or is there a better approach
Now, with regards to acutal upgrade I need to identify a time window where in less activity is done during which I could have a downtime for the actual SQL Server 2005 production environment
Post downtine, I should do a BackUp for all databases from SQL Server 2005 production environment
Test on environment readiness of SQL Server 2012 can be compared against the documentation done as part of the first Step
<Question> Ideally I should a restore first in the new environment which has SQL Server 2012
<Question> Then run the Scripted changes where we fixed all the breaking, discontinued & deprecated changes
<Question> Does above sequence of Step 9 & 10 make sense or is there a better approach of doing it
<Question> Post Upgrade and running of changed scripts, I should run the Upgrade Advisor again and see if everything looks fine
<Question> Perform test again which we ran on SQL Server 2005 Test environment
<Question> These steps should complete the Upgrade process.
Please do let me know if the above sequence look ok to all of you and does it really work in a practical scenario, do let me know your feedback or any change in sequence/process or any other tools that can be used here.
Thanks Again ...

Best practices for ZFS file systems when using live upgrade?

I would like feedback on how to layout the ZFS file system to deal with files that are constantly changing during the Live Upgrade process. For the rest of this post, lets assume I am building a very active FreeRadius server with log files that are constantly updating and must be preserved in any boot environment during the LU process.
Here is the ZFS layout I have come up with (swap, home, etc omitted):
NAME                                USED AVAIL REFER MOUNTPOINT
rpool                              11.0G 52.0G    94K /rpool
rpool/ROOT                         4.80G 52.0G    18K legacy
rpool/ROOT/boot1                   4.80G 52.0G 4.28G /
rpool/ROOT/boot1/zones-root         534M 52.0G    20K /zones-root
rpool/ROOT/boot1/zones-root/zone1   534M 52.0G   534M /zones-root/zone1
rpool/zone-data                      37K 52.0G    19K /zones-data
rpool/zone-data/zone1-runtime        18K 52.0G    18K /zones-data/zone1-runtimeThere are 2 key components here:
1) The ROOT file system - This stores the / file systems of the local and global zones.
2) The zone-data file system - This stores the data that will be changing within the local zones.
Here is the configuration for the zone itself:
<zone name="zone1" zonepath="/zones-root/zone1" autoboot="true" bootargs="-m verbose">
<inherited-pkg-dir directory="/lib"/>
<inherited-pkg-dir directory="/platform"/>
<inherited-pkg-dir directory="/sbin"/>
<inherited-pkg-dir directory="/usr"/>
<filesystem special="/zones-data/zone1-runtime" directory="/runtime" type="lofs"/>
<network address="192.168.0.1" physical="e1000g0"/>
</zone>The key components here are:
1) The local zone / is shared in the same file system as global zone /
2) The /runtime file system in the local zone is stored outside of the global rpool/ROOT file system in order to maintain data that changes across the live upgrade boot environments.
The system (local and global zone) will operate like this:
The global zone is used to manage zones only.
Application software that has constantly changing data will be installed in the /runtime directory within the local zone. For example, FreeRadius will be installed in: /runtime/freeradius
During a live upgrade the / file system in both the local and global zones will get updated, while /runtime is mounted untouched in whatever boot environment that is loaded.
Does this make sense? Is there a better way to accomplish what I am looking for? This this setup going to cause any problems?
What I would really like is to not have to worry about any of this and just install the application software where ever the software supplier sets it defaults to. It would be great if this system somehow magically knows to leave my changing data alone across boot environments.
Thanks in advance for your feedback!
--Jason

Hello "jemurray".
Have you read this document? (page 198)
http://docs.sun.com/app/docs/doc/820-7013?l=en
Then the solution is:
01.- Create an alternate boot enviroment
a.- In a new rpool
b.- In the same rpool
02.- Upgrade this new enviroment
03.- Then I've seen that you have the "radious-zone" in a sparse zone (it's that right??) so, when you update the alternate boot enviroment you will (at the same time) upgrading the "radious-zone".
This maybe sound easy but you should be carefull, please try this in a development enviroment
Good luck

Looking for information on best practices using Live Upgrade to patch LDOMs

This is in Solaris 10. Relatively new to the style of patching... I have a T5240 with 4 LDOMS. A control LDOM and three clients. I have some fundamental questions I'd like help with..
Namely:
#1. The Client LDOMS have zones running in them. Do I need to init 0 the zone or can I just +zoneadm zone halt+ them regardless of state? I.E. if it's running a database will halting the zone essentially snapshot it or will it attempt to shut it down. Is this even a nessessary step.
#2. What is the reccommended reboot order for the LDOMs? do I need to init 0 the client ldoms and the reboot the control ldom or can I leave the client LDOM's running and just reboot the control and then reboot the clients after the control comes up?
#3. Oracle. it's running in several of the zones on the client LDOM's what considerations need to be made for this?
I am sure other things will come up during the conversation but I have been looking for an hour on Oracle's site for this and the only thing I can find is old Sun Docs with broken links.
Thanks for any help you can provide,
pipelineadmin+*

Before you use live upgrade, or any other patching technique for Solaris, please be sure to read http://docs.oracle.com/cd/E23823_01/html/E23801/index.html which includes information on upgrading systems with non-global zones. Also, go to support.oracle.com and read Oracle Solaris Live Upgrade Information Center [ID 1364140.1]. These really are MANDATORY READING.
For the individual questions:
#1. During the actual maintenance you don't have to do anything to the zone - just operate it as normal. That's the purpose of the "live" in "live upgrade" - you're applying patches on a live, running system under normal operations. When you are finisihed with that process you can then reboot into the new "boot environment". This will become more clear after reading the above documents. Do as you normally would do before taking a planned outage: shut the databases down using the database commands for a graceful shutdown. A zone halt will abruptly stop the zone and is not a good idea for a database. Alternatively, if you can take application outages, you could (smoothly) shutdown the applications and then their domains, detach the zones (zoneadm detach) and then do a live upgrade. Some people like that because it makes things faster. After the live upgrade you would reboot and then zoneadm attach the zones again. The fact that the Solaris instance is running within a logical domain really is mostly besides the point with respect to this process.
As you can see, there are a LOT of options and choices here, so it's important to read the doc. I ***strongly*** recommend you practice on a test domain so you can get used to the procedure. That's one of the benefits of virtualization: you can easily set up test environments so you cn test out procedures. Do it! :-)
#2 First, note that you can update the domains individually at separate times, just as if they were separate physical machines. So, you could update the guest domains one week (all at once or one at a time), reboot them into the new Solaris 10 software level, and then a few weeks later (or whenever) update the control domain.
If you had set up your T5240 in a split-bus configuration with an alternate I/O domain providing virtual I/O for the guests, you would be able to upgrade the extra I/O domain and the control domain one at a time in a rolling upgrade - without ever having to reboot the guests. That's really powerful for providing continuous availability. Since you haven't done that, the answer is that at the point you reboot the control domain the guests will lose their I/O. They don't crash, and technically you could just have them continue until the control domain comes back up at which time the I/O devices reappear. For an important application like a database I wouldn't recommend that. Instead: shutdown the guests. then reboot the control domain, then bring the guest domains back up.
3. The fact that Oracle database is running in zones inside those domains really isn't an issue. You should study the zones administration guide to understand the operational aspects of running with zones, and make sure that the patches are compatible with the version of Oracle.
I STRONGLY recommend reading the documents mentioned at top, and setting up a test domain to practice on. It shouldn't be hard for you to find documentation. Go to www.oracle.com and hover your mouse over "Oracle Technology Network". You'll see a window with a menu of choices, one of which is "Documentation" - click on that. From there, click on System Software, and it takes you right to the links for Solaris 10 and 11.

Upgrade process to SAP Solution Manager 7.1

Hello!
We use SAP EHP 1 for SAP Solution Manager 7.0 (SPS 26) and plan to upgrade to the new SAP Solution Manager 7.1.
We currently do not have Java Stack there.
Some questions about Upgrade process
1) Can a direct Upgrade from SAP EHP 1 for SAP Solution Manager 7.0 (SPS 26) to SAP Solution Manager 7.1 be realized?
2) Should we first install Java Stack and then proceed with the Upgrade or otherwise?
3) Will Windows 32 Bit and None-Unicode Version of SAP Solution Solution Manager be supported?
It will be great to get some helpful information.
kind regards

Hello!
Trying to answer your question
1) As described in note 1244225, there no restriction to upgrade the Solman EHP1 to solman 7.1. Refer to the section:
In case you do not participate in this current Solution Manager 7.1 beta shipment there are no restrictions for implementing now SP stack 25 and upgrading in the future to an equivilant SP stack of release 7.1."
2) The Solman EHP1 must always be a dual stack system, I am not sure, how you are running the Solman EHP1 without a Java Stack, you should have one.
3) I am not sure if there will be a Solman 7.1 32Bit Non-UNICODE version. But, SAP recommends to run Solution Manager on Unicode (see also customer letter on http://service.sap.com/Unicode). At solman EHP1 there are some issues when running the system as Non_UNICODE, refer note 1383407.
I am not sure if I could clarify all your doubts.
You may check the following URL:
http://service.sap.com/instguides
- SAP Components
- Solution Manager 7.1
As this is a very new software there is few documents in it, but soon you should see a upgrade guide here.
Regards,
Allam

Siebel 7.8 -- 8 upgrade process and environments

Hi,
I'm new to Siebel Upgrade and I'm trying to figure out the upgrade process searching on the bookshelf and white papers (best practices).
I still can't comprehend the upgrade architecture and where the new Siebel sw (for ex. Siebel 8 in my case) has to be installed:
Let's suppose to have 3 starting environments: development (7.8), test/production replication (7.8) and production (7.8).
According to the bookshelf there's an initial phase (and this is valid for development environment too) called "upgrade infrastructure" in which they talk about "upgrading" the server, gateway, SWSE, etc. and about installing Siebel software.
For example at pag. 26 in Upgrade Guide version 8.1, during the development environment upgrade explanation, you can read:
"...Upgrade the Gateway Name Server, Siebel Servers, and Siebel Web Server Extension (SWSE).
For information upgrading these Siebel Enterprise components, see Siebel Installation Guide for the operating system you are using.
3 - Install the Siebel Database Server files on the Siebel Server you will use to perform the upgrade.
You only need to install the database server files for the database type that you are upgrading.
4 Install language packs for your currently deployed languages and any new languages...."
Now, starting with a 7.8 development environment, what do they mean: Do I need to install on the same development box (where the 7.8 already resides) also a new 8 development environment (server, gateway, etc.) in order to execute the development upgrade process?
And then, should I install another new 8 environment on the Production/Test machine, in order to perform the production/test environment?
Finally, should I use the test machine (once all is tested as the new production environment?
Probably I'm a bit confused. Can you help me?
Thank you,
Best Regards

Your upgrade process depends on how you want to carry out.
For a Inplace upgrade, whicih means you will be using the existing hardware where earlier version exists, you need to uninstall the earlier version install the new version and the kick of your siebel database upgrade.
The other process is where you obtain new hardware, in this case install new version of siebel software as per requirements and then start your siebel database upgrade. For this you may need to replicate your existing siebel database.
This process applies to all the environments.

HT201210 I have error code -43 when trying to upgrade iPhone 3GS running v4.3 to version 5 or above. This error occurs whilst trying to back up phone during upgrade process. 2GB of free memory on phone. Can anyone help?

I have error code -43 when trying to upgrade iPhone 3GS running v4.3 to version 5 or above. This error occurs whilst trying to back up phone during upgrade process. 2GB of free memory on phone. Can anyone help?

Well I spoke too soon.
The update was successful, but now I cannot connect to the 3GS data network.
Cannot get email and cannot open a page in Safari.
+"Safari could not open the page because the server stopped responding."+
+"Cannot Get Mail+
+THe mail server is not responding. Verify that you have entered the correct account info in Mail settings."+
Email and internet work fine on WiFi.........no data using 3GS network.
Looks like I will have to revert back to old OS.

DB upgrade during a Solaris upgrade using live upgrade feature

Hello,
Here is the scenario. We are currently upgrading our OS from Solaris 9 to Solaris 10. And there is also a major database upgrade involved too. To help mitigate downtime, the Solaris Live Upgrade feature is being used by the SA's. The DB to be upgraded is currently at 9i and the proposed upgrade end state is at 10.2.0.3.
Does anyone know if it is possible to do at least part of the database upgrade in the alternate boot environment created during the live upgrade process? So lets say that I am able to get the database partly upgraded to 10.2.0.1. Then, I want to run the patch set for 10.2.0.3 in the alternate boot environment and do the upgrade of the instance there too so that when the alternate boot environment is booted to the primary boot environment, I can, in effect, just start up the database.
That's sort of a high level simplified version of what I think may be possible.
Does anyone have any recommendations? We don't have any other high availability solutions currently in place so options such as using data guard do not apply.
Thanks in advance!

Hi magNorth,
I'm not a Solaris expert but I'd always recommend not to do both steps (OS upgrade and database upgrade) at the same time. I've seen to many live scenarios where either the one or the other has caused issues - and it's fairly tough for all three parties (You as the customer, Sun Support, Oracle Support) to find out the end what was/is causing the issues.
So my recommendation would be:
1) Do your Solaris upgrade from 9 to 10 and check for the most recent Solaris patches - once this has been finished and run for one or two weeks successfully in production then go to step 2
2) Do your database upgrade - I would suggest not going to 10.2.0.3 but directly to 10.2.0.4 because 10.2.0.4 has ~2000 bug fixes plus the security fixes from April2008 - but that's your decision. If 10.2.0.3 is a must then at least check Note:401435.1 for known issues and alert in 10.2.0.3 and for both cases the Upgrade Companion: Note:466181.1
Kind regards
Mike

IDSM-2 upgrade process questions.

Hello,
I started a new job and have been tasked with looking into what we can do with the IDSM-2 module we have in our 6509. The company has not been using the module so it hasn't been updating in a few years. I do not have a current license so I know I cannot install new signature updates, but what I would like to do is upgrade the software to version 7.0(5a)E4. Once I have it upgraded I would like to configure it in our environment and then see about getting a signature license.
I have a few questions regarding the upgrade process, and could use some assistance.
First the IDSM is currently running version 5.1(3)S256.0. From what I have read I don't believe I can go directly to 7.0(5a)E4 so my Planned Upgrade Path is: 5.1(3)S256.0 -> 5.1(8)E3 -> 7.0(5a)E4.
Am I able to upgrade this way or is there another recommended way that I should do this upgrade?
The files I have for this are below, will they be enough or am I missing any?
Do I apply them in the order listed?
Can I apply all of these files from the IDM GUI?
IPS-K9-5.1-8-E3.pkg
IPS-engine-E3-req-5.1-8.pkg <--- Is this included in the above file?
IPS-K9-r-1.1-a-5.1-8-E3.pkg
IPS-K9-7.0-5a-E4.pkg
IPS-K9-r-1.1-a-7.0-5a-E4.pkg
I plan on backing up my configuration first just in case, but should this process have any affect on the configuration?
I also saw that the upgrade will convert the configuration, so should I back it up a second time between the 5.1(8)E3 and 7.0(5a)E4 step?
Will there be any effect on network traffic or downtime during this process?
Is there any thing else I need to be aware of or that I'm missing?
Thanks in advance,
Will

Hi Will. Since you indicated that this sensor has not been in-use, it would be quickest/easiest to simply re-image it directly to the desired version (7.0(5a)E4). Additional benefits of doing this are that the sensor's filesystem will be created clean, OS/binaries cleanly installed, no potential config conversion issues, etc.
Step-by-step instructions for doing this can be found here.
And, the System Recovery Image file you will need ('IPS-IDSM2-K9-sys-1.1-a-7.0-5a-E4.bin.gz') can be downloaded here.
Will there be any effect on network traffic or downtime during this process?
That depends on whether the sensor is configured in Promiscuous Mode or Inline [VLAN Pair] Mode. You can determine this from the Catalyst config. If the sensor is installed in Inline [VLAN Pair] Mode, then certainly the re-image (and even just upgrade) could be traffic-impacting (if there is no alternative/backup path for traffic to take), as in both scenarios, the sensor is rebooted and not available for ~10 minutes (during which time, it would not be forwarding traffic (if it were installed Inline)). Additionally, since re-imaging results in a clean/default config, if the sensor were configured Inline, that portion of the config would have to be re-input post-reimage so that the sensor would know to forward traffic accordingly again. Details about the modes can be found here.

CF 9 Upgrade process Ran All Scheduled Tasks

I just completed the upgrade process from CF8 Enterprise to CF9 Enterprise on our test system, Windows 2003 R2P2 using IIS6 and SQL Server 2000. I have no schedule tasks with an active schedule, but the upgrade process ran all of the tasks. Running all of the scheduled tasks created 200+ e-mails.
Any ideas on what happened? I ran the coldfusion_9_wwe_win.exe and installed the CF9 ODBC and CF9 SOIR services.
If this happened on my TEST system (with no actively scheduled tasks) what's going to happen when I upgrade my production system?
Thanks in advance for your time.
Libby

I can't answer your specific question (*), but I would seriously reconsider your approach of UPGRADING a CF server. Set up CF9 in parallel, and migrate the application/website across to it.
If you do an inline upgrade and it fails: you've got nothing to fall back on. If you to a "cross-grade", your working CF8 instance is still there as a fail-over, if anything goes wrong with the CF9 install.
Adam
(*) you might want to raise a bug report, though.

Trouble activating OIAACCGI structure in upgrade process, fields repeated

Hi community,
I'm working in an upgrade process from 4.6 to ECC 6 versions.
In the activation step some errors have arisen and many of that have been solved but still there is an error
with the OIAACCGI structure.
the trouble is that this structure has two more structures appended which have one field with the same name
each one, the structures are ZAKOMKCV and ZAKOMPCV and the field repeated is FKART.
Because of that, we can't activate the structure OIAACCGI in the system.
Does anybody has an idea how to solve this problem?? or what field of what structure we must delete????
We cannot leave this structure inactive, is strongly necesary activate it.
Thanks in advance.
Regards.
Tony Montes.

Well, i solved this problem making an analisis from the structure and watching which of them are less used and then delete the duplicated field..
Thanks for all and i hope this answer is helpful

DMM 5.3 upgrade process failing

We are running the Digital Media Manager version 5.2.3 on a UCS-C210.
I have attempted to upgrade to version 5.3 twice, but each time the process is failing.
I have downloaded the ISO and burned to disk, backed up the system and kicked off the upgrade. It states it completes, informs me that I can eject the disk and reboot the system. However I have discovered I've been having to manually shut the server down and restart it, but it boots up into 5.2.3.
Is there something I am missing?
Thanks much.

Paul,
I assume that you were connected to CIMC, KVM or Physical Monitor/Keyboard when the remote upgrade was triggered. You do have to select few options when the remote upgrade happens, The only thing you avoid in remote upgrade process is - burning the DVD and inserting it in the drive.
I'd recommend that you setup CIMC (SETUP instructions :
http://www.cisco.com/en/US/products/ps10493/products_configuration_example09186a0080b10d66.shtml)
or KVM and open a TAC case, TAC can see where exactly the failure is happening.
I assume that you have already backed up 5.2.3's CONFIG+CONTENT before starting the upgrade to 5.3. The sysmptoms described in this thread are vey unique and would need deeper investigation.
Also once the device is UP via SSH , Get a syslog out of the device for analysis. The syslog contains dmsupgrade.log which should help TAC determine the root cause.
Worst case scenario, you may have to re-image the system using 5.2.3 FRESH ISO (different than upgrade ISO, this image can be obtained via TAC) , restore the CONTENT and CONFIG (assuming you have the backup of both) and re-trying the upgrade.
Or if this is fairly new setup you can also choose to run 5.3 FRESH ISO (assuming you don't want to retain any content and config)
I'd recommend opening a TAC case to troubleshoot this further.
Thanks,
Sagar Dhanrale

Is R3load used in Upgrade process

Similar Messages

Maybe you are looking for