NetXMS Support Forum

Theoretically, server should do that automatically if it knows route from itself to nodes behind router. However, it often not working as expected. You can also do manual correlation using situations.

Best regards,
Victor

Hi!

Automatic map population is not implemented yet. Only manual maps are working. I hope to fix that in 1.2.4.

Best regards,
Victor

Quote from: bdefloo on October 10, 2012, 05:34:24 PM
Sounds great. By "extendable", you probably mean by editing the source code of the console?

Yes. As console is actually a set of plugins, additional plugins can register it's own double click handlers.

Quote from: bdefloo on October 10, 2012, 05:34:24 PM
The problem with Object Details is when a different window is in front of it; like a graph, configuration window or the alarm browser. The object browser is still visible to the left, but clicking in it won't seem to change anything.

I have the intuition that the object browser and object details pretty much belong together, similar to when you click a code file in the project explorer in Eclipse you expect the code editor for that file to come to the foreground.

Now I'm understand. Then it's probably must be made configurable, because somebody (me for example) may still wish to expand a node to see interfaces by double click. Btw, I can also add a keyboard shortcut for object details view.

I was mean that I just implemented that. So it will be available in 1.2.4 release

Hi!

I have implemented extendable "open" function in object tree. By default double-clicking on object in the tree will expand/collapse it, unless this action is redefined. So far it's redefined for network maps and dashboards - double click on them will open appropriate view. Object details shows data for currently selected object in object tree, so I don't see how double click will help there. Using CTRL and SHIFT keys as click modifiers is problematic, as they already used for selecting multiple items. I'll try to implement "alternative open" by double click with ALT key. Line graph by double click is on the way.

Best regards,
Victor

Hi!

There are startup files in source tree under contrib/startup/redhat. Copy netxmsd and nxagentd to /etc/init.d, and run

chkconfig --add nxagentd
chkconfig --add netxmsd

to enable autostart.

Best regards,
Victor

Hi!

That means that agent returns an error. Can you get other parameters from same agent? Also check for any errors in agent's log.

Best regards,
Victor

Quote from: SKYnv on October 05, 2012, 06:17:10 PM
src\server\core\main.cpp

Code Select Expand

for(int i = 0; i < vlans->getSize(); i++)
{
VlanInfo *vlan = vlans->get(i);
ConsolePrintf(pCtx, _T("%4d | %-16s |"), vlan->getVlanId(), vlan->getName());
for(int j = 0; j < vlan->getNumPorts(); j++)
ConsolePrintf(pCtx, _T(" %d.%d"), (int)(vlan->getPorts()[j] >> 16), (int)(vlan->getPorts()[j] & 0xFFFF));
ConsolePrintf(pCtx, _T("\n"));
}

если порты идут в формате 1/portNum то в данном месте

Code Select Expand

(int)(vlan->getPorts()[j] >> 16), (int)(vlan->getPorts()[j] & 0xFFFF));
они все станут 0.0 0.0

Quotenetxmsd: sh vl 2738
VLAN | Name             | Ports
-----+------------------+-----------------------------------------------------------------
   1 | default          | 0.0
   3 | vlan3            | 0.0 0.0
   4 | vlan4            | 0.0 0.0
   5 | vlan5            | 0.0 0.0
   6 | vlan6            | 0.0 0.0
   7 | vlan7            | 0.0 0.0
   8 | vlan8            | 0.0 0.0
   9 | vlan9            | 0.0 0.0
  10 | vlan10           | 0.0 0.0 0.0

Вроде так )))

0.0 они становятся скорее всего из-за отсутствия драйвера для сетевого устройства. Без драйвера сервер не знает, какие интерфейсы являются физическими портами, а какие нет, поэтому у всех интерфейсов номер слота и порта выставлены в 0.

Можно использовать PING субагента для мониторинга - он выдает время ответа и количество потерянных пакетов. Соответственно средствами NetXMS сервера уже можно отслеживать резкие изменения во времени ответа. Конечно это будет статистика по ICMP, но в большинстве ситуазий она даст представление о примерном состоянии каналов. Конкретные данные по VoIP трафику надо снимать уже с VoIP устройств.

Yes, crash dump will be extremely helpful.

Best regards,
Victor

Hi!

I agree that alarm separation could be useful. I see that it can be done that way: introduce new entity - alarm category, and on alarm creation (in event processing policy) add the ability to set category for alarm. Then users will be able to filter/group alarms by categories, and access control can be enforced on category level (i.e. do not define access rights for each alarm, but for category).

Best regards,
Victor

Hi!

I fixed that, next release will support basic command editing in remote console. Another workaround is to close console tab and open it again

Best regards,
Victor

Quote from: sabonez on October 05, 2012, 09:14:21 AM
СМС-ки вроде в UCS-2.

SMS с русскими буквами можно посылать только в PDU режиме насколько я понимаю. Кроме того, сам сервер должен работать в UNICODE или code page должен быть выставлен в CP-1251.

Quote from: sabonez on October 05, 2012, 09:14:21 AM
База у меня в 1251, с utf-8 почему-то java-console под вендой не задружилась - резала русские имена. Если это как-то лечится, может есть смысл конвертнуть базу в UTF?

Здесь скорее проблема с самим сервером, а не с базой. Проверьте что параметр CodePage в netxmsd.cond выставлен в CP1251, или попробуйте UNICODE сборку сервера.

Я сталкивался с проблемами со скоростью порта. Generic SMS драйвер по умолчанию пытается работать на 9600. Попробуйте поставить скорость побольше - 38400 или выше, и проверьте что в настройках самого виртуального порта тоже эта скорость стоит (это для Windows актуально, про Linux не знаю).

Quote from: SKYnv on October 03, 2012, 08:13:43 AM
это нормальная работа?

Quotenetxmsd: sh po
PT  TIME                   STATE
S   03/Oct/2012 11:02:42   wait
S   03/Oct/2012 11:03:01   poll: M_Uz_Zarech_16 [5464] - wait for lock
S   03/Oct/2012 11:02:42   wait
S   03/Oct/2012 11:02:59   wait
S   03/Oct/2012 11:01:10   poll: 192.168.1.33 [7713] - wait for lock
S   03/Oct/2012 11:00:35   poll: 192.168.1.33 [7683] - wait for lock
S   03/Oct/2012 11:03:16   wait
S   03/Oct/2012 11:02:50   wait
S   03/Oct/2012 11:00:40   poll: 192.168.1.33 [7701] - wait for lock
S   03/Oct/2012 11:00:15   poll: 192.168.1.33 [7695] - wait for lock
S   03/Oct/2012 11:00:25   poll: 192.168.1.32 [7710] - wait for lock
S   03/Oct/2012 11:01:20   poll: 192.168.1.32 [7722] - wait for lock
S   03/Oct/2012 11:01:20   poll: 192.168.1.32 [7728] - wait for lock
S   03/Oct/2012 11:01:25   poll: 10.255.141.201 [114] - wait for lock
S   03/Oct/2012 11:00:55   poll: 192.168.1.33 [7719] - wait for lock
S   03/Oct/2012 11:02:56   wait
S   03/Oct/2012 11:00:35   poll: 192.168.1.33 [7731] - wait for lock
S   03/Oct/2012 11:02:58   wait
S   03/Oct/2012 11:02:51   wait
S   03/Oct/2012 11:00:45   poll: 192.168.1.32 [7692] - wait for lock
S   03/Oct/2012 11:03:12   wait
S   03/Oct/2012 11:03:11   wait
S   03/Oct/2012 11:03:10   wait
S   03/Oct/2012 11:00:40   poll: 192.168.1.33 [7725] - wait for lock
S   03/Oct/2012 11:02:42   wait
S   03/Oct/2012 11:01:10   poll: 192.168.1.32 [7698] - wait for lock
S   03/Oct/2012 11:01:05   poll: 192.168.1.32 [7680] - wait for lock
S   03/Oct/2012 11:02:55   wait
S   03/Oct/2012 11:00:45   poll: 192.168.1.33 [7707] - wait for lock
S   03/Oct/2012 11:02:40   wait
S   03/Oct/2012 11:01:05   poll: 192.168.1.32 [7704] - wait for lock
S   03/Oct/2012 11:00:45   poll: 192.168.1.33 [7677] - wait for lock
S   03/Oct/2012 11:02:42   wait
S   03/Oct/2012 11:02:41   wait
S   03/Oct/2012 11:00:25   poll: 192.168.1.32 [7716] - wait for lock
S   03/Oct/2012 11:02:56   wait
S   03/Oct/2012 11:03:06   wait
S   03/Oct/2012 11:03:10   wait
S   03/Oct/2012 11:00:55   poll: 192.168.1.33 [7689] - wait for lock
S   03/Oct/2012 11:03:01   wait
S   03/Oct/2012 11:03:01   wait
S   03/Oct/2012 11:03:16   wait
S   03/Oct/2012 11:00:25   poll: 192.168.1.32 [7686] - wait for lock
S   03/Oct/2012 11:02:56   wait
S   03/Oct/2012 11:02:56   wait
S   03/Oct/2012 11:03:08   wait
S   03/Oct/2012 11:02:45   wait
S   03/Oct/2012 11:03:01   poll: 192.168.1.146 [5696] - wait for lock
S   03/Oct/2012 11:02:48   wait
S   03/Oct/2012 11:03:05   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7704] - hook
C   03/Oct/2012 10:59:17   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7695] - hook
C   03/Oct/2012 10:59:51   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7683] - hook
C   03/Oct/2012 11:01:47   poll: 192.168.1.33 [7719] - hook
C   03/Oct/2012 11:02:22   poll: 10.255.141.201 [114] - hook
C   03/Oct/2012 11:01:47   poll: 192.168.1.32 [7722] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7686] - hook
C   03/Oct/2012 10:59:17   wait
C   03/Oct/2012 11:03:12   wait
C   03/Oct/2012 11:01:47   poll: 192.168.1.33 [7731] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7710] - hook
C   03/Oct/2012 10:59:30   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7698] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7707] - hook
C   03/Oct/2012 11:02:48   wait
C   03/Oct/2012 10:59:17   wait
C   03/Oct/2012 11:02:00   wait
C   03/Oct/2012 11:01:42   poll: 192.168.1.32 [7716] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7689] - hook
C   03/Oct/2012 11:01:42   poll: 192.168.1.33 [7713] - hook
C   03/Oct/2012 11:02:24   wait
C   03/Oct/2012 11:01:32   poll: 192.168.1.33 [7677] - hook
C   03/Oct/2012 11:01:47   poll: 192.168.1.32 [7728] - hook
C   03/Oct/2012 11:01:47   poll: 192.168.1.33 [7725] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.33 [7701] - hook
C   03/Oct/2012 11:01:36   wait
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7680] - hook
C   03/Oct/2012 11:01:37   poll: 192.168.1.32 [7692] - hook
R   03/Oct/2012 11:00:50   wait
R   03/Oct/2012 11:00:50   wait
R   03/Oct/2012 11:02:41   wait
...
T   03/Oct/2012 11:02:46   wait
T   03/Oct/2012 11:03:12   wait
T   03/Oct/2012 11:02:05   poll: 192.168.1.146 [5696]
T   03/Oct/2012 11:02:15   poll: 192.168.1.33 [7677]
T   03/Oct/2012 11:02:24   wait
T   03/Oct/2012 11:02:05   poll: M_Uz_Zarech_16 [5464]
T   03/Oct/2012 11:03:06   poll: 192.168.1.32 [7686]
T   03/Oct/2012 11:02:41   poll: 192.168.1.32 [7680]
T   03/Oct/2012 11:02:48   wait
T   03/Oct/2012 11:02:51   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
B   03/Oct/2012 09:59:18   wait
A   03/Oct/2012 10:27:21   check

учитывая что ноды 1.32 1.33 были удалены сутки назад.

Нет, поведение ненормальное. Похоже, что зависли hook-скрипты по каким-то причинам. Сейчас думаю без рестарта сервера уже ситуация не поправится.