|
Home > |
|---|
This section describes how to recognize and fix some problems that you could encounter.
On a system with two network connections, if pedserver attempts to use an IP address that is not accessible externally, then command lunacm:>ped connect can fail.
Here is an example:
This host computer is accessible through 192.20.10.175 and has an additional IP address 192.168.72.1 (that is not accessible).
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.20.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 172.20.10.175
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.20.10.10
Ethernet adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.72.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Command lunacm:> pedserver -m show returns
Ped Server Version 1.0.5 (10005)
Ped Server launched in status mode.
Server Information:
Hostname: noi1-502192
IP: 192.168.72.1
Firmware Version: 0.0.0-0
PedII Protocol Version: 0.0.0-0
Software Version: 1.0.5 (10005)
Ped2 Connection Status: Disconnected
Ped2 RPK Count 0
Ped2 RPK Serial Numbers (none)
Client Information: Not Available
Operating Information:
Server Port: 1503
External Server Interface: Yes
Admin Port: 1502
External Admin Interface: No
Server Up Time: 5 (secs)
Server Idle Time: 5 (secs) (100%)
Idle Timeout Value: 1800 (secs)
Current Connection Time: 0 (secs)
Current Connection Idle Time: 0 (secs)
Current Connection Total Idle Time: 0 (secs) (100%)
Total Connection Time: 0 (secs)
Total Connection Idle Time: 0 (secs) (100%)
1.Ensure that Pedserver is listening on the IP address that is accessible from outside.
2.If that condition (step 1) is not the case then disable the network connection on which Pedserver is listening.
3.Restart Pedserver and confirm that Pedserver is listening on the IP address that is accessible from outside.
If pedserver is running on a laptop that might change location, it can happen that the active network address changes, even though the laptop is not shutdown. An example might be if you unplugged from working at home, over the corporate VPN, commuted to the office, and reconnected the laptop there. The IP address that your laptop is assigned when joining directly to the office network would be different from the address that had been assigned by the VPN server.
In that situation, pedserver is still configured with the address you had while using the VPN.That pedserver session cannot work with the new address that is now assigned to your laptop. Running pedserver -mode stop does not completely clear all settings, so running pedserver -mode start again fails with a message like "Startup failed. : 0x0000303 RC_OPERATION_TIMED_OUT".
To resolve this problem,
1.Close the current Command Prompt window.
2.Open a new Command Prompt.
3.Verify the current IP address with command ipconfig
4.Run pedserver -mode start -ip <new-ip-address> -port <port-number> and it should now succeed.
The default timeout for a Remote PED link between PedClient at the HSM and PedServer at the Remote PED, is 1800 seconds, or 30 minutes. If no Remote PED activity is requested for the entire timeout duration, the link ends, and must be re-established. While that link is down, and the HSM remains set to expect Remote PED operation, any requested PED operations simply fail. We recommend performing a disconnect before performing a connect, to ensure that the old link is cleanly severed and that a new link is cleanly established.
The pedserver.exe process must be run using administrator privileges. If you forget and accidentally launch pedserver.exe in an ordinary, non-privileged-user command-prompt window, the pedserver fails to work, but the process is launched and continues in the background. If you then attempt to launch pedserver.exe from an Administrator command prompt, it fails with message "LOGGER_init failed". The logger is a necessary service for pedserver, and has failed to initialize for the new attempt because the earlier, non-functional instance of pedserver has locked the logger.
If pedserver fails with the message "LOGGER_init failed", proceed as follows:
1.Check that the pedserver process is not already running.
2.If it is, stop the process (to free the logger service).
3.Start the pedserver process again, as Administrator.