Preparing SNE for a network that supports DHCP and DNS - Metasys - LIT-12013352 - M4-SNE10500-0 - M4-SNE10501-0 - M4-SNE11000-0 - M4-SNE11001-0 - M4-SNE110L0-0 - M4-SNE110L1-0 - M4-SNE22000-0 - M4-SNE22001-0 - Supervisory Device - SNE10 Network Engine - SNE11 Network Engine - SNE22 Network Engine - SNE Supervisory Network Engine - 12.0

SNE Commissioning Guide
Product
Network Engines > Network Control Engines > SNE22 Network Engine
Network Engines > Network Control Engines > SNE11 Network Engine
Document type
Commissioning Guide
Document number
LIT-12013352
Version
12.0
Revision date
2022-12-12
Product status
Active

The following scenario is typical when you install an SNE on an existing building network. Your computer must be connected to the network. The computer must be a DHCP client or configured to use a static IP address appropriate for the network.

Note: We recommend that you configure a DHCP reservation for the SNE to ensure it always receives the same IP address when its lease expires. This practice prevents address bindings between the SNE and other devices from breaking.
  1. Verify that your network administrator has updated the DNS server and the DHCP server with the SNE Ethernet MAC address and the SNE host name.
  2. With your computer or commissioning laptop connected to the building network, open SCT Pro. This tool listens for, and shows, the IP address information of the SNE as it comes online.
  3. Connect the SNE to the network with an Ethernet patch cable.
  4. Connect 24 VAC supply power to the SNE. Then wait for the SNE to complete the startup and initialization sequence. SCT Pro indicates the current IP address of the network engine.
    Note: The startup and initialization sequence may take up to 10 minutes to complete. If the DHCP server is not online when the SNE is powered on (or if the SNE Ethernet cable is disconnected and reconnected with no DHCP server online), the SNE assumes a unique IP address between 169.254.0.1 and 169.254.255.254 and a subnet mask of 255.255.0.0. This is a feature of Automatic Private Internet Protocol Addressing (APIPA) that applies when DHCP is enabled in the SNE (factory default).
  5. Go to Installing Launcher to access the SNE, follow all instructions, then return to the next step in this section.
  6. After you have completed the steps in Installing Launcher to access the SNE, including the step for logging in to the SNE, select the SNE device object in the Navigation panel, and drag it to the Display panel of the Site Management Portal UI. The Focus tab for the selected SNE appears in the Display panel.
    Figure 1. SNE Focus Tab - Basic
  7. Go to the Network tab and verify the Computer Name and Domain Name values. Change these values to the assigned values for your network site. Also verify the Allow http attribute. If trusted certificates are not deployed to the engine, communication between the engine and its clients occurs over port 80. If you need to close the network engine's incoming http communication port (port 80), select False for Allow http. Otherwise, keep this attribute at its default value (True).
    Figure 2. SNE Network Tab - Edit Mode
    Note: Changing the Computer Name forces a device reset on the SNE. (See Computer name and Reset command device.)
  8. Go to the Focus tab and check the SNE Object Name. Change the Object Name to the descriptive label used to identify the SNE in the Site Management Portal UI and SCT.
Figure 3. SNE Focus Tab - Advanced Edit Mode

Depending on the DNS server configuration, the SNE should be reachable from the subnet on which the SNE resides or from other subnets.