<?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 Auto-attaching VM series to Panorama in AWS in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/auto-attaching-vm-series-to-panorama-in-aws/m-p/526079#M1778</link>
    <description>&lt;P&gt;I am trying to boot and auto-attach a VM series FW to Panorama in AWS. I am specifying the user-data as follows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;type=dhcp-client&lt;BR /&gt;hostname=aws-palo-1&lt;BR /&gt;panorama-server=a.b.c.d&lt;BR /&gt;tplname=lz-firewall&lt;BR /&gt;dgname=lz-firewall&lt;BR /&gt;dns-primary=8.8.8.8&lt;BR /&gt;dns-secondary=8.8.4.4&lt;BR /&gt;op-command-modes=mgmt-interface-swap&lt;BR /&gt;dhcp-send-hostname=yes&lt;BR /&gt;dhcp-send-client-id=yes&lt;BR /&gt;dhcp-accept-server-hostname=yes&lt;BR /&gt;dhcp-accept-server-domain=yes&lt;BR /&gt;vm-auth-key=&amp;lt;omitted&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But after the firewall boots it is not attaching itself to Panorama. Is it supposed to connect to Panorama and add itself? What's the point of the vm auth key?&lt;/P&gt;</description>
    <pubDate>Fri, 06 Jan 2023 01:35:13 GMT</pubDate>
    <dc:creator>BBartik</dc:creator>
    <dc:date>2023-01-06T01:35:13Z</dc:date>
    <item>
      <title>Auto-attaching VM series to Panorama in AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/auto-attaching-vm-series-to-panorama-in-aws/m-p/526079#M1778</link>
      <description>&lt;P&gt;I am trying to boot and auto-attach a VM series FW to Panorama in AWS. I am specifying the user-data as follows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;type=dhcp-client&lt;BR /&gt;hostname=aws-palo-1&lt;BR /&gt;panorama-server=a.b.c.d&lt;BR /&gt;tplname=lz-firewall&lt;BR /&gt;dgname=lz-firewall&lt;BR /&gt;dns-primary=8.8.8.8&lt;BR /&gt;dns-secondary=8.8.4.4&lt;BR /&gt;op-command-modes=mgmt-interface-swap&lt;BR /&gt;dhcp-send-hostname=yes&lt;BR /&gt;dhcp-send-client-id=yes&lt;BR /&gt;dhcp-accept-server-hostname=yes&lt;BR /&gt;dhcp-accept-server-domain=yes&lt;BR /&gt;vm-auth-key=&amp;lt;omitted&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But after the firewall boots it is not attaching itself to Panorama. Is it supposed to connect to Panorama and add itself? What's the point of the vm auth key?&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jan 2023 01:35:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/auto-attaching-vm-series-to-panorama-in-aws/m-p/526079#M1778</guid>
      <dc:creator>BBartik</dc:creator>
      <dc:date>2023-01-06T01:35:13Z</dc:date>
    </item>
    <item>
      <title>Re: Auto-attaching VM series to Panorama in AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/auto-attaching-vm-series-to-panorama-in-aws/m-p/526152#M1780</link>
      <description>&lt;P&gt;The issue was I did not have the proper&amp;nbsp;&lt;SPAN&gt;tplname value. I was using a template name, it should have been the stack name.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jan 2023 14:01:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/auto-attaching-vm-series-to-panorama-in-aws/m-p/526152#M1780</guid>
      <dc:creator>BBartik</dc:creator>
      <dc:date>2023-01-06T14:01:38Z</dc:date>
    </item>
  </channel>
</rss>

