<?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: Replace gateway device in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798852#M392344</link>
    <description>thanks,&lt;BR /&gt;&lt;BR /&gt;only 1 catalyst is configured as default gateway.</description>
    <pubDate>Wed, 15 Jun 2011 09:39:54 GMT</pubDate>
    <dc:creator>yulianto piyut</dc:creator>
    <dc:date>2011-06-15T09:39:54Z</dc:date>
    <item>
      <title>Replace gateway device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798848#M392340</link>
      <description>All,&lt;BR /&gt;&lt;BR /&gt;My network team have a plan to replace catalyst device consists of default gateway used by servers.&lt;BR /&gt;What i must to do to make my server still connect to gateway? the ip for gateway is still same.</description>
      <pubDate>Wed, 15 Jun 2011 06:53:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798848#M392340</guid>
      <dc:creator>yulianto piyut</dc:creator>
      <dc:date>2011-06-15T06:53:26Z</dc:date>
    </item>
    <item>
      <title>Re: Replace gateway device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798849#M392341</link>
      <description>if  the dead gateway detection is on, this should work ok, but if they cut the old one after enabling the new one, there will be a race for arp, - if their mac differ, and the connection may take time to identify it, but the dgd will refresh the internal route entries when the first will be cut&lt;BR /&gt;( 3min  max usually)&lt;BR /&gt;&lt;BR /&gt;if dgd is off, then if the old one is cut after the new one is connect, there will be an unsolicited arp emited by the new one, then the old one will defend its arp and resent a new arp, making a new ire. That new ire will leave for about 20mn at most, so my be a good idea at that time to reduce ip_ire_flush_interval to reduce that time during the switch.&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Jun 2011 07:30:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798849#M392341</guid>
      <dc:creator>Laurent Menase</dc:creator>
      <dc:date>2011-06-15T07:30:56Z</dc:date>
    </item>
    <item>
      <title>Re: Replace gateway device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798850#M392342</link>
      <description>Default configuration for hp-ux 11.31 for dead gateway detection is 1 (on). Currently, my server using APA (LAN Monitor, active standby) for network multipath. This ip (configured with APA) connected to 2 catalyst. One of this catalyst is problem and network team plan to replace it. Catalyst that will be replaced has been set as default gateway. &lt;BR /&gt;&lt;BR /&gt;to minimal downtime, what must I do?&lt;BR /&gt;disable default gateway detection?&lt;BR /&gt;&lt;BR /&gt;can server detect automatically for the new catalyst (with new mac address)? how long it?</description>
      <pubDate>Wed, 15 Jun 2011 07:48:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798850#M392342</guid>
      <dc:creator>yulianto piyut</dc:creator>
      <dc:date>2011-06-15T07:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: Replace gateway device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798851#M392343</link>
      <description>don't disable dgd default is good&lt;BR /&gt;&lt;BR /&gt;if the 2 catalysts can be used as gateway,&lt;BR /&gt;and if the 2 are default gateway, it should work ok just replace.&lt;BR /&gt;&lt;BR /&gt;again if the 2 can be default gateway, and the 2 are configured as gateways, just remove the default gateway to the one to replace, change it, then reenable it.&lt;BR /&gt;&lt;BR /&gt;in fact many possibilities.</description>
      <pubDate>Wed, 15 Jun 2011 09:18:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798851#M392343</guid>
      <dc:creator>Laurent Menase</dc:creator>
      <dc:date>2011-06-15T09:18:26Z</dc:date>
    </item>
    <item>
      <title>Re: Replace gateway device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798852#M392344</link>
      <description>thanks,&lt;BR /&gt;&lt;BR /&gt;only 1 catalyst is configured as default gateway.</description>
      <pubDate>Wed, 15 Jun 2011 09:39:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798852#M392344</guid>
      <dc:creator>yulianto piyut</dc:creator>
      <dc:date>2011-06-15T09:39:54Z</dc:date>
    </item>
    <item>
      <title>Re: Replace gateway device</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798853#M392345</link>
      <description>just avoid that the 2 catalysts ( the old and the new one) have duplicate ip, so disable the old one interface before enabling the new one,&lt;BR /&gt;should work&lt;BR /&gt;you can also use an intermediate ip address configured on the new one,&lt;BR /&gt;then configure a route default to that ip, remove the old default gateway route, shutdown the one to be replaced, enable the old gateway address on the new one, reput the routes.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;or you can just stop your old one, replace.&lt;BR /&gt;- tcp connections can wait up to 10min before resetting by default.</description>
      <pubDate>Wed, 15 Jun 2011 10:19:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-gateway-device/m-p/4798853#M392345</guid>
      <dc:creator>Laurent Menase</dc:creator>
      <dc:date>2011-06-15T10:19:30Z</dc:date>
    </item>
  </channel>
</rss>

