<?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 Isolated Backup Network via NIC Teaming in Networking</title>
    <link>https://community.hpe.com/t5/networking/isolated-backup-network-via-nic-teaming/m-p/4515274#M1808</link>
    <description>&lt;!--!*#--&gt;I am setting up an isolated backup network that I would like to keep production traffic off and visa versa.&lt;BR /&gt;The issue I am having is that if I enable the "Backup Network" Team, ip resolves eventually go to this network team which is isolated to its self via Vlan 110.&lt;BR /&gt;I would like to configure the Teams based on priority or exclusion. Where Team Nic01 is priority one, Team Nic02 is priority two, and Backup Network is only used by the backup software that sees only what server is on that Vlan.&lt;BR /&gt;Currently the Teams are configured with TLB and Round Robin (packet order not guaranteed)&lt;BR /&gt;&lt;BR /&gt;I thank you in advance for any suggestions.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Network Team Nic01 172.22.30.xx, Vlan 10&lt;BR /&gt;Network Team Nic02 192.1.1.xx, Vlan 11&lt;BR /&gt;Backup Network 172.22.130.xx, Vlan 110&lt;BR /&gt;&lt;BR /&gt;Vlan 10 sees Vlan 11, Vlan 11 sees Vlan 10  but Vlan 110 does not see either Vlan 10 or 11&lt;BR /&gt;</description>
    <pubDate>Fri, 16 Oct 2009 02:11:36 GMT</pubDate>
    <dc:creator>Romy Aquino</dc:creator>
    <dc:date>2009-10-16T02:11:36Z</dc:date>
    <item>
      <title>Isolated Backup Network via NIC Teaming</title>
      <link>https://community.hpe.com/t5/networking/isolated-backup-network-via-nic-teaming/m-p/4515274#M1808</link>
      <description>&lt;!--!*#--&gt;I am setting up an isolated backup network that I would like to keep production traffic off and visa versa.&lt;BR /&gt;The issue I am having is that if I enable the "Backup Network" Team, ip resolves eventually go to this network team which is isolated to its self via Vlan 110.&lt;BR /&gt;I would like to configure the Teams based on priority or exclusion. Where Team Nic01 is priority one, Team Nic02 is priority two, and Backup Network is only used by the backup software that sees only what server is on that Vlan.&lt;BR /&gt;Currently the Teams are configured with TLB and Round Robin (packet order not guaranteed)&lt;BR /&gt;&lt;BR /&gt;I thank you in advance for any suggestions.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Network Team Nic01 172.22.30.xx, Vlan 10&lt;BR /&gt;Network Team Nic02 192.1.1.xx, Vlan 11&lt;BR /&gt;Backup Network 172.22.130.xx, Vlan 110&lt;BR /&gt;&lt;BR /&gt;Vlan 10 sees Vlan 11, Vlan 11 sees Vlan 10  but Vlan 110 does not see either Vlan 10 or 11&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Oct 2009 02:11:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/isolated-backup-network-via-nic-teaming/m-p/4515274#M1808</guid>
      <dc:creator>Romy Aquino</dc:creator>
      <dc:date>2009-10-16T02:11:36Z</dc:date>
    </item>
    <item>
      <title>Re: Isolated Backup Network via NIC Teaming</title>
      <link>https://community.hpe.com/t5/networking/isolated-backup-network-via-nic-teaming/m-p/4515275#M1809</link>
      <description>Im not sure if I understand your issue, but you can add static routes on windows, it will allow to send traffic to an specific gateway.&lt;BR /&gt;&lt;BR /&gt;For example, if you were on VLAN10 and you had a gateway on 172.22.30.1 configured to access the 10.10.10.0/24 network, you can use a route add statement like this:&lt;BR /&gt;&lt;BR /&gt;route ADD 10.10.10.0 MASK 255.255.255.0 172.22.30.1&lt;BR /&gt;&lt;BR /&gt;Then the traffic for that network will go to that gateway instead of the backup network.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Nov 2009 00:52:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/networking/isolated-backup-network-via-nic-teaming/m-p/4515275#M1809</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2009-11-17T00:52:46Z</dc:date>
    </item>
  </channel>
</rss>

