Quick answer: Record the actual channel message and affected device before changing anything. Check compatible power and the physical path, then actual identity/addressing, accounts, media and recorder resources as the evidence directs. A lit LED, discovery result or online status does not prove every layer works. Protect required recordings and verify playback and events after the approved correction.
On this page
Which symptom are you looking at? Symptom, cause and fix
Use the exact model/firmware message and logs as starting evidence, then corroborate the relevant layer. A dark IR array or lit port LED is not a universal power test, and two alternating channels do not by themselves prove an IP conflict.
| Observed symptom | Possible areas | Next check |
|---|---|---|
| Missing link or offline | Power, path, device, mapping or application settings | Exact status meaning and supported power/link diagnostics |
| Link reported, channel offline | Address, account, endpoint, integration, capacity or remaining path errors | Actual identity, errors and approved network/service path |
| Discovered but add fails | Supported method, account/rights, endpoint, time or resources | Read the exact error; discovery does not establish media access |
| Alternating channels | Address/mapping conflict or another correlated fault | Corroborate actual device/IP/MAC and network records |
| Online but black or stuttering | Media/codec, authorization, transport, decode, load or another fault | Actual stream settings and logs, not automatic compression reduction |
| Drop after change or on a schedule | Firmware/configuration, services, load, environment or time | Correlate actual versions, changes and event records |
Step 1: Does the camera actually have power? (PoE LED, cable budget, switch class)
- Power and indicators: read exact-model diagnostics. Not every camera has visible IR, and a missing red glow does not establish missing power. A link LED does not certify delivered power under peak load.
- Compatible PoE: compare source/device class, per-port/shared budget, startup/night loads, losses and environment. Source15.4/30 W ratings are not the same as power available at the device.
- Cable path: verify the actual channel/topology and required tests. Conventional100 m channel design limits include patching; length alone does not determine every fault.
- Switch example: CS-H1108PLS lists8×100 Mbps PoE ports,2×100 Mbps uplinks,100 W total budget and100 m standard/250 m Extend Mode. Confirm speed, cable, compatible power and load in the selected mode; the distance row is not a universal extension guarantee.
- Recording: obtain approval for interruption and preserve required footage before moving ports, changing power or resetting equipment.
A controlled short-cable/compatible-port comparison can narrow a fault but does not prove the entire device healthy or immediately locate the failing part. Record original mapping, test one variable at a time and use the safe service process. Have the responsible installer/designer confirm actual routing, ratings and applicable local installation requirements. The PoE camera troubleshooting guide covers the power checks.
Step 2: Can you find the camera on the network? (Search Config Tool)
Confirm actual device identity and the supported discovery/configuration tool for that firmware. Discovery is a separate function from authenticated services, media and recording; successful discovery does not clear all network or configuration issues.
- Use the recorder’s supported search on its actual configured interfaces. Record the discovered identity and endpoint, then verify the intended device and integration rather than trusting an IP alone.
- Use the current supported tool on an authorized path. The Search Config Tool guide and Downloads are the references for the actual utility/version and supported actions.
- Coordinate any address/DHCP change with IT and the recorder mapping; do not bridge an isolated camera network or bypass access rules just to make discovery work.
If discovery fails, investigate the actual permitted path, service support, power and device evidence. Do not automatically reterminate, move a live camera or assume a different subnet is wrong. Routed subnets or scoped discovery can be part of a valid design.
Step 3: DHCP or static IP on the NVR PoE ports?
Read the exact recorder camera/uplink interface and address behavior from supported configuration. CS-N110 P8H-AI lists10 channels/eight PoE ports and CS-N220 P16H-AI20/16 with a Gigabit uplink; these rows do not establish universal internal DHCP behavior or a required camera address mode. The DHCP addressing guide explains the addressing concepts.
| Actual path | What to establish | Controlled action |
|---|---|---|
| Built-in camera ports | Exact supported address assignment, activation, accounts and channel mapping | Use that model/firmware’s approved configuration; no universal DHCP mandate |
| External switch | Compatible power, approved stable addressing and recorder reachability | Use supported static allocation or reservations, routes and exclusions with IT |
| Routed/segmented network | Permitted services/media and actual discovery scope | Preserve designed isolation; verify exact flows rather than forcing one segment |
Alternating channels can suggest an address or mapping issue but are not conclusive. Compare actual identities, DHCP/neighbor records and approved topology before a controlled correction. IP address conflicts between cameras provides the full check.
Step 4: Credentials and ONVIF profile
A failed add can involve account/permissions, supported method, endpoint, lockout, time or other constraints. Check the actual error and intended device first. Correct a confirmed channel credential mismatch through the supported account process; stop repeated guesses and use the actual recovery instructions if needed.
Choose an integration supported by the exact camera, recorder and firmware, including native or ONVIF where documented. Confirm actual ONVIF conformance/functions, secure account method, endpoint and relevant clock requirements. Do not assume S/T/G/M on all CASE products, one separate-user rule or a universal AI path. ONVIF camera not connecting to NVR covers the detailed checks; recording, events and VCA Search need their own acceptance tests.
Step 5: Is the channel over the NVR bandwidth or resolution limit?
Check actual media setup and errors alongside the recorder limits. An online-but-black tile does not identify bandwidth as the cause or prove the most recently added channel should fail first. The catalog gives these model rows, subject to the actual revision and configuration:
- CS-N110 P8H-AI: bandwidth 100 Mbps incoming / 80 Mbps outgoing, maximum resolution 16MP.
- CS-N220 P16H-AI: bandwidth 160 Mbps incoming (120 Mbps with AI on) / 80 Mbps outgoing, maximum resolution 16MP.
Budget all required streams and relevant input/output/decode/AI/storage loads with headroom; confirm the manufacturer’s definitions. CS-N220 P16H-AI’s input row is160 Mbps or120 Mbps with AI on. That can affect design, but does not establish the cause or which channel fails. Any codec/fps/bitrate change must remain compatible and meet the agreed image task; S+265 or H.265 does not guarantee lower traffic at unchanged usable quality. The IP camera bandwidth calculator covers the calculation.
Step 6: Firmware and time sync
Compare the exact last-known-working versions/configuration and incident times with the actual errors. A scheduled drop can have several causes, and a post-update symptom does not prove one firmware fault or justify an immediate rollback. Use the firmware maintenance calendar to track the approved changes.
- Firmware: obtain exact-revision approved releases and a supported update/rollback plan with backups and recording impact understood. Keeping an older file alone does not establish safe downgrade support.
- Time: use approved accurate coherent sources and current applicable local display rules. Timestamp checks depend on the authentication method; preserve relevant recordings and known clock offsets before correction.
- Restart: use only the actual supported sequence when needed and authorized. Do not automatically power-cycle the recorder and every camera or assume a camera remains at an old address because of boot order.
- Acceptance: verify required channels, events, recording, playback and recovery after the change under representative load.
When to call technical support
Escalate with the exact full models/firmware, affected identity/mapping, redacted status/errors and controlled tests, including power/path and required recording impact. The list of possible causes is not exhausted by a few passed checks. Anabon supports installers, integrators, dealers and approved business accounts; send only necessary information privately, without passwords, secret QR codes or unrelated footage.
What to tell your customer
We will explain the actual checks and confirmed findings, agree the correction and verify the required recording and playback afterwards. We will document any remaining limits rather than declaring an addressing fault from a status light. For warranty and service, end users should contact the installer or company that supplied the system; Anabon supports that partner through its business-account channel.
FAQ
Why does my NVR show a camera as offline when the camera LED is on?
A lit indicator alone does not establish stable compatible power or end-to-end communication. Check its exact meaning, errors and real-load behavior alongside device identity/addressing, accounts, endpoints and capacity. Do not automatically change to DHCP or a new fixed IP without the approved plan.
Should cameras on the NVR PoE ports be DHCP or static?
Use the exact recorder/firmware’s supported camera-network configuration and the site’s approved addressing design. Static allocation or supported reservations may suit an external path; a lease renewal does not inherently change an address and a reservation need not be outside the managed scope. Confirm actual mapping and recovery behavior with IT.
Can a PoE budget problem look like a network problem?
Yes. Inadequate compatible power can prevent a device starting or retaining link, but the symptom does not prove the cause or identify the last camera as the failing one. Compare actual class, per-port/shared budget, losses, peak load and environment using supported diagnostics, then test the approved correction and required recordings. Use the PoE budget calculator for the actual load assessment.
Does a third-party camera work on a CASE NVR?
It depends on the exact camera, recorder, firmware and supported integration. Check current conformance/functions where relevant and test live view, required events/controls, recording and playback. A brand/profile label alone is not a compatibility or recorder-AI/VCA Search guarantee; get written confirmation for the required workflow.
References
- Anabon: exact model and revision documents
- Anabon Technical Support
- IETF RFC2131: DHCP allocation and renewal
- ONVIF: exact conformant products/firmware
