<?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: TPC IP cluster alias address in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411647#M65382</link>
    <description>Valker,&lt;BR /&gt;&lt;BR /&gt;you mean that i should set some command on the TCP startup procedure in order to syncronize the cluster alias with the address where my application is running?&lt;BR /&gt;&lt;BR /&gt;Sorry if i maybe i missunderstood but it is not so clear to me.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 01 Nov 2004 13:51:52 GMT</pubDate>
    <dc:creator>maurizio carnesecchi</dc:creator>
    <dc:date>2004-11-01T13:51:52Z</dc:date>
    <item>
      <title>TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411639#M65374</link>
      <description>Hello everybody,&lt;BR /&gt;&lt;BR /&gt;I have a VMS cluster with 2 DS25 and a QUORUM disk.&lt;BR /&gt;Only one machine is active and in the active one a TCP server application is running (only in the active machine).&lt;BR /&gt;The client application, developped in Visual Basic, doesnt know in wich machine the Server is running.&lt;BR /&gt;It is possible to address the server by the client application using the cluster alias IP address? So the cluster should solve the problem to undersatnd where the TCP server application is running.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;maurizio carnesecchi</description>
      <pubDate>Mon, 01 Nov 2004 07:17:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411639#M65374</guid>
      <dc:creator>maurizio carnesecchi</dc:creator>
      <dc:date>2004-11-01T07:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411640#M65375</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;The better way is to have a homegene cluster, where the application runs on both nodes.&lt;BR /&gt;&lt;BR /&gt;By experience I know that the first booted machine gets all the cluster address services.&lt;BR /&gt;So you need to syncronize the boot sequence.&lt;BR /&gt;&lt;BR /&gt;Bojan</description>
      <pubDate>Mon, 01 Nov 2004 07:51:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411640#M65375</guid>
      <dc:creator>Bojan Nemec</dc:creator>
      <dc:date>2004-11-01T07:51:58Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411641#M65376</link>
      <description>Hi Bojan,&lt;BR /&gt;&lt;BR /&gt;i'm agree with you, but, the problem is that we cannot have two homogeneous systems.&lt;BR /&gt;&lt;BR /&gt;The TCP server application need to be mapped in global sections only installed in the active machine.&lt;BR /&gt;&lt;BR /&gt;This global sections are also mapped by many others applications in order to have a sort of online database installed in the memory.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;maurizio&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Nov 2004 08:29:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411641#M65376</guid>
      <dc:creator>maurizio carnesecchi</dc:creator>
      <dc:date>2004-11-01T08:29:06Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411642#M65377</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;Then you must synchronize the boot sequence. (I am not shure but this was a side efect in a homogene cluster, so you must try it).&lt;BR /&gt;&lt;BR /&gt;You can synchronize the boot with cluster wide logical names (replace primary with your node name):&lt;BR /&gt;&lt;BR /&gt;Before starting TCPIP:&lt;BR /&gt;&lt;BR /&gt;$ if f$trnlnm("SYS$NODE").eqs."primary"&lt;BR /&gt;$ then&lt;BR /&gt;$ define/cluster primary_up true&lt;BR /&gt;$ goto secondary_ok&lt;BR /&gt;$ endif&lt;BR /&gt;$secondary_loop:&lt;BR /&gt;$ if f$trnlnm("primary_up").eqs."TRUE"&lt;BR /&gt;$ then&lt;BR /&gt;$ goto secondary_ok&lt;BR /&gt;$ else&lt;BR /&gt;$ wait 00:10&lt;BR /&gt;$ goto secondary_loop&lt;BR /&gt;$ endif&lt;BR /&gt;$secondary_ok:&lt;BR /&gt;&lt;BR /&gt;If you have two startup_vms.com you can split  commands so that you have on the primary node:&lt;BR /&gt;$ define/cluster primary_up true&lt;BR /&gt;&lt;BR /&gt;and on the secondary:&lt;BR /&gt;$secondary_loop:&lt;BR /&gt;$ if f$trnlnm("primary_up").eqs."TRUE"&lt;BR /&gt;$ then&lt;BR /&gt;$ goto secondary_ok&lt;BR /&gt;$ else&lt;BR /&gt;$ wait 00:10&lt;BR /&gt;$ goto secondary_loop&lt;BR /&gt;$ endif&lt;BR /&gt;$secondary_ok:&lt;BR /&gt;&lt;BR /&gt;Maybe will be good to implement some timeout, so the secondary will not wait for infinite, if the primary machine is broken. After timeout you can setup the secondary machin to work as the primary.&lt;BR /&gt;&lt;BR /&gt;Bojan</description>
      <pubDate>Mon, 01 Nov 2004 09:00:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411642#M65377</guid>
      <dc:creator>Bojan Nemec</dc:creator>
      <dc:date>2004-11-01T09:00:53Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411643#M65378</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;you might want to associate the TCPIP cluster alias address with your TCP server application, i.e. during the startup or shutdown of your application enable or disable a TCPIP cluster alias dynamically.&lt;BR /&gt;&lt;BR /&gt;Prior to V5.4, use the SET INT/CLUSTER and SET INT/NOCLUSTER commands, with V5.4 or higher use ifconfig xxx -alias name and ifconfig xxx -alias name delete &lt;BR /&gt;&lt;BR /&gt;(need to invoke @SYS$MANAGER:TCPIP$DEFINE_COMMANDS to define symbols for the UNIX style commands).&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 01 Nov 2004 09:04:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411643#M65378</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2004-11-01T09:04:18Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411644#M65379</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;We have a manifold of your situation.&lt;BR /&gt;&lt;BR /&gt;- 4-node cluster&lt;BR /&gt;- ca 20 different applics, _MOST_ clusterwide, but several are (regrettably, but those are like yours) single-node.&lt;BR /&gt;&lt;BR /&gt;And then, at times we want to do maintenance/upgrades to an applic, during which we will NOT want users in that applic on that node.&lt;BR /&gt;&lt;BR /&gt;To enable this, we use DNS.&lt;BR /&gt;&lt;BR /&gt;DNS has a CNAME for the cluster, that goes round-robin along the nodes (which also allows us to take one node out for maintenance!)&lt;BR /&gt;Clusterwide applics have CNAMES (just the applic name) to the cluster CNAME&lt;BR /&gt;Single-node applics have CNAMES to the currently-active node.&lt;BR /&gt;&lt;BR /&gt;And, we have a menu-procedure to quickly change any of those CNAMES if needed.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;&lt;BR /&gt;Cheers.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Nov 2004 10:26:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411644#M65379</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-11-01T10:26:26Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411645#M65380</link>
      <description>First thanks to everybody.&lt;BR /&gt;&lt;BR /&gt;But i have soemthing not clear.&lt;BR /&gt;&lt;BR /&gt;I would like manage this situation as the cluster manages the telnet services.&lt;BR /&gt;If i try to telenet the cluster alias address, the cluster connect one of the 2 server. If the telent service is disable in one machine i think the cluster will connect always the machine where the telnet service is running.&lt;BR /&gt;&lt;BR /&gt;I dont know if it is possible to do the same with my TCP server application.  &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Nov 2004 13:04:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411645#M65380</guid>
      <dc:creator>maurizio carnesecchi</dc:creator>
      <dc:date>2004-11-01T13:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411646#M65381</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;Ask the Wizard #51 talks about UCX cluster alias:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/wizard/wiz_0051.html" target="_blank"&gt;http://h71000.www7.hp.com/wizard/wiz_0051.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you check with UCX SHOW INT/CLUSTER on both nodes of your cluster, you'll see that only one of the nodes shows up as impersonator, e.g.&lt;BR /&gt;&lt;BR /&gt;UCX&amp;gt; sho int/clus&lt;BR /&gt;                                                           Packets&lt;BR /&gt;Interface   IP_Addr         Network mask          Receive          Send     MTU&lt;BR /&gt;&lt;BR /&gt; SE0        10.20.30.204    255.255.255.0          166452          4882    1500&lt;BR /&gt;   Cluster  10.20.30.205    255.255.255.0       Impersonator&lt;BR /&gt;&lt;BR /&gt; LO0        127.0.0.1       255.0.0.0                  21            41   65535&lt;BR /&gt;&lt;BR /&gt;This is not service-specific, so if you disable the TELNET service on the 'cluster impersonator' node, the TELNET client will still try to access that host. You can fail over the cluster address with UCX SET INT/NOCLUSTER SE0 - but this will disconnect all IP sessions established using the cluster alias.&lt;BR /&gt;&lt;BR /&gt;If you include the UCX SET INT/CLUSTER=... xxx commands in your TCP server startup and shutdown (UCX SET INT/NOCLUSTER ...)procedures, you could easily switch the cluster alias together with the application.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 01 Nov 2004 13:44:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411646#M65381</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2004-11-01T13:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411647#M65382</link>
      <description>Valker,&lt;BR /&gt;&lt;BR /&gt;you mean that i should set some command on the TCP startup procedure in order to syncronize the cluster alias with the address where my application is running?&lt;BR /&gt;&lt;BR /&gt;Sorry if i maybe i missunderstood but it is not so clear to me.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Nov 2004 13:51:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411647#M65382</guid>
      <dc:creator>maurizio carnesecchi</dc:creator>
      <dc:date>2004-11-01T13:51:52Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411648#M65383</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;yes. Depending on your version of TCPIP, just use the appropriate commands to activate the cluster alias during your TCP server application startup and disable the alias in your TCP server application shutdown procedure.&lt;BR /&gt;&lt;BR /&gt;Which version of TCPIP are you running ($ TCPIP SHOW VERS) ?&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 01 Nov 2004 14:01:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411648#M65383</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2004-11-01T14:01:39Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411649#M65384</link>
      <description>Volker,&lt;BR /&gt;&lt;BR /&gt;I dont know my TCP version, and i can check it only tomorrow morning when i will be in the office.   Now i m at home.&lt;BR /&gt;&lt;BR /&gt;Anyway  the operating system is an OpenVMS 7.3 and TCP should be last available with that OS.</description>
      <pubDate>Mon, 01 Nov 2004 14:18:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411649#M65384</guid>
      <dc:creator>maurizio carnesecchi</dc:creator>
      <dc:date>2004-11-01T14:18:19Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411650#M65385</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;do your applications connect to an IP address or to "a" name, (the cluster alias)?&lt;BR /&gt;&lt;BR /&gt;If you use names (and I think you REALLY should!!), then WHERE do you define your names? In every local .HOST , or in a DNS server?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Mon, 01 Nov 2004 16:20:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411650#M65385</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-11-01T16:20:19Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411651#M65386</link>
      <description>You'll need to use the DNS "solution" - this has been discussed in this forum: &lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=385987" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=385987&lt;/A&gt;&lt;BR /&gt;It is on load balancing but your problem is likewise: ANY node in your cluster would be able to serve your VB application. But which one....&lt;BR /&gt;The cluster will be addressed when using the cluster IP address, and one machine - normally the one with most free resources - will react - sending it's IP address, bnot the cluster's one. This differs from the sending address, so the requestor - your application - should have to deal with that.&lt;BR /&gt;It won't, I'm afraid.&lt;BR /&gt;The IP definitions - developed in a Unix environment long time ago - don't take clustering into account. Therefore you need some concept like "impersonator" - OUTSIDE the cluster software. (For what I know (I have no experience in that area) DECNet handles the same concept internally - and transparantly)&lt;BR /&gt;&lt;BR /&gt;Willem</description>
      <pubDate>Tue, 02 Nov 2004 03:17:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411651#M65386</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2004-11-02T03:17:16Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411652#M65387</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;as you're not using TCPIP V5.4, you can use the TCPIP SET INT/CLUSTER commands to dynamically set up the cluster alias on the node, where your TCP server app is running:&lt;BR /&gt;&lt;BR /&gt;Assuming you have an IP interface called WE0&lt;BR /&gt;n.n.n.n is your cluster IP adress&lt;BR /&gt;&lt;BR /&gt;$ TCPIP SET INT/CLUSTER=n.n.n.n WE0&lt;BR /&gt;&lt;BR /&gt;start your TCP server app&lt;BR /&gt;have the clients connect to n.n.n.n&lt;BR /&gt;(test it with TELNET n.n.n.n first)&lt;BR /&gt;&lt;BR /&gt;shutdown your TCP server app&lt;BR /&gt;$ TCPIP SET INT/NOCLUSTER=n.n.n.n WE0&lt;BR /&gt;&lt;BR /&gt;Then issue the same commands on the other node in the cluster, if you want to run your TCP app over there. As your application can only run on ONE node in the cluster at a time, this setup should satisfy your needs.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Tue, 02 Nov 2004 03:36:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411652#M65387</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2004-11-02T03:36:55Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411653#M65388</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;Here we have a somewhat similar situation.&lt;BR /&gt;What we do is:&lt;BR /&gt;- assign each application an IP address and name that are defined in our DNS&lt;BR /&gt;- before an application is started on one of our cluster nodes, we "map" the application's IP address on the main interface:&lt;BR /&gt;    ifconfig WE0 alias &lt;APPL_ADDR&gt;/&lt;NETBITS&gt; &lt;BR /&gt;- then we start the application&lt;BR /&gt;- after the application is halted, we remove the IP address from the main interface:&lt;BR /&gt;    ifconfig WE0 -alias &lt;APPL_NAME&gt;&lt;BR /&gt;&lt;BR /&gt;So clients always connect to the application name and thus to the correct node.&lt;BR /&gt;&lt;BR /&gt;Greetz,&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;&lt;/APPL_NAME&gt;&lt;/NETBITS&gt;&lt;/APPL_ADDR&gt;</description>
      <pubDate>Tue, 02 Nov 2004 04:01:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411653#M65388</guid>
      <dc:creator>Kris Clippeleyr</dc:creator>
      <dc:date>2004-11-02T04:01:23Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411654#M65389</link>
      <description>Volker,&lt;BR /&gt;&lt;BR /&gt;I tryed to use the command u suggest to me but i got this error:&lt;BR /&gt;&lt;BR /&gt;-TCPIP-I-NOMORE, parameter or qualifier NOCLUSTER no longer supported; see the documentation for valid options and re-enter command&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;my TCPIP version is the following one:&lt;BR /&gt;  HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 1&lt;BR /&gt;  on a AlphaServer DS25 running OpenVMS V7.3-2  &lt;BR /&gt;</description>
      <pubDate>Tue, 02 Nov 2004 09:30:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411654#M65389</guid>
      <dc:creator>maurizio carnesecchi</dc:creator>
      <dc:date>2004-11-02T09:30:12Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411655#M65390</link>
      <description>Maurizio,&lt;BR /&gt;&lt;BR /&gt;with TCPIP V5.4 and the failSAFE IP functionality, the TCPIP SET INT/CLUSTER commands are no longer supported and may even cause to destroy the active IP interface config, if executed in the running system.&lt;BR /&gt;&lt;BR /&gt;For V5.4, use these commands (assuming WE0 is your IP interface):&lt;BR /&gt;&lt;BR /&gt;$ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS&lt;BR /&gt;&lt;BR /&gt;$ ifconfig we0 alias n.n.n.n/nn&lt;BR /&gt;&lt;BR /&gt;start your server&lt;BR /&gt;&lt;BR /&gt;To fail over to the other node:&lt;BR /&gt;&lt;BR /&gt;stop your server&lt;BR /&gt;&lt;BR /&gt;$ ifconfig we0 -alias n.n.n.n delete&lt;BR /&gt;&lt;BR /&gt;Help is available with $ TCPIP HELP IFCONFIG&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Tue, 02 Nov 2004 09:48:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411655#M65390</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2004-11-02T09:48:50Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411656#M65391</link>
      <description>as Volker said for V5.4 use ifconfig -alias</description>
      <pubDate>Tue, 02 Nov 2004 09:49:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411656#M65391</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-11-02T09:49:46Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411657#M65392</link>
      <description>Volker ,&lt;BR /&gt;&lt;BR /&gt;I tryed your command:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt; @SYS$MANAGER:TCPIP$DEFINE_COMMANDS&lt;BR /&gt;&amp;gt; ifconfig IE1 -alias 10.2.199.5 delete&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;But when i do that i lost the connection to the machine.&lt;BR /&gt;The address 10.2.199.5 was the address defined during TCPIP$CONFIG &lt;BR /&gt;           C_Addr:&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 02 Nov 2004 10:23:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411657#M65392</guid>
      <dc:creator>maurizio carnesecchi</dc:creator>
      <dc:date>2004-11-02T10:23:26Z</dc:date>
    </item>
    <item>
      <title>Re: TPC IP cluster alias address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411658#M65393</link>
      <description>to which address had you connected when you did the alias delete ?&lt;BR /&gt;&lt;BR /&gt;Did anyone else lose the connection?</description>
      <pubDate>Tue, 02 Nov 2004 11:16:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tpc-ip-cluster-alias-address/m-p/3411658#M65393</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-11-02T11:16:28Z</dc:date>
    </item>
  </channel>
</rss>

