Re: Connecntion Manager x DBSERVERALIASES
Just a correction, The CM isn't to smart like I said. They appear be capable to identify listeners of localhost and not try do redirect client connection to them . But about not redirect to services / network what the client ins't capable to use, isn't true. I execute a new test here, where I have a serveralias/service specific to mach (HA_ALIAS), what is specific NIF connected with a "cross cable" between the machines, this network is specific for them and the CM try to redirect the clients connectivity trough this serveralias/service! Just for test I test the HA_ALIAS with s=6 and they still redirect the connections for this serveralias. --- Em seg, 18/10/10, Cesar Inacio Martins <cesar_inacio_martins@yahoo.com.br> escreveu: De: Cesar Inacio Martins <cesar_inacio_martins@yahoo.com.br> Assunto: Connecntion Manager x DBSERVERALIASES Para: "informix-list cdi" <informix-list@iiug.org>, "informix-iiug" <ids@iiug.org> Data: Segunda-feira, 18 de Outubro de 2010, 9:55 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? -----Anexo incorporado----- _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list
On 18/10/2010 13:09, Cesar Inacio Martins wrote: > Just a correction, > The CM isn't to smart like I said. > They appear be capable to identify listeners of localhost and not try do > redirect client connection to them . > But about not redirect to services / network what the client ins't > capable to use, isn't true. > I execute a new test here, where I have a serveralias/service specific > to mach (HA_ALIAS), what is specific NIF connected with a "cross cable" > between the machines, this network is specific for them and the CM try > to redirect the clients connectivity trough this serveralias/service! > Just for test I test the HA_ALIAS with s=6 and they still redirect the > connections for this serveralias. > > > > --- Em *seg, 18/10/10, Cesar Inacio Martins > /<cesar_inacio_martins@yahoo.com.br>/* escreveu: > > > De: Cesar Inacio Martins <cesar_inacio_martins@yahoo.com.br> > Assunto: Connecntion Manager x DBSERVERALIASES > Para: "informix-list cdi" <informix-list@iiug.org>, "informix-iiug" > <ids@iiug.org> > Data: Segunda-feira, 18 de Outubro de 2010, 9:55 > > 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? > > > > > -----Anexo incorporado----- > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org </mc/compose?to=Informix-list@iiug.org> > http://www.iiug.org/mailman/listinfo/informix-list > > Hi ... 1. Connection by default will "route clients to any available DBSERVERALIAS / DBSERVERALIASES with the equivalent protocol" by querying the server. 2. IC69128: CONNECTION MANAGER NEEDS THE ABILITY TO DISTRIBUTE TO A SPECIFIC SERVER (OR SET OF SERVERS) OF THE SAME PROTOCOL A new option in CM has been added (not sure exact version ... SQLHOSTS=LOCAL|REMOTE|LOCAL+REMOTE when SQLHOSTS=LOCAL only servers in the CM sqlhosts will be used for connections from that CM.
Thank you Jonny! I test this parameter on xC7 and don't work.. let's wait for xC8 .. Regards Cesar --- Em seg, 18/10/10, JonnyTDI@Usenet-News.net <JonnyTDI@Usenet-News.net> escreveu: De: JonnyTDI@Usenet-News.net <JonnyTDI@Usenet-News.net> Assunto: Re: Connecntion Manager x DBSERVERALIASES Para: informix-list@iiug.org Data: Segunda-feira, 18 de Outubro de 2010, 10:32 On 18/10/2010 13:09, Cesar Inacio Martins wrote: > Just a correction, > The CM isn't to smart like I said. > They appear be capable to identify listeners of localhost and not try do > redirect client connection to them . > But about not redirect to services / network what the client ins't > capable to use, isn't true. > I execute a new test here, where I have a serveralias/service specific > to mach (HA_ALIAS), what is specific NIF connected with a "cross cable" > between the machines, this network is specific for them and the CM try > to redirect the clients connectivity trough this serveralias/service! > Just for test I test the HA_ALIAS with s=6 and they still redirect the > connections for this serveralias. > > > > --- Em *seg, 18/10/10, Cesar Inacio Martins > /<cesar_inacio_martins@yahoo.com.br>/* escreveu: > > > De: Cesar Inacio Martins <cesar_inacio_martins@yahoo.com.br> > Assunto: Connecntion Manager x DBSERVERALIASES > Para: "informix-list cdi" <informix-list@iiug.org>, "informix-iiug" > <ids@iiug.org> > Data: Segunda-feira, 18 de Outubro de 2010, 9:55 > > 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? > > > > > -----Anexo incorporado----- > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org </mc/compose?to=Informix-list@iiug.org> > http://www.iiug.org/mailman/listinfo/informix-list > > Hi ... 1. Connection by default will "route clients to any available DBSERVERALIAS / DBSERVERALIASES with the equivalent protocol" by querying the server. 2. IC69128: CONNECTION MANAGER NEEDS THE ABILITY TO DISTRIBUTE TO A SPECIFIC SERVER (OR SET OF SERVERS) OF THE SAME PROTOCOL A new option in CM has been added (not sure exact version ... SQLHOSTS=LOCAL|REMOTE|LOCAL+REMOTE when SQLHOSTS=LOCAL only servers in the CM sqlhosts will be used for connections from that CM. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list