It is assumed that most of the Finance Institutes already work together with a System Integrator providing IBASEC specific integration and configuration services.

Only the Ethernet network adapter eth0 (labeled 1) is configured according to your information in the order form.

The Ethernet network adapter eth1 (labeled 2) is not initialized but may be used for administration purposes. Please ask your service provider for further information or ask for our IBASEC specific Services.

PED keys have no PIN. Just press the <Enter> button on the PED if you are asked to enter a PIN.

Please ask your service provider if you want to protect your PED key with a PIN. You may ask for our IBASEC specific Services.

There might be several problems in conjunction with the following error:

C_Initialize returns 0x30 [see example]

This problem occurs if the Luna SP appliance is out of sync. To fix this problem please login into the secure shell (SSH) and perform the following commands [as textfile] :

spadmin halt all
spconfig lunaSP hsm
spconfig lunaSP network
spconfig partition cachePassword <PIN from PIN Letter>
spadmin start webService

The IBASEC Premium Rollout settings remain. See also #12.

You always get the following warning when you execute a Luna SP command in the secure shell (SSH):

Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location [see example]

This warning occurs since the Java Virtual Machine runs in a jailed environment. You can simply ignore it.

There are two possibilites on how to handle a damaged Luna SP HSM, PED or Backup Token device without Premium Support.

IMPORTANT new processing as to the initial setting of the Admin and the Partition Password according to this PIN letter (Premium Rollout):

Please note that the Use Case 11 (Connect a new HSM with "Premium Rollout") differs from the last User Manual version 2.3 published on March 26, 2007. The updated Use Case is now available in the most recent User Manual version 2.4 from April 30, 2007. It can be downloaded here.

Login via the serial console (not via secure shell (SSH)) and perform the following commands [as textfile]:

spadmin halt all
network interface device eth0 ip <IP HSM>
        gateway <IP Gateway> netmask <IP Netmask> force
service restart syslog force
service restart network force
sysconf regenCert force
service restart ntls force
spconfig lunaSP hsm
spconfig lunaSP network
spconfig partition cachePassword <PIN from PIN Letter>
spadmin start webService

The IBASEC Premium Rollout settings remain. See also #12.

Login via the serial console or via secure shell (SSH) and perform the following command:

sp getversion

The result looks like this.

The PIN Entry Device (PED) used at IBASEC (Luna SP) is the same as used at SWIFT (Luna IS). It is not bound to a specific Luna HSM and can be used by either system.

Note: The IBASEC Hardware is provided under special contract conditions. The use of any hardware parts such as the PIN Entry Device (PED) for non IBASEC purpose may violate the contract.

The Luna SA front-panel LCD provides system status summary information which are explained in this PDF document (Extract from Luna SP 2.0 Product Documentation, Copyright 2006 SafeNet, Inc.).

The status summary can be either read of the display or by entering the following command in the console (ssh or serial):

status sysstat show

The result looks like this.

A flashing backlight on the Luna SA front-panel may indicate a problem. Please check the system state (#14)  and perform the following commands (ssh or serial).

hsm information reset
hsm information show

The result looks like this. Please contact your service provider if the problem remains.

Normally all the Luna SP specific log files can be downloaded using the functionality of IBASEC server. But there might be some circumstances where the log files have to be downloaded manually.

Follow this guideline if you have to download the log files manually.