User Manual
If you do not explicitly restore hardware access when the maintenance operation is completed, the
driver restart will NOT do so. The driver will come back after restart with hardware access dis-
abled. Note, though, that the SMP firewall will still be active.
Rev 2.3-1.0.1
Mellanox Technologies
125
A host reboot will restore hardware access (with SMP firewall active). Thus, when you disable
hardware access, you should restore it immediately after maintenance has been completed, either
by using the flint command above or by rebooting the host (or both).
3.2.4.1.2 Burning New Firmware when Secure-Mode is Active
To burn a new firmware when the secure-mode is active:
Step 1. Temporarily enable the hardware access (see section Enabling/Disabling hardware access).
Step 2. Burn the new firmware.
Step 3. Reboot the host (not just restart the driver).
3.2.4.1.3 Permanently Disabling Secure-Mode
To permanently disabled Secure-mode by setting the pass-key to zero:
Step 1. Temporarily disable the secure-mode (see section “Enabling/Disabling Hardware Access”
on page 124).
Step 2. Reset the pass-key to zero.
flint -d <device> set_key 0
Step 3. Reboot the host.
This operation will cause the HCA to always come up (even from host reboot) in unsecured
mode.
To restore security, simply set a non-zero pass-key again.
3.2.4.1.4 Checking if Hardware Access is Active
To check if hardware access is active:
flint -d /dev/mst/mt26428_pci_cr0 -qq q
If the hardware access is active, you will see the following error message:
E- Cannot open /dev/mst/mt26428_pci_cr0: HW access is disabled on the device.
E- Run "flint -d /dev/mst/mt26428_pci_cr0 hw_access enable" in order to enable HW access.
3.2.4.1.5 Checking if the SMP Firewall is Active
The SMP firewall is active as long as there is a non-zero pass-key active in the firmware (regard-
less of whether or not the Secure-Mode has been temporarily disabled).
To check if SMP Firewall is active, run the InfiniBand diagnostic command sminfo.
If the SMP firewall is active, the command will fail as shown below:
[root@dev-l-vrt-016 ~]# sminfo
ibwarn: [26872] mad_rpc: _do_madrpc failed; dport (Lid 1)
sminfo: iberror: failed: query