Refer to the QuickLIT website for the most up-to-date version of this document.

(1)

NAE Commissioning Guide

Code No. LIT-1201519 MS-NAE35xx-x, MS-NAE45xx-x, MS-NAE55xx-x, MS-NIE55xx-x,

MS-NCE25xx-x, MS-NIE8500-x, MS-NAE8500-x Software Release 8.0

Issued June 2016

Refer to theQuickLIT websitefor the most up-to-date version of this document.

Document Introduction...4

Summary of Changes...4

NAE Commissioning Overview...6

Network Automation Engines (NAEs)...6

NAE35 Models...7 NAE45 Models...7 NAE55 Models...7 NIE55 Models...7 NCE25 Models...8 NxE85 Model...8 MS/TP Communications Bus...8

Metasys Network Sites...8

NAE Commissioning...10

NAE Configuration...11

Site Management Portal User Interface...12

Ready Access Portal UI...14

Metasys Help Files...14

Browser Recommendations for Downloading the Launcher...15

System Configuration Tool...15

CCT...16

Archive Databases...16

NAE Disk Image Updates and Archive Database Upgrades...16

Site Director...16

NAE Computer Name...17

NAE Object Name...18

Basic Access Operating Mode...18

Login User Names and Passwords...18

NAE Connectivity...19

Modems and Dial-Out Features...19

Time Zone, Date, and Time Management...21

Alarms and Events...21

Serial Printer DDA (Alarm Printer)...23

Recommended Serial Printer...23

Serial Printer Installation Considerations...26

Email Notification...26

Pager Notification...27

Syslog DDA...28

Simple Network Management Protocol (SNMP) Notification...30

Initial Default NAE Configuration...31

System and User Preferences...32

Reset Device Command...32

Detailed Procedures...33

Using Launcher to Discover the NAE...33

(2)

Single Site Connection...38

Establishing a Direct Connection to an NAE...39

Preparing an NAE for an Ethernet LAN That Supports DHCP and DNS...39

Preparing an NAE for an Ethernet LAN without DHCP and without DNS Support When the NAE Uses APIPA...41

Preparing an NAE for an Ethernet LAN without DHCP and without DNS Support When the NAE Uses a Static IP Address...42

Preparing an NAE for an Ethernet LAN That Supports DHCP but Not DNS...43

Preparing an NAE for an Ethernet LAN That Supports DNS but Not DHCP...44

Enabling the Serial Printer DDA...44

Preparing the NxE85 for Serial Printing...47

Creating Audit Entries for Discarded Events...47

Accessing the Site Management Portal UI on an NAE...47

Establishing Basic NAE Parameters in the Focus Screen...48

Establishing the NAE Network Parameters...49

Establishing the NAE Direct-Connect and Modem Parameters...50

Creating Email Alarm and Event Notifications and Destinations...53

Configuring Encrypted Email...56

Configuring Encrypted Email with No Authentication Required...57

Configuring Encrypted Email with SMTP Authentication...57

Configuring Encrypted Email with POP-Before-SMTP Authentication...57

Creating Pager Alarm and Event Notifications and Destinations...59

Creating NAE SNMP Alarm Notifications and Destinations...62

Enabling Syslog Reporting...64

Setting the Time, Date, Time Zone, and Time Synchronization...66

Setting up the NAE Alarm Parameters...66

Editing the Existing Alarm Parameters...67

Creating a New Alarm...68

Changing Site Director Status of an NAE...69

Changing the Site Director with the SCT...71

Removing User Accounts from a Demoted Site Director...71

Moving the Security Database and Clearing It from the Demoted Site Director Prior to Release 6.0.71 Moving the Security Database and Clearing It from the Demoted Site Director at Release 6.0 or Later...72

Establishing a Dial-up Connection to an NAE...72

Configuring an NAE to Dial Out to an ADS/ADX/ODS...73

Printing Information from the NAE Site Management Portal UI...74

Disabling the Windows Firewall on an NAE...74

Enabling and Disabling the Warning Banner...78

Replacing an NAE...78

Troubleshooting...79

Common NAE Problems...79

Corrupted NAE Memory...79

Login Problems...80

Network Connection Related Problems...80

NAE Reset Related Problems...80

Troubleshooting Guide...81

NAE Diagnostic Tools...84

NAE LED Status Indicators...84

NAE35/NAE45 LED Startup Sequence...87

(3)

NCE25 LED Startup Sequence...88

Diagnostic Tab...88

Summary Tab...90

Troubleshooting Procedures...92

Verifying Ethernet Network Communications (Ping)...92

Pre-Boot Execution Environment (PXE)...92

Determining the NAE IP Address and Device Name for a LAN Connection...92

Determining the NAE IP Address By Using the NCT...92

Determining the NAE IP Address and Device Name By Using a Serial Port Monitor...92

Setting a Computer to be Compatible with APIPA...93

Technical Specifications...94

Appendix: Time Zone, Date, and Time Management...98

Time Zone, Date, and Time Management Introduction...98

Overview of Time Synchronization...98

ADS/ADX/ODS Site Director with Network Engines...98

NIE and Child Devices...99

Time Synchronization Methods...99

Windows Time Synchronization...99

Multicast Time Synchronization...100

BACnet Time Synchronization...100

Example Network...100

Multiple Time Zones...101

Site Time Server...101

Time in Device Object and User Interface Status Bar...102

Steps for Successful Time Management...102

Verifying the Site Director Defined for an Engine/Server...103

Setting the Time Synchronization Method...103

Network Engine Is the Site Director...104

ADS/ADX/ODS Is the Site Director...107

Configuring Additional Multicast Time Synchronization Settings...110

Appendix: Configuring and Maintaining Preferences...112

Configuring and Maintaining Preferences Introduction...112

Preferences Concepts...112

System and User Preferences...112

Managing Preferences...114

Detailed Procedures...115

Configuring Preferences...115

Restoring Default System Preferences...115

Copying Preferences between Devices...115

Restoring Default User Preferences...115

Removing User Preference Files...116

Copying User Preferences to Another User...116

(4)

Document Introduction

This document describes how to:

• commission a Network Automation Engine (NAE)Network Integration Engine (NIE), or Network Control Engine (NCE) for network connectivity in several network scenarios

• access the Metasys®system Site Management Portal UI on an NAE • configure the basic NAE parameters for initial operation on the network • troubleshoot an NAE

• configure the NAE Destination Delivery Agents (DDAs) for sending alarm and event messages via email, pager, and Simple Network Management Protocol (SNMP)

• configure a Syslog DDA for sending events and audits to an external Syslog server

• disable the Windows firewall on an NCE25, NAE35, or NAE45 for the purpose of improving the overall performance of these network engine models

This document does not describe how to mount, wire, or power on an NAE. Also, this document does not describe how to build or download an archive database for a Metasys system site or how to configure an NAE to monitor and control a Building Automation System (BAS).

Note: In this document, NAE refers to all NCE25, NAE35, NAE45, NAE45-Lite, NAE55, NIE55, NxE85 models, unless noted otherwise. Refer to the NxE85 Commissioning Guide (LIT-12011044) for additional information specific to the NxE85 Series network engines. Refer to the NCE Technical Bulletin (LIT-12011267) for additional information specific to the NCE25 Series network control engines. Refer to the NIEx9 Commissioning Guide (LIT-12011922) for additional information specific to the NIEx9 Series network control engines.

Summary of Changes

The following information is new or revised:

• Added information about how to configure the NAE to send events and audits to a Syslog server. For details, seeSyslog DDAandEnabling Syslog Reporting.

• Updated screen examples to reflect the new software release.

• Specified that Internet Explorer 11 is the recommended browser for downloading the Launcher application. • Added information about a log in problem that might occur if you do not reset the network engine after changing

its security database. Not all models are affected. SeeLogin Problems.

• Added steps on how to disable the Windows firewall on an NCE25, NAE35, or NAE45 for the purpose of improving the overall performance of these network engine models. SeeDisabling the Windows Firewall on an NAE.

NAE Commissioning Overview

Network Automation Engines (NAEs)

NAEs are web-enabled, Ethernet-based, supervisory controllers that connect BAS networks to IP networks and the web, and allow you to monitor and control BAS field devices from a computer using the Launcher application. You use the Launcher application to log in to the NAE. If the Launcher is not already installed on your machine, you are prompted to install it when you attempt to log in using a web browser. To install the Launcher, use either Windows Internet Explorer®version 11 or Apple®Safari®version 8.0 or 9.0. (Other web browsers may work, but are not tested or supported.) Refer to the Launcher Installation Instructions (LIT-12011783).

The NAE Series of supervisory controllers is a scalable line of appliance computers with varying network, trunk, and field device capacities to meet the requirements of different applications.

All NAEs provide scheduling, alarm and event management, trending, energy management, data exchange, dial-out capability, and password protection. NAEs are factory-loaded with a supported Microsoft®Windows®operating system and the current release of the Metasys system software.

An NAE set as a Site Director can have its Warning Banner enabled, which forces a special U.S. Department of Defense (DoD) statement to appear when operators log in to the Site Management Portal of the engine. This banner is primarily intended for United States military facilities. The banner satisfies the requirements for a mandated DoD Information Assurance Certification and Accreditation Process (DIACAP). The banner cannot be customized or its text be changed. For steps on how to enable or disable this banner, seeEnabling and Disabling the Warning Banner.

(7)

NAE35 Models

The NAE35 models:

• support one RS485 field bus or one LONWORKSnetwork trunk into a Metasys system network. The NAE351x

models integrate one N2 Bus or one BACnet®MS/TP trunk with up to 50 field controllers. The NAE352x models integrate a single LONWORKStrunk with up to 64 LONWORKSdevices.

• monitor and control up to 50 BACnet IP devices over Ethernet at the supervisory level

• serve as a Site Director supervising a maximum of two additional network engines, which can be NAE35 or NCE25 model engines only

Several NAE35 models provide the Basic Access operating mode as the primary UI. SeeBasic Access Operating Modefor more information.

NAE45 Models

The NAE45 models:

• support either one RS485 field bus or one LONWORKSnetwork trunk into a Metasys system network. The NAE451x

models integrate one N2 Bus or one BACnet MS/TP trunk with up to 100 field controllers. The NAE452x models integrate a single LONWORKStrunk with up to 127 LONWORKSdevices.

• monitor and control up to 50 BACnet IP field devices over Ethernet at the supervisory level • monitor and control up to 50 BACnet IP field devices over Ethernet at the supervisory level

• serve as a Site Director supervising a maximum of two additional network engines, which can be NAE35, NAE45, or NCE25 model engines only

Note: The NAE45-Lite supports the MS/TP bus and BACnet IP communication to third-party devices. The NAE45-Lite does not support the N2 Bus, N1 integration, VND integration, Xl5K integration, LONWORKSnetwork, or wireless

supervisor (N2).

Note: The NAE45-Lite must have an ADS-Lite-A as its Site Director, or be stand-alone. The NAE45-Lite cannot be a Site Director to other engines.

NAE55 Models

The NAE55 models:

• support up to two RS485 field buses into a Metasys system. The NAE551x models integrate two N2 Buses, two BACnet MS/TP trunks, or one N2 Bus and one BACnet MS/TP trunk. Each bus or trunk may contain up to 100 field controllers. The NAE552x models can also integrate a LONWORKSnetwork trunk with up to 255 LONWORKS

devices. NAE55 models can also monitor and supervise a number of BACnet IP devices; the total number of BACnet IP devices depends on the number of objects each device supports.

• serve as a Site Director supervising a maximum of four other network engines, which can be NAE35, NAE45, NCE25, NAE55, or NIE55 model engines

NIE55 Models

The NIE55 models:

• migrate N1 networks into a Metasys system network. NIEs do not integrate BACnet networks, N2 trunks, or LONWORKSnetworks

• serve as a Site Director supervising a maximum of four other supervisory devices, which can be NAE35, NAE45, NCE25, NAE55, or NIE55 model engines

(8)

NCE25 Models

The NCE25 models:

• support either one field bus or one LONWORKS®network trunk into a Metasys system network, specifically:

- NCE256x-x: one BACnet®MS/TP trunk with up to 32 MS/TP controllers - NCE251x-x: one N2 Bus with up to 32 N2 controllers

- NCE252x-x: one LONWORKStrunk with up to 32 LONWORKSdevices

• monitor and control up to 50 IP BACnet field devices over Ethernet at the supervisory level • provide an integral MS/TP Field Equipment Controller with 33 Input/Output (I/O) points • cannot serve as Site Director except in stand-alone applications

NxE85 Model

The NAE85 model:

• migrates large N1 networks into a Metasys network

• serves as a Site Director supervising a maximum of four other supervisory devices, which can be NAE35, NAE45, NCE25, NAE55, NIE55, or NxE85 model engines

Refer to the NxE85 Commissioning Guide (LIT-12011044) for additional information specific to the NxE85 Series network engines.

MS/TP Communications Bus

The MS/TP bus is a local or remote network that connects supervisory controllers and field controllers to point interfaces using BACnet MS/TP protocol. The remote network, called the Remote Field Bus, requires the addition of a BACnet/IP to BACnet MS/TP Router. The MS/TP bus consists of two types of buses: the Field Controller (FC) Bus or the Sensor/Actuator (SA) Bus. Each bus has its own set of device addresses. For details on how to apply the local and remote MS/TP bus, refer to the MS/TP Communications Bus Technical Bulletin (LIT-12011034).

Metasys Network Sites

A remote services connection allows you to connect your Metasys site to cloud-based applications.Figure 2and Figure 3show how a cloud-based application is incorporated into the Metasys network. For more information on how to connect to cloud-based applications, refer to Remote Services Connection in the Metasys®SMP Help (LIT-1201793) or the Metasys®SCT Help (LIT-12011964).

A small Metasys network site comprises a single NAE or multiple NAEs with one of the NAEs designated as the Site Director (Figure 2). SeeSite Directorfor additional information on Site Director hierarchy and the number of network engines a Site Director can supervise.

(9)

Figure 2: Metasys Network with NAE55 as Site Director for Multiple NAEs

Larger Metasys network sites can comprise multiple NAEs and one or more Application and Data Servers (ADSs) or Extended Application and Data Servers (ADXs) with access to multiple remote sites. On any site with one or more ADSs/ADXs, an ADS/ADX is designated as the Site Director.Figure 3 shows an example of a simple Metasys network with multiple NAEs and an ADS as the Site Director.

(10)

Figure 3: Metasys Network with ADS as Site Director for Multiple NAEs

NAE Commissioning

NAE commissioning includes preparing the NAE for connectivity, connecting to the NAE, adding the NAE to the profile list in Launcher, and accessing and logging in to the Site Management Portal UI.

Each Metasys network installation, commissioning, and configuration scenario is unique. In some scenarios, the NAEs (on a Metasys network) may be commissioned and configured before they are installed and connected to the network; in other scenarios, the NAEs are mounted and wired to the network before they are commissioned and configured.

Note: NAE installation includes locating, mounting, wiring, and powering on an NAE. SeeRelated Documentation for references to NAE installation instructions for the various NAE models.

The commissioning tasks, the task order, and the required attribute values (at commissioning) for an NAE are determined by the specific Metasys network installation, commissioning, and configuration scenario for the site. The NAE commissioning procedures presented in this document are the procedures required for most scenarios regardless of when commissioning occurs.

(11)

The first task in commissioning an NAE is to establish a connection with the NAE via the Launcher. If the Launcher is not already installed on your machine, you are prompted to install it when you attempt to log in using the web browser. The Launcher is a software application installed on each client computer that lets you access any Metasys server or supervisory engine on the building network, regardless of its software version. For details, refer to the Launcher Tool Help (LIT-12011742) and the Launcher Installation Instructions (LIT-12011783).

After a connection is established, you can then access the Site Management Portal on the NAE from the Launcher. SeeNAE Connectivityfor six typical network connection scenarios. SeeSite Management Portal User Interfaceand Accessing the Site Management Portal UI on an NAEfor more information on accessing and navigating the Site Management Portal UI.

After you have accessed the Site Management Portal UI on an NAE, you can configure the NAE: • object name and basic device parameters

• host name (Computer Name), domain name, and network parameter • direct-connect and modem parameters

• time and date management parameters • alarm and event parameters

• SNMP messages and the network management destination • modem dial-out and dial-up parameters

• Site Director status

• firewall setting (optional to NCEs, NAE35s, and NAE45s only)

After commissioning an NAE, you must configure the NAE for the specified job site.Figure 4is a flowchart that provides an overview of the sequence of steps needed to install, commission, and configure a new NAE.

NAE Configuration

NAE configuration is preparing an NAE in the Site Management Portal UI and the System Configuration Tool (SCT) to operate on a specific Metasys network site, and communicate with, monitor, and control specific BAS field devices on that site. Configuration also includes preparing the NAE to compile, generate, and communicate information about site status, alarms, events, and trends.

You can typically accomplish NAE configuration by downloading a pre-built archive database (from the SCT) that contains the device objects, object references, attribute values, logic, graphics, user information, and other references and data required for the NAE to perform its specific tasks on the network.

You can create and edit an archive database online in the Site Management Portal UI, but in almost all cases, you should create and edit the NAE archive database offline in the SCT. When you download the database, the values in the archive database overwrite the existing values on the commissioned NAE. Refer to the Metasys®SCT Help (LIT-12011964) for information on creating and downloading archive databases.

After you configure an NAE with an archive database containing user information, you can set up the email, pager, Syslog, and SNMP DDAs and create specific alarm and event notifications for delivery to specific email, pager, Syslog server, and network management destinations.

(12)

Figure 4: NAE Commissioning and Configuration Flowchart

Site Management Portal User Interface

You can view and edit NAE parameters and the parameters for associated devices in the engine's Site Management Portal UI. Access the NAE Site Management Portal UI by using the Launcher. SeeAccessing the Site Management Portal UI on an NAE.Figure 5shows an example of the Site Management Portal UI.

In the Display panel on the right side of the window is a series of tabbed screens.Table 3andTable 2describe the information that you can view and edit in each tabbed screen. The navigation panel on the left displays the navigation tree for the BAS network integrations, field devices, field points, and their associated objects that the NAE is monitoring and supervising.

(13)

Figure 5: NAE Focus Tab in Edit Mode - Advanced

Table 2: NAE Focus Tab Descriptions Description

Callout

Previous and next arrows for navigating to viewed screens

1

NAE object: Double-click or drag into display panel to view and edit NAE parameters.

2

Display panel (in Edit view)

3

Editable values: type in or select the appropriate value.

4

Viewable but non-editable values in the displayed screen.

5

Navigation panel

6

Alarm and event indicator

7

When you view the online NAE Site Management Portal UI, the border around the panels is blue (Figure 5). When you view the offline SCT UI, the border is black (Figure 6).

(14)

Table 3: Metasys Site Management Portal UI Tabbed Screens Access Online/Offline Purpose Screen Tab Designation Both Provides the description and name (label) of the device object, the local time and date, the firmware version, message buffer and alarm, and audit repository sizes. The Focus tab also identifies the local Site Director and includes general site information about the ADS/ADX to which the NAE reports (if applicable).

Focus OR Configuration

Both Establishes communication parameters, including Serial port and internal or external USB modem configuration.

Communications

Both Establishes Computer Name (host name) for network identity, LAN, and

ADS/ADX dial-up parameters (if applicable).

Network

Both Establishes the NAE email alarm-notifications features common to all email messages and create unique email message destinations.

Email

Both Establishes the NAE pager alarm-notifications features common to all pager messages and create unique pager message destinations.

Pager

Both Establishes the NAE Simple Network Management Protocol (SNMP) features common to all SNMP notifications and create unique SNMP message destinations.

SNMP

Both Provides the NAE Syslog server reporting destination information.

Syslog

Both Provides the NAE alarm setup and destination information.

Alarm

Online Provides network and field device status information and attribute values for supervisory and field devices on the NAE field trunks.

Summary

Online Provides various status reports to aid in troubleshooting the NAE.

Diagnostic

Online Monitors and records the changes in the behavior of an NAE over time,

assisting with diagnosing various system-wide behavioral characteristics.

Trend

Menus, tab screens, attribute lists, values, and units of measure in the Site Management Portal UI are dynamic and change in the displayed screen according to the item you select from the navigation tree. Refer to the Object and Feature Tabs section in the Metasys SMP Help for descriptions of menu items.

Ready Access Portal UI

In addition to the Site Management Portal UI, an alternative, optional interface called the Ready Access Portal UI is also available. This software, which comes with the ADS/ADX software, is targeted to users who access only specific key functions of the Metasys system and perform typical tasks through a more intuitive navigation process. Available via a computer or handheld platform, the Ready Access Portal UI requires only a web browser. For more details, refer to the Ready Access Portal Catalog Page (LIT-1900538).

Metasys Help Files

The Metasys Help files provide shared system information and individualized mode-dependent information for the Metasys Site Management Portal (SMP) or the System Configuration Tool (SCT). The Metasys®SMP Help (LIT-1201793) provides information about alarming, commanding, auditing live data values, and other online features. The Metasys®SCT Help (LIT-12011964) provides information about offline operations such as managing archives, creating spaces, simulating systems, and establishing equipment and serving relationships.

In either SMP or SCT mode, the Metasys Help menu provides Help files in PDF format. Refer to theQuickLIT website

(15)

Browser Recommendations for Downloading the Launcher

The Metasys system currently supports Windows Internet Explorer version 11 and Apple Safari versions 8.0 or 9.0 for downloading the Launcher application. Other web browsers may work, but are not tested or supported. After you install the Launcher, you use the Launcher, not the web browser, to open the Site Management Portal UI.

System Configuration Tool

The SCT is an offline software tool used to create, edit, save, and restore the various archive and security databases that are used to configure Metasys system networks, ODSs, ADSs/ADXs, NAEs, and supported field devices. The SCT UI opens in its own window and has a similar look and function to the online Site Management Portal UI (Figure 6).

The SCT allows commissioning of N2 devices by allowing HVAC PRO software, GX-Tool software, and XTM Configurator software to access the devices on the N2 Bus of an NAE, and allows commissioning of FECs, VMA16s, and Input/Output Modules (IOMs) by using the CCT software to access the devices on the field bus of an NAE. The SCT provides a Simulation feature that allows you to simulate an online supervisory device and test a database’s control logic prior to downloading it to an NAE. Using the SCT, you can view and configure multiple sites in one archive.

(16)

CCT

Use the CCT in conjunction with the Metasys system user interface to configure, simulate, and commission Field Equipment Controllers (FECs), IOMs, and VAV Modular Assembly (VMA) 16s, on an N2 network or MS/TP bus. You must install CCT on the same computer as SCT software to use the Ethernet Passthru option in SCT. For more information on CCT, refer to the Controller Tool Help (LIT-12011147).

Archive Databases

A Metasys archive database contains the configuration information for ADSs/ADXs, NAEs, BAS network integrations, field devices, and field points that make up a single site or multiple sites on a Metasys system network. Multiple archive databases, representing multiple sites, can reside on a single ADS/ADX running the SCT. The SCT navigation panel inFigure 6provides graphical representation of some of the items that may be in a Metasys archive database. An NAE archive database, which resides in the NAE internal memory, contains only the specific configuration information that makes up the network integrations, field devices, and field points that the NAE is supervising. Each NAE retains only its own archive database. You can also save the NAE database in a Metasys archive database on an ADS/ADX or another computer using the SCT. A graphical representation of some of the items contained in an NAE archive database is shown inFigure 5in the Site Management Portal UI navigation panel.

You can upload an NAE archive database to the SCT where it can be saved to a hard disk or other long-term storage media. You can also edit an NAE archive database offline in the SCT and download the edited archive database to the NAE.

NAE Disk Image Updates and Archive Database Upgrades

The NAE operating system, Metasys system software, NAE archive database, and recent NAE operation data reside on the NAE disk image.

Use the NAE/NIE Update Tool or the SCT to update the NAE disk image to the latest release version of the Metasys system software. Refer to the NAE/NIE Update Tool Help (LIT-12011524) or the Metasys®SCT Help (LIT-12011964). When you update an NAE to a new version of the Metasys system software, you must also upgrade the NAE archive database to a new release database. For an overview of the upgrade process, refer to the SCT Installation and Upgrade Instructions (LIT-12012067) or the ODS Installation and Upgrade Instructions Wizard (LIT-12011945). Note: The NAE45-0, NAE55-0, and NIE55-0 engines with 256 MB flash memory are not supported at Release 4.1

or later. For upgrade options, contact the Johnson Controls®Field Support Center.

Site Director

For each Metasys system network site, a single network engine or a Metasys server is designated as the Site Director. The Site Director UI provides a single point of access to the site and all of the web-enabled devices on the site; and supports functions such as user login, user administration, user views, time synchronization, and data traffic management.

On larger Metasys system networks with one or more ADSs, ADXs, or ODSs, an ADS, ADX, or ODS is designated as the Site Director. On small network sites without an ADS, ADX, or ODS, you must designate one of the NAEs as the Site Director.

All NAEs are shipped factory-designated as Site Directors. You must demote any NAE that is not the designated Site Director on a site. SeeChanging Site Director Status of an NAEfor more information.

Note: You can establish or change the login user name and password for the NAE only when the NAE is designated as a Site Director. Establish these values before demoting an NAE from the Site Director.

If an ADS/ADX is on a site, an NAE cannot be the Site Director. You must demote the NAE to be a child of an ADS/ADX or ODS. SeeChanging Site Director Status of an NAEfor more information.

(17)

Note: The NAE45-Lite cannot be a Site Director to other engines. The NAE45-Lite can only be a child device of an ADS-Lite-A. You must demote the NAE to be a child of an ADS/ADX or ODS. SeeChanging Site Director Status of an NAEfor more information.

If an NAE85 is the Site Director, it can supervise up to four additional engines on the site: NAE35s, NAE45s, NCE25s, NAE55s, NIE55s, or NxE85s.

If an NAE55 is the Site Director, it can supervise up to four additional engines on the site: NAE35s, NAE45s, NCE25s, NAE55s or NIE55s.

If an NAE45 is the Site Director, it can supervise up to two additional engines on the site: NAE35s, NAE45s, or NCE25s.

If an NAE35 is the Site Director, it can supervise up to two additional NAE35s or NCE25s on the site. An NCE25 cannot be designated as the Site Director, except in stand-alone applications.

Note: If you attempt to add an NAE to a site and the new NAE exceeds the supervisory device limit for the Site Director, the Site Director does not accept the additional device. The Site Director records an error message in the Site Director Audit Trail each time you attempt to add a new device that exceeds the device limit. If you attempt to add the same device more than once, each attempt fails but no error message is recorded after the first attempt.

NAE Computer Name

The NAE Computer Name is an editable Network Identification attribute on the NAE Network tab. Devices on the LAN and the Metasys system network use the NAE Computer Name to identify and communicate with the NAE across the network. Computer Name is synonymous with host name on a network.

Each NAE ships with a unique initial Computer Name value NAExxxxxxxxxxxx, where xxxxxxxxxxxx is the Ethernet MAC address of the device without the hyphens. For example, if the NAE's MAC address is 00-80-66-05-0F-FC, the initial computer name is NAE008066050FFC. Changing the Computer Name value initiates a device reset on the NAE.

The initial computer name is often useful during commissioning for locating and connecting to an NAE before it is configured with an archive database download from the SCT. In most cases, the archive database download from the SCT overwrites the initial Computer Name value and determines the NAE Computer Name on the Metasys site. Changing the NAE Computer Name breaks any existing references between the NAE object and other objects on the site and may break the existing network connection to other devices on the network.

Important: The NAE/NIE Update Tool places restrictions on the Host Name (Computer Name) values you can use for NAE35, NAE45, or NCE25 models. Name values must start with a letter, end with either a letter or a number, and may contain dashes only in the interior of the name. The Host Name must contain a letter other than or in addition to the letter A and digits. For example, A522446 is not valid, but either A522446B or AB52446 are valid. B522446 or C522446 are valid Host Names. This restriction is caused by a known problem with Microsoft Windows®CE. Failure to follow the Host Name restrictions results in the Computer Name value changing when an NAE35, NAE45, or NCE25 is updated. Refer to the NAE/NIE Update Tool Help (LIT-12011524) for more information on Host Name restrictions.

Note: Before building the archive database in SCT, you should consult the network administrator or Information Technology department to determine if there is an existing protocol for host names (computer names) on the network.

(18)

NAE Object Name

The NAE Object Name is an editable attribute on the NAE Focus tab that the Metasys software uses to identify the NAE in the Site Management Portal UI and in the SCT. The Object Name is a label only and is not (necessarily) the same as the Computer Name. Changing the Object Name merely changes the name that you see in the navigation tree, alarm messages, trend reports, and other screens in the Site Management Portal UI and SCT that refer to the NAE. Changing the Object Name does not impact the object references or network communication with other devices on the site. You can change the Object Name at any time. We recommend an intuitive name that clearly identifies the NAE in the Site Management Portal UI and Metasys site.

Basic Access Operating Mode

Basic Access is a mode of operation allowing users with Basic Access user accounts access to a subset of the standard user interface capabilities based on their assigned permissions. Basic Access user accounts are created by Metasys system administrators using the Security Administrator system. Basic Access meets the user interface requirements for most building operators. Basic Access is provided on all of the Metasys system engines and servers but is the primary user interface in the NAE3514, NAE3515, NAE3524, and NAE3525 controllers.

You cannot commission or configure an NAE35 in Basic Access mode. You must log in to the full Site Management Portal UI on the NAE35 to commission and configure the device. SeeLogin User Names and Passwordsfor information on logging in to NAE35 Basic Access.

Login User Names and Passwords

All NAEs are shipped with the same initial login user name and default password. The initial login user name is MetasysSysAgent, and it is not case sensitive. For the MetasysSysAgent default password, contact your local Johnson Controls representative.

Use the initial user name and password to log in to any NAE the first time you commission the NAE. The Change Password dialog box then appears and prompts you to change the initial default password before continuing. You must change the MetasysSysAgent default password when you first log in to a new NAE, or an NAE that was recently updated with the NAE/NIE Update Tool or SCT. The process for updating the password may take up to 60 seconds to complete.

Complex passwords are required to access the NAE, or an NAE securely on the site. Complex passwords meet the following requirements:

• The password must include a minimum of 8 characters and a maximum of 50 characters.

• The password cannot include spaces or include a word or phrase that is in the Blocked Words list. • The password and the user name cannot share the same three consecutive characters.

• The password must meet the four following conditions: - Include at least one number (0–9)

- Include at least one special character (-, ., @, #, !, ?, $, %)

Note: Only the special characters listed above can be used; all other special characters are invalid. - Include at least one uppercase character

- Include at least one lowercase character

Note: The NAE login user name and password values can only be changed when an NAE is a Site Director. If you want to change the NAE login user name or password, you must do so before demoting the NAE from Site Director status.

The NAE35 models with Basic Access operation mode require an additional login user name and password to enable and use the Basic Access mode. The initial login user name is BasicSysAgent, and it is not case sensitive. You are prompted to create your own account password.

(19)

Note: When you change (or add) an NAE login user name or password, make sure to record the new user name and password and store them in a safe location. You cannot access the NAE Site Management Portal UI without a valid user name and password. Refer to the Security Administrator System Technical Bulletin (LIT-1201528) for details.

NAE Connectivity

You can establish a connection between a computer and an NAE using one of the following procedures: • Establishing a Direct Connection to an NAE

• Preparing an NAE for an Ethernet LAN That Supports DHCP and DNS

• Preparing an NAE for an Ethernet LAN without DHCP and without DNS Support When the NAE Uses APIPA • Preparing an NAE for an Ethernet LAN without DHCP and without DNS Support When the NAE Uses a Static

IP Address

• Preparing an NAE for an Ethernet LAN That Supports DNS but Not DHCP

Modems and Dial-Out Features

You can set up an NAE with a modem to dial out to an ADS/ADX from a remote location or to be accessible from a computer remotely. Some NAE models include an optional, factory-installed, internal modem. You can also install a user-supplied external modem on the NAE. SeeTable 4for a list of supported modem combinations for the NxE models. For example, an NAE55 with an internal modem can have an external USB modem, but not an external serial modem.

Table 4: Supported Modem Combinations

External Serial Modem Supported?

External USB Modem Supported?

Internal Modem Present? NxE Model No Yes Yes NAE55/NIE55 No Yes No No Yes Yes NAE35/NAE45/NCE25

Yes - RS232C Port B Only Yes

No

1 Only one external modem is supported per NAE: USB or Serial. 2 The RS232C A serial port does not support an external modem.

Note: The optional factory-installed, internal modem cannot be added to an NAE in the field.

Each NAE is pre-loaded with the modem drivers for the following (optional and user-supplied) supported external USB modems:

• Zoom Telephonics, 2985-00-00L modem, V.90 external USB modem • Multi-Tech Systems, MT5634ZBA - USB 56K, V.90 external USB modem

• U.S. Robotics®USR5637 modem, 56K, external USB modem (requires 4.1.5 image or later) • Radicom Research V92HU-E2 external USB modem

The Multi-Tech®modem in Metasys system networks requires the 8.27L Version or higher of the Multi-Tech Systems modem firmware installed on the modem.

The Zoom®and Multi-Tech models specified here are discontinued and are no longer available from Johnson Controls, but may be obtained from other vendors.

The USRobotics USR5637 modem requires firmware version 1.1.0. Dial-out problems occur if you update the firmware with a newer version. To obtain firmware version 1.1.0 for this modem, search for Article 33356 on the Field Support Center Solutions Database (http://support.controls.johnsoncontrols.com/kb), or contact your local Johnson Controls field representative.

(20)

By default, the NAE is not set up to accept incoming dial-up connections via a modem. To enable modem connections, access the NAE Site Management Portal UI, go to the Communication tab, and set the Allow Incoming Connections attribute value in the Internal Modem Config or External Modem Config sections to True.

Modems used for Metasys system DDAs must be dedicated for the DDA. For example, a conflict exists if the Launcher application attempts to use the same modem that is configured for a Pager DDA. To help you understand supported uses of internal and external modems, seeTable 5. For example, an internal modem can be shared for ADS/ADX dial-out (alarm, event, and audit forwarding) and incoming connection (Launcher) functions, whereas the external modem is dedicated to the paging function. Also, if you use the same modem for the ADS/ADX dial-out and Launcher functions, you may need to increase the number of redial attempts and time between redial attempts for that modem. Table 5: Supported Modem Communication Uses

Paging Dial In Dial Out External Internal Internal Type of Modem Internal External External

With the presence of two modems, the NAE is capable of communicating over an incoming modem connection and an outgoing modem connection simultaneously. The supported modem configuration scenarios are summarized in Table 6. As an example, the NAE’s internal modem can handle communications to an ADS/ADX and accept incoming connections, while its external modem can send out pages. An example of an unsupported combination is for the same modem (internal or external) to handle all three communication types: dial-out, dial-in, and paging.Table 7 lists the unsupported modem scenarios.

Table 6: Supported Modem Configuration Scenarios for NAE

Paging Dial In

Dial Out

Modem enabled Use external modem Modem enabled

Use internal modem

Modem enabled Use internal modem

Modem enabled Use internal modem Modem enabled

Use external modem

Modem enabled Use external modem

Modem disabled No modem in use Modem enabled or disabled

Use internal or external modem

Modem enabled or disabled Use internal or external modem

Modem enabled

Use internal or external modem Modem disabled

No modem in use

Modem disabled No modem in use

Table 7: Unsupported Modem Configuration Scenarios for NAE

Paging Dial In Dial Out Modem enabled Internal modem Modem enabled Internal modem Modem enabled Internal modem Modem enabled External modem Modem enabled External modem Modem enabled External modem Modem enabled Internal modem Modem enabled Internal modem Modem disabled No modem in use Modem enabled External modem Modem enabled External modem Modem disabled No modem in use

(21)

Table 7: Unsupported Modem Configuration Scenarios for NAE Paging Dial In Dial Out Modem enabled Internal modem Modem disabled No modem in use Modem enabled Internal modem Modem enabled External modem Modem disabled No modem in use Modem enabled External modem

Time Zone, Date, and Time Management

The procedure you use to set the time zone, date, and time on an NAE depends on how the NAE fits into the Metasys site hierarchy. SeeAppendix: Time Zone, Date, and Time Managementfor information and detailed procedures for setting time zone, date, and time on an NAE and on a Metasys network.

Alarms and Events

Each NAE stores alarm and event messages generated by the NAE and the connected field trunk devices. You can configure an NAE to send alarm and event notifications via the NAE DDAs to email destinations, paging devices, and SNMP devices.

DDAs are agents that route and deliver alarm and event messages to destinations such as pagers, printers, email addresses, Syslog servers, and SNMP management systems.

If the site has an ADS/ADX or ODS, each NAE can forward alarm and event information to the ADS/ADX or ODS for centralized notification and long-term storage.

Important: If the site depends on alarm paging, printing, or emailing alarms, the Metasys system manages the NAE repositories according to the following criteria to avoid a loss of notification if the repository becomes full:

• Events forwarded to an ADS or ODS Event Repository are always removed before events that are not forwarded.

• The lowest priority event with the oldest time stamp and Acknowledge Required flag set to false is replaced first.

• If the event about to be created is of a higher priority than at least one event in the repository, the event with the oldest time stamp and the lowest priority is replaced.

• If all events are of the same priority, the event with the oldest time stamp is replaced.

• If the event about to be created is of a lower priority than all other events in the Event Repository, no event is replaced and the new event is discarded.

A loss of alarm paging, printing, or emailing can result if the NAE is not commissioned with strict adherence to these criteria. To avoid managing events in this way, move ADS/ADX and the notification DDAs to the server.

You can designate multiple alarm and event sources in an NAE and in the connected field devices, and then configure the conditions that trigger those alarms or events. You can also define multiple notification types and multiple notification destinations for each alarm or event.

The NAE also has several pre-configured internal diagnostic features that are factory set to generate alarms. NAE device diagnostic features with factory-set default alarm values include:

• usage • flash usage • memory usage • battery condition

(22)

• CPU temperature (NAE55/NIE55 models only) • board temperature

You can check the status of these diagnostic features on the Diagnostic tab.

Refer to the Introduction to Alarm and Event Management in the Metasys SMP system Help for more information. Note: After an alarm is generated, anyone who acknowledges the alarm clears that alarm notification for all other

users. If an ADS/ADX or ODS is the Site Director, you can set the ADS/ADX or ODS to deliver alarm and event notifications to a network printer.

(23)

Serial Printer DDA (Alarm Printer)

Alarms from supervisory devices can be sent automatically to an alarm printer if one is configured and online. Alarms can be sent to an NAE55/NIE55 and NxE85. The Serial DDA must be enabled on the Site Director NAE/NIE that is connected to the serial printer and all NAEs/NIEs from which you want alarms printed. You can print alarms from all NAEs/NIEs using the serial printer connected to the Site Director (Figure 7). You can also print alarms to a local printer connected to a single NAE/NIE.

Important: Alarms are sent directly to the printer and are not queued or stored by the supervisory device. Alarms sent to an alarm printer that is offline, turned off, or out of paper are not printed and cannot be recovered. Figure 7andFigure 9show the possible printer connections to a Site Director NAE/NIE.

Recommended Serial Printer

Table 8describes the recommended serial printer and accessories. Table 8: Recommended Serial Printer and Accessories

ITAS Number Description

Item

C11C524001 Epson®FX890 9-pin, 680 cps printer

Serial Printer

C12C824431 Serial Card for Epson Dot Matrix printer

Serial Card

F2J044-06 Serial Null Modem Printer Cable

Serial Printer Cable

Table 9shows the recommended settings for the serial card. Table 9: Serial Card Setup

Description Position Switch Switch 1 Setup Enable Card On SW1-1 8-bit word On SW1-2 parity - none Off SW1-3 parity - none Off SW1-4 9600 Baud On SW1-5 9600 Baud Off SW1-6 Switch 2 Setup 9600 Baud On SW2-1 9600 Baud On SW2-2 Xon/Xoff Off SW2-3 Xon/Xoff On SW2-4 RS232 Off SW2-5 RS232 Off SW2-6 Switch 3 Setup Buffer size Off SW3-1

SW3-2 Off Buffer full recovery

Buffer full recovery Off SW3-3 DTR + or -Off SW3-4 DSR/DCD Off SW3-5 DTR flag set Off SW3-6

Self test enable Off

SW3-7

Self test selection Off

(24)

Table 9: Serial Card Setup Description Position Switch Jumper Setup On J1A Off J1B On J2A Off J2B Off J3 Off J4

Factory set - Do not change.

J5

J6

J7

Off

J8

Figure 7shows a Metasys system with the alarm printer connected to the Site Director NAE/NIE, and alarms for NAEs/NIEs (2 and 3) are routed to the Site Director NAE/NIE (1) for printing. All alarms from the NAEs/NIEs (1, 2, and 3) print on the serial printer. The serial printer DDA must be enabled on all NAEs/NIEs (1, 2, and 3).

Figure 7: Metasys System with One Alarm Printer

Figure 8shows a Metasys system with a local alarm printer (A) connected to an NAE/NIE (3) for printing. Only alarms from this NAE (3) print on this printer. The alarms from all NAEs/NIEs (1, 2, and 3) are routed to the Site Director NAE/NIE (1), and all alarms are printed to serial printer B. The serial printer DDA must be enabled on all NAEs (1, 2, and 3).

(25)

Figure 8: Metasys System with Local Alarm Printer

Figure 9shows a Metasys system with one local Alarm Printer. The alarms from only one NAE/NIE (3) print on a serial printer (A). Only that NAE/NIE(3) has the serial printer DDA enabled. The Site Director NAE/NIE (1) and NAE/NIE (2) do not have the serial printer DDA enabled.

(26)

Serial Printer Installation Considerations

Follow these guidelines when installing a serial printer:

• You cannot install the serial printer option on an ADS/ADX or ODS computer.

• You can install the serial printer option on an NIE that has an application that is already using the COM ports if the NIE is not designated as the Site Director. For example, you can install the serial printer option on an XL5000 NIE.

• You must connect the physical connection of the serial printer to COM2.

• You can install the serial printer option on an NIE85. The NIE85 uses COM1 for the physical connection of the serial printer.

• If your site contains multiple supervisory devices from which alarms are forwarded, you must connect the physical connection of the serial printer to COM2 of the Site Director and perform the installation sequence on all supervisory devices from which alarms are forwarded.

• You must install the serial printer option when an NAE/NIE is reloaded or upgraded with the NAE/NIE Update Tool.

• You cannot filter alarms. All alarms forwarded from the device on which you install the serial printer DDA are printed.

• You cannot enable the Serial Printer DDA on an NAE35, NAE45, or NCE25.

• The NAE55/NIE55 battery must be in good condition prior to enabling the DDA (the procedure requires you to remove power from the engine).

• Before enabling the Serial Printer DDA, you must have a computer with the NxE Information and Configuration Tool (NCT) installed that has network access to each NAE/NIE on which the DDA is to be installed. If you have access to an NxE85 with a monitor and keyboard, you do not need to use NCT and may perform the procedures in this document directly on the NxE85 computer.

Important: Use care and follow instructions carefully when using NCT to access an engine or computer. Failure to follow the steps as written can render your engine or computer inoperable.

Email Notification

You can configure an NAE to generate alarm and event messages by sending email to one or more email destinations using the email DDA. The steps require you to configure custom email messages and specify email message destinations in the Email tab of the Site Management Portal UI. The following figure provides an example of an email message destination that is active Monday through Friday from 7:00 A.M. to 4:00 P.M.

(27)

Figure 10: Example of Defining an Email Notification

Pager Notification

You can configure an NAE to generate alarm and event messages using Telelocator Alphanumeric Protocol (TAP) to one or more pager destinations using the pager DDA. The steps require you to configure custom pager messages and specify the pager message destinations in the Pager tab of the Site Management Portal UI. (TAP is an

ASCII-based protocol that allows the submission of a numeric or alphanumeric message).

The following figure provides an example of how to define a set of pager destinations that can route a fire alarm to the same pager over the weekend (4:00 P.M. Friday to 7:00 A.M. Monday). Note that this application requires the definition of three separate pager destinations.

(28)

Figure 11: Examples of Defining a Pager Notification

Syslog DDA

An NAE configured as a Site Director has the optional capability of sending its configured audit log entries and alarm notifications to the central repository of an external, industry-standard, Syslog server, conforming to Internet published RFC 3164. After you save the Syslog DDA configuration, all messages that are sent to the local ADS Repository are also sent immediately to the configured Syslog server. You can then open a user interface at the Syslog server and use the provided filters to interrogate or apply forensic analysis on these messages. To assist in reading the log, a vertical bar symbol (|) separates individual fields of each Metasys message and a single character dash (-) replaces any blank field.

By default, the Syslog option is disabled. Changing the Syslog Reporting Enabled attribute to True on the Syslog window enables the Syslog function. The prerequisities to the Syslog DDA are as follows:

• The Syslog server must be installed and running on a computer server or virtual machine that is reachable by the NAE.

• The NAE must be running Release 8.0 software or later. • No more than three Syslog destinations can be specified. • The firewall port must be open.

The definition of the Syslog DDA requires: • label to identify the Syslog server • IP address of the Syslog server

• port numbers for the UDP send port and UDP receive port (for example, 514 for both)

• event and audit filters to apply against all events and audit messages. Only those events and audit messages that match the filters are passed to the Syslog server.

(29)

The Syslog DDA attribute called Syslog Reporting Enabled appears on the Shared Configuration section of the Syslog tab of an NAE device object (Figure 12). This attribute has two selections: True or False.

When the Syslog Reporting Enabled attribute is set to True, the feature is active and your Metasys messages (events and audits) are forwarded to your destination Syslog server according to the filtering you specified. When the Syslog Reporting Enabled attribute is set to False, the feature is inactive and no Metasys messages are forwarded to the Syslog server. The configuration example inFigure 12is set to route to the Syslog server all High Warning alarms that require acknowledgment.

The Syslog DDA implementation is UDP, not TCP. Therefore, any audits/events generated while the Syslog server is offline are not recorded at the Syslog server, even though the Metasys system, unable to determine the current status of the Syslog server, continues to send out messages. A gap in time is present between events when the Syslog server comes back online.

Figure 12: Syslog Tab in Engine's Device Object

Figure 13shows an example of Metasys system messages as they appear on the Kiwi Syslog Server Console user interface. Use the console to filter the messages. If you do not have a tool, open a web browser and type the following URL:

http://<IP of the server>>:<Port>/Events.aspx For example:

(30)

When you browse to this site, type a valid username and password when prompted to gain access to the Syslog server. A user interface appears with the captured messages.

Figure 13: Syslog User Interface

If you run into any trouble while implementing the Syslog DDA functionality, consult this following table. Table 10: Syslog Server Troubleshooting

Behavior Scenario

All generated audits and events are cached and sent to Syslog DDA once it is started. The maximum size of the cache is 1000 audits and 1000 events per hour.

The engine is starting up but the SysLog DDA has not yet started.

All generated audits and events that the engine sends to the Syslog server are lost; nothing is cached.

The Syslog server crashes.

All generated audits and events that the engine sends to the Syslog server are lost; nothing is cached. No data is sent to the Syslog server until it comes back online or becomes reachable.

The Syslog server goes offline or is unreachable.

All generated audits and events that the engine sends to the Syslog server are lost; nothing is cached. No data is sent to the Syslog server until you correct the invalid parameters in the Syslog DDA.

The IP address, name, or port numbers of the Syslog server as defined in the engine's object are invalid.

All generated audits and events that the engine sends to the Syslog server are lost; nothing is cached. No data is sent to the Syslog server until you specify the parameters that the Syslog DDA requires.

The Syslog Reporting Enabled parameter is set to True, but no Syslog parameters are defined.

All generated audits and events that the engine sends to the Syslog server are lost; nothing is cached. No data is sent to the Syslog server until the ports on the Syslog server are opened.

The UDP Send Port or UDP Receive Port is blocked by a firewall.

All generated audits and events that the engine sends to the Syslog server are lost; nothing is cached. No data is received at the Syslog server until you correct the invalid parameters in the Syslog DDA.

A parameter of the Syslog server changes, but the corresponding parameter in the Syslog DDA of the engine is not likewise changed.

Simple Network Management Protocol (SNMP) Notification

SNMP is a protocol governing network management and the monitoring of network devices and their functions. It is not necessarily limited to TCP/IP networks. SNMP monitoring is typically used for large BAS networks with many network devices. Alarm and event notifications are sent to and stored on an SNMP management computer that monitors all devices on the network.

The NAE uses SNMP protocol to deliver network device status and conditions to a designated SNMP management computer. You must set up SNMP monitoring at the network level, and you must assign an SNMP management device on the network. (For details, seeCreating NAE SNMP Alarm Notifications and Destinations.) If you are applying a Metasys system to an existing network, consult with the network administrator or IT department that administers the network to determine if SNMP monitoring is available on the network.

(31)

Configure custom SNMP messages and specify the SNMP message destinations in the SNMP tab of the Site Management Portal UI. Perform this configuration to each NAE individually; SNMP configuration cannot be done on an ADS/ADX.

Release 3.0 and later provides enhanced SNMP functionality on Metasys systems, including a Metasys system Management Information Base (MIB) file for configuring third-party SNMP translation applications to request, receive, and translate specified SNMP trap messages generated by the Metasys SNMP DDA.

Initial Default NAE Configuration

NAEs are shipped with standard initial values for many of the editable attributes. The following table lists some important initial default configuration values for the NAE35, NAE45, and NCE25 models.Table 12andTable 13 define some important initial default configuration values for the NAE55/NIE55 and NxE85 models.

Table 11: NAE35, NAE45, and NCE25 Initial Configuration Values

NAE35, NAE45, and NCE25 Initial Value Attribute/Field Name

NAExxxxxxxxxxxx or NCExxxxxxxxxxxx, where xxxxxxxxxxxx is the Ethernet MAC address of the device without hyphens. For example, if the Ethernet MAC address is 00-80-66-05-0F-FC, the initial Computer Name is NAE08066050FFC.

Computer Name

Enabled

DHCP Client

Enabled. It can be optionally disabled to increase system performance. SeeDisabling the Windows Firewall on an NAE.

Windows Firewall

115,200 baud, 8 bits, no parity, 1 stop bit (115200,8,n,1), Direct Connect IP over Point-to-Point (PTP).

Serial Port RS232C A

115,200 baud, 8 bits, no parity, 1 stop bit (115200,8,n,1)

Serial Port RS232C B

A new NAE35/NAE45 is a Site Director by default. If an NAE is not going to be the Site Director, it must be demoted and the Computer Name or IP address of the designated Site Director must be entered here.

Note: An NCE25 should not be designated as a Site Director except in stand-alone applications.

Site Director

MetasysSysAgent (not case sensitive)

Initial Login Username

Contact your local Johnson Controls representative.

Initial Login Password

1 This information does not apply to the NAE45-Lite.

Table 12: NAE55/NIE55 Initial Configuration Values

NAE55/NIE55 Initial Value Attribute/Field Name

NAExxxxxxxxxxxx, where xxxxxxxxxxxx is the Ethernet MAC address of the device without the hyphens. For example, if the Ethernet MAC address is

00-80-66-05-0F-FC, the initial Computer Name is NAE008066050FFC for NAE55s, NIE55s, or NIE59s.

Computer Name

Enabled

DHCP Client

Enabled. It should not be disabled.

Windows Firewall

115,200 baud, 8 bits, no parity, 1 stop bit (115200,8,n,1), Direct Connect IP over Point-to-Point (PTP).

Serial Port A

9600 baud, 8 bits, no parity, 1 stop bit (9600,8,n,1)

Serial Port B

A new NAE55/NIE55 is a Site Director by default. If an NAE is not a Site Director, it must be demoted and the Computer Name or IP address of the designated Site Director is entered here.

Site Director

MetasysSysAgent (not case-sensitive)

(32)

Table 12: NAE55/NIE55 Initial Configuration Values

NAE55/NIE55 Initial Value Attribute/Field Name

Initial Windows Login ID

Initial Windows Password

1 The Windows operating system login ID and password are used with dial-up and direct connections.

Table 13: NxE85 Initial Configuration Values

NxE85 Initial Value Attribute/Field Name

NAExxxxxxxxxxxx, where xxxxxxxxxxxx is the Ethernet MAC address of the enabled Ethernet card without the hyphens. For example, if the Ethernet MAC address is 00-1E-EC-6E-5D-32, the initial Computer Name is NAE001EEC6E5D32.

Computer Name

Enabled

When you commission an NxE85 for an Ethernet LAN that supports Dynamic Host Configuration Protocol (DHCP) and Domain Name Server (DNS), we recommend that you configure a DHCP reservation for the NxE85 to ensure it always receives the same IP address when its lease expires. This practice prevents address bindings between the NxE85 and other devices from breaking.

DHCP Client

A new NxE85 is shipped as a Site Director. If you do not want the NxE85 to be the Site Director, you must demote it by entering the ComputerName or IP address of the designated Site Director in the Site Director attribute field on the Advanced Focus tab of the NxE85.

Site Director

Initial Login Password

Initial Windows Login ID

Initial Windows Password

1 The Windows operating system (OS) has two administrator level user accounts. For security reasons, we strongly recommend changing the Windows OS login password for both accounts when you commission the engine. You can disable the administrator account, but do not disable the MetasysSysAgent account.

System and User Preferences

The Metasys system provides customized preferences for the Site Management Portal UI. The preferences allow you to configure how the UI behaves, including the sounds and colors, the startup view, and the ability to add links to external applications that can be accessed from within the UI of the NAE device. SeeAppendix: Configuring and Maintaining Preferencesfor information and detailed procedures on how to customize system and user preferences.

Reset Device Command

The NAE Reset Device command in the Site Management Portal UI initiates an orderly reset that saves recent changes to the NAE archive database and restarts the NAE operating system. When the NAE requires a reset, the title bar of the object in the Display panel displays Reset Needed. A reset is required for new settings to take effect after making changes to the following attributes:

• APDU Retries

• APDU Segment Time-Out • APDU Time-Out

• BACnet IP Port • Computer Name • Contact Person

Refer to the QuickLIT website for the most up-to-date version of this document.

NAE Commissioning Guide

Document Introduction...4

Summary of Changes...4

Related Documentation...4

NAE Commissioning Overview...6

Detailed Procedures...33

Troubleshooting...79

Technical Specifications...94

Appendix: Time Zone, Date, and Time Management...98

Appendix: Configuring and Maintaining Preferences...112

Document Introduction

Summary of Changes

Related Documentation

NAE Commissioning Overview

Network Automation Engines (NAEs)

NAE35 Models

NAE45 Models

NAE55 Models

NIE55 Models

NCE25 Models

NxE85 Model

MS/TP Communications Bus

Metasys Network Sites

NAE Commissioning

NAE Configuration

Site Management Portal User Interface

Ready Access Portal UI

Metasys Help Files

Browser Recommendations for Downloading the Launcher

System Configuration Tool

CCT

Archive Databases

NAE Disk Image Updates and Archive Database Upgrades

Site Director

NAE Computer Name

NAE Object Name

Basic Access Operating Mode

Login User Names and Passwords

NAE Connectivity

Modems and Dial-Out Features

Time Zone, Date, and Time Management

Alarms and Events

Serial Printer DDA (Alarm Printer)

Recommended Serial Printer

Serial Printer Installation Considerations

Email Notification

Pager Notification

Syslog DDA

Simple Network Management Protocol (SNMP) Notification

Initial Default NAE Configuration

System and User Preferences

Reset Device Command