Log partition SNMP OID deleted when AWS VM Series Logging disk space are added

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Log partition SNMP OID deleted when AWS VM Series Logging disk space are added

L0 Member

Hi, nice to meet you.

I recently expanded the logging disk space on my VM-Series firewall following the official Palo Alto Networks Knowledge Base article (link below).

KB Reference: https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNuACAW&lang=en_US

 

I noticed a strange side effect with SNMP monitoring. The specific OIDs for the Log Partition (hrStorageSize and hrStorageUsed) under index 1041 have disappeared:

- usage : .1.3.6.1.2.1.25.2.3.1.6.1041

- max : .1.3.6.1.2.1.25.2.3.1.5.1041

*Before adding disk space

ssublue_1-1779092069962.png

*After adding disk space

ssublue_0-1779091849628.png

Related KB : https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNuACAW&lang=en_US%E2%80%A...

In my opinion, method mentioned in KB above doesn't seem to expand the root disk. But rather mounts the newly attached volume to the logging partition. I suspect this logic is causing the OID to be deleted...

 

Has anyone seen this symptoms too? If so, did the storage index shift to another number (e.g., a new index instead of 1041), or did it stop reporting via SNMP entirely?

And are there alternative ways to expand the firewall disk space?

 

 

 

 

0 REPLIES 0
  • 21 Views
  • 0 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!