NetXMS Support Forum

Yes, export - copy - import  is another option. It may not work well on large databases though (because of space requirements, extra time to write export file, and on some systems hitting file size limit).

Best regards,
Victor

Yes, you create script in library and then create script DCI specifying this script as parameter name. For testing you can select any container, right click and select "execute server script". You can also add print or trace calls to provide diagnostic. You have to use * as wildcard in FindAllDCIs call.

Best regards,
Victor

Hi,

just commented in the issue.

Best regards,
Victor

Quite strange, I don't see anything wrong with the data. Could you please make it crash under debugger again, and then do the following commands:

bt
print module
print *module
print row
print column
print *var
print *request
print *response

Best regards,
Victor

Список квот можно возвращать как External Parameter. DCI с объединенной историей - сделать script DCI который будет собирать данные с индивидуальных квот и возвращать сумму. Чтобы сделать два параметра на одном графике надо делать два отдельных DCI.

Тогда похоже на то, что карта не сохраняется корректно в базе и после рестарта перестраивается. Проверьте содержимое таблиц network_maps и network_map_elements - там все элементы будут сохранены?

Hi,

currently you should enable duplicate detection - that will not prevent duplicate node creation, but they will be deleted shortly after. We are currently working on improving parallel discovery and earlier duplicate detection.

Best regards,
Victor

Hi!

If I correctly identified devices it seems that they have management IP address and mask in private MIB: http://www.circitor.fr/Mibs/Html/R/RADWIN-MIB-WINLINK1000.php#winlink1000OduAdmAddres. Can you check if this MIB is supported and that device returns correct information? If yes then we cn create driver that will utilize private MIB to create management interface object.

Best regards,
Victor

Hi!

If you need just one number for total disk space then best approach would be script DCI that will enumerate all servers and add up used disk space. Possible script implementation is following:


// Find "Entire Network" object and start enumeration from it
global TOTAL = 0;
EnumerateNodes(FindObject(1));
return TOTAL;

// This function walks object tree recursively starting from given root
sub EnumerateNodes(rootObject)
{
// Walk all child objects
foreach(o : GetObjectChildren(rootObject))
{
if (classof(o) == "Node")
{
// Process node object
            for(d : FindAllDCIs(o, "FileSystem.Used(*)"))
            {
                v = GetDCIValue(o, d->id);
                if (v != null)
                {
                    TOTAL += v;
                }
            }
}
else
{
// For all other objects, go down the tree
EnumerateNodes(o);
}
}
}


You should select right top level object for enumeration. Also this script does not check if same node encountered multiple times - so you either have to pass such rot object under which each node bound exactly once, ar add additional check to avoid duplicates.

Best regards,
Victor

Hi,

you may need to use instance discovery.

Best regards,
Victor

Hi,

from version information for the client it seems that client is of much older version. Make sure that you have deployed new version correctly. You can see web client version on login screen in bottom right corner.

Best regards,
Victor

Could you please also show walk output for .1.3.6.1.4.1.9.6.1.101.53.3.1.6 and .1.3.6.1.4.1.9.6.1.101.53.3.1.7?

Best regards.
Victor

Hi,

could you please run netxmsd under gdb (with Cisco driver back) and when it crashes show output of bt command. You'll need to install -dbg packages if you installed NetXMS from deb packages.

Best regards,
Victor

In source config on new machine specify address of old server in DBServer. You may need to enable Postgres connections from new machine in pg_hba.conf on old machine.

Best regards,
Victor

Hi,

it is not necessary that both databases are local for nxdbmgr migrate - both just should be accessible from the machine where you running migration tool. Usually it's better to run migration on destination (new machine) - then you can create correct netxmsd.conf for use by new server, copy netxmsd.conf from old server under different name or path, change it so that DBServer points to old database server, and run nxdbmgr migrate.

Best regards,
Victor