NetXMS Support Forum

Hello,

where can i send you the snmpwalk files ?

thank you

no luck,

do you need an snmp walk output to add the switches to netxms ?

Hello,

i have aruba switch cx series 6300, 6200, 
SNMP object ID=1.3.6.1.4.1.47196.4.1.1.1.323
SNMP object ID=1.3.6.1.4.1.47196.4.1.1.1.324
SNMP object ID=1.3.6.1.4.1.47196.4.1.1.1.119

the driver generic is used, i cannot see vlan, arp, ports, fdb, vlan table etc....

how can i change it to use aruba driver ?

thank you

Hi,

[28039.876445] $POLLERS/WRK[15318]: segfault at 3c8 ip 00007f60d32ab2b0 sp 00007f608aaea8c8 error 4 in libc.so.6[7f60d3245000+155000] likely on CPU 5 (core 5, socket 0)
[28039.876460] Code: 30 11 00 ba c2 01 00 00 48 8d 35 57 ac 10 00 48 8d 3d 65 ac 10 00 e8 cf 8b fa ff e8 1a be 08 00 66 2e 0f 1f 84 00 00 00 00 00 <8b> 47 10 89 c2 81 e2 7f 01 00 00 83 e0 7c 0f 85 ac 00 00 00 53 48

got the same error.

2023.10.02 18:32:48.183 *I* [linux              ] Unable to parse /proc/drbd, DRBD data collector will not start
2023.10.02 18:32:48.184 *I* [subagents          ] Subagent "Linux" (/usr/lib/x86_64-linux-gnu/netxms/linux.nsm) loaded successfully (version 4.4.2)
2023.10.02 18:32:48.187 *I* [subagents          ] Subagent "SSH" (/usr/lib/x86_64-linux-gnu/netxms/ssh.nsm) loaded successfully (version 4.4.2)
2023.10.02 18:32:48.187 *I* [subagents          ] Subagent "PING" (/usr/lib/x86_64-linux-gnu/netxms/ping.nsm) loaded successfully (version 4.4.2)
2023.10.02 18:32:48.188 *I* [startup            ] System hardware IDxxxxxxxxxxxxxx
2023.10.02 18:32:49.193 *I* [comm              ] Listening on socket 0.0.0.0:4700
2023.10.02 18:32:49.193 *I* [comm              ] Listening on socket :::4700
2023.10.02 18:32:49.193 *I* [comm              ] Control connector is disabled
2023.10.02 18:32:50.194 *I* [filemon            ] Path list for file monitor is empty
2023.10.02 18:32:50.194 *I* [                  ] NetXMS Agent started
2023.10.02 18:33:19.588 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:19.588 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:21.027 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:24.592 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:24.592 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:24.592 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:24.592 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:25.038 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:25.042 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:25.044 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:25.074 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:35.065 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:35.067 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:35.069 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:36.086 *W* [comm              ] Too many communication sessions open - unable to accept new connection
2023.10.02 18:33:39.568 *W* [comm              ] Too many communication sessions open - unable to accept new connection

yes

agent conf:

# Log File
LogFile=/var/log/nxagentd

# IP white list, can contain multiple records separated by comma.
# CIDR notation supported for subnets.
MasterServers=127.0.0.1
SubAgent=ssh.nsm
SubAgent=ping.nsm
[SSH]
ConfigFile = /etc/nxagentd-ssh-config
MaxSessions=500



even tried adding MaxSessions=500 in /etc/nxagentd-ssh-config....

no luck

Hello,
yes i have a lot of ssh metrics configured.
i tried to set MaxSessions to 100 and 500 but the log is full of error message.

it is no agent proxy, agent is netxms server itself.

Hello,

i noticed in agentd log:


Too many communication sessions open - unable to accept new connection


and i noticed that my ssh dci's dont update ...

i read the manual and forum but could not find a solution.

I try to connect to ubiquiti gear with ssh but get the error in the log on the client side:
Exit before auth: No matching algo hostkey
in Netxms i get ssh connection not available.

if i connect with tools, connect, ssh, it asks me user and password and connects.

My goal is to have passwordless connection to ubiquiti devices...

Is there a howto ? I tried several times but no luck....

Hello,

it works perfect!!

thank you

Hello,

i have a lot of Aruba APs i want to monitor, problem on discovery:
only 1 is discovered:
log:

2023.08.08 16:57:42.286 *D* [poll.discovery    ] AcceptNewNode(10.66.180.129): IP address xxxxxxxxxxxon interface BR0 matches existing node xxxxxxxxxxxxx [1678]
2023.08.08 16:57:42.286 *D* [poll.discovery    ] AcceptNewNode(10.66.180.131): MAC address is not known, will lookup in ARP caches
2023.08.08 16:57:42.286 *D* [poll.discovery    ] AcceptNewNode(10.66.180.131): found MAC address 44:48:C1:C8:22:0A
2023.08.08 16:57:42.287 *D* [poll.discovery    ] AcceptNewNode(10.66.180.131): filter flags=0000

how can i avoid this problem ? The Aruba AP have all the same ip on BR0 interface...

Hello,

does someone monitor a large number of ubiquiti gear?

I would like to use netxms for monitoring but,
Aircontrol2 -- discontinued
UNMS -- cannot monitor 3rd party gear

Tested netxms and i think it can do all with proper configuration.
Problem: ubiquiti has different snmp oids, maybe someone has templates for all different Products?

Thanks.