Flapping Interfaces on ICX 7150

[Darkmoon_430]

 

Hi community,

I’m reaching out to see if anyone has experienced a similar issue.

We’re seeing random interface flapping on multiple ICX 7150 switches, all running the same firmware version. The affected ports are connected to PoE IP cameras (same model and vendor across all switches and ports).

Environment:

Firmware version: SPR08095k

• Connected devices: IP cameras (same model across all ports)

• Interface config: stp-bpdu-guard
  
  Observations:

• PoE is stable (no faults, normal power draw)

• TDR results also look normal

• STP logs show flapping behavior, transitioning between FORWARDING → BLOCKING → DISABLED (PortDown), then back to FORWARDING

• The issue occurs intermittently and affects different ports

• Other ports with the same camera and cabling work fine
  
  Workarounds Tried:

• Shutting/no shutting the port temporarily resolves the issue

• Moving the camera to another port also works, but the issue may return later
  
  Has anyone else experienced similar interface flapping issues on ICX 7150 switches with IP cameras connected?
  
  Any feedback or suggestions would be greatly appreciated.
  Thanks in advance for your time and support!

[Mayank]

Hi Darkmoon_430,

Thank you for posting your query!

I understand that on multiple Ruckus ICX 7150 switches (firmware SPR08095k), interfaces connected to PoE IP cameras are intermittently flapping.

I have one suggestion for you to test:

Could you please disable BPDU guard on one of the affected camera ports for testing purposes? I suspect that if the camera (or any device in between, such as a surge protector or unmanaged mini-switch) ever sends a BPDU, the switch will immediately err-disable or flap the port, which could be triggering this issue.

If these ports are dedicated only to cameras, you can safely disable stp-bpdu-guard. Instead, to minimize the impact of false BPDU detections, I recommend enabling the following:

errdisable recovery cause all
errdisable recovery interval 20

This will allow the port to automatically recover within 20 seconds, preventing extended outages.

Let me know how it goes after applying this change on one port for testing.

Note: Please feel free to mark the post as ACCEPTED SOLUTIONS if its addressed your query.

Thanks & Regards,
Mayank

[Darkmoon_430]

Hello Mayank

Thank you for your response.

I’ve followed the recommended steps, but unfortunately, they didn’t resolve the issue.

As a next step, I’ll either migrate the port to another switch (from a different vendor) or remove the port from the vlan. I’ll keep you posted on the results.

Kind regards,

Darkmoon430

[Mayank]

Hi Darkmoon_430,

Thank you for the update,

Please log a ticket with the below link so that we will help you to further.

https://support.ruckuswireless.com/contact-us

Please feel free to leave us a message if any concerns

Best regards,
Mayank

[jonathan_golles]

A few things:

• Run: show inline power and see if the switch power is overloaded. Check how much power the ports are consuming. For instance, one example of a functioning camera reads "1/1/27 On On 2100 15400 802.3af Class 3"
• Run show int e 1/1/10 or whatever for each port each camera connected to.  Look for port errors which could indicate layer 1 or cable issues. A clean bill of health will look like "0 input errors, 0 CRC, 0 frame, 0 ignored
  0 runts, 0 giants" If you see errors, replace the patch cables on the switch and camera side.
• Run show int brief and check check to see what the port speed is for these cameras, 100 M may be typical. 10 M could be red flag (or a veery far run).
• Also you could try putting a power injector in between to power the camera and test to see if it's a power issue or a switch port issue.