Networking Guide Redwood Manager 3.
Table of Contents 1 Introduction..................................................................................................................................................... 3 1.1 IP Addresses .......................................................................................................................................... 3 1.1.1 Static vs. DHCP .......................................................................................................................... 3 1.2 Required Ports ...
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.
DHCP Advantages • Easiest deployment because all parameters are automatically provided to the device from the DHCP server when the device is attached to the network. • No possibility of IP address conflicts. • Allows for static DHCP assignment: A DHCP server leases a permanent IP address to a device based on the device’s MAC address. You can turn off a device and move it from one location to another without it losing its IP address assignment.
2 Adding the Redwood Engine to the Network The front of the Engine has two management ports. Use the LAN port if you are connecting the Engine to your network (if this is a standalone Engine that will not be connected to a network, you may use the secondary port for Engine access). The Redwood Engine must be connected to a network switch or router via a Cat 5e, Cat6 or Cat6A network cabling.
5. Click Manage Lights. 6. On the Redwood Manager page, click the gear icon ( ) in the top right corner to open the Engine Configuration screen. 7. On the Network tab, select Static. 8. Enter the Engine’s hostname, IP address, net mask, and Gateway address. Providing a Gateway address and hostname is optional. Configuring a Gateway allows the Engine to communicate with external resources, such as an NTP or SMTP server. Using a hostname makes it easier to identify the Engine.
9. (Optional) To set the Engine’s date and time, click the Time tab. a. To set the time manually, select Manual, select the time zone, and enter the date and time. The time is entered in 24-hour format, but it is displayed in AM/PM format. b. To use NTP, select NTP Server. Enter a valid timeserver, such as pool.ntp.org. If you want to use a domain name, you must configure a DNS server on the DNS tab. Otherwise, enter the IP address of the NTP server. 10.
3 Grouping Engines into Clusters If you have several Engines, you can group them together into a Cluster or multiple Clusters for easier management. You can combine up to eight Redwood Engines into a Cluster when a Redwood Director is not used as a Cluster Master, or up to 64 Engines if a Redwood Director is used as a Cluster Master. A Cluster acts as a single Redwood Engine. Either the Redwood Director or one of the Redwood Engines serves as the Master.
3. In the Cluster tab, name the Cluster and set the Master Engine and Local Engine IDs to 0. You can leave the Master IP field empty. Note: You do not need to use 0. The ID can be any number, but the Master ID must be the same across all Engines in the Cluster. 4. Repeat this process for each Engine that is part of this Cluster. Use the same Master Engine ID for all Engines in the Cluster, but assign each Engine a unique ID.
4 Troubleshooting If you are having problems networking the Engines, review the following common problems. 4.1 Unable to Remotely Access the Engine on the LAN Verify that the IP address is configured correctly. Determine whether your Engine is supposed to receive an IP address via DHCP or programmed with a static IP address. 1. Connect to the Engine via the secondary LAN interface using the static IP address 192.168.1.1/24. You must adjust your computer’s IP address to match the subnet (192.168.1.
If the Cluster configuration is correct on all Engines, the Engines might not be communicating with each other due to a network related problem. Normally, connecting the Engines to an unmanaged switch is the best practice, because unmanaged switches allow all traffic and do not have options to switch protocols off. If your Engines are connected to a managed switch and you have verified that all network and Cluster settings are correct, contact your IT department for further assistance. 4.
Appendix A: How to Set the IP Address on Your Operating System Windows XP and Windows 7 1. 2. 3. 4. 5. 6. 7. 8. From the Control Panel, open Network Connections. In the search box, type adapter. Under Network and Sharing Center, click View network connections. Right-click the connection that you want to change, and select Properties. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
