![]() As I already wrote in this incident, Management Center was aware of this new path, as I could observe it create the appropriate files in the tftpboot/configs/tmp/ directory to prepare for a switch to send its configs to the Management Center server. ![]() Of course, I had to manually create the tftpboot/ and its subdirectories on that new drive letter, which I did. I found where to change this in Management Center > Administation > Options > Inventory Manager > File Transfer, and did so, assigning the path for TFTP to another drive letter (b:/, on my server). When I installed Management Center, I don’t think it ever gave me an option of changing the path to the TFTP root directory, which defaults to (C:/tftpboot). X460.4 # tftp -v "VR-Default" -p -l internal-memory show_ -r \show_Įrror: Illegal filename (\show_) X460.3 # tftp -v "VR-Default" -p -l internal-memory show_ -r show_ X460.2 # tftp -v "VR-Default" -p -l internal-memory show_ 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.Ĭan'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. ![]() The message in Netsight syslog is as follows:ġ27.0.0.1 open() file=C:\tftpboot/show_ client ![]() Tftp put vr "VR-Default" internal-memory ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |