Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
rvb set up an HDR pair and asked whether Informix CSM encryption could protect replication; it failed with HDR cannot connect over a CSM connection on 9.40. Madison Pruet said CSM is half duplex and HDR full duplex, advised separating the HDR port using s=6, but later confirmed HDR cannot use encryption. s=6 got HDR working only without CSM.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
I set up a HDR pair of two servers.
The replication is in clear text. Is it possible to use encryption with the
Informix CSM methods for this HA pair.
My first test failed with :
12:25:34 HDR can not connect to <paired server> over a CSM connection
↪ replying to rvb
Madison Pruet — — source: Usenet: comp.databases.informix
CSM is half duplexed. HDR is fully duplexed.
You will need to seperate the port used by HDR from the normal client
activity.
See the release notes for the usage of option s=6 for details on how to do
this.
"rvb" <rvbon@gmx.de> wrote in message
news:6e9a0040.0407050233.3643d4a9@posting.google.com...
> I set up a HDR pair of two servers.
>
> The replication is in clear text. Is it possible to use encryption with
the
> Informix CSM methods for this HA pair.
>
> My first test failed with :
>
> 12:25:34 HDR can not connect to <paired server> over a CSM connection
Madison,
I isolated HDR communication with option s=6 as follows:
lvv_prod_sec onsoctcp <servername> lvv_prod_sec s=6
and HDR works. But using CSM like
lvv_prod_sec onsoctcp <servername> lvv_prod_sec s=6 csm=(ENCCSM)
still gives
HDR can not connect to lvv_prod_sec over a CSM connection
Am I still missing something ??
BTW I am using 9.40 HC3
"Madison Pruet" <mpruet@comcast.net> wrote in message news:<B8fGc.26413$a24.21070@attbi_s03>...
> CSM is half duplexed. HDR is fully duplexed.
>
> You will need to seperate the port used by HDR from the normal client
> activity.
>
> See the release notes for the usage of option s=6 for details on how to do
> this.
>
>
> "rvb" <rvbon@gmx.de> wrote in message
> news:6e9a0040.0407050233.3643d4a9@posting.google.com...
> > I set up a HDR pair of two servers.
> >
> > The replication is in clear text. Is it possible to use encryption with
> the
> > Informix CSM methods for this HA pair.
> >
> > My first test failed with :
> >
> > 12:25:34 HDR can not connect to <paired server> over a CSM connection
↪ replying to rvb
Madison Pruet — — source: Usenet: comp.databases.informix
HDR is using full duplex protocol. The CSM is using half duplex. That
means that HDR can not be using encryption.
"rvb" <rvbon@gmx.de> wrote in message
news:6e9a0040.0407060058.a949384@posting.google.com...
> Madison,
>
> I isolated HDR communication with option s=6 as follows:
>
> lvv_prod_sec onsoctcp <servername> lvv_prod_sec s=6
>
> and HDR works. But using CSM like
>
> lvv_prod_sec onsoctcp <servername> lvv_prod_sec s=6 csm=(ENCCSM)
>
> still gives
>
> HDR can not connect to lvv_prod_sec over a CSM connection
>
> Am I still missing something ??
> BTW I am using 9.40 HC3
>
>
>
> "Madison Pruet" <mpruet@comcast.net> wrote in message
news:<B8fGc.26413$a24.21070@attbi_s03>...
> > CSM is half duplexed. HDR is fully duplexed.
> >
> > You will need to seperate the port used by HDR from the normal client
> > activity.
> >
> > See the release notes for the usage of option s=6 for details on how to
do
> > this.
> >
> >
> > "rvb" <rvbon@gmx.de> wrote in message
> > news:6e9a0040.0407050233.3643d4a9@posting.google.com...
> > > I set up a HDR pair of two servers.
> > >
> > > The replication is in clear text. Is it possible to use encryption
with
> > the
> > > Informix CSM methods for this HA pair.
> > >
> > > My first test failed with :
> > >
> > > 12:25:34 HDR can not connect to <paired server> over a CSMconnection
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.