This file is saved at the following location as a detailed setting file of the storage management:
Platform of Manager | Location |
|---|---|
Windows | $ENV_DIR\ESC\Manager\etc\opt\FJSVssmgr\current\sanma.conf |
Solaris OS, | /etc/opt/FJSVssmgr/current/sanma.conf |
Reflecting the contents of the setting file
If the setting file is changed, execute re-read definition file by using the Web Console, or reactivate the Manager. This reflects the settings on this software.
Customization
Note
Note that the memory or the disk capacity may become insufficient when the number of generations or the maximum capacity of each log file is increased. Operation may stop when the memory or the disk capacity becomes insufficient.
Note when changing the number of generations or maximum capacity, secure the memory capacity and the disk capacity.
Specify the address of a subnet searched during an automatic device search. Use a "," (comma) to define multiple subnets.
Example: AUTODISCOVER_SUBNET="10.12.13.255,133.134.13.255";
The Management Server issues SNMP broadcasts for automatic device detection in these subnets, but if the broadcast is limited by network settings, this function is not enabled.
If the Management Server is clustered system which has physical IPs and logical IP, logical IP address must be specified in this parameter. For this parameter, specify only IPv4 format IP address.
Example: LOGICAL_MANAGER_IP="10.12.13.14";
This parameter is used to automatically configure a SNMP Trap send destination address for a fault monitoring device when adding devices. Refer to "5.2.5 SNMP Trap transmission place automatic setting function" for more information.
If the Management Server is clustered system which has physical IPs and logical IP, logical IP address must be specified in this parameter. For this parameter, specify only IPv6 format IP address.
Example: LOGICAL_MANAGER_V6IP="2001:db8::2:1";
This parameter is used to automatically configure a SNMP Trap send destination address for a fault monitoring device when adding devices. Refer to "5.2.5 SNMP Trap transmission place automatic setting function" for more information.
This is specified if device detection and registration fail due to the environment having the Management Server which holds multiple IP addresses.
If specifying this parameter in a cluster environment, be sure to specify a logical IP address at the beginning.
For this parameter, specify only IPv4 format IP address.
Example: MANAGER_LAN_CARD_IP="10.12.13.14,100.101.102.103";
This is specified if device detection and registration fail due to the environment having the Management Server which holds multiple IP addresses.
If specifying this parameter in a cluster environment, be sure to specify a logical IP address at the beginning.
For this parameter, specify only IPv6 format IP address.
Example: MANAGER_LAN_CARD_V6IP="2001:db8::2:1,2001:db8::2:2";
When an access path is set, if the zoning setting for the Fibre Channel switch need not be added because port zoning is set, this software does not generally set zoning for Fibre Channel. Specifying 1 in this parameter sets one-to-one WWPN zoning even in the above case (excluding cases in the No Security state):
Example: SET_SW_ZONING_ALWAYS=1; (Default: 0)
Specify whether the SNMP Trap (Cold Start Trap etc.) common to devices from a device is indicated in the event log. Setting 1 for this parameter indicates the SNMP Trap common to devices. Setting 0 for this parameter does not indicate it. Default is 1 (indicate).
Example: DISPLAY_ SNMP_STANDARD_EVENT = 0;
This specifies the name of the SNMP Community used when this software communicates with devices using SNMP protocol. However, if the Community names being used are "public" (Read-direction) and "private" (Write-direction), filling in this parameter is not necessary.
Specify the IP address of the device and the community name used for SNMP communication with the device, delimiting them with a space.
Note that a community name that includes space characters cannot be set in this parameter.
When setting "abc" as the community name used for SNMP communication with IP address 10.11.12.13, set as follows:
Example: SNMP_COMMUNITY_NAME_FOR_IP="10.11.12.13 abc";
Wild card definitions in which "*" is used at the end of the IP address is permitted. However, for IPv6 address, a wild card using "*" cannot be defined.
Example: SNMP_COMMUNITY_NAME_FOR_IP="10.11.12.* abc"; SNMP_COMMUNITY_NAME_FOR_IP="20.21.*.* def"; SNMP_COMMUNITY_NAME_FOR_IP="30.*.*.* ghi";
To define community names for multiple devices, specify the names on as many definition lines as the number of devices.
Example: SNMP_COMMUNITY_NAME_FOR_IP="10.11.12.13 abc"; SNMP_COMMUNITY_NAME_FOR_IP="10.11.14.15 def";
If community names must be different in the READ-direction and WRITE-direction of SNMP communication, specify a device IP address, community name used for READ-direction, and community name used for WRITE-direction, delimiting them with a space.
When setting "abc" as the READ-direction community name and "def" as the WRITE-direction community name used for SNMP communication with IP address 10.11.12.13, set as follows:
Example: SNMP_COMMUNITY_NAME_FOR_IP="10.11.12.13 abc def";
Using the SNMP protocol, the Intra-subnet device detection function detects devices. If "public" is used as the SNMP community name, it is unnecessary to specify this parameter. When a SNMP community name other than "public" is used, specify the name in this parameter. When specifying this parameter, be sure to specify SNMP_COMMUNITY_NAME_FOR_IP.
Note that a community name that includes space characters cannot be set in this parameter.
When community name is "abc," set as follows:
Example: SNMP_COMMUNITY_NAME_FOR_AUTODISCOVER="abc";
In an environment where each device has a unique community name, not all devices can be detected even if the parameter is specified. In this case, specify only SNMP_COMMUNITY_NAME_FOR_IP to search for one device at a time.
The number of generations of log files (log.* and event.*) of the whole storage management is specified by an arbitrary decimal number. Default is two. It circulates in the second generation (log.0 and log.1 or event.0 and event.1), when 2 is set.
Example for circulating in the fifth generation: LOG_CYCLE = 5;
Platform of Manager | Location |
|---|---|
Windows | $TMP_DIR\ESC\Manager\var\opt\FJSVssmgr\current |
Solaris OS, | /var/opt/FJSVssmgr/current |
The maximum capacity of the log file (log.* and event.*) of the whole storage management is specified within the range of 0-2147483647 (KB). Default capacity is 1024(KB). When 0 is specified, the log is not output. Moreover, when the value is specified outside the range, it becomes a default value.
Example for setting the maximum capacity to 2MB: LOG_MAX_SIZE = 2048;
Refer to "LOG_CYCLE" for location of the log files.
The number of generations of log files (snmpth.*) related to SNMP Trap is specified by an arbitrary decimal number.
Default is 2.
It circulates in the second generation (snmpth.0 and snmpth.1), when 2 is set.
Example for circulating in the fifth generation: SNMPTH_LOG_COUNT = 5;
Refer to "LOG_CYCLE" for location of the log files.
The maximum capacity of the log file (snmpth.*) related to SNMP Trap is specified within the range of 0-2147483647 (KB).
Default capacity is 1024 (KB).
When 0 is specified, the log is not output. Moreover, when the value is specified outside the range, it becomes a default value.
Example for setting the maximum capacity to 2MB: SNMPTH_LOG_LIMIT = 2048;
Refer to "LOG_CYCLE" for location of the log files.
Any "Unsupported Firmware Version" message output to the event log indicates that a device with firmware not supported by ETERNUS SF Storage Cruiser has been detected. This message is output at the time of an operation.
To suppress output of the message, make the following setting:
FIRMWARE_VERSION_CHECK = 0;
Since new firmware can be supported by applying certain patches to ETERNUS SF Storage Cruiser, be sure to delete this setting after applying the patches.
In consideration of incompatibility of Fibre Channel switch firmware, if unsupported firmware is detected, all functions including the configuration management functions are restricted. Normally, in such cases, patches need to be applied to ETERNUS SF Storage Cruiser. However, when such firmware has no incompatibility, it can be handled without applying patches.
Note
Make this setting only for firmware that is confirmed to have no incompatibility.
The procedure for upgrading firmware is described in the firmware upgrade manual.
If it is impossible to confirm that firmware has no incompatibility, contact your Fujitsu CE or SE.
For example, to handle the firmware that has no incompatibility and whose version is v12.34.56a, make settings as follows.
First, change each of the three numeric values in firmware version v12.34.56a to a two-digit value in hexadecimal notation.
Characters such as the first "v" and the last "a" need not be considered.
12 -> 0C 34 -> 22 56 -> 38
Then, these three two-digit values are concatenated to produce a six-digit value in hexadecimal notation.
0C2238
Specify this value as follows:
SILKWORM_SUPPORTED_FIRMWARE_VERSION = "0C2238";
When specifying multiple versions, delimit them with a comma ",".
To specify both v2.4.1 and v5.0.1, describe them as follows:
SILKWORM_SUPPORTED_FIRMWARE_VERSION = "020401,050001";
The hyphen "-" can be used to specify a range of version.
To specify versions v4.0.0 to v4.2.2, describe them as shown below. Be sure to describe the smaller version number first.
SILKWORM_SUPPORTED_FIRMWARE_VERSION = "040000-040202";
Also, the above description methods can be combined.
SILKWORM_SUPPORTED_FIRMWARE_VERSION = "020401,040000-040202,050001";
