Aruba AP
-
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=0000how can i avoid this problem ? The Aruba AP have all the same ip on BR0 interface...
-
Yes, NetXMS expects IP addresses to be unique within a zone. What probably should help - we can disable interface creation. In script library there is Hook::CreateInterface script, it is executed each time a new interface is found. Here's an example:
if ($node->snmpOID == ".X.X.X.X" and $1->name == "BR0") {
PollerTrace("Blocking interface " .. $1->name .. " creation");
return false;
}
return true;I am checking node's SNMP ID, you can use any other approach - by subnet, container, etc - this is not to affect other nodes that might also happen to have an interface named BR0. PollerTrace line is optional - it's just for adding some info to output of manually-called configuration poll.
You have to delete all existing BR0 interfaces (or probably just one) that you have in your system. -
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login