<?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: Licensing Issues with PAYG Bundle 2 on AWS in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/272141#M619</link>
    <description>&lt;P&gt;I'm having the same issue. This is very odd. it should the very least shows the vm-model.I will raise a case on this.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jun 2019 12:13:22 GMT</pubDate>
    <dc:creator>Retired Member</dc:creator>
    <dc:date>2019-06-21T12:13:22Z</dc:date>
    <item>
      <title>Licensing Issues with PAYG Bundle 2 on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/267891#M606</link>
      <description>&lt;P&gt;I have just setup the PAYG AWS Bundle 2 and am having issues with enabling the URL filtering etc. subscriptions.&lt;/P&gt;&lt;P&gt;I'm unsure if it could be to do with the fact that I am still in the Free Trial, but I would assume these subscriptions would be present in this state?&lt;/P&gt;&lt;P&gt;Below I have attached screenshots of what the current&amp;nbsp;Licensing and Version config. are.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2019-06-07 at 14.18.08.png" style="width: 791px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/20335iA367DCDA5C11DE35/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot 2019-06-07 at 14.18.08.png" alt="Screenshot 2019-06-07 at 14.18.08.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2019-06-07 at 14.18.49.png" style="width: 247px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/20336i5D25F0B5891C2BC6/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot 2019-06-07 at 14.18.49.png" alt="Screenshot 2019-06-07 at 14.18.49.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2019 13:42:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/267891#M606</guid>
      <dc:creator>edd_mann</dc:creator>
      <dc:date>2019-06-07T13:42:35Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing Issues with PAYG Bundle 2 on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/268001#M607</link>
      <description>&lt;P&gt;What is the actual error you are receiving? If you are using a bundle you shouldn't be on a free trial. If you haven't tried this already go back to the licensing tab and fetch licensing again.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2019 16:30:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/268001#M607</guid>
      <dc:creator>jperry1</dc:creator>
      <dc:date>2019-06-07T16:30:48Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing Issues with PAYG Bundle 2 on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/268005#M608</link>
      <description>&lt;P&gt;Thanks for the response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Whenever I attempt to commit changes with subscription based functionality (i..e URL filtering) enabled I get 'No Valid License' errors.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2019-06-07 at 17.36.47.png" style="width: 381px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/20338iBD48B908465286BC/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot 2019-06-07 at 17.36.47.png" alt="Screenshot 2019-06-07 at 17.36.47.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;However, when I check the license page I get the following output which leads me to believe the License is valid? and there is no option to fetch the license again.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2019-06-07 at 14.18.08.png" style="width: 791px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/20339i5F3A744A6676714E/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot 2019-06-07 at 14.18.08.png" alt="Screenshot 2019-06-07 at 14.18.08.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2019 16:39:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/268005#M608</guid>
      <dc:creator>edd_mann</dc:creator>
      <dc:date>2019-06-07T16:39:37Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing Issues with PAYG Bundle 2 on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/272141#M619</link>
      <description>&lt;P&gt;I'm having the same issue. This is very odd. it should the very least shows the vm-model.I will raise a case on this.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2019 12:13:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/272141#M619</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2019-06-21T12:13:22Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing Issues with PAYG Bundle 2 on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/272215#M623</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I just spun up a FW in AWS and short of complaining that the sig pack wasn't&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;loaded the FW worked as expected.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2019 17:13:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/272215#M623</guid>
      <dc:creator>dleitzel</dc:creator>
      <dc:date>2019-06-21T17:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing Issues with PAYG Bundle 2 on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/272463#M628</link>
      <description>&lt;P&gt;Hi all, can you please check the instance type. This was caused by chosing the wrong instance type. Vm-series PAYG model in AWS is a VM-300 model, if you do not allocate the right memory and number of CPUs, then, it wont be able to register itself to the license server. I have changed my instance type to m4.xlarge, the everything is working as expected. I can see the instance now is licensed properly (see the below screenshot).&amp;nbsp; To find out the minimum requirements for VM-300, go to the following link&amp;nbsp;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClDCCA0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClDCCA0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;On how to change EC2 instance type, go to the following link&amp;nbsp;&lt;A href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html" target="_blank"&gt;https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2019-06-24_08-01-30.jpg" style="width: 350px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/20480iFD771CA95AF053F9/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="2019-06-24_08-01-30.jpg" alt="2019-06-24_08-01-30.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 23 Jun 2019 22:02:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/272463#M628</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2019-06-23T22:02:47Z</dc:date>
    </item>
    <item>
      <title>Re: Licensing Issues with PAYG Bundle 2 on AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/272465#M630</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/2533"&gt;@jperry1&lt;/a&gt;&amp;nbsp;there is no option to fetch a license in PAYG model. Once you have registrered the CPUID and serial number in customer support portal (&lt;A href="https://docs.paloaltonetworks.com/vm-series/9-0/vm-series-deployment/license-the-vm-series-firewall/register-the-vm-series-firewall/register-the-usage-based-model-of-the-vm-series-firewall-in-aws-and-azure-no-auth-code.html#" target="_blank"&gt;https://docs.paloaltonetworks.com/vm-series/9-0/vm-series-deployment/license-the-vm-series-firewall/register-the-vm-series-firewall/register-the-usage-based-model-of-the-vm-series-firewall-in-aws-and-azure-no-auth-code.html#&lt;/A&gt;), the instance (if properly sized) will download the license automatically.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 23 Jun 2019 22:07:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/licensing-issues-with-payg-bundle-2-on-aws/m-p/272465#M630</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2019-06-23T22:07:37Z</dc:date>
    </item>
  </channel>
</rss>

