IMO, there is no ideal scenario for doing it. It is there primarily to support earlier versions of PANOS, but running Panorama in legacy mode restricts some of the things you can do if you were running in non-legacy mode. So a few points about this:
1 - Legacy mode is only relevant to a VM implmentation of Panorama. It is not an option for the hardware implmentations.
2 - You will need additional memory/CPU to run in Panorama mode vs. legacy mode.
3 - In legacy mode, Panorama presents you with a single interface for doing everything. In Panorama mode, you'll have additional interfaces that allow you to spread the load.
4 - In legacy mode. you cannot run the Panorama VM as a dedicated log collector.
So really, the only reason I can see for running it in legacy mode would be in a lab environment where you can run it with limited CPU/RAM. Otherwise in a production environment, there is really no good reason to run in legacy mode.
Hope this helps.
@deepak12 There is a particular case, when you need to use Panroama VM for management and log collection in small environemnt, but can not afford to have the required hardware resources for "Panorama" mode.
Some smaller comapnies find it very hard to allocate 2TB logging disk, which is required in Panorama mode. In addition Legacy mode Panorama can run with as little as 4GB RAM / 4 CPU, while the minimum for Panorama mode is 16GB, 8CPU.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!