Hi Bill,
Thanks for getting back to me and for the info.
Had unfortunately already tried that but it still didn't work, for the same reason........
If you look at my internal memory you can see the show_tech.log.gz file listed
X460.3 # ls internal-memory
-rwxr-xr-x 1 root 0 62357 Apr 22 10:51 show_tech.log.gz
-rwxr-xr-x 1 root 0 161911 Apr 22 10:51 trace.devmgr.1421
-rwxr-xr-x 1 root 0 592 Apr 22 10:51 trace.fdb.1443
-rwxr-xr-x 1 root 0 608 Apr 22 10:50 trace.mcmgr.1490
-rwxr-xr-x 1 root 0 143117 Apr 22 10:51 trace.nodemgr.1425
-rwxr-xr-x 1 root 0 600 Apr 22 10:51 trace.rip.1497
-rwxr-xr-x 1 root 0 608 Apr 22 10:51 trace.rtmgr.1482
-rwxr-xr-x 1 root 0 1034 Apr 22 10:45 trace.vlan.1441
If you run the upload debug command you get the following:
X460.2 # upload debug xxx.xxx.xxx.xxx vr "VR-Default"
Do you want to run show tech logto file first? (y/N) Yes
Upload debug cancelled. Please run show tech logto file now.
X460.4 # upload debug xxx.xxx.xxx.xxx vr "VR-Default"
Do you want to run show tech logto file first? (y/N) No
.......................................................................................................
Error: tftp: server error: (2) unable open file
Netsight gives the following error:
Upload Engineering to hostname ip address xxx.xxx.xxx.xxx VR VR-Default
Upload Engineering failed. Failed to tftp intern tarball to server
In order to find out more what is going on I enabled the debug mode on the TFTP server. This is done by editing the nstftpd.cfg file in the Netsight services file. The option you can have are as follows:
Usage : tftpd [-v][-c][-d dirname][-p pidfilename][-trace][-debug]
-v print version and exit
-c allow tftpd to create uploaded files if they do not already exist.
-d use the specified dirname as the base where tftpd will look to read/store files
-p use the specified pid file name to store the pid of the process
-fg run tftpd in the foreground rather than
So I changed the:
-d "c:\tftpboot"
to
-d "c:\tftpboot" -debug
Now the syslog on Netsight shows the following issue:
Netsight 127.0.0.1 open() file=C:\tftpboot/X460_I_04230955.tgz client session: xxx.xxx.xxx.xxx:38436
Netsight 127.0.0.1 Sending error (2) -- unable open file to client session: xxx.xxx.xxx.xxx:38436
Netsight 127.0.0.1 Retrieving session client session: xxx.xxx.xxx.xxx:38436
Upload Engineering failed. Failed to tftp intern tarball to server
Received write request file=X460_I_04230955.tgz mode=octet client session: xxx.xxx.xxx.xxx:38436
So two things about that don't seem right, the first is the slash is in the wrong direction again and the file is "X460_I_04230955.tgz", instead of" show_tech.log.gz" that was created by the show tech command?
Also if I run the following:
X460.6 # upload configuration xxx.xxx.xxx.xxx primary.cfg vr "VR-Default"
Uploading primary.cfg to xxx.xxx.xxx.xxx ... failed!
Error: (2) unable open file
Netsight reports the same problem with the slash in the wrong direction:
Netsight 127.0.0.1 open() file=C:\tftpboot/primary.cfg client session: xxx.xxx.xxx.xxx:51367
At first I thought the issue might be a firewall problem, but the permission for TFTP has been added and the firewall logs are not showing a deny.
The other thought was that there might be a permissions issue on the c:\tftpboot folder, which I am still looking into but at the moment the slash seems to be the most obvious issue.
So as you can see no matter what command I use the slash is always in the wrong direct for use on Netsight / windows tftp server?