Required LDAP entries for High Availability Branch Servers (SLRS8).

  • Document ID:3855172
  • Creation Date:12-Sep-2006
  • Modified Date:16-Mar-2012

Environment

SUSE Linux Retail Solution 8
Heartbeat
Branchserver
LDAP

Situation

Before you can configure and deploy a high availability Branch Server pair, you must first create the necessary objects in the LDAP directory. Unfortunately, this information can not be found in the official documentation for Suse Linux Retail Solution 8. Without these entries the scriptposInitBranchserver.shdoesn't work correctly.

Resolution

The following examples demonstrate how to add network interface cards for the Branch Server, drbd, and heartbeat interfaces:

  1. Create an organizationalUnit object.
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base o=mycorp,c=us --add --organizationalUnit --ou boston

  2. Create the scLocation object.
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base ou=boston,o=mycorp,c=us --add --scLocation --cn branch\
    --ipNetworkNumber 192.168.1.0 --ipNetmaskNumber 255.255.255.0\
    --scDhcpRange 192.168.1.4,192.168.1.99\
    --scDhcpFixedRange 192.168.1.100,192.168.1.199\
    --scDefaultGw 192.168.1.1 --scDynamicIp TRUE\
    --scWorkstationBasename CR --scEnumerationMask 000

  3. Create an scServerContainer object.
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=branch,ou=boston,o=mycorp,c=us --add --scServerContainer --cn server

  4. In the new server container, create two Branch Server objects.
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scBranchServer --cn bs1

    posAdmin.pl --user\
    cn=admin,o=mycorp,c=us --password secret\
    --base cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scBranchServer --cn bs2

  5. Define the network interface cards for each Branch Server.

    Depending on network traffic and the desired performance, you can configure one to four network interface cards per Branch Server. The following examples demonstrate how to add network interface cards for the Branch Server, drbd, and heartbeat interfaces.

    Branch Server 1 Network Interface Card Configuration

    eth0 on BS1 for the public interface:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password novell\
    --base cn=bs1,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scNetworkcard --scDevice eth0\
    --ipHostNumber 151.155.173.111

    eth1 on BS1 for the Branch Server interface:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs1,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scNetworkcard --scDevice eth1\
    --ipHostNumber 192.168.1.1\
    --ipNetmaskNumber 255.255.255.0

    eth2 on BS1 for the drbd interface:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs1,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scNetworkcard --scDevice eth2\
    --ipHostNumber 192.168.2.1

    eth3 on BS1 for the heartbeat interface:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs1,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scNetworkcard --scDevice eth3\
    --ipHostNumber 192.168.3.1

    eth1:0 on BS1 for the Branch Server interface virtual IP:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs1,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scNetworkcard --scDevice eth1:0\
    --ipHostNumber 192.168.1.3

    Branch Server 2 Network Interface Card Configuration

    eth0 on BS2 for the public interface:
    posAdmin.pl --user cn=admin,o=a35,c=us --password secret\
    --base cn=bs2,cn=server,cn=branch,ou=provo,o=a35,c=us\
    --add --scNetworkcard --scDevice eth0\
    --ipHostNumber 151.155.173.112

    eth1 on BS2 for the Branch Server interface:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs2,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scNetworkcard --scDevice eth1\
    --ipHostNumber 192.168.1.2\
    --ipNetmaskNumber 255.255.255.0

    eth2 on BS2 for the drbd interface:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs2,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scNetworkcard --scDevice eth2\
    --ipHostNumber 192.168.2.2

    eth3 on BS2 for the Heartbeat interface:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs2,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scNetworkcard --scDevice eth3\
    --ipHostNumber 192.168.3.2

    eth1:0 on BS2 for the Branch Server interface virtual IP:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs2,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scNetworkcard --scDevice eth1:0\
    --ipHostNumber 192.168.1.3

  6. Add DHCP, DNS, and TFTP as HA services.

    The following commands demonstrate how to add DHCP, DNS, and TFTP as HA services in the example scenario.

    Branch Server 1 HA Services Configuration

    For DHCP on BS1 as the primary service:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs1,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scHAService --cn dhcp --ipHostNumber 192.168.1.3\
    --scDnsName dhcp --scServiceName dhcp\
    --scServiceStartScript dhcpd\
    --scServiceStatus TRUE --scPrimaryService TRUE

    For DNS on BS1 as the primary service:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs1,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scHAService --cn dns --ipHostNumber 192.168.1.3\
    --scDnsName dns --scServiceName dns\
    --scServiceStartScript named\
    --scServiceStatus TRUE --scPrimaryService TRUE

    For TFTP on BS1 as the primary service:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs1,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scHAService --cn tftp --ipHostNumber 192.168.1.3\
    --scDnsName tftp --scServiceName tftp\
    --scServiceStartScript atftpd\
    --scServiceStatus TRUE --scPrimaryService TRUE

    Branch Server 2 HA Services Configuration

    For DHCP on bs2 as the backup service:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs2,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scHAService --cn dhcp --ipHostNumber 192.168.1.3\
    --scDnsName dhcp --scServiceName dhcp\
    --scServiceStartScript dhcpd\
    --scServiceStatus TRUE --scPrimaryService FALSE

    For DNS on BS2 as the backup service:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs2,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scHAService --cn dns --ipHostNumber 192.168.1.3\
    --scDnsName dns --scServiceName dns\
    --scServiceStartScript named\
    --scServiceStatus TRUE --scPrimaryService FALSE

    For TFTP on BS2 as the backup service:
    posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret\
    --base cn=bs2,cn=server,cn=east,ou=boston,o=mycorp,c=us\
    --add --scHAService --cn tftp --ipHostNumber 192.168.1.3\
    --scDnsName tftp --scServiceName tftp\
    --scServiceStartScript atftpd\
    --scServiceStatus TRUE --scPrimaryService FALSE