This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Translation agency/company employee or owner, Verified site user
Data security
This person has a SecurePRO™ card. Because this person is not a ProZ.com Plus subscriber, to view his or her SecurePRO™ card you must be a ProZ.com Business member or Plus subscriber.
English to Japanese: Translation English to Japanese
Source text - English
Solaris Client
1, p.63
In step one, eith the /kernel/drv/st.conf file to support the tape device.
Please add some notes:
NOTE: These must be added on the top line(s) of the st.conf file.
NAS
NAS-1, p.84
The ¡°Add NFS Client dialog¡± has changed. Please use the updated screen shot below.
NAS-2, p.87
In the second line:
"You cannot use blanks or the following characters in the Resource name: < > " & $/\' ()%#:;|*?". Also the screen shot is changed to include this message
should be:
"You cannot use blanks or the following characters in the Resource name: < > " & $/\'()%# :;|*?`"
NAS-3, p.88
Quota Manager Dialog. Please add the following information:
The default Hard Limit and Soft Limit are zero, which stands for no limit.
SNMP Integration
SNMP-1, p.140
Traps (Fault management) area list all the IPStor components that we can monitor. But it should be mentioned that When "NAS option is Enabled , we can monitor the NAS components from the
list, otherwise, there is no NAS components to monitor.
SNMP-2, p.141
The line between the last two rows of the graph seems to be too thick.
SNMP-3, p.141
About the "Event Log message".
By default, all Event Log messages (informational, warnings, errors, and critical errors) will *NOT* be sent.
SNMP-4, p.143
Please add a Note here:
NOTE: The default SNMP Get community (read-only community, public community) is "public". And the default SNMP Set community (read-write community, private community) is "falcon".
SNMP-5 p.143-144, and 146-148
In the section ¡°configuration¡±, we are setting the trap from HP Openview (or CA Unicenter). But actually, there is a parameter in the Server¡¯s snmp configation file to be checked for this trap setting.
In the Server, in file /usr/local/ipstor/etc/snmp/snmpd.conf, a line com2sec falconRW
The HP Openview mchine must reside in the IP subnetwork (address/netmask) specified in this line as to setup the trap definition in the IPStor Server.
SNMP-6, p.145
Please add a Note here :
NOTE: The blank in the community field is assumed the read-only right.
SNMP-7 p.145, and 149
Please add a Note in the statistic query part:
NOTE: Since the cache refresh mechanism, whenever there is a change in configuration (add a SAN Resource, delete a SAN Client ¡), it may take up to 20 seconds for the SNMP manager¡¯s query to take effect.
REPLICATION
P. 155
Please add another NOTE after first NOTE in the 1st step of Setup:
If you are replicating a NAS Resource , you must have the same GID of group NASGRP on both the promary and the target servers. If the GID of the group NASGRP are different, it does not function when you promote the replica in the target server to a NAS Resource.
SECURITY
P. 177
Disable ports. The only ports required by the IPStor Server are:
11762 ¨C Client port. The Console uses this port to communicate with the Client.
It is pretty confusing whey Console is using port 11762 to communicate with the Client but this is IPStor Server. I do not know if we want to address that there is a ¡°Local Client¡± here. And will the IPStor SAN Client machine need to disable the port 11762 ? Do we need to add information in the Manage IPStor SAN Client part that we need to disable port 11762?
NAS
NAS-1.
Please add the following in page-4:
5. While doning the SnapCopy of a NAS resource, the console should be opend until the completion of SnapCopy process. If the time is too long and console encounters a timeout, you need to use the command line to attach and mount the NAS resource manually.
NOTE: Terry will also check with Frank and Tat about these kind of problems, and they may respond to you as well.
SNMP
SNMP-1.
Please add the following for the SNMP part.
When you install the IPStor Server, the original SNMP agent will be stopped and replaced by the SNMP daemon in the IPStor Server. This SNMP daemon will be started automatically. To manually stop the daemon, in the IPStor Server machine:
# /usr/local/ipstor/bin/ipstorsnmpd stop
If the SNMP daemon is stopped, there may be problems when we query the server information from SNMP manager machine.
IPStor SAN Client for Solaris
P. 5
It says that a new virtual device needs to be labeled. Since local SCSI disk needs not be labelled (only our assigned SAN resource needs to be labelled), I would suggest in putting the labelling method in the Release Note or User Gide. As I recalled, the labelling method was put into the knowledge base, please verify.
P. 5
There is some limitation in the Virtual Device size for Solaris Client. We claimed that each virtual device can be of 2TB. For Solaris Client, it can be only 256GB.
NAS
NAS-1.
If we have two NFS shares in the IPSTor NAS Server, the mounting path of each is /nas/VirtulaDisk-10/NFSShare1 and /nas/VirtulaDisk-10/NFSShare1/ShareX respectively. If they are assigned assigned to the same NFS Clients, but with different permissions. The IPStor NFS server will give the NFS Clients the permission on the first directory, that is, the permission with the upper level file system tree.
This result is according to the design of NFS protocol. The IETF RFC1094 describes the detail.
Some system, such as Turbo Linux, has a better way to address this issue. If we do the command "showmount -e " in the NFS client, the result only shows the upper level share and hide another invalid mountpoint.
English to Japanese: English to Japanese Technical
Source text - English
Solaris Client
1, p.63
In step one, eith the /kernel/drv/st.conf file to support the tape device.
Please add some notes:
NOTE: These must be added on the top line(s) of the st.conf file.
NAS
NAS-1, p.84
The gAdd NFS Client dialogh has changed. Please use the updated screen shot below.
NAS-2, p.87
In the second line:
"You cannot use blanks or the following characters in the Resource name: < > " & $/\' ()%#:;|*?". Also the screen shot is changed to include this message
should be:
"You cannot use blanks or the following characters in the Resource name: < > " & $/\'()%# :;|*?`"
Keywords: Japanese Translation Agency, Japanese to English Translation India, Japanese to Engiish. English to Japanese, Localization. All language translation Agency, J to E, E to J, Indian agency, Cheap translation Japanese, Software localization, Web localization. See more.Japanese Translation Agency, Japanese to English Translation India, Japanese to Engiish. English to Japanese, Localization. All language translation Agency, J to E, E to J, Indian agency, Cheap translation Japanese, Software localization, Web localization, IT translation . See less.
