pls share 800XA 6.0 Upgrade Lesson Learned
We are upgrading 800xa 5.0 SP2 system to 800xa 6.0
Can you all please share your lesson learned in that process.
Issue Faced :
Issues to look at before start of project :
Any think please share
Voted best answer
Experience of 6.0 is still limited.
Here are a few of my experiences (not only from 6.0):
1. Use System Configuration Console to install & deploy the nodes in your system. The 6.0 media has still got a (incorrect!) splash screen inviting you for manual install (which work at start... but will cause trouble later on when upgrading, etc). Do not install manually!
2. Do not add/remove nodes using old method in config wizard
3. Do not rename nodes after adding them with SCC
4. Do not add features you do not need
5. IM and 800xA History share some components. Naming has been changed slightly since 5.1. Thoroughly read instructions before commencing adding IM / 800xA History.
6. If possible, rehearse in some offsite / virtual mockup system before starting with the production system.
7. To ease reverting on a mistake, maintain drive image backups of most nodes. Backup at critical phases of the configuration process:
a) As received from hardware supplier
b) After Microsoft Windows installation (if done)
c) After Node Preparation Tool (NPT)
d) First aspect server before system creation, before adding features, etc
e) Do not backup a disk drive with a running system. Perform cold drive imaging, preferably while booted on some alternate media.
8) In general, we see less problems in systems (re-)installed with a bonafide Microsoft Windows installation media compared to trusting a preloaded OEM version which was shipped with the hardware.
9. Firewall exclusions are carried out by SCC when deploying a feature. Manual adding of a feature, eg Basic History might not work since firewall config may be missed. Current workflow require SCC to be in control. Later versions may start to accept some degree of service manipulation from the Service Structure again, but in 6.0.0 SCC should be used.
10. As with 5.1, RNRP connectivity between servers and clients are *MANDATORY* in 6.0 even if running with singular network. Get RNRP running with the address scheme of your choice *BEFORE* trying to add features and nodes. As before a lot of work is saved by using suggested IP scheme (172.16.x.0 / 255.255.252.0). If you absolutely need to use other IP-addresses or subnetwork masks, learn how to configure explicit addresses in RNRP *before* deploying the system. Only hard limit of RNRP is node number need to be set to 500 or less. 192.168.1.11 / 255.255.0.0 *IS NOT* node 11 no matter how much you like to think it! Correct calculation throw 267 since the one (1) in the third byte add the value of 256. 1 * 256 + 11 = 267. The choice of subnetwork mask affects how the node number is calculated. All 0 bits in mask causes the corresponding bit in IP address to contribute to the node number. Only "simple" mask is 255.255.255.0; ie last byte = node number. Get all warnings out and away from the RNRP Monitor / Utility (use option 1, "Search own networks for errors...") before starting with the next step.
When we upgraded from 5.0 SP2 to 6.0. We got several systems in the in the system setup windows in the system config after restore.
-We had several problems with installing the 800xA history. Be sure to install the node prep on the history server first. Then add the function to the system, and the deplot the 800xa server and collector node to the system. if you do this the wrong we you wont get the services installed.