Code was checked in to return SA_ERR_HPI_BUSY where
appropriate (See description below).
1. Add snmp_bc_snmp_get() to snmp_bc.c/h to inteprete
STAT_TIMEOUT from snmp agent. If receiving STAT_TIMEOUT
five (5) times in the row, return SA_ERR_HPI_NO_RESPONSE;
otherwise return SA_ERR_HPI_BUSY. (a) Five (5) is arbitrary
selected. (b) snmp_bc_snmp_get() is snmp_bc plugin specific.
2. For the rest of snmp_bc plugin, use snmp_bc_snmp_get()
instead of snmp_get() where we know that initial snmp
communication has been established, i.e. hpiInit has been
successful. (a) More fine tuning may be needed here to add
or remove places that returns SA_ERR_HPI_BUSY.
3. To do: clients and example applications need to know and
handle SA_ERR_HPI_BUSY status.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=901950
Code was checked in to return SA_ERR_HPI_BUSY where
appropriate (See description below).
1. Add snmp_bc_snmp_get() to snmp_bc.c/h to inteprete
STAT_TIMEOUT from snmp agent. If receiving STAT_TIMEOUT
five (5) times in the row, return SA_ERR_HPI_NO_RESPONSE;
otherwise return SA_ERR_HPI_BUSY. (a) Five (5) is arbitrary
selected. (b) snmp_bc_snmp_get() is snmp_bc plugin specific.
2. For the rest of snmp_bc plugin, use snmp_bc_snmp_get()
instead of snmp_get() where we know that initial snmp
communication has been established, i.e. hpiInit has been
successful. (a) More fine tuning may be needed here to add
or remove places that returns SA_ERR_HPI_BUSY.
3. To do: clients and example applications need to know and
handle SA_ERR_HPI_BUSY status.