Re: Connection Manager - restrict connections

Tom wrote: I think to do what you are trying to do that you will need to use the password file. The second column has an alias to use in place of the HA_ALIAS. > On May 14, 11:47 am, Tom <tlow...@munis.com> wrote: >> On May 14, 4:57 am, theBP <th...@Usenet-News.Net> wrote: >> >> >> >> >> >>> Tom wrote: >>>> On May 13, 8:44 am, theBP <th...@Usenet-News.Net> wrote: >>>>> Tom wrote: >>>>>> On May 12, 3:05 pm, Tom <tlow...@munis.com> wrote: >>>>>>> On May 12, 2:11 pm, theBP <th...@Usenet-News.Net> wrote: >>>>>>>> Tom wrote: >>>>>>>>> Greetings all, >>>>>>>>> In a world where multiple DBSERVERALIAS values exist, is there a way >>>>>>>>> to restrict which ones the Connection Manager tries to establish >>>>>>>>> connections through? >>>>>>>>> As a brief example, If I have these values in the ONCONFIG file: >>>>>>>>> DBSERVERNAME aspbeL1 >>>>>>>>> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>>>>>>>>> And given this sqlhosts file: >>>>>>>>> aspbeL1 onipcshm asp5 aspbeL1 >>>>>>>>> aspbeL1_live onsoctcp asp5_be aspbeL1_live>>>>>>>>> hdr1P_be onsoctcp asp5_be hdr1P_be s=6 >>>>>>>>> odbc_asp5 onsoctcp asp5 odbc_asp5>>>>>>>>> NOTE: asp5 and asp5_be are two distinct IP's on two separate NIC's on >>>>>>>>> the same server. >>>>>>>>> The CM insists on trying to connect via the shared memory service >>>>>>>>> "aspbeL1", which it cannot because the CM is running on a separate >>>>>>>>> server. >>>>>>>>> What I want is for the CM to connect only to service aspbeL1_live. How >>>>>>>>> do I get the CM to ignore those other entries? It even tries to >>>>>>>>> connect to hdr1P_be even though the s=6 setting should (I believe) let >>>>>>>>> the CM know that only HDR-related traffic is allowed on this port. >>>>>>>>> Thanks, >>>>>>>>> Tom >>> Hi Tom, >>> Well, a few defects to be logged I feel :-/ >>> 1. dbserveralias=off is not present in 3.50.xC4 >>> 2. I would suggest that you consider using "group" syntax in your sqlhosts (note shared memory connection is not in the group): >>> aspbeL1 onipcshm asp5 aspbeL1 >>> aspbel group - - i=1>>> aspbeL1_live onsoctcp asp5_be aspbeL1_live g=aspbel >>> hdr1P_be onsoctcp asp5_be hdr1P_be g=aspbel,s=6 >>> odbc_asp5 onsoctcp asp5 odbc_asp5 g=aspbel >>> Really, the "group" should also include the actual HDR secondary, so that if you want to re-direct connections to the HDR secondary >>> you can. >>> 3. What INFORMIXSERVER do you start connection manager with? >>> I suggest that you use either the "group" aspbel (although this appears to have issues :-/ ) or aspbeL1_live. >>> 4. The is an error being generated when one of the Connection Manager tries to use : >>> hdr1P_be onsoctcp asp5_be hdr1P_be s=6 >>> 08:22:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be SQLCODE = (-25539,0,) >>> which I think is for your HDR secondary >>> > finderr 25539 >>> -25539 Invalid connection-type. >>> The connection-type is invalid for the database server. This message appears when >>> the database server is configured to address specific connection requests, for examplefor an >>> ER or HDR connection. >>> In order for me to (more easily) get a complete picture, can you fill in the blanks : >>> Primary : >>> ========= >>> DBSERVERNAME aspbeL1 >>> DBSERVERALIASES hdr1P_be,aspbeL1_live,odbc_asp5>>> Secondary : >>> =========== >>> DBSERVERNAME ??????>>> DBSERVERALIAS ?????? >>> sqlhosts >>> ======== >>> # Primary entries >>> aspbeL1 onipcshm asp5 aspbeL1 >>> aspbel group - - i=1>>> aspbeL1_live onsoctcp asp5_be aspbeL1_live g=aspbel >>> hdr1P_be onsoctcp asp5_be hdr1P_be g=aspbel,s=6 >>> odbc_asp5 onsoctcp asp5 odbc_asp5 g=aspbel >>> # Secondary entries >>> ?????????? >>> hdr1S_be onsoctcp asp6_be hdr1S_be g=aspbel >>> ?????????? >>> ?????????? >>> ?????????? >>> # Connection Manager SLA Entries >>> aspbeL1_live onsoctcp ??????? >>> etc. etc. >>> Connection Manager INFORMIXSERVER env vars >>> ========================================== >>> Connection Manager oncmsm_1 Config File : >>> ========================================= >>> NAME oncmsm_1 >>> SLA oltp_cm1=aspbeL1_live >>> SLA report_cm1=hdr1_live >>> ???????????? >>> LOGFILE (Hopefully separate to oncmsm_2) >>> Connection Manager oncmsm_2 Config File : >>> ========================================= >>> NAME oncmsm_2 >>> SLA ????????????? >>> SLA ????????????? >>> ???????????????? >>> LOGFILE (Hopefully separate to oncmsm_1) >>> If anything, we can at least get a load of issues logged :-/- Hide quoted text - >>> - Show quoted text - >> Here is my configuration: >> >> ASP5 is the primary server in an HDR pair. ASP6 is the secondary, or >> HDR server in the pair. >> >> Each server is connected to a private switch that also connects them >> to the application server, which is ASP4. ASP4 is not part of the >> MACH11 Cluster. Each server also connects to a routed switch, that is >> accessible throughout our network. the "_be" in the host name >> indicates "back end", which is the private switch connection. >> >> The goal is to have the CM use ONLY aspbeL1_live and hdr1_live for >> connections. Here is the desired connection usage: >> >> Private switch connections: >> >> aspbeL1_live: Primary. All CM managed connections go here. >> hdr1_live: Secondary. If aspbeL1_live dies - promote to >> active (normally HDR1 is read-only) >> >> hdr1P_be: For HDR server to server traffic only (hence the s=6 value) >> hdr1S_be: For HDR server to server traffic only (hence the s=6 value) >> >> Routed switch connections: >> >> odbc_asp5: To allow non-application server (ASP4) ODBC type >> connections >> munislive: To allow non-application server (ASP4) ODBC type >> connections >> >> Shared Memory connections: >> >> aspbeL1: For internal use only. >> hdr1: For internal use only. >> >> Here are the ASP5 configuration values: >> >> DBSERVERNAME: aspbeL1 >> DBSERVERALIASES: hdr1P_be, aspbeL1_live, odbc_asp5 >> >> sqlhosts file on ASP5: >> # ASP5 >> aspbeL1 onipcshm asp5 aspbeL1>> # aspbeL1_live onsoctcp asp5_be aspbeL1_live >> hdr1P_be onsoctcp asp5_be hdr1P_be s=6 >> odbc_asp5 onsoctcp asp5 odbc_asp5>> >> # ASP6 >> # hdr1 onipcshm asp6 hdr1 >> # hdr1_live onsoctcp asp6_be hdr1_live >> hdr1S_be onsoctcp asp6_be hdr1S_be s=6 >> munislive onsoctcp asp6 munislive>> >> # ASP4 Programs connect via this group via the connection manager >> g_mach group - -