1. Os2. Define /.profiles and TCPIP (and edit / etc / hosts, plus /.rhosts file) 3. Defining TTY core jumpers (1) Terminal lines are connected to S1 ports of their respective host terminals (2) The two main unit S3 interconnections (S3 ports are standard core jump) (3) After the OS is installed, the two hosts should have been The respective S1 ports are defined, and the output is available in LSDEV-CC TTY: TTY0 Available 01-S1-00-00 Asynchronous Termind (which shows S1 means that this TTY is connected to S1 port) (4) Presented the core jump and S3 port Smit-> TTY-> Add A TTY-> RS232-> SA2 Available 01-S3 Standard I / O Serial Port-> Definition Port Number = 0 (5) After the S3 core jump is defined on the two hosts, use Stty Confirming whether the two core jumps can communicate normally> Enter the command stty Enter the command stty> / dev / tty1 on the B machine After the machine outputs the same information> Enter the command stty Enter the command stty> / dev / tty1 on the machine, enter the same information in the B-machine after entering the bus . Do RAID (only on the host) (1) Define all physical disc attributes smit dev-> ssa raid arrays-> change / show use of an SSA Physical Disk-> SSA0-> Select Physical Disk -> Define Properties (Array Candidate Disk / Hot Spare Disk / AIX System Disk (2) Take RAID SMIT Dev-> SSA RAID ARRAYS-> Add An SSA RAID ARRAY-> SSA0-> RAID5-> Definition MEMBER Disk and Enable Hot SPARE (3) View RAID State Smit Dev-> SSA RAID Arrays-> List Status of All Defined SSA RAID ARRAYS5. Establish a volume group and make the two machines to share the resource * LSDEV-CC PDisk View Physical Dry * LSDEV-CC Disk View Logic * LSPV View * LSVG View all volume group * lsvg -o View activity volume group (1) RAID after completion With LSDEV-CC Disk to see the logic disk on both machines, if it is inconsistent, use rmdev -dl hdisk * (* <> 0) to remove all logical discs outside HDisk0, and then use the CFGMGR to confirm the device, then the two machine will correctly identify OS. Put HDisk0 and RAID logic disk hdisk *, in addition, use the command LSPV to output the information of the logical disk on both two, where the HDisk0 volume group is named rootvg, and the HDisk * volume group name is None, if hdisk * has the old old The volume group name used by the system can be used to activate the volume group after activating the volume group and then enter the SMIT VG-> Remove A Volumn Group and then CFGMGR can be normal.
(2) SMIT VG-> Add A Volumn Group on the host, define all parameters as follows:> Volume Group name [raidgroup1] # Volume group name> Physical partition size in megabytes [32] # This volume group Physical partition size> Physical Volume Names [HDisk1] # This volume group physical volume name> Activate volume group automaticly [no] #]]]] 组 将 组 组 组 组 激 组]]]]]]]]]]]]]]]]]]] The system does not automatically activate the volume group after startup and is activated and used by HA. (3) After the completion, the output of LSDEV-CC PDISK and LSDEV-CC Disk is still not changed, and the HDisk * in the LSPV output has been put on the newly defined volume group name, and then LSVG and LSVG are used. -o two commands, the former displays all VG in the system, the latter shows all activated VG in the system, the same output is the same (because all volume group names are activated), but now use varyoffvg raidgroup1 commands Due to the Raidgroup1 volume group, the LSVG is different from the output of LSVG -O. At this time, the SMIT VG-> Import A Volume Group is on the slave and determines the following parameters, the Varyoffvg volume group on the host RAIDGROUP1 is now being used by Varyonvg, which is expressed in the LSVG output. In addition to rootvg, there are HDisk1 volume group names in Raidgroup1 and LSPVs, becomes raidgroup1> Volume Group name [raidgroup1]> Physical Volume Name [hdisk1] 6. Do HA (1) on the master-slave patch: bos.data, bos.adt.syscalls, bos.net.tcp.server, bos.adt.libm, sysmgt.Websm, X11.dt.tooltalk, x11.dt .lib, x11.base.rte, x11.vsm.rte (2) In the master-slave HA software (including Haview's subset) (3) Define a cluster topology on the host> Configure Cluster Smit Hacmp-> Cluster Configuration -> cluster topology-> configure cluster-> add a cluster definition-> determining cluster ID and cluster name> configuration node smit hacmp-> cluster configuration-> cluster topology-> configure nodes-> add a cluster nodes-> OK twice / etc / hosts defined in the two Node names> Matching Smit Hacmp-> Cluster Configuration-> Cluster Topology-> configure adapters-> During the host, the following 8 Adapter is defined, and then restart the two machines: Restart the machine Before you want to edit the / etc / hosts file, pay attention to the name of the address to be consistent with the Lable name sensing.
Adapter ip lable syb01_ip h701_boot h701_stdby h701_tty Network type ehter ether ether rs232Network name ehternet ehternet ehternet rs232netNetwork attribute public public public serialAdapter function service boot standby serviceAdapter identifier 162.105.161.12 162.105.161.13 168.100.100.4 / dev / tty1Adapter hardware address 000629acaaaaNode name node_h701 node_h701 node_h701 node_h701 Adapter ip lable syb02_ip h702_boot h702_stdby h702_tty Network type ehter ether ether rs232Network name ehternet ehternet ehternet rs232netNetwork attribute public public public serialAdapter function service boot standby serviceAdapter identifier 162.105.161.14 162.105.161.15 168.100.100.5 / dev / tty1Ada pter hardware address 000629acccccNode name node_h702 node_h702 node_h702 node_h702 (4) to synchronize the cluster resource smit hacmp-> cluster configuration-> cluster topology-> synchronize cluster topology error was encountered:. connect to remote host refused because /.rhost file after There is a space to ensure that there is only one characters in this file to be resolved. (5) Check Cluster Resources Smit Hacmp-> Cluster Configuration-> Cluster Verification-> Verify Cluster7.
Sybase (1) SMIT VG-> Set Characteristics of a Volume Group-> Change a Volume Group-> raidgroup1-> Change Activate Volumn Group AutomatiTiVate AT System Restart for NO-> RAIDGROUP2 for the same modification (the main slave is modified) 2) Varyoffvg hdisk * on the host Varyonvg HDisk * (3) Sybase logic volume on the host SMIT-> System Storage Management-> Logical Volume Manager-> Logical Volume -> Add Alogical Volume-> Determine Volume Group Name Rootvg-> Determine the following parameters> Logical Volume Name [lv_sybase]> volume group name [rootvg]> Number of logical partitions [40]> physical volume names [hdisk0] (4) Make the logical volume on the slave system smit-> system storage management-> file systems-> add / change / show / delete file systems-> journaled file systems-> add a journaled file system on a previously defined logical volume-> add a standard journaled file system -> Determine the following parameters> Logical Volume Name [lv_sybase]> Mount Point [/ Sybase]> Mount Automatically At System RESTART [YES] (5) On the Mount file system SMIT-> SY Stem Storage Management-> File Systems-> Mount A file system-> It is true> file system name [/ dev / lv_sybase]> Directory over which to mount [/ sybase] (6) Construction users Sybase on the slave, Home Directory is [/ sybase] and edits its .profile as follows, then / dev / * lv * is changed to Sybase.
Path = / usr / bin: / most / usr / sbin: / usr / ucb: $ home / bin: /sybase.bin: / sybase / install: / sybase: / usr / bin / x11: / sbin :. export PATH TERM = ibm3151 export TERM DSQUERY = SYBASE export DSQUERY SYBASE = / sybase export SYBASE LIBPATH = / sybase / lib export LIBPATH (7) to copy files from a machine sybase smit-> system storage management-> file systems-> mount a file system -> Determine the following parameters> file system name [/ dev / cd0]> Directory over which to mount [/ mnt]> Type of file system [cdfs]> mount as a removable file system [yes]> mount as a ready System [YES] After installing the disc, the / sybase directory is Sybase, then execute the / mnt / sybload -d command with the Sybase user, then build start_sybase and stop_sybase, Note that this two files should be given to execute.
Current directory is "/ sybase": Is this the correct directory for installation If so, please enter 'y' or 'Y':? Y Is this a local or remote installation, as defined in your installtion Guide Please enter L for or? R for remote> L Please enter the full name of the disk file of the global archive:.> / mnt / sybimage You specified / mnt / sybimage for the media device Is this correct Please enter 'y' or 'Y' to.? continue: Y Please enter your customer authorization string.letters only> JLBKBKBKGKCMBYBKBFGZBYBKBKBKQPQDRX (/ mnt / install / cas) Terminate your entries with a blank line: select product 1,2> Adaptive server enterprise, RS6000,11.9.2> Monitor server for 11.9 .2 ASE, RS6000, 11.9.2> Enter The Following Products Were Chosen for Installation: Choice No.1: Adaptive Server Enterprise, RS6000, 11.9.2 Choice No.2: Monitor Server for 11.9.2 ASE, RS6000, 11.9 .2 if this list is correct as shown, please enter 'y' Y 'To Continue, please ente R 'q' or 'q' to quit, or any other character to make another set to choices: y is to copy the Sybase system file.
The contents of editing / sybase / start_sybase are as follows: (Repeat (2) - (7) step on the host (9) Construction database device SMIT MKLV-> RAIDGROUP1-> determine The following parameters> Logical Volume Name: [LV_Master]> Number of Logical Partitions: [3] # RAIDGROUP1 volume group 32M per physical partition (see 5- (2)), 3 partitions a total of 96m> Physical Volume Names: [hdisk1] Top 4 sets, Logical Volume Name is LV_SYBPROC, LV_TEMPDB, LV_DATA1, LV_LOG1, Number of Logical Partitions, respectively, 3 (96M), 20 (640M), 330 (10560M), 64 (2048M), Physical Volume Names HDisk1. Complete the reform / dev / * lv * is Sybase.
(10) After the Sybase device IMPORT generated on the host, after Varyoffvg RaidGroup1 on the host, the Smit Exportvg on the host and determines the parameter raidgroup1, (at this time, the slave is not first Varyonvg RaidGroup1), then LSVG can be seen on the LSVG can see RaidGroup1 Fill, then use Smit Importvg on the slave and determine that Volume Group Name is RAIDGROUP1, then change the machine on / dev / * lv * for Sybase, and VaryOffvg raidgroup1 on the slave Varyonvg RaidGroup1. TOI: Somit exportvg on a machine is removed, the importvg is loaded with a VG (note that the VG loaded at this time must be Varyoffvg on the target). (11) Edit three Sybase files on the host> Su - Sybase > cd / sybase / init / sample_resoure_files> mkdir / sybase / yijian> cp * .rs / sybase / yijian> cd / sybase / yijian> mv srvbuild.adaptive_server.rs syb.rs> mv srvbuild.backup_server.rs syback.rs> modify syb.rs follows sybinit.release_directory: / sybase sybinit.product: sqlsrv sqlsrv.server_name: SYBASE sqlsrv.new_config: yes sqlsrv.do_add_server: yes sqlsrv.network_protocol_list: tcp sqlsrv.network_hostname_list: YYSD_H701 sqlsrv.network_port_list: 6000 sqlsrv.master_device_physical_name: / dev / rlv_master sqlsrv.master_devi ce_size: 90 sqlsrv.master_database_size: 60 sqlsrv.errorlog: USE_DEFAULT sqlsrv.do_upgrade: no sqlsrv.sybsystemprocs_device_physical_name: / dev / rlv_sybproc sqlsrv.sybsystemprocs_device_size: 90 sqlsrv.sybsystemprocs_database_size: 80 sqlsrv.default_backup_server: SYB_BACKUP> modified as follows sybinit.release_directory syback.rs : / sybase sybinit.product: bsrv bsrv.server_name: SYB_BACKUP bsrv.do_add_backup_server: yes bsrv.network_protocol_list: tcp bsrv.network_hostname_list: YYSD_H701 bsrv.network_prot_list: 6002 bsrv.language: USE_DEFAULT bsrv.character_set: cp850 bsrv.errorlog: USE_DEFAULT>
Sqlloc.rs modified as follows sybinit.release_directory: / sybase sqlsrv.server_name: SYBASE sqlsrv.sa_login: sa sqlsrv.sa_password: sqlsrv.default_language: us_english sqlsrv.default_install_list: USE_DEFAULT sqlsrv.default_characterset: cp850 sqlsrv.characterset_install_list: USE_DEFAULT sqlsrv.characterset_remove_list: USE_DEFAULT SQLSRV.SORT_ORDER: Binary After three files are finished, log in and execute instructions with Sybase users to create a database: $ srvbuildres -r syb.rs $ srvbuildres -r syback.rs $ sqllocres -r sqlloc.rs $ chown Sybase / dev / * LV * $ Chown -r Sybase / Sybase After starting Sybase to confirm success, pay attention to the permission unity, and Run * should have an execution right. (12) From the host copy three group files (/SYBASE/Sybase.cfg ,/sybase/interfaces ,/sybase/ install / run *) to the slave, where Interfaces wants to change the host name, after completion, Varyoffvg Raidgroup1 on the host and From the machine first smit exportvg, then smit importvg and varyonvg the volume group, execute Chown -R Sybase / Sybase and Chown Sybase / DEBASE and Chown Sybase / DEBASE and Chown Sybase / DEV / * LV * after completion, and start Sybase confirmation. (13) Varyoffvg raidgroup1 on the host, execute the Smit Importvg after Export Raidgroup1 on the slave, then introduced RaidGroup1, after completion of Varyonvg RaidGroup1, and start Sybase on the slave to confirm success. 8.
Set HA Application Services on the host (1) Setting HA Resource Group Smit Hacmp-> Cluster Configuration-> Cluster Resources-> Define Resource Groups-> Add A Resource Group-> Determine the following parameters> Resource Group name [ResourceGroup1]> Participting Node names [node_h701 node_h702] (2) defines application service smit hacmp-> cluster configuration-> cluster resources-> define application servers-> add an application server-> determining the following parameters> server name [sybase_app]> start script [/ sybase / start_sybase]> stop_script [/ sybase / stop_sybase] (3) resource resource modification group smit hacmp-> cluster configuration-> cluster resources-> change / show resources for a resource group-> determining the following parameters> service IP libel [syb01_ip] > VOLUME Group [RAIDGROUP1]> Application Servers [Sybase_APP]> Inactive Takeover ActiVated [TRUE] (4) HA Resource Synchronous Synchronization First, the RAIDGROUP1 VARYONVG will be on the host and change the host name in the two machine Interfaces files to the service address IP. (SYB01_IP), restart the system after synchronization. Smit Hacmp-> Cluster Configuration-> Cluster Resources-> SYNCHRONIZE CLUSTER RESOURCES (5) Start the master-slave HACMP service, and then the master-slave switching test. 9. Sybase patch (1) Install patch disc, execute the cp /mnt/ebf8943.tar /sybase/ebf.tar command, and then perform the tar xvf /sybase/ebf.tar command with Sybase. (2) Start the HA and Sybase, perform the following statement with Sybase Sybase> isql -usa -p -n -i / sybase / scripts / installmaster -o installmaster.txt> isql -usa -p -n -i / sybase / scripts / installdbcdb -o installdbcdb.txt> isql -usa -p -n -i /sybase/scripts/instmsgs.ebf -o instimsgs.txt ------------------------------------------------------------------------------------------------ ----- Supplement: Installation applications on the ground, so that the cluster is running two applications and is two-machine. 1. Create a Sybase user on the slave, edit its .profile file, build the Sybase logical volume on rootvg and make the file system after Mount.
