IMSCLI / ISREST Server Log Collection

This guide translates the stored source’s IMSCLI/ISREST workflow. Its downloads are from the V7.5/V7.3 era, while the screenshots span several older releases. Use the executable names, paths and options supported by the package you actually download.

The vendor’s live article has since added newer V7.7 examples using imscli. The historical screenshots below use isrest; do not mix the two release-specific instructions. Check the current official guide for the matching release.

1. Download the tool

Direct download links from the source

• IMSCLI-Linux-V7.5.0-202506301430.tar.gz.zip — the Linux local-collection workflow in section 3.1.
• IMSCLI-Linux-aarch64-V7.3.0.0-202406301046.tar.gz.zip — ARM/aarch64 version listed by the source.
• ISREST-Linux-V6.2.0-202305171730.tar.gz.zip — the source’s legacy package for systems such as RHEL 6 and Ubuntu 14.
• IMSCLI-Windows-V7.5.0-202506301430.zip — the Windows-based BMC/black-box collection workflow in section 3.2.

These are source-era package choices, not a compatibility guarantee for every OS release. The download responses were checked against all four filenames during translation review.

Download through the official REPO portal

Open the official REPO sign-in page. Sign in with your account, or register if needed. The source illustrates entering a user name and email, obtaining a verification code, then setting and confirming a password:

After signing in, verify a server serial number through Account Settings → Security Settings → Verify Serial Number. The source states that the InManage Server CLI software entry does not appear before verification:

After verification, open Software → InManage Server CLI and download the required package:

2. Before collection

The original vendor source recommends closing antivirus software to avoid interference. Treat this as a source troubleshooting recommendation, not a universal prerequisite. If endpoint protection blocks the tool, use the approved exception or support procedure for the affected environment.

3. Collect logs

3.1 Local Linux system logs

The source’s preparation example names IMSCLI-Linux-V7.3.0.0-202406301630.tar.gz.zip; its terminal screenshots use IMSCLI-Linux-V7.3.2.1-202410290900.tar.gz. Filenames and extracted directories vary. If the download ends in .tar.gz.zip, first extract the outer ZIP on a workstation to obtain the TAR.GZ package.

1. Upload the TAR.GZ package to a directory on the target Linux server. Use ls to confirm it is present.

2. Extract the actual package. The source example is:

tar -zxf IMSCLI-Linux-V7.3.2.1-202410290900.tar.gz

3. List the extracted directory and enter it. The source’s directory is IMSCLI-Linux-V7.3.

4. Enter bin and confirm that the isrest script exists. The source uses ll; use ls -l if that alias is unavailable.

5. Run the local collection with root privileges. The letters L and C are uppercase:

./isrest osLogCollect

6. When collection finishes, use the output path printed by the tool to locate the resulting .tar.gz archive. The source example uses /root/IMSCLI-Linux-V7.3/logs.

7. Copy the generated archive from the server and provide it to the support engineer through the agreed transfer method. The source describes sending it as an email attachment.

openEuler example: tar is unavailable

The source shows tar: command not found. Its workaround is to extract the package on a workstation and upload the extracted directory:

The source then illustrates the following broad permission change before continuing from step 3:

# Historical source workaround; not a routine permission requirement.
chmod 777 -R IMSCLI-Linux-V7.3

That command grants access to the whole directory. Check the required ownership and executable permissions for the installed package and follow the approved support procedure instead of applying this permission change automatically. The source’s subsequent collection example is retained below:

3.2 Windows collection interface

The source describes single-host or batch collection of BMC/black-box data and supported OS logs. For BMC collection, the workstation must reach the server’s management interface; for remote OS collection it must reach the OS network interface. The pictured release supports remote Linux OS collection and local Windows system-log collection.

1. Extract the compatible Windows package into a path without Chinese characters. Open the tool directory and launch LogCollect.

2. Select the required mode: BMC Log Collection, Remote System Log Collection or Local System Log Collection.

3. The source’s example selects Local System Log Collection, then Add Host.

4. Choose the required log level. The example selects Basic Logs and leaves the optional save path empty, using the default logs directory. Click OK. Other collection modes require their corresponding host and credential settings.

5. Click Start Collection and monitor the result. The screenshot shows 0% and pre-processing; wait for successful completion.

6. Find the generated package in the configured output path, normally the tool’s logs directory, and provide it to support.

3.3 Linux command-line reference from the source

The examples below use the source’s isrest executable. Run its matching package and check that release’s help. Option prefixes have been normalized to ASCII hyphens; -L and -F are single-hyphen options. Angle-bracket values are placeholders.

Single-server BMC collection

./isrest -H HOST -U USERNAME -P PASSWORD bmcLogCollect [-L LEVEL] [-F FILEPATH]

• HOST: server BMC address.
• USERNAME and PASSWORD: configured BMC credentials.
• LEVEL: optional; 1 collects basic logs by default, 2 adds register logs. The source reserves register collection for specific support-directed diagnostic cases.
• FILEPATH: optional output directory; otherwise use the tool’s default logs directory.

./isrest -H 192.168.1.100 -U <BMCUser> -P <BMCPassword> bmcLogCollect
./isrest -H 192.168.1.100 -U <BMCUser> -P <BMCPassword> bmcLogCollect -F /home/logsdir

Batch BMC collection

./isrest bmcLogCollectBatch [-F FILEURL]

FILEURL is the batch configuration file. Create the source’s example file logcollect_config.txt, with one host per line:

-H 192.168.1.100 -U <BMCUser1> -P <BMCPassword1> -F /home/logsdir
-H 192.168.1.101 -U <BMCUser2> -P <BMCPassword2>

Then run:

./isrest bmcLogCollectBatch -F logcollect_config.txt

Local OS collection

./isrest osLogCollect [-F FILEPATH] [-L LEVEL]

For OS collection, level 1 is basic logs and level 2 adds debug logs. Use level 2 for the specific diagnostics requested by support. -F selects an output path; if omitted, use the tool’s default logs directory.

Single remote OS collection

./isrest -H HOST -U USERNAME -P PASSWORD osLogCollect [-F FILEPATH] [-L LEVEL]

Use the target OS address and configured OS credentials. The source’s examples use a root account:

./isrest -H 192.168.1.100 -U root -P <OSPassword> osLogCollect
./isrest -H 192.168.1.100 -U root -P <OSPassword> osLogCollect -F /home/logsdir

Batch OS collection

./isrest osLogCollectBatch [-F FILEURL]

Use a configuration file with the corresponding OS host details, one per line:

-H 192.168.1.100 -U root -P <OSPassword1> -F /home/logsdir
-H 192.168.1.101 -U root -P <OSPassword2>

./isrest osLogCollectBatch -F ./logcollect_config.txt

The source’s illustrative password values have been replaced with placeholders. Use the credentials configured on the target; the example addresses, package names and screenshot values are not settings to apply to an unrelated system.