Tutorial: Setting up the secure network

Contents

• Basic concepts
• Before you begin
• Task flow
• Command reference

Basic concepts

Some of the key features of the secure network are listed here:

• An end-to-end encrypted network.
• Controlled by the user rather than the cloud provider. The secure network configuration for a virtual server is managed by the user who creates the Hyper Protect Virtual Server instance, and this configuration cannot be modified by the IBM Cloud IAM user, nor by the IBM Cloud operator.

A user with administrator access to the Hyper Protect Virtual Server must set up the entire secure network and can configure multiple users to this role, who have access to the capabilities to manage the secure network and deploy solutions on the secure network.

1. The secure network management agent that runs on the Hyper Protect Virtual Servers receives commands from the secure network management agent CLI and updates the Virtual Private Network (VPN) configuration on the Hyper Protect Virtual Servers, as requested.
2. The secure network management agent CLI receives the user command inputs and updates the VPN configuration of the Hyper Protect Virtual Servers by sending requests to the secure network management agent that is running on the Hyper Protect Virtual Servers.
3. The secure network opens two endpoints on the virtual server network interface:
   • In the data plane: A WireGuard endpoint (UDP port) that is used by the WireGuard driver.
   • In the control plane: A management agent endpoint (TCP port) that is used by the management agent.
4. The secure network stores configuration data in files. The data volume should be mounted on the virtual server local persistent storage for the secure network configuration data. All network configuration files are mounted at /data/hpagent_store.
5. The IBM Cloud® Identity and Access Management (IAM) is used for user authentication. For more information, see IBM Cloud Identity and Access Management.

Before you begin

To complete this tutorial, you need to meet the following prerequisites:

• Administrator access to the Hyper Protect Virtual Server.
• Two Hyper Protect Virtual Servers instances.
• Install the IBM Cloud CLI.

• Install the HPVS CLI plugin version 1.4.17, of IBM Cloud. The HPVS CLI plugin is a dependency of the hpnet CLI plugin.
• Install the secure network CLI plugin by running the command ibmcloud plugin install hpnet. To install the plugin in the staging environment, complete the following steps:
  • Install from staging environment by running the ibmcloud plugin install hpnet -r stage1 command.
  • To install plugin on production environment by running the ibmcloud plugin install hpnet command.
• Log in to IBM Cloud by using the CLI. If you have multiple accounts, select the account that your service instance is created with. Make sure that you log in to the correct region and resource group where the service instance is located by running the command ibmcloud target -r <region> -g <resource_group>

Task flow

To complete this solution, you walk through the following steps:

1. Configuring the virtual servers
2. Configuring the audit log
3. Admin key administration
4. VPN administration
5. End to end encryption via the VPN tunnel

Step 1: Configuring the virtual servers

The Hyper Protect Virtual Servers instances are considered as 'HPVS_A', and 'HPVS_B', in this tutorial. For each of these two instances, complete the following steps:

1. To install CA certificates, run the following command:

   apt-get update && apt-get install -y ca-certificates
   

2. Create the authorized_user file and save it at /data/hpagent_store/authorized_user, with a list of IBM Cloud user IDs. The secure network management agent uses this list to approve a request and rejects any request that is not in this list. To create the authorized_user file, run the following commands:

   mkdir -p /data/hpagent_store
   cat <<EOF > /data/hpagent_store/authorized_user
   <email_of _authorized_user>
   EOF
   

3. If the secure network management agent is deployed in a Hyper Protect Virtual Server instance which is in the staging environment (you should not run this command in the production environment), then you must export the following variable:

   export isProduction=false
   

4. To install the secure network management agent, download the files dap-public.pem, encryptednetwork-2.0.0.tar.gz, and encryptednetwork-2.0.0.tar.gz.sig from this GitHub repository.

   The secure network management agent and its repository are for allowlisted accounts. To get added to the allowlist, open a case with support.

   After you save the files to /root, or /data, and complete the following steps:

   • To verify secure network management agent's signature, run the following command.

     openssl dgst -sha256 -verify dap-public.pem -signature encryptednetwork-2.0.0.tar.gz.sig encryptednetwork-2.0.0.tar.gz
     

     The following snippet shows an example output.

     encryptednetwork-2.0.0.tar.gz Verified OK
     

   • To extract the compressed file, run the following command.

     tar -zxvf encryptednetwork-2.0.0.tar.gz
     

   After you successfully extract the compressed file, the folder 'encryptednetwork' contains a file called encryptednetwork. To install and launch the secure network management agent, run the following commands:

   mkdir /data/log/
   

   nohup ./encryptednetwork > /data/log/log.log 2>&1 &
   

   The secure network management agent is now running. The following network configuration files are mounted at /data/hpagent_store:

   /data/hpagent_store/authorized_user
   /data/hpagent_store/public.pem
   /data/hpagent_store/private.key
   /data/hpagent_store/agent_config
   /data/hpagent_store/connections-config
   

   The agent_config, and connections-config files are automatically generated by the secure network management agent later. You must configure only the /data/hpagent_store/authorized_user file. All the other files are created and maintained by the secure network management agent. You must ensure that the contents of the /data/hpagent_store/agent_config and connections-config files are not modified and is protected from inadvertent exposure because that can cause potential attacks on the system. To keep the data at this location safe, you should follow the guidance on backup and restore.

   After you complete these steps, the secure network management agent starts listening on the specified network port and is ready to accept requests from the secure network management CLI. These tasks can be done manually after connecting to the Hyper Protect Virtual Servers instance by using SSH, or when creating a container image in the case of BYOI.

   To prevent any malicious access, consider the following recommendations to control access to the Hyper Protect Virtual Server:

   • The secure network management agent binary and configuration files are highly sensitive and should never be exposed or altered. It is your responsibility to control access to the Hyper Protect Virtual Server.
   • Disable SSH access for your production environment when you have highly sensitive workloads. When you need to grant SSH access to the Hyper Protect Virtual Server to multiple users, you must control the permissions of SSH users, and configure the Hyper Protect Virtual Server file system permission to allow only designated users to access the secure network management agent binary and all configuration files, and prevent any other users from having any read, write, or execute on these files.
   • It is your responsibility to keep the SSH private key secure, if SSH is enabled for the Hyper Protect Virtual Server.

   To prevent malicious access to the desktop that you used to set up and configure the secure network management, consider the following recommendations:

   • You must download and install the secure network management agent only from this Github repository, with the correct signature provided by IBM. Do not install any programs from any other address that does not have the correct signature from IBM, as it might be malicious and can cause potential attacks on the virtual server.
   • It is your responsibility to keep your desktop secure.
   • It is your responsibility to encrypt the admin private key and keep it secure.

Step 2: Configuring the audit log

Complete the following to configure Log Analysis to trace audit logs:

1. Create a LogDNA service instance

   • Create a logging service in the production environment in the us-south region.
   • Get the ingestion key.

   For more information about the LogDNA service, see Configuring a Logging agent for Linux Ubuntu or Debian.

2. Monitor the Hyper Protect Virtual Servers instance via the LogDNA instance.

   • Log in to the Hyper Protect Virtual Servers instance (either staging or production in any region).
   • Configure the LogDNA agent on the Hyper Protect Virtual Servers instance

   apt-get update
   apt-get install -y git npm curl wget
   npm install -g n
   n lts
   PATH="$PATH"
   node -v
   
   git clone https://github.com/logdna/logdna-agent.git
   cd logdna-agent && npm install
   node index.js -k <ingestion-key>
   node index.js -d /data/log
   node index.js -t logging
   node index.js -s LOGDNA_APIHOST=api.us-south.logging.cloud.ibm.com
   node index.js -s LOGDNA_LOGHOST=logs.us-south.logging.cloud.ibm.com
   node index.js
   

   For more information about how to set up monitoring in Hyper Protect Virtual Servers, see Monitoring logs.

3. Check for logs of the configuration status from the LogDNA dashboard.

   The following actions are traced by the audit log:

   • 'Admin Public Key' >>> 'secure-network-admin-key'

   secure-network-admin-key.read
   secure-network-admin-key.create
   secure-network-admin-key.update
   secure-network-admin-key.delete
   

   • 'Connection' >>> 'secure-network-connection'

   secure-network-connection.add
   secure-network-connection.update
   secure-network-connection.delete
   secure-network-connection.read
   

   • 'Node' >>> 'secure-network-node'

   secure-network-node.delete
   secure-network-node.create
   secure-network-node.update
   secure-network-node.read
   

   The following snippet shows an example of an audit log:

   {
       "action":"<hpvs service name>.secure-network-admin-key.delete",
       "initiator":{
           "id":token.IBMid,
           "name":token.sub,
           "typeURI":"service/security/account/user",
           "authnId":token.IBMid,
           "authnName":token.sub,
           "credential":{
               "type":"user"
           },
           "host":{
               "address":"9.197.247.35",
               "addressType":"IPv4",
               "agent":"grpc-go/1.38.0"
           }
       },
       "eventTime":"2021-07-14T10:27:00.39+0000",
       "logSourceCRN": <full CRN which is provided by user/customer>",
       "message":"Hyper Protect Virtual Server : delete secure-network-admin-key",
       "observer":{
           "name":"ActivityTracker"
     },
     "outcome":"success",
     "reason":{
         "reasonCode":200,
         "reasonType":"ok"
     },
     "saveServiceCopy":true,
     "severity":"critical",
     "target":{
         "name":"",
         "typeURI":"<hpvs service name>/secure-network-admin-key",
         "id":<full CRN which is provided by user/customer>,
         "resourceGroupId":<full CRN of resourceGroupId which is provided by HPVS team>
     },
     "dataEvent":true,
     "requestData":{
         "serviceInstanceId":<analysis from instance CRN>,
         "accountId":<token.account>,
         "adminPubKeyId":<token.IBMid>
     },
     "responseData":{
         "adminPubKeyId":<token.IBMid>
     }
   }
   

Step 3: Admin key administration

The secure network management CLI stores the newly generated key pair in the local file system, the private key is derived by using PBKDF2, which is aligned with the PKCS#5 standard, and the private key is protected by a mandatory passphrase. The private key is stored in a local file that follows the PKCS#8 standard, and you must ensure that you protect the passphrase and keep the private key file secure. The secure network management CLI uses the private key to sign the request to upload the public key to the secure network management agent over the secure connection. Thereafter, the uploaded public key is associated with the user ID, and works as the administrator key to authenticate all subsequent operations that the specified user executes.

After this is complete, the secure network management agent is ready to accept requests from the secure network management CLI to perform secure network administration including admin key management and VPN management. The administration requests are signed with the user provided admin private key (except reading requests which do not make any changes on the secure network), and are authenticated by the uploaded corresponded admin public key.

ibmcloud hpvs instances

Getting instances ...


Name                     hpnet-test1   
CRN                      crn:v1:staging:public:hpvs:dal10:a/9f63166137084e9d9131e42bfce481a6:8ba48f91-ef4a-4433-b411-fd8b2becc18b::   
Location                 dal10   
Cloud tags                  
Cloud state              active   
Server status            running   
Plan                     Free  
Public IP address        52.117.54.147   
Internal IP address      172.17.24.116   
Boot disk                25 GiB   
Data disk                25 GiB   
Memory                   2048 MiB   
Processors               1 vCPUs   
Image type               ibm-provided   
Image OS                 ubuntu20.04   
Public key fingerprint   RA1/M9gnMnz831+Q4pGpZ74/BPcJV047zIHb5HCaxOs   
Last operation           create succeeded   
Last image update        -   
Created                  2022-03-04   


Name                     hpnet-test2   
CRN                      crn:v1:staging:public:hpvs:dal10:a/9f63166137084e9d9131e42bfce481a6:1b763c10-2970-48aa-88d8-9c63fb66cc7d::   
Location                 dal10   
Cloud tags                  
Cloud state              active   
Server status            running   
Plan                     Free   
Public IP address        52.117.54.138   
Internal IP address      172.17.24.117   
Boot disk                25 GiB   
Data disk                25 GiB   
Memory                   2048 MiB   
Processors               1 vCPUs   
Image type               ibm-provided   
Image OS                 ubuntu20.04   
Public key fingerprint   RA1/M9gnMnz831+Q4pGpZ74/BPcJV047zIHb5HCaxOs   
Last operation           create succeeded   
Last image update        -   
Created                  2022-03-04   

ibmcloud hpnet adminkey set

Select the HPVS instance for '--instance'

Select a virtual server:
1. hpnet-test1 - crn:v1:staging:public:hpvs:dal10:a/9f63166137084e9d9131e42bfce481a6:8ba48f91-ef4a-4433-b411-fd8b2becc18b::
2. hpnet-test2 - crn:v1:staging:public:hpvs:dal10:a/9f63166137084e9d9131e42bfce481a6:1b763c10-2970-48aa-88d8-9c63fb66cc7d::
Enter a number>

ibmcloud hpnet adminkey set --instance "hpnet test1"

Generating public/private ed25519 key pair for the admin of hpnet test1...

ibmcloud hpnet adminkey set --instance "crn:v1:staging:public:hpvs:dal10:a/9f63166137084e9d9131e42bfce481a6:8ba48f91-ef4a-4433-b411-fd8b2becc18b::"

Generating public/private ed25519 key pair for the admin of hpnet test1...

ibmcloud hpnet adminkey get

Select the HPVS instance for '--instance'

Select a virtual server:
1. hpnet-test1 - crn:v1:staging:public:hpvs:dal10:a/9f63166137084e9d9131e42bfce481a6:8ba48f91-ef4a-4433-b411-fd8b2becc18b::
2. hpnet-test2 - crn:v1:staging:public:hpvs:dal10:a/9f63166137084e9d9131e42bfce481a6:1b763c10-2970-48aa-88d8-9c63fb66cc7d::
Enter a number> 1

Connecting to the server hpnet-test1 [52.117.54.147] ...

The connecting server's certificate is valid and already confirmed in previous command
The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances

Continue connecting to the server...

Querying the public key of the admin...

The retrieved public key:
+---------------+-----------+----------------------------------------------+---------------------------------------------------------+
| INSTANCE_NAME | KEYTYPE   | VALUE(BASE64)                                | PRIVATEKEY                                              |
+---------------+-----------+----------------------------------------------+---------------------------------------------------------+
| hpnet-test1   | PublicKey | 1BCBy+SEWAEigYQPWXHpkJh039ZUZ4ie42AUrMi7MvM= | /Users/hexiaohu/.hpnet-cfg/hpnet-test1-83-92-b6-4b.priv |
+---------------+-----------+----------------------------------------------+---------------------------------------------------------+


OK

Step 4: VPN administration

The VPN administration tasks must be performed by a user who has a valid IBM Cloud user account and a valid secure network admin key pair (by using these procedures).

The VPN administration involves the following tasks:

• Setting up a VPN node
• Setting up VPN trusted peers

See Parameter specification for details about some specifications that apply to some of the parameters of the secure network management CLI commands.

Step 5: End to end encryption via the VPN tunnel

After setting up the admin key, the VPN node, and the VPN trusted peers, complete the following steps to encrypt the connection between the two Hyper Protect Virtual Server instances.

1. Start a service on 'HPVS_A' by binding to the VPN IP, which is ${VPN_IP_A}, as set earlier in this tutorial.
2. Have a client on 'HPVS_B' connect to the service running on 'HPVS_A' by using the VPN IP, which is ${VPN_IP_A}, as set earlier in this tutorial.
3. Now the connection between the client on HPVS_B and the service on HPVS_A are end to end encrypted via the VPN tunnel.

Command reference

• To view the details of the commands and their parameters, type the command you want view with the --help option, for example the following command shows you details about the hpnet adminkey set command:

  ibmcloud hpnet adminkey set --help
  NAME:
    set - Set the admin keypair
  
  USAGE:
    ibmcloud hpnet adminkey set [--instance <NAME | CRN>]
  
  OPTIONS:
    --instance  The hpvs instance name or crn
  

• The adminkey get command, to retrieve the configured admin public key

  ibmcloud hpnet adminkey get --instance "$HPVS_A"
  
  
  Connecting to the server hpnet-test1 [52.117.54.147] ...
  
  The connecting server's certificate is valid and already confirmed in the previous command
  The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances
  
  Continue connecting to the server...
  
  Querying the public key of the admin...
  
  The retrieved public key:
  +---------------+-----------+----------------------------------------------+---------------------------------------------------------+
  | INSTANCE_NAME | KEYTYPE   | VALUE(BASE64)                                | PRIVATEKEY                                              |
  +---------------+-----------+----------------------------------------------+---------------------------------------------------------+
  | hpnet-test1   | PublicKey | 1BCBy+SEWAEigYQPWXHpkJh039ZUZ4ie42AUrMi7MvM= | /Users/hexiaohu/.hpnet-cfg/hpnet-test1-83-92-b6-4b.priv |
  +---------------+-----------+----------------------------------------------+---------------------------------------------------------+
  
  
  OK
  
  

• The adminkey update command, to generate a new keypair and update the admin public key on the VPN node

  ibmcloud hpnet adminkey update --instance "$HPVS_A" --admin-priv-key "$ADMIN_PRIV_KEY_A"
  
  
  Generating public/private ed25519 key pair for the admin of hpnet-test1...
  
  Enter passphrase of the private key>
  Enter same passphrase again>
  OK
  
  Starting to encrypt key '/Users/hexiaohu/.hpnet-cfg/temp/hpnet-test1-a5-d8-9a-25.priv.tmp'....
  
  Enter passphrase to use the private key '--admin-priv-key'>
  OK
  
  Starting to decrypt key '/Users/hexiaohu/.hpnet-cfg/hpnet-test1-83-92-b6-4b.priv'....
  
  Connecting to the server hpnet-test1 [52.117.54.147] ...
  
  The connecting server's certificate is valid and already confirmed in the previous command
  The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances
  
  Continue connecting to the server...
  
  Refreshing the public key of the admin...
  
  The new generated key pair:
  +-------------------------------------------------------------+------------+---------------------------------------------------------+
  | FINGERPRINT(SHA1)                                           | KEYTYPE    | FILE                                                    |
  +-------------------------------------------------------------+------------+---------------------------------------------------------+
  | f7:25:20:96:96:47:46:ec:b7:b5:a1:ff:53:62:68:dd:cb:21:6d:9c | PrivateKey | /Users/hexiaohu/.hpnet-cfg/hpnet-test1-a5-d8-9a-25.priv |
  | 04:03:60:c8:52:5f:dc:b4:93:1b:fc:7f:62:d1:a9:54:a5:d8:9a:25 | PublicKey  | /Users/hexiaohu/.hpnet-cfg/hpnet-test1-a5-d8-9a-25.pub  |
  +-------------------------------------------------------------+------------+---------------------------------------------------------+
  
  An automatically generated keypair is stored locally and configured to node remotely.
  The keypair is required to keep carefully!!!
  
  
  OK
  

  ibmcloud hpnet adminkey delete --instance "$HPVS_A" --admin-priv-key "$ADMIN_PRIV_KEY_A"
  
  
  Enter passphrase to use the private key '--admin-priv-key'>
  OK
  
  Starting to decrypt key '/Users/hexiaohu/.hpnet-cfg/hpnet-test1-a5-d8-9a-25.priv'....
  
  Connecting to the server hpnet-test1 [52.117.54.147] ...
  
  The connecting server's certificate is valid and already confirmed in the previous command
  The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances
  
  Continue connecting to the server...
  
  Deleting the public key of the admin...
  
  OK
  The public key of the admin was deleted.
  
  

• The hpnet node get command, to get the configuration on the VPN node

  ibmcloud hpnet node get --instance "$HPVS_A"
  
  
  Connecting to the server hpnet-test1 [52.117.54.147] ...
  
  The connecting server's certificate is valid and already confirmed in the previous command
  The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances
  
  Continue connecting to the server...
  
  Querying detail of the node hpnet-test1 ...
  +-----------------+----------------------------------------------+
  | NODE_PROPERTIES | VALUES                                       |
  +-----------------+----------------------------------------------+
  | VPNPublicKey    | zHlHCJCV7ub7FJjAWOXGZU3BV/rQOLMwMCq2dqOKsW0= |
  | VPNIp           | 10.10.10.1/24                                |
  +-----------------+----------------------------------------------+
  
  
  OK
  
  

• The hpnet node refresh command, to refresh the keypair of the VPN connection

  ibmcloud hpnet node refresh --instance "$HPVS_A" --admin-priv-key "$ADMIN_PRIV_KEY_A"
  
  
  Enter passphrase to use the private key '--admin-priv-key'>
  OK
  
  Starting to decrypt key '/Users/hexiaohu/.hpnet-cfg/hpnet-test1-c3-10-f7-a3.priv'....
  
  Connecting to the server hpnet-test1 [52.117.54.147] ...
  
  The connecting server's certificate is valid and already confirmed in the previous command
  The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances
  
  Continue connecting to the server...
  
  Refreshing the node hpnet-test1 ...
  
  The refreshed connections:
  +---------------+-------------+-----------+--------------+-------+
  | INSTANCE_NAME | TARGET_NAME | STATE     | SYNCHRONIZED | ERROR |
  +---------------+-------------+-----------+--------------+-------+
  | hpnet-test1   | hpnet-test2 | connected | true         |       |
  +---------------+-------------+-----------+--------------+-------+
  
  
  OK
  Node hpnet-test1 was refreshed.
  

• The hpnet node delete command, to clear the configuration of the VPN node

  ibmcloud hpnet node delete --instance "$HPVS_A" --admin-priv-key "$ADMIN_PRIV_KEY_A"
  
  
  Enter passphrase to use the private key '--admin-priv-key'>
  OK
  
  Starting to decrypt key '/Users/hexiaohu/.hpnet-cfg/hpnet-test1-c3-10-f7-a3.priv'....
  
  Connecting to the server hpnet-test1 [52.117.54.147] ...
  
  The connecting server's certificate is valid and already confirmed in the previous command
  The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances
  
  Continue connecting to the server...
  
  Deleting the node hpnet-test1 ...
  
  OK
  Node hpnet-test1 was deleted.
  

• The hpnet connect list command, to get view all configured VPN links on the VPN node:

  ibmcloud hpnet connect list --instance "$HPVS_A"
  
  
  Connecting to the server hpnet-test1 [52.117.54.147] ...
  
  The connecting server's certificate is valid and already confirmed in previous command
  The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances
  
  Continue connecting to the server...
  
  Querying connections of hpnet-test1 ...
  
  The connections:
  +---------------+-------------+----------+-----------+--------------+
  | INSTANCE_NAME | TARGET_NAME | TYPE     | STATE     | SYNCHRONIZED |
  +---------------+-------------+----------+-----------+--------------+
  | hpnet-test1   | hpnet-test2 | outgoing | connected | true         |
  +---------------+-------------+----------+-----------+--------------+
  
  OK
  

• The hpnet connect sync command, to synchronize the connection configuration which might be refreshed but out of synchronization on any of the VPN node:

  ibmcloud hpnet connect sync --instance "$HPVS_A" --target "$HPVS_B"  --admin-priv-key "$ADMIN_PRIV_KEY_A"
  
  
  Enter passphrase to use the private key '--admin-priv-key'>
  OK
  
  Starting to decrypt key '/Users/hexiaohu/.hpnet-cfg/hpnet-test1-c3-10-f7-a3.priv'....
  
  Connecting to the server hpnet-test1 [52.117.54.147] ...
  
  The connecting server's certificate is valid and already confirmed in previous command
  The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances
  
  Continue connecting to the server...
  
  Synchronizing the connection between hpnet-test1 and hpnet-test2 ...
  
  OK
  The connection between hpnet-test1 and hpnet-test2 was synchronized.
  

• The hpnet connect delete command, to delete the connection between two VPN nodes:

  ibmcloud hpnet connect delete --instance "$HPVS_A" --target "$HPVS_B"  --admin-priv-key "$ADMIN_PRIV_KEY_A"
  
  
  Enter passphrase to use the private key '--admin-priv-key'>
  OK
  
  Starting to decrypt key '/Users/hexiaohu/.hpnet-cfg/hpnet-test1-c3-10-f7-a3.priv'....
  
  Connecting to the server hpnet-test1 [52.117.54.147] ...
  
  The connecting server's certificate is valid and already confirmed in previous command
  The certificate can be confirmed again by removing the HPVS instance from file /Users/hexiaohu/.hpnet-cfg/known_instances
  
  Continue connecting to the server...
  
  Deleting the connection between hpnet-test1 and hpnet-test2 ...
  
  OK
  The connection between hpnet-test1 and hpnet-test2 was deleted.
  

Parameter specification

The following table lists the specifications that apply to some of the parameters of the CLI commands.