SteelEye Protection Suite for Linuxv8.1Technical DocumentationAugust 2012
Extending a Raw Device Resource Hierarchy 140Unextending a Hierarchy 140Creating a Resource Dependency 141Deleting a Resource Dependency 142Deleting a
Data Replication Configurationlibstdc++libraryrequirementWhile running the SPS Installation setup script, you may encounter a messageregarding a faile
Network ConfigurationItem DescriptionSteelEye DataKeeperdocumentationThe documentation for SteelEye DataKeeper is located within theSteelEye Protectio
Storage and Adapter ConfigurationItem DescriptionLocalizedOraclemountpointsLocalized Oracle environments are different depending on whether you connec
Storage and Adapter ConfigurationItem DescriptionHeavy I/O in Multipath ConfigurationsIn multipath configurations, performing heavyI/O while paths are
Storage and Adapter ConfigurationItem DescriptionSpecial Considerations for Switchovers withLarge Storage ConfigurationsWith some large storage config
Storage and Adapter ConfigurationItem DescriptionHP 3PAR V400The HP 3PAR V400 was tested by a SIOSTechnology Corp. partner with the followingconfigura
Storage and Adapter ConfigurationItem DescriptionHP MSA2000fcCertified by Hewlett-Packard Company withFibre Channel in both single path and multipathc
Storage and Adapter ConfigurationItem DescriptionHP P2000 G3 MSA SASCertified by SIOS Technology Corp. in multipathconfigurations using the Device Map
Storage and Adapter ConfigurationItem DescriptionHP XP20000/XP24000Certified by SIOS Technology Corp. usingLifeKeeper forLinux with DMMP ARK in RHEL5
Storage and Adapter ConfigurationItem DescriptionIBM DS3500(FC Model)Certified by SIOS Technology Corp. in singlepath and multipath configurations on
GUI Client 157Starting GUI clients 157Starting the LifeKeeper GUI Applet 157Starting the application client 158Exiting GUI Clients 158Configuring the
Storage and Adapter ConfigurationItem DescriptionIBM eServer xSeries Storage Solution ServerType445-R / Type445-FR for SANmelodyCertified by partner t
Storage and Adapter ConfigurationItem DescriptionDell PowerVault with Dell PERC and LSI LogicMegaRAID controllersSIOS Technology Corp. has certified t
Storage and Adapter ConfigurationItem DescriptionDell | EMC (CLARiiON) CX200EMC has approved two QLogic driver versionsfor use with this array and the
Storage and Adapter ConfigurationItem DescriptionDell EqualLogic PS5000The Dell EqualLogic was tested by a SIOSTechnology Corp. partner with the follo
Storage and Adapter ConfigurationItem DescriptionHitachi HDS 9570V, 9970V and 9980VCertified by SIOS Technology Corp. in a singlepath configuration wi
Storage and Adapter ConfigurationItem DescriptionHitachi HDS 9980VThere are certain specific “host mode” settingsrequired on the Hitachi arrays in ord
Storage and Adapter ConfigurationItem DescriptionFujitsu ETERNUS3000This storage unit was tested by a SIOSTechnology Corp. partner organization in asi
Storage and Adapter ConfigurationItem DescriptionFujitsu ETERNUS2000 Model 200This storage unit was tested by Fujitsu Limitedin a multipath configurat
Storage and Adapter ConfigurationItem DescriptionTID MassCareRAIDThis storage unit was tested by a SIOSTechnology Corp. partner with the followingsing
Storage and Adapter ConfigurationItem DescriptionDataCore SANsymphonyThis storage device was successfully testedwith SUSE SLES 9 Service Pack 3, Devic
Internet Explorer 168Status Table 168Properties Panel 169Output Panel 169Message Bar 170Exiting the GUI 170Common Tasks 170Starting LifeKeeper 170Star
HP Multipath I/O ConfigurationsHP Multipath I/O ConfigurationsItem DescriptionMSA1000 andMSA1500MultipathRequirementswith SecurePathLifeKeeper support
HP Multipath I/O ConfigurationsMultipathSupport forEVA withQLogicFailover DriverLifeKeeper supports the EVA 3000/5000 and the EVA 4X00/6X00/8X00 with
Device Mapper Multipath I/O ConfigurationsSingle Path onBoot Up DoesNot CauseNotificationIf a server can access only a single path to the storage when
Device Mapper Multipath I/O ConfigurationsHardwareRequirementsThe Device Mapper Multipath Kit has been tested by SIOS Technology Corp. withthe EMC CLA
Device Mapper Multipath I/O ConfigurationsTransientpath failuresWhile running IO tests on Device Mapper Multipath devices, it is not uncommonfor actio
LifeKeeper I-O Fencing IntroductionLifeKeeper I-O Fencing IntroductionI/O fencing is the locking away of data from a malfunctioning node preventing un
Non-Shared StorageNon-Shared StorageIf planning to use LifeKeeper in a non-shared storage environment, the risk of data corruption thatexists with sha
I/O Fencing ChartQuroum/WitnessWatchdogWatchdog & Quorum/WitnessSTONITH (serial)Reservations OffNothingSTONITH (serial)CONFIRM_SO*Quorum/WitnessWa
Quorum/WitnessMost Reliable Least Reliable* While CONFIRM_SO is highly reliable (depending upon the knowledge of
Package Installation and ConfigurationPackage Installation and ConfigurationThe Quorum/Witness Server Support Package for LifeKeeper will need to be i
Column Width 180Viewing Message History 181Reading the Message History 181Expanding and Collapsing a Resource Hierarchy Tree 182Cluster Connect Dialog
Available Quorum ModesAvailable Quorum ModesThree quorum checking modes are available which can be set via the QUORUM_MODE setting in/etc/default/Life
Available Witness Modes# This can be either off/none or remote_verify. In remote_verify# mode, core event handlers (comm_down) will doublecheck the# d
Available Actions When Quorum is LostAvailable Actions When Quorum is LostThe witness package offers three different options for how the system should
Adding a Witness Node to a Two-Node ClusterGUI will not automatically connect to the other servers with established communication paths. Asthis behav
Expected Behaviors (Assuming Default Modes)Simple Two-Node Cluster with Witness NodeServer A and Server B should already be set up with LifeKeeper cor
Scenario 4In this case, Server B will do the following:l Begin processing a communication failure event from Server A.l Determine that it can still co
SCSI ReservationsSCSI ReservationsStorage Fence Using SCSI ReservationsWhile LifeKeeper for Linux supports both resource fencing and node fencing, its
Alternative Methods for I/O Fencingfrom partially hung servers. In cases where a hung server goes undetected by LifeKeeper, watchdogwill begin recover
Package RequirementsPackage Requirementsl VMware vSphere SDK Package (e.g. VMware-vSphere-SDK-4.X.X-XXXXX.i386.tar.gz)l VMware vSphere CLI (vSphere CL
<vm_id>/opt/LifeKeeper/config/stonith.conf# LifeKeeper STONITH configuration## Each system in the cluster is listed below. To enable STONITH for
LifeKeeper Flags 196Resources Subdirectories 197Resource Actions 198Structure of LCD Directory in /opt/LifeKeeper 198LCM 199Communication Status Infor
Expected Behaviorsvmware-cmd -H 10.0.0.1 -U root -P secret/vmfs/volumes/4e08c1b9-d741c09c-1d3e-0019b9cb28be/lampserver/lampserver.vmxstop hardNote:
ConfigurationRead the next section carefully. The daemon is designed to recover from errors and will reset thesystem if not configured carefully. Plan
UninstallNote: Configuring watchdog may cause some unexpected reboots from time to time. This is thegeneral nature of how watchdog works. If processes
Steeleye Protection Suite/vAppKeeper Recovery BehaviorSteeleye Protection Suite/vAppKeeper Recovery BehaviorSteeleye Protection Suiteand SteelEye vAp
Meta Policiesprior to performing a failover. This policy setting can be used to turn on/off local recovery.l TemporalRecovery- Normally, Steeleye Pro
The lkpolicy ToolIn the above resource hierarchy, app depends on both IP and file system. A policy can be setto disable local recovery or failover of
Listing Policies[root@thor49 ~]# lkpolicy -l -d v6test4Please enter your credentials for the system 'v6test4'.Username: rootPassword:Confirm
Configuring CredentialsConfiguring CredentialsCredentials for communicating with other systems are managed via a credential store. This store canbe ma
LifeKeeper APIThis will show the entire man/help page for the command.LifeKeeper APIThe LifeKeeper API is used to allow communications between LifeKee
LifeKeeper AdministrationOverviewLifeKeeper does not require administration during operation. LifeKeeper works automatically tomonitor protected resou
Starting LifeKeeper 210Starting LifeKeeper Server Processes 211Enabling Automatic LifeKeeper Restart 211Stopping LifeKeeper 211Disabling Automatic Lif
Administrator TasksAdministrator TasksEditing Server Properties1. To edit the properties of a server, bring up the Server Properties dialog just as yo
Deleting a Communication PathHelp for an explanation of each choice.3. Select the Local Server from the list box and click Next.4. Select one or more
Server Properties - Failoverl Right-click on a server icon, then click Delete Comm Path when the server contextmenu appears.l On the global toolbar, c
Creating Resource HierarchiesTo commit your selections, press the Apply button.Creating Resource Hierarchies1. There are four ways to begin creating a
LifeKeeper Application Resource Hierarchies3. Select the Switchback Type and click Next.4. Select the Server and click Next. Note: If you began from t
Creating a File System Resource Hierarchybutton.l On the Edit menu, select Server, then click on Create Resource Hierarchy.2. A dialog entitled Create
Creating a Generic Application Resource HierarchyCreating a Generic Application Resource HierarchyUse this option to protect a user-defined applicatio
Creating a Raw Device Resource Hierarchycause the resource state to be set to OSU following the create; selecting Yes will cause thepreviously provide
Editing Resource Properties7. Click Create Instance to start the creation process. A window titled Creating scsi/rawresource will display text indicat
Using the Up and Down ButtonsThere are two ways to modify the priorities:l Reorder the priorities by moving an equivalency with the Up/Down buttons ,o
Data Replication 231IPv6 234Apache 237Oracle Recovery Kit 237NFS Server Recovery Kit 238SAP Recovery Kit 239LVM Recovery Kit 240DMMP Recovery Kit 241P
Editing the Priority ValuesEditing the Priority Values1. Select a priority by clicking on a priority value in the Priority column of the Equivalencies
Extending a File System Resource Hierarchythe Pre-Extend Wizard dialog appears, select a Template Server and a Tag toExtend, clicking on Next after ea
Extending a Raw Device Resource Hierarchyextending resource hierarchies. After you have done that, you then complete the steps below, whichare specifi
Creating a Resource Dependencyl Right-click on the icon for the global resource hierarchy that you want to unextended.When the resource context menu a
Deleting a Resource Dependencyl On the Edit menu, point to Resource and then click Create Dependency. When thedialog comes up, select the server in th
Deleting a Hierarchy from All Serversservers in the cluster.4. If the output panel is enabled, the dialog closes, and the results of the commands to d
LifeKeeper User GuideThe User Guide is a complete, searchable resource containing detailed information on the manytasks that can be performed within t
Using LifeKeeper for LinuxUsing LifeKeeper for LinuxThe following topics provide detailed information on the LifeKeeper graphical user interface (GUI)
Exiting GUI Clientstasks.l The context (popup) and global menus provide access to all tasks.Exiting GUI ClientsSelect Exit from the File Menu to disco
Suggested Action: 251Recovering from a Non-Killable Process 252Recovering From A Panic During A Manual Recovery 252Recovering Out-of-Service Hierarchi
MenusMenusSteelEye LifeKeeper for Linux MenusResource Context MenuThe Resource Context Menu appears when you right-click on a global (cluster-wide) re
Server Context MenuExtend Resource Hierarchy. Copy a resource hierarchy to another server for failover support.Unextend Resource Hierarchy. Remove an
File MenuFile MenuConnect. Connect to a LifeKeeper cluster. Connection to each server in the LifeKeeper clusterrequires login authentication on that s
Edit Menu - ServerEdit Menu - ServerDisconnect. Disconnect from a cluster.Refresh. Refresh GUI.View Logs. View LifeKeeper log messages on connected se
Help MenuProperties Panel. Display this component if the checkbox is selected.Output Panel. Display this component if the checkbox is selected.Options
GUI ToolbarDisconnect. Disconnect from a LifeKeeper cluster.Refresh. Refresh GUI.View Logs. View LifeKeeper log messages on connected servers.Create R
Resource Context ToolbarCreate Dependency. Create a parent/child relationship between two resources.Delete Dependency. Remove a parent/child relations
Resource Context ToolbarRemove Dependency. Remove a parent/child relationship between two resources.Delete Resource Hierarchy. Remove a resource hiera
Server Context ToolbarServer Context ToolbarThe server context toolbar is displayed in the properties panel when you select a server in the statustabl
GUI Serverits configuration data. Since the LifeKeeper GUI is a client/server application, a user will run thegraphical user interface on a client sys
Scenario 4 262Installation and Configuration 265Before Configuring Your DataKeeper Resources 265Hardware and Software Requirements 265Hardware Require
Starting the application clientNOTE: When you run the applet, if your system does not have the required Java Plug-in, you will beautomatically taken t
GUI ConfigurationSee Running the GUI on a Remote System for information on configuring and running the GUI on aremote system outside your LifeKeeper c
GUI LimitationsGUI LimitationsItem DescriptionGUI inter-operabilityrestrictionThe LifeKeeper for Linux client may only be used to administer LifeKeepe
LifeKeeper GUI Server ProcessesThis command halts all LifeKeeper GUI Server daemon processes on the server being administered ifthey are currently run
Java Security PolicyThey take effect on the user's next login or when the GUI server is restarted, whichever comes first.Each user has a single p
Policy File Creation and ManagementThe user policy file starts with `.` and is by default at:<USER.HOME>\.java.policyNote: USER.HOME refers to t
Sample Policy Fileperm = new java.io.FilePermission("/tmp/abc","read");In this, the target name is "/tmp/abc" and the ac
Java Plug-InJava Plug-InRegardless of the browser you are using (see supported browsers), the first time your browserattempts to load the LifeKeeper G
Running the GUI on a Remote Systeml If you already have a user policy file, you can add the required entries specifiedin/opt/LifeKeeper/ htdoc/java.po
Applet TroubleshootingApplet TroubleshootingIf you suspect that the applet failed to load and initialize, try the following:1. Verify that applet fail
Overview 284Creating a DataKeeper Resource Hierarchy 284Extending Your Hierarchy 286Extending a DataKeeper Resource 287Unextending Your Hierarchy 288D
Browser Security Parameters for GUI Appletand password.4. Once a connection to the cluster is established, the GUI window displays a visualrepresentat
Properties Panelresources. It shows:l the state of each server in the top row,l the global (cross-server) state and the parent-child relationships of
Message Barthat command is added under this label. If you are running multiple commands at the same time(typically on different servers), the output f
Enabling Automatic LifeKeeper RestartNote: If you receive an error message referencing the LifeKeeper Distribution Enabling Packagewhen you start Life
Disabling Automatic LifeKeeper RestartDisabling Automatic LifeKeeper RestartIf you do not want LifeKeeper to automatically restart when the system is
Connecting Servers to a ClusterREGISTRY=internal -DGUI_WEB_PORT=81com.steeleye.LifeKeeper.beans.S_LKConnecting Servers to a Cluster1. There are two po
Viewing Connected Servers1. There are three possible ways to begin.l On the Global Toolbar, click the Disconnect button.l On the Edit Menu, select Ser
Viewing Server PropertiesALIVEClient has valid connection to the server.Comm paths originating from this server to an ALIVE remote server areALIVE.Com
Viewing Resource Tags and IDsl On the Edit Menu, point to Server, click View Log, then select the server that you wantto view from the Server list in
Global Resource StatusServerResourceStateVisualStateWhat it MeansActive Resource is operational on this server and protected. (ISP)DegradedResource is
This document and the information herein is the property of SIOS Technology Corp. (previouslyknown as SteelEye® Technology, Inc.) and all unauthorized
Example: 302Server Failure 303Resynchronization 303Avoiding Full Resynchronizations 304Method 1 304Procedure 304Method 2 305Procedure 305Clustering wi
Viewing Resource PropertiesVisualStateDescription What it Means / CausesNormalResource is active (ISP) and all backups areactive.WarningResource is ac
Setting View Options for the Status WindowSetting View Options for the Status WindowThe Options Dialog is available from the View menu. This allows yo
Resource TreeResource TreeThis option group allows you to specify the sorting order of the resources in the resource hierarchytree.l Sort By Resource
Viewing Message Historyl Automatic: Automatically resizes all columns to fill available space.Note: The 7 (seven) and 8 (eight) keys are defined as ho
Expanding and Collapsing a Resource Hierarchy TreeExpanding and Collapsing a Resource Hierarchy TreeIn this segment of the tree, the resource file_sys
Cluster Connect DialogNote: The "9" and "0" keys are defined as hot/accelerator keys to facilitate quickly expanding orcollapsing
Resource Properties DialogResource Properties DialogThe Resource Properties dialog is available from the Edit menuor from aresource context menu.Thi
Relations Tabresources can be active on only one of the grouped systems at a time.l Initialization. The setting that determines resource initializatio
General TabGeneral Tabl Name. Name of the selected server.l State. Current state of the server. These are the possible server state values:l ALIVE - s
General Tabl Administrator - the user can perform any LifeKeeper task.l Operator - the user can monitor LifeKeeper resource and server status, and can
Successful Migration 334Troubleshooting 337Index 341Table of Contents xix
CommPaths TabCommPaths Tabl Server. The server name of the other server the communication path is connected to in theLifeKeeper cluster.l Priority.Th
Resources TabThese are the possible communications path status values displayed below the detailed textin the lower panel:l NORMAL - all comm paths fu
Operator Tasksl Name. The tag name of a resource instance on the selected server.l Application. The application name of a resource type (gen, scsi, ..
Taking a Resource Out of Serviceservice without bringing its parent resource into service as well. Click In Service to bring theresource(s) into servi
Related TopicsThe LifeKeeper Configuration Database (LCD) maintains the object-oriented resource hierarchyinformation and stores recovery direction in
Hierarchy DefinitionHierarchy DefinitionThese are the tasks required to construct the example application hierarchy:1. Create file system resources. T
Hierarchy DefinitionNote: Although you can create much of the definition using the LifeKeeper GUI, the rest of thisexample demonstrates the command in
LCD Configuration Datadep_create -d Server1 -p the-project-plan -c schedule-on-Server1dep_create -d Server2 -p the-project-plan -cschedule-from-Server
LCD Directory StructureDisks on a Small Computer System Interface (SCSI) bus are one example of equivalent resources.With the SCSI locking (or reserve
Resources Subdirectoriesdifferent resource type for other application resource hierarchies or app for generic or user-defined applications.lOther typi
Resource Actionsl actions. This directory contains the set of recovery action programs that act only on resourceinstances of the specific resource typ
LCMLCMThe LifeKeeper Communications Manager (LCM) provides reliable communication betweenprocesses on one or more LifeKeeper servers. This process can
Communication Status Informationl Failover Recovery. If a resource fails on a system, the LCM notifies LifeKeeper to recoverthe resource on a backup s
Alarm ProcessingDefining additional scripts for the sendevent alarming functionality is optional. When you defineLifeKeeper resources, LifeKeeper prov
Changing LifeKeeper Configuration Values2. If you are changing the uname of a LifeKeeper server, change the server's hostname using theLinux host
File System Health MonitoringValue Old Newuname Server1 Newserver1comm path address 172.17.100.48 172.17.105.49IP resource address 172.17.100.220 172.
Condition Definitionsl A warning message can be logged and email sent to a system administrator.l Local recovery of the resource can be attempted.l Th
Maintaining a LifeKeeper Protected Systeml mount point is busyl mount failurel LifeKeeper internal errorMaintaining a LifeKeeper Protected SystemWhen
Recovering After a Failover3. Restore the hierarchy. Use the LifeKeeper GUI to bring the resource hierarchy back inservice. See Bringing a Resource In
Removing via GnoRPMl Remove all packages. If you remove the LifeKeeper core, you should first remove otherpackages that depend upon LifeKeeper; for ex
Chapter 1: IntroductionAbout SteelEye Protection Suite for LinuxSteelEye Protection Suite (SPS) for Linux integrates high availability clustering with
LifeKeeper Communication Pathsnetwork access requirements.Note: If you wish to simply disable your firewall, see Disabling a Firewallbelow.LifeKeeper
Disabling a Firewallformula:10001 + <mirror number> + <256 * i>where i starts at zero and is incremented until the formula calculates a po
Starting LifeKeeper1. Make sure your IT department has opened the secure shell port on the corporate firewallsufficiently to allow you to get behind t
Starting LifeKeeper Server ProcessesStarting LifeKeeper Server ProcessesIf LifeKeeper is not currently running on your system, type the following comm
Disabling Automatic LifeKeeper RestartThis command will remove the resources from service but does not set the !nofailover! flag [seeLCDIflag(1M)] on
TuningLargeClusterSupportLifeKeeper supports large cluster configurations, up to 32 servers. There are manyfactors other than LifeKeeper, however, tha
LifeKeeper OperationsIPCSemaphoresand IPCSharedMemoryLifeKeeper requires Inter-Process Communication (IPC) semaphores and IPCshared memory. The defau
LifeKeeper OperationsSystemPanic onLockedSharedDevicesLifeKeeper uses a lock to protect shared data from being accessed by other servers ona shared SC
Server ConfigurationServer ConfigurationItem DescriptionBIOS Updates The latest available BIOS should always be installed on all LifeKeeper servers.Pa
Set Block Resource Failover On:system administrator before allowing LifeKeeper to perform a failover recovery of a system that itdetects as failed.Use
SPS Core Package ClusterThe SPS for Linux image file includes a core package cluster containing the following softwarepackages:SPS Core Package Cluste
NFS Client Mounting ConsiderationsNFS Client Mounting ConsiderationsAn NFS Server provides a network-based storage system to client computers. To util
Expanded Multicluster ExampleSteelEye Protection Suite for Linux219
TroubleshootingThe Message Catalog (located on our Technical Documentation site under “Search for an ErrorCode”) provides a listing of all error codes
InstallationDescriptionGUI does not work with default RHEL6 64-bitThere is a compatibility issue against Red Hat Enterprise Linux 6 64-bitSolution: In
LifeKeeper CoreLifeKeeper CoreSteelEye Protection Suite for Linux223
LifeKeeper CoreDescriptionLanguage Environment EffectsSome LifeKeeper scripts parse the output of Linux system utilities and rely on certain patterns
LifeKeeper CoreDescriptionlkscsid will halt system when it should issue a sendeventWhen lkscsid detects a disk failure, it should, by default,issue a
LifeKeeper CoreDescriptionThe use of lkbackups taken from versions of LifeKeeper previous to 8.0.0 requiresmanually updating /etc/default/LifeKeeper w
LifeKeeper CoreDescriptionLifeKeeper syslog EMERG severity messages do not display to a SLES10 or SLES11host's console which has AppArmor enabled
TrainingSection DescriptionSPS for LinuxInstallationGuideProvides useful information for planning and setting up your SPS environment,installing and l
Internet/IP LicensingInternet/IP LicensingDescriptionINTERFACELIST syntax,/etc/hostssettings dependency/etc/hosts settings:When using internet-based
GUIGUIDescriptionGUI login prompt may not re-appear when reconnecting via a web browser after exitingthe GUIWhen you exit or disconnect from the GUI a
GUIDescriptionJava Mixed Signed/Unsigned Code Warning - When loading the LifeKeeper Java GUIclient applet from a remote system, the following security
Data ReplicationDescriptionsteeleye-lighttpd process fails to start if Port 778 is in useIf a process is using Port 778 when steeleye-lighttpd starts
Data ReplicationDescription32-bit zlib packages should be installed to RHEL 6 (64-bit) for Set Compression LevelWhen using SDR with RHEL 6 (64-bit),
Data ReplicationDescriptionMirror resyncs may hang in early RedHat/CentOS 6.x kernels with a "Failed to removedevice" message in the LifeKee
IPv6IPv6234Troubleshooting
IPv6DescriptionSIOS has migrated to the use of theipcommand and away from theifconfigcommand.Because of this change,customers with external scrip
IPv6Description'IPV6_AUTOCONF = No' for/etc/sysconfig/network-scripts/ifcfg-<nicName>is not beinghonored on reboot or bootOn boot, a
ApacheDescriptionIPv6 resource reported as ISP when address assigned to bonded NIC but in 'tentative'stateIPv6 protected resources in LifeKe
Technical Supportl Log a Caseto report new incidents.l View Casesto see all of your open and closed incidents.l Review Top Solutionsproviding infor
NFS Server Recovery KitDescriptionThe Oracle Recovery Kit does not support the ASM or grid component features of Oracle10gThe following information ap
SAP Recovery KitDescriptionNFS v4 cannot be configured with IPv6IPv6 virtual IP gets rolled up into the NFSv4 heirarchy.Solution: Do not use an IPv6 v
LVM Recovery KitDescriptionWhen changes are made to res_state, monitoring is disabledIfProtection Levelis set toBASICand SAP is taken down manuall
DMMP Recovery KitDMMP Recovery KitDescriptionDMMP: Write issued on standby server can hangIf a write is issued to a DMMP device that is reserved on an
MD Recovery KitMD Recovery KitDescriptionMD Kit does not support mirrors created with “homehost”The LifeKeeper MD Recovery Kit will not work properly
Samba Recovery KitDescriptionMD resource instances can be adversely impacted by udev processing during restoreDuring udev processing, device nodes are
Running from a Modem:e.g.:208.2.84.61 homer.somecompany.com homerThis should reduce the time it takes to make the first lookup.In addition, incorrect
From Windows:addresses. When unresolvable names, WINS names or unqualified DHCP names are used, thiscauses Java to throw an UnknownHostException.This
From Linux:l Try editing the hosts file to include entries for the local host and the LifeKeeperservers that it will be connected to.On Windows 95/98
Unable to Connect to X Window Server:5. Try setting the hostname property to be used by the GUI client. This will need to be changedfor each administr
Chapter 2: SPS InstallationThe SteelEye Protection Suite (SPS) Installation Guide contains information on how to plan andinstall your SPS environment.
Communication Paths Going Up and DownAs a result of this problem, your users may have trouble creating or changing resources during thefrozen interval
Restoring Your Hierarchy to a Consistent Stateresources for a hierarchy. In order to maintain consistency in a hierarchy, LifeKeeper requires thatprio
No Shared Storage Found When Configuring a Hierarchy6. As a last resort, if the hierarchy cannot be repaired, you may have to delete and re-create the
Recovering from a LifeKeeper Server Failurewith "NU-" then LifeKeeper was unable to get a unique ID from the device.Without a unique IDLife
Recovering from a Non-Killable Process4. Finally, extend each resource hierarchy from the server where the resource hierarchy is in-service to the re-
Taking the System to init state S WARNING(RS-232 TTY) console can experience severe problems with LifeKeeper service. During operation,LifeKeeper gene
Suggested Action:reason for alarm. However, if this message is frequently in the log, or the number is 2 or 3, then twoactions may be necessary:l Atte
Chapter 4: SteelEye DataKeeper for LinuxIntroductionSteelEye DataKeeper for Linux provides an integrated data mirroring capability for LifeKeeperenvir
Synchronous vs. Asynchronous Mirroringl Provides failover protection for mirrored data.l Integrates into the LifeKeeper Graphical User Interface.l Ful
Synchronization (and Resynchronization)that consists of a local disk or partition and a Network Block Device (NBD) as shown in the diagrambelow.A Life
SPS Core Package Clusteranswering Yes to each question in order to complete all the steps required by the installation imagefile.The SPS for Linux ima
Standard Mirror ConfigurationStandard Mirror ConfigurationThe most common mirror configuration involves two servers with a mirror established between
Multiple Target ConfigurationMultiple Target ConfigurationWhen used with an appropriate Linux distribution and kernel version 2.6.7 or higher, SteelEy
SteelEye DataKeeper Resource HierarchyA given source disk or partition can be replicated to a maximum of 7 mirror targets, and each mirrortarget must
Failover ScenariosThe resource datarep-ext3-sdr is the NetRAID resource, and the parent resource ext3-sdr is the filesystem resource. Note that subseq
Scenario 2Scenario 2Considering scenario 1, Server 2 (still the primary server) becomes inoperable during theresynchronization with Server 1 (now the
Scenario 4Result: LifeKeeper will not bring the DataKeeper resource ISP on Server 2. When Server 1 comesback up, LifeKeeper will automatically bring t
Installation and ConfigurationBefore Configuring Your DataKeeper ResourcesThe following topics contain information for consideration before beginning
Software RequirementsSoftware Requirementsl Operating System – SteelEye DataKeeper can be used with any major Linux distributionbased on the 2.6 Linux
Changing the Data Replication Pathl This release of SteelEye DataKeeper does not support Automatic Switchback for DataKeeperresources. Additionally,
Planning Your SPS EnvironmentThe following topics will assist in defining the SPS for Linux cluster environment.Mapping Server ConfigurationsDocument
Determine Network Bandwidth Requirementssufficient bandwidth to successfully replicate the partition and keep the mirror in the mirroring state asthe
Measuring Detailed Rate of ChangeSteelEye DataKeeper can mirror daily, approximately:T1 (1.5Mbps) - 14,000 MB/day (14 GB)T3 (45Mbps) - 410,000 MB/day
Analyze Collected Detailed Rate of Change Datamsg "\n";msg "This utility takes a /proc/diskstats output file that contains\n";msg
Analyze Collected Detailed Rate of Change Data'ios_pending' => 11,'ms_time_total' => 12,'weighted_ms_time_total' =
Analyze Collected Detailed Rate of Change Datamy $dev = shift;my $blksize = shift;my $interval = shift;my ($max, $maxindex, $i, $first, $last, $total)
Analyze Collected Detailed Rate of Change Datareturn @totalvals;}# converts to KB, MB, etc. and outputs size in readable formsub HumanSize {# params:
Graph Detailed Rate of Change Data# ./roc-calc-diskstats 2m “Jul 22 16:04:01” /root/diskstats.txtsdb1,sdb2,sdc1 > results.txtThe above example dump
Graph Detailed Rate of Change Data1. Open results.csv, and select all rows, including the total column.2. Open diskstats-template.xlsx, select the dis
Graph Detailed Rate of Change Data5. Make a note of the following row/column numbers:a. Total (row 6 in screenshot below)b. Bandwidth (row 9 in screen
Graph Detailed Rate of Change Data“=diskstats.csv!$B$<row>:$<final_column>$<row>"example: “=diskstats.csv!$B$9:$R:$9"iv. C
Table of ContentsChapter 1: Introduction 1About SteelEye Protection Suite for Linux 1SPSfor Linux Integrated Components 1SteelEye Protection Suite So
Sample Configuration Map for LifeKeeper Pairlocked resources at any given time. LifeKeeper device locking is done at the Logical Unit(LUN) level. For
Confirm Failover and Block Resource Failover Settingsiv. Click OKc. Click OK to exit the Wizard8. The Bandwidth vs ROC graph will update.Please analy
When to Select This Settingtime in seconds that LifeKeeper should wait before taking the default action (setting this to zeromeans “don’t wait before
Setting the Flags on Each Serverfailure. It will only block failovers due to local resource failures.Setting the Flags on Each Server1. Log in to the
Examples3. In the Set Block Resource Failover On column, select the checkbox for each server in thecluster as required.In the following example, Serve
Block Failover in One Direction3. In /etc/default/LifeKeeper, set the following:CONFIRMSODEF = 1CONFIRMSOTO = 04. Perform the above steps on each serv
Replicate New File Systemtype. There are several different DataKeeper resource types. The following information can help youdetermine which type is b
Resource Configuration TasksResource Configuration TasksYou can perform all SteelEye DataKeeper configuration tasks via the LifeKeeper Graphical UserI
Creating a DataKeeper Resource HierarchyField TipsSwitchbackTypeYou must select intelligent switchback. This means that after a failover tothe backup
Extending Your HierarchyExtending Your HierarchyThis operation can be started from the Edit menu or initiated automatically upon completing theCreate
Extending a DataKeeper ResourceField TipsTargetPrioritySelect or enter the Target Priority. This is the priority for the new extendedDataKeeper hierar
Storage and Adapter Optionsreside on a disk array subsystem (Redundant Array of Inexpensive Disks, or RAID). LifeKeepersupports a number of hardware
Unextending Your HierarchyField TipsDataKeeperResourceTagSelect or enter the DataKeeper Resource Tag name.Bitmap FileSelect or edit the name of the bi
Deleting a Resource Hierarchy1. On the Edit menu, select Resourcethen Unextend Resource Hierarchy.2. Select the Target Server where you want to unext
Bringing a DataKeeper Resource In Servicebreaks the mirror, unmounts the file system (if applicable), stops the md device and kills the nbdserver and
Performing a Manual Switchover from the LifeKeeper GUIIf you execute the Out of Service request, the resource hierarchy is taken out of service withou
AdministrationAdministering SteelEye DataKeeper for LinuxThe following topics provide information to help in understanding and managing SteelEye DataK
GUI Mirror AdministrationGUI Mirror AdministrationA SteelEye DataKeeper mirror can be administered through the LifeKeeper GUI in two ways:1. By enabli
Create and View Rewind BookmarksClick on each icon below for a descriptionor,2. By right-clicking thedata replication resourceand selecting an actio
Force Mirror OnlineForce Mirror OnlineForce Mirror Online should be used only in the event that both servers have become inoperable andthe primary ser
Rewind and Recover Data1. The mirror is paused.2. A timestamp associated with previous disk write is selected and the disk is rewound to thattime.3. T
Supported Storage ModelsVendor Storage Model CertificationConsan CRD5440 SIOS Technology Corp.testingCRD7220 (f/w 3.00) SIOS Technology Corp.testingDa
Rewind and Recover DataDialog 34. The data is being rewound. After the data is rewound, the target disk is mounted for read-onlyaccess so that the dat
Set Compression Levelresynced to the old source disk. Click Finish. Rewind is complete.10. You are asked to manually copy files to the source system.
Command Line Mirror Administrationmaximum size. However, the log will wrap around and overwrite the earliest entries when it detectsthat it has run ou
Examples:Note: mirror_settings should be run on the target system(s) (or on all systems, if you want thesettings to take effect regardless of which sy
Monitoring Mirror Status via Command LineMonitoring Mirror Status via Command LineNormally, the mirror status can be checked using the Replication Sta
Server FailureServer FailureIf both your primary and backup servers become inoperable, your DataKeeper resource will bebrought into service/activated
Avoiding Full ResynchronizationsAvoiding Full ResynchronizationsWhen replicating large amounts of data over a WAN link, it is desirable to avoid fullr
Method 27. Bring the mirror and dependent filesystem and applications (if any), into service. The bitmapfile will track any changes made while the dat
Clustering with Fusion-io3. Configure the communication paths in LifeKeeper.4. Create the mirror and extend to the target. A full resync will occur.5.
NetworkNetworkl Use a 10 Gbps NIC: Flash-based storage devices from Fusion-io (or other similar productsfrom OCZ, LSI, etc.) are capable of writing da
Supported Storage ModelsVendor Storage Model CertificationEMC Symmetrix 3000 Series SIOS Technology Corp.testingSymmetrix 8000 Series Vendor support s
Configuration Recommendationsnet.ipv4.tcp_wmem = 4096 65536 16777216net.ipv4.tcp_timestamps = 0net.ipv4.tcp_sack = 0net.core.optmem_max = 16777216net.
Multi-Site ClusterSteelEye Protection Suite for Linux Multi-Site ClusterThe SteelEye Protection Suite for Linux Multi-Site Cluster is a separately lic
Multi-Site Cluster Configuration Considerationsand are familiar with the SteelEye LifeKeeper graphical user interface, the SteelEye Protection SuiteMu
Multi-Site Cluster RestrictionsExample Description1Using the Multi-Site Cluster hierarchy’s mirror disk resource more than once in thesame or differen
Replicate New File SystemField TipsHierarchyTypeChoose the data replication type you wish to create by selecting oneof the following:l Replicate New F
Replicate New File System3. Select Back to select a different source disk or partition that is shared. Provide the remaininginformation to finish conf
Replicate New File SystemField TipsBitmap FileSelect the bitmap file entry from the pull down list.Displayed in the list are all available shared file
Replicate Existing File SystemReplicate Existing File SystemThis option will unmount a currently mounted file system on a local disk or partition, cre
DataKeeper ResourceField TipsBitmap FileSelect the bitmap file entry from the pull down list.Displayed in the list are all available shared file syste
DataKeeper ResourceField TipsSource Disk orPartitionThe list of Source Disks or Partitions in the drop down box contains all theavailable disks or par
Supported Storage ModelsVendor Storage Model CertificationFujitsu ETERNUS3000 (w/ PG-FC105, PG-FC106, or PG-FC107), single path onlyPartner testingET
Extending Your HierarchyField TipsDataKeeperResourceTagSelect or enter a unique DataKeeper Resource Tag name for the DataKeeperresource instance.Bitma
Extending Your Hierarchyinput/confirmation, click Accept Defaults.2. The Pre-Extend Wizard will prompt you to enter the following information.Note: Th
Extending a DataKeeper Resource4. Depending upon the hierarchy being extended, LifeKeeper will display a series of informationboxes showingthe Resour
Extending a Hierarchy to a Disaster Recovery SystemDuring resynchronization, the DataKeeper resource and any resource that depends on it willnot be ab
Extending a Hierarchy to a Disaster Recovery SystemNote: Depending upon the hierarchy being extended, LifeKeeper will display a series ofinformation b
Configuring the Restore and Recovery Setting for Your IP ResourceField TipsReplicationPathSelect the pair of local and remote IP addresses to use for
Migrating to a Multi-Site Cluster EnvironmentMigrating to a Multi-Site Cluster EnvironmentThe SteelEye Multi-Site Migrate feature is included in the S
Performing the MigrationPerforming the MigrationThere are three methods for configuring and performing a Multi-Site Migrate. You can:lSelect the Migra
Performing the Migrationl Select the file system resource and select the Migration icon from the Properties Paneltoolbar.326Multi-Site Cluster
Performing the MigrationIf you initiate the Migrate from the global toolbar icon, the following dialog box will display:1. Select the server where the
Supported Storage ModelsVendor Storage Model CertificationHitachi DataSystemsHDS RAID 700 (VSP) Partner testingHDS 7700 Vendor support statementHDS 58
Performing the Migration2. Select the root hierarchy tag that will be migrated and click Next. The root tag can be a filesystemor other application r
Performing the Migration3. Press Continue when the Continue button is enabled. The following bitmap dialog will display.SteelEye Protection Suite for
Performing the Migration4. Select a bitmap file for the file system you are migrating. Select Next.Important: Once you select Next, you will not be ab
Performing the Migration5. Select the second bitmap file for the second file system being migrated within the hierarchy.After selecting the first bitm
Performing the Migration7. This Summary screen displays all the configuration information you’ve submitted during theMigrate procedure. Once you selec
Performing the Migration8. The Migration status will display in this window. Press Finish when the Finish button isenabled.SteelEye Protection Suite f
Successful MigrationSuccessful MigrationThe following image is an example of a file system resource hierarchy after the Multi-Site migration iscomplet
Successful MigrationSteelEye Protection Suite for Linux335
TroubleshootingThis section provides information regarding issues that may be encountered with the use ofDataKeeper for Linux. Where appropriate, addi
Supported Storage ModelsVendor Storage Model CertificationHP/Compaq RA 4100 SIOS Technology Corp.testing14Planning Your LifeKeeper Environment
TroubleshootingSymptom Suggested ActionPrimary servercannot bring theresource ISP when itreboots after bothservers becameinoperable.If the primary ser
TroubleshootingSymptom Suggested ActionCore -LanguageEnvironmentEffectsSome LifeKeeper scripts parse the output of Linux system utilities and relyon
TroubleshootingSymptom Suggested ActionData Replication -GUI does not showproper state onSLES 10 SP2systemOn SLES 10 SP2, netstat is broken due to a
IndexIndexAActive/Active 42Active/Standby 43Adapter Options 9Administration 127API 126Asynchronous Mirroring 256Automatic LifeKeeper RestartDisabling
IndexConfiguration 61Application 79Concepts 40Data Replication 78General 266Network 79Verify Network Configuration 26Network and LifeKeeper 266Optiona
IndexServer Properties 185Disconnecting 173EEnvironmentSetup 25Error Detection 127Event Email Notification 67Configuration 69Overview 63Troubleshootin
IndexForce Mirror Online 296GGeneric Applications 39GUIAdding Icon to Desktop Toolbar 71Configuring 158Configuring Users 161Exiting 170Overview 156Run
IndexMirroring 255IP Addresses 39JJavaPlug-in 165Security Policy 162LLCD Interface (LCDI) 192License 31LifeKeeper Alarm Interface 200LifeKeeper Commun
IndexMenus 148Edit Menu - Resource 150Edit Menu - Server 151File 150Help 152Resource Context 148Server Context 149View 151Message Bar 170Mirror Admini
IndexRestore and Recover 323Restrictions 311NN-Way Recovery 127Nested File System 233Network BandwidthDetermine Requirements 267Measuring Rate of Chan
Supported Storage ModelsVendor Storage Model CertificationMA / RA 8000 SIOS Technology Corp.testingMSA1000 / MSA1500 (active/active and active/passive
IndexRecoveryAfter Failover 206Non-Killable Process 252Out-of-Service Hierarchies 252Panic During Manual Recovery 252Server Failure 251Removing LifeKe
IndexExtending 138, 286File System 139Generic Application 139Raw Device 140Hierarchy Relationships 47In Service 290Information 48Maintaining 205Out of
IndexFailover 130Viewing 175Shared Communication 41Shared Data Resources 40Shared Equivalencies 47Starting LifeKeeper 170, 210Status DisplayDetailed 4
IndexGUITroubleshooting 243Incomplete Resource Created 248Incomplete Resource Priority Modification 248Known Issues 221Restrictions 221TTY Connections
Supported Storage ModelsVendor Storage Model CertificationIBM FAStT200 SIOS Technology Corp.testing16Planning Your LifeKeeper Environment
Supported Storage ModelsVendor Storage Model CertificationFAStT500 SIOS Technology Corp.testingSteelEye Protection Suite for Linux17
Supported Adapter Models 22Setting Up Your SPS Environment 25Installing the Linux OS and Associated Communications Packages 25Connecting Servers and S
Supported Storage ModelsVendor Storage Model CertificationDS4100 * Partner testing18Planning Your LifeKeeper Environment
Supported Storage ModelsVendor Storage Model CertificationDS4200 Partner testingDS4300 (FAStT600) * SIOS Technology Corp.testingDS4400 (FAStT700) * SI
Supported Storage ModelsVendor Storage Model CertificationJetStor JetStor II SIOS Technology Corp.testingMicroNet Genesis One Vendor support statement
Supported Storage ModelsVendor Storage Model CertificationSun StorEdge 3310 Partner testingStorEdge 3510 FC (w/ Sun StorEdge 2Gb PCI SingleFC Network
Supported Adapter ModelsSupported Adapter ModelsAdapterTypeAdapter Model CertificationDifferentialSCSIAdapterAdaptec 2944 W, Adaptec 2944 UW, orAdapte
Supported Adapter ModelsAdapterTypeAdapter Model CertificationFibreChannelQLogic QLA 2100, QLogic QLA 2200, QLogic QLA2340, QLogic QLA 200 (HP Q200)HP
Setting Up Your SPS EnvironmentNow that the requirements have been determined and LifeKeeper configuration has been mapped,components of this SPS envi
Verifying Network Configuration1. Partition disks and LUNs. Because all disks placed under LifeKeeper protection must bepartitioned, your shared disk
VLAN Interface Support Matrixb. Change the server’s hostname using the Linux hostname command.c. Before continuing, you should ensure that the new hos
System Grouping Arrangements 41Active - Active Grouping 42Active - Standby Grouping 43Intelligent Versus Automatic Switchback 44Logging With syslog 45
Installing and Setting Up Database Applicationsprimary server, that IP address “switches” to the backup server.If you plan to configure resource hiera
Installing the SteelEye Protection Suite SoftwareInstall the SPS software on each server in the SPS configuration. Each SPS server must have thepackag
Installing the SPS SoftwareIMAGE_NAME is the name of the imageMOUNT_POINT is the path to mount location2. Change to the sps.img mounted directory and
Obtaining and Installing the LicenseSPS for Linux requires a unique license for each server. The license is a run-time license, whichmeans that you ca
Primary Network Interface Change May Require a License Rehost3. Ensure you have your LifeKeeper Entitlement ID (Authorization Code). You should havere
Internet/IP LicensingInternet/IP LicensingFor information regarding Internet/IP Licensing, please see the Known Issue in the SPS for LinuxTroubleshoot
Obtaining an Internet HOST IDl If ownership of the license certificate has changed, please contact SIOS Technology Corp.support personnel to have the
Upgrading SPSupgrade from the older version to one of the two acceptable versions, then perform the upgrade to thecurrent version.Note: If using lkbac
Upgrading SPSupgrades, LifeKeeper should not be started when a different version or release is resident and runningon another system in the cluster.36
Chapter 3: SteelEye LifeKeeper for LinuxIntroductionSteelEye LifeKeeper for Linux provides high availability clustering for up to 32 nodes with manysu
Set Up TTY Connections 62LifeKeeper Event Forwarding via SNMP 63Overview of LifeKeeper Event Forwarding via SNMP 63LifeKeeper Events Table 63Configuri
LifeKeeper CoreLifeKeeper CoreLifeKeeper Core is composed of four major components:l LifeKeeper Core Softwarel File System, Generic Application, Raw I
File System, Generic Application, IP and RAW I/O Recovery Kit Softwareindicates the server has failed.l LifeKeeper Alarm Interface - The LifeKeeper Al
LifeKeeper GUI SoftwareLifeKeeper GUI SoftwareThe LifeKeeper GUI is a client / server application developed using Java technology that provides agraph
Components Common to All LifeKeeper ConfigurationsLifeKeeper automatically manages the unlocking of the disks from the failed server and thelocking of
Active - Active GroupingIn an active/active group, all servers are active processors, but they also serve as the backup serverfor resource hierarchies
Active - Standby GroupingAppB and AppC, however, have several grouping options because all four servers have access to theAppB and AppC shared resourc
Intelligent Versus Automatic SwitchbackA standby server can provide backup for more than one active server. For example in the figureabove, Server 2 i
Logging With syslogl LifeKeeper never performs an automatic switchback from a higher priority server to a lowerpriority server.Logging With syslogBegi
Resource StatesResource StatesState MeaningIn-Service,Protected(ISP)Resource is operational. LifeKeeper local recovery operates normally. LifeKeeperin
Hierarchy RelationshipsHierarchy RelationshipsLifeKeeper allows you to create relationships between resource instances. The primary relationshipis a
How Certificates Are Used 74Using Your Own Certificates 74Linux Configuration 75Data Replication Configuration 78Network Configuration 79Application C
Resource Hierarchy InformationResource Hierarchy InformationThe resource status of each resource is displayed in the Detailed Status Display and the S
Resource Hierarchy ExampleResource Hierarchy ExampleDetailed Status DisplayThis topic describes the categories of information provided in the detailed
Detailed Status DisplaySHARED equivalency with "apache-home.fred" on "roadrunner", priority = 10FAILOVER ALLOWEDipeth0-172.17.104.
Resource Hierarchy Informationto machine=roadrunner type=TCP addresses=192.168.1.1/192.168.105.19state="DEAD" priority=2 #comm_downs=0LifeKe
Communication Status Informationl these resources are dependent.If present, indicates the tag names of all parent resourcesthat are directly depende
LifeKeeper Flagspath in the DEAD state, which initiates a failover event if there are no othercommunications paths marked ALIVE.l Remote system writer
Shutdown StrategylOther typical flags include !nofailover!machine, !notarmode!machine, and shutdown_switchover. The !nofailover!machineand !notarmode
Communication Status Informationresources within the hierarchy indented appropriately to indicate dependency relationships betweenresources.The BACKUP
Local Recovery Scenariowhen a particular interface fails on a server, the protected IP address can be made to function on thebackup interface, therefo
Resource Error Recovery ScenarioThis operation will fail if there is no backup interface configured for this instance. If the specifiedresource instan
SCSI Reservations 114Storage Fence Using SCSI Reservations 114Alternative Methods for I/O Fencing 115STONITH 115Using IPMI with STONITH 115Package Req
Resource Error Recovery Scenario1. lkcheck runs. By default, the lkcheck process runs once every two minutes. When lkcheckruns, it invokes the appropr
Server Failure Recovery Scenariodetermines whether the failing resource or a resource that depends upon the failing resourcehas any shared equivalenci
Server Failure Recovery ScenarioThe following steps describe the recovery scenario, illustrated above, if LifeKeeper marks allcommunications connectio
Installation and ConfigurationSPS for Linux InstallationFor complete installation instructions on installing the SPS for Linux software, seethe SPS f
Set Up TTY Connections5. Perform any of the following optional configuration tasks:l Set the Server Shutdown Strategyl Configure the manual failover c
LifeKeeper Event Forwarding via SNMPecho Helloworld | /opt/LifeKeeper/bin/portio -p port -b baudwhere:l baud is the same baud rate selected for Server
LifeKeeper Events TableLifeKeeper Event/DescriptionTrap#Object IDLifeKeeper Startup CompleteSent from a node when LifeKeeper is started on that node10
Configuring LifeKeeper Event ForwardingLifeKeeper Communications Path UpA communications path to a node has become operational140 .1.3.6.1.4.1.7359.1.
Verifying the Configuration1. Ensure that the snmptrap utility is available as noted above.2. Specify the network management node to which the SNMP tr
SNMP TroubleshootingSNMP TroubleshootingFollowing are some possible problems and solutions related to SNMP Event Forwarding. For specificerror message
Adding or Changing Credentials 125Listing Stored Credentials 125Removing Credentials for a Server 125Additional Information 125LifeKeeper API 126Netwo
LifeKeeper Events Generating EmailTo disable Email Notification, either run lk_confignotifyalias (See thelk_confignotifyalias(1M) man page for an exa
Configuring LifeKeeper Event Email NotificationLifeKeeperCommunications PathUpA communications path to a node has become operational.LifeKeeperCommuni
Disabling Event Email NotificationLifeKeeper log can be inspected to determine if there was a problem sending the emailmessage.SeeEmail Notification
Optional Configuration Tasksgenerate email notification messages.Also, see theOverview of LifeKeeper Event EmailNotificationto see if the LifeKeepe
Tuning the LifeKeeper HeartbeatDo Not Switch OverResources (default)LifeKeeper will not bring resources in service on a backup serverduring an orderly
ExampleImportant Note: The values for both tunables MUST be the SAME on all servers in the cluster.ExampleConsider a LifeKeeper cluster in which both
Using Custom Certificates with the SPS APILCMNUMHBEATS=2LifeKeeper will use a 1 second interval for the TCP communications path, and a 2 second interv
Linux ConfigurationLinux ConfigurationOperatingSystemThe default operating system must be installed to ensure that all required packagesare installed.
Linux ConfigurationKernelupdatesIn order to provide the highest level of availability for a LifeKeeper cluster, the kernelversion used on a system is
Linux ConfigurationDynamicdeviceadditionPrior to LifeKeeper startup, Linux must configure all devices. If a LifeKeeperprotected device is configured
Kommentare zu diesen Handbüchern