Static IP or DHCP Reservation for AV Devices?

Use a DHCP reservation when the venue reliably operates DHCP and can maintain the reservation record. Use a manually configured address when the device or isolated installation requires it and the network owner can exclude that address from dynamic allocation. The important outcome is one documented owner for every address, with a replacement procedure that keeps controller destinations valid.

Decide who will maintain the address

A projector that works on the integrator's bench can fail after delivery if the controller stores a destination that later changes. Start the design meeting with ownership rather than the familiar argument that static addressing is always more reliable. Ask who controls the venue's DHCP service, who can edit reservations, and whether that service remains available during recovery from an outage.

RFC 2131 defines DHCP allocation mechanisms, including administrator controlled allocation. A reservation is commonly a server implementation of that operational idea; the exact identifier can be a client identifier rather than simply the MAC address. Confirm what the actual server and endpoint send before cloning reservation entries.

Build a conflict free address register

• Obtain the approved subnet, prefix, gateway and DNS settings from the network owner.

• Record each endpoint's asset label, wired interface identifier, firmware and chosen allocation method.

• Reserve a nonoverlapping range for manually configured infrastructure, or explicitly exclude individual manual addresses in the DHCP service.

• Assign a maintenance laptop address through an approved method; do not guess that an apparently unused address is safe.

• Update the controller's device destinations only after the endpoint has its final address.

For example, a project register might allocate 10.40.20.30 to a rack gateway and 10.40.20.60 to a projector. Those are illustrative private addresses, not recommended defaults. RFC 1918 identifies private IPv4 space; private addressing still needs local coordination and does not establish a security boundary.

Test the dependencies separately

For a reservation, renew the lease through the endpoint's documented interface and check that the recorded identifier receives the intended address. Reboot the endpoint and the controller separately. Then schedule a controlled DHCP outage test with the network owner if offline recovery matters. A client may reuse a valid lease, but that observation must not be interpreted as proof that every cold start works without a server.

For a manual address, inspect the mask and gateway on the device itself. Confirm that a controller on another permitted subnet can receive a reply, not just that a laptop beside the projector can ping it. Save the reservation export or manual configuration alongside the addressing register. Include both the old and replacement identifiers in the change record when equipment is swapped.

Acceptance and limits

Accept the addressing plan when the endpoint retains the intended identity after restart, the intended controller can execute a harmless status query, and another technician can replace the endpoint using the register. Record how long startup recovery took and which network services were required. Do not claim that a reservation eliminates all address conflicts; a manually configured device can still duplicate a leased address.

Use the AV commissioning checklist for wider handover checks. Integrators evaluating a repeatable deployment process can discuss partnership requirements with the address register and device models available.