NetXMS Support Forum

Hi all!

NetXMS version 1.1.0 released. It's a first version in 1.1.x branch. Please note that this is a development branch and generally not recommended for production use.
Changes from previous versions:

- Server jobs introduced
- Java API added
- Portable (Eclipse-based) management console introduced
- Server switched to UNICODE on Windows platform
- Windows x64 server version added
- MIB compiler improved
- Dropped agent support for Novell NetWare and Windows NT 4.0, 95, 98, Me

Best regards,
Victor

Hi!

I changed both setPassword and validatePassword to use UTF-8 instead of current server's page to calculate hash:


bool User::validatePassword(const TCHAR *password)
{
   BYTE hash[SHA1_DIGEST_SIZE];

#ifdef UNICODE
   char mbPassword[1024];
   WideCharToMultiByte(CP_UTF8, 0, password, -1, mbPassword, 1024, NULL, NULL);
   mbPassword[1023] = 0;
   CalculateSHA1Hash((BYTE *)mbPassword, strlen(mbPassword), hash);
#else
   CalculateSHA1Hash((BYTE *)password, strlen(password), hash);
#endif
   return !memcmp(hash, m_passwordHash, SHA1_DIGEST_SIZE);
}


void User::setPassword(const TCHAR *password, bool clearChangePasswdFlag)
{
#ifdef UNICODE
   char mbPassword[1024];
   WideCharToMultiByte(CP_UTF8, 0, password, -1, mbPassword, 1024, NULL, NULL);
   mbPassword[1023] = 0;
   CalculateSHA1Hash((BYTE *)mbPassword, strlen(mbPassword), m_passwordHash);
#else
   CalculateSHA1Hash((BYTE *)password, strlen(password), m_passwordHash);
#endif
   m_graceLogins = MAX_GRACE_LOGINS;
   m_flags |= UF_MODIFIED;
   if (clearChangePasswdFlag)
      m_flags &= ~UF_CHANGE_PASSWORD;
}


tested it on Russian, Chinese, and Japanese characters - works fine. This solution, however, will cause problem for already set non-latin1 passwords - they will need to be reset.

Changed code already commited to svn.

Best regards,
Victor

Hi!

Condition can have only two statuses - when it is active and when it is not active. Condition script expected to return true or false - if it returns true, condition considered as "active", and it's status changed appropriately.

For your case, I see the following solution (not very elegant though):

1. On nodes A and B, set status propagation to fixed value "Normal" - this will ensure that they will not change status of parent location directly;
2. Create 2 conditions in same location, each having DCI Status for node A and node B as data (A Status first).
3. For condition 1, set active status to "Minor" and inactive to "Normal", and use the following script:

($1 == 4) && ($2 == 0)


3. For condition 1, set active status to "Major" and inactive to "Normal", and use the following script:

($1 == 4) && ($2 == 4)

Should work

Best regards,
Victor

Hi!

Currently there are no reporting engine built into NetXMS. You should either use third part reporting tools or write your own export tool in C or Java.

Best regards,
Victor

A kak vigljadit konfig agenta na teh mashinah, kotorie ne rabotajut? I sam service agenta zapuschen pri etom? Esche mozno poprobovat' zapustit' agenta s komandnohj stroki v debug rezime:

nxagentd -D 9

Hi!

What is A, B, and "Location" - containers? If you need to calculate status of Location based on statuses of subcontainers A and B, the beset way is to use status calculation/propagation rules. If this is the case, tell me what statuses could have A and B, and I'll try to create rules for your requirement.

Best regards,
Victor

As I found in log, interface Vl1 has IP address 172.30.1.25, and interface eth0 on management server has same address. This cause NetXMS server to interpret switch as local machine.

Looks like management server has the same IP address as on one of 6509 interfaces. Could you check it? Does NetXMS server has only one IP?

Hi!

Looks somehow similar to this bug: https://www.netxms.org/bugtrack/view.php?id=319. Could you please run server in debug mode (by adding -D 6 switch to netxmsd command line) and send me the logs (either here or to dump-at-netxms.org)?

Also, question to all readers: does anybody has Cisco device in a lab with such big number of ports and able to provide me with remote access to it for some days? My best Cisco device has only 24 ports, and I can reproduce such problem (either described here or listed in the bug record) on big Nortel switches

Best regards,
Victor

You should put all files from the archive into src/nxmibc directory (replacing existing files) and run command make (assuming you still have configured source tree). If you remove sources you have built NetXMS from, you need to unpack them again, replace files, and then run ./configure and make as usual. If build will be successful, run make install to put resulting binary to appropriate place.

Best regards,
Victor

Attached. Patch file contains modified parser.l and parser.y from src/nxmibc directory, and in case you don't have flex and bison resulting C files.

Compilation is not cumulative - each time nxmibc reads all presented source MIBs and generate compiled file, erasing previously created one, if any.

Best regards,
Victor

Hi!

I run MIB compiler against Cisco MIBs from location you provided. Some of the MIBs really contains errors, but most compiler errors are bugs in nxmibc. I have fixed them, next release will contain improved MIB compiler. If you need, I can post a patch for MIB compiler here.

Best regards,
Victor

Добрый день!

Нет, функций инвентаризации в NetXMS нет. В Википедии неверная информация.

Про Wiki - попробую, вроде существует дополнение к OpenOffice для публикации документов в Wiki.

В серверных командах можно использовать серверные макросы, как в событиях или алармах. Для передачи IP адреса надо использовать %a, например

/usr/local/bin/nxsnmpset -c private -t INTEGER %a .1.3.6.1.4.1.259.6.10.94.1.7.3.0 3

С динамическими адресами пока довольно плохо. Можно делать discovery и искать вновь появившиеся адреса, но это не совсем то.

По поводу NAT - сервер подключается к агентам, поэтому один прокси на сеть скорее всего понадобится.