Firmware 3.21 issues

I can't help with the problem but before you downgrade I thought I'd draw your attention to a point in the 3.21 update documentation TN-0020 Issue 6.

... [PRINTED IN RED] After upgrading to 3.21, do not attempt to downgrade to a previous version.

My firmware update forced a factory reset (on my ND5XS) so that all iradio presets disappeared but I was able to add new stations and iradio seems to be working OK. Presumably you had to go through the same process but you seem to be having other issues as well.

Hi, I've got a issue with the update, too. I've tried both updaters (PC and MAC). And with both it won't find the IP address of my uniti. The actual firmware is 3.16 and I've tried to shut down, disconnect etc. several times. Any ideas out there? Thanks

Not so fast! All I've done so far is read all the words 3x over as I don't want to make an avoidable mistake (I'm not suggesting you have). Finger's crossed my SU will arrive next week with 3.21 pre-installed, all I have to do is grasp the nettle & update the kit I have...

Do you have a fixed IP address set? If not, it would be a good idea.

First of all apologies to Naim for doubting the firmware which I don't think is essentially at fault - but.....

It appears to be an odd coincidence that the two Sonos units I am using caused an odd conflict with the Uniti even when I re-installed firmware version 3.17. 

One of the Sonos units was on an adjacent IP address to the Uniti and once I moved it and the Uniti to reserved IPs far away from each other the problem was resolved - uniti that is I added the second Sonos and the problem recurred even though it was on a far away address. Oh well, there isn't a need for this unit to be wired so I disconnected it and all is well. I am not sure if this is an issue with the way Sonos arrange themselves on the network or not, but it is something we should take care about.

Any help on this matter gratefully received too!

As for downgrading the firmware, I had no issues whatsoever doing this despite the warnings on the documentation. Now it's al working (more or less) I see no reason to downgrade but if anyone is thinking of dong it, it appears to wok.

Thanks to all who have replied, keep going, the Sonon issue is still there - but that's for a Sonos forum too I guess.

I occasionally have problems if I have to reconnect to the network. I usually find that resetting my router (power off and on again) and then re-powering the Uniti then selecting internet radio appears to force the Uniti to seek an address and sorts it out. Beyond that I find everything rock solid apart from problems with other kit appearing to cause conflicts, but that isn't a Naim blame thing of course!

If you are on firmware version 3.16 then I think you will find that you need to upgrade to firmware 3.17 successfully before you can then upgrade to firmware version 3.21.

Sorry but it is unclear as to what you mean by Sonos issue. I assume you are using DHCP for your LAN and your Sonos (Connect/Play etc) are assigned IP addresses by your router dynamically and that you have used the feature found in most routers to always assign the same IP address to a specific MAC. If you do this for all you Sonos units and your Uniti then you should not get any IP address conflicts.

(Oversimplifying this a bit,) Sonos' roomplayers tend to issue a fair bit of traffic onto the (wired) network, which can affect other UPnP / DLNA devices.  There are a few ways you can mitigate this (excluding more sophisticated traffic-shaping, etc.):

1. Connect all Sonos units via wired Ethernet to a dedicated switch, which connects to the primary (wired) network
2. Use Sonos' wireless mesh network, if possible (could be a wild ride in congested urban markets!)
3. Use a nested network router (with a dedicated Wi-Fi SSID) to host the Sonos roomplayers via wired Ethernet

My advice (and I suspect the simplest) would be to use the Sonos wireless mesh network for all Sonos devices except the one that you have to connect via a wired connection. This works well in a non congested environment and has the advantage of keeping most of the Sonos traffic off your normal wired and wireless networks. The reason for this is that Sonos will always try to use the mesh network as well as any wired connections. This will cause a loop and in such cases you can get broadcast storms which flood the network. Luckily Sonos supports  STP (Spanning Tree protocol) but  your switch or switches need to provide support for this too. If they don't then you can get some weird and wonderful effects. If you have one switch and all your Sonos units are wired to it then it just needs to provide minimal STP support - i.e. just pass through the STP BPDU packets. If however you connect multiple Sonos units to different switches then the switches need to work to together in the same way with STP.

Hi, hafler3o

My response related to Daunt's original post about his iradio problem following the firmware update but clearly I didn't make this clear. I hope my post didn't cause you any issues.

No problem at all! Maybe it was me misreading things 

There is a problem with the internet radio service - see the stickies at the top of the forum. Nothing to do with the upgrade.

Scillyisles, most on here won't know about IEEE STP and it's  use of BPDU ( bridge protocol data unit) frames- its not that kind of forum. Implying that users should check their switches support itI i suspect might only add confusion, as a typical consumer switch manual will make no mention of it and to the non initiated it will sound like double Dutch.

Fortunately IEEE BPDU  is a 802.2 LLC frame, which has a source and destination MAC address just like an Ethernet frame. The destination address is the 'well-known' IEEE link layer discovery mac address used by many discovery application from Cisco Discovery Protocol to Microsoft Link Layer Topology Protocol.

Therefore consumer switches are going to almost certainly support this by treating the BPDU as a 802.2 frame (which is what switches are supposed to do),I otherwise many consumer network LAN functions won't work properly and Sono wouldn't be relying on it unduly.. What we don't expect a consumer switch to do is shut the port down itself in a loop, but the bridge unit (Sonos) will be doing that.

So i suspect  for 99.99% of issues we don't need to worry the poor consumer whether their consumer switch supports kink layer discovery frames and BPDUs, as for most known makes they will.

Simon

Hi,

I’ve also experienced some severe issues after ugrading from 3.17 to 3.21 on my NDX. The updating process went fine, and after installing the NDX again everything worked just fine, but when I should listen to the system again the next day I got no contact to the NDX via nStream and the following text (maybe not literally) was displayed on the NDX “Firmware upgrade finished successfully, please shut down your NDX”. So I did, and it worked fine for some hours. Then the problem repeated again and again.  This is really annoying and since it is not recommended to switch back to 3.17 I do not know what to do. Truly grateful for any advice!

BR K

Call your dealer or Naim.

Just add a router, connect it to your main router (for internet access), permit access only to the items you mention. Leave the other units to access the main router.