patch 1 for sp1 installation problem on IMSA

1. Did the client already update the IMSA for SP1 prior to patch 1?
2. If yes and this happens, we need to ask the client to collect some logs to analyze
a. Connect the pc to IMSA to the CLI (command line) via SSH
b. Go to $IMSA_Home/cdt
c. Open the cdt.ini and check SilentMode=1 is set to zero "0"
bash-3.0# cd /opt/trend/imss/cdt
bash-3.0# vi cdt.ini
d. Save the changes and run it. bash-3.0# ./cdt
e. Select All Events and once the CDT is running, replicate the patch installation.
f. Once the issue occurs, allow CDT to continue running for about 5 mins more. Afterwards, stop CDT and collect the CDT logs. Move the CDT*.zip to /tmp folder and using UI console, export the logs/CDT. Otherwise, you can try the following to move the logs out from the IMSA.

Transferring files to / from IMSA

=======
Using FTP
=======
Use the ncftp FTP client to access the external FTP servers (in our case you can upload it here ftp.trend.com.au; user: xxxx and pass: yyyy) and exchange files. The command-line arguments must include username, password and the port number if it is not 21:

bash-3.00# ncftp -u -p -P 2121 10.13.130.253 NcFTP 3.1.9 (Mar 24, 2005) by Mike Gleason (http://www.NcFTP.com/contact/).
Connecting to 10.13.130.253...
transfer Microsoft FTP Service (Version 5.0).
Logging in...
User training logged in.
Logged in to 10.13.130.253.
ncftp / >

Example:

bash-3.00# cd /tmp
bash-3.00# ncftp -u xxxx -p yyyyy ftp.trend.com.au NcFTP 3.1.9 (Mar 24, 2005) by Mike Gleason (http://www.NcFTP.com/contact/).
Connecting to ...
transfer Microsoft FTP Service (Version 5.0).
Logging in...
User training logged in.
Logged in.
ncftp / >cd _asiasupport/upload/logs/1-1-271644771
ncftp > put


=======
Using the NFS Client
=======
Using the NFS client from the shell allows one to set up a remote filesystem to which files can be copied:

mount -t nfs -o nolock 10.13.9.186:/data /mnt

Note: Since there is no locking daemon available on IMSA, you have to tell the mount command to not use locking.

These files can then be accessed from non-IMSA devices (Linux, Windows, etc.) that have an NFS client. In other words, in windows machine, create a folder and have it shared (Everyone with Read & Write). Example. I have a machine 10.0.0.1 and I created IMSA folder and shared it so if I access it using windows, it is like: \\10.0.0.1\imsa