Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

This issue still exists in 2.2.15.

In a strange twist - visibility via the tool-tip when hovering over alert in Alarm Browser, does not have the limitation. This gets us around this being a major impact and instead, is an annoyance that we hope gets adjusted at some point.

It just really stands out by having 2 or three events and the rest of that empty, a comments section - also empty, and the Alarm Overview that has to scroll to see the whole alarm.

Went with export / import. 1.4GB export file took about an hour to import - VM built as 4 core 12GB E2680 V4 CPU with all Flash storage - everything was local (iscsi to SAN). Included collected data.

Panicked when I started the console locally and pointed it at the new server - error.  Helps to start the NetXMS service first

Everything was perfect - the only thing I had to do in addition to the import was to copy the MIBS across.

Any ideas why netxms is crashing with ssh as data source?

Hi all,

maybe someone can help me with the following:

I am currently trying to set up a SSO (Single sign on) solution for NetXMS using Apereo CAS. After several days of research and digging, I stumbled across a few lines in the WebUI source code, indicating that it has native SSO support, which was then confirmed by the change log of version 1.2.8 (https://www.netxms.org/forum/announcements/netxms-1-2-8-released/).

However, I could not find a single line of documentation nor a single forum thread on this topic, which is why I started one, by myself.

Currently, the following are the main questions related to this:

1. How does the Webapp handle the SSO session?
-> Is there a special URL to which CAS needs to redirect upon successful login?
-> Which attributes (if any) are needed from and for CAS?
-> Is SLO (single log out) also implemented?
2. How is the user management handled?
-> Does the user still need to be present in the NetXMS database?
-> If not, how are access rights handled (maybe via a special group?)
3. Can the official documentation be extended with this topic? It would really be cool to have a proper guide on how to set this up

I would be really happy, if someone could find the time to help me with this topic 

Thank you and kind regards,
fbu

Главная моя задача получить тля телефона по cdp его привязку к порту свича, чтобы Network Maps построился линк и привязка к порту свича.

А какую информацию можно получить через CDP про телефон? В любом случае, если есть OID'ы на свиче, то можно их настроить на ноде телефона и как source node указать ноду свича - тогда реальный сбор данных будет на свиче а показываться они будут на телефоне.

Dear NetXMS team,

here is another thing that came to my mind when creating line charts in NetXMS:

Currently, NetXMS provides the ability to create "stacked" line chart diagrams, however, it only allows to stack all or none of the data from the source DCIs.

I think it would be useful to manually choose, which data to stack on top of each other and to have a more user friendly way of defining the stacking order (right now it is defined by the order the DCI sources).

Imagine the following: We have the four metrics TCP upstream, UDP upstream, HTTP upstream and overall upstream (downstream equivalent). To combine all four within one diagram, it should be possible to only stack UDP on top of TCP, as HTTP is a subset of the TCP traffic and the overall upstream is the superset of all three (which would only be added as a reference line).

What do you think about this idea?

Thanks and kind regards,
fbu 

Hi NetXMS team,

here's another idea of a potentially useful feature addition:

A NXSL function which allows to manually enable and disable DCIs or set their states. The function could be defined such as "setDCIStatus(dci, status)", where dci would be the DCI-object and status an integer with 0=Active, 1=Disabled and 2=Not Supported.

Maybe "setDCIStatusByID(dciID, node, status)", with dciID being an integer representing the DCI ID and node being a node-object as optional parameter, would also be possible.


The idea came to my mind, because a fairly large set of the nodes within my current setup is receiving monitoring data via NXAgent extension scripts from a centralized database, and are initially created via a big NXSL script under "Infrastructure Services", based on this data, as it is impossible to have a direct monitoring communication with NetXMS - not even with the use of NXAgent and proxy agents.

Because these devices might change in their states and different metrics temporarily might not return data any more, it would be useful to have a NXSL function, to disable those metrics via a script, as the "unsupported"-detection is also not working with this setup.

I know, template automatic apply rules can be used for this, however, once a template is un-applied from a node, the DCIs on it are gone and there is no way to access their history data via the management console until the template is re-applied, again.


What do you think, could this be useful if so, would it be difficult to implement?

Kind regards,
fbu

Добрый день.
У меня вот какая проблема. Есть необходимость отслеживать телефоны cisco 8851, на телефонах нет snmp, но по умолчанию включено cdp и свичи cisco их видяти получают информащию. Вопрос как настроить узел на netxms чтобы он получал информацию cdp с телефона если нет snmp?