<?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: Bond Interface Copper &amp;amp; Fiber in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bond-Interface-Copper-amp-Fiber/m-p/155012#M26456</link>
    <description>&lt;P&gt;In addition to what other said, you can form bond port-channel with only single interface. If you are short on free interfaces and would like to get rid of topology work everytime during HW replacement, just use bonds for everything (also for management and sync traffic). You are able to add another slave(s) to the existing bond with no problem.&lt;/P&gt;</description>
    <pubDate>Mon, 15 Aug 2022 19:10:27 GMT</pubDate>
    <dc:creator>JozkoMrkvicka</dc:creator>
    <dc:date>2022-08-15T19:10:27Z</dc:date>
    <item>
      <title>Bond Interface Copper &amp; Fiber</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bond-Interface-Copper-amp-Fiber/m-p/154993#M26453</link>
      <description>&lt;P&gt;Is it possible to have copper and fiber as part of the same port-channel group?&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 13:18:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bond-Interface-Copper-amp-Fiber/m-p/154993#M26453</guid>
      <dc:creator>thant</dc:creator>
      <dc:date>2022-08-15T13:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: Bond Interface Copper &amp; Fiber</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bond-Interface-Copper-amp-Fiber/m-p/154999#M26454</link>
      <description>&lt;P&gt;Generally should be OK as long as the interface speeds are the same. (Will also depend on the adjacent device).&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 23:29:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bond-Interface-Copper-amp-Fiber/m-p/154999#M26454</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2022-08-15T23:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: Bond Interface Copper &amp; Fiber</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bond-Interface-Copper-amp-Fiber/m-p/155003#M26455</link>
      <description>&lt;P&gt;It generally works even if the interface speeds aren't the same. Let's say you have a 1g copper interface and a 10g fiber interface bonded. With LACP, round-robin, or XOR load distribution, it works as if all the interfaces in the bond were the same speed as the slowest. You can get an aggregate throughput of 2g. Maybe a little more if your flows happen to be distributed such that the big flows get hashed to the 10g link, but that's down to luck.&lt;/P&gt;
&lt;P&gt;With active/standby load distribution, you can get 10g, but if that link fails, suddenly it's limited to 1g, which probably isn't a suitable backup. Even this&amp;nbsp;&lt;EM&gt;can be&lt;/EM&gt; okay, if you're moving from an all-1g bond to an all-10g bond, for example.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 14:41:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bond-Interface-Copper-amp-Fiber/m-p/155003#M26455</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2022-08-15T14:41:09Z</dc:date>
    </item>
    <item>
      <title>Re: Bond Interface Copper &amp; Fiber</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bond-Interface-Copper-amp-Fiber/m-p/155012#M26456</link>
      <description>&lt;P&gt;In addition to what other said, you can form bond port-channel with only single interface. If you are short on free interfaces and would like to get rid of topology work everytime during HW replacement, just use bonds for everything (also for management and sync traffic). You are able to add another slave(s) to the existing bond with no problem.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Aug 2022 19:10:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bond-Interface-Copper-amp-Fiber/m-p/155012#M26456</guid>
      <dc:creator>JozkoMrkvicka</dc:creator>
      <dc:date>2022-08-15T19:10:27Z</dc:date>
    </item>
  </channel>
</rss>

