Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Get Started
- News & Events
- Collaboration
- Education Services
- Technologies
- Next-Generation Firewall
- GlobalProtect
- Threat Prevention Services
- Endpoint Protection
- SSL Decryption
- 5G
- IoT Security
- Prisma SD-WAN
Network Security
- Prisma Access
- Prisma SaaS
- Prisma Cloud
- CN-Series
- VM-Series:
- Alibaba
- AWS
- GCP
- Azure
Cloud Security
- Cortex XDR
- Cortex XSOAR
- Cortex Data Lake
Security Operations
- Resources
- COVID-19 Response Center
- LIVEcommunity
- ›
- About OUAHID
About OUAHID
Announcements
Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
07-16-2020
2Posts
0Likes
1Solution
Jul 16, 2020Last Visited
User
Activity
User
Profile
Latest posts by OUAHID
| Subject | Views | Posted |
|---|---|---|
| 695 | 07-01-2020 10:04 AM | |
| 769 | 06-26-2020 06:27 AM |
User Badges
Public Statistics
| Date Registered | 02-05-2019 06:43 AM |
| Date Last Visited | 07-16-2020 08:48 AM |
| Total Messages Posted | 2 |
07-01-2020
10:04 AM
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
06-26-2020
06:27 AM
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
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
07-16-2020
08:48 AM
|
Latest Blogs
Latest Posts
Copyright 2007 - 2021 - Palo Alto Networks
