A few wrinkles ....
So, the all of WebSphere Java agents can't be restarted on the same day. They currently have a 1, 2, 3, 4 Sunday and 1, 3, 4 Saturday groups. This would cause the production environment to be split for three weeks, which isn't selling all that well with the end users.
So thought of a new possible process to do this.
1. Create a network virtual ip address configured to the SLES 10.0 MOM
2. Reconfigure all agents to point to the new VIP so when they restart normally over the month, they will be addressing the VIP
3. Install 10.5.2 on RHEL (MOM/Collectors)
4. Switch the VIP from the 10.0 SLES MOM to the 10.5.2 RHEL MOM
5. Shutdown the SLES MOM/Collectors forcing the agents to ask the VIP MOM for a new collector list
6. Agents get a RHEL collector list and start report to the RHEL cluster
7. Keep the SLES environment down long enough for all agents to switch to RHEL
8. Start the SLES environment with the unmounts period set to 130,000 minutes (90 days) for historic searches
9. After 90 days, shutdown and decommission the SLES APM cluster.
Once we get the 10.0 agents reporting to a 10.5.2 environment, we can then do a phased upgrade of the agents and hopefully this plan will prevent having two different APM instances we would need to review or to triage with.
How does that sound?
Thanks,
Billy