ISO8859-1A 2, P_ H lfO\)02Z7;%,'6TfFk9M* O >8 L !3 "T H#; $U %< /&_ l'F (G )) [*6 +R ,s -' .4 /; 0>1H[293A4% 5F6be7[8U$9Tz:P;A <`b=M>e?w@o A|B_C2aDFEHFJ$GEoH>IFJ*;( !f .$q >N!q"/##/$0S)#*!+.,'-4!.&V/3}0%122$ 31/4$a516:G%H&I$@J#eK#L QRrS?_TrU0V0CW3tX3Y4Z5[6G 1~91$V!g ! "/)<  ;!l"#(#&' *H *+'C+R.+Validating TSM client Smart Assist application id TSM client smart assist Application id=%1$s is not in the rage [a-z][A-z][0-9]_ completion of validating TSM client Smart Assist for applicaton id=%1$s TSM HSM client is not installed on the nodes %1$s but it is selected for PowerHA SystemMirror configuration Validating TSM client Nodes TSM client smart assist has primary=%1$s and takeover nodes=%2$s as repetitive completion of validating TSM client Smart Assist nodes primary=%1$s amd takeover nodes=%2$s Modify the TSM client configuration=%1$s Checking if the TSM client is already configured. TSM client with application %1$s is already configured TSM client with application %1$s is not already configured Adding TSM client configuration %1$s Unable to get the unused name for %1$s=%2$s File system %1$s specified is not a valid file system This function checks to see if the VG's are already defined to the PowerHA SystemMirror configuration Checking the Volume Group=%1$s in PowerHA SystemMirror configuration Volume Group=%1$s is already defined in PowerHA SystemMirror configuration so removing from client VG list service label %1$s already defined in the PowerHA SystemMirror configuration Service IP label %1$s can not be resolved creating Service IP label %1$s No suitable PowerHA SystemMirror network is defined to create service IP label Error while adding service IP label %1$s to netowk %2$s Adding TSM client Resource Group %1$s to PowerHA SystemMirror configuration Failed while adding TSM client Resource Group %1$s Adding TSM HSM client Application client %1$s to PowerHA SystemMirror configuration Failed while adding TSM HSM client Application client %1$s Adding TSM HSM client Application monitor %1$s to PowerHA SystemMirror configuration Failed while adding TSM HSM client Application monitor %1$s Adding TSM backup archive client Application client %1$s to PowerHA SystemMirror configuration Failed while adding TSM backup archive client Application client %1$s Failed while adding TSM backup archive client Application monitor %1$s Modifying TSM client Resource Group %1$s Failed while modifying TSM client Resource Group %1$s Failed while Adding parent /child dependencies for TSM client Resource Group %1$s Failed while adding location dependency (for TSM client Resource Group %1$s) of "online on same node" dependency. "Adding TSM client configuration to ODM Failed while Adding TSM client configuration to ODM Generating verify script for TSM client configuration %1$s Pushing the verification scripts to other node %1$s is failed Failed while Generating verify script for TSM client configuration %1$s Pushing the dsm.sys scripts to other node %1$s is failed Removing TSM client %1$s from PowerHA SystemMirror configuration Resource Group %1$s not found in ODM DEPENDENT_RG not found in ODM Failed while Removing online on same node dependency between the client RG %1$s and other RGs%2$s Failed while Removing parent/child dependency between the client RG %1$s and other RGs%2$s Failed while deleting Application monitor %1$s for changing TSM client configuration Failed while deleting Application clients for changing TSM client configuration%1$s Failed while deleting Resource Group %1$s for changing TSM client configuration Failed while deleting ODMs for changing TSM client configuration Adding TSM backup archive client Application monitor %1$s to PowerHA SystemMirror configuration dsm.sys file is not present in the default TSM client installation directory The resource Groups %1$s on which the VGs already configured are not having same participating nodes Failed while deleting the TSM client Resource group %1$s when the volume group defined to TSM client is already present in the other Resource group Failed while adding TSM client Resource Group %1$s when the Volume group is shared between the Resource groups Failed while modifying TSM client Resource Group %1$s while adding the remaining vgs that are not present in other Resource groups Failed while modifying TSM client Resource Group %1$s while adding service IP and application configuring TSM client using manual configuration No value is specified for PrimaryNode property in TSM client xml file No value is specified for TakeoverNodes property in TSM client xml file No value is specified for ConfigDirectory property in TSM client xml file No value is specified for ServiceIPs property in TSM client xml file No value is specified for Hsm property in TSM clinet xml file No value is specified for FileSystems property in TSM clinet xml file No entry for service IP in /etc/host file starting BA client deamon dsmcad Failed while starting BA client deamon dsmcad stoping the BA client deamon dsmcad Failed while monitoring BA client dsm.sys file is changed; need to start the client again to reflect the changes Failed while monitoring BA client, wrong dsm.sys is mentioned Failed while monitoring BA client dsm.opt file is changed; need to start the client again to reflect the changes Failed while monitoring BA client dsm.opt file Monitoring BA client deamon dsmcad Failed while monitoring BA client deamon dsmcad starting BA and HSM client deamons starting BA client deamon dsmcad Failed while starting BA client deamon dsmcad starting HSM client deamon dsmmonitord Failed while starting HSM client deamon dsmmonitord starting HSM client deamon dsmrecalld Failed while starting HSM client deamon dsmrecalld starting HSM client deamon dsmscoutd Failed while starting HSM client deamon dsmscoutd starting HSM client deamon dsmrootd Failed while starting HSM client deamon dsmrootd starting HSM client deamon hsmagent Failed while starting HSM client deamon hsmagent Failed while reactivating filesystem %1$s for HSM client stoping HSM client deamon dsmrecalld stoping HSM client deamon dsmmonitord stoping HSM client deamon dsmscoutd stoping HSM client deamon dsmrootd stoping HSM client deamon hsmagent stoping BA client deamon dsmcad monitoring HSM and BA client Failed while monitoring HSM client dsm.sys file is changed; need to start the client again to reflect the changes Failed while monitoring HSM client, wrong dsm.sys is mentioned Failed while monitoring HSM client dsm.opt file is changed; need to start the client again to reflect the changes Failed while monitoring HSM client dsm.opt file Failed while monitoring BA client deamon dsmcad Failed while monitoring HSM client deamon hsmagent Failed while monitoring HSM client deamon dsmrootd Failed while monitoring HSM client deamon dsmscoutd Failed while monitoring HSM client deamon dsmrecalld Failed while monitoring HSM client deamon dsmmonitord Enter the TSM client configuration file DirectoryAdd a TSM client Highly Available Instance Resource GroupApplication NameTSM client Owning NodeTake over Node(s)shared file systems of the client to be backed upService IP LabelNetmask(IPv4)/Prefix Length(IPv6)TSM Space Management (HSM) clientTSM client configuration directoryEnter TSM client shared configuration directoryModify a TSM client Highly Available Instance Resource GroupAdd a TSM client Highly Available Instance Resource Group SMIT panel configures TSM client in a active-standby configuration. The following information must be provided for each added TSM client * Application Name * Primary Node and Takeover Node(s) * shared file systems of the client to be backed up * Service IP label * Netmask(IPv4)/Prefix Length(IPv6) * TSM Space Management(HSM) client Specify the name for the collection of PowerHA SystemMirror component that represent TSM client component. The name is limited to 64 characters and cannot contain spaces. This is the highest priority node that can own the resource group created by Smart Assist for TSM client. This is the lowest priority node in order that can own the resource group that the TSM client configuration Assistant will create. Leave a space between node names. File systems list will be taken from dsm.opt file to get client backup file systems. These file systems will be highly available. The VGs on which the file systems will reside will be highly available. If the VG is already configured in other Resource group like application Resource group then the VG will not be included in the Resource group created by smart assist for TSM client. If the VGs are not configured on other Resource group then TSM client smart assist will configure the VGs in the Resource group created by smart assist for TSM client. If in later stages PowerHA SystemMirror administrator wants to use the VG specified for TSM client for the application then care to be taken on dependencies between the Resource groups by smart assist for TSM client and application. Specify the service IP label to be used by the TSM client. The TSM client will be accessed on the service IP label. The service IP label must be defined in the /etc/hosts file on all cluster nodes. Enter the netmask in range [1-32] or as /X.X.X.X/, where X in [0-255] for IPv4 service IP, or enter prefix length in range [1-128] for IPv6 service IP. Please follow below for more information. a. With IPv4 service IP and underlying network IPv6, netmask is must. b. With IPv6 serivice IP and underlying network IPv4, prefix length is must. c. With service IP and underlying network both are IPv4, netmask can be blank,however, netmask will not be considered even though specified. d. With service IP and underlying network both are IPv6, prefix length can be blank, and however, prefix length will not be considered even though specified TSM space management client list yes or no. If y is selected then TSM Space management will be configured along with TSM client, if n is selected the TSM space management will not be configured along with TSM client TSM client shared configuration directory Enter the TSM client shared directory where dsm.opt file is stored Modify a TSM client Highly Available Instance Resource Group SMIT panel modifies TSM client in a active-standby configuration.