eAuth keycode installation

[arunknair82]

Hello team,
We recently placed order for eAuth for IP aAuth User license and the distributor delivered the .key and .kcd file.
How this license is installed in the system. System is Release 7.5.

 

[Firebird Scrambler]

First of all I think you need to remove the external RMD from the active CPU and place the keycode.kcd file onto that RMD compact flash card in a folder called keycode.

Replace the RMD back into the slot on the CPU card.
Log into the system and then go to LD 143.
From there, you need to enter in the command

.KSHO REC to view the current keycode status.

To install the new keycode, I think the command is KNEW RMD

##############################################

KNEW dr Select new candidate keycode from: parm. Depending on
eligibility, the keycode may be instantly activated or activated
on next reset. Instant activation is supported if the new ISM limit
is greater than or equal to the actual ISM usage in the system.
Otherwise, the keycode activation is blocked.
Where parm has one of the following values:
PIV and CP PM CPU only
• RMD - candidate keycode on Removable Media Device
• FMD - candidate keycode created by means of KMAN/KUPL
PII CPU only
• F0 or F1 - keycode on the floppy drive on Core 1 or Core 0
• HD - candidate keycode hard drive
If the system instantly activates the New Keycode, the following
message prints:

###########################################

It's been a few years since I last did this.


Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[Wanebo]

Properly stage Keycode file on the removable media
For release 6.0 or later use the following procedure
Transfer/save the Keycode file to your desktop PC on a known location on the C: drive. You will need to know the path that the file is saved at in further steps.
Open up a Windows command window by using Start, then Run, and type in CMD and click OK.
In the resulting command window change to your C: drive and the location of the file (in this example it is in the C:\Keycode) and verify that the file is present.
FTP to the PBX using the command line, starting in the folder that the patch file resides. FTP {pbx name}. Use your username and password for UCM PBX’s and admin1 or admin 2 for others as required to log in. Note: Always try admin1 before using admin2.
Once an FTP session has been established change directory to the compact flash media by using the CD /CF2/KEYCODE command. Print the directory contents by issuing the DIR command. Rename the keycode.kcd file that is there to keycode.old. (if there is more than one delete the .old one first).
Transfer the file from your computer to the PBX by using the PUT {filename} command. In this example the Keycode file that we want is currently called D11499_20111206_115015_keycode.kcd therefore the command we issue is PUT D11499_20111206_115015_keycode.kcd.
The file is now staged and ready for loading when needed. You may now issue the QUIT command to end the FTP session, and then exit out of the command window.

Login to the PBX and go to overlay 143 (LD 143).
Compare the difference in the currently loaded Keycode file and the new file by issuing the KDIF REC RMD command.
It will show you what you have and what you’re getting. This is important because once installed, that is what you have or don’t have. This command is just a print out. If you like what you see go to next command.
Load the new Keycode by issuing the KNEW RMD command.
This is where you will be informed if a sysload is needed or not for the new ISM’s to take effect.

If required perform a sysload after the above commands have finished running. <insert sysload procedure>
Verify installation
Go to overlay 22 (LD 22) and issue the SLT command. Verify that the new Keycode properly loaded by inspecting the license numbers.

 

[bignose21]

Also when you do the KDIF pay particular attention to the differences in Licences (make sure they are all the same or larger on the new keycode) and the packages (Make sure none are being removed).

I have had it a few times where they say add you IP Licence and you see the extra amount, but when you look at the packages for no reason at all they just remove one. In that case you obviously just get back onto them and get it re cut.

As Wanebo says

new keycode goes in /cf2/keycode
LD143
KDIF REC RMD
KNEW RMD

If a Sysload is required you dont have to do it there and then you can schedule but new licence would not be available until you do it. Usually if its increase in licence a sysload is not required, if it is moving from 0 or a new package it asks for a sysload (not always though )