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

NSX Network Detection and Response: How to configure the analysis upload size limit on the Manager and Sensor (900100)

Last Updated: 3/31/2023Categories: InformationalTotal Views: 1311Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

By default, the Sensor appliance only uploads attachments that are within a specific megabyte limit. Depending on when you installed the sensor, the default values may differ. In earlier software versions, we had a default 8MB limit. In more recent versions, the default limit was set to a 20MB limit. It is possible to increase the maximum size of an attachment we analyze as defined in the below maximums.

Important: In very old installations, there was an option to increase the max file size via an override.yaml entry, this is no longer required as this article allows the steps to be performed via the lastline_setup utility.

Solution

Please follow the below instructions to adjust the default file size maximum on the Manager or Sensor appliances.

Manager (also described in the Manager installation manual https://user.lastline.com/install-manuals/Manager_Installation_Manual.html#uploadsize ):

Log into the Manager using either console or SSH.

Run lastline_setup

Use analysis_max_upload_filesize_mb to set the max file size the system can analyze. For example, analysis_max_upload_filesize_mb 20 will set the max file size to 20MB.

Use save to save the change.

Sensor:

Log into the Sensor using either console or SSH.

Run lastline_setup

Use sensor_max_upload_filesize_mb to set the max file size the sensor can upload. For example, sensor_max_upload_filesize_mb 20 will set the max file size to 20MB.

Use save to save the change.

Now your system should start analyzing attachments up to 20MB.

Note: The sensor will display "sensor_max_upload_filesize_mb = None" - the value of "None" shows by default and  means this has not been changed from the default (either 8MB or 20MB) but is not displayed.

Maximum values allowed:

For  On-premise NSX Lastline Defender deployments, The maximum file size allowed is 100MB. Can be configured between 10 and 100.

For  Hosted NSX Lastline Defender deployments, The maximum file size allowed is 64MB. Can be configured between 8 and 64.

Related Information

Note: This article is applicable to the standalone NSX Network Detection and Response product (formerly Lastline) and is not intended to be applied to the NSX NDR feature of NSX-T.

Contact VMware Tech Support team if you need assistance or more information on this.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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