What are the recommended server specifications?

Number of Devices (routers/switches) Monitoring Recommended Server Specifications
Less than 100 devices (routers/switches) and less than 100K Flows/sec
  • 8 Virtual Core 2+ GHz CPU
  • 8 GB RAM
  • 2-6 TB 7,200 RPM HD*
500 devices (routers/switches) and less than 200K Flows/sec
  • 16 Virtual Core, 2+ GHz CPU
  • 16 GB RAM
  • 8-16 TB 7,200+ RPM HD*
*Depends on flow rate from devices and retention time. For higher performance use RAID 10 or RAID 0 if redundancy is not required.


Node and Server Hard Drive Sizing
Avg flow rate (K flows/sec) < 25K/sec < 100K/sec < 200K/sec > 200K/sec
Approx. monthly drive usage (TB) 0.5 2 3 5
Recommend drive size (TB) 2 6 10 10
  • Local drive preferred
    • Minimum equivalent to SATA 6 Gb/s performance
    • 7,200 RPM base or 10,000 RPM for better performance
    • RAID 10 for better performance
    • SSD for better performance
  • SAN and NAS
    • Meet performance and latency specification of local drive
    • Support sustained writes at high speed
    • Support sequential reads at high speed for sequential blocks

Back to top ^

What types of Operating Systems will LiveAction work on?

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

Back to top ^

How do I activate my LiveAction license?

You can either do online or offline activation of your license:
Online Activation:
  • From the Management Console License Tab, select Activate License to start the License Activation Assistant.
  • Select Activate Online, then click Next.
  • If your server is directly connected to the Internet, select Direct connection. If your connection to the Internet is through a proxy server, select Use proxy. Contact your administrator for your Proxy information, if necessary. Click Next.
  • If connection is successful, the Activating License screen will appear. Click Finish to complete license activation.
Offline Activation:
  • From the Management Console License Tab, select Activate License to start the License Activation Assistant.
  • Select Activate Offline, then click Next.
  • The License Number and Activation key will be displayed. This information must be sent to LiveAction to complete offline activation. Click Copy to store the information to the Windows clipboard and paste it into a text file to send to the LiveAction License Team.
  • Click Cancel to exit the License Activation Assistant. You can continue to use the software for up to seven days prior to completing the activation process.
  • Using another computer that has an Internet connection, e-mail your contact information and the saved License Number and Activation key to sales@liveaction.com. LiveAction will then process your license and send you a permanent key for the next step.
Load the Activation Key you received from LiveAction.
  • When you receive your new Activation Key file, copy it to a location that can be reached by the LiveAction server PC.
  • Start the Management Console and select the License tab. Select Upgrade License to restart the Licensing Assistant.
  • Select I have a valid license file¸ and then click Next.
  • On the License Location screen, browse to locate the Activation Key file that you saved. Click Finish to complete license activation

Back to top ^

How do I start LiveAction Client through a Java Webstart?

    • Make sure your LiveAction server is running.
    • Open a web browser and connect to your LiveAction server by typing the IP address followed by a colon “:” and the port number of the server start page (default=”8092”) as the URL. For example:
      • http://
      • or http:// localhost:8092/ if trying to run the client on the same PC as the server.
      • If “httpserver.secure” is specified “true” in the LiveAction Management Console, the URL must specify https as shown below:
    • Click the link Launch LiveAction Client and accept the Java Webstart installation. 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 LiveAction login prompt.
    • If this is your first time logging into the LiveAction Client, login into the default administrator account and create users. The initial default admin credentials are as follows:
Username: admin
Password: admin

Back to top ^

How do I export LiveAction logs for support?

  • From the Management Console:
    • Help –> Export Logs
  • Select the file export location (choose Desktop for convenience) and send the logging zip file to LiveAction Support.

Back to top ^

How do I save my configuration?

From the Management Console, click Manage and select Export Configurations. You can then reload them at a later time by selecting Import Configurations.

Back to top ^

How do I reinstall LiveAction?

Be sure to export the LiveAction configuration

  • Close the LiveAction client and stop the service.
  • Uninstall the old version of LiveAction.
  • Install the new version of LiveAction (your previous license should be found).
  • LiveAction should be installed. If your data directory is in the default location (“C:\LiveAction Server Data\2.x”) and you are simply reinstalling, the app should find your previous data automatically.

Back to top ^

How do I migrate LiveAction to a new server?

Follow the following instructions on how to migrate LiveAction from your current server:
Initial considerations
  • Please ensure that you have your license key.
  • Best practice: Have a backup admin account for LiveAction that is not used in case the primary account gets locked out.
On the old server:
  • Close the LiveAction client.
  • Deactivate the LiveAction license using the Management Console.
  • Stop the service (using the Management Console)
  • Make a backup copy of the following directories to migrate the LiveAction database to the new server (if the historical data is not necessary this step can be skipped):
    • C:\LiveAction Server Data\2.X\cassandra
    • C:\LiveAction Server Data\2.X\netflow (for 2.5+, flowstore)
On the new server:
  • Apply and activate the license on the new server
  • Import the previously saved LiveAction configuration file using the Import tool.
  • Close the LiveAction client and stop the service (using the Management Console).
  • In version 2.5x and higher – copy the previously backed up “cassandra” and “flowstore” directories to the new server.
  • Restart LiveAction on the new server.

Back to top ^

How do I change my default data directory

By default, LiveAction uses the following directory to store database and configuration files used by the application (referred to as “data directory”).
Default location:
C:\LiveAction Server Data\2.x
Steps to change the LiveAction Data Directory location:
As a precaution and back-up, export the LiveAction configuration.
  • Shut down the LiveAction application and the LiveAction service (using the management Console).
  • Copy the files in your current data directory to your new data directory location.  This will retain your current settings (i.e. topology layout and device settings).
  • Use the Management Console – Properties tab to change the data directory used by LiveAction (app.datadir property). This will edit the application.properties file. Please note the verbiage on the dialog regarding the new location having full read/write access by the LiveAction service.
  • Restart your LiveAction Server and Client.


Back to top ^

What should I do if I get a serial number validation error?

We noticed strange cases in the past where the serial number of a device changes when the IOS is upgraded. Please contact customer support at http://LiveAction.com/support and we will try to resolve your problem. Here are some questions that would help us get back to you quickly:
  • What version of LiveAction are you using?
  • Export the device information by doing the following:
    • Right click Home and Export Data.
    • Please send the .csv file and the serial number of the device in question.
  • Export the log files by doing the following:
    • From the Management Console, click Help –> Export Logs
    • Please send us the .zip file.
  • Are you running the following command on your devices to possibly set the serial number manually?
    • “snmp-server chassis-id <custom-serial-num>”

Back to top ^

What do I do if I am locked out of my account?

You can reset your password through another admin account, if there is one available. Otherwise, you can do the following:
  • Stop the LiveAction service
  • Rename the “server.conf” file to a backup name (i.e.: “server_backup.conf”) in your data directory.
    • Default Data Directory: C:\LiveAction Server Data\2.x
  • Backup the “C:\LiveAction Server Data\2.x\topology-layouts” directory to save your topology.
  • Restart the LiveAction service with the management Console.Restart the LiveAction client.
  • Setup a new admin account.
  • Re-add your devices
  • Close the LiveAction client and stop the LiveAction service
  • Restore the “topology-layouts” directory and the files within (overwrite with the backed up files if necessary).
  • Restart the LiveAction service and client.  (Note: you may need to adjust the interfaces assigned to each router).
It is highly recommended to create a secondary admin account that you will not use regularly, as a backdoor.
As a suggestion you may also want to adjust the user management settings here:
  • Tools –> Options –> Security
  • Raise the number of failed consecutive login attempts


Back to top ^

Does LiveAction allow local authentication alongside LDAP?

LiveAction does allow local authentication alongside LDAP. If you are planning to migrate to LDAP and would like to test it with LiveAction please ensure to export the configuration.

Back to top ^

How can I get LDAP to work with LiveAction using Microsoft AD?


  • Open the LiveAction User Management


  • Create LiveAction users that correspond to LDAP users
  • Select Allow LDAP Authentication, and click the Settings button
  • Set the LDAP Authentication Mapping to match the result of the command “dsquery user” executed before.

For Example: If you see “CN=First Last,CN=Users,DC=company,DC=local”, your Base DN in LiveAction should be “cn=Users,dc=company,dc=local”. Map user to cn, and the Base DN is everything in the dsquery output after “cn=<username>”.

Base DN: cn=users,dc=sdfqa,dc=com

Map User to: cn


  • Click the Test Settings button, and enter your username and password. Your username is the full name configured in Active Directory, not the “login” name


  • If you have issues with getting LDAP to work, you can import the previously backed up configuration file to revert back to local authentication.

With Active Directory LDAP, it is important to use the user’s Display Name, instead of the actual account name. You can verify this information by running the “dsquery user” command, or by looking at the account properties. The Display Name will be the login credentials used for LiveAction, when LDAP authentication is enabled.

The red bordered login name will not work, during the LDAP test; while the green bordered login name will work.

Back to top ^

How many users can connect to a LiveAction server?

You may have a total of ten active sessions connecting to a LiveAction 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.

Back to top ^

Why is LiveAction not working after moving my VM to another machine?

One possible reason is that the LiveAction license was still activated on the original computer the VM was on before it was moved. If this was the reason, stand the image back on the server it was on and perform a license deactivation. You should then be able to reactivate of your license in the new location of the VM.

If the problem still persists, please contact customer support.

Back to top ^

I am not seeing NBAR Application statistics in the QoS interface view. Why is that?

There is a known bug found in IOS 15.0 and higher where the CISCO-NBAR-PROTOCOL-DISCOVERY-MIB is not populating NBAR application statistics (Cisco IOS bug ID: CSCty56850).
The following IOS versions fix this bug: 
15.2(4)S – available in CCO now
15.2(4)M1 – available in CCO now
15.2(3)T2 – will be available after 10/12/2012


Back to top ^

What is best practice when applying a QoS policy to a sub interface?

Cisco suggests using a hierarchical policy since there are no hard bandwidth limits associated with the sub interface.
You can create a “shaping” policy in LiveAction and set a shape value to the “class-default” like in the screenshot below:

Notice the policy called “shape-a” is setting a shaping policy of 10Mbps. Then drag another policy under class-default – in this case
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 sub interface 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
ip nbar protocol-discovery
ip flow ingress
ip flow egress
no cdp enable
service-policy output shape-a


Back to top ^

I don’t think I’m seeing any NetFlow data on my device but am not sure. How can I verify this?

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

  • Flows should be coming in on port 2055, unless changed in the Management Console.
  • LiveAction 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.
  • If seeing strange NetFlow data or collisions please see: I am seeing strange flow data for various advanced NetFlow data

Back to top ^

I am seeing NetFlow data intermittently or the data looks strange for various advanced NetFlow features (for example — Medianet, AVC, PfR). Why is this happening?

If you are running Traditional NetFlow (TNF) and Medianet performance monitoring or other Flexible NetFlow (FNF) based technologies at the same time, there could be NetFlow version 9 template collisions. This is because FNF and TNF are not aware of each other. As a result, both technologies will assign template IDs to their records starting from template id 256. This will cause NetFlow template collisions resulting in strange data being displayed in LiveAction.
A. Set TNF (Traditional NetFlow) export version to NetFlow version 5:
ip flow-export version 5


B. Use only flexible NetFlow-based configurations on the device to allow flexible NetFlow to manage all the templates and remove traditional NetFlow. Please find the example config below.

Example Flexible NetFlow config:
flow exporter LIVEACTION
source Loopback 201
transport udp 2055
template data timeout 60
flow monitor IPV4FLOW
record netflow ipv4 original-input
cache timeout inactive 10
cache timeout active 60
interface Gig0/0
ip flow monitor IPV4FLOW input
ip flow monitor IPV4FLOW output
The above example will result in the same data as the following traditional NetFlow config:
ip flow-cache timeout inactive 10
ip flow-cache timeout active 1
ip flow-export source Loopback201
ip flow-export version 9
ip flow-export template timeout-rate 1
ip flow-export destination 2055
interface Gig0/0
ip flow ingress
ip flow egress

Back to top ^

Do you support NX-OS products?

Yes, we support NX-OS from a Flow perspective today and we will continue adding more NX-OS support in the future.

Does LiveAction support non-Cisco devices?

We support flow analysis for non-Cisco devices, for example Alcatel, Extreme, Brocade, Hewlett-Packard, Juniper, NetVanta, nProbe.

How are devices discovered by LiveAction?

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

Is there a limit of to the number of interfaces LiveAction supports on one device?

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 have been enabled.

When you save CLI configurations to the device how is LiveAction communicating with the device?

It is through SNMP and Telnet/SSH.

Can LiveAction schedule periodic reports?

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

Can I customize my dashboard with LiveAction?

Yes, you customize your dashboard by dragging different reports into a user-defined dashboard.

Does LiveAction support historical routing data?

We save raw data for flow and snmp for replay/rewind/fast-forward via our Flow DVR feature, but no historical routing table data.

Does LiveAction support foll FCAPS (Fault, Configuration, Accounting, Performance, Security) management?

LiveAction specializes in application and network performance with QoS Control. It offers alerting, visual path trace and other 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, interface up/down. LiveAction also support NCCM via Netline Dancer integration. LiveAction provide performance baselining and capacity planning via Flow, SNMP, and IP SLA. On Security, LiveAction can recognize DDoS-like behaviors and allows customers to create an access-list on-the-fly to block malicious traffic.

How many devices can a LiveAction server handle?

Prior to LiveAction 4.0, each server can manage up to 500 devices. Thus, for networks of more than 500 devices, multiple servers would be needed, each having its own network view and license. Beginning with LiveAction 4.0, we can support large- scale enterprise networks up to 40,000 devices with a single-pane-of-glass view across the entire network and one license since the devices are being monitored via the collector nodes which provide horizontal scaling and report to the server.

How long does LiveAction save the raw data for?

One of LiveAction’s unique feature is that it saves all the raw data as long as there is disk space. You can limit the data storage by setting disk utilization warning and purging parameters under “Tools”, “Options”, “Database”.

With the new 3-tier architecture of application, node, server in LiveAction 4.0, what is the increase of latency given the new “extra hop” between the endpoint device and the head end server? How long does the node collector hold onto information before sending it up to the head end server?

There is minimal additional latency with this model. The Server pulls data from the Node(s) on an as needed basis.

What is LiveAction’s flow rate?

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

Other questions or concerns?

You may contact us at http://LiveAction.com/support with any questions or concerns that you may have.

The technical support engineer may ask to see the LiveAction log files.