White Paper: Utilizing Flow and Packet Data to Optimize Network Performance Read Now

Frequently Asked Questions

LiveNX can process 1 M flows/sec via a special-purpose, high-performance database.

Via SNMP by specifying an IP address, subnet range, or a seed device.

You can reset your local admin password using the LiveNX Server Management Console. LiveNX Server Management Console can be access thru VM console or VNC.

Instruction to reset admin password:

1. SSH onto LiveNX OVA
2. SSH login credential, username = admin, password = changeme
3. Run command “vnc start”
4. Connect thru VNC Viewer
5. VNC login credential, username = admin, password = changeme
6. Launch LiveNX Server Management Console.
7. Go to Manage > Reset Password
8. After resetting password, login to the LiveNX Client and change password.

LiveNX Flow provides advanced end-to-end system-level flow visualizations for multi-vendor networks. The following devices have gone through flow-analysis testing with LiveNX can be found in the LiveNX specifications page at specifications.

As of LiveNX 7.2.0, Custom Dashboard is available in the Web UI.

  • Dashboards can be shared with other users
  • Custom widgets can be created from a certain report
  • A new “Filterable Custom Dashboard” has been added to allow filtering of dashboards containing only custom widgets
  • Default templates have been reworked to provide more insight into the information they provide
  • “Add Widget” process has been improved

A new license is not required to upgrade minor release versions

You can schedule daily, weekly and monthly reports via LiveNX Report Scheduler. The report can be sent as a PDF attachment or a hyperlink via emails.

You may have a total of ten active sessions connecting to a LiveNX server at any time, but only one admin session. This is to ensure that key items (for example – alerting, device settings, etc.) are properly handled. Please see the user guide for more information about the different rule-based access control privileges available for each user type.

1. Login into the LiveNX Web UI Client.
2. Go to https://LiveNXIP
3. Enter username and password
4. Click Login
5. On the top right corner, click the Desktop icon to Launch Desktop App and accept the Java Webstart installation.

livenx-client-through-a-java-webstart

This may take several minutes as all the files are downloaded and installed. Once installed you will be prompted to run the client and you will get the LiveNX login prompt.

If this is your first-time logging into the LiveNX Client, login into the default administrator account and create users. The initial default admin credentials are as follows:

Username: admin
Password: admin

In 7.1.0 release, the automatic purging schedule is now available from 1-365 days. To change LiveNX Database settings, go to Tools > Options > Database in the Java Client.

In the LiveNX client, you can verify that you are not seeing any NetFlow data by selecting Flow –> Data Status and clicking the Execute Flow Counts button.

netflow-data-on-my-device

  • Flows should be coming in on port 2055, unless changed in the Management Console.
  • LiveNX may not read the flow data if it is coming from an IP address that was not used when adding it to the application.
    • If this is the case, you could try re-adding the device using the IP address being used to source NetFlow.
    • You could also potentially set the NetFlow source interface to correspond with the IP address used to add the device.
  • Ensure that there are no ACLs that could be blocking NetFlow out of the device.

1. Login to the LiveNX Web UI Client.
2. Go to https://LiveNXIP
3. Enter username and password
4. Click Login
5. On the top right corner of the LiveNX page, Click the Gear icon, System Management > Configuration
livenx-backup-configuration-
6. Click Export to Export Backup Configuration or Import to Restore Backup Configuration
import-to-restore-backup-configuration

Note:
1. Java Client session will timeout during the export configuration process.
2. Import Configuration process will require to restart LiveNX Service.

Windows 64-bit Operating System – Server 2008 or 2012 R2, Windows 7 (Professional or Ultimate) with .NET framework v3.5.1+

Linux RHEL/CENTOS 6.4 or 6.5 with GNOME UI

Yes, LiveNX support Rest API. This is a way for users to access captured network data on the LiveNX Server without direct use of the LiveNX Client. This allows the user to build up their own special reports or analysis through a programmatic way based upon the LiveNX data.

To Access the LiveNX Rest API Swagger Page:

1. Login to the LiveNX Web UI Client.
2. Go to https://LiveNXIP
3. Enter username and password
4. Click Login

On the top right corner of the LiveNX page, Click the API icon, you will be redirected to the API page https://<LiveNXIP>:8093/v1/docs/

livenx-rest-api-swagger-page

There are 2 scenarios that would require you to deactivate your license.

License activations are tied to the original server’s MAC address.

Deactivating your license will enable it to be re-activated at a future time or location with a new MAC address.

a. Migrating your LiveNX Server to a new location.
b. Starting a fresh installation.

Using NetFlow, we can map IP address wrt DSCP markings, but we don’t map IP address directly to QoS queue. Most companies use DSCP based QoS queue maps so this works most of the time.

LiveAction does allow local authentication alongside LDAP. If you are planning to migrate to LDAP and would like to test it with LiveNX.

This feature has already been implemented in 6.2.0, but not many customers are aware of how it works. Follow these steps to add users from AD Security group.

https://community.liveaction.com/knowledge_base/configuration-add-users-from-ad-security-groups-v1/

From a topology drawing perspective, we have a 100-interface limit, so you can see them. In the future, we’re looking at grouping on the screen. For interface level alerts for up/down, errors or drops, we provide that for all interfaces. For layer 2 trunks and access ports and HW queue information, we show all interface. From a flow device view, we show flows from any interface that has been enabled.

LiveAction specializes in application and network performance with QoS Control. It offers alerting, visual path trace and another color-coded status for fault management, but no syslogging. It also provides network health functionality including network discovery and topology, network monitoring using NetFlow, IPFIX, SNMP, QoS, routing and LAN statistics, dashboard, Top N analysis, device CPU/memory usage, link utilization and interface up/down. LiveAction also supports NCCM via Netline Dancer integration and provides performance baselining and capacity planning via Flow, SNMP and IP SLA. As for Security, LiveAction can recognize DDoS-like behaviors and allows customers to create an access-list on-the-fly to block malicious traffic.

LiveNX specializes in application and network performance with QoS Control. It offers alerting, visual path trace and another color-coded status for fault management, but no syslogging. It also provides network health functionality including network discovery and topology, network monitoring using NetFlow, IPFIX, SNMP, QoS, routing and LAN statistics, dashboard, Top N analysis, device CPU/memory usage, link utilization and interface up/down. LiveNX also supports NCCM via Netline Dancer integration and provides performance baselining and capacity planning via Flow, SNMP and IP SLA. As for Security, LiveNX can recognize DDoS-like behaviors and allows customers to create an access-list on-the-fly to block malicious traffic.

Cisco suggests using a hierarchical policy since there are no hard bandwidth limits associated with the subinterface.

You can create a “shaping” policy in LiveAction and set a shape value to the “class-default” as in the screenshot below:

faq_qos-settings-13

Notice the policy called “shape-a” is setting a shaping policy of 10Mbps. Then, drag another policy under class-default, as shown below:

faq_qos-policy-14

Here is an example of the config using a policy called “a” and how it is associated with the hierarchical shaping policy called “shape-a”. It is then tied to a Gig subinterface in our lab setup.

policy-map a
class a
bandwidth percent 80
class b
class c

policy-map shape-a
class class-default
shape average 10000
service-policy a

interface GigabitEthernet0/1.101
encapsulation dot1Q 101
ip address 10.2.1.1 255.255.255.0
ip nbar protocol-discovery
ip flow ingress
ip flow egress
no cdp enable
service-policy output shape-a
end