AWS - Additional logging disk added as legacy disk

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

AWS - Additional logging disk added as legacy disk

L0 Member

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

 

1 accepted solution

Accepted Solutions

L0 Member

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 solution in original post

1 REPLY 1

L0 Member

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

  • 1 accepted solution
  • 2936 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!