Home
Administering
This section describes how to plan for, install, configure, operate, and manage the SafeLinx Server.
Installation planning
Before you install HCL SafeLinx, verify that you meet the hardware and software requirements, and that the network connections that you want to use are available.
Your network
Before you install the SafeLinx Server, assess your administration, network, and capacity needs.
Transmission of accounting packets to RADIUS servers
For mobile access service VPN connections that communicate over the wireless optimized link protocol (WLP) or over IP, the SafeLinx Server can send accounting packets to a RADIUS server. The SafeLinx Server transmits accounting on/off and accounting start/stop packets to the RADIUS server.

Administering
This section describes how to plan for, install, configure, operate, and manage the SafeLinx Server.
- Overview
  HCL SafeLinx uses standards-based protocols to enable secure access from mobile computing devices outside the firewall to business applications and data on your organization's internal network.
- Security
  HCL SafeLinx includes a range of options for configuring the security of your network, applications, and data.
- Installation planning
  Before you install HCL SafeLinx, verify that you meet the hardware and software requirements, and that the network connections that you want to use are available.
  - Installation checklist
    The installation checklist provides an overview of the installation process so that you can verify that you are ready to install HCL SafeLinx.
  - System requirements
    Review the system requirements for using HCL SafeLinx.
  - Your network
    Before you install the SafeLinx Server, assess your administration, network, and capacity needs.
    - Supported network providers
      To support mobile access service connections from SafeLinx Clients or messaging services, you must install support for the network types that your clients use. The SafeLinx Server supports a range of IP and non-IP networks.
    - Capacity and performance
      The computer that hosts the SafeLinx Server must be powerful enough to handle the number of concurrent connections it services. It must also have enough disk space to store logging and accounting records.
    - Native-PPP connections
      You can connect to the SafeLinx Server from any dial-in device that supports the Point-to-Point Protocol (PPP), as defined in RFC 1661. The use of PPP connections applies to mobile access services for SafeLinx Clients only.
    - Default port numbers
      By default, each component of the SafeLinx Server is configured to listen on certain ports. For each component, you can modify the port that the SafeLinx Server listens on.
    - Transmission of accounting packets to RADIUS servers
      For mobile access service VPN connections that communicate over the wireless optimized link protocol (WLP) or over IP, the SafeLinx Server can send accounting packets to a RADIUS server. The SafeLinx Server transmits accounting on/off and accounting start/stop packets to the RADIUS server.
    - Firewall ports
      Your organization's firewall must be configured to allow connections from external clients and devices to the SafeLinx Server. If a second firewall stands between the SafeLinx Server and resources on the internal network, you must also establish rules that enable communications between them.
  - Upgrades from earlier HCL SafeLinx environments
    HCL SafeLinx 1.0.0 supports being installed on a previous release.
- Roadmaps: Installing and setting up SafeLinx
  The following "roadmap" topics guide you through installing and initially configuring SafeLinx. Refer to the topic that corresponds to your relational database and server operating system.
- Installing and initial configuration
  Initial configuration and installation of HCL SafeLinx varies based on your operating system and relational database.
- Adding a secure login profile
  By default, the SafeLinx Administrator communicates with the access manager over an unencrypted connection. If you want the connection between the SafeLinx Administrator and the access manager to use transport layer security (TLS) protocols, add a secure login profile to the SafeLinx Administrator.
- Adding and configuring resources
  After you complete the installation and initial configuration, continue to prepare the deployment by configuring other network resources.
- Administering
  The SafeLinx Administrator administration client is the primary tool for viewing, adding, configuring, and managing HCL SafeLinx resources. Along with the SafeLinx Administrator, you can use the HCL SafeLinx Monitor to view information about packet flow through the SafeLinx Server. You can also use a set of command line tools to perform common SafeLinx Server tasks.
- Programming reference
  There are several programming considerations of which you might want to take advantage.
- Database schema information
  HCL SafeLinx uses a DB2, Oracle, MySQL, or SQL database to store tables of information about current and past activity of SafeLinx Server sessions. The following tables are created and accessed by using the qualifier name wg for DB2 installations.
- Step by step: Nomad configuration
  Here are step-by-step instructions that serve as an example of how to install and configure HCL SafeLinx for Nomad on MySQL on Linux.

Transmission of accounting packets to RADIUS servers

For mobile access service VPN connections that communicate over the wireless optimized link protocol (WLP) or over IP, the SafeLinx Server can send accounting packets to a RADIUS server. The SafeLinx Server transmits accounting on/off and accounting start/stop packets to the RADIUS server.

If the primary RADIUS server does not acknowledge receipt of a packet within 3 seconds, the SafeLinx Server attempts to send the packet twice more. After the second attempt the SafeLinx Server waits 9 seconds for a response from the RADIUS server before it makes a third and final attempt. If all attempts fail, the error is logged by using a network management trap and the SafeLinx Server attempts to send the packet to the secondary RADIUS server. Another network management trap is sent if both RADIUS servers fail to respond.

Each valid RADIUS accounting request packet causes the RADIUS server to send a corresponding response packet. When the SafeLinx Server shuts down, an accounting-off packet is sent. Before it shuts down, the SafeLinx Server does not wait for a response packet from the RADIUS server.

If you disable the RADIUS accounting configuration during normal operation, an accounting-off packet is sent to the RADIUS server. Then, the SafeLinx Server continues to process response packets and to resend any packets that were not acknowledged. No new request packets are generated while the RADIUS accounting configuration is disabled.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.