<?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 How to support PIXIE and UEFI operations on the same network in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-support-pixie-and-uefi-operations-on-the-same-network/m-p/72329#M18953</link>
    <description>I have a customer who wants to use PIXIE and UEFI on the same physical network .&lt;BR /&gt;
At the moment the dhcp server scope for the specific network details where the SCCM server is located by a statement in the infoblox scope.&lt;BR /&gt;
&lt;BR /&gt;
I have seen a number of udpforward policy , where the ip address of teh Infoblox and the ip address of the pixi boot server is also part of this policy .&lt;BR /&gt;
&lt;BR /&gt;
So for example&lt;BR /&gt;
&lt;BR /&gt;
entry one { &lt;BR /&gt;
if match all { &lt;BR /&gt;
  destination-port 67 ;&lt;BR /&gt;
}&lt;BR /&gt;
then {&lt;BR /&gt;
  destination-ipaddress 10.10.10.10 ; ( infoblox)&lt;BR /&gt;
}&lt;BR /&gt;
}&lt;BR /&gt;
entry two { &lt;BR /&gt;
if match all { &lt;BR /&gt;
  destination-port 67 ;&lt;BR /&gt;
}&lt;BR /&gt;
then {&lt;BR /&gt;
  destination-ipaddress 20.20.20.20  infoblox)&lt;BR /&gt;
}&lt;BR /&gt;
}&lt;BR /&gt;
entry SCCM-dp01 { &lt;BR /&gt;
if match all { &lt;BR /&gt;
  destination-port 67 ;&lt;BR /&gt;
}&lt;BR /&gt;
then {&lt;BR /&gt;
  destination-ipaddress 192.168.10.1  PIXIE/UEFI server )&lt;BR /&gt;
}&lt;BR /&gt;
}&lt;BR /&gt;
entry SCCM-dp03 { &lt;BR /&gt;
if match all { &lt;BR /&gt;
  destination-port 67 ;&lt;BR /&gt;
}&lt;BR /&gt;
then {&lt;BR /&gt;
  destination-ipaddress 192.168.20.1 ; ( PIXIE etc.&lt;BR /&gt;
}</description>
    <pubDate>Sat, 09 Feb 2019 00:22:05 GMT</pubDate>
    <dc:creator>Rod_Robertson</dc:creator>
    <dc:date>2019-02-09T00:22:05Z</dc:date>
    <item>
      <title>How to support PIXIE and UEFI operations on the same network</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-support-pixie-and-uefi-operations-on-the-same-network/m-p/72329#M18953</link>
      <description>I have a customer who wants to use PIXIE and UEFI on the same physical network .&lt;BR /&gt;
At the moment the dhcp server scope for the specific network details where the SCCM server is located by a statement in the infoblox scope.&lt;BR /&gt;
&lt;BR /&gt;
I have seen a number of udpforward policy , where the ip address of teh Infoblox and the ip address of the pixi boot server is also part of this policy .&lt;BR /&gt;
&lt;BR /&gt;
So for example&lt;BR /&gt;
&lt;BR /&gt;
entry one { &lt;BR /&gt;
if match all { &lt;BR /&gt;
  destination-port 67 ;&lt;BR /&gt;
}&lt;BR /&gt;
then {&lt;BR /&gt;
  destination-ipaddress 10.10.10.10 ; ( infoblox)&lt;BR /&gt;
}&lt;BR /&gt;
}&lt;BR /&gt;
entry two { &lt;BR /&gt;
if match all { &lt;BR /&gt;
  destination-port 67 ;&lt;BR /&gt;
}&lt;BR /&gt;
then {&lt;BR /&gt;
  destination-ipaddress 20.20.20.20  infoblox)&lt;BR /&gt;
}&lt;BR /&gt;
}&lt;BR /&gt;
entry SCCM-dp01 { &lt;BR /&gt;
if match all { &lt;BR /&gt;
  destination-port 67 ;&lt;BR /&gt;
}&lt;BR /&gt;
then {&lt;BR /&gt;
  destination-ipaddress 192.168.10.1  PIXIE/UEFI server )&lt;BR /&gt;
}&lt;BR /&gt;
}&lt;BR /&gt;
entry SCCM-dp03 { &lt;BR /&gt;
if match all { &lt;BR /&gt;
  destination-port 67 ;&lt;BR /&gt;
}&lt;BR /&gt;
then {&lt;BR /&gt;
  destination-ipaddress 192.168.20.1 ; ( PIXIE etc.&lt;BR /&gt;
}</description>
      <pubDate>Sat, 09 Feb 2019 00:22:05 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/how-to-support-pixie-and-uefi-operations-on-the-same-network/m-p/72329#M18953</guid>
      <dc:creator>Rod_Robertson</dc:creator>
      <dc:date>2019-02-09T00:22:05Z</dc:date>
    </item>
  </channel>
</rss>

