<?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: Cluster Alias.. in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499708#M67202</link>
    <description>Hi Mobeen,&lt;BR /&gt;&lt;BR /&gt;    What I was asking for is something like this... If you want to get a node_name you can use f$getsyi("nodename". The same way is there any way to find the cluster alias. Its true that you can find it from UCX SHOW INTERFACE/FULL. I think the other solution for patches was good. Thanks really.&lt;BR /&gt;&lt;BR /&gt;Joseph,&lt;BR /&gt;&lt;BR /&gt;    Thanks for your efforts. I just wanted to know if there any possiblities other than extracting the data from a text file after directing the output of DCL commands to it. Because, I wanted to create a command procedure wherein I just wanted to reduce the coding. &lt;BR /&gt; &lt;BR /&gt;    I knew the stuffs you provided me. Hope you agree that I am a SysAdmin.:-) :-). &lt;BR /&gt;&lt;BR /&gt;Muthuvel.B</description>
    <pubDate>Tue, 08 Mar 2005 04:22:41 GMT</pubDate>
    <dc:creator>Muthuvel.B</dc:creator>
    <dc:date>2005-03-08T04:22:41Z</dc:date>
    <item>
      <title>Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499705#M67199</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;   Is there any way to find out the Cluster_Alias name, Cluster IP_address and the patches installed on a system using command procedures? &lt;BR /&gt;&lt;BR /&gt;Muthuvel.B</description>
      <pubDate>Tue, 08 Mar 2005 02:55:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499705#M67199</guid>
      <dc:creator>Muthuvel.B</dc:creator>
      <dc:date>2005-03-08T02:55:48Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499706#M67200</link>
      <description>Muthu,&lt;BR /&gt;Yes its possible.&lt;BR /&gt;&lt;BR /&gt;&lt;CLUSTER alias="" name=""&gt;&lt;BR /&gt;Could you elaborate what you are referring to by this. Normally in DNS round robin, you actually have a cluster alias name defined and that name alternates between different IP addresses for each of the nodes in the cluster&lt;BR /&gt;For example&lt;BR /&gt;I have a cluster called SUN and this cluster consists of the nodes SUN1, SUN2 and SUN3.&lt;BR /&gt;Assuming that SUN is defined as DNS round robin, the first hit to SUN resolves the IP for SUN1, 2nd to SUN2, 3rd to SUN3, 4th to SUN1 and so on. Do note that there is no IP for SUN.&lt;BR /&gt;So could you now clarify what you are asking for ?&lt;BR /&gt;&lt;BR /&gt;As for the patches applied...you could get that from SYS$UPDATE:VMSINSTAL.HISTORY&lt;BR /&gt;If you would like to search for patches installed in a particular month then you could do something like&lt;BR /&gt;$pipe type sys$update:VMSINSTAL.HISTORY | search sys$input "FEB-2005"&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;Mobeen&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/CLUSTER&gt;</description>
      <pubDate>Tue, 08 Mar 2005 03:05:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499706#M67200</guid>
      <dc:creator>Mobeen_1</dc:creator>
      <dc:date>2005-03-08T03:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499707#M67201</link>
      <description>First of all, as a system-manager, You should know it :-)&lt;BR /&gt;&lt;BR /&gt;TCPIP alias: depends on the TCP/IP stack , for TCPIP services (UCX):&lt;BR /&gt;  TCPIP SHOW INTERFACE xxx /FULL&lt;BR /&gt;Cluster alias under the heading "Cluster Impersonator".&lt;BR /&gt;&lt;BR /&gt;Decnet (Phase V):&lt;BR /&gt;  NCL show all&lt;BR /&gt;&lt;BR /&gt;Under "Identifiers" You will see the address towers (like NSP or Ositransport) twice, the second one is the cluster alias.&lt;BR /&gt;It is defined in SYS$SPECIFIC:[SYSMGR]NET$ALIAS_STARTUP.NCL&lt;BR /&gt;Example: &lt;BR /&gt;DNA_OSInetwork , 47:20:00-0D:AA-00-04-00-69-35:20 &lt;BR /&gt;69-35&lt;BR /&gt;Hex 3569 = decimal 13673 = Decnet IV addresse&lt;BR /&gt;13.361&lt;BR /&gt;If You know the cluster alias name, then use &lt;BR /&gt;decnet_register to look up the name.&lt;BR /&gt;&lt;BR /&gt;Decnet (Phase IV): NCP SHOW EXECUTOR should give similar info.&lt;BR /&gt;&lt;BR /&gt;Installed patches:&lt;BR /&gt;&lt;BR /&gt; PRODUCT SHOW HISTORY&lt;BR /&gt;lists all installed products including patches.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;From inside a DCL procedure, I know no other way than to analyze the output of the commands above.</description>
      <pubDate>Tue, 08 Mar 2005 03:28:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499707#M67201</guid>
      <dc:creator>Joseph Huber_1</dc:creator>
      <dc:date>2005-03-08T03:28:24Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499708#M67202</link>
      <description>Hi Mobeen,&lt;BR /&gt;&lt;BR /&gt;    What I was asking for is something like this... If you want to get a node_name you can use f$getsyi("nodename". The same way is there any way to find the cluster alias. Its true that you can find it from UCX SHOW INTERFACE/FULL. I think the other solution for patches was good. Thanks really.&lt;BR /&gt;&lt;BR /&gt;Joseph,&lt;BR /&gt;&lt;BR /&gt;    Thanks for your efforts. I just wanted to know if there any possiblities other than extracting the data from a text file after directing the output of DCL commands to it. Because, I wanted to create a command procedure wherein I just wanted to reduce the coding. &lt;BR /&gt; &lt;BR /&gt;    I knew the stuffs you provided me. Hope you agree that I am a SysAdmin.:-) :-). &lt;BR /&gt;&lt;BR /&gt;Muthuvel.B</description>
      <pubDate>Tue, 08 Mar 2005 04:22:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499708#M67202</guid>
      <dc:creator>Muthuvel.B</dc:creator>
      <dc:date>2005-03-08T04:22:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499709#M67203</link>
      <description>Muthu,&lt;BR /&gt;In your environment does the following theory hold good&lt;BR /&gt;&lt;BR /&gt;Is the cluster alias the first 5 characters of any node name in the cluster ?&lt;BR /&gt;&lt;BR /&gt;Illustration :-&lt;BR /&gt;Lets assume we have a cluster with 3 nodes named VMSND1, VMSND2 and VMSND3, then the cluster alias is the first 5 chars of any node name .. i.e VMSND in this case&lt;BR /&gt;&lt;BR /&gt;If the above theory holds good in your case, let me know, i will post something :)&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;Mobeen</description>
      <pubDate>Tue, 08 Mar 2005 04:52:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499709#M67203</guid>
      <dc:creator>Mobeen_1</dc:creator>
      <dc:date>2005-03-08T04:52:26Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499710#M67204</link>
      <description>Hi Mobeen,&lt;BR /&gt;&lt;BR /&gt;    In my environment, no such terminology is being used. The cluster alias for many of the clusters is entirely different than the node names. On some nodes, I find some logicals like SYS$CLUSTER_NAME or like that. But on the others I dont find it which means that its not a default one.&lt;BR /&gt;&lt;BR /&gt;    For the cluster Ip address, i think as Joseph said, we can use the SH  INTER/FULL.&lt;BR /&gt;But once again we will have to direct it to some files and extract it.&lt;BR /&gt;&lt;BR /&gt;    Anyway pls send me the stuffs which you have right now.&lt;BR /&gt;&lt;BR /&gt;Muthuvel.B</description>
      <pubDate>Tue, 08 Mar 2005 05:11:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499710#M67204</guid>
      <dc:creator>Muthuvel.B</dc:creator>
      <dc:date>2005-03-08T05:11:02Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499711#M67205</link>
      <description>Muthuvel,&lt;BR /&gt;Now i understand what you are looking for. But the way to accomplish depends on the TCPIP component you are running... HP TCPIP or TCPware from Process Software and so on.&lt;BR /&gt;&lt;BR /&gt;What is the goal that you are trying to achieve.. ?&lt;BR /&gt;&lt;BR /&gt;Are you trying to write a command file that is generic enough and can run on any system and get the following details&lt;BR /&gt;&lt;BR /&gt;1. Determine if a node is part of cluster&lt;BR /&gt;   or stand alone&lt;BR /&gt;2. Then determine what patches are installed&lt;BR /&gt;   on that system and&lt;BR /&gt;3. Only if that system is part of the &lt;BR /&gt;   cluster then find out the IP alias ?&lt;BR /&gt;&lt;BR /&gt;If this is what you like, then may be i could quickly write one, test here and upload it :)&lt;BR /&gt;&lt;BR /&gt;rgds&lt;BR /&gt;Mobeen</description>
      <pubDate>Tue, 08 Mar 2005 05:36:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499711#M67205</guid>
      <dc:creator>Mobeen_1</dc:creator>
      <dc:date>2005-03-08T05:36:40Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499712#M67206</link>
      <description>Hi Mobeen,&lt;BR /&gt;&lt;BR /&gt;   You got exactly what I want. Also you are right that I am writing a generic procedure which I would be using on several nodes. &lt;BR /&gt;I can find if a node is a member of a cluster or not. And ofcourse the patches too. But the problem is with the cluster_alias and ip. I badly need it.&lt;BR /&gt;&lt;BR /&gt;   I want to give you an example for this. Say there are three nodes in a cluster NODEA, NODEB and NODEC. If these have ips like x.x.x.1, x.x.x.2 and x.x.x.3, we also have another ip x.x.x.4 which is meant for the cluster with Cluster_alias name. It also has an entry in TCPIP route database. Looks odd???? Me too...&lt;BR /&gt;&lt;BR /&gt;   Hope you got it..&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Muthuvel.B</description>
      <pubDate>Tue, 08 Mar 2005 06:28:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499712#M67206</guid>
      <dc:creator>Muthuvel.B</dc:creator>
      <dc:date>2005-03-08T06:28:51Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499713#M67207</link>
      <description>Muthuvel, Mobeen,&lt;BR /&gt;&lt;BR /&gt;_IF_ you are using DNS round-robin, then technically you are _NOT_ using a cluster alias!&lt;BR /&gt;What you are doing is: you have defined a CNAME, which arternatingly translates into a cyclus of (names or adresses of) nodes.&lt;BR /&gt;Using Metric &amp;amp; Loadbroker, this same principle is used for Load Balancing.&lt;BR /&gt;&lt;BR /&gt;IP _DOES_ have the "ability" of a cluster alias, but that is not exactly what is expected in a VMS environment:&lt;BR /&gt;the relevant interfaces are defined to have the cluster alias name/address.&lt;BR /&gt;_ONE_ interface (the first to be able to do so) becomes the "cluster impersonator", and will handle _ALL_ communication directed at the cluster. Only upon failure (or shutdown) will the impersonation be released, and another interface will assume it.&lt;BR /&gt;And as long as there is ANY connection using it, it cannot be failed over.&lt;BR /&gt;&lt;BR /&gt;Using DNS, one way or another, the cluster might not even know it can also be addressed as a cluster via IP...&lt;BR /&gt;And DNS might know any number of different names for the cluster, or a subset of its nodes...&lt;BR /&gt;&lt;BR /&gt;hth.&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Tue, 08 Mar 2005 07:45:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499713#M67207</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-03-08T07:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499714#M67208</link>
      <description>Muthuvel,&lt;BR /&gt;Here we go... i think this should help you to get started :)&lt;BR /&gt;&lt;BR /&gt;Determine Cluster or Not&lt;BR /&gt;------------------------&lt;BR /&gt;$ if f$getsyi ("cluster_member") .eqs. "TRUE"&lt;BR /&gt;$ then  nodename = f$extract(0,5,f$getsyi("nodename"))&lt;BR /&gt;$ else&lt;BR /&gt;$    nodename = f$getsyi("nodename")&lt;BR /&gt;$ endif&lt;BR /&gt;&lt;BR /&gt;Cluster Alias&lt;BR /&gt;-------------&lt;BR /&gt;$ pipe tcpip show inter/full | search sys$input "Impersonator"&lt;BR /&gt;&lt;BR /&gt;Patches&lt;BR /&gt;--------&lt;BR /&gt;For those installed using VMSINSTAL&lt;BR /&gt;$ pipe type sys$update:vmsinstal.history | search sys$input "Feb-2005"&lt;BR /&gt;&lt;BR /&gt;For those installed using PCSI, use&lt;BR /&gt;$ pipe product show hist | search sys$input "Feb-2005"&lt;BR /&gt;&lt;BR /&gt;Put them all together and you should be able to get started :)&lt;BR /&gt;&lt;BR /&gt;All the best and let us know how it goes&lt;BR /&gt;&lt;BR /&gt;rgds&lt;BR /&gt;Mobeen&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Mar 2005 08:05:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499714#M67208</guid>
      <dc:creator>Mobeen_1</dc:creator>
      <dc:date>2005-03-08T08:05:54Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499715#M67209</link>
      <description>Hi Mobeen,&lt;BR /&gt;&lt;BR /&gt;   Happy with your results. Sorry that I am still not convinced. I tried with your suggestion.&lt;BR /&gt;&lt;BR /&gt;$ pipe ucx show inter/full | search sys$input Impersonator&lt;BR /&gt; Cluster Impersonator&lt;BR /&gt;    C_Addr: x.x.x.x   C_NETWRK: x.x.x.x   C_BRDCST: x.x.x.x&lt;BR /&gt;&lt;BR /&gt;    Here I could get the cluster_ip address(one of my exact requirements) but not the cluster alias. Now I have found one another way for this.&lt;BR /&gt;&lt;BR /&gt;I found two logicals generally in these systems which are SYS$CLUSTER_NODE and SYS_CLUSTER_NAME. Atleast one of these are available almost on all the systems in my network. So I have made use of these for finding it out. &lt;BR /&gt;&lt;BR /&gt;   I have one more way of finding the Cluster_ip which is as easy as running UCX SHOW HOST CLUSTER_ALIAS /out=a.txt and extracting the third line from it.&lt;BR /&gt;&lt;BR /&gt;   Just let me know the way I use for finding the cluster_alias is correct or not.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Muthuvel.B</description>
      <pubDate>Tue, 08 Mar 2005 08:24:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499715#M67209</guid>
      <dc:creator>Muthuvel.B</dc:creator>
      <dc:date>2005-03-08T08:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499716#M67210</link>
      <description>Muthu,&lt;BR /&gt;I am happy as long as it works for you :)&lt;BR /&gt;Can you post the output from the following command ....&lt;BR /&gt;&lt;BR /&gt;$UCX SHOW HOST CLUSTER_ALIAS&lt;BR /&gt;&lt;BR /&gt;(you can change your IP address to xxx.xxx.xxx.xxx)&lt;BR /&gt;:)&lt;BR /&gt;&lt;BR /&gt;rgds&lt;BR /&gt;Mobeen</description>
      <pubDate>Tue, 08 Mar 2005 08:29:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499716#M67210</guid>
      <dc:creator>Mobeen_1</dc:creator>
      <dc:date>2005-03-08T08:29:47Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499717#M67211</link>
      <description>Mobeen,&lt;BR /&gt;&lt;BR /&gt;  $ ucx show host 'Cluster_alias'&lt;BR /&gt;&lt;BR /&gt;     LOCAL database&lt;BR /&gt;&lt;BR /&gt;Host address    Host name&lt;BR /&gt;&lt;BR /&gt;x.x.x.x   xxxxxx, XXXXXX&lt;BR /&gt;$&lt;BR /&gt;   where Cluster_alias equates the cluster's real alias name.&lt;BR /&gt;&lt;BR /&gt;Muthuvel.B&lt;BR /&gt;  &lt;BR /&gt;Btw: Leaving rightaway. BRB later.&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Mar 2005 08:34:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499717#M67211</guid>
      <dc:creator>Muthuvel.B</dc:creator>
      <dc:date>2005-03-08T08:34:28Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499718#M67212</link>
      <description>&lt;BR /&gt;&amp;gt;&amp;gt; SYS$CLUSTER_NODE and SYS_CLUSTER_NAME. &lt;BR /&gt;&lt;BR /&gt;The first one is the DECNET clustername, not the IP cluster impersonation. &lt;BR /&gt;SYS_CLUSTER_NAME I don't think is commonly existing.&lt;BR /&gt;&lt;BR /&gt;To have different DECNET and IP cluster names I&lt;BR /&gt;think is not so uncommon: in my case, all nodes can be reached by the DECNET cluster address. But the IP cluster alias is only defined for nodes offering services (mail,ftp,web).&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Mar 2005 08:56:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499718#M67212</guid>
      <dc:creator>Joseph Huber_1</dc:creator>
      <dc:date>2005-03-08T08:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499719#M67213</link>
      <description>Muthuvel, Mobeen,&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;$ pipe ucx show inter/full | search sys$input Impersonator&lt;BR /&gt;Cluster Impersonator&lt;BR /&gt;C_Addr: x.x.x.x C_NETWRK: x.x.x.x C_BRDCST: x.x.x.x&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;Please note, that this will _ONLY_ return cluster info on the _ONE_ node that is at that moment the cluster impersonator.&lt;BR /&gt;On _NONE_ of the other nodes cluster info is returned!&lt;BR /&gt;&lt;BR /&gt;Joseph,&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;in my case, all nodes can be reached by the DECNET cluster address. But the IP cluster alias is only defined for nodes offering services&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;Even much stronger than that: the IP cluster alias is at any moment in time _ONLY_ offered by a _SINGLE_ node, and can _NOT_ be changed while there is _ANY_ connection active on it!!&lt;BR /&gt;&lt;BR /&gt;hth,&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Mar 2005 10:10:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499719#M67213</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-03-08T10:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499720#M67214</link>
      <description>note that the Failsafe IP feature in TCPIP Serv ices for VMS V5.4 and later sort of superceeds the cluster alias and the ifconfig command is what you use to determine what's going on with alias addresses.</description>
      <pubDate>Tue, 08 Mar 2005 10:29:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499720#M67214</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-03-08T10:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499721#M67215</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;   Yeah its true that the SYS_CLUSTER_NAME is not common on all nodes. By raising some questions, I got many new concepts. Thanks to all.&lt;BR /&gt;&lt;BR /&gt;   Now I have got another question. How do you configure a Cluster_alias in a VMS cluster environment? I think, I was not presented an option to configure it when I ran Cluster_config.com.&lt;BR /&gt;&lt;BR /&gt;Muthuvel.B</description>
      <pubDate>Tue, 08 Mar 2005 22:17:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499721#M67215</guid>
      <dc:creator>Muthuvel.B</dc:creator>
      <dc:date>2005-03-08T22:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499722#M67216</link>
      <description>Muthuvel,&lt;BR /&gt;The command for setting cluster alias in TCPIP is as follows&lt;BR /&gt;&lt;BR /&gt;$tcpip set interface/cluster=alias-name&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;Mobeen</description>
      <pubDate>Wed, 09 Mar 2005 00:38:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499722#M67216</guid>
      <dc:creator>Mobeen_1</dc:creator>
      <dc:date>2005-03-09T00:38:04Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499723#M67217</link>
      <description>&amp;lt; How do you configure a Cluster_alias in a VMS &amp;lt; cluster environment? I think, I was not &lt;PRESENTED an="" option="" to="" configure="" it="" when="" i="" ran=""&gt;&lt;/PRESENTED&gt;&lt;BR /&gt;The DECnet cluster alias IS asked in cluster_config when adding a node.&lt;BR /&gt;If You mean IP cluster alias: since it has nothing to do with VMS cluster, cluster_config is simply not aware of it (and any other TCPIP related items).</description>
      <pubDate>Wed, 09 Mar 2005 03:10:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499723#M67217</guid>
      <dc:creator>Joseph Huber_1</dc:creator>
      <dc:date>2005-03-09T03:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster Alias..</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499724#M67218</link>
      <description>Muthuvel,&lt;BR /&gt;&lt;BR /&gt;Ian's answer made me realise that I have a small correction to make to my own statements:&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;Even much stronger than that: the IP cluster alias is at any moment in time _ONLY_ offered by a _SINGLE_ node, and can _NOT_ be changed while there is _ANY_ connection active on it!!&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;It is even still stronger: it should not be "_ONLY_ offered by a _SINGLE_ node", but, "_ONLY_ offered by a _SINGLE_ _INTERFACE_" This becomes VERY relevant when having multiple interfaces!&lt;BR /&gt;The FailSafe IP feature (IP 5.4 and after) addresses some of that.&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Wed, 09 Mar 2005 03:33:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cluster-alias/m-p/3499724#M67218</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-03-09T03:33:02Z</dc:date>
    </item>
  </channel>
</rss>

