- Change in switch initialization settings to protect against loss of connectivity between internal switch and modem.
- Web Interface supports only single level access.
- Loopback Mode - rf_refl is not supported in this release.
- BER is only available for internal data pattern with QAM256 not for live link.
To apply the upgrade from 2.0, simply load the sys_fw file via tftp, issue the command bootimage upgrade 2 and reboot. If you are running an earlier version, like 1.3.1, you will need to transfer the images as included in the 2.0 or 2.0.1 release: Apex 2.0.1 Firmware & MIB | Apex 2.0 Firmware & MIB
Detailed upgrade instructions can be found in a previous release or the manual. If applying the beta release, please subscribe to this thread so you can be notified of any updates/comments. Please note that the CRC checksum in the filename may change in subsequent postings.
Please see the comments below for the latest release.
Attached is the 5/15 beta.
Anyone is welcome to apply the upgrade, but we are awaiting feedback from certain customers who are trying it before releasing it. I have not received any word that they have experienced any problems with the new firmware, so if you'd like to install it for added protection, you may do so.
This release includes the previous changes, including disabling MAC address learning.
We are running 2.1 and are having traffic stoppages on our link. I am leaning towards believing this is an RF issue with ducting causing fading in the early morning hours... but how can we verify whether we are experiencing this loss of connectivity issue between internal switch and modem?
I do inexplicably see that the GE1 and GE2 indicators in the GUI are both red, even when traffic is passing over the link (we are using copper 1000 FDX for data). Any relation to issues that may be fixed by this beta release?
Please sign in to leave a comment.