Connecntion Manager x DBSERVERALIASES
Posted in 2010
Topics: High Availability & Replication, Networking & sqlhosts Configuration, Clustering, Grid & MACH11
Hi, csdk 3.50 xC7 ifx 11.50 xF7 - Linux. I got a issue here to configure the Connection Manager over a HDR cluster and theirs DBSERVERALIASES. On the configuration of the two instances, exists some aliases what not should be considered to client connectivity. I already notice that configurations of the listeners network what the client isn't capable to use, they ignore and not try o redirect the client to them (differ networks/netmask). But I want to get more control over the serveralias/services what a SLA will redirect. For example, If I configure a serveralias/service specific for ER , what work on the same network of the clients, but is a different port, I don have how avoid the CM to redirect a connection to this service/port. If for some reason later I want to do some maintenance on this service and put down this listener I will kill users sessions... I don't found anything on the manuals. I already try force the servername on the SLA configuration, don't work... the CM detect the others listeners and redirect to them. I try create a specific sqlhosts for the CM, without the serveralias/services what I don't want they redirect... this is worst, the CM don't start this way, they need to "see" all serveralias.... I don't want to set the s=6 for this situation because I already have a lot of problems with this parameters (the $INFORMIXDIR/etc/hosts.equiv appear not work well). And this is not the unique situation, I have listeners/port specific for admin connectivity what not should be considered to cluster/SLAs redirects. So, there is some way to do this what I missing here?
Hello Cesar. Someone else already mentioned this. There is (or should be) a new option that tells the CM to use only the ALIAS listed in the local (from the CM point of view) SQLHOSTS. This should be included in *FC8 when available. I was involved (from a customer point of view) in this issue, but I didn't have the opportunity to test it. If you have any issue with it I'd like to know... Regards. On Mon, Oct 18, 2010 at 12:56 PM, Cesar Inacio Martins < cesar_inacio_martins@yahoo.com.br> wrote: > Hi, > > csdk 3.50 xC7 > ifx 11.50 xF7 - Linux. > > I got a issue here to configure the Connection Manager over a HDR cluster > and > theirs DBSERVERALIASES. > > On the configuration of the two instances, exists some aliases what not > should > be considered to client connectivity. > > I already notice that configurations of the listeners network what the > client > isn't capable to use, they ignore and not try o redirect the client to them > (differ networks/netmask). > > But I want to get more control over the serveralias/services what a SLA > will > redirect. > For example, If I configure a serveralias/service specific for ER , what > work > on the same network of the clients, but is a different port, I don have how > avoid the CM to redirect a connection to this service/port. > If for some reason later I want to do some maintenance on this service and > put > down this listener I will kill users sessions... > > I don't found anything on the manuals. > I already try force the servername on the SLA configuration, don't work... > the > CM detect the others listeners and redirect to them. > > I try create a specific sqlhosts for the CM, without the > serveralias/services > what I don't want they redirect... this is worst, the CM don't start this > way, > they need to "see" all serveralias.... > > I don't want to set the s=6 for this situation because I already have a lot > of > problems with this parameters (the $INFORMIXDIR/etc/hosts.equiv appear not > work well). > And this is not the unique situation, I have listeners/port specific for > admin > connectivity what not should be considered to cluster/SLAs redirects. > > So, there is some way to do this what I missing here? > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --001636c5b24495d7dd0492e3b10a
Hi Fernando, Thanks for your answer. If you see the messages on the CDI there is a answer from Jonny what they talk about the new parameter: SQLHOSTS=LOCAL|REMOTE|LOCAL+REMOTE Probably this is the same solution what you talk about. I tested this parameter on xC7 and appear no have effect. And yes, I have this issue in two clients with mach active.. --- Em seg, 18/10/10, Fernando Nunes <domusonline@gmail.com> escreveu: De: Fernando Nunes <domusonline@gmail.com> Assunto: Re: Connecntion Manager x DBSERVERALIASES [21727] Para: ids@iiug.org Data: Segunda-feira, 18 de Outubro de 2010, 10:55 Hello Cesar. Someone else already mentioned this. There is (or should be) a new option that tells the CM to use only the ALIAS listed in the local (from the CM point of view) SQLHOSTS. This should be included in *FC8 when available. I was involved (from a customer point of view) in this issue, but I didn't have the opportunity to test it. If you have any issue with it I'd like to know... Regards. On Mon, Oct 18, 2010 at 12:56 PM, Cesar Inacio Martins < cesar_inacio_martins@yahoo.com.br> wrote: > Hi, > > csdk 3.50 xC7 > ifx 11.50 xF7 - Linux. > > I got a issue here to configure the Connection Manager over a HDR cluster > and > theirs DBSERVERALIASES. > > On the configuration of the two instances, exists some aliases what not > should > be considered to client connectivity. > > I already notice that configurations of the listeners network what the > client > isn't capable to use, they ignore and not try o redirect the client to them > (differ networks/netmask). > > But I want to get more control over the serveralias/services what a SLA > will > redirect. > For example, If I configure a serveralias/service specific for ER , what > work > on the same network of the clients, but is a different port, I don have how > avoid the CM to redirect a connection to this service/port. > If for some reason later I want to do some maintenance on this service and > put > down this listener I will kill users sessions... > > I don't found anything on the manuals. > I already try force the servername on the SLA configuration, don't work... > the > CM detect the others listeners and redirect to them. > > I try create a specific sqlhosts for the CM, without the > serveralias/services > what I don't want they redirect... this is worst, the CM don't start this > way, > they need to "see" all serveralias.... > > I don't want to set the s=6 for this situation because I already have a lot > of > problems with this parameters (the $INFORMIXDIR/etc/hosts.equiv appear not > work well). > And this is not the unique situation, I have listeners/port specific for > admin > connectivity what not should be considered to cluster/SLAs redirects. > > So, there is some way to do this what I missing here? > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --001636c5b24495d7dd0492e3b10a ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.