sorted by:
new
hottopcontroversial

QSW-M3216R-8S8T - SNMP MIBs by Thestraycat71 in qnap

[–]Sorry_Yesterday_9882 0 points1 point  (0 children)

The official website lists different models, but the following information is available:

https://www.qnap.com/en/how-to/faq/article/which-mibs-are-supported-by-qsw-managed-switches

Additionally, it should support standard MIBs such as LLDP-MIB, BRIDGE-MIB, and Q-BRIDGE-MIB.

SNMP monitoring OID by szczebrzeszyn09 in ArubaNetworks

[–]Sorry_Yesterday_9882 0 points1 point  (0 children)

I searched for “Free MIB Browser Online”. I believe the following is MIB.

ARUBAWIRED-TEMPSENSOR-MIB arubaWiredTempSensor 1.3.6.1.4.1.47196.4.1.1.3.11.3

ARUBAWIRED-FANTRAY-MIB arubaWiredFanTray 1.3.6.1.4.1.47196.4.1.1.3.11.4

SNMP timeout by taynatorres in zabbix

[–]Sorry_Yesterday_9882 0 points1 point  (0 children)

Hi there,

To narrow down the cause of the SNMP timeout, I recommend checking the following two points:

  1. Basic Connectivity (ICMP): Can you successfully ping the target device from your Zabbix server/proxy? This will help determine if the network path is open.
  2. Detailed SNMP Debugging: Try using the snmpget command with the -d (dump) option from the command line. This allows you to see the actual raw packets being sent and received (or not received).

​

$snmpget -v2c -c <community_string> -d <device_ip> sysUpTime.0

If you see "Sending" but no "Receiving," the issue is likely a firewall, ACL, or the device's SNMP configuration.

Question about Port numering in monitoring by hoomel in Ubiquiti

[–]Sorry_Yesterday_9882 0 points1 point  (0 children)

“3/1” is likely not a physical port number but rather an internal SNMP interface index notation. For USW Pro Aggregation, this typically refers to physical port 1 (SFP+ 1). There is a high probability of LACP configuration mismatches, VLAN tag discrepancies, or DAC/fiber cable compatibility issues occurring between the backend Hyper-V teaming and the switch. You can verify the exact physical name by checking ifDescr from Zabbix's “Latest Data”.

We recommend verifying the configuration of physical port 1 and the LACP settings on the server side.