for some MIB, it is "normal" because vendor specific
What netdisco doc say about this ?
------------------------------
PowerArubaSW : Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP...
PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...)
PowerArubaCL: Powershell Module to use Aruba Central
PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)..
ACEP / ACMX #107 / ACDX #1281
------------------------------
Original Message:
Sent: Aug 30, 2024 03:33 PM
From: AnonBlack
Subject: Issue with SNMP on ArubaOS-CX:FL.10.13
I checked the netdisco log and found that several MIBs and related methods are unavailable or could not be resolved.
Here is the list:
VTP-MIB (VLAN Trunking Protocol MIB)
Unresolved methods:
vtp_d_name
vtp_d_mode
SNMP::Info Autoload Methods
Various methods related to neighbor discovery protocols:
hasCDP (Cisco Discovery Protocol)
hasSONMP (Nortel's Simple Network Management Protocol)
hasFDP (Foundry Discovery Protocol)
hasEDP (Extreme Discovery Protocol)
hasAMAP (Alcatel-Lucent Management Access Protocol)
ENTITY-MIB
Unresolved methods:
slots
IF-MIB (Interface MIB)
Unresolved methods:
i_ignore
i_duplex_admin
IEEE8021-Q-BRIDGE-MIB
Unresolved method:
iqb_i_vlan
IEEE8023-LAG-MIB
Unresolved method:
raw_ad_lag_ports
IF-MIB (subinterface management)
Unresolved method:
i_subinterfaces
Does anyone know how to resolve this issue?
Original Message:
Sent: Aug 29, 2024 06:59 PM
From: AnonBlack
Subject: Issue with SNMP on ArubaOS-CX:FL.10.13
Dear All,
I am facing an issue with ArubaOS-CX:FL.10.13, where the system is not delivering L3 information of connected devices via SNMP to Netdisco, despite all configurations being correct.
We have already checked the following configurations:
SNMP community correctly configured.
ACLs allowing SNMP traffic.
SNMPv2c enabled on the device.
Even with these configurations, Netdisco is not receiving the expected information. I would like to know if there is any additional command or specific configuration that could resolve this issue.
I believe the problem might be related to the MIB.
Thank you in advance for your attention.
Has anyone else experienced this issue?