Hi, I recently upgraded from one of the turnkey appliances to Observium running in a VM on its own running Observium CE 17.9.0. Since that upgrade my queries for ports haven't been completed against my main FortiSwitch. Looking at the poller times the ports module seems to be taking the longest (ports/1,562.4587s/156.25%). Debugging that on the fortiswitch I am seeing the following queries and very high CPU usage on the FortiSwitch (124D running 3.6.6). Is there a way to disable that query specifically rather than ports as a whole?
snmpd: <msg> 49 bytes xxxxx:8089 -> xxxxx/xxxxx:161 (itf 32.32) snmpd: checking if community "xxxxx" is valid snmpd: checking against community "xxxxx" snmpd: request 1(root)/32/xxxxx == comm 1/0/0.0.0.0/0.0.0.0 snmpd: matched community "xxxxx" snmpd: get-next: OID: 1.3.6.1.2.1.17.7.1.4.3.1 : dot1qVlanStaticEntry .4.1964 -> (snmpd: get_last_index_dot1qVlanStaticTable() snmpd: get_dot1qVlanStaticEntry() fld:4 ) -> 0 snmpd: </msg> 1
snmpd: <msg> 49 bytes xxxxx:17885 -> xxxxx/xxxxx:161 (itf 32.32) snmpd: checking if community "xxxxx" is valid snmpd: checking against community "xxxxx" snmpd: request 1(root)/32/xxxxx == comm 1/0/0.0.0.0/0.0.0.0 snmpd: matched community "xxxxx" snmpd: get-next: OID: 1.3.6.1.2.1.17.7.1.4.3.1 : dot1qVlanStaticEntry .4.859 -> (snmpd: get_last_index_dot1qVlanStaticTable() snmpd: get_dot1qVlanStaticEntry() fld:4 d) -> 0 snmpd: </msg> 1
Thanks, Matt
Disable the fdb-table module on that device in the device's settings in the observium ui.
adam. On 2018-08-06 19:06:58, Matthew Goeres mgoeres@gmail.com wrote: Hi, I recently upgraded from one of the turnkey appliances to Observium running in a VM on its own running Observium CE 17.9.0. Since that upgrade my queries for ports haven't been completed against my main FortiSwitch. Looking at the poller times the ports module seems to be taking the longest (ports/1,562.4587s/156.25%). Debugging that on the fortiswitch I am seeing the following queries and very high CPU usage on the FortiSwitch (124D running 3.6.6). Is there a way to disable that query specifically rather than ports as a whole?
snmpd: <msg> 49 bytes xxxxx:8089 -> xxxxx/xxxxx:161 (itf 32.32) snmpd: checking if community "xxxxx" is valid snmpd: checking against community "xxxxx" snmpd: request 1(root)/32/xxxxx == comm 1/0/0.0.0.0/0.0.0.0 [http://0.0.0.0/0.0.0.0] snmpd: matched community "xxxxx" snmpd: get-next: OID: 1.3.6.1.2.1.17.7.1.4.3.1 : dot1qVlanStaticEntry .4.1964 -> (snmpd: get_last_index_dot1qVlanStaticTable() snmpd: get_dot1qVlanStaticEntry() fld:4 ) -> 0 snmpd: </msg> 1
snmpd: <msg> 49 bytes xxxxx:17885 -> xxxxx/xxxxx:161 (itf 32.32) snmpd: checking if community "xxxxx" is valid snmpd: checking against community "xxxxx" snmpd: request 1(root)/32/xxxxx == comm 1/0/0.0.0.0/0.0.0.0 [http://0.0.0.0/0.0.0.0] snmpd: matched community "xxxxx" snmpd: get-next: OID: 1.3.6.1.2.1.17.7.1.4.3.1 : dot1qVlanStaticEntry .4.859 -> (snmpd: get_last_index_dot1qVlanStaticTable() snmpd: get_dot1qVlanStaticEntry() fld:4 d) -> 0 snmpd: </msg> 1
Thanks, Matt
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
It looks like the queries are still happening. I disabled the fdb-table and also did the Q-BRIDGE-MIB and the queries are still happening.
Here is an example of the process that is doing it on the server side: observi+ 24789 22046 0 14:00 ? 00:00:00 sh -c /usr/bin/snmpwalk -t '3' -r '1' -v1 -c 'xxxxx' -Pu -OQUs -m Q-BRIDGE-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'xxxxx':'161' dot1qVlanStaticUntaggedPorts 2>/dev/null observi+ 24790 24789 0 14:00 ? 00:00:00 /usr/bin/snmpwalk -t 3 -r 1 -v1 -c -Pu -OQUs -m Q-BRIDGE-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp udp:xxxxx:161 dot1qVlanStaticUntaggedPorts
On Mon, Aug 6, 2018 at 1:16 PM, Adam Armstrong adama@memetic.org wrote:
Disable the fdb-table module on that device in the device's settings in the observium ui.
adam.
On 2018-08-06 19:06:58, Matthew Goeres mgoeres@gmail.com wrote: Hi, I recently upgraded from one of the turnkey appliances to Observium running in a VM on its own running Observium CE 17.9.0. Since that upgrade my queries for ports haven't been completed against my main FortiSwitch. Looking at the poller times the ports module seems to be taking the longest (ports/1,562.4587s/156.25%). Debugging that on the fortiswitch I am seeing the following queries and very high CPU usage on the FortiSwitch (124D running 3.6.6). Is there a way to disable that query specifically rather than ports as a whole?
snmpd: <msg> 49 bytes xxxxx:8089 -> xxxxx/xxxxx:161 (itf 32.32) snmpd: checking if community "xxxxx" is valid snmpd: checking against community "xxxxx" snmpd: request 1(root)/32/xxxxx == comm 1/0/0.0.0.0/0.0.0.0 snmpd: matched community "xxxxx" snmpd: get-next: OID: 1.3.6.1.2.1.17.7.1.4.3.1 : dot1qVlanStaticEntry .4.1964 -> (snmpd: get_last_index_dot1qVlanStaticTable() snmpd: get_dot1qVlanStaticEntry() fld:4 ) -> 0 snmpd: </msg> 1
snmpd: <msg> 49 bytes xxxxx:17885 -> xxxxx/xxxxx:161 (itf 32.32) snmpd: checking if community "xxxxx" is valid snmpd: checking against community "xxxxx" snmpd: request 1(root)/32/xxxxx == comm 1/0/0.0.0.0/0.0.0.0 snmpd: matched community "xxxxx" snmpd: get-next: OID: 1.3.6.1.2.1.17.7.1.4.3.1 : dot1qVlanStaticEntry .4.859 -> (snmpd: get_last_index_dot1qVlanStaticTable() snmpd: get_dot1qVlanStaticEntry() fld:4 d) -> 0 snmpd: </msg> 1
Thanks, Matt
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/ cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (2)
-
Adam Armstrong -
Matthew Goeres