Preparing NAE for a network that supports DHCP and DNS - Metasys - LIT-1201519 - MS-NAE35xx-2 - MS-NAE45xx-2 - MS-NAE5510-2U - MS-NAE5510-3U - MS-NAE551S-2 - MS-NAE55xx-3 - MS-NCE25xx-0 - MS-NXE85SW-x - Supervisory Device - NAE35 Network Automation Engine - NAE45 Network Automation Engine - NAE55 Network Automation Engine - NAE85 Network Automation Engine - NCE25 Network Control Engine - 11.0

NAE Commissioning Guide

Brand
Metasys
Product name
NAE35 Network Automation Engine
NAE45 Network Automation Engine
NAE55 Network Automation Engine
NAE85 Network Automation Engine
NCE25 Network Control Engine
Document type
Commissioning Guide
Document number
LIT-1201519
Version
11.0
Revision date
2022-02-09
Language
English

The following scenario is typical when you install an NAE 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 NAE to ensure it always receives the same IP address when its lease expires. This practice prevents address bindings between the NAE and other devices from breaking.
  1. Verify that your network administrator has updated the DNS server and the DHCP server with the NAE Ethernet MAC address and the NAE host name.
  2. With your computer or commissioning laptop connected to the building network, start NCT. This tool listens for and shows the IP address information of the NAE as it comes online.
  3. Connect the NAE to the network with an Ethernet patch cable.
  4. Connect 24 VAC supply power to the NAE . Then wait for the NAE to complete the startup and initialization sequence. The NCT 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 NAE is powered on (or if the NAE Ethernet cable is disconnected and reconnected with no DHCP server online), the NAE 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 NAE (factory default).
  5. Go to Installing Launcher to access the NAE, 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 NAE, including the step for logging in to the NAE , select the NAE 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 NAE appears in the Display panel.
    Figure 1. NAE 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. Doing so does not interfere with NAE Update Tool operations. Otherwise, keep this attribute at its default value (True).
    Figure 2. NAE Network Tab - Edit Mode
    Important: The NAE Update Tool places restrictions on the host name (Computer Name) values that you can use for an NAE. Names must start with a letter or number, and must end with either a letter or a number, and may contain dashes only in the interior of the name. Refer to the NAE Update Tool Help (LIT-12011524) for more information on host name restrictions.
    Note: Changing the Computer Name forces a device reset on the NAE . (See NAE Computer name and Reset command device.)
  8. Go to the Focus tab and check the NAE Object Name. Change the Object Name to the descriptive label used to identify the NAE in the Site Management Portal UI and SCT.
Figure 3. NAE Focus Tab - Advanced Edit Mode

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