Size of nmap file

Usage and Config
1

(imported topic written by JRigas)

Hey all,

Is it possible to change the max size of a nmap file? Or will this give errors?

Default it is set to 8MB, but I have files that are a lot bigger (40MB).

setting 
"_BESClient_ArchiveManager_MaxArchiveSize"=
"8388608" on 
"{parameter "action issue date
" of action}" 

for client
2

(imported comment written by BenKus)

Its ok to make it bigger… but… why is it so bug? Are you scanning a very large subnet?

Ben

3

(imported comment written by JRigas)

Ben Kus

Its ok to make it bigger… but… why is it so bug? Are you scanning a very large subnet?

Ben

Yes, the customer where we’re scanning is using a subnet like 10.x.x.x.

I’ve tried to set the maxarchivesize limit, and it worked.

Only thing is the assets that were found are not showing up in the unmanaged assets tab.

Do I also have to change this?

setting 
"_BESClient_ArchiveManager_IntervalSeconds"=
"604800" on 
"{parameter "action issue date
" of action}" 

for client
4

(imported comment written by SystemAdmin)

You will edit this:

Code:

setting “_BESClient_ArchiveManager_MaxArchiveSize”=“20000000” on “{parameter “action issue date” of action}” for client

There are two instances, depending if your scan point is on Windos or Red Hat.

I have mine bumped up, and then I have a task to clean this directory every 14 days to keep it from getting to large.

5

(imported comment written by JRigas)

weberch

You will edit this:
Code:
setting “_BESClient_ArchiveManager_MaxArchiveSize”=“20000000” on “{parameter “action issue date” of action}” for client

There are two instances, depending if your scan point is on Windos or Red Hat.

I have mine bumped up, and then I have a task to clean this directory every 14 days to keep it from getting to large.

Thanks for the reply.

I did change it, and the task has run fine. It’s says “fixed” in the console.

Only the assets it found are not showing in the console.

Mind you, to scan this large subnet I’ve devided it into separate tasks, each task scans something like this: 10.1-6.0-254.0-254, another one 10.7-12.0-254.0-254 and so on.

I have also scheduled them, so one runs in the morning, and one in the afternoon.

There are in total 3 scan points with this kind of configuration to speed things up.

Is it possible to ‘manually’ import the xml files with the importer?

6

(imported comment written by kevin_friedheim)

Hi Jani,

Yes. You can manually import xml files by dropping the XML file in question into the folder Program Files\Bigfix Enterprise\BES Server\AssetDiscovery\Nmap_DataFolder

Note: You will need to create this folder if it doesn’t exist.

Then restart the UnmanagedAssetImporter service. The xml file should disappear from said folder, and added to the NMAP_ArchiveFolder.

It concerns me that your scans have completed but no computers are showing up – can you see the ‘completed’ scan xml files on your server in the NMAP_ArchiveFolder?

Check out http://support.bigfix.com/cgi-bin/kbdirect.pl?id=1623 for more information about how the importer works.

7

(imported comment written by JRigas)

Hey Kevin,

Thanks for your reply, I did however already found the nmap_datafolder in the BES server folder to ‘manually’ run it :slight_smile:

The scans were visible in the Temp\Nmap folder, not in the NMAP archive folder.

The original nmap files were quite large though (40MB +) and I think this was the reason why they weren’t being imported.

Because as soon as I deleted all the older files from the Nmap_ArchiveFolder, it worked again.

8

(imported comment written by kevin_friedheim)

Asset Discovery uses the TEM Archive and Upload Manager to push the NMAP scan files upstream to the server. You will need to tweak certain settings if you find that your scan files are larger than are allowable by the rules set by default for this Archive/Upload tool.

Check out http://support.bigfix.com/product/documents/Upload_Manager_70_090602.pdf – you’ll be interested in _BESClient_ArchiveManager_MaxArchiveSize

HTHs