NetXMS Support Forum

Proboval povtorit' u sebja - vse rabotaet. V loge agenta (ili v sistemnih eventah) est' kakie-nibud' soobschenija ob oshibke? Esli vse chisto, ja sdelaju build s dopolnitel'nim debagom.

NetXMS supports topology discovery via CDP. The message "device does not support layer 2 discovery" is sometimes misleading, because it can be shown in case of other errors too. Check "Capabilities" box on overview page - there should be "Yes" in from of isCDP attribute.

Also, what version of server you are using?

Best regards,
Victor

Da, mozno, ispol'zuja macro %n. POlnij spisok dostupnih macrosov - v manuale v razdele 10.6.

I use 1.6.22. but any 1.6 will be ok.

Quote from: Billy on February 28, 2011, 02:04:41 PM
   another question is, in this java project,  whether the domain server is needed for the eclipse development environment?

Sorry, I didn't understand the question. What is the connection between domain server (what domain btw? DNS? Active Directory?) and Eclipse?

Best regards,
Victor

Hi!

You will require Maven and Eclipse 3.6. First, run "package" script from src/java directory - it will build client library using maven and put resulting jars into appropriate places. Then, import all projects under src/java/netxms-eclipse into Eclipse, find file nxmc.product under nxmc-core project, right-click on it and select "export". In export dialog, select "Eclipse product", press Next, and follow the wizard. If you wish just test something after changes in source code, you can run console directly from Eclipse by right-clicking nxmc.product and selecting Run As -> Eclipse Application.

Best regards,
Victor

Hi!

Yes, there was an error in the installer. I have uploaded updated version - please download it and try again.

Best regards,
Victor

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