topic Re: Panorama Virtual disk addition for logging - legacy mode. in General Topics

Panorama Virtual disk addition for logging - legacy mode.

Venkatesan_radhakrishnan — Sat, 19 Oct 2019 13:15:40 GMT

Hi Team,

We have panorama in legacy mode. We deployed it using 8.1 ova file by default it too 80GB storage and allocated 11GB for logging.

Now we want to add additional virtual disk in esxi server. When we add additional disk it by following below KB.

https://docs.paloaltonetworks.com/panorama/8-0/panorama-admin/set-up-panorama/set-up-the-panorama-virtual-appliance/expand-log-storage-capacity-on-the-panorama-virtual-appliance/add-a-virtual-disk-to-panorama-on-an-esxi-server.html

It shows like disk is unavailable when we try to add it shows I need to be in panorama mode. Can you someone let me know how to fix this issue.

Panorama> show system disk details

Name : sdb

State : Present

Size : 204800 MB

Status : Unavailable

Reason : Admin disabled

Panorama> request system disk add sdb

Executing this command will delete all data on the drive being added. Do you want to continue? (y or n)

You are currently in legacy mode. You must be in logger of panorama mode to add a disk

Re: Panorama Virtual disk addition for logging - legacy mode.

Venkatesan_radhakrishnan — Sat, 19 Oct 2019 13:39:57 GMT

Also, I'm confused even there is space for traffic logs why retention is one day.

show system logdb-quota

Quotas:
system: 8.00%, 1.880 GB Expiration-period: 0 days
config: 8.00%, 1.880 GB Expiration-period: 0 days
appstat: 5.00%, 1.175 GB Expiration-period: 0 days
traffic: 29.00%, 6.814 GB Expiration-period: 0 days
threat: 16.00%, 3.760 GB Expiration-period: 0 days
trsum: 3.00%, 0.705 GB Expiration-period: 0 days
hourlytrsum: 1.00%, 0.235 GB Expiration-period: 0 days
dailytrsum: 1.00%, 0.235 GB Expiration-period: 0 days
weeklytrsum: 1.00%, 0.235 GB Expiration-period: 0 days
urlsum: 3.00%, 0.705 GB Expiration-period: 0 days
hourlyurlsum: 1.00%, 0.235 GB Expiration-period: 0 days
dailyurlsum: 1.00%, 0.235 GB Expiration-period: 0 days
weeklyurlsum: 1.00%, 0.235 GB Expiration-period: 0 days
thsum: 3.00%, 0.705 GB Expiration-period: 0 days
hourlythsum: 1.00%, 0.235 GB Expiration-period: 0 days
dailythsum: 1.00%, 0.235 GB Expiration-period: 0 days
weeklythsum: 1.00%, 0.235 GB Expiration-period: 0 days
extpcap: 1.00%, 0.235 GB Expiration-period: 0 days
hipmatch: 3.00%, 0.705 GB Expiration-period: 0 days
gtp: 2.00%, 0.470 GB Expiration-period: 0 days
gtpsum: 1.00%, 0.235 GB Expiration-period: 0 days
hourlygtpsum: 1.00%, 0.235 GB Expiration-period: 0 days
dailygtpsum: 1.00%, 0.235 GB Expiration-period: 0 days
weeklygtpsum: 1.00%, 0.235 GB Expiration-period: 0 days
auth: 1.00%, 0.235 GB Expiration-period: 0 days
userid: 1.00%, 0.235 GB Expiration-period: 0 days
sctp: 0.00%, 0.000 GB Expiration-period: 0 days
sctpsum: 0.00%, 0.000 GB Expiration-period: 0 days
hourlysctpsum: 0.00%, 0.000 GB Expiration-period: 0 days
dailysctpsum: 0.00%, 0.000 GB Expiration-period: 0 days
weeklysctpsum: 0.00%, 0.000 GB Expiration-period: 0 days

Disk usage:
traffic: Logs and Indexes: 361.8MB Current Retention: 1 days
threat: Logs and Indexes: 8.9MB Current Retention: 1 days
system: Logs and Indexes: 3.5MB Current Retention: 1 days
config: Logs and Indexes: 4.0MB Current Retention: 1 days
trsum: Logs and Indexes: 88.0MB Current Retention: 1 days
hourlytrsum: Logs and Indexes: 115.8MB Current Retention: 1 days
dailytrsum: Logs and Indexes: 12.2MB Current Retention: 1 days
weeklytrsum: Logs and Indexes: 0 Current Retention: 0 days
thsum: Logs and Indexes: 8.3MB Current Retention: 1 days
hourlythsum: Logs and Indexes: 1.7MB Current Retention: 1 days
dailythsum: Logs and Indexes: 164.0KB Current Retention: 1 days
weeklythsum: Logs and Indexes: 0 Current Retention: 0 days
appstatdb: Logs and Indexes: 1.4MB Current Retention: 1 days
hipmatch: Logs and Indexes: 0 Current Retention: 0 days
extpcap: Logs and Indexes: 0 Current Retention: 0 days
urlsum: Logs and Indexes: 24.0KB Current Retention: 0 days
hourlyurlsum: Logs and Indexes: 24.0KB Current Retention: 0 days
dailyurlsum: Logs and Indexes: 12.0KB Current Retention: 0 days
weeklyurlsum: Logs and Indexes: 0 Current Retention: 0 days
gtp: Logs and Indexes: 0 Current Retention: 0 days
gtpsum: Logs and Indexes: 24.0KB Current Retention: 0 days
hourlygtpsum: Logs and Indexes: 24.0KB Current Retention: 0 days
dailygtpsum: Logs and Indexes: 12.0KB Current Retention: 0 days
weeklygtpsum: Logs and Indexes: 0 Current Retention: 0 days
auth: Logs and Indexes: 0 Current Retention: 0 days
userid: Logs and Indexes: 0 Current Retention: 0 days
sctp: Logs and Indexes: 0 Current Retention: 0 days
sctpsum,: Logs and Indexes: 0 Current Retention: 0 days
hourlysctpsum: Logs and Indexes: 0 Current Retention: 0 days
dailysctpsum: Logs and Indexes: 0 Current Retention: 0 days
weeklysctpsum: Logs and Indexes: 0 Current Retention: 0 days

Space reserved for cores: 0MB

Regards

Venky

Re: Panorama Virtual disk addition for logging - legacy mode.

Venkatesan_radhakrishnan — Sat, 19 Oct 2019 15:21:22 GMT

Hi Team,

I have replicated this issue in Vmware, I'm facing issue like below.

I added two 2TB disk in panorama in vmware but disk status is always unavailable. Why it is like can someone suggest to fix this issue.

admin@Panorama> show system disk details

Name : sdb
State : Present
Size : 2088960 MB
Status : Unavailable
Reason : Admin disabled

Name : sdc
State : Present
Size : 2088960 MB
Status : Unavailable
Reason : Admin disabled

admin@Panorama>

Regards

Venky

Re: Panorama Virtual disk addition for logging - legacy mode.

BruceBennett — Sat, 19 Oct 2019 15:58:12 GMT

I ran into the same issue when I upgraded from 7 to 8.1. To add the additional logging storage, you have to upgrade your Panorama instance from "legacy" mode to "panorama" mode. Until that is completed, which took me several tries, you will not be able to see the additional drive space.

Check out this link for the process:

https://docs.paloaltonetworks.com/panorama/8-1/panorama-admin/set-up-panorama/set-up-the-panorama-virtual-appliance/set-up-the-panorama-virtual-appliance-with-local-log-collector.html

Re: Panorama Virtual disk addition for logging - legacy mode.

Venkatesan_radhakrishnan — Sun, 20 Oct 2019 08:18:26 GMT

Why we are not able to proceed this way.

Regards

Venky

Re: Panorama Virtual disk addition for logging - legacy mode.

BruceBennett — Mon, 21 Oct 2019 12:41:43 GMT

I wish I had an answer for you. I see the language in the link that says you should be able to add the 2TB drive without any issues, "If the appliance is in Legacy mode, you can add one virtual logging disk of up to 8TB on ESXi 5.5 and later versions or one disk of up to 2TB on earlier ESXi versions". I just know that the issues that I ran into that PAN support told me that I had to upgrade the mode from legacy to panorama to be able to see the new drive. Good luck.

Re: Panorama Virtual disk addition for logging - legacy mode.

Venkatesan_radhakrishnan — Tue, 05 Nov 2019 07:55:01 GMT

Hi Everyone,

In this issue, I have used command "debug panorama-vld-mgr reset-logging-disk" and then rebooted panorama.

Post this I can able to add virtual disk in panorama and it was reflecting in log disk storage.

just writing this here, So it may help other who face this issue in future.

Regards

Venky

Re: Panorama Virtual disk addition for logging - legacy mode.

svondandamo — Thu, 25 Feb 2021 19:05:34 GMT

Hi,

This command : debug panorama-vld-mgr reset-logging-disk doesn't exist in 9.1.6.

Does any one know the equivalent for 9.1.6 ?

My situation:

Panorama is in legacy mode and can't be changed to panorama mode due to logging disk not recognized.

Logging disk is present but not recognize due to the Legacy mode.

show system disk details

Name : sdb
State : Present
Size : 2097152 MB
Status : Unavailable
Reason : Admin disabled

I am blocked 😉

Any idea ?

Re: Panorama Virtual disk addition for logging - legacy mode.

MnMSecurityMGMT — Thu, 06 Jun 2024 08:26:49 GMT

Check the system mode using below command.

>show system info | match system-mode ------if system mode is showing management then change the system mode using the command: >request system system-mode panorama

The Panorama virtual appliance reboots. If the reboot process terminates your terminal emulation software session, reconnect to the Panorama virtual appliance to see the Panorama login prompt.
If you see a CMS Login prompt, this means the Panorama virtual appliance has not finished rebooting. Press Enter at the prompt without typing a username or password.

Verify the panorama mode status:

> show system info | match system-mode

It should be showing: > system mode:panorama

After that check the show system disk details.