ISO8859-1; 2 QG H O\P$;/3>!r,NFKWM19#:];* O!8o"U#<$Y ;%@ &Z 'A 1(? s)0 *= +6 ",G Y-6 .> /C 00 [1% 2^ 3] 4Y o5J 6,7A8)P9;z:C;F<HA=L>E??@C]AGB*C4DFIK)A8Hi c!:O 79 &8Q"o  !  !)<%  bl3J;   G . /! Validating TSM server Smart Assist application id TSM server smart assist Application id=%1$s is not in the rage [a-z][A-z][0-9]_. completion of validating TSM server Smart Assist for applicaton id=%1$s Validating TSM server Nodes TSM server smart assist has primary=%1$s and takeover nodes=%2$s as repetitive completion of validating TSM server Smart Assist nodes primary=%1$s amd takeover nodes=%2$s Modify the TSM server instace=%1$s Checking if the TSM server instance is already configured. TSM server instance=%1$s is already configured TSM server instance=%1$s is not already configured Adding TSM server instance=%1$s Unable to get the unused name for %1$s=%2$s To find if the VG's are already defined to PowerHA SystemMirror configuration Checking the Volume Group=%1$s in PowerHA SystemMirror configuration Volume Group=%1$s is already defined in PowerHA SystemMirror configuration service label %1$s already defined in the PowerHA SystemMirror configuration TSM server instance user id %1$s is not created TSM server directory volume group %1$s can not be varied TSM instance directory %1$s is not on shared volume group TSM user home directory %1$s is not on shared volume group 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 server instance Resource Group %1$s to PowerHA SystemMirror configuration Failed while adding TSM server instance Resource Group %1$s Adding TSM server instance Application server %1$s to PowerHA SystemMirror configuration Failed while adding TSM server instance Application server %1$s Adding TSM server instance Application monitor %1$s to PowerHA SystemMirror configuration Failed while adding TSM server instance Application monitor %1$s Failed while modifying TSM server instance Resource Group %1$s Adding TSM server instance configuration to ODM Failed while Adding TSM server instance configuration to ODM Generating verify script for TSM server instance %1$s Generating verify Header for TSM server instance Application name %1$s Generating verify Script for TSM server instance %1$s Pushing the verification scripts to other node %1$s is failed Failed while Generating verify script for TSM server instance %1$s Removing TSM server instance Resource Group ... Resource Group %1$s not found in ODM Failed while deleting Application monitor %1$s for changing TSM server instance configuration Failed while deleting Application servers for changing TSM server instance configuration%1$s Failed while deleting Resource Group %1$s for changing TSM server instance configuration Failed while deleting ODMs for changing TSM server instance configuration TSM server instance %1$s is stopped at %2$s TSM_6.1_SERVERModifying TSM server Resource Group %1$s configuring TSM server Instance using manual configuration No value is specified for Instance property in TSM server xml file No value is specified for PrimaryNode property in TSM server xml file No value is specified for TakeoverNodes property in TSM server xml file No value is specified for InstanceDirectory property in TSM server xml file No value is specified for ServiceIPs property in TSM server xml file No value is specified for User property in TSM server xml file No value is specified for Password property in TSM server xml file No value is specified for VolumeGroups property in TSM server xml file No entry for service IP in /etc/host file Failed to set the TSM server password for user %1$s Invalid password, failed to set the TSM server password for user %1$s starting the TSM server instance %1$s with instance directory %2$s at %3$s Stoping TSM server instance %1$s at %2$s The PID %1$s of the stopped dsmserv for TSM server instance %2$s Starting monitoring of TSM server instance %1$s at %2$s dsmserv deamon is not running with PID %1$s present in dsmserv.v6lock file, for TSM server instance %2$s Monitoring is failed while querying TSM server connection information for TSM server instance %1$s TSM server instance %1$s is monitored sucessfully at %2$s Select the TSM server instance to make highly availableAdd a TSM server Highly Available Instance Resource GroupApplication NameTSM instance Owning NodeTake over Node(s)TSM server Instance NameTSM server Instance DirectoryShared VGs for TSM server instanceService IP LabelNetmask(IPv4)/Prefix Length(IPv6)TSM server Administrator user idTSM server Administrator passwordSelect a TSM server InstanceModify a TSM server Highly Available Instance Resource GroupAdd a TSM server Highly Available Instance Resource Group SMIT panel configures TSM server instance in a active-standby configuration. The following information must be provided for each added instance * Application Name * Primary Node and Takeover Node(s) * TSM server Instance Name to Make Highly Available * TSM server Instance Directory to Monitor * Shared VGs for TSM server instance * Service IP label * TSM server user id and password TSM server instance will be selected through selctor screen. Specify the name for the collection of PowerHA SystemMirror component that represent TSM server 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 server. This is the lowest priority node in order that can own the resource group that the TSM server configuration Assistant will create. Leave a space between node names. This is the lowest priority node in order that can own the resource group that the TSM server configuration Assistant will create. Leave a space between node names. TSM server instance directory will be the directory where the TSM instance logs will be kept; this directory should be present in shared disk Shared VGs are the VGs in which the TSM servers log and configuration information is stored. The different VGs which contain Database volumes, Recovery log volumes, Storage pool volumes, Instance directory and Instance user directory. The VGs specified must be different for different TSM server instances. Specify the service IP label to be used by the TSM server instance. The TSM server instance 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 server user id which is used for monitoring server instance. TSM admin can setup a user id and password for PowerHA SystemMirror, with a limited authority. TSM server password which is used for monitoring server instance. TSM admin can setup a user id and password for PowerHA SystemMirror, with a limited authority. Modify a TSM server Highly Available Instance Resource Group SMIT panel modifies TSM server instance in a active-standby configuration. TSM server user id which is used for monitoring server instance. TSM admin can setup a user id and password for PowerHA SystemMirror, with a limited authority. Users will be asked to provide the password in next screen.