LAN-520 AESP - Full Installation Guide

LAN-520 AESP - Full Installation Guide


1.0 Introduction


The following are basic setup steps for the LAN-520 AESP. Some settings may not apply to every application.

Note: The LAN-520 AESP is an updated version of Keri’s LAN-520X device. If you are using the new NC-485X Network Converter with the LAN-520, you must use the LAN-520 AESP module (or the existing LAN-520X module). The original NC-485 Network Converter is NOT compatible with the new LAN-520 AESP (or the existing LAN-520X module).

Note: To set up the LAN-520, you MUST have technical knowledge of general networking in a PC environment. Please have a network administrator on site to resolve any special networking issues that might occur during device programming. Network topologies and strategies will vary.


Figure 1: The LAN-520 AESP Unit


2.0 Connecting the LAN-520 to a PXL-500 Controller
  1. Power down the PXL-500 Primary controller (controller addressed as #1).
  2. On the Primary controller remove jumpers from JP6 and JP7.
  3. Insert the LAN-520 AESP into the TB13 port of the PXL-500. Orient the unit as shown in figure 2.

    Note: Mounting screws are supplied to secure the LAN-520 AESP to the PXL. The PXL will have to be removed from its enclosure to do this.


    Figure 2 - LAN-520 Anchoring to PXL PCB

  4. Connect the RJ-45 port on the LAN-520 AESP to the network via a patch cable, or directly to the PC using a cross-over cable.
  5. The LAN-520 should be displaying 2 x green LEDs and 1 x yellow LED.

               

  6. Power-up the PXL-500 (if this is a new PXL controller or it was from a Doors32 system and will now be used with Doors.NET, a ram reset is required).


Figure 3: Installing the LAN-520 AESP on a PXL-500 Controller

3.0 Installing the LAN-520 to an EntraGuard Controller

Support for the LAN unit on Entraguard begins with PCB 23217-001 Rev. E. Earlier units cannot support a LAN unit.

1. Power down the Entraguard Primary controller.
2. On the Entraguard PCB, remove jumpers from J11, J19, and J20.
3. Insert the LAN-520X into J7 on the Entraguard. Orient the LAN unit as shown in Figure 2.
Note: Mounting screws are supplied to secure the LAN-520 to the Entraguard unit. The Entraguard PCB will have to be removed from its enclosure to do this.
4. Connect the RJ-45 port on the LAN-520 to the network or directly to the host PC via a cross-over cable.
5. Power up the Entraguard unit (if this is a new Entraguard panel, or a Primary controller from a Doors32 conversion then a RAM reset is required).


Figure 4: Installing the LAN-520 AESP on an Entraguard


4.0 Download Lantronix Device Installer

If you do not have an installation DVD you can download the device installer program from the Lantronix website:
  1. In a web browser address field, enter www.lantronix.com.
  2. From the home page, click on Products and Services >> Management Software.


    Figure 5: Device Installer Management Software Link

  3. Next Click on Utilities.
  4. Then click on Device Installer.
  5. Click on the link to 'Download the latest version of Device Installer'.
  6. Select the 1.3MB file if there WILL be an internet connection at the host PC when it is installed.
  7. Select the 123MB file if there is NOT an internet connection on the host PC. It is strong recommended that you select to download this larger file.
  8. You will need to unzip the downloaded file.
Note: The above information is correct at the time of writing. If the Lantronix website has subsequently changed, go to a search engine and enter the text: 'Lantronix Device Installer' and you should see a link to the download page.


5.0 Install Lantronix Device Installer

  1. On the host PC, navigate to the Downloads folder.
  2. Double-click the recently downloaded installation file.


    Figure 5: Run the Installer

  3. You should see a notification window informing you that .NET Framework and Device installer are both required along with their version numbers.
  4. Click 'Install' to proceed.
  5. You will not need an active internet connection as all the required components are included in the executable file.
  6. Place a check mark to install Device Installer and the required version of .NET Framework.


    Figure 6: Select the components to install

  7. Click the install button and, if required, the .NET Framework 4 Client Profile will install.
  8. Click Finish once installation is complete.
  9. The Lantronix Device Installer Setup Wizard will then start automatically.
  10. Click Next on the Welcome page.
  11. The Installation Folder page displays the default location where the program will be installed. You can click Browse to locate and select a different location.
  12. Click Next, then Next again to start installing Device Installer. Installation of this program should take no longer than a minute.
  13. Once installation is complete you can locate the application via; Start >> All Programs >> Lantronix >> Device Installer 4.4 >> Device Installer.
  14. Right-click the Device Installer application file and select Send to – Desktop (create shortcut).

6.0 Run Lantronix Device Installer

Note: You should contact your IT administrator if the LAN-520 AESP device is being installed on a different subnet to the host PC.
  1. The Device Installer icon will be found on the desktop so double-click this to open up the application.



  2. When you first open the program you may see a notification that no serial port has been detected, this is not of any concern so select ‘Do not prompt me about this’. Then click OK.
  3. Select No to the prompt to check for updates.
  4. If the LAN-520 AESP module has been connected to a DHCP router which is on the same physical subnet as the host PC then the device should appear. It should also show as online. The software searches for the device via its MAC address.
  5. The device should display along with its assigned IP address. The MAC address will begin 00-80 if it is the AESP module. The older LAN-520 modules will have a MAC address beginning 00-20.


    Figure 7: LAN-520 Displayed in Device Installer

  6. Even if you wish to use the IP address that has been assigned via DHCP, the LAN-520 AESP will still need to be assigned a static IP address (otherwise the address can still dynamically change).


7.0 Assign the LAN-520 With a Static IP Address

  1. Highlight the LAN-520 entry and click the Assign IP button.


    Figure 8: LAN-520 selected in Lantronix Device Installer

  2. The Assignment Method page defaults to ‘Assign a specific IP address’ so click Next.
  3. Enter a new static IP address or leave as is (if you are happy with the address that was assigned by DHCP). On this page you can optionally add a gateway IP address as well. A gateway address is not required if the PC running Doors32/Doors.NET is on the same subnet. Click Next again.
  4. Click the Assign button to complete the static IP address assignment.
  5. Click Finish when you see assignment has successfully completed. 

8.0 Setting a Static IP Address Using Telnet

The following steps explain how to assign the LAN-520 a static IP address using Telnet (for example; in the event that Lantronix Device Installer is not available or permitted on the host PC).

Setting up the LAN-520 AESP via a command prompt is an easy process without the need of installing any extra software. To use this method the person configuring the LAN-520 AESP must have administrative rights in order to run the required commands and Telnet must be enabled on the operating system.

Two basic commands are used in this method: ARP and Telnet.

Note: Address Resolution Protocol (ARP) is the standard method for finding a host's hardware address when only its network layer address is known. For more info on the usage of arp type ARP/? at the command prompt and press ENTER.

Information to be typed is displayed in bold.

1. Open a command prompt:
- (Enter CMD in the Windows search field).
- Press Enter.
- This will open up a Command Prompt (DOS) window.

2. At the prompt, type the following to make a Telnet connection to the LAN-520 AESP1:

arp -s <LAN-520 IP address><LAN-520 MAC address><ENTER>
    Example: C:\>arp -s 174.120.9.115 00-20-4A-24-89-67 arp –a


arp-a <ENTER>

telnet >LAN-520 IP address> 1 <ENTER>
Example: C:\>telnet 174.120.9.115 1

Note: A Telnet “Connection Failed” screen appears. This is normal.

Example: C:\>telnet 192.168.100.250 9999 <ENTER><ENTER>
(The Enter button must be pressed twice within 5 seconds).     

Note: The ARP command does not report when this command is completed successfully. However, if it has been done incorrectly, an error will occur. To verify the contents of the ARP table type arp -a and press ENTER. The MAC address should be paired with the IP address to be assigned.

The following menu appears:
Change Setup:
0 Server
1 Channel 1
2 Channel 2
5 Expert
6 Security
7 Defaults
8 Exit without save
9 Save and exit
Your choice?
Select option #7:

7 Defaults
This will set communications settings to the defaults which are the recommended channel 1 settings.

Note: This will not reset the IP or subnet settings in the unit.

0 Server
IP Address: Enter the IP address in segments then press enter.     

This will replace the numbers in parenthesis     
Example: 192.168.100.103 would be entered as:

192<ENTER>
168<ENTER>100<ENTER>103


Set Gateway: Gateway will only be needed if you intend to communicate with another subnet.
Enter “Y” then enter address if needed as done with IP ADDRESS in the prior step, otherwise type “N” and proceed to next step.

NetMask: Number of Bits for Host Part: This number is a calculation of the subnet mask.     Most common are: 255.255.255.0 = 8 & 255.255.0.0 = 16

Note: See Section 7.0 for a description of how to calculate the number of bits.

9 - (Press 9 to save and exit).


9.0 Enabling Telnet Client on Windows 10

If you try to make a telnet connection to the LAN-520 but you see the following message: ‘telnet is not recognized as an internal or external command, operable program or batch file’ then it is likely that Telnet is disabled on the operating system.

Perform the following steps to enable Telnet in Windows 10:
  1. From the Windows start menu go to Control Panel >> Programs and Features.
  2. On the left of the program list click Turn Windows Features on or off.
  3. From the Windows features list locate Telnet Client.
  4. Place a check-mark against Telnet Client.


    Figure 9: Select to Enable Telnet Client

10.0 Set a Telnet/Web Manager Password on the LAN-520

Keri systems strongly recommends setting the LAN-520 with a password (to prevent unauthorized connections to the module).
Note: The following steps require Telnet to be enabled on the host PC.
  1. Double-click the LAN-520 device listed in Lantronix Device Installer.
  2. Select the Telnet tab and then click on the CONNECT button.
  3. As soon as the Telnet sign-on screen appears, press <Enter> to go into the LAN-520X Setup mode. There is a two to three second window in which you must press <Enter> before the Telnet session automatically closes. If the Telnet session closes before you enter Setup mode (if nothing happens when you press <Enter>), simply click the button to establish the connection.
  4. Once Telnet connects with the LAN-520 all current configuration information is displayed and the cursor is placed at the “Your choice” field.
  5. Enter 0 to go into the device's server settings.
  6. Enter through the list of options until you see: 'Change Telnet/Web Manager Password'.


    Figure 10: Option to set a password on the LAN-520

  7. Enter Y for Yes, then enter.
  8. Input the password you wish to assign to the device.
Note: If you forget or lose the LAN-520 assigned password you will need to perform a factory reset on the device (see section 2.0).


11. Additional Security Settings

You can change security settings via Telnet or serial connections only, not on the Web-Manager.
  1. Perform a Telnet connection to the LAN-520.
  2. From the device main menu screen, enter the number 6 to access the device security settings.

Figure 11: LAN-520 Optional Security Settings

Note: We recommend that you set security over the dedicated network or over the serial setup. If you set parameters over the network (Telnet 9999), someone else could capture these settings.

Caution: Disabling both Telnet Setup and Port 77FE prevents users from accessing the setup menu from the network.

Disable SNMP This setting allows you to disable the SNMP protocol on the unit for security reasons.

SNMP Community Name This setting allows you to change the SNMP community name. Community name is a required field for NMS to read or write to a device. The default setting is public. The name is a string of 1 to 13 characters.

Disable Telnet Setup
Note: If you choose to disable this option, please note that disabling both Telnet Setup and Port 77FE prevents users from accessing the setup menu from the network. This setting defaults to the N (No) option. The Y (Yes) option disables access to Setup Mode by Telnet (port 9999). It only allows access locally via the web pages and the serial port of the unit.

Disable TFTP Firmware Upgrade
This setting defaults to the N (No) option. The Y (Yes) option disables the use of TFTP to perform network firmware upgrades. With this option, you can download firmware upgrades over the serial port using Device Installer’s Recover Firmware procedure. (See Serial Port Recovery Procedure on page 5-3.)

Disable Port 77FE (Hex)
Note: If you choose to disable this option, please note that disabling both Telnet Setup and Port 77FE prevents users from accessing the setup menu from the network.
Port 77FE is a setting that allows DeviceInstaller, Web-Manager, and custom programs to configure the unit remotely. You may wish to disable this capability for security purposes. The default setting is the N (No) option, which enables remote configuration. You can configure the unit by using DeviceInstaller, web pages, Telnet, or serial configuration. The Y (Yes) option disables remote configuration and web sites. Note: The Yes option disables many of the GUI tools for configuring the unit, including the embedded Web-Manager tool.


11.0 Verify Communication By Performing a Telnet Session to Port 10001

This will test the default port used by Doors32/Doors.NET to communicate to the device.

The telnet command is preferred over the ping command in testing communications because the telnet command will give a specific response from the device, whereas the ping command may give a response from a different device (if there is a duplicate IP address on the network).
  1. In a command prompt window type in, telnet [IP address] 10001 then enter.
  2. If successful a blank screen and a blinking cursor will appear. The link LED (bottom green LED) will blink on and off on the LAN-520 AESP indicating that port 10001 is open. Close the command prompt window and the link LED should stop blinking.
  3. If telnet is unable to connect, then review the settings. If the settings are correct then contact a network administrator to verify the needed ports are available. Some operating systems and hardware, such as routers and firewalls are set to block ports. Ensure these firewalls have ports 10001, 10021, and 9999, open for communication with the Doors32 or Doors.NET software.

    Note: If you are able to telnet into port 9999 in the command prompt but not to 10001, it is very likely that the ports required by Doors are blocked and will require that a Network Administrator address the issue so a successful telnet session to port 10001 may take place.

12.0 Enter the LAN-520 IP Settings into Doors.NET

This section explains the steps required to add a new PXL-500 to the system and then assign the LAN-520 AESP IP address to the controller. It assumes you already have the PXL gateway setup ready to add the new PXL controller(s).

  1. Log into Doors.NET. 
  2. Go to Setup >> Hardware Setup >> All.
  3. Click the PXL gateway and then click on the Add PXL icon.



  4. Enter a description for the new controller.
  5. Select the specific model from the drop-down list.
  6. Click Accept and the new PXL master controller will appear in the hardware tree.
  7. Next, select Communication Channels.
  8. From the ribbon bar select to add a 'Network' communication channel.
  9. Select the new channel from the hardware tree.
  10. Enable the channel via its properties on the right (set it from False to True).
  11. Enter a new description for the channel, then save.
  12. Select the new PXL from the hardware tree.
  13. Assign the new communication channel via its properties on the right.
  14. Once you have selected the network communication channel you will be able to enter the IP address (the IP address which has been set to the LAN-520 AESP).



  15. Save your controller settings and within a few seconds the new controller should come online. You will see online events displayed in the live events grid.




    • Related Articles

    • LAN-520 - Quick Start Guide

         1.0 Introduction The following steps explain how to setup a PXL-500 in the Doors.NET software using a LAN-520 module. It assumes you have worked through the steps to install and license the Doors.NET software and that you have also setup the PXL ...
    • LAN-520 and NC-485 Network Converter Setup Guide

      1.0 Introduction The NC-485X offers you more flexibility in managing multiple, remote, physical sites and enhanced networking capability. By using the LAN-520X in combination with an NC-485X Network Converter, PXL-500 controllers, which are normally ...
    • What to do if Your LAN-520 Gets Hacked

      1.0 Introduction If the LAN-520 channel 1 port # has been changed to 1234 then this is highly indicative that the device has been hacked. The default value for the port number is 10001. This is the number that identifies the channel for remote ...
    • Troubleshooting LAN-520

      LAN-520 Troubleshooting 1.0 Cannot Connect to the PXL Network - Check the LAN-520 IP address and port number is correct in the Doors.NET software. The IP address should match the address which has been programmed in the LAN-520.     - By default, the ...
    • Verify Communication By Performing a Telnet Session to Port 10001

      This will test the default port used by Doors32/Doors.NET to communicate to the device. The telnet command is preferred over the ping command in testing communications because the telnet command will give a specific response from the device, whereas ...