Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Document reviewed / typos / Preformatted text in cells migrated to wiki markup in cells (PDF export issues)

Anchor
TopUtilPage
TopUtilPage

...

UtilityDescription
mkdskcmdUsed 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_viewUsed to display the CHARON license contents, to collect the host system fingerprint and to transfer software licenses from one host to another.
hasp_updateSentinel standard utility used to retrieve Sentinel protection key information, detache detach a license from a Sentinel SL key and rehost a license from a Sentinel SL key
ncuUsed to dedicate a host interface to CHARON-AXP, to release it back to the host and to manage CHARON virtual interfaces (TAPs).
mtdUsed to create CHARON tape images from physical tapes and to write tape images back to physical tapes.

...

To get all the available parameters please use the "–help"switch:

Usage:

mkdskcmd


   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 --transfer - please see the '--transfer' options description -t - please see the '-t' options description Return value: 0 - for Success Non zero - in case of failure Examples: mkdskcmd -h mkdskcmd -l mkdskcmd -a

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

   --transfer - please see the '--transfer' options description
   -t - please see the '-t' options description

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

Examples:
   mkdskcmd -h
   mkdskcmd -l
   mkdskcmd -a /opt/charon/bin/mkdsk.vtable

-o

/etc/rk07.vdisk

-d

rk07 mkdskcmd

rk07
   mkdskcmd -o

/etc/custom.vdisk

-z

512

-c

16384

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

...

  • <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 provided by the "mkdskcmd --list" request command execution or the disk geometry specification (see below).

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

...

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 without interruption. It implies "-r 0"

-nDo not rewind tape
-pDisable progress reporting
-v

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

...

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

#hasp# hasp_srm_view -help

CHARON Sentinel HASP utility
Copyright: STROMASYS SA, 2013

Options:
    -? or -h or -help - to see help screen
   -l - to see CHARON license details
   -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 HASP SL license (V2C file)
   -tfr <LicenseID> - to remove HASP SL license (V2C file) from the local host
   -idf - to get transfer recipient (ID) file "recipient.id"

The specific type of CHARON license defines what switches may be used in each case.

...

  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"
     

  5. 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 the "RecipientHost", open "Sentinel Admin Control Center" (ACC) (http://localhost:1947) and apply the "<license number>.v2c" file as  described above.

...

  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

...

Path
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 when used with the 'u' pdate/attach)option

Optional path to the C2V file
Optional: uses when used with the 'i' option

Uses "stdout" if file name is not specified (in case of 'i'nfo)specified

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.

...

Dedication of a host physical interface to CHARON

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

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

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

...

"ncu" offers several options:

  1. Dedicate interface to CHARON

...

  1. Release interface to host

...

  1. Create a bridge between a chosen physical network interface and the Linux virtual network and create a number of virtual network

...

  1. interfaces 
  2. Remove the Linux virtual network and all the created virtual network

...

  1. interfaces 
  2. Print status  - use it to display status of network interfaces and the menu shown above

...

  1. Exit

In the example above we see 2 network interfaces - "eth0" and "eth1", both of them are dedicated to host, but host uses only the interface "eth0".

...

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

...

Release of a host physical interface back to host

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

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

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
:> 2

...

Creation of a virtual network

Login a as root . Start and enter "ncu" utility:

#

ncu
CHARON

Network

Configuration

Utility,

STROMASYS

(c)

2015

Version

1.

4

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

Enter "3" to create a bridge between the host physical network adapter and the LINUX virtual network Interfaces interfaces (TAP) and specify the physical network interface ("eth1" in our example) and a the number of the  virtual network Interfaces interfaces to be created (2 in our example):

...

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

Interfaces

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

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 

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
:> E

...

Login a root. Start "ncu" utility:

# ncu

CHARON

Network

Configuration

Utility,

STROMASYS

(c)

2015

Version

1.

4 Interfaces Dedicated to

4

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

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

Enter "4" , after that specify then enter the interface name that is a bridge to the Linux virtual network on this host ("eth1" in our example) and press Enter:

Specify the phys interface used for BRIDGE:eth1
Cleanup bridge br0_eth1 with ip over eth1...
Removing the bridge: ..1..2 delif eth1
delif tap0
delif tap1
..5..6..7..8 done!

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

...