Friday, November 27, 2020

Support on Dell N2048P Ports Flapping

Hi All

So i Have a stack of 4 Dell N2048P Switches that im having problems with the Ports flapping or going up and down speradically (at least in 5 minute intervals).

I needed to move these 4 switches to a new rack in a new building, and thought it would be a good time to re-configured them and have a better setup. So i zeroed the configuration and setup a new coonfiguration. Everything was working well to a few days ago when i noticed my devices going up and down.

On further rinvestigation i notice that SW3 ports are going up and down and in checking the logs i see only ports on switch 3 going up and down, i also notice that on Switch 2 that there is no data traffic to my end device but the switch is providing PoE so i shutdown all the porots on Switch 2 and bring them back up and that brings up all my devices and havent had that problem since, after i took up the poorts i deciced to reload the entire stack to make sure that it would work after a reboot and everything seemed fine.

Soo i check the switch logs and now i see that other ports on are going up and down and this is not just an issue on Switch 3 but on Switch 1, 2 and 4 now.

I have just upgraded the firmware to latest 6.6.0.24 and reloaded the switch but i get the same behaviour, i havent had the time yet to default the configuration and start afresh.

Below you can find an abstract part of the log file. I have a feeling that this may be hardware related (i havent as of yet been able to check if its always the same ports that go down) and before i go any further i am hoping someone can perhaps point me in the right directon before i restart the configuration.

<189> Nov 27 16:26:18 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 15124 %% NOTE Link Up: Gi3/0/2 <189> Nov 27 16:26:17 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 15114 %% NOTE Link on Gi4/0/23 is failed <189> Nov 27 16:26:17 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 15113 %% NOTE Link Down: Gi4/0/23 <189> Nov 27 16:26:17 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 15100 %% NOTE Link Up: Gi3/0/3 <189> Nov 27 16:26:16 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 15083 %% NOTE Link on Gi1/0/1 is failed <189> Nov 27 16:26:16 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 15082 %% NOTE Link Down: Gi1/0/1 <189> Nov 27 16:26:13 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 15044 %% NOTE Link Up: Gi1/0/9 <189> Nov 27 16:26:11 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 15006 %% NOTE Link on Gi1/0/9 is failed <189> Nov 27 16:26:11 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 15005 %% NOTE Link Down: Gi1/0/9 <189> Nov 27 16:26:09 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 14959 %% NOTE Link Up: Gi3/0/5 <189> Nov 27 16:26:09 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 14952 %% NOTE Link Up: Gi3/0/1 <189> Nov 27 16:26:08 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 14939 %% NOTE Link Up: Gi4/0/25 <189> Nov 27 16:26:06 172.25.172.15-1 TRAPMGR[trapTask]: traputil.c(721) 14901 %% NOTE Link on Gi4/0/25 is failed 


No comments:

Post a Comment