If you’re reading this, chances are you’re either a network engineer, IT manager, or someone tasked with keeping their PoE-powered devices running smoothly—probably with the POE-2036P, our 24-port gigabit PoE+ switch that’s become a go-to for small businesses, retail chains, and school campuses alike. Over the past five years as a supplier, I’ve fielded hundreds of questions about configuring this switch, and one that comes up more than any other is flow control. Folks see lag in their IP cameras, dropped packets on their wireless access points, or strange latency spikes during peak hours, and they immediately wonder: can flow control fix this? And how do I set it up right? POE-2036P
I get it—network settings can feel like navigating a maze when you’re deep in a 9-to-5, juggling 10 different devices. Flow control isn’t the most glamorous part of switch configuration, but done right, it prevents data congestion that crashes your whole network mid-shift. Let’s break this down step by step, from what flow control actually is, to how to configure it on the POE-2036P, and the common mistakes I see users make every single time. No jargon overload, just real-world advice I’ve learned from working directly with clients over the years.
First, let’s get the basics straight: What is flow control, and why does it matter for the POE-2036P? Imagine your network is a highway, and data packets are cars. During peak times—like when all 24 IP cameras are uploading footage to a central NVR, or every employee is on a video call—too many “cars” try to cram into the same “lane” (a single port or switch internal buffer). Without flow control, those packets will just pile up, get dropped, or cause bottlenecks. Flow control is the stop-and-go system that tells a sending device: “Slow down, my buffer is full right now—wait a second before sending more.”
On the POE-2036P, we support two main types of flow control: IEEE 802.3x (which is the standard, per-port flow control for full-duplex links) and Priority-based Flow Control (PFC), which is more advanced for handling different types of traffic (like separating video data from email data so one doesn’t swamp the other). A lot of new users only mess with 802.3x, but if you’re running high-bandwidth devices, PFC is actually the game-changer. I’ve seen this first-hand: a retail client with 16 POE cameras on their POE-2036P thought their switch was faulty because footage was lagging during store hours. After enabling PFC for the video VLAN, their latency dropped by 70% within an hour. That’s the kind of win that makes flow control worth getting right.
Now, let’s talk about prerequisites before you even touch the configuration screen. I can’t tell you how many times someone calls me up saying “my flow control isn’t working” and turns out they forgot a basic step: flow control has to be enabled on both the switch port and the connected device. If your POE-2036P port is set to send pause frames but your IP camera isn’t configured to receive them, those pause frames just disappear into the ether, and you still get dropped packets. So first, confirm that all connected devices (wireless APs, cameras, VoIP phones, whatever) have their flow control enabled too. Most modern devices do this by default, but older ones or cheap no-name models sometimes don’t—double-check their user manuals if you’re seeing inconsistent results.
Next, make sure your switch is running the latest firmware. This is non-negotiable. We push firmware updates for the POE-2036P every quarter, mostly to fix flow control glitches that pop up when we add new device compatibility. Last year, we had a batch of switches that had a bug where 802.3x pause frames weren’t being sent properly on ports 17 through 24—we fixed that in firmware version V2.1.4, so if you’re running anything older than that, your flow control settings won’t work as intended. You can check firmware status via the switch web interface under “System Settings” > “Firmware Update,” and if you need help updating, our support team walks you through it in 10 minutes flat.
Okay, now the fun part: configuring flow control on the POE-2036P. Let’s start with the most common, per-port 802.3x flow control, since that’s what most users need first. I’ll walk you through this using the web interface, which is the easiest way, rather than the command line—no obscure CLI codes, just point-and-click.
First, log into your POE-2036P’s web interface. You’ll find the IP address either on the switch label, or by scanning for it with a free tool like Advanced IP Scanner if you forgot it. Once logged in, navigate to the “Port Configuration” tab—this is where all your individual port settings live. You’ll see a list of 24 ports, labeled 1 through 24, along with their current speed, PoE status, and flow control setting.
For each port you want to enable flow control on, click the “Edit” button next to that port. A pop-up window will open with settings for speed, duplex, and flow control. Under “Flow Control,” you’ll have three options: Disabled, Rx Only, Tx Only, and Full (which is both Rx and Tx). Let me break what each of these does, because choosing the wrong one is a super common mistake. Disabled is obvious—no flow control. Rx Only means the switch will listen for pause frames from the connected device, but won’t send its own. Tx Only means the switch will send pause frames to the device if its buffer is full, but won’t respond if the device sends a pause frame to it. Full is the right setting for almost all scenarios, because it’s bidirectional: both the switch and the connected device can send and receive pause frames. The only time you don’t want Full is if you have an older device that only supports unidirectional flow control—check its manual, and if it only uses Tx, set your switch port to Rx Only, and vice versa.
Once you select Full (or the right setting for your device), click “Save.” Now, repeat this for every port that has high-bandwidth devices connected—like your camera ports, core network ports, and wireless AP ports. You don’t need to enable flow control on ports connected to low-bandwidth devices like desktop PCs, because their data load is never high enough to cause congestion. Pro tip: I usually group my camera ports into a VLAN called “Video” and my AP ports into “Wireless,” so I can quickly enable flow control only on those ports instead of scrolling through all 24 every time I need to adjust something.
Now, if you’re running a larger network with lots of different traffic types, like a school with video conferencing, IP cameras, and VoIP phones, 802.3x might not be enough. That’s where Priority-based Flow Control (PFC) comes in, and I recommend enabling this on your POE-2036P too—it’s even simpler than it sounds. PFC works by classifying traffic into different priority queues, so if one type of traffic (say, a big file download from a teacher’s laptop) starts clogging the switch, it only slows down that specific queue, not the entire network. For schools, this means video calls won’t drop because someone is downloading a movie, and for retail, cash register transactions won’t lag because cameras are uploading footage.
To enable PFC, go to the “QoS” (Quality of Service) tab on your POE-2036P’s web interface, then select “Priority-based Flow Control.” First, you’ll need to map your traffic types to 802.1p priority codes. Let’s keep this simple: most users assign priority 5 to video (cameras, video calls), priority 4 to VoIP, priority 3 to critical network traffic, and priority 0 to regular data (email, downloads). Once you have your mapping set, check the box next to “Enable PFC” and select the priorities you want to apply PFC to. I almost always enable PFC for priorities 4 and 5, since those are the high-bandwidth, time-sensitive ones. Then, just like with 802.3x, you need to enable PFC on each connected device’s port too—most modern APs and cameras support PFC now, but again, double-check if you’re using older hardware.
Now, let’s talk about common mistakes I see users make when configuring flow control on the POE-2036P, because fixing these is half the battle. First mistake: Enabling flow control on all 24 ports. I’ve had a client call me panicking because their network got even laggier after enabling flow control everywhere—turns out they turned it on for their 48-port uplink to their core router, which had the opposite effect. Flow control is for ports with high-speed, short-distance links; uplinks to core routers shouldn’t have flow control enabled, because it can cause bottlenecks across your entire network backbone. Stick to enabling it only on ports connecting your end devices (cameras, APs, VoIP phones).
Second mistake: Forgetting to restart or reload the switch after changing flow control settings. A lot of users click “Save” and think they’re done, but the POE-2036P sometimes requires a quick reload to apply flow control changes. I always tell users to save their settings, then go to “System Tools” > “Reboot Switch” and select “Reboot Now” to make sure all settings take effect. No more guessing if your change is active.
Third mistake: Ignoring buffer size settings. The POE-2036P has built-in switch buffers, and if you set flow control but your buffer is too small, you’ll still get dropped packets. You can adjust buffer size in the “Port Configuration” tab too—for ports that handle video or VoIP, I recommend setting the buffer to 2MB per port, instead of the default 1MB. I had a warehouse client a year ago with 24 cameras; their buffer was set to default 1MB per port, so even with flow control, during shift changes, footage would drop. Increasing the buffer fixed that instantly.
Another thing to note: Flow control isn’t a fix for every network problem. If you’re seeing latency, first check your cable length—if you’re using a 100-foot Cat5e cable, that’s too long for gigabit PoE, and you’ll get signal loss that looks like congestion. Or if you have too many devices on your network that aren’t PoE-powered, you might need to upgrade to a higher-capacity switch. Flow control is a band-aid for congestion from data overload, not a cure-all for bad cabling or underpowered switches.
Let me walk you through a real example to make this concrete. Last quarter, I worked with a small café chain in downtown Austin that had 5 locations, each with a POE-2036P switch. They were getting complaints that during lunch rush, their point-of-sale (POS) systems would freeze for 10-15 seconds, and IP cameras would miss footage. Their IT guy tried everything: updating software, rebooting routers, replacing cables, but nothing worked. When I logged into their POE-2036P, I saw they had flow control disabled entirely, and all their camera ports were set to the default 1MB buffer. I enabled full 802.3x flow control on the 8 ports used for cameras and POS, increased their buffer to 2MB each, and enabled PFC for video and VoIP traffic. Within a week, they reported zero freezes at lunch, and their camera footage was consistent. That’s exactly what flow control is supposed to do.
If you’re still confused about configuring flow control, don’t overcomplicate it. Start with the basics: Enable 802.3x Full on only your high-bandwidth device ports, make sure both the switch and connected device have flow control on, update your firmware, and adjust buffer sizes if you’re still seeing congestion. If you need more hands-on help, our team is here to walk you through it—we’ve supported thousands of POE-2036P users, and we don’t do robotic support scripts, just real advice from people who sell, configure, and troubleshoot these switches every day.
At the end of the day, the POE-2036P is a versatile switch that’s built to handle small to medium networks, and flow control is one of the most powerful tools to get the most out of it. Whether you’re running a retail store, school, or office, taking 15 minutes to set up flow control correctly will save you hours of troubleshooting down the line, and keep your critical devices running smoothly.
If you’re looking to upgrade your network with POE-2036P switches, or need help configuring flow control for your existing setup, reach out to our team to discuss your requirements and get a tailored solution. We’re here to support your network, not just sell you hardware.
25W References
- IEEE 802.3-2018, Standard for Ethernet, Clause 31: Media Access Control (MAC) Control Layer.
- POE-2036P User Manual, Revision 2.1, 2023.
- Cisco Small Business Switch Configuration Guide: Priority-Based Flow Control Implementation, 2022.
- Network Congestion Management Best Practices for Gigabit PoE Switches, TechRepublic, 2024.
Shenzhen Jingangxia Technology Co., Ltd.
We are one of the most reliable poe-2036p manufacturers and suppliers in China, specialized in providing high quality customized service for global clients. Please rest assured to wholesale discount poe-2036p for sale here from our factory.
Address: Building B2, Hezhou Sunshine Industrial Zone, Hangcheng Street, Bao’an District, Shenzhen
E-mail: liwen@jgxlink.com
WebSite: https://www.upsdcpower.com/
