I have obtained a new licence file for our RDzUT installation and am now trying to update the USB token. SecureUpdateUtility fails, however: Could not update license.

Some further diagnostic data:
suse:/home/ibmsys1/licence # netstat -a | grep 945
tcp 0 0 *:9450 : LISTEN
udp 0 0 *:9450 :
suse:/home/ibmsys1/licence # ps -ef | grep usbdaemon
root 1319 1 0 12:42 ? 00:00:00 /opt/safenet_sentinel/common_files/sentinel_usb_daemon/usbdaemon
root 6939 5632 0 13:21 pts/0 00:00:00 grep usbdaemon
suse:/home/ibmsys1/licence # ps -ef | grep SntlKeysSrvr
daemon 2455 1 0 12:42 ? 00:00:02 ./SntlKeysSrvrlnx
root 6949 5632 0 13:22 pts/0 00:00:00 grep SntlKeysSrvr

suse:/home/ibmsys1/licence # z1090ver
IBM System z Personal Development Tool (zPDT)
Licensed Materials - Property of IBM
5799-ADE
(C) Copyright IBM Corp. 2007 All Rights Reserved.

z1090, version 1-2.41.21, build date - 05/10/10 for Linux on SuSE 64bit
I ran strace on the tool. It is sending and receiving to /var/run/sentinel/u.daemon multiple times before failing, incrementing a number.
bind(4, {sa_family=AF_FILE, path="/tmp/u.MGzBM5"}, 15) = 0
sendto(4, "\v\315\0\0\260\0\0\0\0\0\0\0\0\0\0\0\4\0\"\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4272, 0, {sa_family=AF_FILE, path="/var/run/sentinel/u.daemon"}, 110) = 4272
select(5, [4], NULL, NULL, {5, 0}) = 1 (in [4], left {4, 999303})
recvfrom(4, "\v\315\0\0\344;\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\24\0\0\0"..., 4352, 0, {sa_family=AF_FILE, path="/var/run/sentinel/u.daemon"}, 29) = 4352
close(4) = 0

Running SecureUpdateTool with the old license file gives the same error.

You are very down level on zPDT level. What level of RDz-UT are you running? Please send output of SecureUpdateUtlity command.

RDzJohn

Here's the output from SecureUpdateUtility:
suse:/home/ibmsys1/licence # SecureUpdateUtility -u RDzUT-1B70B-201311062359-L03.upw

---

Secure Update Utility
Sentinel Keys 1.0.3
Copyright (C) 2007 SafeNet Inc. All rights reserved.

---

Could not update license!

Hello,

Not sure which userid you attempted to perform the SecureUpdate. Please try
su - # switch to root
cd /usr/z1090/bin # change directory to where the z1091 executables are installed
./SecureUpdateUtility -u <path_to_your_update_file>/RDzUT-1B70B-201311062359-L03.upw

I look forward to hearing of your results.
Keith

Hi,

I was already running SecureUpdate as root. I had temporarily added /usr/z1090/bin to the PATH.

I tried cwd'ing to /usr/z1090/bin like you described, but that didn't change anything.

Hi,

FYI: drivers released in the last year, REQUIRE SecureUpdateUtility to be executed from the /usr/z1090/bin directory with the ROOT id. This is required due to a code change by our token supplier.

I am guessing you are using RDZ_z1090-1-2.41.21.x86_64, a very old driver. Please correct me if I am wrong. This driver does not require you to be root and does not require you to execute from the /usr/z1090/bin directory. (obviously you need your paths to point to it)

I just used 41.21 and pulled a token request file using SecureUpdateUtility . This worked fine. But I do not have a token update file I can try.

My understanding is that for RDzUT, you go to a Web site to request a token update file. I have seen a problem where the characters on the token are hard to read ("D" look like "0" and vice versa, and "B" and "8" are also easily misunderstood.) So please check that on your input to the website. I see your token number is 1B70B which might be suspect.

The next series of debug question are: where did you get the update file ? Was that from the Rational License Key Center ? Did you transfer the file in binary to your Linux machine? Has the machine ever run z1090 / RDZ_z1090 ? Can you get a higher level driver from RDzDT ?

Can you try capturing the return code from the SecureUpdateUtility command by issuing command : echo $? immediately after you run the SecureUpdate ?

If nothing becomes clear, we will need to get the RDzDT folks to investigate: Whether the token or the token update could be defective.

I spoke with the RDzDT team and I understand you are already talking with them. If nothing above helps,
then we will have them contact you directly.

Regards,
Keith

Hi,

I can't find the installation media that we used to install RDzUT, but it has been in use at our location for over two years now, so it could well be an old version.

I have now generated a token update file using the Rational License Key Center. The filename is consistent with the filename of the previous token update file that I installed last year without problems. The serial number is encoded in the filename and matches the old filename. I rechecked with the token, and the serial number is correct. If I use SecureUpdateUtility with last year's token update file, it gives me the same error message, by the way.

I transferred the file to the SuSE server using scp, after downloading it directly from the Rational License Key Center, so no binary/text conversion either.

Here is the return code from SecureUpdateUtility:

[/usr/z1090/bin]% ./SecureUpdateUtility -u /home/ls/RDzUT-1B70B-201311090533-3.upw ; echo $?

---

Secure Update Utility
Sentinel Keys 1.0.3
Copyright (C) 2007 SafeNet Inc. All rights reserved.

---

Could not update license!
0

I will try to upgrade our RDzUT to 8.5 and use the new SecureUpdateUtility.

Hello,

I think it wise to upgrade your zPDT to the 8.5 version.
Is this a new machine ? Has zPDT ever run on this machine? What is the Linux distribution and version ?
Please run /usr/z1090/bin/z1090installcheck and report on any "BAD" findings.

Thanks,
Keith

Alright, now I've installed z1091_850-1-3.43.20.x86_64.

This is the result of running the new SecureUpdateUtility:

[/usr/z1090/bin]% ./SecureUpdateUtility -u /home/ls/RDzUT-1B70B-201311090533-3.upw ; echo $?

---

Secure Update Utility
Sentinel Keys 1.3.1
Copyright (C) 2009 SafeNet Inc. All rights reserved.

---

Unit not found!
0

I tried pulling the USB dongle and plugging it in again. I also tried rebooting the Linux server. The sentinel server processes are running.

We've been running zPDT on this machine for more than two years. I've already installed an update token last year, the filename contained the same serial number as the recent one. The Linux is openSUSE 11.3.

When I start zPDT, I get an error message saying that the licence has expired, giving me the exact day and time the licence expired. That means that the USB dongle is working, right?

Here is the output from z1090instcheck:

[/usr/z1090/bin]% ./z1090instcheck

Checking zPDT prerequisites ....

For more information about this script, issue : z1090instcheck -?

1. SUSE os level at 11.3 which is
greater the minimum level OK
2. SUSE kernel.shmmax of 18000000000 is greater than min. NOTE
shmmax should be greater than 1.1 times the sum
of z memory (as specified in your devmap) for
ALL your 1090 instances.
3. SUSE (kernel.shmall * PAGE_SIZE) is 206158430208
which is greater/equal to kernel.shmmax which is OK
4. SUSE kernel.msgmni is 512 which is OK
5. SUSE kernel.msgmax is 65536 which is OK
6. SUSE kernel.msgmnb is 65536 which is OK
7. SUSE net.core.rmem_default is 1048576 which is OK
8. SUSE net.core.rmem_max is 1048576 which is OK
9. SUSE kernel.core_uses_pid is 1 which is OK
10. SUSE kernel.core_pattern is core-%e-%p-%t which is OK
11. SUSE ulimited -c is not set to unlimited : = 0 BAD
12. SUSE ulimited -d is set to unlimited OK
13. SUSE rpm libstdc++45-32bit-(x86_64) is installed OK
14. SUSE sntl-sud-7.5.2-0.i386 rpm is greater than required OK
15. SUSE zpdt-shk-server-1.3.1.2-0.i586 rpm is equal to required level OK
16. SUSE dmidecode-2.10-7.1.x86_64 rpm is greater than required OK
17. SUSE rpm beagle is not installed which is OK
18. SUSE rpm zmd is not installed which is OK
Running uimcheck ...

The UIM client is configured in local mode.

UIMCHECK: serial number entry not yet added to local data base.
UIMCHECK: No local errors

thank you for the update. "Unit not found" - let's see that Linux sees the token.
execute: "lsusb | grep Rain" ... Linux sees the token coming from "Rainbow Technologies, Inc"

Are you run natively on the machine or are you running from a Virtual machine ?
Regards,

Keith

Here's the output you wanted:

[~]% lsusb | grep Rain
Bus 004 Device 002: ID 04b9:8000 Rainbow Technologies, Inc.

So it looks like Linux sees the token.

Linux is running natively on that machine, it's a PC with 8GB RAM.

Good morning Lars. From the serial number you gave, it appears that the token may not be from the RDzUT (or RDT) product but rather from a different origin. If the USB token has a metal loop and a tag attached then it is not an RDz UT/RDT token and you will need to get a new update file from the supplier of the key, most likely IBM ResourceLink or a business partner that supplied the token. Please let us know if the key has a metal loop and tag attached.

Hi,

I will overtake from Lars...
And yes: our token has a metal loop and a tag attached.
Is this good or bad news for us?

Cheers,
Ingo

That means you have a zPDT key, not an RD&T/RDz UT key. How did you order the key? You should have ordered it via the PassPort Advantage physical media order tool.

Thanks for clarification. We suggest, we got the key from our IBM responsible... I have already contacted him and see what happens... Will keep you informed

zPDT USB keys (with metal loop and tag) are the ISV-only offering of the technology (https://www-304.ibm.com/partnerworld/wps/servlet/ContentHandler/pw_com_zpdt).

zPDT uses much of the same technology as RD&T/RDzUT, but follows a different ordering, licensing, and fulfillment process.

Hi, together, the problem is solved!
A new RD&T USB Token from our IBM representative leads to access.
License generation worked. - Our Z is up and running again!

Thanks for help!