CommScope Redwood Networking User Manual

Networking Guide

Redwoo d Ma na ger 3.0
August 2013

Table of Contents

1 Introduction ..................................................................................................................................................... 3

1.1 IP Addresses .......................................................................................................................................... 3

1.1.1 Static vs. DHCP .......................................................................................................................... 3

1.2 Required Ports ........................................................................................................................................ 4

2 Adding the Redwood Engine to the Network ............................................................................................... 5

2.1 Using a Static IP Address ....................................................................................................................... 5

2.2 Using DHCP ........................................................................................................................................... 6

2.3 Verifying the Connection ......................................................................................................................... 7

2.4 Backing Up the Configuration ................................................................................................................. 7

3 Grouping Engines into Clusters ................................................................................................................... 8

3.1 Creating a Cluster Plan ........................................................................................................................... 8

3.2 Prerequisites ........................................................................................................................................... 8

3.3 Creating a Cluster ................................................................................................................................... 8

3.4 Verifying the Clustering ........................................................................................................................... 9

4 Troubleshooting ........................................................................................................................................... 10

4.1 Unable to Remotely Access the Engine on the LAN ............................................................................ 10

4.2 Cannot See Cluster Member Engines from the Master ........................................................................ 10

4.3 Cannot Access a Cluster from the LAN ................................................................................................ 11

Windows XP and Windows 7 ................................................................................................................ 12

Mac OS X .............................................................................................................................................. 12

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.

The Redwood Engine, Sensors, and Gateways are for commercial use only and are not designed
for household use.

IMPORTANT NOTE

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.

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. A static DHCP address also ensures accessibility from any
LAN segment of which the DHCP server has visibility.

DHCP Disadvantages

• Relies on an available DHCP server. If the server goes down or a network outage occurs, accessibility

to devices with DHCP addresses might be interrupted.

• In a loosely secured environment, any device, even an unauthorized one, can receive a DHCP

assigned IP address and have access to the network.

1.2 Required Ports

The Redwood Manager provides users the ability to commission lights, manage lighting policies, and
manage and maintain the system. The Redwood Manager uses specific ports to communicate across the
network. These ports must remain open for the system to function correctly. Under normal operation, the
Redwood Manager does not accept HTTP (port 80) connection attempts. HTTP connections are accepted
only when the Engine is in maintenance mode.

To access the Redwood Manager via a web browser within your LAN, HTTPS access (port 443) must be
allowed to the Engine’s IP address as well as any other Engine that is part of a Cluster. Engines used for
reporting purposes must have Adobe Flash access (port 843).

Port Protocol

65432 UDP
65433 UDP
54321 UDP
443 TCP (HTTPS)
843 TCP (Adobe Flash)
514 UDP