| 2016-11-10 21:05:17 |
Félix Bouliane |
description |
Some PDU seems to take a long time to respond. The default configuration of snmpset (retries=5, timeout=1) is sometimes not sufficient to be able to snmp set/get. It would be nice, as an openstack operator, to make ironic's udp timeout and retries configurable in the global configuration.
# Conductor log
WARNING ironic.conductor.manager [-] During sync_power_state, could not get power state for node XX-XX-XX-XX, attempt 1 of 3. Error: SNMP operation 'GET' failed: No SNMP response received before timeout.
# Behavior when SNMP set with insufficient timeout
Timeout: No Response from 10.209.1.20.
# Time for a response (in the case of SNMPSET)
$ time snmpset -t5 -r0 -v2c X.X.X.X ${OID} i 0
${OID} = INTEGER: 0
real 0m2.711s
user 0m0.000s
sys 0m0.006s
Raw |
Some PDU seems to take a long time to respond. The default configuration of snmpset (retries=5, timeout=1) is sometimes not sufficient to be able to snmp set/get. It would be nice, as an openstack operator, to make ironic's udp timeout and retries configurable in the global configuration.
# Conductor log
WARNING ironic.conductor.manager [-] During sync_power_state, could not get power state for node XX-XX-XX-XX, attempt 1 of 3. Error: SNMP operation 'GET' failed: No SNMP response received before timeout.
# Behavior when SNMP set with insufficient timeout
Timeout: No Response from X.X.X.X.
# Time for a response (in the case of SNMPSET)
$ time snmpset -t5 -r0 -v2c X.X.X.X ${OID} i 0
${OID} = INTEGER: 0
real 0m2.711s
user 0m0.000s
sys 0m0.006s
Raw |
|
