EXOS TFTP put to Netsight failing due to incorrect forward slash

[Anonymous]

Whenever I submit the command:

tftp put xxx.xxx.xxx.xxx vr "VR-Default" internal-memory
show_tech.log.gz

It fails with the following response:

Uploading show_tech.log.gz to xxx.xxx.xxx.xxx ... failed!

Error: (2) unable open file

The message in Netsight syslog is as follows:

127.0.0.1 open() file=C:\tftpboot/show_tech.log.gz client
session: xxx.xxx.xxx.xxx:57941



So my guess is with Netsight being windows based using a \ (backslash) and EXOS being Linux based and using a / (Forward slash), this is where the problem comes in.

Can't see how to correct this in EXOS as specifying a forward slash gives an error, and I don't know if there is a way to correct within the TFTP server in Netsight.

Have also tried the following:

X460.2 # tftp xxx.xxx.xxx.xxx -v "VR-Default" -p -l internal-memory show_tech.log.gz

Uploading show_tech.log.gz to xxx.xxx.xxx.xxx... failed!
Error: (2) unable open file

...

X460.3 # tftp xxx.xxx.xxx.xxx -v "VR-Default" -p -l internal-memory show_tech.log.gz -r show_tech.log.gz

Uploading show_tech.log.gz to xxx.xxx.xxx.xxx... failed!

Error: (2) unable open file

...

X460.4 # tftp xxx.xxx.xxx.xxx -v "VR-Default" -p -l internal-memory show_tech.log.gz -r \show_tech.log.gz

Error: Illegal filename (\show_tech.log.gz)

ExtremeXOS version 15.3.1.4

Netsight version 6.2.0.199

[Anonymous]

Hi Jesse,

I wonder if the switch is having trouble communicating with NetSight rather than a permissions issue.

For example I've seen something a bit similar to this before when NetSight has 2 interfaces with different IP's and it was communicating with the wrong one, or access to NetSight is via Vr-Mgmt instead Vr-Default.

Not saying its one of those but wonder if its worth adding the -c option in the nstftp.cfg file and running the following command directly on the X440's, taken from the script and see what the switch says the problem is:

tftp 10.1.1.16 -v "VR-Default" -p -l primary.cfg -r /configs/tmp/10_20_36_2/primary.cfg

It might also be worth running tcpdump on NetSight at the same time or before making the change to check that you are receiving the TFTP communication from the switch as you would expect.

Many thanks.

[Jesse_Ohlsson]

Hi Ronald,

It's what I posted above: https://community.extremenetworks.com/extreme/topics/exos-tftp-put-to-netsight-failing-due-to-file-s...

Here's what the Inventory server log recorded:

[Ronald_Dvorak]

OK I also run EMC 7.0 - could you please share the error description from the archive window...

[Ronald_Dvorak]

If you use inventory manager that shouldn't be a problem - only if you load files directly from a system to the TFTP directory...

"Inventory Manager will first create an empty file as part of the archive process before it tells the device to TFTP the config to the server."

You might want to take a look into this post...
https://community.extremenetworks.com/extreme/topics/am-using-netsight-to-backup-the-extreme-switch-...

[Jesse_Ohlsson]

Not so, Ronald. That error above was from Command Center. I wasn't asking about how to use the legacy application called Inventory Manager, which is a Java app. I don't want to use those old Java based legacy applications.

I can watch the folder on my Command Center server b:/tftpboot/configs/tmp/10_20_30_40/, and I can see Command Center create the files: nms.xsf, and primary.cfg, with filesize zero, as I'd expect to happen.

That's as far as it gets, until the archive fails, and I see another copy of the above error.