Do not load profiles from 6000 series?

Scott - WM7C

I imported profiles from my old 6400M onto my 8600 and the radio seemed fine. Then I shut it off. When I turned it back on a few hours later, the radio will not start. I submitted a ticket, but wanted to warn others incase they try this. I read I'm not the only one.

I followed the instructions for the 6000 series to factory reset, but this results in a flashing red light for several tries. I read that I may need an image and instructions for loading the image.

Chris Long

I am right with you! Happened late on Friday, after just receiving the new radio. Transferred my 6600 profiles, and a couple boots later it fails. Ticket submitted, back to waiting …

Chris N1CL

Chris Long

Ken from the Helpdesk just replied to me, and was very helpful in providing instructions on how to recover the system. It appears that the issue arises when profiles are imported from a 6x00 series that was configured with a static IP address. Hopefully you can resolve your issues soon as well.

Mike-VA3MW

You should not have an issue importing profiles, but if you do, let us know.

There is a bug with static IP addresses on v3.8.19 that is fixed in the next release coming out shortly. For the meantime, please do not set a static IP address and if you need a fixed/static IP address then make sure you use a DHCP reservation.

For most customers, there is really no requirement to use static IP addresses as there is no performance reason, even with SmartLink and uPNP.

But, if you are a network person and you understand the implications of doing so, you are welcome to do that.

If your networking skills are limited, the radio works wonderfully out of the box with the current networking setup.

Scott - WM7C

I must have had a static IP set in the profiles. My issue is resolved through support.

Flexed

Network professionals favor static IP addresses because they are not dependent on another service (DHCP) for the provision of IP addresses.

David Decoons, wo2x

Two of the main reasons we recommend DHCP reservation over static are:

1. Troubleshooting. If you need to troubleshoot you can connect the radio direct to computer and use link local IP. without changing radio to DHCP. Especially if radio becomes unreachable on network.
2. Subnet changes. You go out and buy a new router but instead of 192.168.0.x the new router uses 192.168.1.x. There would be no Internet access since the gateway changed. It
   

Remember, most hams are not I.T. Professionals so it needs to be as simple as possible.

73 Dave wo2x

Mike-VA3MW

To add to what Dave says.

Public Service Announcement.

Please do NOT do Static IP unless you fully comfortable of TCP/IP addressing. Our support team spends a lot of time undoing these changes. It often happens when their 'buddy' drops in, configures everything as static and then disappears. A year later the owner can't tell us what was done.

DHCP servers have been in place since the 90's. They work and they work well. Millions of devices run on DHCP servers without issue and since they know were all the 'stuff' is they prevent conflicts.

I know that it is in the SmartSDR for MAC documentation that static is highly recommended, and yes, there might be a case or 2 where that is the solution. However, I have run multiple radios on the same network using DHCP and DHCP reservations using all sorts of client software without issue.

Flexed

Okay, guys, I don’t want to cause any trouble. I’m a Network Engineer, but you know the FlexRadio better than I do. (I’m waiting for the 8400m to arrive.) I’ll leave it as DHCP, but I’m reading that I could use the radio as an NTP server. How would I do that if I’m using dynamic IP addresses? and don’t bring DHCP reservations. (We just said that not everyone is IT.)