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...@xxxxxxxxx> wrote:
On May 14, 4:57 am, theBP <th...@xxxxxxxxxxxxxxx> wrote:





Tom wrote:
On May 13, 8:44 am, theBP <th...@xxxxxxxxxxxxxxx> wrote:
Tom wrote:
On May 12, 3:05 pm, Tom <tlow...@xxxxxxxxx> wrote:
On May 12, 2:11 pm, theBP <th...@xxxxxxxxxxxxxxx> 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 - - e=hdr1_live
aspbeL1_live onsoctcp asp5_be aspbeL1_live
g=g_mach
hdr1_live onsoctcp asp6_be hdr1_live
g=g_mach

# Connection Manager - ASP4 Programs
oltp group -
- e=oltp_cm2
oltp_cm1 onsoctcp asp5_be cmport1 g=oltp
oltp_cm2 onsoctcp asp6_be cmport1 g=oltp

# Connection Manager - ODBC read-only programs
report group -
- e=report_cm2
report_cm1 onsoctcp asp5_be cmport2
g=report
report_cm2 onsoctcp asp6_be cmport2
g=report

CM Configuration file - ASP5 - oncmsm_1.cfg

NAME oncmsm_1
SLA oltp_cm1=aspbeL1_live
SLA report_cm1=hdr1_live
DEBUG 1
LOGFILE /usr/local/IDS/IBM_IDS/tmp/cmsm_1.log
FOC hdr1_live,10

##################################

Here are the ASP6 configuration values:

DBSERVERNAME: hdr1
DBSERVERALIASES: hdr1S_be, hdr1L1_live, munislive

sqlhosts file on ASP6:

# 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 -
- e=hdr1_live
aspbeL1_live onsoctcp asp5_be aspbeL1_live
g=g_mach
hdr1_live onsoctcp asp6_be hdr1_live
g=g_mach

# Connection Manager - ASP4 Programs
oltp group -
- e=oltp_cm2
oltp_cm1 onsoctcp asp5_be cmport1 g=oltp
oltp_cm2 onsoctcp asp6_be cmport1 g=oltp

# Connection Manager - ODBC read-only programs
report group -
- e=report_cm2
report_cm1 onsoctcp asp5_be cmport2
g=report
report_cm2 onsoctcp asp6_be cmport2
g=report

CM Configuration file - ASP6 - oncmsm_2.cfg

NAME oncmsm_2
SLA oltp_cm2=aspbeL1_live
SLA report_cm12=hdr1_live
DEBUG 1
LOGFILE /usr/local/IDS/IBM_IDS/tmp/cmsm_1.log
FOC hdr1_live,10

#################

Both /etc/services files have these entries:

#
## IDS Entries
#
munislive 1440/tcp # ODBC live DB on ASP6
hdr1P_be 9081/tcp # IBM IDS HDR Server-Server connection
aspbeL1_live 9082/tcp # IBM IDS aspbeL1 private network
connection
hdr1S_be 9083/tcp # IBM IDS aspbeL1 private network
connection
hdr1_live 9084/tcp # IBM IDS aspbeL1 private network
connection
cmport1 9085/tcp # Connection Manager oncmsm_1
cmport2 9086/tcp # Connection Manager oncmsm_2
cmport3 9087/tcp # Connection Manager oncmsm_3 (not
used yet)
odbc_asp5 9088/tcp # ODBC live DB
...

read more »- Hide quoted text -

- Show quoted text -

Here is a small example of my CM log. It seems to run through this
cycle continiously:

14:23:30 Arbitrator setting primary name = hdr1P_be
14:23:30 FOC[0] = hdr1_live
14:23:30 FOC timeout = 10
14:30:00 Arbitrator FOC string = hdr1_live,10
14:30:00 Arbitrator setting primary name = aspbeL1
14:30:00 FOC[0] = hdr1_live
14:30:00 FOC timeout = 10
14:30:00 create new thread 60397 for hdr1S_be
14:30:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:30:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:30:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:30:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:30:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:30:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:30:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:30:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:30:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:30:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:30:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:30:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:32:36 Arbitrator FOC string = hdr1_live,10
14:32:36 Arbitrator setting primary name = hdr1P_be
14:32:36 FOC[0] = hdr1_live
14:32:36 FOC timeout = 10
14:38:15 Arbitrator FOC string = hdr1_live,10
14:38:15 Arbitrator setting primary name = aspbeL1
14:38:15 FOC[0] = hdr1_live
14:38:15 FOC timeout = 10
14:38:15 create new thread 60654 for hdr1S_be
14:38:15 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:38:15 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:38:25 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:38:25 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:38:35 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:38:35 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:38:45 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:38:45 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:38:55 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:38:55 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:39:05 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:39:05 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:41:42 Arbitrator FOC string = hdr1_live,10
14:41:42 Arbitrator setting primary name = hdr1P_be
14:41:42 FOC[0] = hdr1_live
14:41:42 FOC timeout = 10
14:46:30 Arbitrator FOC string = hdr1_live,10
14:46:30 Arbitrator setting primary name = aspbeL1
14:46:30 FOC[0] = hdr1_live
14:46:30 FOC timeout = 10
14:46:30 create new thread 60911 for hdr1S_be
14:46:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:46:30 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:46:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:46:40 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:46:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:46:50 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:47:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:47:00 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:47:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:47:10 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)
14:47:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
14:47:20 CONNECT to sysmaster@hdr1S_be|onsoctcp|asp6_be|hdr1S_be
SQLCODE = (-25539,0,)


Tom

.

Relevant Pages

  • RE: Remote Connection Manager
    ... *I can ping the internal address of the server when connected. ... the SBS 2003 Remote Connection Manager is a client side VPN ...
    (microsoft.public.windows.server.sbs)
  • Re: Connection Manager - restrict connections
    ... DBSERVERNAME aspbeL1 ... the same server. ... I would suggest that you consider using "group" syntax in your sqlhosts (note shared memory connection is not in the group): ... What INFORMIXSERVER do you start connection manager with? ...
    (comp.databases.informix)
  • Re: RWW connect to computer at work issue
    ... from here for some reason (on the old server) and he setup a wildcard ... >> - Connect using connection manager (it shows that it connects, ... >> that the remote computer is on and connected to the Windows Small ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN questions
    ... When you ran the Remote Access Wizard, it had you type in the FQDN or IP ... you use when you manually create a VPN connection? ... Small Business Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Connection Manager - restrict connections
    ... to restrict which ones the Connection Manager tries to establish ... DBSERVERNAME aspbeL1 ... the same server. ... SQLCODE = ...
    (comp.databases.informix)