<?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: 2 nic cards on different subnet in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/2-nic-cards-on-different-subnet/m-p/6853277#M81608</link>
    <description>&lt;P&gt;Interesting issue!&lt;/P&gt;&lt;P&gt;Did you work this one out? I suppose iptables and NAT rules could be&amp;nbsp;used to accomplish this. But maybe also by assigning the virtual IP to a subinterface (like em3:1) and not directly to em3?&lt;/P&gt;</description>
    <pubDate>Sat, 23 Apr 2016 13:59:56 GMT</pubDate>
    <dc:creator>Johan Guldmyr</dc:creator>
    <dc:date>2016-04-23T13:59:56Z</dc:date>
    <item>
      <title>2 nic cards on different subnet</title>
      <link>https://community.hpe.com/t5/operating-system-linux/2-nic-cards-on-different-subnet/m-p/6850878#M81607</link>
      <description>&lt;P&gt;Team,&lt;/P&gt;&lt;P&gt;We have 2 node RHEL cluster. 6.7 &amp;nbsp;App and DB in 2 different subnet.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Node 1&lt;/P&gt;&lt;P&gt;====&lt;/P&gt;&lt;P&gt;App 10.1.11.7 &amp;nbsp;Physical&amp;nbsp;&lt;/P&gt;&lt;P&gt;DB 10.1.12.9 Physical&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Node 2&lt;/P&gt;&lt;P&gt;===&lt;/P&gt;&lt;P&gt;App 10.1.11.9 Physical&lt;/P&gt;&lt;P&gt;DB 10.1.12.7 Physical&lt;/P&gt;&lt;P&gt;We have a VIP configured 10.1.11.8&amp;nbsp;&lt;/P&gt;&lt;P&gt;When app is down , the filesystem alongwith ip moves to failover node.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Route -n from both nodes given below :&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;From 10.1.11.7&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;route -n&lt;BR /&gt;Kernel IP routing table&lt;BR /&gt;Destination Gateway Genmask Flags Metric Ref Use Iface&lt;BR /&gt;10.1.12.0 0.0.0.0 255.255.255.128 U 0 0 0 em4&lt;BR /&gt;10.1.11.0 0.0.0.0 255.255.255.128 U 0 0 0 em3&lt;BR /&gt;169.254.0.0 0.0.0.0 255.255.0.0 U 1008 0 0 em3&lt;BR /&gt;169.254.0.0 0.0.0.0 255.255.0.0 U 1009 0 0 em4&lt;BR /&gt;0.0.0.0 10.1.11.1 0.0.0.0 UG 0 0 0 em3&lt;/P&gt;&lt;P&gt;ip addr show&lt;BR /&gt;1: lo: &amp;lt;LOOPBACK,UP,LOWER_UP&amp;gt; mtu 65536 qdisc noqueue state UNKNOWN&lt;BR /&gt;link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00&lt;BR /&gt;inet 127.0.0.1/8 scope host lo&lt;BR /&gt;inet6 ::1/128 scope host&lt;BR /&gt;valid_lft forever preferred_lft forever&lt;BR /&gt;2: p2p1: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether a0:36:9f:83:f0:c4 brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;3: p2p2: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether a0:36:9f:83:f0:c6 brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;4: p3p1: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether a0:36:9f:7c:54:e8 brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;5: p3p2: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether a0:36:9f:7c:54:ea brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;6: em1: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether 14:18:77:6a:35:07 brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;7: em2: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether 14:18:77:6a:35:08 brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;8: em3: &amp;lt;BROADCAST,MULTICAST,UP,LOWER_UP&amp;gt; mtu 1500 qdisc mq state UP qlen 1000&lt;BR /&gt;link/ether 14:18:77:6a:35:09 brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;inet 10.1.11.7/25 brd 10.1.11.127 scope global em3&lt;BR /&gt;inet 10.1.11.8/25 scope global secondary em3&lt;BR /&gt;inet6 fe80::1618:77ff:fe6a:3509/64 scope link&lt;BR /&gt;valid_lft forever preferred_lft forever&lt;BR /&gt;9: em4: &amp;lt;BROADCAST,MULTICAST,UP,LOWER_UP&amp;gt; mtu 1500 qdisc mq state UP qlen 1000&lt;BR /&gt;link/ether 14:18:77:6a:35:0a brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;inet 10.1.12.9/25 brd 10.1.12.127 scope global em4&lt;BR /&gt;inet6 fe80::1618:77ff:fe6a:350a/64 scope link&lt;BR /&gt;valid_lft forever preferred_lft forever&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From 10.1.12.7&lt;/P&gt;&lt;P&gt;route -n&lt;BR /&gt;Kernel IP routing table&lt;BR /&gt;Destination Gateway Genmask Flags Metric Ref Use Iface&lt;BR /&gt;10.1.12.0 0.0.0.0 255.255.255.128 U 0 0 0 em1&lt;BR /&gt;10.1.11.0 0.0.0.0 255.255.255.128 U 0 0 0 em2&lt;BR /&gt;169.254.0.0 0.0.0.0 255.255.0.0 U 1006 0 0 em1&lt;BR /&gt;169.254.0.0 0.0.0.0 255.255.0.0 U 1007 0 0 em2&lt;BR /&gt;0.0.0.0 10.1.12.1 0.0.0.0 UG 0 0 0 em1&lt;/P&gt;&lt;P&gt;ip addr show&lt;BR /&gt;1: lo: &amp;lt;LOOPBACK,UP,LOWER_UP&amp;gt; mtu 65536 qdisc noqueue state UNKNOWN&lt;BR /&gt;link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00&lt;BR /&gt;inet 127.0.0.1/8 scope host lo&lt;BR /&gt;inet6 ::1/128 scope host&lt;BR /&gt;valid_lft forever preferred_lft forever&lt;BR /&gt;2: p2p1: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether a0:36:9f:84:04:b0 brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;3: p2p2: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether a0:36:9f:84:04:b2 brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;4: p3p1: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether a0:36:9f:7c:58:8c brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;5: p3p2: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether a0:36:9f:7c:58:8e brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;6: em1: &amp;lt;BROADCAST,MULTICAST,UP,LOWER_UP&amp;gt; mtu 1500 qdisc mq state UP qlen 1000&lt;BR /&gt;link/ether 14:18:77:66:c8:ac brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;inet 10.1.12.7/25 brd 10.1.12.127 scope global em1&lt;BR /&gt;inet 10.1.12.8/25 scope global secondary em1&lt;BR /&gt;inet6 fe80::1618:77ff:fe66:c8ac/64 scope link&lt;BR /&gt;valid_lft forever preferred_lft forever&lt;BR /&gt;7: em2: &amp;lt;BROADCAST,MULTICAST,UP,LOWER_UP&amp;gt; mtu 1500 qdisc mq state UP qlen 1000&lt;BR /&gt;link/ether 14:18:77:66:c8:ad brd ff:ff:ff:ff:ff:ff&lt;/P&gt;&lt;P&gt;We need traffic coming out of 10.1.12.7 to be from 10.1.11.9 Physical IP , but as of now its coming from 10.1.12.7 which we cannot open at Firewall due to compliance issues.&lt;/P&gt;&lt;P&gt;Suggest a solution for the same.&lt;BR /&gt;inet 10.1.11.9/25 brd 10.1.11.127 scope global em2&lt;BR /&gt;inet6 fe80::1618:77ff:fe66:c8ad/64 scope link&lt;BR /&gt;valid_lft forever preferred_lft forever&lt;BR /&gt;8: em3: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether 14:18:77:66:c8:ae brd ff:ff:ff:ff:ff:ff&lt;BR /&gt;9: em4: &amp;lt;BROADCAST,MULTICAST&amp;gt; mtu 1500 qdisc noop state DOWN qlen 1000&lt;BR /&gt;link/ether 14:18:77:66:c8:af brd ff:ff:ff:ff:ff:ff&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2016 06:27:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/2-nic-cards-on-different-subnet/m-p/6850878#M81607</guid>
      <dc:creator>chindi</dc:creator>
      <dc:date>2016-04-15T06:27:45Z</dc:date>
    </item>
    <item>
      <title>Re: 2 nic cards on different subnet</title>
      <link>https://community.hpe.com/t5/operating-system-linux/2-nic-cards-on-different-subnet/m-p/6853277#M81608</link>
      <description>&lt;P&gt;Interesting issue!&lt;/P&gt;&lt;P&gt;Did you work this one out? I suppose iptables and NAT rules could be&amp;nbsp;used to accomplish this. But maybe also by assigning the virtual IP to a subinterface (like em3:1) and not directly to em3?&lt;/P&gt;</description>
      <pubDate>Sat, 23 Apr 2016 13:59:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/2-nic-cards-on-different-subnet/m-p/6853277#M81608</guid>
      <dc:creator>Johan Guldmyr</dc:creator>
      <dc:date>2016-04-23T13:59:56Z</dc:date>
    </item>
  </channel>
</rss>

