No IP addresses for Aruba 6300M

[iliessens]

Expected Behavior

For other brands of switches Netdisco nicely displays the IP's for each MAC-address node on the ports tab.

Current Behavior

No IP-adresses for the connected nodes are shown for the Aruba switches running AOS-CX FL.10.07.0041, presumably because the ARP-table can not be extracted.
MAC-addresses are correct, and the "addresses" tab also shows the IP's of the switch itself as expected.

Possible Solution

It seems that Netdisco uses the ipNetToMediaTable (OID 1.3.6.1.2.1.4.22) to read the ARP table. Aruba support has confirmed that this OID is deprecated and ipNetToPhysicalTable (OID 1.3.6.1.2.1.4.35) should be used instead.

I don't know if any work has been done on integrating this, or how difficult it would be.

Steps to Reproduce (for bugs)

Add an Aruba switch to Netdisco and check if any IP info is shown on the ports tab.

Context

We are starting to use switches from HPE Aruba and would love to continue using Netdisco as our global discovery tool, spanning all vendors.

Your Device

• Vendor: HPE Aruba
• Device Model: JL661A
• Operating System Version: FL.10.07.0041

Your Environment

• SNMP::Info version used: 3.73
• Netdisco version (if used): 2.47.8

[inphobia]

i can confirm, ipNetToMediaTable is not available on FL.10.12.0006 either.

most of what you want is implemented in SNMP::Info::IPv6, with a few non-exposed stubs in SNMP::Info::Layer3. i found a comment from 2006 that there were concerns that trying all possible routes could lead to strange results.

and aruba is right i guess, ip-mib has replaced rfc1213 years ago and calls ipNetToMediaTable deprecated and we should go to ipNetToPhysicalTable. (#153 alrdy had issues with rfc vs ipmib, but due to overlap, loading order, whatever, we are still working on it)

@JeroenvIS & @fenner are the references on this.

i don't route on my 6300m's so only have a few entries in the mapping table, perhaps when my the rest arrives that i ordered 18 months ago i can set one with a bit of routing and see if i can whip something up.

or perhaps App::Netdisco::SSHCollector::Platform::Aruba; works on aoscx, the info isn't really clear on what aruba devices it should work.

[jrbinks]

Just to note that I also have this problem and now I've noticed it (although it has been there a while and I've only just had chance to dig harder at it), it is annoying. I am using OSCX in various routing capacities so can do tests and provide info if it helps. My own ND-coding-brain is long comatose...

I upgraded today to ensure I was latest etc

Software Version
App::Netdisco 2.76.4
SNMP::Info 3.970001

[jrbinks]

@inphobia said

or perhaps App::Netdisco::SSHCollector::Platform::Aruba; works on aoscx, the info isn't really clear on what aruba devices it should work.

In theory yes, that should work for OSCX (only) (see netdisco/netdisco#1230), although in my case it doesn't work for some pty issue. I think it is misnamed, as I've said there.