Intel vPro® Platform
Intel Manageability Forum for Intel® EMA, AMT, SCS & Manageability Commander
2834 Discussions

How to use imrcli?

idata
Employee
1,838 Views

Hello.

I had to download Intel(R)_AMT_SDK_6.0_Hot_Fix_2450.

The sdk to my Linux system was extracted.

I'm trying to use is the imrcli.

Intel(R)_AMT_SDK_6.0_Hot_Fix_2450/Linux/Intel_AMT/Samples/Redirection/RedirectionSample/imrcli does not work.

After reading the README files listed in there, I've had to make.

But the behavior did not imrcli.

How to use imrcli?

The Linux server is an IP XX.XX.XX.230 and the other one is XX.XX.XX.230 VPRO server IP.

I have a Linux server tries to use IDE_R vpro server.(Remote from the ISO image installation)

I've been using the following command.

↓↓↓↓

 

**************************

[root@Test1 RedirectionSample]# ./imrcli

 

Redirection Console Sample Application version 1.0.1.54

 

Copyright (C) Intel Corporation, 2003 - 2009

Client List

 

ID Address/Name Type

 

------------------------------------

 

0. XX.XX.XX.230 TCP

Options:

 

a. Add Client

 

b. Delete All Clients

 

c. Set TLS Certificates

 

x. Exit

Choose an option or a client ID> 0

Handling Client XX.XX.XX.230

 

IDER Session Closed

Options:

 

a. Delete Client

 

b. Open SOL Session

 

c. Open IDER Session

 

x. Exit

Choose an option> b

 

Enter user name: admin

 

Enter password:

 

Configure proxy settings? [Yes|No] No

 

Error: Open SOL Session: Socket Error

Handling Client XX.XX.XX.230

 

IDER Session Closed

Options:

 

a. Delete Client

 

b. Open SOL Session

 

c. Open IDER Session

 

x. Exit

Choose an option>

************************

0 Kudos
4 Replies
Jacob_G_Intel
Employee
554 Views

You message says you have the same IP address on the linux server as on the vpro system. I assume it's a typo, but just to be sure, the IPs need to be different. Other than that, it looks like you're using imrcli correctly. The error means that imrcli can't connect to the redirection service running in AMT. This could happen for a number of reasons. Generally I'd start be ensuring you have network connectivity. Can you ping your vPro system? Can you get to AMT's WebUI? In case you don't know, AMT has it's own web service. If you're not using TLS you can reach it here: http://<AMT http:// IP>:16992. If you are are using TLS it's here: https://<AMT https:// IP>:16993. If you can not ping there's a basic network issue. If you can not get to the WebUI AMT may not be setup/configured or may have a different IP (or no IP) than the OS running on your vPro system.

If both of those work, then AMT is accessible and ready for use. However, its possible that Redirection is disabled or that there's a TLS cert issue. These are more complicated to advise on without more information. What AMT version are you using? How did you setup/configure AMT? Are you using static IP's or DHCP? Is there a firewall on or between these systems?

On thing to check: Be sure SOL, IDER, and the Redirection Listener (which is only listed in AMT 6's MEBx) are all enabled in MEBx.

idata
Employee
554 Views

We have a similar problem.

Manageability commander in windows is working fine, so AMT and addresses etc are set up correctly.

We use the same AMT SDK as the topic starter, and most tools work, for example remoteControl can remotely manage the machine and power up with IDE-Redirection ** when the image is mapped in the windows commander **.

However we'd like to use imrcli to handle the redirection. imrcli works fine with SOL and displays the bootup. With IDE redirection, it displays a lot of packets being received and sent, but the "data counter" is zero and the machine waits at the "Attempting remote IDE boot..." prompt.

We've tried strace'ing the process, enabling debugging etc but no avail. We've also updated AMT from 3.2.3 to 3.2.20 (dell optiplex 755, bios A17), but no difference. We have tried AMT SDK 5.1.1, but no difference.

And help would be greatly appreciated!

BR,

Stefan

0 Kudos
idata
Employee
554 Views

Ok, problem solved. It turns out that the [/dev/cdrom] cannot point directly to an iso-file. However, with a loop device redirection it works:

losetup -f disc.iso

mount /dev/loop0 /mnt/cdrom (the manual says it must be mounted)

and then /dev/loop0 is used as the cdrom device.

HTH.

0 Kudos
Jacob_G_Intel
Employee
554 Views

Thank you for sharing your solution...I just learned something!!!

0 Kudos
Reply