Product User Guide

Intel® Remote Management Module 2 User Guide 29
The example below shows you the output of the test all command on an Intel
®
RMM2 module with
no remote connections:
C:\Program Files\KiraTool>kiratool -l 192.168.2.5 –a -u admin -p
password test all
device: ok (firmware 4.2.0, Build 5359)
Could not query DDC from device: Self test not supported
ddc info: error
video status: failed
IPMB BMC status test failed: Self test not supported
ipmb bmc: error
FML ESB2 status test failed: Self test not supported
fml esb2: error
usb status: failed
nic status: ok (link: up, duplex: full, speed: 100 MBit)
4.2.6 Test Types
Here is a more detailed listing of the available tests.
Note: the tests are organized in a hierarchical fashion. If you exclude a top-level test like –s nic
from the testing then ALL of the nic tests will be skipped! Conversely if you specify a top-level test
to be done, then all of the available sub-tests will be executed.
• video <subtest> - tests video interface (digital video input and output)
status – checks detected video signal and resolution
crc – calculate CRC sum over the captured screen
• ddc <subtest> – test DDC interface
info – queries EDID information from the device and compares it to the EDID
information known by the OS (only available under Windows)
• ipmb <subtest> – test IPMB interface
bmc – test whether a BMC responds over IPMB
evalboard – test whether the IPMB connection between two evaluation boards work
• fml <subtest> – test FML interface
esb2 – test whether an ESB2 is responding on FML when TPT (TCP PassThrough)
is active
evalboard – test whether the FML connection between two evaluation boards work
• usb <subtest> – test USB interface
status – test whether the device's USB module is enumerated
• nic <subtest> – tests network interface
status – test NIC status and parameters
loopback – test NIC loopback functionality
• ping <host> – Test whether pinging a host works