NetXMS Support Forum

Работа по локализации начата вообщем-то, надо продолжать Локализация для десктоп и веб интерфейсов общая. Уже сейчас веб можно переключить на русский, добавив ?lang=ru к URL'у. На русском правда будет только несколько пунктов меню. Самый правильный вариант думаю будет такой - я подготовлю новые message-файлы, и пришлю вам для перевода. На форуме есть ветка, посвященная локализации консоли: https://www.netxms.org/forum/general/about-the-language/ .

Hi!

NetXMS should work with any SNMP-capable device. You can create links on map with any name set. However, there are no dynamically updated information on the links yet.

Best regards,
Victor

In enterprise WiFi system, you usually have wireless switches (controllers) and access points. In most cases access points are not directly accessible, and all management information must be read from controllers. Starting from 1.2.7, NetXMS can read information from wireless controllers and create separate access points objects that can be used on maps, etc. Support from network device driver is required for this functionality. Currently we have driver for Motorola/Symbol wireless controllers.

Best regards,
Victor

Hi!

Currently map object status is always NORMAL. I will add an option for map to calculate status based on underlying objects. Currently you can use containers if you want to see status - but that's a double work. For example, you can create container C and map object M. Then you add nodes to both of them, and set map object M as a drill-down map for container C. Then you can add container C to top-level map. You will see it's status depending of underlying nodes status, and if you double click it, map M will open.

Best regards,
Victor

Your script has syntax error, and so it not compiles. Because of that you got "script not found" message (not very meaningful in this case, I agree). Besides that, it has other errors. First of all, you have to create SNMP transport object for node you want to query, and then use it in SNMPGet function. Below is an example of script which can be run from server's debug console to get SNMP object ID from node passed as parameter:


if ($1 == null)
{
   println "Please specify node name as parameter";
   return 3;
}

transport = CreateSNMPTransport(FindObject($1));    // Create SNMP transport for node
if (transport == null)
{
    println "Failed to create SNMP transport, exit";
    return 1;
}

value = SNMPGetValue(transport, ".1.3.6.1.2.1.1.1.0");
if (value == null)
{
    println "Failed to issue SNMP GET request";
    return 2;
}
else
{
    println "System description: " . value;
    return 0;
}


Example of running this script on my test server attached.

Best regards,
Victor

Hi!

This can happen if counter resets to 0 at some point. Then delta between new value of 0 and previous value if very large. You can prevent such incorrect spikes by checking for reasonable maximum value in transformation script. For example, if max. possible value for inbound is 600000, you can use transformation script like this:


return ($1 <= 600000) ? $1 : 0;


Best regards,
Victor

Hi!

Yes, it's possible, you have to install web UI for that. It's in a separate package: https://www.netxms.org/download/webui/netxms-webui-1.2.7.exe or https://www.netxms.org/download/webui/netxms-webui-1.2.7-x64.exe. If you already have Java application server installed, you can just deploy war file: https://www.netxms.org/download/webui/nxmc-1.2.7.war. There is short instruction about web UI installation: http://wiki.netxms.org/wiki/Web_Interface_Installation_Guide.

Best regards,
Victor

Hi!

There are lot of different options for different integration scenarios. One option is to use event forwarding between NetXMS servers: collector server collects and analyzes data from devices, and send events to operations manager server when something happens. In such configuration historical data will be kept at collector server, but important events will be available on central server. If you prefer to use other collection tools, you can use integration utilities to send events and data to central NetXMS server (nxevent for sending events and nxpush for pushing performance data).
NetXMS agent is able to parse log files and send events to server when match is found. It cannot forward SNMP traps. Agent is not collecting data automatically - only by server request.

Best regards,
Victor

Hi!

Yes, that was the intention. Minimal package contains only NetXMS itself.

Best regards,
Victor

Hi all!

Finally, NetXMS version 1.2.7 is out! We had some unexpected delays with this release, but now we are back on track and I hope that next versions will come out faster. Changes since previous release are following:

- Simplified configuration of DCIs based on Windows performance counters
- Basic software inventory
- Network discovery improved
- Status of zone's proxy node now used in "node down" event correlation
- Configurable default DCI retention time and polling interval
- New NXSL functions: CreateNode, GetSumDCIValue
- New NXSL operator @ (safe get object's attribute)
- New MIBs added: ASTARO-MIB, CPQHOST-MIB, CPQPOWER-MIB
- Special support for wireless switches
- Driver for Motorola/Symbol wireless switches
- Fixed bugs in template export/import
- Database manager: Fixed bugs in database export
- New parameters for Windows Security Center provided by WMI subagent:
   System.AntiSpywareProduct.Active
   System.AntiSpywareProduct.DisplayName
   System.AntiSpywareProduct.UpToDate
   System.AntiVirusProduct.Active
   System.AntiVirusProduct.DisplayName
   System.AntiVirusProduct.UpToDate
   System.FirewallProduct.Active
   System.FirewallProduct.DisplayName
   System.FirewallProduct.UpToDate
- Management console:
   - "Export to CSV" option added to most tabular data views
   - Auto login option for web console
   - Last values of selected DCIs can be shown in object tooltips
     on network maps
- Fixed issues: #86, #199, #242, #246, #249, #250, #251, #256, #260, #268, #275

Best regards,
Victor

Hi!

Most information located in tables nodes, interfaces, and object_properties. You can consult data dictionary for detailed information about these tables: https://www.netxms.org/documentation/NetXMS_data_dictionary.pdf.

Best regards,
Victor

Quote from: jamesof on May 09, 2013, 06:20:53 PM

Quotewhat do you mean by security policy on agent?

agent check manager have right to do action.

There are 3 level of access for an agent. Depending on how server's IP address listen in nxagentd.conf, it will have different access level. If server listed in:

1. MasterServers - full access
2. ControlServers - can read data and execute predefined actions, but cannot change config nor install policies.
3. Servers - read only access

Quote from: jamesof on May 09, 2013, 06:20:53 PM
and another question . can we have any accounting feature? which user how many usage which app ... for any session in remote device that running agent .

No, we don't have functionality like that.

Best regards,
Victor

Quote from: jamesof on May 08, 2013, 06:41:55 PM
is it possible to return generated output. i remember you said it is not possible (around 2010) . is this feature added to netxms?

still not possible

Quote from: jamesof on May 08, 2013, 06:41:55 PM
can i set snmp oid with agent?

Only by calling external tools. You can copy nxsnmpset to agent and configure action which will call it.

Quote from: jamesof on May 08, 2013, 06:41:55 PM
can i define security policies on agent ?

what do you mean by security policy on agent?

Best regards,
Victor

Hi!

You can include custom attribute in mail and/or alarm message by using %{name} macro. For example, if you have custom attribute named additionalInfo, you can use %{additionalInfo} to insert value of this attribute into message text.

Inserting comments into message is a bit more complicated - you have to create script in script library, like this:


return $node->comments;


and then call it using %[script_name] macro.

Best regards,
Victor

Hi!

There are two problems in your config:

1. You put Action keyword in wrong section. It should be like this:

ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
LogFile = {syslog}
FileStore = C:\NetXMS\var
SubAgent = ecs.nsm
SubAgent = ping.nsm
SubAgent = logwatch.nsm
SubAgent = portcheck.nsm
SubAgent = winperf.nsm
Action= dir:cmd.exe /c "dir c:\ > c:\1.txt"
SubAgent = wmi.nsm
SubAgent = ups.nsm

2. On server side, you should only put name of the action configured on agent in "agent action" field. It will be just dir in your case.

Best regards,
Victor