Recent Posts

Pages: [1] 2 3 ... 10
1
General Support / Performance tab graphs - Auto color
« Last post by blazarov on Today at 12:56:53 pm »
Hello,
We are running version 3.1-300

We are heavily using instance discovery and the performance tab for network devices. It works very very well and way it is developped gives us the flexibility we need to cover wide variety of scenarios.

Often we are using the grouping function which is also really nice, but i am wondering if there is a way to use automatic color selectionl, so that automatically created and grouped DCIs by instance discovery end up with distinct colors in the same graph?
2
Общие вопросы / Re: Не работает мониторинг UPS APC по SNMPv3
« Last post by TOLeg on Today at 06:46:39 am »
# количество интерфейсов
nxsnmpget IP .1.3.6.1.2.1.2.1.0

Результат
### Проверка UPS
Request timed out
### Проверка принтера
.1.3.6.1.2.1.2.1.0 [INTEGER]: 2

# список индексов интерфейсов
nxsnmpwalk IP .1.3.6.1.2.1.2.2.1.1   

Результат
###UPS
SNMP Error: Request timed out
###Printer
.1.3.6.1.2.1.2.2.1.1.1 [INTEGER]: 1
.1.3.6.1.2.1.2.2.1.1.2 [INTEGER]: 2

# имена
nxsnmpwalk IP .1.3.6.1.2.1.2.2.1.2
Результат
###UPS
SNMP Error: Request timed out
###Printer
.1.3.6.1.2.1.2.2.1.2.1 [STRING]: HP ETHERNET MULTI-ENVIRONMENT,ROM none,JETDIRECT,JD137,EEPROM V.37.12
.1.3.6.1.2.1.2.2.1.2.2 [STRING]: HP ETHERNET MULTI-ENVIRONMENT,ROM none,JETDIRECT,JD137,EEPROM V.37.12

# имена другим методом
nxsnmpwalk IP .1.3.6.1.2.1.31.1.1.1.1

Результат
###UPS
SNMP Error: Request timed out
###Printer
нет данных

# алиасы
nxsnmpwalk IP .1.3.6.1.2.1.31.1.1.1.18
Результат
###UPS
SNMP Error: Request timed out
###Printer
нет данных
3
Общие вопросы / Re: Не работает мониторинг UPS APC по SNMPv3
« Last post by Alex Kirhenshtein on January 16, 2020, 06:21:56 pm »
А это ноды вообще отдают список интерфейсов через SNMP?

Проверьте при помощи snmpget/snmpwalk:

Code: [Select]
# количество интерфейсов
nxsnmpget IP .1.3.6.1.2.1.2.1.0
.1.3.6.1.2.1.2.1.0 [INTEGER]: 33

# список индексов интерфейсов
nxsnmpwalk IP .1.3.6.1.2.1.2.2.1.1   
.1.3.6.1.2.1.2.2.1.1.1 [INTEGER]: 1
.1.3.6.1.2.1.2.2.1.1.2 [INTEGER]: 2
…

# имена
nxsnmpwalk IP .1.3.6.1.2.1.2.2.1.2
.1.3.6.1.2.1.2.2.1.2.1 [STRING]: GigabitEthernet1/0/1
.1.3.6.1.2.1.2.2.1.2.2 [STRING]: GigabitEthernet1/0/2
.1.3.6.1.2.1.2.2.1.2.3 [STRING]: GigabitEthernet1/0/3
…


# имена другим методом
nxsnmpwalk IP .1.3.6.1.2.1.31.1.1.1.1
.1.3.6.1.2.1.31.1.1.1.1.1 [STRING]: GigabitEthernet1/0/1
.1.3.6.1.2.1.31.1.1.1.1.2 [STRING]: GigabitEthernet1/0/2
.1.3.6.1.2.1.31.1.1.1.1.3 [STRING]: GigabitEthernet1/0/3
…

# алиасы
nxsnmpwalk IP .1.3.6.1.2.1.31.1.1.1.18
.1.3.6.1.2.1.31.1.1.1.18.1 [STRING]: ESX1
.1.3.6.1.2.1.31.1.1.1.18.2 [STRING]: ESX2
.1.3.6.1.2.1.31.1.1.1.18.3 [STRING]: ESX1-vMotion
…
4
General Support / Local Command can not find file
« Last post by Jeremy Davenport on January 16, 2020, 05:21:21 pm »
I recently upgraded NetXMS to version 3.1.260.  I had two object tools that I had built to start Putty or WinBox from the tools menu in NetXMS.  Now when I try and run those tools I get an error that Windows can not find <path to my exe file> but in the error message all of the back slashes are missing so instead of "C:\Program Files (x86)\WinBox" it reads "C:Program Files (x86)WinBox".  I have checked the path in the definition of the object tool and it is correct.  It worked before I upgraded.  Any ideas?

Jeremy
5
General Support / Re: login with nxencpasswd not working
« Last post by Woody on January 16, 2020, 02:10:30 pm »
Okay. Thank you very much!  :D

Best regards
6
Общие вопросы / Re: Не работает мониторинг UPS APC по SNMPv3
« Last post by TOLeg on January 16, 2020, 01:26:32 pm »
Проверил на принтере HP 2055. Тоже ошибка на интерфейсах

Unable to get interface list from node

 :(

HELP!!!
7
General Support / Re: login with nxencpasswd not working
« Last post by Victor Kirhenshtein on January 16, 2020, 11:31:17 am »
Hi,

I just increased maximum password length for nxencpasswd in 3.2 branch.

Best regards,
Victor
8
General Support / Re: String length cut at 255 Characters
« Last post by Victor Kirhenshtein on January 16, 2020, 10:46:41 am »
Hi,

DCI value length is limited to 255 characters. In your case you can use external parameter provider instead of external parameter, do JSON parsing in agent side script and output all parameters you are interested in as name = value. Then you'll be able to collect them by name as any other agent's parameters.

Best regards,
Victor
9
General Support / Re: cant get powershell script to run
« Last post by Egert143 on January 16, 2020, 08:03:20 am »
Code: [Select]
2020.01.14 19:49:15.569 *D* [                   ] ProcessExecutor::readOutput(): stopped on GetOverlappedResult (The pipe has been ended.)
Could that mean script or agent error ? It seems script runs about 5-6 seconds as usual. Also if someone is decent at powershell maybe there is somthing wrong with script itself? I am very beginner in PS :)
10
General Support / String length cut at 255 Characters
« Last post by hewa6254 on January 15, 2020, 05:04:58 pm »
Hi Everyone,

i wrote a simple curl Shell script that consumes a REST API from my Service i need to monitor.
The ccript is stored on my netxms server and executed as an ExternalParameter from the local netxms agent.
It returns JSON Data which i transform with nxsl to get the Information that i want. (This way i can reuse my CURL Script for diffrent APIs)

My Problem occures when the API returns more than 255 Characters (which it does most of the time).
The Datatype from the DCI is a String and apparently it can contain 255 Characters max. Everything longer gets cut off.

Is there a better way to monitor my REST API or am i limited to those 255 Chars?
I want to transform the Data with nxsl so i dont need a new shellscript for each diffrent API Parameter i want to monitor.
I think this is a common Monitoring Task, so i think i am just doing this wrong :D

Best Regards
Henry
Pages: [1] 2 3 ... 10