LB Code upgrade implementation process in Production environment

1. The bridge call will be opened at least 1 hour prior to the code upgrade process. Make sure to involve
all the application checkout people to join the call for application pre-verification during the activity.

2. Once everyone joined, please change the status of the column roll as "yes" in front of your team name
in the SharePoint link provided and all the teams can start the pre-verification of their application (update
SharePoint pre-verification status from "W" to "G").

3. After the roll call is done, if all the teams are good with pre-verification, we will proceed with updating
MAC masquerade on the Active/standby devices. No outage us expected at this time, but a checkout is
required post the MAC masquerade update.

4. After the MAC masquerade checkout is done, we will start upgrading the standby device with the latest
code.

5. Post standby upgradation, the standby device will be failed over to active, here the first service
interruption occurs and we need a checkout from all the application team. Please change the post
verification status in the SharePoint link (update SharePoint pre-verification status from "W" to "G").

6. Once the checkouts are good from all the team, the active device which is now standby will be upgraded
to latest code.

7. Once the device is upgraded, the devices will be failed over to original active/standby state. This is
where the second and final service interruption occurs and we need a final checkout from all the
application team. Please change the post verification status in the SharePoint link (update SharePoint pre-
verification status from "W" to "G").

8. If the final validations are good as well, this concludes our upgrade.