NetXMS Support Forum

Hi,

currently screenshot requires read access. We can change it to separate access right in next release. I've added it as feature request: https://track.radensolutions.com/issue/NX-1147.

Best regards,
Victor

Hi,

try to use $dci->instance like this:


In = GetDCIValue($node, FindDCIByDescription($node, "Inbound traffic on " . $dci->instance . " (bits/sec)"));
[code]

Best regards,
Victor


Hi,

check that all users have access right "view all alarms" (which actually means "access to all alarm categories", we will fix the text). It should be granted either directly or via group, you can add this right to "everyone" group to give it to all users. As we introduce alarm categories in 2.1-M2, by default user only see alarms belonging to categories it has access to. This access right supposed to be set by upgrade procedure but probably there is a bug in it.

Best regards,
Victor

А в логах сервера нет никаких ошибок при обработке этой команды? Сервер вытаскивает историю событий из базы, возможно медленный доступ к базе?

"изменения статуса Alram ( Ack, Sticky ack, resolved, terminated ) через nxshell" - это есть уже сейчас, через методы acknowledgeAlarm, resolveAlarm, terminateAlarm. Комментарии также можно добавлять/смотреть. Единственно что нельзя - напрямую менять helpdesk status и helpdek reference.

Hi all,

NetXMS 2.1-M2 is out. It's next milestone release in 2.1 branch. It should be considered beta version and used with caution, although we do our best to ensure it's stability. Changes since 2.1-M1 are following:

- Added alarm category functionality to manage which alarms are seen by what users
        - EPP rules can be configured to generate categorised alarms
        - Alarm categories can be created and configured in Alarm Category Configurator
        - By default view_all_alarms acl added to Everyone group
- Server can be configured to periodically send alarm summary emails
- Added template graphs
- New NXSL functions: mktime, GetSyslogRuleCheckCount, GetSyslogRuleMatchCount
- New NXSL "Node" class attributes: isInMaintenanceMode, lastAgentCommTime
- New NXSL "Table" class attribute "rows"
- Access to object's alarms in NXSL via "alarms" attribute in "NetObj" class
- Operator "new" in NXSL which can be used to instantiate objects if object class supports it
- Template auto-apply and container auto-bind works for clusters
- H3C driver correctly reads IPv6 addresses on interfaces
- Improved HP ProCurve driver
- SMS driver for Nexmo service
- SMS driver for SMSEagle gateway
- SMS driver for MyMobile service
- Fixed FDB handling on Cisco switches
- Added support for CHAP, MS-CHAPv1, and MS-CHAPv2 in RADIUS authentication
- MySQL monitoring subagent
- Fixed FreeBSD 11 compatibility issues
- Implemented interrupt and context switch counters in platform subagents
- Implemented CPU interrupt time parameters on Windows
- JMX subagent
- Event sending by agent do not restricted to master servers only anymore
- Launcher for nxshell
- Log monitoring subagent supports pre-allocated log files
- Management console:
        - File manager improvements
        - Option to save graph as image
        - Added multipliers support in data format string for gauges
- Fixed issues: #42, #106, #130, #174, #179, #185, #496, #526, #569, #633, #637, #784, #876, #951, #953, #1031, #1043, #1069, #1079, #1087, #1090, #1097, #1123, #1156, #1192, #1201, #1205, #1206, #1208, #1233, #1258, #1285, #1292, #1300, #1310, #1311, #1312, #1314, #1318, #1320, #1323, #1326, #1329, #1332, #1338, #1341, #1348, #1349, #1351, #1352, #1354, #1357, #1360, #1361, #1362, #1363, #1366, #1367, #1368, #1374, #1376, #1379, #1389, #1396, #1397

Best regards,
Victor

Проверьте что в конфиге агента правильно прописаны адреса всех серверов, которые к нему обращаются.

hdlink - это по сути драйвер интерфейса тикет системы. Сейчас есть для Jira. Я посмотрю API ManageEngines - возможно мы сможем добавить драйвер для них тоже.

Hi,

server currently ignores "dormant" state. I'll add support for that (https://dev.raden.solutions/issues/1401).

Best regards,
Victor

Hi,

there are two options. First, you can schedule script run in scheduled tasks. You'll have to enumerate all nodes in that script and check interfaces. Other option is to create a hook script for configuration poll - then it will be called for each node after configuration poll, so you'll have to write code only for checking interfaces.

Best regards,
Victor

Hi,

if syslog message contains correct device name and you have that device under same name in NetXMS, try to set server configuration parameter SyslogNodeMatchingPolicy to 1 (which means "host name then IP") and restart server.

Best regards,
Victor

Hi,

it cannot be solved without change in code. Please register issue in bug tracker to make Y axis always started at 0 configurable option for line charts.

Best regards,
Victor

Hi,

alternatively, it could be path from the root instead of just name (or as second column) - it's easier to implement and should be as useful. What do you think?

Best regards,
Victor

Hi,

seems to be good idea. I've registered in our bug tracker: https://dev.raden.solutions/issues/1400

Best regards,
Victor

Switch OID - value of .1.3.6.1.2.1.1.2.0. For example, on my H3C switch:

victor@hp8570w ~ $ /opt/netxms/bin/nxsnmpget 10.5.4.1 .1.3.6.1.2.1.1.2.0
.1.3.6.1.2.1.1.2.0 [OBJECT IDENTIFIER]: .1.3.6.1.4.1.43.1.16.4.3.83

Port layout - just specify how many rows and how numbering goes. Same H3C example:
2 rows, numbering down-up then left-right:
2 4 6 8 ...
1 3 5 7 ...

Best regards,
Victor