Opened 13 years ago
Closed 12 years ago
#83 closed defect (fixed)
a bug about snmpwalk_flg function
Reported by: | human | Owned by: | somebody |
---|---|---|---|
Version: | 2.x | Keywords: | snmp |
Cc: |
Description
i use mrtg to gather device's iftable infomation, the ifDescr back error.it's all the same description, such as
==[0]=gei_0/9/4
==[1]=gei_0/9/4
==[2]=gei_0/9/4
==[3]=gei_0/9/4
==[4]=gei_0/9/4
==[5]=gei_0/9/4
==[6]=gei_0/9/4
because the mrtg use get_bulk_request to get the port infomation, maybe the device doesn't support this function.
if use get_next_request, it return the true result.
so i think the function snmpwalk_flg in Net_SNMP_util.pm,such as
if ($Net_SNMP_util::Version > 1) {
$args{'-maxrepetitions'} = $Net_SNMP_util::MaxRepetitions?;
}
could write like this:
if ($Net_SNMP_util::Version > 1 && $Net_SNMP_util::MaxRepetitions? > 1) {
$args{'-maxrepetitions'} = $Net_SNMP_util::MaxRepetitions?;
} .so when the snmp version is v2c, and i want to use get_next_request to get infomation, i can config $Net_SNMP_util::MaxRepetitions? = 0
Change History (1)
comment:1 Changed 12 years ago by oetiker
- Resolution set to fixed
- Status changed from new to closed
I have added this in r318