Support Center > Search Results > SecureKnowledge Details
Traffic flow issue on Maestro Hyperscale Orchestrator (MHO) Technical Level
Symptoms
  • If the user upgrades the Maestro Hyperscale Orchestrator (MHO) from R80.20SP Jumbo Hotfix Take 295 or older to a new Take, the upgrade can possibly have an effect on traffic flow.

  • g_tcpdump> packet capture shows that connection packets do not get to the Security Gateway Modules (SGMs) in the Security Group.

Cause
The uninstallation code for R80.20SP MHO builds older than R80.20SP Jumbo Hotfix Take 302 does not do an "orchd stop" as part of the uninstallation phase.

The abovementioned issue might occur when you upgrade an MHO from a build older than R80.20SP Jumbo Hotfix Take 302 to a newer Take, such as R80.20SP Jumbo Hotfix Take 310.

During the MHO's CPUSE upgrade from the example Takes above (upgrade of R80.20SP Jumbo Hotfix Take 295 to R80.20SP Jumbo Hotfix Take 310), the upgrade removes the older Jumbo Hotfix Take 295 and then installs the new Jumbo Hotfix Take 310.

The issue is that the uninstallation code of the older R80.20SP Jumbo Hotfix Take 295 does not do an "orchd stop" as part of the uninstallation phase. Therefore, the link state of the MHO uplinks stay up during the R80.20SP Jumbo Hotfix installation, which can potentially cause a traffic impact.


Solution
Note: To view this solution you need to Sign In .