---

Hej. Jeg har installeret og compiled mrtg på min Linux box.

Men når jeg vil lave en cfgfil med cfgmaker får jeg denne fejl:

root@gimli:/usr/local/mrtg-2/bin# ./cfgmaker public@10.0.0.1
--base: Get Device Info on public@10.0.0.1:
SNMP Error:
no response received
SNMPv1_Session (remote host: "10.0.0.1" [10.0.0.1].161)
community: "public"
request ID: -1301896935
PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/local/mrtg-2/bin/../lib/mrtg2/SNMP_util.pm line 622
SNMPWALK Problem for 1.3.6.1.2.1.1 on public@10.0.0.1::::::v4only
at ./cfgmaker line 821
WARNING: Skipping public@10.0.0.1: as no info could be retreived

I min Cisco 677 har jeg tilføjet en SNMP Manager således:

cbos#set snmp manager 10.0.0.4 public read on all
Added SNMP Manager

og

SNMP Configuration
Currently enabled
Currently accepts connections from any host
Currently not sending any traps

Håber nogen kan komme med et godt bud eller en god forklaring.
--

/ Benjamin

---

Benjamin wrote:
>> Hej. Jeg har installeret og compiled mrtg på min Linux box.
>>
>> Men når jeg vil lave en cfgfil med cfgmaker får jeg denne fejl:
>>
>> root@gimli:/usr/local/mrtg-2/bin# ./cfgmaker public@10.0.0.1
>> --base: Get Device Info on public@10.0.0.1:
>> SNMP Error:
>> no response received
>> SNMPv1_Session (remote host: "10.0.0.1" [10.0.0.1].161)
>> community: "public"
>> request ID: -1301896935
>> PDU bufsize: 8000 bytes
>> timeout: 2s
>> retries: 5
>> backoff: 1)
>> at /usr/local/mrtg-2/bin/../lib/mrtg2/SNMP_util.pm line 622
>> SNMPWALK Problem for 1.3.6.1.2.1.1 on public@10.0.0.1::::::v4only
>> at ./cfgmaker line 821
>> WARNING: Skipping public@10.0.0.1: as no info could be retreived
>>
>> I min Cisco 677 har jeg tilføjet en SNMP Manager således:
>>
>> cbos#set snmp manager 10.0.0.4 public read on all
>> Added SNMP Manager
>>
>> og
>>
>> SNMP Configuration
>> Currently enabled
>> Currently accepts connections from any host
>> Currently not sending any traps
>>
>> Håber nogen kan komme med et godt bud eller en god forklaring.

OK -... pinligt. En genstart af routeren er åbenbart nødvendigt. Nu virker
alt som det skal.
--

/ Benjamin