NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XSM4348S firmware update causes errors
Hi all, I've got a M4300 24x24F that is currently running firmware version 12.0.0.19, with a backup image of 12.0.0.14 (The original firmware that came on the switch). when loading the switch w...
When trying newer firmware like 12.0.2.6 and 12.0.4.8 the interfaces stop working.
When i plug a cable into them nothing happens.
Even if i do no shutdown on said interface
Hi
According to the date code in the download archive the firmware releases you've tested so far are both quite a bit outdated: 12.0.2.6 dates from october 2016, while 12.0.4.8 ist from april 2018, honestly not worth trying such outdated firmware release at this point. The process over the CLI (be it SSH, Telnet or serial console) is very robust, maybe your are hitting a browser compatibility issue due to your old firmware.
If it's for one switch I'd suggest doing a backup of the config first, then use the CLI over serial console and i.e. copy the latest firmware to the currently inactive firwmare image from a USB key (which is often easier than using SCP or TFTP). M4300's have a RJ45 ("Cisco-style pinoput") or a simple Mini-USB port for serial console. For the later, on Windows you need to install driver from the download section, whereas on Linux no drivers are required. Use any serial console tool like screen, miniterm, PuTTY or Tera Term and connect to the USB-to-serial using 115'000 baud rate.
! Identify your currently active firmware image show bootvar [...] Images currently available on Flash ---- ------------ ------------ ----------------- ----------------- unit image1 image2 current-active next-active ---- ------------ ------------ ----------------- ----------------- 1 12.0.X.XX 12.0.Y.Y image2 image2 2 12.0.X.XX 12.0.Y.Y image2 image2 ! Copy the firmware image to image1, as image2 is our currently active image copy usb://m4300v12.0.11.16.stk image1 [...] ! Verify the updated firmware image show bootvar [...] ---- ------------ ------------ ----------------- ----------------- unit image1 image2 current-active next-active ---- ------------ ------------ ----------------- ----------------- 1 12.0.11.16 12.0.Y.Y image2 image2 2 12.0.11.16 12.0.Y.Y image2 image2 ! Activate image1 at next boot boot system image1 ! Verify that this has worked show bootvar [...] ---- ------------ ------------ ----------------- ----------------- unit image1 image2 current-active next-active ---- ------------ ------------ ----------------- ----------------- 1 12.0.11.16 12.0.Y.Y image2 image1 2 12.0.11.16 12.0.Y.Y image2 image1 ! Save current config to NVRAM (precaution) write memory confirm ! Reboot the switch / stack reloadAfter a reboot you can use the CLI i.e. to check the logs (show logging buffered) or the interface status (show interfaces status ...), even the SFP etc. Using the serial console might be it easier to understand as to why your ports didn't come up on mentioned releases.
When uploading firmware version 12.0.11.16 from an usb stick and rebooting the interfaces don't come up anymore.
show logging buffered shows this
<13> Jan 1 00:03:01 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 498 %% Session 0 of type 1 started for user admin connected from EIA-232.
<13> Jan 1 00:02:39 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 490 %% Entity Database: Configuration Changed
<13> Jan 1 00:02:37 192.168.0.239-1 TRAPMGR[boxs Req]: traputil.c(795) 489 %% Temperature state change alarm: Unit Number: 1 Current: Normal, Previous: None
<13> Jan 1 00:02:37 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 488 %% SFP+ inserted in 1/0/2
<13> Jan 1 00:02:36 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 486 %% Power On Start has completed on unit 1.
<13> Jan 1 00:02:36 192.168.0.239-1 DRIVER[cmgrInsertTask]: l7_usl_port_sync.c(3467) 484 %% Port sync failed for FP Unit 1, bcm_unit 0 bcm_port 26 rv -4
<11> Jan 1 00:02:36 192.168.0.239-1 DRIVER[USL Control Tas]: l7_usl_port_sync.c(2113) 483 %% Db PORT_DB(2) sync failed, error code -4 Port Info: cmd 24 bcm_unit/port 0/25
<12> Jan 1 00:02:35 192.168.0.239-1 PTP_TC[ptpTc]: cnfgr_hw_tally.c(356) 479 %% PTP_TC reported unexpectedly for L2 hardware reconciliation
<13> Jan 1 00:02:35 192.168.0.239-1 General[procLOG]: procmgr.c(2444) 477 %% Administrative Command:app-start DiscoveryAgent
<13> Jan 1 00:02:35 192.168.0.239-1 IP[ipMapProcessing]: vrf_util.c(1563) 476 %% Registered IPMAP-0 as a best route callback with RTO
<12> Jan 1 00:02:34 192.168.0.239-1 PVT_GROUP[nim_t]: cnfgr_hw_tally.c(356) 469 %% PRIVATE_GROUP_VLAN reported unexpectedly for L2 hardware reconciliation
<13> Jan 1 00:02:33 192.168.0.239-1 USB_FD[emWeb]: usbFlashDrive_core.c(903) 465 %% There is startup-config on flash.
<13> Jan 1 00:02:33 192.168.0.239-1 SIM[emWeb]: sim_util.c(3869) 439 %% Switch firmware operational: M4300-24X24F ProSAFE 24-port 10GBASE-T and 24-port 10G SFP+, 12.0.11.16, B1.0.0.15
<13> Jan 1 00:02:33 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 430 %% Link Down: vlan 500
<13> Jan 1 00:02:33 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 425 %% Link Down: vlan 1
<13> Jan 1 00:02:29 192.168.0.239-1 IP[tRpcsrv.02000]: openr_policy.c(1438) 236 %% Added RPPI routing policy client ospf:0.
<13> Jan 1 00:02:29 192.168.0.239-1 General[Cnfgr_Thread ]: l7utils_inet_addr.c(508) 105 %% INET_ADDR:Invalid FamilyType - 0
<13> Jan 1 00:02:28 192.168.0.239-1 SIM[Cnfgr_Thread ]: sim_svc_port.c(337) 104 %% Service port IPv4 address has been set to 192.168.0.239.
<13> Jan 1 00:02:28 192.168.0.239-1 SIM[Cnfgr_Thread ]: sim_svc_port.c(337) 100 %% Service port IPv4 address has been set to 192.168.0.239.
<13> Jan 1 00:02:28 192.168.0.239-1 SIM[Cnfgr_Thread ]: sim_svc_port.c(337) 99 %% Service port IPv4 address has been set to 192.168.0.239.
<13> Jan 1 00:02:24 0.0.0.0-0 General[procLOG]: procmgr.c(2444) 35 %% Administrative Command:app-start traceroute-0
<13> Jan 1 00:02:24 0.0.0.0-0 General[procLOG]: procmgr.c(2444) 33 %% Administrative Command:app-start ping-0
<13> Jan 1 00:02:22 0.0.0.0-0 General[procLOG]: procmgr.c(2444) 31 %% Administrative Command:app-start ospf-00 0
<13> Jan 1 00:02:21 0.0.0.0-0 General[procLOG]: procmgr.c(2444) 28 %% Administrative Command:app-start vr-agent-0
<13> Jan 1 00:02:21 0.0.0.0-1 BSP[intDisTask]: cpu_boxs.c(2086) 20 %% FAN Module interrupt received on the unit 0
<10> Jan 1 00:02:21 0.0.0.0-1 General[intDisTask]: cpu_boxs.c(2077) 19 %% Event(0x5c000002)
<13> Jan 1 00:02:21 0.0.0.0-1 BSP[intDisTask]: cpu_boxs.c(2074) 18 %% Power Module interrupt received on the unit 0
<13> Jan 1 00:02:21 0.0.0.0-1 BSP[intDisTask]: cpu_boxs.c(2067) 17 %% SFP Interrupt received on the unit 0
<9> Jan 1 00:02:20 0.0.0.0-1 SIM[Cnfgr_Thread ]: sim_util.c(3906) 16 %% Switch was reset due to operator intervention.
<13> Jan 1 00:02:20 0.0.0.0-1 OSAPI[fp_main_task]: osapi_netlink.c(489) 15 %% Unable add the entry to /etc/iproute2/rt_protos.
<10> Jan 1 00:02:20 0.0.0.0-1 General[fp_main_task]: bootos.c(188) 14 %% Event(0xaaaaaaaa)
<13> Jan 1 00:02:20 0.0.0.0-1 BSP[fp_main_task]: bootos.c(172) 13 %% BSP initialization complete, starting switch firmware.
<12> Jan 1 00:02:11 0.0.0.0-1 DRIVER[fp_main_task]: phy8481.c(1177) 9 %% PHY8481 reset failed: u=0 p=40
<12> Jan 1 00:02:09 0.0.0.0-1 DRIVER[fp_main_task]: phy8481.c(1177) 8 %% PHY8481 reset failed: u=0 p=39
<12> Jan 1 00:01:54 0.0.0.0-1 DRIVER[fp_main_task]: phy8481.c(906) 7 %% PHY8481 reset failed: u=0 p=40
<12> Jan 1 00:01:52 0.0.0.0-1 DRIVER[fp_main_task]: phy8481.c(6794) 6 %% PHY8481 firmware programming timed out !.: u=0 p=40
<12> Jan 1 00:01:33 0.0.0.0-1 DRIVER[fp_main_task]: phy8481.c(906) 5 %% PHY8481 reset failed: u=0 p=39
<12> Jan 1 00:01:31 0.0.0.0-1 DRIVER[fp_main_task]: phy8481.c(6794) 4 %% PHY8481 firmware programming timed out !.: u=0 p=39
<13> Jan 1 00:01:06 0.0.0.0-1 General[fp_main_task]: sdm_template_mgr.c(488) 3 %% Booting with default SDM template Data Center - IPv4 and IPv6.
<13> Jan 1 00:01:05 0.0.0.0-0 General[fp_main_task]: unitmgr.c(6584) 1 %% Reboot 1 (0x1)Any idea what PHY8481 is?
Hi
OK, looks like the firmware update tries to update some sub-components and it encounters a timeout. I don't have an exact idea what PHY8481 means, but PHY in networking oftne stands for PHYsical layer and 8481 could be related to the BCM8481, a 10GBASE-T transceiver from Broadcom, but that's something only Netgear can confirm or deny.
I've had past experiences with PoE daughterboards on M4100's not picking up the its own firmware update after a reboot, but usually after a second reboot. It looks like the newer firmware wants to update this subcomponent and times out. If my guess is right, having issues with some or all ports after the update with these message, seems plausible.
If it doesn't work after a reboot, I'd sincerely suggest contacting Netgear Support and inquire the case there. Maybe it's fixable, maybe there is something off with your switch.
That's where your lifetime warranty on the M4300 becomes valuable, and from past experiences mine were quite good. :-)
Hope that helps!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
