× NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Orbi WiFi 7 RBE973
Reply

Randomly Link UP & Link Down on ports are noticed on random ports on M4300-52G-PoE+ ProSAFE 48-port

pavan4cambium
Follower

Randomly Link UP & Link Down on ports are noticed on random ports on M4300-52G-PoE+ ProSAFE 48-port

Hi Team,

 

We use switch (M4300-52G-PoE+ ProSAFE 48-port 1G PoE+ and 2-port 10GBASE-T and 2-port 10G SFP+) as Layer 2 switch configured with Static IP. 

 

Wifi Access Points are connected to this Switch for our internal lab testing. Certain times, randomly we notice that there is network loss for few seconds. While i check the logs on the switch i see Link up and down traps are generated on the ports.

 

Switch is running with Factory defaults with Spanning Tree Admin Mode disabled. Did several reboots and factory reset on the switch but nothing solved the problem.

Also ensure that, there is no loop with in the switch. Need expertise help in order to resolve this. Some ideas or leads to resolve this would be greatly appreciated as this is causing the network unstable and unreliable.

 

below is the logs and switch firmware details for reference. Experts, please feel free to let me know in case if you need more information from my end. 

 

Firmware Version12.0.4.8
Boot VersionB1.0.0.11
CPLD Version0x1
Internal AC-1Operational
Internal AC-2Not present
EPS/RPSNot present
MAX PoEON

 

Logs

 

<13> Oct 9 20:21:29 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1888 %% Link Up: 1/0/46

<13> Oct 9 20:21:26 192.168.0.239-1 TRAPMGR[emWeb]: traputil.c(795) 1885 %% HTTP session : Login to the switch is not successful, User ID: admin

<13> Oct 9 20:21:20 192.168.0.239-1 TRAPMGR[emWeb]: traputil.c(795) 1882 %% HTTP session : Login to the switch is not successful, User ID: admin

<12> Oct 9 20:21:19 192.168.0.239-1 ARP[ipMapForwarding]: ipmap_arp_api.c(1149) 1880 %% Received ARP Reply on interface vlan 1 with bad target IP address 255.255.255.255. Sender IP is 10.110.241.66,
 sender MAC is 0a:00:3e:bb:96:ae.

<13> Oct 9 20:21:09 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1879 %% Link Down: 1/0/46

<13> Oct 9 20:20:52 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1877 %% Link Up: 1/0/46

<13> Oct 9 20:20:49 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1875 %% Link Down: 1/0/46

<13> Oct 9 20:20:47 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1873 %% Link Up: 1/0/25

<13> Oct 9 20:20:44 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1871 %% Link Down: 1/0/25

<13> Oct 9 20:20:34 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1869 %% Link Up: 1/0/25

<13> Oct 9 20:20:31 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1867 %% Link Down: 1/0/25

<12> Oct 9 20:19:09 192.168.0.239-1 ARP[ipMapForwarding]: ipmap_arp_api.c(1149) 1865 %% Received ARP Reply on interface vlan 1 with bad target IP address 255.255.255.255. Sender IP is 10.110.241.66,
 sender MAC is 0a:00:3e:bb:96:ae.

<12> Oct 9 20:13:23 192.168.0.239-1 ARP[ipMapForwarding]: ipmap_arp_api.c(1149) 1864 %% Received ARP Reply on interface vlan 1 with bad target IP address 255.255.255.255. Sender IP is 10.110.241.66,
 sender MAC is 0a:00:3e:bb:96:ae.

<13> Oct 9 20:12:51 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1863 %% Link Up: 1/0/25

<13> Oct 9 20:12:48 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1861 %% Link Down: 1/0/25

<13> Oct 9 20:12:40 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1859 %% Link Up: 1/0/41

<13> Oct 9 20:12:38 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1857 %% Link Up: 1/0/25

<13> Oct 9 20:12:38 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1855 %% Link Down: 1/0/41

<13> Oct 9 20:12:35 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1853 %% Link Down: 1/0/25

<13> Oct 9 20:12:28 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1851 %% Link Up: 1/0/27

<13> Oct 9 20:12:26 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1849 %% Link Down: 1/0/27

<13> Oct 9 20:12:25 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1847 %% Link Up: 1/0/41

<13> Oct 9 20:12:23 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1845 %% Link Down: 1/0/41

<13> Oct 9 20:12:12 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1843 %% Link Up: 1/0/41

<13> Oct 9 20:12:08 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1841 %% Link Down: 1/0/41

<13> Oct 9 20:12:08 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1839 %% Link Up: 1/0/27

<13> Oct 9 20:12:05 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1837 %% Link Down: 1/0/27

<13> Oct 9 20:12:01 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1835 %% Link Up: 1/0/27

<13> Oct 9 20:11:56 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1833 %% Link Down: 1/0/27

<13> Oct 9 20:11:55 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1831 %% Link Up: 1/0/41

<13> Oct 9 20:11:51 192.168.0.239-1 TRAPMGR[PoE Req]: traputil.c(795) 1829 %% PoE: 1/0/41 power up

<13> Oct 9 20:11:30 192.168.0.239-1 TRAPMGR[PoE Req]: traputil.c(795) 1828 %% PoE: 1/0/41 power down

<13> Oct 9 20:11:27 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1827 %% Link Down: 1/0/41

<13> Oct 9 20:11:01 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1825 %% Link Up: 1/0/30

<13> Oct 9 20:10:58 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1823 %% Link Down: 1/0/30

<13> Oct 9 20:10:44 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1821 %% Link Up: 1/0/30

<13> Oct 9 20:10:42 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1819 %% Link Down: 1/0/30

<13> Oct 9 20:10:32 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1817 %% Link Up: 1/0/30

<13> Oct 9 20:10:27 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1815 %% Link Down: 1/0/30

<13> Oct 9 20:10:15 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1813 %% Link Up: 1/0/30

<13> Oct 9 20:10:08 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1811 %% Link Down: 1/0/30

<13> Oct 9 20:07:24 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1809 %% Link Up: 1/0/9

<13> Oct 9 20:07:21 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1807 %% Link Down: 1/0/9

<13> Oct 9 20:07:03 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1801 %% Link Up: 1/0/9

<13> Oct 9 20:07:01 192.168.0.239-1 TRAPMGR[trapTask]: traputil.c(753) 1799 %% Link Down: 1/0/9
Model: GSM4352PA|M4300-52G-PoE+ - 48x1G PoE+ Stackable Managed Switch with 2x10GBASE-T and 2xSFP+ (550W PSU)
Message 1 of 2
schumaku
Guru

Re: Randomly Link UP & Link Down on ports are noticed on random ports on M4300-52G-PoE+ ProSAFE

Completely odd - @LaurentMa ?

 

Better file a support ticket on https://www.netgear.com/support/contact.aspx 

Message 2 of 2
Top Contributors
Discussion stats
  • 1 reply
  • 1593 views
  • 0 kudos
  • 2 in conversation
Announcements