N3024 can't transfer file to tftp server (Yes the path is correct and TFTP is running)
-
Not sure how many of you here deal with Dell switches....
I just got a refurb N3024P from xByte.com. I unpacked it and then booted it up and started configuring. Things have gone fine so far except I am having a lot of trouble using TFTP (of all things) to update firmware and export configs, etc.
I do have a TFTP server running currently which I've used to grab firmware updates many times in the past for other N3000 switches. I just now tested TFTP with another N3000 switch to make sure I could export the running config to the TFTP folder as a test.txt file. It works perfectly and the file showed up right away and there were no errors.
I attempted the same thing with my new N3024 but it just sits there and says "0 bytes transferred" and then eventually fails. I used the EXACT same command as with the other switch, except I exported to "test2.txt".
NOTE: Yes the path is correct and yes TFTP is running on the server. I also ran WireShark on my server and filtered for TFTP and noticed that there was no traffic at all. So it's as if TFTP is not even running on the N3024P switch..
Commands that were used:
console# en
console# copy running-config tftp://192.168.10.36/Switches/filename.txtThe switch from xByte has the same firmware as the other N3000 which I have successfully tested TFTP on:
active: 6.3.3.8
backup: 6.3.2.3
current-active: 6.3.3.8
next-active: 6.3.3.8Any thoughts?
-
@dave247 said in N3024 can't transfer file to tftp server (Yes the path is correct and TFTP is running):
Not sure how many of you here deal with Dell switches....
I just got a refurb N3024P from xByte.com. I unpacked it and then booted it up and started configuring. Things have gone fine so far except I am having a lot of trouble using TFTP (of all things) to update firmware and export configs, etc.
I do have a TFTP server running currently which I've used to grab firmware updates many times in the past for other N3000 switches. I just now tested TFTP with another N3000 switch to make sure I could export the running config to the TFTP folder as a test.txt file. It works perfectly and the file showed up right away and there were no errors.
I attempted the same thing with my new N3024 but it just sits there and says "0 bytes transferred" and then eventually fails. I used the EXACT same command as with the other switch, except I exported to "test2.txt".
NOTE: Yes the path is correct and yes TFTP is running on the server. I also ran WireShark on my server and filtered for TFTP and noticed that there was no traffic at all. So it's as if TFTP is not even running on the N3024P switch..
Commands that were used:
console# en
console# copy running-config tftp://192.168.10.36/Switches/filename.txtThe switch from xByte has the same firmware as the other N3000 which I have successfully tested TFTP on:
active: 6.3.3.8
backup: 6.3.2.3
current-active: 6.3.3.8
next-active: 6.3.3.8Any thoughts?
can you ping from the new switch to the TFPT server, or vice versa?
-
@dashrender said in N3024 can't transfer file to tftp server (Yes the path is correct and TFTP is running):
@dave247 said in N3024 can't transfer file to tftp server (Yes the path is correct and TFTP is running):
Not sure how many of you here deal with Dell switches....
I just got a refurb N3024P from xByte.com. I unpacked it and then booted it up and started configuring. Things have gone fine so far except I am having a lot of trouble using TFTP (of all things) to update firmware and export configs, etc.
I do have a TFTP server running currently which I've used to grab firmware updates many times in the past for other N3000 switches. I just now tested TFTP with another N3000 switch to make sure I could export the running config to the TFTP folder as a test.txt file. It works perfectly and the file showed up right away and there were no errors.
I attempted the same thing with my new N3024 but it just sits there and says "0 bytes transferred" and then eventually fails. I used the EXACT same command as with the other switch, except I exported to "test2.txt".
NOTE: Yes the path is correct and yes TFTP is running on the server. I also ran WireShark on my server and filtered for TFTP and noticed that there was no traffic at all. So it's as if TFTP is not even running on the N3024P switch..
Commands that were used:
console# en
console# copy running-config tftp://192.168.10.36/Switches/filename.txtThe switch from xByte has the same firmware as the other N3000 which I have successfully tested TFTP on:
active: 6.3.3.8
backup: 6.3.2.3
current-active: 6.3.3.8
next-active: 6.3.3.8Any thoughts?
can you ping from the new switch to the TFPT server, or vice versa?
hmm, from the new switch, it seems I can't get a ping response from anything except itself. I don't know why though. I set up the ip and netmask correctly as well as the default gateway.
show ip interface and show ip route display the same things as my other working switch (aside from the different unit IP addresses). They are both VLAN1 as well.
I mean, the switch works and is on the LAN connected to another LAN switch and I am accessing it through SSH and HTTPS just fine. This is starting to concern me...
-
I got it working by resetting to factory defaults and running the setup Wizard. I tried to do that right away the first time but I missed the option and the switch booted, so I configured it without the Wizard. It probably shouldn't matter so I don't know why it seems to in my situation.
-
@dave247 Well obviously, because you missed something. Otherwise it would have the same result with the wizard as you did manually.
Not having a copy of your config vs a copy of the wizard config, who knows what it was.
-
@dave247 said in N3024 can't transfer file to tftp server (Yes the path is correct and TFTP is running):
I got it working by resetting to factory defaults and running the setup Wizard. I tried to do that right away the first time but I missed the option and the switch booted, so I configured it without the Wizard. It probably shouldn't matter so I don't know why it seems to in my situation.
Probably is best practice to reset to defaults when you receive a new device. This way you know you go the settings right from the get go. What you should also know is that you should configure the default first, login to the switch and change the IP address or use the USB Console to Serial.
-
@jaredbusch said in N3024 can't transfer file to tftp server (Yes the path is correct and TFTP is running):
@dave247 Well obviously, because you missed something. Otherwise it would have the same result with the wizard as you did manually.
Not having a copy of your config vs a copy of the wizard config, who knows what it was.
Yeah I'm sure I missed something, but the wizard really only asks for admin name, password, then the switch ip information, then it boots. All these things you can also set manually, which I did. I set them exactly the same as in the wizard. I checked everything numerous times and found no discrepancies. Beats me.
