tftp issue after upgrading NPM and Cirrus -Orion

Question

I have upgraded both Enginner's Toolset and Cirrus Network Configuration Manager to v9 and Orion 5.0. The former scheduled job for daily configuration backup stopped to work. I have already found on Thwack that the new version of TFTP server does not support the mapped drives. Well, I have created the backup folder on the local disk. But it did't help. The copy tftp command entered on a switch works well: cs-diag1#copy run tftp://147.231.126.13/test Address or name of remote host [147.231.126.13]? Destination filename [test]? !! 6863 bytes copied in 0.629 secs (10911 bytes/sec) cs-diag1# The file copied is on the supposed place: Directory of D: \Zalohy_Cisco 14.11.2008 21:58 . 14.11.2008 21:58 .. 14.11.2008 21:58 6 863 test 1 File(s) 6 863 bytes 2 Dir(s) 34 863 626 752 bytes free If I enter the same command as a scheduled job, the job seems to finish properly but nothing is copied and SolarWinds TFTP server displays no activity: command Script -------------- copy running-config t147.231.126.13/config_run -------------- cs-diag1.fzu.cz: copy running-config t147.231.126.13/config_run Address or name of remote host [147.231.126.13]? ___________________________________________________________________________ 14.11.2008 22:00:53 : Completed test_tftp : Job-559517 ; Devices : 1 ; Errors : 0 Execution time : 4 seconds ___________________________________________________________________________ What I am doing wrong? Tomas

Tomas · Answer

Thanks Chris for your prompt reaction. Yes, I hope I have TFTP server started. The copy tftp command entered on the switch console works well - config is copied via TFTP and TFTP log is completed. I see now a progress in the issue. The test job  copy running-config "t">147.231.126.13/config_run"     launched from Orion by command "Test Job" works only seemingly -

the job log is created but nothing is copied and TFTP log remains unchanged. The original scheduled job

"copy run t147.231.126.13/${sysname}.config.text

${CRLF}

copy vlan.dat t147.231.126.13/${sysname}.vlan.dat

${CRLF}

${CRLF}"

launched on scheduled time worked almost well - all configs.text and vlan.dat were copied on the same place to the file named "${CRLF}". It means that the variable ${sysname} was not interpreted.

Remark: The text entered "tftp..." converts THWACK to the link "ftp..." . I don't know how to awoid it.

Regards,

Tomas

chris.lapoint · Answer

Do you have Engineer's Toolset TFTP server service started?