Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: NetworManager note is added

Anchor
TopUtilPage
TopUtilPage

...

UtilityDescription
mkdskcmd

Used to create CHARON virtual disk containers of custom or standard types.

This utility also may be used to transfer virtual disks of one type to virtual disks of another type.

hasp_srm_view

Used to display the CHARON license contents, to collect the host system fingerprint and to transfer software licenses from one host to another.

hasp_update

Sentinel standard utility used to retrieve Sentinel protection key information, detache a license from a Sentinel SL key and rehost a license from a Sentinel SL key

ncu

Used to dedicate a host interface to CHARON-VAX, to release it back to the host and to manage CHARON virtual interfaces (TAPs).

mtd

Used to create CHARON tape images from physical tapes and to write tape images back to physical tapes.

All these utilities are invoked from Linux console command line.

...

$ mkdskcmd --disk rz22 --output rz22.vdisk

A disk container "rz22.vdisk" will be created in the current directory.

Info

A file "rz22.avdisk" will also be created. This file helps CHARON accurately recognize a specific disk image type. It is recommended to put the ".avdisk" file in the same directory as the created disk image.

...

mkdisk for CHARON utility v. 1.14
Copyright: STROMASYS, 2015

Usage:
mkdskcmd [Options]

Options:
--help - to see help screen
-h - to see help screen

--output <full name> - to specify output file name
-o <full name> - to specify output file name

--disk <disk name> - to specify the disk name from Disk table
-d <disk name> - to specify the disk name from Disk table

--blsize <number> - to specify the block size in bytes (custom disk image)
-z <number> - to specify the block size in bytes (custom disk image)

--blcount <number> - to specify number of the blocks (custom disk image)
-c <number> - to specify number of the blocks (custom disk image)

--avtable <full_name> - to specify AVDISK table file
-a <full_name> - to specify AVDISK table file

-t - please see the '--transform' options description
--transform <source_disk_name> <source_disk_params> - to transform the the disk image (change actual size)
<source_disk_name> - the file name of the disk image to be transformed
<source_disk_params> - the name of the disk from the list of available at the Disk table
The source disk size will changed accordingly the reach the specified parameters.
To specify the transform parameters manually, follow the option below:
--transform <source_disk_name> --blsize <number> --blcount <number>

--shrink - parameter which needs to be EXPLICITLY provided, if the disk size is to be decreased
-k - parameter which needs to be EXPLICITLY provided, if the disk size is to be decreased

--list <full_name> - to display AVDISK table
-l <full_name> - to display AVDISK table

--silent - silent mode running
-s - silent mode running

Return value:
0 - for Success
Non zero - in case of failure

Examples:
mkdskcmd -h
mkdskcmd -l
mkdskcmd -a /opt/charon/utils/mkdsk.vtable -o /etc/rk07.vdisk -d rk07
mkdskcmd -o /etc/custom.vdisk -z 512 -c 16384
mkdskcmd -t /etc/rz22.vdisk rz25 -a /opt/charon/utils/mkdsk.vtable
mkdskcmd -t /etc/rz22.vdisk rz25 -a /opt/charon/utils/mkdsk.vtable -z 512 -c 262134

The "--avtable" parameter is used to work with an alternative disk specification database (or to point to the standard database ("mkdsk.vtable") if it is in a location other than the current directory).

The "--blcount" (blocks count) and "--blsize" (blocks size) switches are used to create custom disk images.

Back to Table of Contents

...

Info

If a source disk image is larger than the target disk image, the extra data is lost. If the source disk image is smaller, it will be extended and padded with null bytes ('\0').

An example of the syntax follows:

$ mkdskcmd --transfer <source disk file name> <source disk parameters> [--shrink] [-k]

...

  • <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).

  • --shrink or -k - used in the case when the target disk is transferred to a smaller disk.

Example:

$ mkdskcmd --transfer /etc/rz22.vdisk rz25

It is also possible to specify the disk parameters manually with "--blcount / -c" (blocks count) and "--blsize / -z" (blocks size) switches:

$ mkdskcmd --transfer <source disk file name> -blsize <number> -blcount <number>

Example:

$ mkdskcmd -t /etc/custom.vdisk -z 512 -c 262134

...

$ mtd [options] <tape device name> <tape container name>


Div
classpagebreak

 

where the options are:

 

ParameterDescription
-l <file name>

Creates an execution log “file name”.

-r <number>Specifies a number of attempts to read a damaged data bock
-i

Directs to ignore bad blocks and continue processing w/o interruption. It implies "-r 0"

-nDo not rewind tape
-pDisable progress reporting
-v

Enable verbose trace of data transfer (implies "-p")

Example:

$ mtd -l tape1.txt -r 10 /dev/st5 /charon/tapes/tape1.vtape

Use the following syntax to write the content of a tape container to a physical tape:

$ mtd <tape container name> <tape device name>

Example:

$ mtd /charon/tapes/tape1.vtape /dev/st5

...

  • "-l" (or without parameters) - CHARON default license details
  • "-all" - all available CHARON licenses details
  • "-key <key number>" - specific CHARON license (defined by its "key number") details

The "hasp_srm_view" utility provides the following functionality:

  • Display the CHARON-AXP licenses details. It is possible to view all available license or some specific one.
  • Collecting license status information
  • Collecting host fingerprint information
  • Managing software license transfer procedure.

Run the utility without any options to display the license details.

#hasp# hasp_srm_view -help

CHARON Sentinel HASP utility
Copyright: STROMASYS, 2015

Options:
-? or -h or -help - to see help screen

-l - to see CHARON license details (for default key)
-all - to see CHARON license details (for all available keys)
-key <key number> - to see CHARON license details (for specific key)

-c2v <C2V file> - to collect the key status information (C2V file)
-fgp <C2V file> - to collect the host fingerprint information (C2V file)

-tfr <LicenseID> <recipient file> - to transfer SL license (V2C file)
-tfr <LicenseID> - to remove SL license (V2C file) from the local host
-idf - to get transfer recipient (ID) file "recipient.id"

...

Remote collection of status information

For remote collection of status information it is recommended to use "ssh" as shown in the following examples:

# ssh root@CHARON_HOST /opt/charon/bin/hasp_srm_view -c2v /opt/charon/bin/my_hasp_key.c2v
# ssh root@CHARON_HOST /opt/charon/bin/hasp_srm_view -fgp /opt/charon/bin/my_host_fingerprint.c2v

 

To see the license text on the console:

# ssh root@localhost /opt/charon/bin/hasp_srm_view

...

  1. 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.
     

  2. Copy the "recipient.id" file to the "SourceHost".

    Info

    "recipient.id" is an ASCII file, so use the "ascii" option for FTP transfer.

           

  3. 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.
     

  4. 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"

    Div
    classpagebreak

     


  5. Copy 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.

          

  6. On On the "RecipientHost", open "Sentinel Admin Control Center" (ACC) (http://localhost:1947) and apply the "<license number>.v2c" file as  described above.

Back to Table of Contents

...

  1. Open "Sentinel Admin Control Center" (ACC) (http://localhost:1947). Note the number of the software license you are going to remove.
     

  2. 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"
     

  3. It is always possible to re-apply the created ".v2c" file to restore the deleted software license.

Back to Table of Contents

...

To invoke the "hasp_update" utility login as "root" and use the following syntax:

# hasp hasp_update <option> update <option> [filename]

where:

ParameterValueDescription
<option>uUpdates a Sentinel protection key / attaches a detached license
iRetrieves Sentinel protection key information
dDetaches a license from a Sentinel Software License (SL) key
rRehost a license from a Sentinel Software License (SL) key
hDisplay help
[filename]Path to the V2C/H2R file (in case of 'u'pdate/attach)

Path to the C2V file
Optional: uses "stdout" if file name is not specified (in case of 'i'nfo)

Example:

hasp# hasp_update u license_update.v2c


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.

Dedication of a host physical interface to CHARON

...

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

Login as root. Type "ncu" and press Enter. The following menu will appear:

# ncu
CHARON Network Configuration Utility, STROMASYS (c) 2015 Version 1.5 

Interfaces Dedicated to State
---------- ------------ ------------
eth0       host         connected to host
eth1       host         connected from host
lo         host         unmanaged from host

==================================================================
bridge

name bridge id STP enabled

name     bridge id        STP enabled            interfaces

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Remove Bridge
5 - Print status
6 - Exit
:> 6

...

Interfaces Dedicated to State
---------- ------------ ------------
eth0       host         connected to host
eth1       CHARON       disconnected from host
lo         host         unmanaged from host

==================================================================
bridge

name bridge id STP enabled

name     bridge id        STP enabled            interfaces

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Remove Bridge
5 - Print status
6 - Exit

...

Login as root. Type "ncu" and press Enter. The following menu will appear:

# ncu
CHARON Network Configuration Utility, STROMASYS (c) 2015 Version 1.5  

Interfaces Dedicated to State
---------- ------------ ------------
eth0       host         connected to host
eth1       CHARON       disconnected from host
lo         host         unmanaged from host

==================================================================
bridge

name bridge id STP enabled interfaces

select name     bridge id        STP enabled            interfaces

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Remove Bridge
5 - Print status
6 - Exit
:> 2

...

Login a root. Start "ncu" utility:

#

ncu
CHARON

Network

Configuration

Utility,

STROMASYS

(c)

2015

Version

1.5 

Interfaces Dedicated to State
---------- ------------ ------------
eth0       host         connected to host
eth1       host         connected to host
lo         host         unmanaged from host

==================================================================
bridge

name bridge id STP enabled

name     bridge id        STP enabled            interfaces

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Destroy Bridge
5 - Print status
6 - Exit
:> 3

...

Now enter "5" to see the created virtual interfaces:

Interfaces Dedicated to

Interfaces   Dedicated to    State
----------

   ------------    -

-----------

-


eth0

        host       

 

 

host        

connected

to

host

eth1       bridge       connected to bridge
lo         host         unmanaged from host
tap0       bridge      connected to bridge
tap1       bridge       connected to

eth1         bridge          connected to bridge
lo           host            unmanaged from host
tap0         bridge          connected to bridge
tap1         bridge          connected to bridge

==================================================================
bridge

name bridge id STP enabled

name     bridge id           STP enabled        interfaces
br0_

eth1       8000.525400698995a  no     tap0
tap1 

eth1        8000.525400698995a  no                 tap0
                                                       tap1

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Remove Bridge
5 - Print status
6 - Exit
:> E

...

Login a root. Start "ncu" utility:

# ncu

CHARON Network Configuration Utility, STROMASYS (c) 2015 Version 1.5 
Interfaces   Dedicated to    State
---------- ------------ ------------
eth0       host         connected to host
eth1       bridge       connected to bridge
lo         host         unmanaged from host
tap0       bridge      connected to bridge
tap1       bridge       connected to bridge
==================================================================
bridge name bridge id STP enabled interfaces
br0_eth1       8000.525400698995a  no     tap0
tap1 

select action:
1 - Dedicate to CHARON
2 - Release to host
3 - Create Bridge with TAPs
4 - Remove Bridge
5 - Print status
6 - Exit
:> 4

...