NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
M4300 could not get interface vlan 300
M4300-24x24f
ALSO none of M4300 switches are not on the model list on this page.
Once a minute I get this information:
Nov 12 10:44:42 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3354 %% Link Down: vlan 300
Nov 12 10:44:42 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3355 %% Link Up: vlan 300
Nov 12 10:44:42 cam2sw5-1 OSAPI[ipMapProcessing]: osapi_net.c(1381) 3356 %% osapiArpFlush: could not get interface vlan 300! errno = 19
Nov 12 10:44:42 cam2sw5-1 IP[ipMapProcessing]: l3_intfload.c(481) 3357 %% Looking up RTO for existing route for ip = 10.0.0.2 mask = 255.255.255.248
Nov 12 10:44:44 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3358 %% Link Down: vlan 300
Nov 12 10:44:44 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3359 %% Link Up: vlan 300
Nov 12 10:44:44 cam2sw5-1 OSAPI[ipMapProcessing]: osapi_net.c(1381) 3360 %% osapiArpFlush: could not get interface vlan 300! errno = 19
Nov 12 10:44:44 cam2sw5-1 IP[ipMapProcessing]: l3_intfload.c(481) 3361 %% Looking up RTO for existing route for ip = 10.0.0.2 mask = 255.255.255.248
Nov 12 10:44:48 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3362 %% Link Down: vlan 300
Nov 12 10:44:48 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3363 %% Link Up: vlan 300
Nov 12 10:44:48 cam2sw5-1 OSAPI[ipMapProcessing]: osapi_net.c(1381) 3364 %% osapiArpFlush: could not get interface vlan 300! errno = 19
Nov 12 10:44:48 cam2sw5-1 IP[ipMapProcessing]: l3_intfload.c(481) 3365 %% Looking up RTO for existing route for ip = 10.0.0.2 mask = 255.255.255.248
Nov 12 10:44:50 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3366 %% Link Down: vlan 300
Nov 12 10:44:50 cam2sw5-1 OSAPI[ipMapProcessing]: osapi_net.c(1381) 3367 %% osapiArpFlush: could not get interface vlan 300! errno = 19
Nov 12 10:44:50 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3368 %% Link Up: vlan 300
Nov 12 10:44:50 cam2sw5-1 IP[ipMapProcessing]: l3_intfload.c(481) 3369 %% Looking up RTO for existing route for ip = 10.0.0.2 mask = 255.255.255.248
Nov 12 10:44:52 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3370 %% Link Down: vlan 300
Nov 12 10:44:52 cam2sw5-1 TRAPMGR[trapTask]: traputil.c(753) 3371 %% Link Up: vlan 300
Nov 12 10:44:52 cam2sw5-1 OSAPI[ipMapProcessing]: osapi_net.c(1381) 3372 %% osapiArpFlush: could not get interface vlan 300! errno = 19
Nov 12 10:44:52 cam2sw5-1 IP[ipMapProcessing]: l3_intfload.c(481) 3373 %% Looking up RTO for existing route for ip = 10.0.0.2 mask = 255.255.255.248
(cam2sw5) >show ip interface brief
Interface State IP Address IP Mask TYPE Method
----------- ----- --------------- --------------- --------------- ---------------
vlan 1 Down 0.0.0.0 0.0.0.0 Primary None
vlan 300 Up 10.0.0.2 255.255.255.248 Primary DHCP
The ip route keeps being reset.
Default Gateway(s): 10.0.0.1
S 0.0.0.0/0 [254/1] via 10.0.0.1, 00h:00m:00s, vlan 300
C 10.0.0.0/29 [0/0] directly connected, vlan 300
Also it for some reason makes the switch gets stuck or crash agfter some time.
| 33 | EVENT> | bootos.c | 188 | 0 | AAAAAAAA | 0 0 1 18 |
| 34 | ERROR> | broad_hpc_stacking.c | 1764 | 0 | 00000001 | 0 0 1 3 |
| 35 | EVENT> | Crashed! | 0 | 0 | 00000000 | 0 0 1 13 |
| 36 | EVENT> | unitmgr.c | 6583 | 0 | 00000000 | 0 0 2 31 |
| 37 | EVENT> | bootos.c | 188 | 0 | AAAAAAAA |
0 0 0 43
|
So I think I solved it.
The port needs to have the vlan has both on PVID and in VLAN member field.
Also I have noticed tat despite setting timeout to 160 minutes, it only takes like 15 minutes for the session to time out.
3 Replies
All M4300 models are missing in the community product tags, too ChristineT...
So I think I solved it.
The port needs to have the vlan has both on PVID and in VLAN member field.
Also I have noticed tat despite setting timeout to 160 minutes, it only takes like 15 minutes for the session to time out.
smwojciech wrote:
The port needs to have the vlan has both on PVID and in VLAN member field.
Yes, of course - still, this should not crash the switch.
smwojciech wrote:
Also I have noticed tat despite setting timeout to 160 minutes, it only takes like 15 minutes for the session to time out.
Yes, happens on several switch models recently.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
