<?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 Re: AWS - Additional logging disk added as legacy disk in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/aws-additional-logging-disk-added-as-legacy-disk/m-p/336354#M84720</link>
    <description>&lt;P&gt;Problem solved&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the steps to follow when you deploy a new panorama using M5.2xlarge EC2 instances :&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Deploy the instance without additional logging disks&lt;/P&gt;&lt;P&gt;2. Upgrade the PANOS from 9.1.2 to 9.1.3&lt;/P&gt;&lt;P&gt;3. Shutdown the instance and attach the additonal disks of 2TB needed for logging.&lt;/P&gt;&lt;P&gt;4. Start the instance and verify that the disks are correctly mounted using "show system disk details"&lt;/P&gt;&lt;P&gt;5. Change panorama mode to panorama instead of management-only "request system system-mode panorama"&lt;/P&gt;&lt;P&gt;6. reboot&amp;nbsp;&lt;/P&gt;&lt;P&gt;7. add logging disks using "request system disk add diskX"&lt;/P&gt;&lt;P&gt;8. verify that disks are added and enabled correctly&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Enjoy&lt;/P&gt;</description>
    <pubDate>Wed, 01 Jul 2020 17:04:10 GMT</pubDate>
    <dc:creator>OUAHID</dc:creator>
    <dc:date>2020-07-01T17:04:10Z</dc:date>
    <item>
      <title>AWS - Additional logging disk added as legacy disk</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/aws-additional-logging-disk-added-as-legacy-disk/m-p/335517#M84551</link>
      <description>&lt;P&gt;&lt;FONT size="2"&gt;Hello,&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;We have deployed a new panorama in aws environnement with version PANOS 9.1.3.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;The panorama is in panorama mode and recognize all the disks attached to the EC2 instance which is m5.2xlarge.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;There is 1 root disk for system&amp;nbsp; and two additional disks of 2TB for logs.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Panorama&amp;gt; show system disk details&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Name : nvme1n1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;State : Present&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Size : 2048000 MB&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Status : Ready for migration&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Reason : Admin disabled&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Name : nvme2n1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;State : Present&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Size : 2048000 MB&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Status : Unavailable&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Reason : Admin disabled&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;When we try to add&amp;nbsp; the first logs disk "nvme1n1" the panorama shows the following message :&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;"You cannot use a legacy disk as a virtual logging disk in panorama mode. After you migrate the data, you must detach it."&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;however , we don't have any problem to add the second one "nvme2n1" and adding it to the local log collector.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Any idea about the fact that the first 2TB disk is considered as legacy disk ?&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Thank you&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jun 2020 13:27:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/aws-additional-logging-disk-added-as-legacy-disk/m-p/335517#M84551</guid>
      <dc:creator>OUAHID</dc:creator>
      <dc:date>2020-06-26T13:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: AWS - Additional logging disk added as legacy disk</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/aws-additional-logging-disk-added-as-legacy-disk/m-p/336354#M84720</link>
      <description>&lt;P&gt;Problem solved&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the steps to follow when you deploy a new panorama using M5.2xlarge EC2 instances :&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Deploy the instance without additional logging disks&lt;/P&gt;&lt;P&gt;2. Upgrade the PANOS from 9.1.2 to 9.1.3&lt;/P&gt;&lt;P&gt;3. Shutdown the instance and attach the additonal disks of 2TB needed for logging.&lt;/P&gt;&lt;P&gt;4. Start the instance and verify that the disks are correctly mounted using "show system disk details"&lt;/P&gt;&lt;P&gt;5. Change panorama mode to panorama instead of management-only "request system system-mode panorama"&lt;/P&gt;&lt;P&gt;6. reboot&amp;nbsp;&lt;/P&gt;&lt;P&gt;7. add logging disks using "request system disk add diskX"&lt;/P&gt;&lt;P&gt;8. verify that disks are added and enabled correctly&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Enjoy&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 17:04:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/aws-additional-logging-disk-added-as-legacy-disk/m-p/336354#M84720</guid>
      <dc:creator>OUAHID</dc:creator>
      <dc:date>2020-07-01T17:04:10Z</dc:date>
    </item>
  </channel>
</rss>

