<?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 Backup data lan card in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568653#M715293</link>
    <description>I am configuring 2 N-4000 servers for a cluster.  Each server has 4 lan cards configured as follows:&lt;BR /&gt;Lan0 = primary heartbeat (10/100)&lt;BR /&gt;Lan1 = unconfigured, backup data (10/100/1000)&lt;BR /&gt;Lan2 = secondary heartbeat (10/100/1000)&lt;BR /&gt;Lan3 = primary data (10/100/1000)&lt;BR /&gt;&lt;BR /&gt;doing a cmquerycl indicates lan1 as a possible backup for lan3, which is our intention, and we are under the assumtion that, in the case of lan3 experiencing failure, MCSG will configure lan1 with its information.  Is this assumtion correct?  If so, is there some configuration parameter we missed to enable this because we have tried to test this by pulling lan3's cable out, but nothing happens.  Thanks in advance for your help.&lt;BR /&gt;&lt;BR /&gt;Chris</description>
    <pubDate>Wed, 22 Aug 2001 15:31:01 GMT</pubDate>
    <dc:creator>Christopher McCray_1</dc:creator>
    <dc:date>2001-08-22T15:31:01Z</dc:date>
    <item>
      <title>Backup data lan card</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568653#M715293</link>
      <description>I am configuring 2 N-4000 servers for a cluster.  Each server has 4 lan cards configured as follows:&lt;BR /&gt;Lan0 = primary heartbeat (10/100)&lt;BR /&gt;Lan1 = unconfigured, backup data (10/100/1000)&lt;BR /&gt;Lan2 = secondary heartbeat (10/100/1000)&lt;BR /&gt;Lan3 = primary data (10/100/1000)&lt;BR /&gt;&lt;BR /&gt;doing a cmquerycl indicates lan1 as a possible backup for lan3, which is our intention, and we are under the assumtion that, in the case of lan3 experiencing failure, MCSG will configure lan1 with its information.  Is this assumtion correct?  If so, is there some configuration parameter we missed to enable this because we have tried to test this by pulling lan3's cable out, but nothing happens.  Thanks in advance for your help.&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Wed, 22 Aug 2001 15:31:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568653#M715293</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2001-08-22T15:31:01Z</dc:date>
    </item>
    <item>
      <title>Re: Backup data lan card</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568654#M715294</link>
      <description>provided the configuration is correct, then yes this should happen. Might be a silly question, but have you configured a package that monitors that subnet yet?&lt;BR /&gt;you could also do a cmscancl and post the output file here.</description>
      <pubDate>Wed, 22 Aug 2001 15:55:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568654#M715294</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-08-22T15:55:03Z</dc:date>
    </item>
    <item>
      <title>Re: Backup data lan card</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568655#M715295</link>
      <description>You may need to check the following&lt;BR /&gt;&lt;BR /&gt;1) Check your package configuration file to see if you have this&lt;BR /&gt;&lt;BR /&gt;NET_SWITCHING_ENABLED     YES&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;2) Verify the SUBNET on the primary LAN is being monitored by verifying the package configuration file&lt;BR /&gt;&lt;BR /&gt;SUBNET YOUR_PRIMARY_SUBNET&lt;BR /&gt;&lt;BR /&gt;If you have these two in place, this will work.&lt;BR /&gt;&lt;BR /&gt;-Sri&lt;BR /&gt;</description>
      <pubDate>Wed, 22 Aug 2001 17:10:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568655#M715295</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2001-08-22T17:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: Backup data lan card</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568656#M715296</link>
      <description>Melvyn,&lt;BR /&gt;Sorry it took so long, but here is the output of the cmscancl.  Unfortunately, I had to "sanitize" the IP addresses, but it should still be understandable.  Thank you again for your help.&lt;BR /&gt;&lt;BR /&gt;Sridhar,&lt;BR /&gt;&lt;BR /&gt;I have the LOCAL_LAN_FAILOVER_ALLOWED set to YES and SUBNET is correct.  Thanks</description>
      <pubDate>Wed, 22 Aug 2001 17:43:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568656#M715296</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2001-08-22T17:43:12Z</dc:date>
    </item>
    <item>
      <title>Re: Backup data lan card</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568657#M715297</link>
      <description>according to th ebinary file info in the cmscancl output, you do not have a backup lan!&lt;BR /&gt;&lt;BR /&gt;      Network ID 2:&lt;BR /&gt;        ppa:    3&lt;BR /&gt;        old_ppa:   0&lt;BR /&gt;        mac addr:   0x00306e038ea7&lt;BR /&gt;        hardware path:   0/4/0/0&lt;BR /&gt;        network interface name:  lan3&lt;BR /&gt;        subnet:    10.12.13.0&lt;BR /&gt;        subnet mask:   255.255.255.0&lt;BR /&gt;        ip address:   10.12.13.88&lt;BR /&gt;        flags:    1 (Heartbeat Network)&lt;BR /&gt;        bridged net ID:   1&lt;BR /&gt;&lt;BR /&gt;      Network ID 1:&lt;BR /&gt;        ppa:    0&lt;BR /&gt;        old_ppa:   0&lt;BR /&gt;        mac addr:   0x00306e035982&lt;BR /&gt;        hardware path:   0/0/0/0&lt;BR /&gt;        network interface name:  lan0&lt;BR /&gt;        subnet:    13.14.15.16&lt;BR /&gt;        subnet mask:   255.255.255.252&lt;BR /&gt;        ip address:   13.14.15.17&lt;BR /&gt;        flags:    1 (Heartbeat Network)&lt;BR /&gt;        bridged net ID:   2&lt;BR /&gt;&lt;BR /&gt;      Network ID 3:&lt;BR /&gt;        ppa:    2&lt;BR /&gt;        old_ppa:   0&lt;BR /&gt;        mac addr:   0x00306e0e17d3&lt;BR /&gt;        hardware path:   1/8/0/0&lt;BR /&gt;        network interface name:  lan2&lt;BR /&gt;        subnet:    13.14.15.32&lt;BR /&gt;        subnet mask:   255.255.255.240&lt;BR /&gt;        ip address:   13.14.15.33&lt;BR /&gt;        flags:    1 (Heartbeat Network)&lt;BR /&gt;        bridged net ID:   3&lt;BR /&gt;&lt;BR /&gt;   Node ID 2:&lt;BR /&gt;      Node name:   dmc31&lt;BR /&gt;      first lock pv name:  /dev/dsk/c5t0d2&lt;BR /&gt;      first lock disk interface type: c720&lt;BR /&gt;&lt;BR /&gt;      Network ID 1:&lt;BR /&gt;        ppa:    3&lt;BR /&gt;        old_ppa:   0&lt;BR /&gt;        mac addr:   0x00306e039e3e&lt;BR /&gt;        hardware path:   0/4/0/0&lt;BR /&gt;        network interface name:  lan3&lt;BR /&gt;        subnet:    10.12.13.0&lt;BR /&gt;        subnet mask:   255.255.255.0&lt;BR /&gt;        ip address:   10.12.13.92&lt;BR /&gt;        flags:    1 (Heartbeat Network)&lt;BR /&gt;        bridged net ID:   1&lt;BR /&gt;&lt;BR /&gt;      Network ID 2:&lt;BR /&gt;        ppa:    0&lt;BR /&gt;        old_ppa:   0&lt;BR /&gt;        mac addr:   0x001083963135&lt;BR /&gt;        hardware path:   0/0/0/0&lt;BR /&gt;        network interface name:  lan0&lt;BR /&gt;        subnet:    13.14.15.16&lt;BR /&gt;        subnet mask:   255.255.255.252&lt;BR /&gt;        ip address:   13.14.15.18&lt;BR /&gt;        flags:    1 (Heartbeat Network)&lt;BR /&gt;        bridged net ID:   2&lt;BR /&gt;&lt;BR /&gt;      Network ID 3:&lt;BR /&gt;        ppa:    2&lt;BR /&gt;        old_ppa:   0&lt;BR /&gt;        mac addr:   0x00306e0e1701&lt;BR /&gt;        hardware path:   1/8/0/0&lt;BR /&gt;        network interface name:  lan2&lt;BR /&gt;        subnet:    13.14.15.32&lt;BR /&gt;        subnet mask:   255.255.255.240&lt;BR /&gt;        ip address:   13.14.15.34&lt;BR /&gt;        flags:    1 (Heartbeat Network)&lt;BR /&gt;        bridged net ID:   3&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;the lan you expect to have as standby i snot  there, and is probaly the result of the binary being applied before this lan was actually there.&lt;BR /&gt;you need to reapply the binary with this info in the ascii file and the links all ok.</description>
      <pubDate>Wed, 22 Aug 2001 18:16:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568657#M715297</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-08-22T18:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Backup data lan card</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568658#M715298</link>
      <description>Melvyn, you are the MAN!!!!! As soon as we got your final response, we looked in our cluster.conf file and, sure enough, &lt;BR /&gt;NETWORK_INTERFACE       lan1 &lt;BR /&gt;was not there.  We added it, and rock and roll!!  I apologize for not getting back earlier (much problems elsewhere), but the ten points you are getting from me is  not near enough.  Thanks to you to Sridhar also.&lt;BR /&gt;&lt;BR /&gt;Good luck to you all!&lt;BR /&gt;Chris</description>
      <pubDate>Fri, 24 Aug 2001 16:59:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/backup-data-lan-card/m-p/2568658#M715298</guid>
      <dc:creator>Christopher McCray_1</dc:creator>
      <dc:date>2001-08-24T16:59:24Z</dc:date>
    </item>
  </channel>
</rss>

