NAT
Network Address Translation
A router or firewall function that changes IP addressing as traffic crosses a boundary.
In everyday business: Many private office devices can share one public Internet address.
POE DESIGN AND INSTALLATION
PoE Installation, Budgeting and Troubleshooting Playbook
How to size PoE, map powered ports, check cabling and troubleshoot devices that do not start or reboot under load.
Book 2 | Chapter 12
Chapter opening
Chapter 12 moves from the course overview into poe installation, budgeting and troubleshooting. The aim is not to memorise product menus or commands. The reader should understand what problem the technology solves, how it fits into the wider cabling, fibre, racks and power textbook, what normal operation looks like, and how to prove the result in the field.
The previous chapter introduced ups sizing, runtime and installation playbook. This chapter continues the sequence by focusing on poe installation, budgeting and troubleshooting playbook, so the reader can connect the architecture to a more specific operational problem.
Learning objectives
- Explain the main purpose of PoE Installation, Budgeting and Troubleshooting in plain language.
- Identify the components that must work together for the service to operate.
- Use evidence to separate a design problem from a configuration or physical fault.
- Describe the business impact of a failure and the evidence required for handover.
Why this matters in a real company
PoE lets the company power devices such as cameras and access points from the network switch. Good design reduces local power supplies and makes UPS protection easier, but power budgets and cabling quality still matter.
Course: Cabling, Fibre, Racks and Power Textbook | Security and CCTV Technical Textbook
PLAIN ENGLISH
Technical terms used in this chapter
You do not need to memorise the jargon first. Understand what each term does and why somebody running a company would care about it.
PAT
Port Address Translation
A form of NAT that lets many internal connections share one public address by tracking transport ports.
In everyday business: Hundreds of users can browse the Internet through one public IPv4 address.
PoE
Power over Ethernet
Technology that sends DC power and Ethernet data over the same twisted-pair cable.
In everyday business: A camera or access point can be installed with one network cable instead of a separate power outlet.
BUSINESS TRANSLATION
What this means outside the server room
This topic matters because technical infrastructure exists to support everyday business operations. Understanding the purpose makes it easier to choose the right design and justify the cost.
Firewall
What it means: A firewall controls which network connections are allowed between users, systems and external networks.
In normal business language: It is a security checkpoint between parts of the company network. It should allow legitimate work while blocking unwanted access.
Why the decision matters: Firewall rules should describe real business flows such as 'staff may reach accounting on HTTPS', not unexplained broad permits.
NAT
What it means: NAT changes IP addresses as traffic crosses a network boundary.
In normal business language: It is similar to a company switchboard: many internal extensions can share one public number.
Why the decision matters: NAT helps with address use and publishing services, but it is not a substitute for firewall security.
PoE
What it means: Power over Ethernet sends both data and electrical power over the same Ethernet cable.
In normal business language: A camera or access point can use one cable instead of separate network and power wiring.
Why the decision matters: PoE can simplify installation and UPS protection, but the switch power budget and cable quality still need to be designed.
Chapter contents
12.1 Design with actual device data
Record the published PoE requirement for each camera, AP, phone or other PD. Do not use one generic wattage for an entire device class. Some devices change demand when heaters, IR illuminators, radios or USB accessories become active.
Build a port-by-port power schedule
| Port | Device | Required PoE | Expected watts | UPS backed? |
|---|---|---|---|---|
| 1 | AP-01 | User verified | User verified | Yes / No |
| 2 | CAM-01 | User verified | User verified | Yes / No |
Why "48-port PoE switch" is not enough information
The switch may have many PoE-capable ports but a smaller total power budget. The installer must check both per-port capability and the sum of planned loads. Some switch models offer different PoE budgets depending on installed power supplies.
Cabling can be the power fault
PoE relies on copper conductors and connector contacts. Excess resistance, poor termination or damaged conductors can create voltage drop and heating. A link can sometimes pass data at a reduced speed while still having a pair fault that interferes with power delivery.
Commission under realistic load
Do not declare the PoE design complete because every endpoint powers up one by one. Bring the system into its expected operating state and check switch power telemetry while cameras enable IR, AP radios are active and phones or other loads are present.
Fault sequence for a device that reboots
- Check switch log and PoE event time.
- Record current port allocation and total switch budget.
- Compare device peak requirement to the port capability.
- Test or replace patch leads.
- Test the permanent link.
- Check upstream AC and UPS events at the same timestamp.
- Move the device to a known-good compatible port only as a controlled test.
Client benefit
Good PoE design reduces random endpoint reboots, avoids power-budget surprises during expansion, and lets the client understand exactly which critical devices remain powered during an outage.
PoE Field Guide | PoE Budget Calculation | PoE Device Not Powering
Training manual: commission PoE as a power system and a data system
Useful switch telemetry
On Cisco Catalyst platforms, show power inline displays PoE availability, used power, remaining power and per-port status. Other vendors expose equivalent information in their UI or CLI. Capture this at commissioning so there is a baseline.
show power inline
show power inline interface GigabitEthernet1/0/12 detail
show interfaces GigabitEthernet1/0/12 status
show interfaces GigabitEthernet1/0/12 counters errors
Calculation example
Suppose a design has 10 devices whose verified maximum requirement is 12 W each and 4 devices whose verified maximum requirement is 22 W each. The entered arithmetic total is:
10 x 12 W + 4 x 22 W = 208 W
That does not prove a 208 W switch budget is sufficient. The installer must still check the PSE port types, allocation behaviour, switch power-supply limits and any planning headroom required by the project.
Night-time camera trap
A camera system may pass commissioning during the day and exceed expected load after IR illuminators or heaters turn on. Commission critical PoE systems in the highest expected operating state, or use manufacturer maximum power values rather than daytime observed values.
Acceptance checklist
- Every PD requirement is taken from the actual model documentation.
- Per-port PoE capability is checked.
- Total switch budget is checked under realistic load.
- Critical ports are mapped to UPS-backed power.
- Switch PoE telemetry is saved as a baseline.
- Cabling is tested where power instability is suspected.
WORKED BUSINESS SCENARIO
Scenario: cameras reboot every night
Cameras work during the day but some restart after dark when infrared LEDs switch on and power draw rises.
What the chapter teaches us: The network can be logically correct while the power path is marginal. Switch budget, per-port allocation, cable resistance and peak device load all need to be checked.
Think it through
- What changes at night that could increase load?
- How would a short known-good cable help isolate the problem?
- Why is total switch PoE budget different from one port's power capability?
PRACTICAL WORK
Hands-on lab
Connect a known PoE device and record switch power allocation, actual draw if available, cable result and behaviour during peak device load.
Troubleshooting exercise
A camera reboots at night. Compare switch PoE budget, device peak load, cable resistance or termination and behaviour on a short known-good cable.
Chapter field checklist
- I can explain the subject without relying only on acronyms.
- I can draw or describe the main traffic, storage, power or service path.
- I know what normal operation should look like.
- I know which logs, counters or test results prove the result.
- I can explain the business impact if this component fails.
- I would document the final configuration and evidence at handover.
Chapter summary
PoE Installation, Budgeting and Troubleshooting Playbook should now be understood as a business service with a technical implementation, not simply a collection of commands or product names. The important habit is to know the purpose, understand the dependencies, measure the result and document what was proven.
END OF CHAPTER
Review questions
- Explain the subject in plain language to a business owner.
- List the main dependencies that must be healthy before this service can work.
- Describe one realistic failure and the first three pieces of evidence you would collect.
- Explain what should be documented at handover.
A good answer should explain the reason, not only repeat a product name or command.