VMware ESXi and vSphere Cluster Management

Introduction to IP Video Surveillance Systems

Learn how IP video surveillance works, including cameras, NVRs, networking, PoE, recording, monitoring, remote access, analytics, and deployment planning.

IP video surveillance is a security and observation system in which cameras transmit digital video over an Internet Protocol (IP) network. The system may be as small as one camera viewed from a phone or as large as a multi-camera installation with dedicated recording, monitoring, user management, and video analytics.

A complete system has several separate responsibilities:

  • Capture: An IP camera observes a scene and creates digital video.
  • Transport: Ethernet cabling, switches, and network protocols carry the video stream.
  • Recording: An NVR or another recording platform stores video for later review.
  • Viewing: A monitor, computer, or mobile device displays live or recorded video.
  • Management: An NVR interface or Video Management Software (VMS) controls cameras, users, recording schedules, playback, and exports.

Typical uses include deterring unwanted activity, reviewing incidents, preserving footage, supporting identification, observing traffic or workplace operations, and performing automated analysis. Video can provide useful evidence, but its value depends on camera placement, lighting, image quality, retention, and controlled access.

Core IP Surveillance Architecture

The usual video path is:

IP camera → Ethernet/UTP network → NVR or recording platform → local or remote viewers

An IP camera digitizes video and sends one or more streams using TCP/IP, the networking protocol suite used by cameras, recorders, computers, switches, and routers. A switch connects devices and forwards traffic. The NVR receives camera streams, records them, and provides playback and management functions. Viewers connect either directly to the recorder or through client software and mobile applications.

  • Camera network: Provides connectivity between cameras, switches, and the recorder.
  • NVR: Receives, stores, plays back, and manages network camera video.
  • Monitor: Displays local live view or playback from the NVR.
  • Client computer: Uses a browser, client application, or VMS to view and manage the system.
  • Mobile device: Uses an authorized application for live view, playback, alerts, or administration.
  • Router: Connects the surveillance network to other LAN devices and, when securely configured, to remote users.

Local viewing normally means a monitor is connected directly to the NVR. A workstation on the same LAN can also access the recorder without sending traffic across the internet. Remote viewing occurs when an authorized computer or phone reaches the system through a router, managed remote-access service, or VPN. Remote access requires correct network configuration and secure authentication; it is not automatic merely because the NVR is connected to a network.

IP Surveillance Component Roles

IP camera — Creates and transmits digital video; usually connects by Ethernet or Wi-Fi; may use PoE or a separate power adapter; selection depends on resolution, lens, lighting, location, and network compatibility.

PoE switch — Connects cameras and forwards video to the NVR while supplying Power over Ethernet; connects by Ethernet; requires compatible ports and sufficient total power budget.

NVR — Receives, stores, plays back, and manages camera streams; connects to the camera network and display; usually uses AC power; selection depends on channels, bandwidth, storage, outputs, and PoE options.

Router — Connects the surveillance LAN to other networks and controlled remote access; uses Ethernet or another WAN connection; requires correct IP, gateway, firewall, and remote-access policies.

Monitor — Displays local live view and playback; commonly connects by HDMI or VGA; uses its own power; check supported resolution and connector type.

Client PC — Provides local or remote live view, playback, export, and administration; connects over the LAN or an approved remote path; requires compatible client software and permissions.

Mobile device — Provides authorized mobile viewing, playback, notifications, and selected administration; uses Wi-Fi or cellular connectivity; requires a secure application and account.

VMS — Provides software-based viewing, device administration, search, playback, and export; runs on a workstation or server; check supported cameras, operating system, licensing, and user roles.

IP Cameras

An IP camera is a network-connected camera that creates and transmits digital video streams. Unlike a simple analog camera that sends a raw video signal to a nearby recorder, an IP camera participates in the network and normally has its own network address and configuration.

Important camera characteristics

  • Resolution: The number of pixels in the image. Higher resolution can reveal more detail, but it also increases storage and bandwidth requirements.
  • Lens and viewing angle: A wide-angle lens covers more area but may show less detail at a distance. A narrower or telephoto lens observes a smaller area with greater apparent detail.
  • Low-light and day/night capability: Cameras may use infrared illumination, sensitivity controls, or a day/night mechanism. Test performance in the actual lighting conditions.
  • Indoor or outdoor suitability: Outdoor installations need suitable weather and temperature protection. Physical housing ratings should be checked rather than assumed from appearance.
  • Connectivity: Wired Ethernet is generally more predictable for continuous surveillance traffic. Wireless-capable models can be useful where cabling is difficult, but interference, signal strength, and congestion must be considered.

Edge storage stores video inside the camera, commonly on a memory card. It can preserve footage when the NVR or network connection is temporarily unavailable. Edge storage is a supplement, not always a replacement for centralized recording: capacity is limited, cards can fail, and retrieving footage may require camera access.

Camera Form Factors

Bullet: An elongated or cylindrical housing, commonly selected for exterior coverage, directional views, or longer viewing distances. Confirm that the lens, mounting position, lighting, and environmental protection match the scene.

Dome: A compact dome enclosure commonly used indoors or where a more discreet appearance is preferred. The dome shape does not by itself determine resolution, lens quality, or weather rating.

PTZ: A pan-tilt-zoom camera that can be moved and zoomed remotely. It is useful for operator-led observation and following activity, but a PTZ cannot show every direction at once and should not automatically replace fixed cameras.

Box: A modular camera body that accepts separately selected lenses. It is useful when a specialized field of view is required. The body and lens must be selected as a compatible pair.

Physical form does not alone determine image quality, coverage, night performance, or environmental rating. Those properties come from the sensor, lens, illumination, processing, housing, installation, and scene conditions.

Network Video Recorders

An NVR, or Network Video Recorder, is a device or appliance that receives network camera streams and stores them. It commonly provides recording, playback, camera discovery or addition, user administration, display output, and basic event or motion configuration.

Many NVRs have direct monitor outputs. HDMI is a digital display connection commonly used with modern monitors, while VGA is an analog connection found on some recorders and displays. Direct output allows onsite viewing without a separate computer.

A recorder's channel count is its camera input capacity. A 16-channel NVR can support up to 16 camera channels, but that does not guarantee that any combination of 16 high-resolution cameras will work. Resolution, frame rate, compression, aggregate bitrate, and recorder limits must also be checked.

NVR selection criteria

Channel count: Determines the maximum supported number of camera streams. Ask how many cameras are needed now and how many may be added later.

Maximum supported resolution: Confirms whether the NVR can record the chosen camera resolutions. Ask whether the limit applies to recording, live display, or both.

Incoming bandwidth: The amount of camera traffic the NVR can accept. Add the expected bitrates of all camera streams and leave practical headroom.

Outgoing bandwidth: The amount of video the NVR can send to monitors, client software, and remote viewers. High-resolution multi-camera viewing can consume substantial output capacity.

Storage capacity: Determines how long recordings can be retained. Capacity depends on camera count, bitrate, resolution, frame rate, recording mode, and retention policy.

HDMI/VGA outputs: Determine which monitors can be connected directly and at what display resolutions.

Integrated PoE ports: A PoE NVR can directly connect and power compatible cameras. Check the number of ports, supported PoE standards, isolation or network design, and total power budget.

Networking and Cabling

Ethernet is the common wired connection for IP surveillance. It usually uses UTP, or unshielded twisted-pair, cable. A cable run connects a camera to a switch, a switch to the NVR, and other devices to the LAN according to the chosen design.

A network switch connects cameras and forwards their video traffic to the NVR. A non-PoE switch supplies connectivity only, so cameras need separate power. A PoE switch supplies both connectivity and electrical power to compatible cameras.

The router connects the surveillance network to other LAN devices and possibly to remote-access services. It can enforce firewall and routing policies. A router should not be treated as a reason to expose every camera or NVR service directly to the public internet.

Each camera, the NVR, and management clients need unique, reachable IP addresses. The subnet mask determines which addresses are local, and the default gateway is used to reach other networks. Document device names, addresses, credentials ownership, and physical locations.

Dedicated and shared networks

  • A dedicated camera network separates surveillance traffic from ordinary business or home traffic. It can simplify control, reduce contention, and limit access.
  • A shared network carries camera traffic alongside computers, phones, printers, and other devices. It may be adequate for a small installation, but bandwidth, addressing, security, and switch capacity must be planned.

Power Delivery

Some cameras and small recorders use conventional DC power from a separate adapter. This approach requires a power outlet or low-voltage power distribution near each device and a suitable cable or adapter.

Power over Ethernet (PoE) combines network data and electrical power on one Ethernet cable. A PoE switch or PoE NVR provides power to compatible cameras while carrying their streams.

PoE planning has two checks:

  1. Confirm that each switch port or NVR port supports the camera's required PoE standard and power level.
  2. Add the expected power draw of all cameras and compare it with the switch or NVR's total PoE budget. The total budget is not necessarily equal to the maximum power of one port multiplied by every port.

Monitoring, Remote Access, and VMS

Local live monitoring is commonly provided by a screen attached to the NVR. The NVR can show a multi-camera grid, a selected full-screen camera, alerts, and playback controls.

Vendor client software and mobile applications extend these functions. Depending on the product, they can provide live view, playback, search, footage export, device configuration, user administration, notifications, and system health information.

VMS means Video Management Software. An NVR's built-in interface is software running within the recorder. A VMS is generally installed on a workstation, server, or mobile device and may manage one or more recorders or cameras. The exact features depend on the product and supported devices.

Remote access from a computer or phone depends on network configuration and secure authentication. Use unique, strong credentials, role-based permissions, current firmware and software, and an approved managed or VPN-based method where available. Avoid broad public exposure of camera and recorder services.

Applications and Video Analytics

  • Deterrence and detection: Visible cameras and associated lighting or signage may discourage unwanted activity and help detect events.
  • Incident investigation: Operators can search and review playback around a known time or event.
  • Evidence preservation: Relevant clips can be exported, documented, and retained according to organizational and legal requirements.
  • Identification support: Properly positioned, well-lit cameras may capture useful clothing, behavior, or facial and vehicle details. Identification is not guaranteed.
  • Traffic and operational observation: Cameras can show vehicle flow, entrances, queues, production areas, or other processes.
  • Analytics: Software may count people, recognize license plates, detect movement, or support speed-related monitoring.

Analytics effectiveness depends on placement, camera angle, resolution, shutter speed, lighting, scene conditions, camera stability, network delivery, and software capability. A general-purpose camera is not automatically suitable for license plate recognition or speed measurement. For example, counting entries requires a controlled view of the doorway, while plate recognition requires a suitable vehicle angle, distance, exposure, and lighting.

Simple Small-Office Deployment

Consider a small office or retail installation with four IP cameras, a PoE switch, four Ethernet cable runs, an eight-channel NVR, an HDMI monitor, an office router, a desktop client, and an authorized mobile application.

  1. Run one Ethernet/UTP cable from each camera to a PoE port on the switch.
  2. The PoE switch supplies power to each compatible camera and transports the camera streams across the network.
  3. Connect the switch to the NVR so the recorder can discover or receive the four streams.
  4. Connect the monitor to the NVR's HDMI output for onsite live view and playback.
  5. Connect the workstation to the same LAN and use approved client software or VMS for live view, playback, export, and administration.
  6. Connect the surveillance LAN to the router according to the network design. The router provides a controlled path for authorized remote workstation and mobile access.
Camera 1 ─┐
Camera 2 ─┤
Camera 3 ─┼─ Ethernet/PoE switch ── NVR ── HDMI monitor
Camera 4 ─┘             │              │
                        │              └─ LAN workstation with VMS
                        └─ Router ─── authorized remote computer/mobile device

In this example, the eight-channel NVR has room for four additional camera channels, but expansion still requires available switch ports, cable routes, PoE capacity, network bandwidth, storage, and recorder bandwidth.

Basic Configuration Workflow

  1. Connect cameras to the camera network or to the NVR's integrated PoE ports.
  2. Assign or document unique IP addresses, names, locations, subnet information, and credential ownership.
  3. Discover or add each camera to the NVR.
  4. Confirm that every camera produces a live stream.
  5. Set continuous or event-based recording schedules and retention behavior.
  6. Configure monitor layouts, users, permissions, date, time zone, and time synchronization.
  7. Test playback, export, storage health, and authorized remote viewing.

An illustrative addressing plan might place the NVR at one unique address, each camera at another unique address in the same camera subnet, and management clients on a routable LAN. The exact addresses are site-specific; avoid duplicate addresses and document every assignment.

Planning and Selection Checklist

  • Define the objective: deterrence, incident review, identification support, traffic observation, counting, or another task.
  • Match the camera type, lens, mounting position, resolution, and lighting capability to the scene.
  • Choose indoor or outdoor equipment based on actual environmental requirements, not housing shape alone.
  • Size the NVR by channel count, camera resolution, aggregate stream bitrate, incoming bandwidth, outgoing bandwidth, and storage retention.
  • Account for Ethernet ports, cable distances and routes, switch capacity, PoE compatibility, and total PoE budget.
  • Decide who needs local viewing, LAN access, remote viewing, playback, export, configuration, and administration.
  • Use separate user accounts and least-privilege permissions where supported.
  • Plan privacy notices, restricted camera views, legal retention requirements, access logging, and secure handling of exported footage.
  • Test the system at night and under the conditions in which incidents are most likely to occur.

Troubleshooting Common Problems

No live image on the NVR

Possible causes include missing camera power, a bad cable or port, an exceeded PoE budget, incompatible IP settings, incorrect credentials, or unsupported stream settings.

  • Check camera power and PoE indicators.
  • Test the cable and switch port.
  • Confirm that the camera is reachable on the correct network.
  • Verify the NVR camera entry and login details.
  • Check camera compatibility and stream configuration.

Live video works but recordings are missing

Review the recording schedule, storage installation and health, recording mode, and recorder date and time. Motion-triggered recording also requires correctly configured event rules. Confirm the time zone and synchronization settings before relying on timestamps.

Remote users cannot connect

Confirm local access first. Then check the NVR's IP address, subnet, gateway, and DNS settings as applicable. Review the remote-access service, VPN, firewall, router policy, and user permissions. Test with an authorized account rather than an administrator account by default.

Video is choppy or delayed

Insufficient network capacity, recorder bandwidth limits, excessive camera resolution or bitrate, unstable wireless connectivity, and too many high-quality remote streams can all cause delay.

  • Inspect switch links and available network capacity.
  • Compare aggregate camera traffic with the NVR's incoming bandwidth.
  • Use a lower-bandwidth substream for remote live viewing when appropriate.
  • Prefer stable wired connections for critical cameras.

Exam-Relevant Notes

  • An IP camera creates and transmits digital video; an NVR receives and stores network camera streams.
  • A switch forwards traffic. A PoE switch also supplies power to compatible devices.
  • A router connects networks and can provide a controlled path for remote access, but it is not itself a recorder.
  • Channel count is the maximum camera input capacity, not a guarantee that every camera combination fits the bandwidth or storage limits.
  • Incoming bandwidth concerns streams entering the NVR; outgoing bandwidth concerns streams leaving it for displays and clients.
  • Edge storage is storage in the camera, often on a memory card, and can help during network or recorder interruptions.
  • Wired Ethernet is generally more predictable than wireless for continuous surveillance traffic.
  • Camera form factor does not by itself determine image quality, field of view, or environmental suitability.
  • Secure remote access requires authentication, permissions, current software, and suitable network controls.

For a concise reference to the subject, see IP video surveillance fundamentals.