<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Log partition SNMP OID deleted when AWS VM Series Logging disk space are added in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/log-partition-snmp-oid-deleted-when-aws-vm-series-logging-disk/m-p/1254181#M2457</link>
    <description>&lt;P&gt;Hi, nice to meet you.&lt;/P&gt;
&lt;P data-path-to-node="6"&gt;I recently expanded the logging disk space on my VM-Series firewall following the official Palo Alto Networks Knowledge Base article (link below).&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;KB Reference: &lt;A class="ng-star-inserted" href="https://www.google.com/search?q=https://knowledgebase.paloaltonetworks.com/KCSArticleDetail%3Fid%3DkA10g000000PNuACAW%26lang%3Den_US" rel="noopener" data-ved="0CAAQ_4QMahcKEwjWxoHXssKUAxUAAAAAHQAAAAAQYA" data-hveid="0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNuACAW&amp;amp;lang=en_US&lt;/A&gt;&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I noticed a strange side effect with SNMP monitoring. The specific OIDs for the Log Partition (&lt;CODE data-index-in-node="192" data-path-to-node="8"&gt;hrStorageSize&lt;/CODE&gt; and &lt;CODE data-index-in-node="210" data-path-to-node="8"&gt;hrStorageUsed&lt;/CODE&gt;) under index &lt;STRONG data-index-in-node="237" data-path-to-node="8"&gt;1041&lt;/STRONG&gt; have disappeared:&lt;/P&gt;
&lt;P&gt;- usage :&amp;nbsp;.1.3.6.1.2.1.25.2.3.1.6.1041&lt;/P&gt;
&lt;P&gt;- max :&amp;nbsp;.1.3.6.1.2.1.25.2.3.1.5.1041&lt;/P&gt;
&lt;P&gt;*Before adding disk space&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ssublue_1-1779092069962.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/71437i0173BE5945E93875/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ssublue_1-1779092069962.png" alt="ssublue_1-1779092069962.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;*After adding disk space&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ssublue_0-1779091849628.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/71436iAE52B43018A49F4B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ssublue_0-1779091849628.png" alt="ssublue_0-1779091849628.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Related KB :&amp;nbsp;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNuACAW&amp;amp;lang=en_US%E2%80%A9" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNuACAW&amp;amp;lang=en_US%E2%80%A9&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;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...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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?&lt;/P&gt;
&lt;P&gt;And are there alternative ways to expand the firewall disk space?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 18 May 2026 08:19:27 GMT</pubDate>
    <dc:creator>ssublue</dc:creator>
    <dc:date>2026-05-18T08:19:27Z</dc:date>
    <item>
      <title>Log partition SNMP OID deleted when AWS VM Series Logging disk space are added</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/log-partition-snmp-oid-deleted-when-aws-vm-series-logging-disk/m-p/1254181#M2457</link>
      <description>&lt;P&gt;Hi, nice to meet you.&lt;/P&gt;
&lt;P data-path-to-node="6"&gt;I recently expanded the logging disk space on my VM-Series firewall following the official Palo Alto Networks Knowledge Base article (link below).&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;KB Reference: &lt;A class="ng-star-inserted" href="https://www.google.com/search?q=https://knowledgebase.paloaltonetworks.com/KCSArticleDetail%3Fid%3DkA10g000000PNuACAW%26lang%3Den_US" rel="noopener" data-ved="0CAAQ_4QMahcKEwjWxoHXssKUAxUAAAAAHQAAAAAQYA" data-hveid="0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNuACAW&amp;amp;lang=en_US&lt;/A&gt;&lt;/P&gt;
&lt;P data-path-to-node="7"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I noticed a strange side effect with SNMP monitoring. The specific OIDs for the Log Partition (&lt;CODE data-index-in-node="192" data-path-to-node="8"&gt;hrStorageSize&lt;/CODE&gt; and &lt;CODE data-index-in-node="210" data-path-to-node="8"&gt;hrStorageUsed&lt;/CODE&gt;) under index &lt;STRONG data-index-in-node="237" data-path-to-node="8"&gt;1041&lt;/STRONG&gt; have disappeared:&lt;/P&gt;
&lt;P&gt;- usage :&amp;nbsp;.1.3.6.1.2.1.25.2.3.1.6.1041&lt;/P&gt;
&lt;P&gt;- max :&amp;nbsp;.1.3.6.1.2.1.25.2.3.1.5.1041&lt;/P&gt;
&lt;P&gt;*Before adding disk space&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ssublue_1-1779092069962.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/71437i0173BE5945E93875/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ssublue_1-1779092069962.png" alt="ssublue_1-1779092069962.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;*After adding disk space&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ssublue_0-1779091849628.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/71436iAE52B43018A49F4B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="ssublue_0-1779091849628.png" alt="ssublue_0-1779091849628.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Related KB :&amp;nbsp;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNuACAW&amp;amp;lang=en_US%E2%80%A9" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PNuACAW&amp;amp;lang=en_US%E2%80%A9&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;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...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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?&lt;/P&gt;
&lt;P&gt;And are there alternative ways to expand the firewall disk space?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2026 08:19:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/log-partition-snmp-oid-deleted-when-aws-vm-series-logging-disk/m-p/1254181#M2457</guid>
      <dc:creator>ssublue</dc:creator>
      <dc:date>2026-05-18T08:19:27Z</dc:date>
    </item>
  </channel>
</rss>

