On the test I will update the firmware in BDCOM P3310C, firmware can be taken here:
http://support.deps.ua/ (need registration)
ftp://ftp.romsat.ua/pub/Lan/BDCOM/
Here are a few more:
https://files.ixnfo.com/Firmware/BDCOM/P3310C/BD_3310C_10.1.0E_43480_en.bin
https://files.ixnfo.com/Firmware/BDCOM/P3310C/BD_3310C_10.1.0F_89898.bin
https://files.ixnfo.com/Firmware/BDCOM/P3310C/BD_3310C_10.1.0F_106557.bin
Below I will describe the procedure for updating the firmware.
We connect to the device via telnet or console cable and see the current firmware version by running the command:
show version
In my case it was displayed:
BDCOM(tm) P3310C Software, Version 10.1.0E Build 43480
Let’s switch to the privileged mode and look at the contents of the file system of the device:
enable
dir
There was little free memory in the device, there is not enough for the second firmware file, so you will have to delete the current one later.
Let’s make a copy of the tiger.blob file, the startup-config configuration and the Switch.bin firmware on the tftp server:
copy flash tftp 192.168.1.2
Articles about the TFTP server are listed in my other articles:
Installing and Configuring a TFTP Server in Ubuntu
Starting a TFTP server in Windows
The new firmware file with the .bin extension, which was downloaded earlier, will be placed on the tftp server.
Delete the active firmware file on the device if there is not enough space to download a new one (it should be noted that if the electricity is lost while copying the new firmware file, the device will have to be restored):
delete Switch.bin
Now upload the new firmware to the device:
copy tftp flash 192.168.1.2
Source file name? BD_3310C_10.1.0F_84499.bin
Destination file name? Switch.bin
When the file is successfully copied to the device, it will reboot to start from the new version:
reboot
Done, the firmware upgrade is complete.
The following MAC addresses are reserved for new firmware versions and can not be used:
X2:XX:XX:XX:XX:XX Local Administered
X6:XX:XX:XX:XX:XX Local Administered
XA:XX:XX:XX:XX:XX Local Administered
XE:XX:XX:XX:XX:XX Local Administered
That they could be used we execute a command:
epon local-mac forward
Also, after the firmware update, the syntax of some commands may change.
I updated it remotely via telnet, the configuration remained, some out-of-date commands in the configuration, for example those starting with sntp, automatically changed to ntp.
See also my articles:
BDCOM OLT Recovery
BDCOM P3310B firmware update
BDCOM P3310D Firmware Update