Configuring the PoE Switch Behind Your Cameras in Waller, TX

What an unconfigured switch leaves undone

An unmanaged PoE switch does two jobs: it powers whatever is plugged in, up to its budget, and it passes traffic. For three or four cameras beside a recorder, that can be enough. Once a system grows, shares a network with computers, or has to be looked after from somewhere else, the settings a managed switch adds start to count.

Where the switch belongs in a new Waller home or a 290 storefront

Waller is changing quickly. New subdivisions off US 290 and FM 2920 sit alongside older homes near downtown, horse properties and acreage out in the county, and a growing number of warehouses, contractor yards and small shops along the highway. Each puts the switch somewhere different, and the location shapes the configuration.

• New production homes. Builders usually terminate low-voltage wiring in a structured-media can in a closet or the garage. A closed metal can in a Texas garage in summer is a poor home for a switch already warm from powering cameras, so we prefer a small wall rack or shelf in conditioned space.
• Homes still under construction. This is the moment to wire each camera location as a home run to the switch spot, never daisy-chained, and to give that spot power, ventilation and room for a UPS.
• Storefronts and flex space. The switch often shares a closet with the landlord’s internet equipment or the office network, which makes the separation steps below mandatory.
• Acreage. A barn or shop beyond about 100 meters of cable from the house needs its own switch, linked back by fiber or a wireless bridge.

Steps 1 and 2: a network of their own, and addresses that never move

Step 1: separate the cameras. On a managed switch we create a camera VLAN and make each camera port an untagged access port on it; the uplink to the recorder, router or firewall carries that VLAN tagged. Computers, phones and guests stay on their own VLAN and cannot browse to a camera. If the recorder has built-in PoE ports, those ports already form a private camera network behind it, and the switch should extend that network rather than create a second one. Mixing the two is a common cause of cameras that appear and disappear.

Step 2: fix the addresses. Each camera gets either a DHCP reservation or a static address outside the router’s automatic pool, and every one is written down. The failure we see most often in Waller homes comes when the internet provider swaps the router: many provider routers default to a different address range, so cameras with static addresses in the old range go unreachable overnight though nothing on the camera side changed. A camera VLAN, or the recorder’s private network, insulates the cameras from that change.

Step 3: set the clock, because a clip with the wrong time is weak evidence

Footage is only persuasive if its timestamp is right. We point the recorder at a reliable time server, set Central time with daylight saving, and have every camera take its time from the recorder so all channels agree. Cameras left on factory clocks drift by minutes over months, and when an insurer or a deputy asks for the clip from 11:42 p.m., two cameras showing the same pickup at different times invites questions.

When the camera VLAN has no internet access by design, the recorder or the firewall serves time internally, so nothing on that VLAN needs to reach outside.

Step 4: add up the video before it reaches the uplink

Each camera sends at least two streams: a full-resolution main stream to the recorder and a lighter substream for grid views and phones. As a working range, a 4-megapixel camera on H.265 often runs a few megabits per second and a 4K camera several times that, depending on frame rate, motion and settings.

Sixteen 4K cameras near eight megabits each come to about 128 Mbps before substreams. A gigabit uplink handles that easily; the older 100 Mbps PoE switches still sold in bargain kits do not, and drop frames as the count climbs. In a warehouse or long commercial building with several switches, we check every uplink between them and the recorder’s own incoming bandwidth rating, since a recorder rated below the total loses video however good the switch is.

Rain, blowing grass and insects in the infrared beam push night bitrates up, so we cap bitrates to keep a stormy night inside the plan.

Step 5: decide which cameras keep power when watts run short

A managed PoE switch can mark each port critical, high or low. If total draw ever exceeds the budget, because of a failing power supply, a UPS at reduced output or a device added later, low-priority ports are cut first. For a Waller business we usually mark entrance, register and loading-door cameras critical and a parking-lot overview low. At home, the front door and driveway stay up while a backyard camera sheds.

Some switches can also switch ports off on a schedule. That suits Wi-Fi access points or signage; we keep every camera port out of it.

Step 6: close the doors most installs leave open

• Replace every default password on the switch, recorder and cameras, with admin credentials held by the owner.
• Turn off UPnP on the router and recorder so nothing opens ports to the internet on its own.
• Use the manufacturer’s app connection or a VPN for remote viewing, never port forwarding.
• Update firmware, and disable management services the site does not use, such as Telnet or plain HTTP.
• Limit switch management to an admin VLAN or specific addresses.
• Disable spare ports or park them on an isolated VLAN, so a laptop plugged into a spare jack in a lobby or shop cannot join the camera network.
• Enable loop protection and storm control, so a cable plugged into two ports of the same switch cannot take the office down.

EVOTECH’s configuration call in Waller

1. Collect what exists: internet provider and router model, current address ranges, camera and recorder models, and who needs access.
2. Draw a port and address plan and agree it with you before anything changes.
3. Back up the current switch and recorder settings so every change can be reversed.
4. Apply VLANs, addressing, time, stream settings, PoE priority and security, then save the configuration.
5. Test every camera on the recorder, on a phone over cellular data, and after a deliberate switch reboot.
6. Label the ports and hand over the plan with credentials, so a future technician or your IT person can pick it up.

For homes under construction, we coordinate the rough-in visit with your builder’s schedule and return to configure after move-in.

What changes the scope and the price

• How many cameras and ports are involved, and whether the current switch is managed or needs replacing.
• Whether cameras share a network with business computers, a point-of-sale system or a firewall someone else manages.
• After-hours work so a business is not interrupted.
• New-construction coordination that takes more than one visit.
• Remote access and documentation requirements.

Once we have walked the site, you receive an itemized quote, so each part of the configuration is visible before you approve it.

Configuration misses that bring us back

• Static addresses inside the router’s pool. Sooner or later a phone gets a camera’s address and both drop.
• Cameras on factory clocks. Every channel shows a different time on the night it matters.
• A 100 Mbps uplink under 4K cameras. Frames drop as soon as the count climbs.
• Port forwarding left open by the last installer. The recorder is scanned constantly from the internet.
• Changes made but not saved. The next power blip restores the old configuration.

Related services

Frequently asked questions