Flapping switch port on Netbiter WS200


#1

Hello,
I have Netbiter WS200,

  • Kernel version 2.6.12-uc0-NB200-13
  • Application version 3.30.4 (build 396)
  • loggraph_security 1.00.0 Patch to replace Java applet log graph with HTML plus additional security fixes.
  • Security_patch_2018_12_04 1.0 HMSSAR-2018-12-04-001 + HMSSAR-2017-05-24-001.
    Port f21 on Cisco SF300-48PP, where is Netbitter connected is flapping, every 10-11min. Down and Up port at the same intervals.
    Try other port, other switch, other cable, other IP addres, problem stays.
    Follows is few logs:
    07-Aug-2019 15:16:33 :%STP-W-PORTSTATUS: fa21: STP status Forwarding
    07-Aug-2019 15:16:28 :%LINK-I-Up: fa21
    07-Aug-2019 15:16:24 :%LINK-W-Down: fa21
    07-Aug-2019 15:05:47 :%STP-W-PORTSTATUS: fa21: STP status Forwarding
    07-Aug-2019 15:05:43 :%LINK-I-Up: fa21
    07-Aug-2019 15:05:38 :%LINK-W-Down: fa21
    07-Aug-2019 14:55:01 :%STP-W-PORTSTATUS: fa21: STP status Forwarding
    07-Aug-2019 14:54:56 :%LINK-I-Up: fa21
    07-Aug-2019 14:54:52 :%LINK-W-Down: fa21
    07-Aug-2019 14:44:15 :%STP-W-PORTSTATUS: fa21: STP status Forwarding
    07-Aug-2019 14:44:10 :%LINK-I-Up: fa21
    07-Aug-2019 14:44:06 :%LINK-W-Down: fa21

Is this correct state!
On the other side I have Netbiter WS100 too and everything is normal.
How can I solve problem?

Goran


#2

Hello @gjovano,

I have not heard of the WS200’s having issues causing flapping. Is this a long standing install that is has just started doing this or is it a new install?

Judging by the logs provided it looks like it is just going down then back up in about 4 seconds. Could the device be getting power cycled at these times?

Deryck


#5

Hello,

this is long time standing installation. His duty is to communicate with diesel agregat, via modbus and TCP IP/RTU Modbus protocol. It works fine about 3 years. But, i supose, after update firmware to latest version few month ago, with security patch too, trouble start.

First, he was powered from battery of diesel agregat CAT (DEA) 24 VDC, same power like control unit of DEA. when flapping starts I was suspicious to DC power too. I change position of Netbiter, a put him in our Data Center, give him stabile power supply, +12VDC. Change mgt switch, cable IP,adress… complete new environment … everything, but problem persist. (I send you just a part of log) there is no any alarm or suspicious event on Netbiter.

It is symptomatic that is repeates at the same time interval, like you see in log. Like his WDT do something and flap communication port.

Can you send me few previous version of firmware, to downgrade software… to see will the problem disappear.

Goran


#6

Hi @gjovano,

I will need to look into this option this device and see what we have available for this device. Is this plugged directly into the Cisco switch? Does this happen with other switches?

Deryck


#7

Hello Deryck,
Netbiter is plugged directly in switch, port 21. Cable is about 2m long, original CAT5e. It was happening on every switch where Netbiter was plugged.
We don`t have problem with other plugged device.

Goran


#8

Hi @gjovano,

I am still looking into what we have available for firmware for the WS200.

My colleague pointed out that he has seen many issues with Cisco switches with flapping problems. It might be worth looking into if there is a solution available for the Cisco switch that you might be able to apply to resolve this.

Deryck


#9

Hi Deryck
Now, I move Netbiter connection from Cisco switch to DCN DCS3950. Send you news.

Goran


#10

OK, thanks for the update let me know if this resolves the issue.

Deryck


#11

Hello Deryck,
There is no change, port no. 10 on DCN still flapping. Below are few log:
bg-tp-r2-mgt-2#sh logging buffered level ?
critical Critical level(2)
warnings Warnings level(4)

bg-tp-r2-mgt-2#sh logging buffered level warnings
Current messages in SDRAM:2533

2533 %Aug 13 09:12:16 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to FORWARDING!
2532 %Aug 13 09:12:00 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to LEARNING!
2531 %Aug 13 09:11:44 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to DISCARDING!
2530 %Aug 13 09:11:44 2019 MODULE_PORT[tphyDaemon]:%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/10, changed state to UP
2529 %Aug 13 09:11:39 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to DISCARDING!
2528 %Aug 13 09:11:39 2019 MODULE_PORT[tphyDaemon]:%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/10, changed state to DOWN
2527 %Aug 13 09:01:30 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to FORWARDING!
2526 %Aug 13 09:01:14 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to LEARNING!
2525 %Aug 13 09:00:58 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to DISCARDING!
2524 %Aug 13 09:00:58 2019 MODULE_PORT[tphyDaemon]:%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/10, changed state to UP
2523 %Aug 13 09:00:54 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to DISCARDING!
2522 %Aug 13 09:00:54 2019 MODULE_PORT[tphyDaemon]:%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/10, changed state to DOWN
2521 %Aug 13 08:50:44 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to FORWARDING!
2520 %Aug 13 08:50:28 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to LEARNING!
2519 %Aug 13 08:50:12 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to DISCARDING!
2518 %Aug 13 08:50:12 2019 MODULE_PORT[tphyDaemon]:%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/10, changed state to UP
2517 %Aug 13 08:50:07 2019 MODULE_L2_MSTP[tMstp]:MSTP set port = 10, mst = 0 to DISCARDING!
2516 %Aug 13 08:50:07 2019 MODULE_PORT[tphyDaemon]:%LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet1/10, changed state to DOWN

Goran


#12

Hi Deryck,

  I sent you post and log from new switch where I connect Netbiter, few days ago. Did you see log. Do you have some news?


#13

#14

#15

#16

Hello @gjovano,

The logs seem to confirm that the port is going down and then re-establishing a connection. I’m not sure what the cause would be. I have not been able to find any cases where the WS200 causes issues like this and I do not believe the firmware update would have caused this issue.

Could the hardware have been damaged at some point? Do you have a second WS200 you could test with?

Attaches is the only firmware i was able to track down so far for the device. This is appears to be the same one available from netbiter.net
netbiter-ws200-full-package-software-upgrade.zip (3.1 MB)

Deryck