ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.
Problem solved Here is the steps to follow when you deploy a new panorama using M5.2xlarge EC2 instances : 1. Deploy the instance without additional logging disks 2. Upgrade the PANOS from 9.1.2 to 9.1.3 3. Shutdown the instance and attach the additonal disks of 2TB needed for logging. 4. Start the instance and verify that the disks are correctly mounted using "show system disk details" 5. Change panorama mode to panorama instead of management-only "request system system-mode panorama" 6. reboot 7. add logging disks using "request system disk add diskX" 8. verify that disks are added and enabled correctly Enjoy
... View more
Hello, We have deployed a new panorama in aws environnement with version PANOS 9.1.3. The panorama is in panorama mode and recognize all the disks attached to the EC2 instance which is m5.2xlarge. There is 1 root disk for system and two additional disks of 2TB for logs. Panorama> show system disk details Name : nvme1n1 State : Present Size : 2048000 MB Status : Ready for migration Reason : Admin disabled Name : nvme2n1 State : Present Size : 2048000 MB Status : Unavailable Reason : Admin disabled When we try to add the first logs disk "nvme1n1" the panorama shows the following message : "You cannot use a legacy disk as a virtual logging disk in panorama mode. After you migrate the data, you must detach it." however , we don't have any problem to add the second one "nvme2n1" and adding it to the local log collector. Any idea about the fact that the first 2TB disk is considered as legacy disk ? Thank you
... View more