4/2/2011

1

Sybase Interoperability in a Virtualized World

Jeffrey WongPrincipal ConsultantAnton Ventures LLC

Presentation Topics

l What this presentation is not

l These techniques might be useful for

l Provisioning Items

l Suggested Implementation Paradigm

l stunnel 4.x configuration steps

l stunnel.pem generation

4/2/2011

2

Presentation Topics (continued)

l stunnel.conf excerpt (server – Win 7 Pro)

l stunnel.conf excerpt (client – guest VM)

l stunnel service installation programs

l Suggested Implementation Paradigm

l So when the rubber met the road?

l Operating Systems Used

Presentation Topics (continued)

l Vendor Products Used

l Implementation Notes

l Demonstration

l Questions and Answers

l References

l Thank You

4/2/2011

3

What this presentation is not

l Sybase and ...

− A “how to” on VMWare vSphere or ESX

− VirtualBox Tips and Tricks

− Solaris LDOMs, Containers, Zones

− AIX Dynamic LPARS

− Xen Paravirtualization, Kernel Mode Linux

− Virtual PC

− Etc ...

These techniques might be useful for

l “Crash and burn” without the pain …

l Technical “tour de force” …

l (Almost) Instant On …

l RAD for a proposed computing infrastructure …

l Enforcing vendor licensing requirements …

l Circumventing initial equipment unavailability …

l Etc ...

4/2/2011

4

Provisioning Items

l VMware Workstation (preferred), VMware Server, or VMware Player

l Multicore x64 laptop with 4 Gb memory minimum (preferred is 8 Gb memory)

l Windows 7 Professional (so you can use Windows XP virtual mode VMs)

l Stunnel V4.x software (server configuration on Win 7 Pro, client configuration on guest VMs)

Provisioning Items (continued)

l Sybase client/server software (licensed on Win 7 Pro, non-licensed/developer on guest VMs)

l Other vendor client/server software (licensed on Win 7 Pro, non-licensed/developer on guest VMs)

l (Optional) VMware VIX VM automation software

4/2/2011

5

Suggested Implementation Paradigm

l Get the guest VM installed and operational

l Install the licensed client/server software on the Win 7 Pro host

l Ensure the installed software basically works

l Install the stunnel 4.x software on the Win 7 Pro host. Configure host server ports, such that localhost:port(s) redirect to respective VMware NAT DHCP IP address and port(s)

Suggested Implementation Paradigm (continued)

l Install the non-licensed/developer client/server software on the guest VM

l Ensure the installed software basically works

l Install the stunnel 4.x software on the guest VM. Configure host server ports, such that VMware NAT DHCP IP address and port(s) redirect to respective localhost:port(s)

4/2/2011

6

Suggested Implementation Paradigm (continued)

l (Optionally) Unpack and install the VMware Virtual Network Editor software on the Win 7 Pro host (later VMware Player versions)

l Log in to the guest VM and configure it to use a static IP address instead of the DHCP provided one (same subnet)

− Static address range is usually from x.x.x.3 to x.x.x.127

Suggested Implementation Paradigm (continued)

l Run the VMware Virtual Network Editor software from the Win 7 Pro host (NAT section)

− Port redirect guest VM server port(s) to the respective NAT IP address and port(s)

l Start up stunnel 4.x on the Win 7 Pro host (server configuration)

l Start up stunnel 4.x on the guest VM (client configuration)

4/2/2011

7

Suggested Implementation Paradigm (continued)

l Test Win 7 Pro host server software connectivity by logging on to the guest VM and running the appropriate client program

l Test guest VM server software connectivity by running the appropriate client program in the Win 7 Pro host environment

stunnel 4.x configuration steps

l Generate the stunnel.pem file for the stunnel server

− Use a Linux VM that has stunnel already installed for this

l Generate the stunnel.pem file for the stunnel client

− Use a Linux VM that has stunnel already installed for this

4/2/2011

8

stunnel 4.x configuration steps (continued)

l Edit the stunnel.conf file for the stunnel server

l Edit the stunnel.conf file for the stunnel client

l Install the stunnel server service and start it

l Install the stunnel client service and start it

l Test the stunnel server service by accessing it from the stunnel client VM or host

stunnel.pem generation

l Diffie – Hellman public/private key generation not used (not needed)

l OpenSSL stunnel.pem generation command:

− openssl req -new -x509 -days 365 -nodes -config stunnel.cnf -out stunnel.pem -keyout stunnel.pem

l OpenSSL stunnel.pem certificate identification command:

− openssl x509 -subject -dates -fingerprint -in stunnel.pem

4/2/2011

9

stunnel.conf excerpt (server – Win 7 Pro)

l Here are the recommended entries for this file:cert = stunnel.pem

socket = l:TCP_NODELAY = 1

socket = r:TCP_NODELAY = 1

[SAMPLE_RS]

accept = 192.168.52.1:31752

connect = 11752

[IQDEMO]

accept = 192.168.52.1:22638

connect = 2638

stunnel.conf excerpt (client – guest VM)

l Here are the recommended entries for this file:cert = stunnel.pem

socket = l:TCP_NODELAY = 1

socket = r:TCP_NODELAY = 1

client = yes

[SAMPLE_RS]

accept = 11752

connect = 192.168.52.1:31752

4/2/2011

10

stunnel.conf excerpt (client – guest VM -continued)

[IQDEMO]

accept = 2638

connect = 192.168.52.1:22638

stunnel service installation programs

l Ubuntu/Xubuntu/Debian Linux

− Example: cd /etc/init.d; update-rc.d sybase defaults

l RHEL/CentOS/Oracle/Fedora Linux

− Example: cd /etc/init.d; chkconfig - - add sybase; chkconfig - - level 345 sybase on

l Windows XP/Vista/7

− Packaged with stunnel binary distribution

4/2/2011

11

So when the rubber met the road?

l It turned out that the original plan to only host non-licensed/developer software was flawed (no surprises at this outcome, right? :-) …), for the following reasons:

− Replication Agent software requires that it be installed in the same O/S environment as that for the targeted RDBMS

− One of the “requirements” was to test ERSSD routing from a guest VM (hmm ...)

So when the rubber met the road? (continued)

l Fortunately, though, these were the only exceptions. So, we can still progress (but after I wash the taste of crow first from my mouth, OK? :-) ...)

4/2/2011

12

Operating Systems Used

l Windows 7 Professional (AV-Laptop host)

l Xubuntu 10.04 x86 LTS (xubuntu guest VM)

l Centos 5.5 x86 (bagvapp guest VM)

l Windows XP SP3 x86 (WXPM-AseOra guest VM)

l Oracle Linux x86 (oracle_on_vmware guest VM)

Operating Systems Used (continued)

l Xubuntu 6.06 x86 (xubuntu_oracle guest VM)

l Centos 5.5 x64 (centos guest VM)

4/2/2011

13

Vendor Products Used

l AV-Laptop

− Replication Server 15.6 x64

− Sybase IQ 15.2 x64

− Sybase Control Center 3.1.1 x86

− ECO 15.5 ESD #1 x64

l xubuntu

− ASE 15.5 ESD #2 x86

Vendor Products Used (continued)

l bagvapp

− ASE 15.5 ESD #2 DE x86

l WXPM-AseOra

− ASE 15.5 ESD #2 DE x86

− Oracle 10.2g XE x86

− RAO 15.6 x86

− DCO 15.0 x86 (part of ECDA 15.0)

4/2/2011

14

Vendor Products Used (continued)

l oracle_on_vmware

− Oracle 10.2g XE x86

l xubuntu_oracle

− Oracle 10.2g XE x86

− RAO 15.6 x86

l centos

− ASE 15.5 ESD #2 DE x64

− Replication Server 15.6 x64

Implementation Notes

l AV-Laptop

− Could not install ASE 15.5 ESD #2 x86 DE or x64 DE on system

− Suspect change in Microsoft package installation (Vista origin) is the root cause

l bagvapp

− Turn off firewall and SELinux (expediency measure only)

4/2/2011

15

Implementation Notes (continued)

l oracle_on_vmware

− Oracle charges for installation changes to this VM

− So this Oracle instance is a Replication Server DSI target only

l xubuntu_oracle

− No stunnel 4.x Debian package available, so had to compile it from source code

Implementation Notes (continued)

l centos

− Turn off firewall and SELinux (expediency measure only)

− Cannot use routes with Replication Server and ERSSD

l Transaction log becomes corrupt on ungraceful powerdown

l Supposedly fixed by upgrading the ASA11 installation to a build later than 2272

4/2/2011

16

Implementation Notes (continued)

l centos (continued)

l ERSSD has to be rebuilt from scratch and previous Replication Server changes backed out

l Will apply build 2569 in the near future to test out fix

Demonstration

l Time permitting, the following subsystems will be covered:

− Bi-directional replication between XUBUNTU and BAGVAPP Sybase ASE VMs

− Uni-directional replication between the XUBUNTU, BAGVAPP Sybase ASE VMs and the IQDEMO Sybase IQ server

− Sybase Control Center 3.1.1 availability visualization of the above two subsystems

4/2/2011

17

Demonstration (continued)

− Uni-directional and DDL replication between the WXPM-AseOra VM Oracle instance and the ORACLE_ON_VMWARE VM Oracle instance (ECO)

− Bi-directional replication between the WXPM-AseOra VM Oracle instance (DCO) and the xubuntu_oracle VM Oracle instance (ECO)

− ERSSD transaction log corruption due to older ASA 11 software used in Rep Server 15.6 (when routes are created :-( ...)

Questions and Answers

l I will try to answer as many questions as possible today, time permitting

l However, if there is overflow, then:

− Please feel free to email me about the contents of this presentation, or on other Sybase technical matters. I will try to help ...

− My email address is wongjtf@gmail.com

4/2/2011

18

References

l The Complete Sybase ASE Quick Reference Guide (Book)

l The Complete Sybase Replication Server Quick Reference Guide (Book)

l Sybase 15 Replication Server Administration (Book)

l The Sybase IQ Survival Guide (Book)

l SQL Anywhere Studio 9 Developers Guide

References (continued)

l Oracle on VMware (Book)

l www.stunnel.org (Website)

l Best Practices for Oracle Data Replication Using Sybase Replication Server (White Paper – Sybase)

l Sybase ASE Query Optimization (White Paper -Embarcadero)

4/2/2011

19

References (continued)

l Managing Workloads with ASE: Techniques for OLTP Scaling and Performance Management with Large SMP and Shared Disk Clusters (White Paper – Sybase)

l www.isug.com

l Google ...

Thank You

l “May you live in interesting times”, goes the old (so-called) Chinese curse. OK, but at least it's not boring :-) ...