Copy the LiveNX client installer (LiveActionClient_<OS>_<VERSION>_setup) to the PC or Mac that LiveNX will be used from and run the installer. Follow the instructions in the installation wizard. The installation should take less than 10 minutes to complete.
Installing on Macs is the same as Windows except the Mac installer is a dmg file.
Start the client by clicking on the desktop shortcut. The user login prompt will appear. Click Configure to enter the Server IP address and application port number. The default port number to use is 7000. The first time username and password are admin and admin. After the initial login completes the user will be prompted to create a stronger password.
NOTE: Forgetting the passwords for all administrative accounts will require resetting all LiveNX settings and rebuilding the configuration. Refer to Chapter 3 for more information on resetting the LiveNX configuration.
• When a user logs in for the first time, the welcome screen will pop up. Click > Start: Discover Devices
Java Web Start Client Installation
Client software can also be installed by opening a web browser to the LiveNX Server.
The client software can also be downloaded from the web user interface
Windows Java Web Start
Click the link Launch the LiveNX Client
1. Accept the Java Web Start installation.
i. This may take several minutes while all the files are downloaded and installed.
2. Once installed the user will be prompted to run the client and receive a LiveNX login prompt.
a. Please note that there are issues with Google Chrome where the initial web start may work but subsequent ones may fail. This is a known issue in Chrome that may be fixed in the future by Google.
Mac Java Web Start
The Mac Java web start can be more involved due to security restrictions for Java web start.
1. Typically, this will require changing the settings in System Preference > Security and Privacy settings to allow running the Java web start program. Please refer to detailed Mac installer documentation for more specifics.
2. Login into LiveNX with the default administrative account.
3. Go to Users > User Management to create user accounts with the appropriate roles.
NOTE: See Chapter 3 Role-Based Access for information on creating user accounts.
NOTE: A fully operational trial version of the software will operate for up to 14 days. The user will have an option to purchase LiveNX when the Trial License expires.
HTTP Proxy Configuration Support
1. LiveNX 6.0.1 version onwards has the ability to configure a HTTP(S) proxy for outgoing web requests. This is useful during geo-lookups, get a license and for sending telemetry data. Some assumptions to consider for this implementation.
a. HTTP clients respect the following environment variables like Linux/UNIX OS.
- i. HTTP_PROXY / http_proxy
- ii. HTTPS_PROXY / https_proxy
- iii. NO_PROXY / no_proxy
b. Only admin users can edit the proxy settings.
c. Only basic level of authentication is supported.
d. Single proxy entry for both HTTP and HTTPS requests and hence all HTTP and
HTTPS request will go through the same proxy.
2. The new proxy settings are exposed in the Management Console properties tab.
a. When the Management Console is run from within an OVA, these properties
settings are not editable but will have a tooltip explaining that the settings
should be changed using the Web UI.
b. When the Management Console is run from a regular OS environment, these
settings can be edited.
3. User Interaction: Users can add the HTTP Proxy configuration and authentication entries from the Web Interface. The web application uses the request NPM module as an HTTP client.
Secure Web Login Configuration
Secure Login to LiveNX can be enabled through the LiveAction Server Management Console.
1. To enable Secure Web Login a. Click Properties > httpserver.secure i. Change this option to True
b. Click httpserver.port i. Default is 8092 [Typical Options are 443 or 8443]
c. Click Apply
2. To ensure that configuration takes effect a. Click Manage > Shutdown Service
b. Click Manage > Start Service
• Open a web browser and type in https://localhost:8092 [Default Port = 8092]. Depending on the browser, there will be a warning with a similar message below.
Click Continue. This will bring up a secure web page.
Enter the administrative LiveNX username and password and click on Login.
The help dropdown components (Quick Start, User Guide, and Launch Client) are available without logging in. All other menu items (QoS Reports, NetFlow Reports, IP SLA Reports, Routing Reports, LAN Reports) require valid log-in credentials to continue.
Unsecured Web Service
To return LiveNX to unsecured web service, go to the LiveAction Management Console > Properties > httpserver.secure
Change true to false (or leave the field blank). Click away from the httpserver.secure field to ensure that the false value is maintained during this process. Click on Manage > Shutdown Service.
After the service shuts down, restart the service by clicking on Manage > Start Service and then Manage > Connect to Service. The title menu bar of the LiveAction Management Console should say Connected.
Once the Server is restarted, open a web browser and type in http://localhost:8092. The webpage will now hide any login entries, and all the menu items are available without any login prompts.
In LiveNX 6.0.1 version, sending out user Telemetry data is enabled by default. Users can disable if required from the Management Console interface.
The management console mentioned above and the properties page can be accessed via the web page also.
The various users sessions/ logins can be viewed and monitored at the following page. Caveat: Users with a timeout of “Never” will never be logged out from the web, even if closing the browser. They must be manually logged out either by pressing the “Logout” button or having their sessions terminated through the Session Management dashboard.
The properties page can be accessed here and all the LiveNX server related parameter changes can be made here. Once a change is made the server needs to be restarted.
Mounted Data Management: User can mount a data directory that contains flow, alert, or QoS data by clicking on the mount directory button. All directories in the list below are grouped together by type. Mounted data directories on server can be related to data of Flow, QoS and SNMP. Changes to priority of individual directories in the list can also managed over here.
Node Management: Addition or modification of LiveNX nodes can be managed in this section. Exporting node configuration file and updating address of node can also be managed here.
Troubleshooting: A heap dump is a snapshot of the memory of a Java™ process. The snapshot contains information about the Java objects and classes in the heap when the snapshot is triggered. User can Sanitize existing heap dump
Email Configuration: This is mainly required for configuration of alert page.
Configuration Mangement: User can import/ export required or current system configuration. Importing a configuration will prompt the user to restart the ova. The restart process takes a few minutes during which time the user will be unable to login.