Anchor | ||||
---|---|---|---|---|
|
...
This command results in a list of all supported disk types.
Div | ||
---|---|---|
| ||
|
Choose the desired disk (for example "RZ22"), then use the "mkdskcmd" command to create the virtual disk image as shown below:
...
Div | ||
---|---|---|
| ||
|
Transferring disk images
The "mkdskcmd" utility is able to transfer (copy) disk images of one type to a disk image of another type.
...
<source disk file name> - a file name of the disk image to be transferred
<source disk parameters> - the name of the disk from the list of available on "mkdskcmd --list" request or the disk geometry specification (see below).
$ mkdskcmd --transfer /etc/rz22.vdisk rz25 |
$ mkdskcmd --transfer <source disk file name> -blsize <number> -blcount <number> |
$ mkdskcmd -t /etc/custom.vdisk -z 512 -c 262134 |
...
Div | ||
---|---|---|
| ||
|
"mtd" utility
The "mtd" utility is used to:
...
Run the utility without any options to display the license details.
...
Div | ||
---|---|---|
| ||
|
|
...
Run "hasp_srm_view" utility on the "RecipientHost" with the following parameters to collect the host ID info:
$ hasp_srm_view -idf
The "recipient.id" file will be created in the current directory.
Copy the "recipient.id" file to the "SourceHost".
Info "recipient.id" is an ASCII file, so use the "ascii" option for FTP transfer.
On the "SourceHost", open the "Sentinel Admin Control Center" (ACC) ( http://localhost:1947). Note the number of the software license you are going to transfer.
Run the "hasp_srm_view" utility in the following way to create a transfer license for the host "RecipientHost":
$ hasp_srm_view -tfr <license number> recipient.id
The "license number" is the value collected at the step 3.
Example of collecting a transfer license:
$ hasp_srm_view
-tfr 12345678
recipient.id
A "<license number>.v2c" file will be created in the current directory. In the example above, the name of the transfer license will be "12345678.v2c"
Copy the resulting "<license number>.v2c" file to the "RecipientHost".
Info "<license number>.v2c" is an ASCII file, so use the "ascii" option for FTP transfer.
On the "RecipientHost", open "Sentinel Admin Control Center" (ACC) (http://localhost:1947) and apply the "<license number>.v2c" file as described above.
...
Open "Sentinel Admin Control Center" (ACC) (http://localhost:1947). Note the number of the software license you are going to remove.
Run the "hasp_srm_view" utility in the following way to remove the license:
$ hasp_srm_view -tfr <license number>
The "license number" is the value collected at the step 1.
Example:
$ hasp_srm_view -tfr 12345678
The "<license number>.v2c" file will then be created in the current directory. In the example above the name of the transfer license will be "12345678.v2c"
It is always possible to re-apply the created ".v2c" file to restore the deleted software license.
Div | ||
---|---|---|
| ||
|
Anchor | ||||
---|---|---|---|---|
|
...
To invoke the "hasp_update" utility, login as "root" and use the following syntax:
# ./ hasp_update <option> [filename] |
...
Parameter | Value | Description |
---|---|---|
<option> | u | Updates a Sentinel protection key / attaches a detached license |
i | Retrieves Sentinel protection key information | |
d | Detaches a license from a Sentinel Software License (SL) key | |
r | Rehost a license from a Sentinel Software License (SL) key | |
h | Display help | |
[filename] | Path to the V2C/H2R file (in case of 'u'pdate/attach) | |
Path to the C2V file |
Example:
|
Info |
---|
We recommend to use this tool only for "Update a Sentinel protection key / attach a detached license" function ("u" option). For the rest use "hasp_srm_view" utility. |
...
The utility allocates chosen network interfaces (both physical and virtual) and configures the offload parameters.
Note |
---|
The NetworkManager service must be running in order to have all the functionalities enabled with "ncu". If the service is not enabled please configure the network using the manual operations described in the section "Manual configuration of CHARON networking" of the Installation chapter of this Guide. |
Dedication of a host physical interface to CHARON
...
|
Div | ||
---|---|---|
| ||
|
Now the interface "eth1" is dedicated to CHARON-VAX:
...
|
Div | ||
---|---|---|
| ||
|
Let's say that we want to return the interface "eth1" (currently dedicated to CHARON) back to host. To do that enter "R" or "r" then "eth1":
...
|
Div | ||
---|---|---|
| ||
|
Enter "B" or "b" to create a bridge between the host physical network adapter and the LINUX virtual network Interfaces (TAP) and specify the physical network interface ("eth1" in our example) and a number of the virtual network Interfaces to be created (2 in our example):
...
Div | ||
---|---|---|
| ||
|
Removal of a virtual network
...