network topology application note - sylvania lighting

Network Topology Application Note

SylSmart

Contents

Network Topology Options ...........................................................................................4

1. EM On Premise with Independent Gateway Network (DHCP from EM) .............5

Network Parameters ............................................................................................................. 7

2. EM On Premise with Gateways on Customer Network (DHCP from EM) ...........8

Network Parameters ........................................................................................................... 10

3. EM On Premise with Gateways on Customer Network (DHCP from Customer)12

Network Parameters ........................................................................................................... 14

4. Energy manager in the Cloud (EMC) ................................................................... 16

Contents

Network Topology Options ...............................................................................................4

1. EM On Premise with Independent Gateway Network (DHCP from EM) ..................5

Network Parameters ................................................................................................................. 7

2. EM On Premise with Gateways on Customer Network (DHCP from EM) ...............8

Network Parameters ............................................................................................................... 10

3. EM On Premise with Gateways on Customer Network (DHCP from Customer) .. 12

Network Parameters ............................................................................................................... 14

4. Energy manager in the Cloud (EMC) ....................................................................... 16

Network Topology Options The SylSmart SSE Energy Manager (EM) may be configured to communicate with devices via the customer network or an independent Enlighted network. The networks can be connected to any Ethernet port, Eth0 or Eth1. A third BACnet network can be configured to communicate with the Building Management System (BMS). Note: Eth0 and Eth1 ports are marked on the Energy Manager (EM) server as LAN 1 and LAN 2 respectively.

Use this application note to determine the appropriate networking configuration depending on the needs of your company and facility layout. The following network options are possible with the Enlighted Lighting network:

1. EM On Premise with Independent Network (DHCP from EM)

2. EM On Premise with Gateways on Customer Network (DHCP from EM)

3. EM On Premise with Gateways on Customer Network (DHCP from Customer)

4. Energy Manager in Cloud (EMC)

The following table summarizes the various network configurations and supported applications:

Network Configuration Gateway Network

DHCP Provider

EM Internet Connection Connected Lighting

BACnet Integration

Space Where

1. Energy Manager on Premise

Independent EM Customer Network or 4G ✓ ✓ ✓

2. Energy Manger on Premise

Customer EM Customer Network ✓ ✓ ✓

3. Energy Manager on Premise

Customer Customer Customer Network ✓ ✓ ✓

4. Energy Manager in Cloud (EMC)

Customer Customer Customer Network ✓ ✓ ✓

The Energy Manager can be located on premise and connected to the Cloud (eCloud) or can reside in the cloud as an

EMC (Energy Manager in the Cloud). The Where application requires EMC. The Space application works with the

Energy Manager on premise connected to eCloud or with EMC.

Note: The Contact Closure devices can connect to the Energy Manager only when it is configured to be the DHCP server providing IP addresses to the Gateways and Contact Closure devices. Each topology is explained in detail in the following sections.

1. EM On Premise with Independent Gateway Network (DHCP from EM)

In this network topology, the Energy Manager (EM) communicates with all devices within the

Lighting network over the Corporate and Gateway networks. The Enlighted sensors communicate

to the Energy Manager through the Gateways using the IEEE 802.15.4 wireless communication

protocol that includes AES encryption.

The on-premise Energy Manager may be on the customer IT network or a stand-alone network.

The Energy Manager’s intuitive graphical user interface can be accessed via a standard secured

browser connection.

Note: POE switches must be 10/100 Full Duplex configured

With Support for BACnet:

The Energy Manager integrates seamlessly with the Building Management Systems (BMS) using

well-defined REST APIs and BACnet interface. The figure below provides an overview of an on

premise network design with support for BACnet.

With eCloud:

All of the Energy Manager configurations may be connected to the Cloud (eCloud). The Space application can be configured to work with the on premise small, mid-range, or Enterprise EM version.

Network Parameters

The Gateway network communicates using standard IP addressing. The parameters for the

networks on Eth1 and Eth2 can be configured in Energy Manager by clicking ADMINISTRATION >

NETWORK SETTINGS. Refer to the following network configuration parameters.

Gateway Network Parameters

Ethernet Port 1 (eth1) The Energy Manager’s DHCP server provides IP addresses for all gateway devices on the network. The default IP address range for the EM and network is 169.254.0.1

Configure the parameters for the Gateway network on Eth1 in EM as shown below. Eth0 is unassigned.

Gateway Network Configuration

Corporate Network Configuration

Corporate and BACnet Network Configuration

2. EM On Premise with Gateways on Customer Network (DHCP from EM)

When the Energy Manager is on premise, it may act as the DHCP server for all Gateways in the

network and provides IP addresses to them. The Gateways communicate with the Energy

Manager (EM) using the customer’s existing network. The Gateway devices are automatically

discovered and added to the Energy Manager. The Corporate network is assigned to use a static

IP address.





With eCloud: All of the Energy Manager configurations may be connected to the Cloud (eCloud). The Space application can be configured to work with the on premise small, mid-range, or Enterprise EM version.

Network Parameters The Gateway and Corporate networks communicate using standard IP addressing. Refer to the following network configuration parameters.


Ethernet Port 1 (eth1) (Two options available)

The Energy Manager’s DHCP server provides the IP addresses for all gateway devices on the network. The default IP address range for the EM and network is 169.254.0.1

Corporate Network Parameters

Ethernet Port 0 (eth0)

Static IP address

• IPV4 address

• Subnet mask

• Default Gateway

Configure the parameters for the Gateway and Corporate networks in Energy Manager as shown below.


3. EM On Premise with Gateways on Customer Network (DHCP from Customer)

The smart sensors communicate with the Energy Manager through the Gateway network using the

IEEE 802.15.4 wireless communication protocol that includes AES encryption. The devices in the

Sensor network interface with the Energy Manager on a Gateway network. The Gateway network

can be configured to receive the IP addresses from the corporate server. The Gateway devices

have to be manually added to the Energy Manager.

The Corporate network is assigned a static IP address on Eth0 port. The BACnet network is

assigned to use a static IP address on the third Ethernet port.





With eCloud:

All of the Energy Manager configurations may be connected to the Enlighted Cloud (eCloud). The Enlighted Space application can be configured to work with the on premise small, mid-range, or Enterprise EM version.

Network Parameters


Ethernet Port 1 (eth1) Energy Manager’s DHCP server provides the IP addresses for all gateway devices on the network. The IP address on the Gateway network cannot be changed from 169.254.0.1

Corporate and BACnet Network Parameters

Ethernet Port 0 (eth0)

Static IP address

• IPV4 address

• Subnet mask

• Default Gateway

Configure the parameters for the Gateway, Corporate and BACnet networks in Energy Manager as shown below.



4. Energy manager in the Cloud (EMC) Starting with EM version 3.6.1, the Energy Manager can reside in the Cloud as an EMC (Energy

Manager in Cloud), and this is the most preferred option as it is scalable and provides easier

administration across multiple sites and applications. The figure below shows the network

architecture for the Energy Manager in the Cloud along with the other components in the network

design:

The smart sensors communicate with the Energy Manager through the Gateway network using the

IEEE 802.15.4 wireless communication protocol that includes AES encryption.

The Gateway network receives the IP addresses from the Corporate server. The Gateway devices

are manually added to the Energy Manager. The Corporate network should have the DNS service

enabled.

Written and maintained by

© 2018 Enlighted, Inc., 930 Benecia Ave., Sunnyvale, CA 94085 U.S.A. All rights

reserved. All other brand or product names are trademarks of their respective

companies or organizations.

network topology application note - sylvania lighting

Documents