Hi Jason and hi Issac,
only one device is facing this problem that began about when it got an IOS Update.
The tcp-dump packet capture is showing an interesting pattern:
xx.xx.xx.xx.60955 > 172-2-23-1.lightspeed.sntcca.sbcglobal.net.snmp: [bad udp cksum 622e!] { SNMPv2c C=snmp-rw { GetNextRequest(33) R=201148990 E:cisco.9.109.1.1.1.1.8 } }
172-2-23-1.lightspeed.sntcca.sbcglobal.net.snmp > xx.xx.xx.xx.60955: [udp sum ok] { SNMPv2c C=snmp-rw { GetResponse(35) R=201148990 E:cisco.9.109.1.1.1.1.8.19=6 } }
The pattern "bad udp cksum", does it reveal something to you?
Thank you very much.
Rudi
Original Message:
Sent: 08-24-2021 11:44 AM
From: Jason Volpini
Subject: SPC-OCC-10747: Error capturing configuration for host: Failure.
Hello
I would suggest to run a tcpdump or Wireshark packet capture. The packet traffic can be very helpful in troubleshooting NCM capture errors.
------------------------------
Jason Volpini
Senior Support Engineer | Enterprise Software
Broadcom
Original Message:
Sent: 08-23-2021 05:58 AM
From: Rudi Baldo
Subject: SPC-OCC-10747: Error capturing configuration for host: Failure.
Hi world,
when I try to capture the configuration by SNMP/TFTP I get the answer: "SPC-OCC-10747: Error capturing configuration for host: Failure.".
In the Eventlog, I see that message:
"Configuration Manager - Capture failed with Primary communication mode SNMP/TFTP for host running configuration file from device xxxxxx of type SwCiscoIOS on landscape xxxxxx initiated by user xxxx.
Specific error: The file transfer on the device timed out.
The network may be overloaded or the TFTP server on the SpectroSERVER machine may not be running or responding."
We have the SNMP RW rights on that device and we increased the DCM Timeouts to the maximum of 6000 ms, TFTP server is up and running, but I don't see any other possibility to look for a missconfiguration.
Does anyone of you has an idea how to fix this problem?
Thank you very much.
Rudi