[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.

Similar Messages

Sun cluster upgrade

Any one did an upgrade from Sun cluster 3.0 07/01 release to 12/01 release
was there any problem in the upgrade and what was the approach
any suggestion

This upgrade is delivered as a patch set and some
additional packages. The upgrade procedure is
basically the same as a normal patch procedure.
You might consider getting the latest core Sun Cluster
patch as well, just to be sure you are at the latest rev.
The additional packages provide new features. The
most popular is the Generic Data Service which can
really save development time for simple agents.
-- richard

Rolling Cluster Upgrade (OES2 to OES11) - GPT partition

We've got an OES2 SP3 cluster that we'll be rolling cluster upgrading to OES11 SP2.
We are currently at max capacity for several of the NSS volumes (2 TB).
If I'm reading/interpreting the OES11 SP2 docs correctly:
AFTER the cluster upgrade is complete, the only way I can get to larger volumes will be to create new LUNs on the SAN and intialize those with GPT. Then I could do the NSS Pool Move feature to get the existing 2 TB volumes to the larger setup?
Is that correct?
Or is there a better way that doesnt' require massive downtime?

Originally Posted by konecnya
In article <[email protected]>, Kjhurni wrote:
> We are currently at max capacity for several of the NSS volumes (2 TB).
I was on the understanding that you could bind multiple partitions to
create NSS volumes up to 8TB. But I'd be hesitant to do that for a
clustered volume as well.
> I could do the NSS Pool Move feature to get the existing 2 TB
> volumes to the larger setup?
> Or is there a better way that doesnt' require massive downtime?
My first thought is the migration wizard so that the bulk of the copy can
be done while system is live but in the quieter times. Then the final
update with down time should be much faster.
But then do you really need down time for the Pool Move feature?
https://www.novell.com/documentation...a/bwtebhm.html
Certainly indicates it can be done live on a cluster with the move
process being cluster aware.
Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
Migration = pew pew (re-doing IP's/etc and copying 4 TB of data is ugly especially when it's lots of tiny stuff).
haha
Anyway, when I asked about a better way that doesn't require massive downtime what I meant was:
Is there a better way vs. Pool Move that doesn't require massive downtime (in other words, the "other way" having the massive downtime, not the Pool Move).
Choice A = Pool Move = No downtime
But let's say that's not a good option (for whatever reason) and someone says use Choice B. But Choice B ends up requiring downtime (like the data copy option).
I just didn't know if Pool Move required that you create the partition ahead of time (so you can choose GPT) or if it kinda did it all for you on the fly (I'll have to read up when I get to that point).
I'm not terribly keep on having multiple DOS partitions, although that technically would work. Just always scares me. It's just temporary for the next 8 months anyway while we migrate to NAS from OES, but I'm running out of space and am on an unsupported OS anyway.

What are best practices for rolling out cluster upgrade?

Hello,
I am looking for your input on the approaches to implement Production RAC upgrade without having a spare instance of RAC servers. We have a 2-node database RAC 11.1 on Production. We are planning to upgrade to 11.2 but only have a single database that the pre-Production integration can be verified on. Our concern is that the integration may behave differently on RAC vs. the signle database instance. How everybody else approaches this problem?

you want to test RAC upgrade on NON RAC database. If you ask me that is a risk but it depends on may things
Application configuration - If your application is configured for RAC, FAN etc. you cannot test it on non RAC systems
Cluster upgrade - If your standalone database is RAC one node you can probably test your cluster upgrade there. If you have non RAC database then you will not be able to test cluster upgrade or CRS
Database upgrade - There are differences when you upgrade RAC vs non RAC database which you will not be able to test
I think the best way for you is to convert your standalone database to RAC one node database and test it. that will take you close to multi node RAC

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.

BFD on ASR9K Cluster

I attempted to setup BFD on a layer3 subint on an ethernet bundle on an ASR9K cluster with two members. The other end of the link is a ME3600X. The BFD session did not come up, the status on the ASR side was 'ADMIN DOWN', I also saw log messages of this type:
%L2-BFD-6-SESSION_NO_RESOURCES
As well as:
show bfd session detail | inc “^(Location|MP)”
Mon Apr 28 06:51:23.228 UTC
MP download state: BFD_MP_DOWNLOAD_NO_LC
So there apparently wasn't a LC resource configured or available. I did find a 'multipath include location' bfd command, I configured both LCs for it and the BFD session came up. What's odd to me is that the only discussion that can see of 'multipath' is in the context of multihop BFD sessions, which this one is not, the link does pass through an intermeidat l2 swtich, but the connection is a direct l3 link from ASR to 3600. Why do I need the multipath command?

hi there, yeah when you have bundle and you are apparently running XR43 or later then you require the multipath location to tie the BFD session to a resource location.
This I think is maybe nicely explained with this: Implementation of various BFD flavours over bundle interfaces in IOS XR was carried out in 3 phases:
IPv4 BFD session over individual bundle sub-interfaces. This feature was called “BFD over VLAN over bundle”.
IOS XR releases 4.0.1 and beyond: “BFD Over Bundle (BoB)” feature was introduced.
IOS XR releases 4.3.0 and beyond: full support for IPv4 and IPv6 BFD sessions over bundle interfaces and sub-interfaces. For disambiguation from the BoB feature, this implementation is called BLB, and sessions are often referred to as native BFD sessions over bundle interfaces and/or sub-interfaces. BFD multipath must be enabled for any of these BFD flavours to work.
Due to the introduction of BLB (bfd over logical bundle) in XR43 this was necessary, I agree that you may have been mislead by the nomenclature of that multipath location keyword which suggests multihop, but it was meant to also include multipath as in multiple members of a bundle...
regards
xander

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*

EM for Coherence - Cluster upgrade

Hi Gurus,
I noticed that there are "Coherence Node Provisioning" process in EM12c, and it says "You can also update selected nodes by copying configuration files and restarting the nodes.". Does the EM will internally check the service HA status before update (stop/start) each node? The "NODE-SAFE" should be the minimum HA Status criterion to meet to ensure there is no data loss.
Thanks in advance
Hysun

Thanks for your hints, but it didn't work either. Maybe because the metaset uses the disks DID-name and those are not available when the node is not booted as part of the cluster.
What I hope will work is this:
- deactivate the zones resourcegroup
- make a backup of the non-global zones root
- restore the backup to a temporary filesystem on the nodes bootdisk
- mount the temporary filesystem as the zones root (via vfstab)
- upgrade this node including the zone
- reboot as part of the cluster (the zone should not start because of autoboot=false and the RG being deactivated)
- acquire access to the zones shared disk resource
- copy the content of the zones root back to its original place
- activate the zones resourcegroup
- upgrade the other node
- and of cource backups, backups and even more backups at the right moments :-)
I will test this scenario as soon as I can find the time for it. If I am successful I will post again.
Regards, Paul

CCM Cluster upgrade/rebuild

i am upgrading my cluster from CCM4.0 to 4.1. i am looking for any advice that would make the process go smooth. i will open a TAC case for backup.
my OS version is 2000.2.7sr4.
thanks in advance.

The only recommendation that I have is to have a backup just in case that something goes wrong. I have made many many upgrades and just the 5% of them have had problems.
The TAC case should be enough.

[asr9k cluster upgrade procedure]

Similar Messages

Maybe you are looking for