Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How To Check If a NSX Lastline Sensor Is Working Correctly Including Log File References (900015)

Last Updated: 10/15/2019Categories: How toTotal Views: 1102Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

Problem

How do I identify if the traffic is scanned properly?
How do I check if the span port is clean and seeing all the traffic that it should?

Resolution

Solutions

1. Run lastline_test_appliance.
There are a number of tests in lastline_test_appliance that sniff all the connected sniffing interfaces and analyze the quality of the traffic to identify common problems.

Login to the monitoring console on the appliance and type in the command lastline_test_appliance at the shell prompt.

2. Check the Monitoring Logs in the UI
There is a software component running on the Sensor called llwatchdog that performs periodic checks on the state of all the critical Sensor components and reports their status in the appliance monitoring logs. Sensors running up-to-date software will report warnings in the Monitoring Logs if, for example, Suricata (our IDS) is not receiving traffic.

You can find the appliance Monitoring Logs in the Portal GUI by going to Admin -> Appliance -> Quick Links -> Monitoring Logs

3. Review Logs
If it is necessary to look deeper into a problem, you may need to check additional log files. Reviewing log files to troubleshoot the Sensor comes with this caveat. Log files are not part of the officially supported software. We do not intend to maintain backwards compatibility or documentation on them. A Sensor upgrade may change these logs or their formats at any time.

Suricata operation (rule parsing warnings, rule reloads, restarts, ...)
/var/log/suricata/suricata.msg

llpsv operation (daemon restarts, ...)
/var/log/llpsv/llpsv.INFO

Archive of recent artifacts extracted and processed by Suricata. Not all artifact types are archived there, especially NTA logs, as this would cause too much I/O load. The NTA pipelines are exclusively in memory.
/var/lib/suricata-eve/archive/suricata-lastline/*

Reputation alerts on plain IPs/domains
/var/log/llpsv/llpsv.log

Operation of the mail component
/var/log/llmail/email/*.log

Operation of the ICAP daemon (custom log format with more metadata)
/var/log/c-icap/processing.log

Logs of the file processing pipeline invoking the prefilter (used by sniffing and ICAP; not mail)
/var/log/llfd/llfd_worker?.log

Logs of the daemon that is in charge of performing the uploads of all the data generated by the Sensor as it transfers the data to our Hosted backend or an On-Premises Manager. This log may be helpful in troubleshooting in only a handful of very specific cases.
/var/log/llshed/*

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE Boxer 21.06 for iOS での [タスク] ボタンおよびフォルダの廃止 (84470)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX Detonator

VMware NSX Defender

Related Versions:

Take Our Survey

Support Assistant