NetXMS Support Forum

Hi,

no, only one group per DCI is possible.

Best regards,
Victor

В версии 2.1 группировку на performance tab изменили - теперь группируются все DCI с одинаковым значением в поле group. Это было сделано для устранения проблем с группировкой при наложении шсблонов и instance discovery. Процедура обновления базы должна была расставить для существующих привязок автоматически сгенерированые названия вида ## и идентификатор основного DCI. Поле должно быть редактируемым. Я перепроверю у себя что его можно менять.

Hi,

grouping was changed in 2.1 - now UI will group all DCIs with same group ID (which is just free form text). This solves various issues with setting up grouping in templates and for instance discovery DCIs. Upgrade procedure expected to replace existing mappings with ## followed by ID of root DCI - so they should be grouped as before. To fix that you can just enter matching group identifiers for all DCIs that should be grouped.

Best regards,
Victor

Hi,

try to change <agent> tag to <core>.

Best regards,
Victor

Hi,

default templates re-imported from file system on server startup. You can disable this behavior by setting server configuration parameter ImportConfigurationOnStartup to 0.

Best regards,
Victor

Yes, console needs at least Java 7. Strange that it starts at all. I'll check that.

Best regards,
Victor

Can somebody please run upgrade with -t option and post output? Also, content of failed table before upgrade could be helpful.

Best regards,
Victor

Hi,

tdata tables holds table DCI values, so you should check your table DCIs. If you don't use them then everything should be fine.

Best regards,
Victor

Hi,

it should be safe. I recommend to backup database before upgrade though nxdbmgr upgrade should handle everything, and if you are using Windows installer, it will be handled by installer.

Best regards,
Victor

In 2.1 user admin is an ordinary user which gets it's access from "Admins" group. Login with user "system" (it is superuser that always has full access) and check that "Admins" group has full permissions (or give explicit permissions directly to user "admin").

Best regards,
Victor

Hi,

seems that global permissions was not updated during upgrade. In 2.1 we introduce alarm categories, and new global access right "access to all alarm categories" which should be enabled for all users to keep behavior compatible with 2.0. Make sure your user/group has this access right set.

Best regards,
Victor

Hi,

try to upgrade to 2.1 if possible.

Best regards,
Victor

Using same version as server will always work. Other versions may or may not work - protocol version may stay the same between product versions. Usually if you got this error that means that your client is too old and you just upgrade to version matching your server version.

Best regards,
Victor

HI,

check that your user/group has global permission "access all alarm categories".

Best regards,
Victor

Hi,

what was exact error message?

Best regards,
Victor