CommScope Redwood Networking version 3.0 - Manual (Page 3)

1 Introduction
The Redwood Engine manages the lighting policies, communicates to the Redwood Gateways, distributes
low-voltage DC power to the fixtures, and collects Sensor data.
After the initial AC, network, and fixture connections are complete, connect the Redwood Engines to the
local network. For information on setting up AC and low-voltage settings, see the Redwood Systems
Installation Guide.
If you have several Engines, you can group them together into Clusters for easier management.
IMPORTANT NOTE
The Redwood Engine, Sensors, and Gateways are for commercial use only and are not designed
for household use.
1.1 IP Addresses
To access a Redwood Systems Engine within your LAN, it must have an IP address configured for the
primary LAN interface. The IP address can be static or provided via your DHCP server. By default, the
Redwood Engine is configured to request an IP address via DHCP. If DHCP is not used, you must
configure the Engine with a static IP address.
1.1.1 Static vs. DHCP
The Redwood Engine can use either a static or DHCP (dynamic-lease or static-lease) IP address for
network connectivity. Each type provides different advantages. If your IT department allows it, Redwood
Systems recommends using a static-lease DHCP address.
Static Advantages
• The IP address remains the same unless manually changed on the device.
• Devices are accessible if a network outage occurs as long as they are connected to the same switch
and the switch is powered on.
• You do not need a DHCP server, which eliminates traffic overhead.
Static Disadvantages
• You must plan ahead and evaluate the current infrastructure to determine which IP addresses are
available.
• Conflicts with other devices might occur if the same static IP address is used by two or more devices.
This is typically common in large infrastructures with poor record-keeping.
• It is not practical in large-scale deployments because it is tedious work.