<?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: Set zone via CLI does not work in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/1234664#M124831</link>
    <description>&lt;P&gt;Logging in to say thank you.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 24 Jul 2025 22:40:37 GMT</pubDate>
    <dc:creator>AdamGoepel-Stillman</dc:creator>
    <dc:date>2025-07-24T22:40:37Z</dc:date>
    <item>
      <title>Set zone via CLI does not work</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/448897#M100871</link>
      <description>&lt;P&gt;admin@firewall(active)# set vsys vsys1 zone test network layer3 ethernet1/17.66&lt;/P&gt;&lt;P&gt;Server error : layer3 'ethernet1/17.66' is not a valid reference&lt;/P&gt;</description>
      <pubDate>Sun, 21 Nov 2021 20:48:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/448897#M100871</guid>
      <dc:creator>davistg</dc:creator>
      <dc:date>2021-11-21T20:48:44Z</dc:date>
    </item>
    <item>
      <title>Re: Set zone via CLI does not work</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/448901#M100872</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/91874"&gt;@davistg&lt;/a&gt; ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you create the zone first with the "set vsys vsys1 zone test" command?&amp;nbsp; Also, you will need to create interface ethernet1/17.66&amp;nbsp; as a layer3 interface if it doesn't already exist.&amp;nbsp; Then, your command should work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Sun, 21 Nov 2021 21:19:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/448901#M100872</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2021-11-21T21:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: Set zone via CLI does not work</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/1226344#M123957</link>
      <description>&lt;P&gt;I had the same issue. Here is the solution:&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/general-topics/panorama-cli-command-to-add-a-tunnel-interface-to-a-zone/td-p/138404" target="_blank" rel="noopener"&gt;https://live.paloaltonetworks.com/t5/general-topics/panorama-cli-command-to-add-a-tunnel-interface-to-a-zone/td-p/138404&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You have to import the interface into the vsys before the Zone will "see" it and be able to be assigned to it&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;set config vsys vsys1 import network interface ethernet1/1.1001&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here is a full set of steps to create new ethernet subinterface, for example, and assign it to the myZone zone:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;# Create subinterface w/ vlan tag, mgmt profile, comment, and IP address
set config network interface ethernet ethernet1/1 layer3 units ethernet1/1.1001 tag 1001 interface-management-profile "Ping" comment "Interface" ip 192.168.100.1/24

# Set the virtual router for the new interface
set config network virtual-router default interface ethernet1/1.1001

# Import the new interface into the vsys (so the Zone can see it as an available interface to add)
set config vsys vsys1 import network interface ethernet1/1.1001

# Set the Zone for the new interface
set config vsys vsys1 zone MyZone network layer3 ethernet1/1.1001

# (Optional, but helpful in many scenarios) Set up DHCP relaying to an existing DHCP server (saved in variable $DHCPSERVER)
set config network dhcp interface ethernet1/1.1001 relay ip server $DHCPSERVER enabled yes&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Apr 2025 17:23:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/1226344#M123957</guid>
      <dc:creator>treeef</dc:creator>
      <dc:date>2025-04-11T17:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: Set zone via CLI does not work</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/1234664#M124831</link>
      <description>&lt;P&gt;Logging in to say thank you.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jul 2025 22:40:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/1234664#M124831</guid>
      <dc:creator>AdamGoepel-Stillman</dc:creator>
      <dc:date>2025-07-24T22:40:37Z</dc:date>
    </item>
    <item>
      <title>Re: Set zone via CLI does not work</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/1234695#M124835</link>
      <description>&lt;P&gt;Thanks! You're quite welcome and I'm glad it was helpful.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jul 2025 12:26:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/set-zone-via-cli-does-not-work/m-p/1234695#M124835</guid>
      <dc:creator>treeef</dc:creator>
      <dc:date>2025-07-25T12:26:08Z</dc:date>
    </item>
  </channel>
</rss>

