V2.8.6
======

- FEATURES

With v 2.8.6 Luminex brings a number of improvements to the GigaCore range for increased compatibility
and stability.

Reliably operating a network with an increasing variety of PoE powered devices currently coming to the
market such as PTZ camera’s, active loudspeaker systems etc. may require a wider power specification
range than strictly standardized in the PoE standards. With v2.8.6 Users can now connect and operate
these devices with confidence.

Also included in this release are AVB/Milan fixes (mainly gPtP and MSRP) that improve stability after linkup/-
down events. These stability fixes mainly resulted from testing large scale real live applications’ edge
cases (like power down and up complete systems at once with more than 200 Milan end devices). These
fixes ensure stable and fast recovery after such events.

User friendliness and status monitoring have been improved with a correction on certain LED indicators,
now indicating the status as specified.

Configuration settings when changing certain GigaCore configuration parameters through Araneo, are
now correctly applied to the GigaCore switches


- FIXES & IMPROVEMENTS

PoE Related:

• Allow PoE class changes at power-up of PoE devices and guarantee power delivery.
• Add multiple power-up attempts when devices disconnect themselves.
• GigaCore 10 PoE occasional startup issue fixed.
• PoE timers set to be more tolerant to non PoE compliant devices.
• Change power limitation threshold window to 1s to allow PoE powered devices with very fluctuating power needs (more robust and tolerant).


AVB Related:

• Listener stuck in Asking Failed state.
• gPtP portEnabled state now always correct after link down.
• Speed up SFP readout to avoid interference on gPtP.
• gPtP port enable state at boot up occasionally incorrect.
• Avoid incorrect timestamp in peer-delay responses after link down occurred.


Araneo Related:

• SNMP saved correctly before any possible reboot.
• PtP settings can now be saved and applied correctly.
• MultiLinkX set during deployment now also sets the defaults of the aggregation correct.
• Wait 500ms to apply IP changes in order for Araneo to get a valid IP change reply.