This section describes the environmental settings required for each admin server.
Communication between an admin server and a virtualization switch is performed using the Transmission Control Protocol (TCP) of Internet Protocol (IP). Therefore, you must modify the following system configuration files:
%SystemRoot%\system32\drivers\etc\hosts
%SystemRoot%\system32\drivers\etc\services
%SystemRoot%\system32\drivers\etc\hosts file
Register the host name and IP address of Ethernet port for virtualization switch control of a virtualization switch in the %SystemRoot%\system32\drivers\etc\hosts file.
A virtualization switch must have a host name beginning with "vsce" as the first four characters. This character string should be followed by a number from 1 to 128 in ascending order.
For a virtualization switch in a redundant LAN configuration, enter a representative IP address of Ethernet port for virtualization switch control specified for the virtualization switch.
Example
Example of coding in the %SystemRoot%\system32\drivers\etc\hosts file
The following shows an example of coding in the %SystemRoot%\system32\drivers\etc\hosts file for virtualization switches with IP addresses 192.168.1.2 and 192.168.1.3.
192.168.1.2 vsce1 # VS900 Model 300 No.1 192.168.1.3 vsce2 # VS900 Model 300 No.2
%SystemRoot%\system32\drivers\etc\services file
In the %SystemRoot%\system32\drivers\etc\services file, register a service name and a port number.
Register the following two services:
Service name | Port number | protocol |
|---|---|---|
ssvscme | 7420 | tcp |
The service name cannot be changed.
Port number 7420 can be changed if already used for another service. When doing so, change the port number specified in "VSCE_PORT" in the configuration data file and that for the virtualization switch. Specify a unique port number in the entire system of servers and peripheral devices.
Example
Example of coding in the %SystemRoot%\system32\drivers\etc\services file
The following shows an example of coding in the %SystemRoot%\system32\drivers\etc\services file.
ssvscme 7420/tcp # VSC Manager - VSC Engine(TCP) ssvscme 7420/udp # VSC Manager - VSC Engine(UDP)
Note that "$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\FJSVssvsc.ini" is the configuration data file.
($ENV_DIR means "Environment Directory" specified at the Manager installation.)
Also note that "$ENV_DIR\Manager\opt\FJSVssmgr\lib\sample\vsc\FJSVssvsc.ini.sample" contains samples of configuration data files.
# # All Rights Reserved, Copyright (c) Fujitsu Ltd. 2004 # # Storage Software Virtual Storage Conductor # # FJSVssvsc.ini: configuration file # ######################################################## LOG_LEVEL=4 COPY_HISTORY_ROTATE_NUMBER=2
If no configuration data file is created, the default values are assumed specified for all settings in the system.
Note
Modifying a configuration data file
A configuration data file cannot be modified while the Manager is running. Be sure to stop the Manager before modifying the configuration data file.
You can modify a configuration data file as follows:
Coding format
Coding of a configuration data file is shown as follows:
Enter one item per line. You cannot enter one item extending beyond one line or place more than one item on a line.
A line that begins with "#" in the first column is handled as a comment line.
Do not insert any character (such as a blank) between an item name and "=", or between "=" and a setting value.
Configuration items
The following table indicates the configuration item in a configuration data file.
Item | Item name | Outline of setting this item | Omission of item |
|---|---|---|---|
LOG_LEVEL | Log level | Specifies the output level of a message. | Possible |
COPY_HISTORY_ROTATE_NUMBER | Number of generations in the copy history | Specifies the number of generations retained in the copy history log file. | Possible |
Specify the error type of messages to be output.
Messages are output via syslogd(1M). Therefore, the settings in eventlog determine whether messages are actually output and to what file messages are output. For information on how to make settings in eventlog, see syslog.conf(4).
If this item is omitted, messages with error type "ERR" are output.
LOG_LEVEL={1 | 2 | 3 | 4}
1: Outputs messages for error type "ERR".
2: Outputs messages for error types "ERR" and "WARNING".
3: Outputs messages for error types "ERR", "WARNING", "NOTICE" and "INFO".
4: Outputs messages for error types "ERR", "WARNING", "NOTICE", "INFO" and "DEBUG".
Specifies the number of generations retained in the copy history log file.
The default number of generations is 2.
COPY_HISTORY_ROTATE_NUMBER={2|3|4|5}
Specify a value ranging from 2 to 5.
When you perform an operation on VSC Manager to modify the configuration information of virtual storage, VSC Manager executes a program or script to create a backup or copy of the virtual storage configuration information. This program or script is called a "Commit Script".
If the virtual storage configuration information is lost due for some reason, no virtual disk can be supplied to a transaction server. Even in case of such unexpected trouble, you must restore the virtual storage configuration information to resume operation. A commit script is intended to create a backup or copy of the virtual storage configuration information in case of any unexpected trouble.
Create a commit script in "$ENV_DIR\Manager\etc\opt\FJSVssmgr\current\VscCommitScript.bat" and give it an execution right.
Note that "$INS_DIR\Manager\opt\FJSVssmgr\lib\sample\vsc\VscCommitScript.bat.sample" contains samples of commit scripts.
Information
$INS_DIR means "Program Directory" specified at the Manager installation.
$ENV_DIR means "Environment Directory" specified at the Manager installation.
$TMP_DIR means "Work Directory" specified at the Manager installation.
Commit script sample
@echo off rem # rem # All Rights Reserved, Copyright (c) Fujitsu Ltd. 2006-2009 rem # rem # Storage Software Virtual Storage Conductor rem # rem # CommitScript Sample rem # rem ######################################################## setlocal set VARDIR=$TMP_DIR\Manager if not exist "%VARDIR%" goto fail set CURRENT_DIR=%VARDIR%\var\opt\FJSVssmgr\current set BKUP_DIR=vsclog\VSCCOMPOSE_BAK set COMPOSE_DIR=vsccompose set /a listflag=0 set /a delflag=0 set /a copyflag=0 cd "%CURRENT_DIR%" :: backup check if not exist "%BKUP_DIR%" mkdir "%BKUP_DIR%" if errorlevel 1 goto fail if not exist "%BKUP_DIR%\*.repository" goto allbackup :: commitlist check set COMMITLIST_DIR=commitlist set INSERT_UPDATE_FILE=%COMMITLIST_DIR%\addlist.vsc set DELETE_FILE=%COMMITLIST_DIR%\deletelist.vsc if not exist "%COMMITLIST_DIR%" goto allbackup if not exist "%COMMITLIST_DIR%\*.vsc" goto allbackup if exist "%INSERT_UPDATE_FILE%" (for %%F in ( %INSERT_UPDATE_FILE% ) do if not %%~zF==0 set /a listflag = 1 && set /a copyflag = 1) if exist "%DELETE_FILE%" (for %%F in ( %DELETE_FILE% ) do if not %%~zF==0 set /a listflag = 1 && set /a delflag = 1) if %listflag% == 0 (goto allbackup) else goto diffbackup :allbackup if exist "%BKUP_DIR%\*.repository" del "%BKUP_DIR%\*.repository" copy /y "%COMPOSE_DIR%\*.repository" "%BKUP_DIR%" > nul if errorlevel 1 goto fail if errorlevel 0 goto success :diffbackup if %delflag% == 1 (for /f "tokens=* delims=" %%F in ( %DELETE_FILE% ) do ((del "%BKUP_DIR%\%%F") & (if exist "%BKUP_DIR%\%%F" goto allbackup))) if %copyflag% == 1 (for /f "tokens=* delims=" %%F in ( %INSERT_UPDATE_FILE% ) do ((copy /y "%COMPOSE_DIR%\%%F" "%BKUP_DIR%" > nul) & (if errorlevel 1 goto allbackup))) :success if exist "%INSERT_UPDATE_FILE%" (del "%INSERT_UPDATE_FILE%") if exist "%DELETE_FILE%" (del "%DELETE_FILE%") echo "Backup Complete." exit 0 :fail echo "Backup failed." exit 1
Notes
The configuration information of VSC Manager is stored in the "$TMP_DIR\Manager\var\opt\FJSVssmgr\current\vsccompose" directory.
Backup all directories and files in this directory. When you restore the configuration information, restore directories and files in the same configuration as when backed up.
Note that a commit script may cause a delay in the processing time of VSC Manager depending on its coding, because the script always starts up whenever the resource status of virtual storage changes.
Do not change the coding in "$INS_DIR\Manager\opt\FJSVssmgr\lib\sample\vsc\VscCommitScript.bat.sample".
Precautions on use
If you do not make a commit script, message "ssvsc0906" is output and no commit script is executed. Therefore, no backup or copy of the virtual storage configuration information is created. Moreover, the virtual storage configuration information cannot be restored if lost for some reason.
If a commit script terminates abnormally for some reason, message "ssvsc0905", "ssvsc0907", or "ssvsc0908" is output. Take action as instructed by these messages and re-execute the commit script.
