Iolan SCG Modular Hardware User Guide
Iolan SCG Modular Hardware User Guide
Guide
Preface
Audience
This guide is for the individual responsible for the installation of the Perle IOLAN SCG.
Familiarity with networking, concepts, and terminology relating to LTE, Ethernet, and LAN
(local area networks) is required.
Purpose
This guide provides the information needed to configure and manage the Perle
IOLAN SCG. This document does not cover hardware features, installation instruction
and product specifications. This information can be found in the product specific Hardware
Installation Guides.
This guide provides information about product features and guidance on configuring and
using these features. Some features may not be applicable to your model or running
software. For users of the WebManager, this guide also provides navigation reference.
For those using the Command Line Interface (CLI), a reference guide can be download
that provides detailed command information.
All guides can be downloaded from the Perle web site at [Link]
Document Conventions
This document contains the following conventions:
Most text is presented in the typeface used in this paragraph. Other typefaces are used
to help you identify certain types of information. The other typefaces are:
Note: Means reader take note: notes contain helpful suggestions.
Caution: Means reader be careful. In this situation, you might perform an action that could
result in equipment damage or loss of data.
Copyright© 2021
Perle Systems Limited.
60 Renfrew Drive
Markham, Ontario
L3R 0E1, Canada
All rights reserved. No part of this document may be reproduced or used in any form
without written permission from Perle Systems Limited.
Publishing History
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
General..................................................................................................... 11
IPv6 .......................................................................................................... 11
Management Access................................................................................ 12
Command Line ......................................................................................... 13
WebManager Access ............................................................................... 14
Logging..................................................................................................... 17
EMAIL....................................................................................................... 22
SMS.......................................................................................................... 23
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Physical Interfaces ................................................................................... 25
Virtual Interfaces ...................................................................................... 26
Interface Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
WLAN (Wireless Radio) ........................................................................... 28
Wireless Network ..................................................................................... 28
Ethernet Interface..................................................................................... 28
Cellular Interface ...................................................................................... 28
VLAN Interface ......................................................................................... 32
Bridge Interface ........................................................................................ 33
PPPoE Interface....................................................................................... 34
Tunnels Interface...................................................................................... 35
VRRP Interface ........................................................................................ 39
Serial ........................................................................................................ 42
Serial Port Services.................................................................................. 46
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Cellular Profiles ...................................................................................... 105
DNS........................................................................................................ 108
IP Host Tables........................................................................................ 110
WAN ....................................................................................................... 111
ARP Management .................................................................................. 124
Network Watchdog ................................................................................. 126
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Default Gateway..................................................................................... 128
Static Routing ......................................................................................... 128
IPv6 ........................................................................................................ 129
Port Forwarding...................................................................................... 130
NAT/ALG ................................................................................................ 131
Access Control Lists (ACLs)................................................................... 133
Prefix List................................................................................................ 135
Route Maps ............................................................................................ 136
AS-Paths ................................................................................................ 140
2
Overview
Hardware
• Please see the Hardware Information Guide for your model for a
detailed description of your hardware.
Functionality
• Console management, Device server, Bridging, Switching, Routing
• Firmware over the Air (FOTA)
IP Applications
• DDNS, DNS Proxy/Spoofing, Relay Client, Opt82
• NTP &SNTP (versions 1, 2, 3, 4)
• DHCP/DHCPv6 server & BOOTP for automated network-based setup
LAN Features
• LAN bridging and/or switching
• 802.1x
• DHCP Server, Client, and Relay
• DNS Server / Forwarding / DDNS / Caching
• STP / MSTP
• VLAN / Sub-interface
• LLDP
• Virtual Modem
• Modbus Master/Slave/Gateway
• Remote Access (PPP)
• Remote Access (SLIP)
Redundancy
• Load balancing
• VPN Failover
• Virtual Router Redundancy Protocol (VRRPv3).
• Primary/Backup host functionality
Routing Protocols
• RIP/RIPNg, OSPF / OSPFv3, BGP-4, NAT, IPv4/IPv6, Static Routing,
IPv6 Encapsulations (GRE, 6in4), Port Routing
Security Features
• AAA Security via remote authentication (RADIUS, TACACS+, LDAP)
• Trusted Host Filtering (IP filtering)
• Ability to disable services
• Ability to disable ping responses
• SSH client and server connections
• SSL/TLS client/server data encryption
• Local user database
• RIP authentication (via password or MD5)
• 2F authentication over Email or SMS
• IP address filtering
• Disable unused features
• Zone-based firewall (DMZ)
• Active Directory via LDAP
Initial Setup
Initial Configuration using the WebManager
Your IOLAN SCG is shipped in Factory Default mode. The IOLAN SCG provides a quick
Setup Mode to configure the required setup fields. You can use the WebManager or the
Command Line Interface (CLI) to perform this operation. For information on using the
Command Line Interface (CLI) to perform the initial setup, please refer to the Hardware
Installation Guide.
You can return to factory default mode at any timer by resetting the IOLAN SCG to factory
mode. (See Reset to Factory Defaults)
Once connected, fill in the required fields, apply changes to save and exit
configuration. The configuration changes are immediately applied.
The IOLAN SCG web configuration Login screen will now be displayed. Using the
credentials you previously defined in the previous steps, you can now log in and access
your units full configuration.
Search Navigation
A search tool is provided on the top of the navigation panel to facilitate finding a specific
keyword in the navigation panel.
Configuration Files
Running-config
The IOLAN operates from a version of the configuration that is loaded into
memory and is referred to as “running-config”. In addition, there is a copy of the configu-
ration file stored in flash memory in text format and used every time the IOLAN is
rebooted. This is referred to as the “startup-config” file. When making changes to the
configuration using the WebManager, it applies all changes to both the “running-config”
and the “startup-config” file when the Apply button is selected. These changes take effect
immediately and are persistent (maintained after a restart of the IOLAN).
However, when using the CLI to configure your IOLAN, configuration changes are made
immediately to the running configuration, but not to your startup-config, therefore, you
must copy the running-config to the startup-config before you reload your IOLAN or your
configuration changes are lost.
Startup-config
The “startup-config” file resides in flash memory and is used every time the IOLAN is
reloaded. When making changes to the configuration using the WebManager, it applies
all changes to both “running-config” and “startup-config” at the same time. All changes
made in WebManager take effect immediately and are persistent (maintained after a
restart of the IOLAN).The “startup-config” file is a CLI formatted text file stored in flash and
can be copied to and from the IOLAN using the CLI-based “copy” command.
===================================
User initial IOLAN configuration
===================================
ETH: Ethernet 2
DHCP Client: Enabled
• 67 (DHCP server)
• 68 (DHCP client)
• 123 (NTP)
• 161 (SNMP)
• 33815 (PerleView)
TCP (outbound)
• 443 (HTTPS)—software update check
Note: If you configure for secure web access (HTTPS), your web browser is re-directed
to a secure URL following initial setup.
Note: startup config may be different depending on the model or running software.
For detailed information on the CLI, please refer to the IOLAN SCG Expandable
Command Line Interface Reference Guide available for download from the Perle web site
at [Link]
System
Under System navigation, the General parameters are configured. Some configuration
parameters may be different on some models or running software
General
Use this section to setup General IOLAN information.
Identification
System name Provide your IOLAN with a name.
IPv6
By default the IOLAN has IPV6 and IPv4 enabled. Enabling or disabling IPv6 requires a
system reboot. The IOLAN’s factory default link local IPv6 address is based upon its MAC
Address.
For example:
For an IOLAN with a MAC Address of 00-80-D4-AB-CD-EF, the Link Local Address would
be fe80::0280:D4ff:feAB:CDEF.
The IOLAN listens for IPv6 router advertisements to obtain additional IPv6 addresses.
Auto configuration is enabled by default, however you can statically configure IPv6
addresses and network settings.
IPv6
Enable IPv6 Activate IPv6 on the next boot. Relevant
configuration screens and CLI commands are added
to the configuration screens and CLI commands.
Management Access
The parameters in this section define how management access to the IOLAN is
controlled. Protocol based access control is used to restrict access to either LAN,WAN,
or TRUSTED type interfaces. Management access is enabled by default, and the default
settling for the three roles are LAN—all protocols enabled except SNMP, WAN—all
protocols are disabled and TRUSTED—all protocols are enabled. From within each
interface configuration screen, you can set the interface role as a WAN, LAN or TRUSTED
management connection.
Management Access
Access Restriction Enable or disable access restrictions.
Default is enabled
Allow from LAN Allow management access from LAN type interfaces
over these protocols.
• HTTP—Allow non-secure Web sessions
• HTTPS—Allow secure Web sessions
• SSH—Allow SSH sessions
• TELNET—Allow Telnet sessions
• SNMP—Allow SNMP sessions
• HTTP RESTful—Allow HTTP RESTful
• HTTPS RESTful—Allow HTTPS RESTful
Default all protocols are enabled, except SNMP.
Allow from WAN Allow management access from WAN type interfaces
over these protocols.
• HTTP—Allow non-secure Web sessions
• HTTPS—Allow secure Web sessions
• SSH—Allow SSH sessions
• TELNET—Allow Telnet sessions
• SNMP—Allow SNMP sessions
Command Line
Access Command Line Access Command Line Mode using:
• Telnet—Telnet session
• SSH—SSH session
• Console—Physical console port
Console Port
Select port Select the port to be used as the console.
• auto
• none
• For “auto” if both ports are connected, the
usb device will be the console.
Terminal Terminal
Enable terminal history
Values are 0–256 buffer size
Default is 20 buffer size
WebManager Access
Use HTTP (non-secure) or HTTPS (secure) to connect to the IOLAN using WebManager
mode. If HTTPS connections are used, a certificate needs to be uploaded to the IOLAN.
If a certificate is not uploaded, the IOLAN uses a self-signed certificate. You are given a
warning by the browser indicating that the identify of the target web site could not be
verified. You must agree to accept the Perle certifiable to connect to the IOLAN in HTTPS
(secure) mode.
Note: if the protocol that is currently being used is disabled, the web session is lost after
the parameters are saved.
WebManager
WebManager Specify protocols to be supported by the
WebManager
HTTP—Allow non-secure Web sessions
Port—Port to use for HTTP sessions
Default port is 80
Values are 1025–65535
SNMP
Enable SNMP The internal SNMP server is activated.
RESTful API
Cookie Max Age Configures set-cookie based authentication.
Values 1–20160 in minutes (14 days)
Default is 1440 in minutes (24 hours)
Enable HTTP Client Requests Configures the IOLAN to accept and respond to HTTP
client request.
Values are port number 80 or enter a number from
1025–65535
Default is port 8080
Enable HTTPS Client Requests Configures the IOLAN to accept and respond to HTTP
client request.
Values are port number 443, or enter a enter from
1025–65535
Default is port 8443
JWS Key Import the key via the terminal screen. To end the
entry type ”quit” on a blank line.
JWT Claims
Audience Claim Configure the identity of the recipients that the JWT
is intended for. This tends to be the “client id” or
“client key” of the application that the JWT is
intended to be used by. It allows the client to verify
that the JWT was sent by someone who actually
knows who they are.
Expiration Time Configure the expiration time on and after the JWT
Claim(s) must not be accepted for processing.
Values are 1–3153600 seconds
Issued at Claim Configure the time the JWT will start to be accepted
for processing.
Not Before Claim/s Configure the time JWT will start to be accepted for
processing.
Values are 1–31536000 seconds
Default is 31536000 seconds
Logging
The IOLAN can log event messages to:
• its local volatile "buffered" memory log
• a file stored on theIOLAN’s non-volatile flash memory
• an external Syslog server
• telnet/SSH sessions
• the console port
Logging is enabled by default.
Logging
Enable logging Enable or disable the logging feature.
General
Include sequence number in log Whether or not to include sequence numbers in the
messages log messages.
Timestamp
Syslog
Level • Emergency
• Alert
• Critical
• Error
• Warning
• Notification (default)
• Informational
• Debugging
• UUCP
• System 9
• System 10
• System 11
• System 12
• System 13
• System 14
• Cron
• Local 0
• Local 1
• Local 2
• Local 3
• Local 4
• Local 5
• Local 6 (default)
• Local 7
Origin ID Source Add origin ID source. Select from the drop-down list.
• None
• IP
• IPv6
• Hostname
• Custom
Console
Enable logging on the Enables or disables the ability to output the log
console port messages to the console.
Telnet/SSH
Buffered
• Notification
• Informational
Debugging (default
File
EMAIL
Overview
Notifications generated by the IOLAN can be sent to one or more recipients via Email.
Setting up the Email subsystem requires setting up the Email server (SMTP) and the list of
recipients. Email is disabled by default.
Email
Enable Enables Email services.
SMTP Server Host Configures the IP Address of the SMTP host used to
send the Email.
SMTP Server Port Configures the SMTP host port number required for
the connection.
Values are 1 to 65535
Default port is 25
Email Subject Line Use the default subject line or configure your own.
Default message is “Notification event from Perle
IOLAN SCG Series Console Server
Send a TEST EMAIL message Configure a user email address, then press the TEST
EMAIL button to send a test message to the user’s
email address.
SMS
SMS Settings
Overview
This feature is dependant on having a cellular interface which includes SMS support.
The IOLAN supports SMS control and SMS two-factor authentication requests. Verify
with your cellular provider that SMS functionality has been enabled.
SMS Control
Through SMS control, a validated user, sends commands to the IOLAN and receives
requested statuses. Users are validated either using a password prefixed with every
request or by the phone number of the sending device used to generate the request or by
both. When using email for two factor authentication, some email programs require
you to set the parameter “allow less secure apps to connect” to receive SMS email
messages. If the authentication method includes a password, you need to send the SMS
For example, if the user password was 54321 and you want to get a list of valid SMS
commands, you would send the follow SMS message to the phone number of the IOLAN
54321 help
Note: SMS commands are not case sensitive and all white spaces are ignored.
The commands that are available to a user from SMS are:
SMS Commands
Help Returns a list of valid commands.
SMS Notifications
SMS notifications generated by the router can be sent to one or more recipients via SMS.
Setting up the SMS notifications subsystem requires enabling SMS and configuring a list
of users/recipients, then enabling the notifications feature for each.
Interfaces
Introduction
Interfaces are networking communication points for your computer. Each interface is
associated with a physical or virtual networking [Link] IOLAN supports a number of
different types of interfaces and each may have it own characteristics and capabilities. Not
all physical interfaces described below are available on all models and the number of
interfaces for a particular interface type may vary as well. Some configuration parameters
may also be different on some models or running software.
Physical Interfaces
Ethernet
Ethernet interfaces connect to devices, switches, or other routers. They are used as a
gateway to a LAN or to provide WAN functionality to routers.
The IOLAN SCG supports two RJ-45 Ethernet interfaces as well as 2, SFP interfaces.
The RJ-45 interfaces are capable of running at 10/100 or 1000Mbps. The SFP interfaces
support 100/1000 Mbps speeds. The RJ-45 and SFP interfaces are combo interfaces
meaning only one of the two can be active at a given time.
Cellular
The cellular interface (wlm0) connects to the cellular network. A SIM card is required for
a cellular connection. To use the LTE modem, your cellular plan must have “data”. If you
wish to make use of the ability to send or receive text messages, you need to ensure that
the plan also includes “SMS” services. The IOLAN SCG does not make use of any “voice”
services. If no cellular profile has been defined, the IOLAN SCG sets an APN based on
the SIM card detected or attempts to get one from the network. If the carrier requires a
specific APN, this is configured in a cellular profile.
• 802.11a
• 802.11b
• 802.11g
• 802.11n
Serial
Virtual Interfaces
VLAN
Each Ethernet interface can support sub-interfaces, which in turn support the transport
and segregation of VLAN traffic. For example if Ethernet 1.51 is defined, the traffic on the
sub interface is associated with and tagged as belonging to VLAN 51.
Bridge
A bridge connects several interfaces together to behave as a single Local Area Network
(LAN). All devices attached to any of the interfaces in the bridge are all part of the same
broadcast domain. They share a common IP address and subnet. You must remove the
interface from the bridge, to use the interfaces individually.
PPPoE
Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol for encapsulating
PPP frames inside. PPPoE allows Internet Service Providers (ISPs) to manage access to
accounts via user names and passwords. You can virtually “dial” from one node to another
over an Ethernet network to establish a client to server point to point connection, then
transport data packets over that connection.
Tunnels
Your IOLAN supports three types of tunnels:
• Generic Routing Encapsulation (GRE)—Generic Routing Encapsulation
(GRE) is a tunneling protocol developed by Cisco Systems that can encapsu-
late a wide variety of network layer protocols inside virtual point-to-point links or
point-to-multipoint links over an Internet Protocol network.
• OpenVPN—uses VPN techniques to secure point-to-point and site-to-site con-
[Link] OpenVPN protocol is responsible for handling client-server com-
munications. Basically, it helps establish a secure “tunnel” between the VPN
client and the VPN server. OpenVPN handles encryption and authentication. It
also, can use either UDP (User Datagram Protocol) or TCP (Transmission Con-
trol Protocol) to transmit data.
• 6in4—6in4 tunnels are configured between border routers or between a border
router and a host. The simplest deployment scenario for 6in4 tunnels is to
interconnect multiple IPv6 sites, each of which has at least one connection to a
shared IPv4 network. This IPv4 network could be the global Internet or a corpo-
rate backbone.
VRRP
Your IOLAN supports the Virtual Router Redundancy Protocol (VRRP). This networking
protocol provides for automatic assignment of available Internet Protocol (IP) routers to
participating hosts. This increases the availability and reliability of routing paths
via automatic default gateway selections on an IP sub-network.
Interface Parameters
Ethernet Interface
Enable/Disable Enabled or disabled this interface.
Default is enabled.
Ethernet Options
Fixed speed (Mbps) Select a speed of 10, 100, 1000. Both ends of the
connection must be set to the same speed.
Not configurable on USB-Ethernet port.
Energy Efficient Ethernet (EEE) Select EEE to allow your device to set low–power
idle mode on this Ethernet interface when there is
no data to send.
DHCP client
IPv6 Neighbor Discovery Select the IOLAN’s default preference. A high value
means this IOLAN will be preferred.
• High
• Medium
• Low
Default is Medium
Manage config flag Hosts should use DHCP for address config.
Enable or disable config flags.
Default is disabled
Manage other config flag Hosts should use DHCP for non-address config.
Enable or disable config flags.
Default is disabled
Add Prefix
Do not use prefix for The sending IOLAN can indicate that a prefix is to
autoconfiguration be used for address autoconfiguration by setting the
autonomous flag and specifying a nonzero Valid
Lifetime value for the prefix.
Enable or disable prefix for autoconfiguration.
Default is off
Hop limit Configure the hop count field of the IP header for
outgoing (unicast) IP packets.
Range is 1–255
Default is 64
VLAN Interface
Enable Enabled or disabled this interface.
Default is enabled
Enable IPv4
For detailed parameter description please see “Ethernet Interface” --> Enable IPv4 address.
Enable IPv6
For detailed parameter description please see “Ethernet Interface” --> IPv6 address .
Bridge Interface
Enable/Disable Interface Enabled or disabled this interface.
Default is enabled.
Enable IPv4
For detailed parameter description please see “Ethernet Interface” --> Enable IPv4 address.
Enable IPv6
For detailed parameter description please see “Ethernet Interface” --> IPv6 address .
PPPoE Interface
Enable/disable interface Enabled or disabled this interface.
Default is enabled
Enable IPv4
For detailed parameter description please see “Ethernet Interface” --> Enable IPv4 address.
Tunnels Interface
Tunnel type Select the tunnel type:
• GRE
• OpenVPN
• 6in4
Default is GRE
Type of service This value is written into the ToS byte in tunnel
packet IP headers (the carrier packet).
The range is 0 to 99, where 0 means tunnel packets
copy the ToS value from the packet being
encapsulated (the passenger packet).
Values 0–99
The default is 0
Time to live This value is written into the TTL field in tunnel
packet IP headers (the carrier packet). The range is 0
to 255, where 0 means tunnel packets copy the TTL
value from the packet being encapsulated (the
passenger packet).
Values are 1-255
The default is 255.
Set multicast operation over Enable or disable multicast operation over the
tunnel tunnel.
Enable IPv6
Static
Manage config flags Hosts should use DHCP for address config.
Enable or disable config flags.
Default is disabled
Manage other config flags Hosts should use DHCP for non-address config.
Enable or disable config flags.
Default is disabled
Add Prefix
Do not use prefix for The sending router can indicate that a prefix is to be
autoconfiguration used for address autoconfiguration by setting the
autonomous flag and specifying a nonzero Valid
Lifetime value for the prefix.
Enable or disable prefix for autoconfiguration.
Default is off
Add DNS
VRRP Interface
Enable VRRP Enable or disable VRRP.
Default is enabled
Priority The priority value for the VRRP router that owns the
IP address(es) associated with the virtual router.
Values are 1–255
Default is 100
Add this VRRP group to a sync Add this sync VRRP group to a sync group.
group Sync groups are used to link VRRP groups together
in order to propagate transition changes from one
group to another group. To clarify, in a VRRP
synchronization group (“sync group”) are
synchronized such that, if one of the interfaces in
the group fails over to backup, all interfaces in the
group fail over to backup.
Note: VRRP groups in a sync group must have
similar priority and preemption configurations.
Before enabling a sync-group you should verify that
one router is master of both groups and the other is
backup of both groups. If both side think they are
master of the same group, then enabling a sync
group can cause endless transitioning to get in sync.
Delay at least this long The time to delay before switching back to a master
when detecting.
Delay is 0–1000 in seconds
Default is 0
Serial
Enable Check option to enable the port.
Hardware settings
Media Type Can define whether the RJ-45 port acts as a DCE or
DTE device. Options are;
• Straight - DCE
• Rolled - DTE
This option is not available on the Multi-protocol
cards.
Initial Delay Configure the time (in ms) between the time the
CTS/RTS signal is raised and the start of character
transmission. This delay only applies if this port is
not running hardware flow control. If hardware flow
control is used, the transmission occurs as soon as
RTS/CTS is raised by the modem.
Final Delay Configure the time (in ms) between the time of
character transmission and when CTS/RTS is
dropped.
Flow control
Enable DTR-DSR monitor The serial doesn’t go active until DTR-DSR are both
active.
Enable Echo Suppression This parameter applies only to EIA-485 Half Duplex
mode. All characters are echoed to the user and
transmitted across the serial ports. Some EIA-485
applications require local echo to be enabled in
order to monitor the loopback data to determine
that line contention has occurred. If your
application cannot handle loopback data, echo
suppression should be enabled.
Default is Disabled
Enable Line Termination If required for RS422 or RS485, enabling this option
puts a 120 Ohm termination on the line.
Serial Port
Name Specify a name for this serial port.
Console Management
The Console Management profile provides access through the network via Telnet or SSH
to a console or administrative port of a server or device attached to the IOLAN’s serial
port. Use the Console Management profile when you are configuring users who need to
access a serial console from the network.
Console Management
Settings
Listen For Connections on TCP The TCP port number the IOLAN will listen on for
Port incoming TCP connections.
Note: If more then one serial port has the same TCP
port number assignment, this creates a hunt group
scenario. You must configure all operating
parameters for each serial port the same.
Default: 10001, depending on the serial port number
Advanced
Enable Message of the Day Enables/disables the display of the message of the
(MOTD) day.
Default is disabled
Dial Options Configures Dial in and Dial Out parameters. See Dial
Options
Session Strings Configures session control for Send at Start, End and
Delay after parameters. See Session Strings
Trueport
TruePort is a COM port redirector client utility that is installed and run on your PC. It can
be run in two modes (the mode is selected on the client software when it is configured).
In client mode the software is installed to listen for connections from the IOLAN to
establish a connection. In server mode, the client PC sends a connection request to the
IOLAN.
Trueport can also be configured on the client to run in Full mode that allows complete
control and operates as if the com port was directly connected to the Workstation/Server’s
local serial port. It provides a complete COM port interface between the attached serial
device and the network. All serial controls, baud rate, control, etc., are sent to the IOLAN
and replicated on its associated serial port.
Alternatively, Trueport can be configured to run in Lite mode where it provides a simple
raw data interface between the application and the remote serial port. Although the port
will operate as a Com port, control signals are ignored.
See the Trueport User’s Guide for more information.
Client Services
Trueport
Settings
Server Initiated
TCP Port The TCP port that the IOLANwill use to communicate
through to the Trueport client.
Default—10001 for serial port 1, then increments by
one for each serial port
Connect to Multiple Hosts When this option is enabled, multiple hosts can
connect to the serial device connected to this serial
port.
Note: These multiple clients (Hosts) need to be
running TruePort in Lite mode.
Default is disabled
Send Name on Connect When enabled, the port name is sent to the host
upon session initiation. This is done before any other
data is sent or received to/from the host.
Default is disabled
Client Initiated
TCP Port The TCP port that the client uses to communicate
through to the Trueport Service
Default—10001 for serial port 1, then increments by
one for each serial port
Client Allow Multiple When this option is enabled, define all the hosts for
Connections (Trueport Lite the client to connect to.
mode) Default is enabled
Note: These multiple clients (Hosts) need to be
running TruePort in Lite mode.
Raise Signals when not under This option has the following impact based on the
Trueport control state of the TruePort connection:
TruePort Lite Mode—When enabled, the EIA-232
signals remain active before, during, and after the
TruePort connection is established.
When disabled, the EIA-232 signals remain inactive
during and after the Trueport connection is
established.
TruePort Full Mode—When enabled, the EIA-232
signals remain active before and after the TruePort
connection and the TruePort client will control the
state of the signals during the established TruePort
connection. When disabled, the EIA-232 signals
remain inactive before and after the TruePort
connection and the TruePort client will control the
state of the signals during the established TruePort
connection.
Default is enabled
Enable Message of the Day Enables/disables the display of the message of the
(MOTD) day (MOTD).
Default is disabled
Enable Data Logging (Trueport When enabled, serial data is buffered if the TCP
Lite Mode) connection is lost. When the TCP connection is re-
established, the buffered serial data is sent to its
destination. If using the Trueport profile, data logging
is only supported in Lite Mode.
Default
Note: a kill line or a reboot of the IOLAN causes all
buffered data to be lost
Some profile features are not compatible with the
data logging feature. See Data Logging Feature
Dial Options Configures Dial in and Dial Out parameters. See Dial
Options
TCP Sockets
The TCP Socket profile allows for a serial device to communicate over a TCP network.
The TCP connection can be initiated from a host on the network and/or a serial device.
This is typically used with an application on a Workstation or Server that communicates
to a device using a specific TCP socket. This is often referred to as a RAW connection.
The TCP Socket profile permits a raw connection to be established in either direction,
meaning that all the connection can be initiated by ether the Workstation/Server or the .
TCP Sockets
Settings • Listen for connection—the IOLAN is
listening for a connection from the server
• Connect to—the IOLAN is initiating a
connection to the server
• Bidirectional Connection—both sides can
initiate or respond to the connection
Connect to Multiple Hosts When this option is enabled, multiple hosts can
connect to the serial device that is connected to this
serial port.
Default is disabled
Enable Message of the Day Enables/disables the display of the message of the
(MOTD) day (MOTD).
Default is disabled
Enable Data Logging When enabled, serial data is buffered if the TCP
connection is lost. When the TCP connection is re-
established, the buffered serial data is sent to its
destination. If using the Trueport profile, data logging
is only supported in Lite Mode.
Default is disabled
Note: a kill line or a reboot of the IOLAN causes all
buffered data to be lost
Some profile features are not compatible with the
data logging feature. See Data Logging Feature
Dial Options Configure Dial in and Dial Out parameters. See Dial
Options
Session Strings Configure session control for Send at Start, End and
Delay after parameters. See Session Strings
UDP Sockets
The UDP profile configures a serial port to send or receive data to/from the LAN using the
UDP [Link] you configure UDP, you are setting up a range of IP addresses and
the port numbers that are used to send UDP data to or receive UDP data [Link] can
use UDP profile in the following two basic modes. The first is to send data coming from
the serial device to one or more UDP listeners on the LAN. The second is to accept UDP
datagrams coming from one or more UDP senders on the LAN and forward this data to
the serial device. You can also configure a combination of both which will allow you to
send and receive UDP data to/from the LAN.
When you configure UDP for LAN to Serial, the following options are available:
To send to a single IP address, leave the End IP Address field at its default value of
([Link])
The IP address can be auto learned if both start/end IP address are left blank/default.
If the Start IP Address field is set to [Link] and the End IP Address is left at
its default value ([Link]), the will accept UDP packets from any source address.
Four individual entries are provided to allow you greater flexibility to specify how data will
be forwarded to/from the serial device. All four entries support the same configuration
parameters. You can configure one or more of the entries as needed.
The first thing you need to configure for an entry is the “Direction” of the data flow. The
following options are available;
• Disabled—UDP service not enabled.
• LAN to Serial—This setting will allow UDP data to be received from one
or more hosts on the LAN and forwarded to the serial device attached to
this serial port.
• Serial to LAN—This setting will allow data originating from the serial
device attached to this serial port to be sent to one or more hosts on the
LAN using UDP datagrams.
• Both—Allows for data to flow from the serial device to the LAN and from
the LAN to the serial device.
The role of each of the configurable parameters in an entry depends on the Direction
selected. When the direction is LAN to Serial the role of the additional parameters is as
follow;
• Start IP Address—This is the IP address of the host from which the
UDP data will originate. If the data will originate from a number of hosts,
this becomes the starting IP address of a range.
• End IP Address—If you wish to receive data only from the single host
defined by Start IP address, leave this entry as is ([Link]). If you wish to
accept data from a number of hosts, this address will represent the
upper end of a range starting from Start IP address. Only data originat-
ing from this range will be forwarded to the serial port.
• UDP port—This is the UPD port from which the data will originate.
There are two options for this parameter.
• Auto Learn—The first UDP message received will be
send to define which UDP port we are going to accept
UDP data from. Once learned, only data from this UDP
port will be accepted. The data must also originate from a
host which is in the IP range defined for this entry.
• Port—Only data originating from the UDP port configured
here as well as originating from a host in the IP range
defined for this entry will be accepted.
When the direction is Serial to LAN the role of the additional parameters is as follow;
• Start IP Address—This is the IP address of the host to which the serial
data will be sent using UDP datagrams. If the serial data is to be sent to
more than one host, this becomes the starting IP address of a range.
• End IP Address—If you wish to send serial data to a single host, leave
this entry as is ([Link]). If you wish to send the serial data to a number
of hosts, this address will represent the upper end of a range starting
from Start IP Address.
• UDP port—This is the UPD port to which the serial data will be for-
warded. For a direction of Serial to LAN, you must specify the port to be
used.
When the direction is Both the role of the additional parameters is as follow;
• Start IP Address—This is the IP address of the host to which the serial
data will be sent using UDP datagrams. It is also the IP address of the
host from which UDP data coming from the LAN will be accepted from. If
the data is to be sent to or received from more than one host, this
becomes the starting IP address of a range.
• End IP Address—If you wish to send serial data to a single host and
only receive data from the single UDP host, leave this entry as is
([Link]). If the data is to be sent to or received from more than one host,
this address will represent the upper end of a range starting from Start
IP Address. Only data originating from this range will be forwarded to
the serial port.
• UDP Port—This is the UPD port to which the serial data will be for-
warded as well as the UPD port from which data originating on the LAN
will be accepted from. For a direction of Both, there are two valid option
for the UDP Port as follows;
• Auto Learn—The first UDP message received will be used to define
which port we are going to accept UDP data from. Once learned, only
data from this UDP port will be accepted and serial data being forwarded
to the LAN will be sent to this UDP port. Until the port is learned, data
from the serial port intended to be sent to the LAN will be discarded.
• Specific/Port—Serial data being forwarded to the LAN from the serial
device will sent to this UDP port. Only data originating from the UDP port
configured here (as well as originating from a host in the IP range
defined for this entry) will be forwarded to the serial device.
UDP Sockets
Listen for Connections on UDP The IOLAN listens for UDP packets on the specified
Port port.
Default is 1000+ port-number. (for example, 10001
for serial port 1)
UDP Port Determines how the UDP port that will send/receive
UDP messages is defined:
• Auto Learn—The IOLAN will only listen to
the first port that it receives a UDP packet
from. Applicable when Direction is set to
LAN to Serial or Both.
UDP Port determines how the UDP port will send/
receive UDP messages.
• Auto Learn—The IOLAN will only listen to
the first port that it receives a UDP packet
from. Applicable when Direction is set to
LAN to Serial or Both.
• Port—The port that the IOLAN will use to
relay messages to servers/hosts. This
option works with any Direction except
disabled. The IOLAN will listen for UDP
packets on the port configured by the
Listen for connection on UDP port
parameter.
Default is Auto Learn
Terminal
The Terminal profile allows network access from a terminal connected to the OLAN’s
serial port. Use this profile to access pre-defined hosts on the network from the terminal.
This profile can be configured for users:
• who must be authenticated by the IOLAN first and then a connection to
a host can be established
• who are connecting through the serial port directly to a host.
Terminal
Settings
Port The TCP Port that the will use to connect to the host.
Default: Telnet-23, SSH-22, Rlogin-513
Enable Local Echo Toggles between local echo of entered characters and
suppressing local echo.
Local echo is used for normal processing, while
suppressing the echo is convenient for entering text
that should not be displayed on the screen, such as
passwords. This parameter is used only when Enable
Line Mode is enabled.
Default is disabled
Enable Line Mode When enabled, keyboard input is not sent to the
remote host until Enter is pressed, otherwise input is
sent every time a key is pressed.
Default is disabled
Control Characters
Advanced
Enable Message of the Day Enables/disables the display of the message of the
(MOTD) day (MOTD).
Default is disabled
Allow Port Locking When enabled, you can lock your terminal with a
password using the Hot Key Prefix (default Ctrl-a) ^a l
(lowercase L). The prompts you for a password and a
confirmation.
Default is disabled
Hot Key Prefix The prefix that a user types to lock a serial port.
Data Range:
• ^a l—(Lowercase L) Locks the
serial port until the user
unlocks it. The user is
prompted for a password
(any password, excluding
spaces) to lock the serial
port. Next, the user must
retype the password to
unlock the serial port. You
can use the Hot Key Prefix
key to lock a serial port only
when the Allow Port locking
is enabled.
Default is Hexadecimal 01 (Ctrl-a, ^a)
Printer
The Printer profile allows for the serial port to be configured to support a serial printer
device that can be access by the network.
Printer
Map CR to CR/LF The default end-of-line terminator as CR/LF (ASCII
carriage-return line-feed) when enabled.
Default is disabled
Session Strings Configures session control for Send at Start, End and
Delay after parameters. See Session Strings
Serial Tunneling
The Serial Tunneling profile allows two to be connected back-to-back over the network to
establish a virtual link between two serial ports based on RFC [Link] serial device that
initiates the connection is the Tunnel Client and the destination is the Tunnel Server,
although once the serial communication tunnel has been successfully established,
communication can go both ways Tunnel Server, although once the serial
communication tunnel has been successfully established, communication can go both
ways.
The Server Tunnel will also support Telnet Com Port Control protocol as detailed in RFC
2217.
Serial Tunneling
Settings
Listen for connection on TCP The TCP port the IOLAN will listen for incoming
Port connection.
Default—10000+serial port number; so serial port 1 is
10001.
Advanced
Break Length When the route receives a command from its peer to
issue a break signal, this parameters defines the
length of time the break condition will be asserted on
the serial port.
Default is 1000ms (1 second)
Delay After Break This parameter defines the delay between the
termination of a a break condition and the time data
will be sent out the serial port.
Default is 0ms (no delay)
Virtual Modem
Virtual Modem (Vmodem) is a feature that provides a modem interface to a serial device.
It responds to AT commands and provides signals in the same way that a serially attached
modem would. This feature is typically used when you are replacing dial-up modems with
the in order to provide Ethernet network connectivity.
The serial port will behave in exactly the same fashion as it would if it were connected to
a modem. Using AT commands, it can configure the modem and the issue a dial-out
request (ATTD). The then translate the dial request into a TCP connection and data will
be begin to flow in both directions. The connection can be terminated by “hanging” up the
phone line. You can also manually start a connection by typing ATD
<ip_address,<port_number> and end the connection by typing +++ATH. The IP address
can be in IPv4 or IPv6 formats and is the IP address of the receiver. For example,
ATD123.34.23.43,10001 or you can use ATD12303402304310001, without any
punctuation (although you do need to add zeros where there are not three digits presents,
so that the IP address is 12 digits long).
Virtual Modem
Settings
Listen on TCP Port The TCP port that the IOLAN will listen on.
Default is 10000 + serial port number (for example,
serial port 1 defaults to 10001)
TCP Port The port number the target host is listening on for
messages.
Default is 0 (zero)
Advanced
Echo characters in command When enabled, echoes back characters that are typed
mode in (equivalent to ATE0/ATE1 commands).
Default is disabled
DTR Signal Always On Specify this option to make the DTR signal always act
as a DTR signal.
Default is enabled
DTR Signal Acts as DCD Specify this option to make the DTR signal always act
as a DCD signal.
Default is disabled
DTR Signal Acts as RI Specify this option to make the DTR signal always act
as a RI signal.
Default is disabled
RTS Signal Always On Specify this option to make the RTS signal always act
as a RTS signal.
Default is enabled
Enable Message of the Day Enables/disables the display of the message of the
(MOTD) day.
Default is disabled
Modbus Gateway
The Modbus Gateway profile configures a serial port to act as a Modbus Master Gateway
or a Modbus Slave Gateway. Each serial port can be configured as either a Modbus
Master or gateway depending on your configuration and requirements.
Modbus Gateway
Settings Modbus Mode - Slave Typically, the Modbus Master is accessing the IOLAN
through the network to communicated to Modbus
Slaves connected to the IOLAN’s Serial Ports.
TCP/UDP Port The network port number that the Slave Gateway
will listen on for both TCP and UDP messages.
Default is 502
Enable Serial Modbus When enabled, a UID of 0 (zero) indicates that the
Broadcast message will be broadcast to all Modbus Slaves.
Default is disabled
Advanced
Local IP address The IPV4 IP address of the IOLAN end of the PPP
link. For routing to work, you must enter a local IP
address. Choose an address that is part of the same
network or subnetwork as the remote end; for
example, if the remote end is address
[Link], your local IP address can be
[Link]. Do not use the IOLAN’s (main) IP
address in this field; if you do so, routing will not
take place correctly.
IPv4 Remote IP Address The IPv4 address of the remote end of the PPP link.
Choose an address that is part of the same network
or subnetwork as the IOLAN. If you set the PPP
parameter IP Address Negotiation to On, the IOLAN
will ignore the remote IP address value you enter
here and will allow the remote end to specify its IP
address. If your user is authenticated by RADIUS and
the RADIUS parameter framed-address is set in the
RADIUS file, the IOLAN will use the value in the
RADIUS file in preference to the value configured
here. The exception to this rule is a Framed-address
value in the RADIUS file of [Link]; this
value allows the IOLAN to use the remote IP address
value configured here.
Dial
Modem init string You can specify additional modem commands that
will affect how the modem starts. The following
commands are supported: ATQn, ATVn, ATEn,
+++ATH, ATA, ATI0, ATI3, ATS0, AT&Z1, AT&Sn,
AT&Rn, AT&Cn, AT&F, ATS2, ATS12, ATO (ATD with
no phone number), and ATDS1.
Phone number The phone number to use when Dial Out is enabled.
Authentication
Remote User Complete this field only if you have specified PAP or
CHAP (security protocols) in the Security field, and
• you wish to dedicate this line to a single
remote user, who will be authenticated by
the IOLAN, or
• you are using IOLAN back-to-back with
another IOLAN
When Dial In or Dial In/Dial Out is enabled, the
Remote User is the name the IOLAN will use to
authenticate the port on the remote device.
Remote Password Complete this field only if you have specified PAP or
CHAP (security protocols) in the Security field, and
• you wish to dedicate this serial port to a
single remote user, and this user will be
authenticated by the IOLAN or
• you are using the IOLAN back-to-back with
another IOLAN
Remote password means the following:
• When PAP is specified, this is the
password the IOLAN will use to
authenticate the remote device.
• When CHAP is specified, this is the secret
(password) known to both ends of the link
upon which responses to challenges will
be based.
Remote password is the opposite of the parameter
Password. Your IOLAN will only authenticate the
remote device when PAP or CHAP is operating.
Field format is you can enter a maximum of 16
alphanumeric characters
CHAP Challenge Interval The interval, in minutes, for which the will issue a
CHAP re-challenge to the remote end. During CHAP
authentication, an initial CHAP challenge takes
place, and is unrelated to CHAP re-challenges.
Enable Roaming Callback A user can enter a telephone number that the IOLAN
will use to callback him/her. This feature is
particularly useful for a mobile user. Roaming
callback can only work when the User Enable
Callback parameter is enabled. Enable Roaming
Callback therefore overrides (fixed) User Enabled
Callback To use Enable Roaming Callback, the
remote end must be a Microsoft Windows OS that
supports Microsoft’s Callback Control Protocol
(CBCP). You are allowed 30 seconds to enter a
telephone number after which the IOLAN ends the
call.
Default is disabled
Configure Request Timeout The maximum time, in seconds, that LCP (Link
Control Protocol) will wait before it considers a
configure request packet to have been lost.
Range is 1–255
Default is 3 seconds
Terminate Request Timeout The maximum time, in seconds, that LCP (Link
Control Protocol) will wait before it considers a
terminate request packet to have been lost.
Range is 1–255
Default is 3 seconds
Settings IPv4
Local IP address The IPV4 IP address of the IOLAN end of the SLIP
link. For routing to work, you must enter a local IP
address. Choose an address that is part of the same
network or subnetwork as the remote end; for
example, if the remote end is address
[Link], your local IP address can be
[Link]. Do not use the IOLAN’s (main) IP
address in this field; if you do so, routing will not
take place correctly.
IPv4 Remote IP The IPv4 address of the remote end of the SLIP link.
Choose an address that is part of the same network
Address or subnetwork as the IOLAN If your user is
authenticated by the IOLAN, this remote IP address
will be overridden if you have set a Framed IP
Address for the user. If your user is authenticated by
RADIUS and the RADIUS parameter Framed -
Address is set in the RADIUS file, the IOLAN will use
the value in the RADIUS file in preference to the
value configured here.
Modem init string You can specify additional modem commands that
will affect how the modem starts. The following
commands are supported: ATQn, ATVn, ATEn,
+++ATH, ATA, ATI0, ATI3, ATS0, AT&Z1, AT&Sn,
AT&Rn, AT&Cn, AT&F, ATS2, ATS12, ATO (ATD with
no phone number), and ATDS1.
Dial Options
Dial in If the device is remote and will be dialing in via
modem or ISDN TA, enable this parameter.
Default is disabled
Dial out If you want the modem to dial a number when the
serial port is started, enable this parameter.
Default is disabled
Modem Init String You can specify additional modem commands that
affect how the modem starts.
Session Strings
Send at Start Session Strings
Controls the sending of ASCII strings to serial device
at session start as follows;
Send at Start—If configured, this string will be sent
to the serial device on power-up of the IOLAN, or
when a kill line command is issued on this serial
port. If the monitor DTR-DSR option is set, the string
will also be sent when the monitored signal is
raised.
Range is 0–127 alpha-numeric characters
Range is hexadecimal 0-FF
Delay after Send If configured, this command will inset a delay after
the string is sent to the device. This delay can be
used to provide the serial device with time to
process the string before the session is initiated.
Default is 10 ms
Packet Forwarding
Packet forwarding can be used to control/define how and when serial port data packets
are sent from the to the network.
Define how the data received on the serial port with be forwarded to the network.
Optimize Network Throughput This option provides optimal network usage while
ensuring that the application performance is not
comprised. Select this option when you want to
minimize overall packet count, such as when the
connection is over a WAN.
Default is disabled
Custom Packet Forwarding This option allows you to define forwarding rules
based on the packet definition or the frame
definition.
Default is disabled
Packet Size The number of bytes that must be received from the
serial port before the packet is transmitted to the
network. A value of zero (0) ignores this parameter.
Range is 0–1024 bytes
Default is 0
End Trigger1 Character When enabled, specifies the character that when
received will define when the packet is ready for
transmission. The actual transmission of the packet
is based on the Trigger Forwarding Rule.
Range Hexadecimal 0–FF
Default is 0
• Trigger+1—Includes the
EOF1, EOF1/EOF2, Trigger1,
or Trigger1/
Trigger2,depending on your
settings, plus the first byte
that follows the trigger.
• Trigger+2—Includes the
EOF1, EOF1/EOF2, Trigger1,
or Trigger1/Trigger2,
depending on your settings,
plus the next two bytes
received after the trigger.
Default is Trigger
SSL/TLS
Enable Enable or disable SSL/TLS.
Add Cipher
Encryption • Any
• AES
• 3DES
• ARCTWO
• ARCFOUR
• AES-GCM
HMAC • Any
• SHA1
• MF5
• SHA256
• SHA384
Common Name An entry for common name; for example, the host
name or fully qualified domain name. This field is
case sensitive in order to successfully match the
information in the peer SSL/TLS certificate.
Data Option is Maximum 64 characters
Login
Limit Connection to User Makes the serial port dedicated to the specified user.
The user won’t need to enter their login name - just
their password.
Telnet
Terminal Type Type of terminal attached to this serial port.
• ansi
• dumb
• hp700
• ibm3151TE
• tvi925
• vt100
• vt320
• wyse60
• term1
• term2
• term3
Enable Local Echo Toggles between local echo of entered characters and
suppressing local echo. Local echo is used for normal
processing, while suppressing the echo is convenient
for entering text that should not be displayed on the
screen, such as passwords. This parameter can be
used only when enable Line Mode is enabled.
Default is disabled
Enable Line Mode When enabled, keyboard input is not sent to the
remote host until Enter is pressed, otherwise input is
sent every time a key is pressed.
Default is disabled
RLogin
Terminal Type Type of terminal attached to this serial port; for
example, ANSI or WYSE60.
SSH
Terminal Type Type of terminal attached to this serial port.
• ansi
• hp700
• ibm3151TE
• tvi925
• vt100
• vt320
• wyse60
• term 1
• term 2
• term 3
Default is dumb
Strict Host Checking When enabled, a host public key (for each host you
want to ssh to) must be downloaded into the
IOLAN.
Default: is enabled
Name The name of the user logging into the SSH session.
Field Format: Up to 20 alphanumeric characters,
excluding spaces.
Protocol
Authentication • RSA
• DSA
• Keyboard-interactive
SLIP
Local IP address The IPV4 IP address of the IOLAN end of the SLIP
link. For routing to work, you must enter a local IP
address.
Choose an address that is part of the same network
or subnetwork as the remote end; for example, if
the remote end is address [Link], your
local IP address can be [Link]. Do not use
the IOLAN’s (main) IP address in this field; if you do
so, routing will not take place correctly.
IPv4 Remote IP The IPv4 address of the remote end of the SLIP link.
Choose an address that is part of the same network
Address or subnetwork as the IOLAN. If your user is
authenticated by the IOLAN, this remote IP address
will be overridden if you have set a Framed IP
Address for the user. If your user is authenticated by
RADIUS and the RADIUS parameter Framed -Address
is set in the RADIUS file, the IOLAN will use the
value in the RADIUS file in preference to the value
configured here.
PPP
Settings IPv4
Local IP address The IPV4 IP address of the IOLAN end of the PPP
link. For routing to work, you must enter a local IP
address.
Choose an address that is part of the same network
or subnetwork as the remote end; for example, if
the remote end is address [Link], your
local IP address can be [Link]. Do not use
the IOLAN’s (main) IP address in this field; if you do
so, routing will not take place correctly.
IPv4 Remote IP The IPv4 address of the remote end of the PPP link.
Choose an address that is part of the same network
Address or subnetwork as the IOLAN. If you set the PPP
parameter IP Address Negotiation to On, the IOLAN
will ignore the remote IP address value you enter
here and will allow the remote end to specify its IP
address. If your user is authenticated by RADIUS and
the RADIUS parameter framed-address is set in the
RADIUS file, the IOLAN will use the value in the
RADIUS file in preference to the value configured
here. The exception to this rule is a Framed-address
value in the RADIUS file of [Link]; this
value allows the IOLAN to use the remote IP address
value configured here.
Authentication
Remote User Complete this field only if you have specified PAP or
CHAP (security protocols) in the Security field, and
• you wish to dedicate this line to a single
remote user, who will be authenticated by
the IOLAN, or
• you are using the back-to-back with
another IOLAN
When Dial In or Dial In/Dial Out is enabled, the
Remote User is the name the IOLAN will use to
authenticate the port on the remote device. Your
IOLAN will only authenticate the port on the remote
device when PAP or CHAP are operating.
When connecting together two networks, enter a
dummy user name; for example, DS_SALES.
Note: If you want a reasonable level of security, the
user name and password should not be similar to a
user name or password used regularly to login to
the IOLAN. This option does not work with external
authentication.
Field Format is you can enter a maximum of 254
alphanumeric characters
Remote Password Complete this field only if you have specified PAP or
CHAP (security protocols) in the Security field, and
• you wish to dedicate this serial port to a
single remote user, and this user will be
authenticated by the IOLAN, or
• • you are using the IOLAN back-to-back
with another IOLAN
Remote password means the following:
• When PAP is specified, this is the
password the IOLAN will use to
authenticate the remote device.
• When CHAP is specified, this is the secret
(password) known to both ends of the
link upon which responses to challenges
will be based.
Remote password is the opposite of the parameter
Password. YourIOLAN will only authenticate the
remote device when PAP or CHAP is operating.
Field format is you can enter a maximum of 16
alphanumeric characters
CHAP Challenge Interval The interval, in minutes, for which the IOLAN will
issue a CHAP re-challenge to the remote end. During
CHAP authentication, an initial CHAP challenge
takes place, and is unrelated to CHAP re-challenges.
The initial challenge takes place even if rechallenges
are disabled. Some PPP client software does not
work with CHAP re-challenges, so you might want to
leave the parameter disabled in the IOLAN.
Range is 0–255
Default is 0 (zero), meaning CHAP re-challenge is
disabled
Enable Roaming Callback A user can enter a telephone number that the
IOLAN will use to callback him/her. This feature is
particularly useful for a mobile user. Roaming
callback can only work when the User Enable
Callback parameter is enabled. Enable Roaming
Callback therefore overrides (fixed) User Enabled
Callback To use Enable Roaming Callback, the
remote end must be a Microsoft Windows OS that
supports Microsoft’s Callback Control Protocol
(CBCP). The user is allowed 30 seconds to enter a
telephone number after which the IOLAN ends the
call.
Default is disabled
Advanced
Network
Cellular Profiles
Cellular profile name Provide a description for this interface.
Name can be up to 32 characters long.
Maximum profiles is 16.
SIM slot 1
• 7
• 8
• 13
•
• 17
• 1800 GSM
• 1900 GSM
• 850 GSM
• 900 GSM
• B13 LTE 700
• B17 LTE 700
• B2 LTE 1900
• B4 LTE 1700
• B5 LTE 850
• BC2 WCDMA 1900
• BC4 WCDAM 1700 AWS
• BC5 WCDMA 850
Advanced
Data APN Settings Specific the APN to use for this connection.
APN
Wireless Profiles
Network name (SSID) Provide a description for this interface.
Name can be up to 32 characters long.
Maximum profiles are 16.
Prevent low level bridging of Dot not allow bridge between clients.
frames between associated clients Default is off
Max Number of Clients Set the number of clients that can connect at the
same time to this ssid.
Values are 1–10
Default is 10
DNS
Overview
The DNS (Domain Name Service) protocol controls the Domain Name System (DNS), a
distributed database with which you can map hostnames to IP addresses. This enables
you to substitute the hostname for the IP address within all local IP commands, such as
ping and telnet. The IP address of the DNS server can be obtained from either a DHCP
server or manually configured on yourIOLAN.
The local Host Table in your IOLAN provides the same function of converting a name to
an IP address to that of using an external DNS server but uses a local database manually
configured by you on your IOLAN.
IPv4 Address (Add, Delete) Enter an IPv4 address for your DNS server. Select
the + symbol to add more.
IPv6 DNS Servers (Add, Delete) Enter an IPv6 address for your DNS server. Select
the + symbol to add more.
DNS Forwarding
Cache Size By setting the cache size, this allows the IOLAN to
store frequently used resolved DNS queries, thereby
allowing clients to resolve DNS queries locally rather
then remotely from a global DNS server.
DNS server 0–10000
Default is 10000
Seconds to Cache NVDOMAIN Cache “Name Error" entries for specified seconds.
entries Also know as Negative caching. It can be useful to
reduce the response time for negative answers. It
also reduces the number of messages that have to
be sent between resolvers and name servers hence
overall network performance.
Range is 0–7200
Default is 3600 seconds
Ignore IP Host Tables Do not check the IP host table for host resolution.
Use DNS Servers received from Select the interfaces that meets this criteria.
DHCP servers for the following
interfaces
DNS Listeners
IPv4 address Enter an IPv4 address to listen for DNS requests.
Dynamic DNS
Host Groups (Add, Edit Configure a Group name.
or Delete)
Web Check to obtain external IP • URL that you want to obtain an IP address
from. This allows the IOLAN to be seen on
the Internet as a public address
• skip everything before this on the given
URL
Registered DNS service Specify whether you are providing a host name or a
host group name.
Host name or Host Specify either a host name or a host group name.
group name
IP Host Tables
The Host table contains the list of hosts to be accessed by an IP address or Fully Qualified
Domain Name (FQDN) from the IOLAN. This local database contains a symbolic names
for the hosts as well as its IP address or FQDN configured by you. When a host entry is
required elsewhere in the configuration, this symbolic name is used. The local Host Table
IP Host Tables
Hostname (Add) Enter a hostname.
WAN
Overview
Your IOLAN has the ability to determine the health status of its interfaces. By configuring
ping and traceroute tests, you can determine whether an interface can send and receive
data, if the interface fails, then a backup action can be taken.
Health Profiles
Profile (Add, Edit, delete)
Test priority Enter a numerical value for the priority for this test.
Tests are (order dependent with 1 being first test to
run and 100 being the last).
Interface IP Health
Interface Select the interface that you want to add a health
profile to.
NextHop Select:
• IP
• DHCP
High Availability
Mode Select:
• Disable
• Failover
• Load Sharing
Failover
Source Interface
WAN Interface
Add WAN Interface Select the interface from the drop-down list.
Rules
Limit
Threshold behavior for limit Configure to apply the threshold limit behavior:
• Above
• Below
The above diagram shows an example of where a customer wants all his local site LAN
traffic on eth1 to by default over his Corporate LAN on eth2, but if that fails, they want all
the traffic to go through the Corporate WiFi on wlan0 and if that fails go through the
Cellular connection on wlm0 in that order of priority. This means that if both eth2 and
wlan0 network connections comes back up it would switch back to the corporate LAN
eth2.
Before configuring the WAN high availability fail-over feature, all 3 network connection
need to configured and tested first by bringing them up 1 at a time and being sure you can
ping a public IP address line "ping [Link]"
In this example the eth2’s IP address is statically configured, so the following two static
configurations are required so that unknown addresses are routed through the eth2. Also
note the administrative distance for the static route needs to match the other 2 WAN
interfaces, in this case 210.
Eth2
Description – Corporate LAN
DHCP
wlm0
Enable
wlan0
Mode – client
SSID Profile – select default SSID of router (example: IRG5521+/2200)
DHCP
Under Network/WAN
High Availability
Mode Failover
Source interface eth1
Add WAN interface
Eth2 priority 40
wlan0 priority 30
wlm0 priority 20
Under WAN
Interface IP Health/Add
eth2
Profile testfailover
Nexthop IP
IP address [Link]
wlan0
Profile testfailover
Nexthop IP
ip address [Link]
wlm0
Profile testfailover
Nexthop DHCP
Under Routing/NAT/ALG
Under Network/DNS/Add
ip address [Link]
To verify the connections, select Command line in the left navigation panel.
At the command prompt type the following commands.
PerleRouter#show ip route
Interface: wlan0
Status: active
Last Status Change: Mon Mar 2 [Link] 2020
+Test: ping Target: [Link]
Last Interface Success: 0s
Last Interface Failure: 43s
# Interface Failure(s): 0
Interface: wlm0
Status: active
Last Status Change: Mon Mar 2 [Link] 2020
+Test: ping Target: [Link]
Last Interface Success: 0s
Last Interface Failure: 57s
# Interface Failure(s): 0
===========================================
Interface: eth2
Status: failed
Last Status Change: Mon Mar 2 [Link] 2020
-Test: ping Target: [Link]
Last Interface Success: 1m8s
Last Interface Failure: 0s
# Interface Failure(s): 6
Interface: wlan0
Status: active
Last Status Change: Mon Mar 2 [Link] 2020
+Test: ping Target: [Link]
Last Interface Success: 0s
Last Interface Failure: 2m32s
# Interface Failure(s): 0
Interface: wlm0
Status: active
Last Status Change: Mon Mar 2 [Link] 2020
+Test: ping Target: [Link]
Last Interface Success: 0s
Last Interface Failure: 45s
# Interface Failure(s): 0
Show wan failover with eth2 and wlan0 network connections down
Interface: wlan0
Status: failed
# Interface Failure(s): 7
Interface: wlm0
Status: active
Last Status Change: Mon Mar 2 [Link] 2020
+Test: ping Target: [Link]
Last Interface Success: 0s
Last Interface Failure: 3m22s
# Interface Failure(s): 0
Show wan failover with eth2 network connection back up but wlan0 network connections
still down
Interface: wlan0
Status: failed
Last Status Change: Mon Mar 2 [Link] 2020
-Test: ping Target: [Link]
Last Interface Success: 3m21s
Last Interface Failure: 1s
# Interface Failure(s): 18
Interface: wlm0
Status: active
Last Status Change: Mon Mar 2 [Link] 2020
+Test: ping Target: [Link]
Last Interface Success: 1s
Last Interface Failure: 5m25s
# Interface Failure(s): 0
ARP Management
Overview
The ARP table holds information on the association between IP addresses and MAC
addresses. This table is maintained by the management software and is used strictly for
management functions.
ARP is used for mapping a network address (e.g. IPv4 address) to a physical address
which in the case of Ethernet is call a MAC address.
Age-out
• Entries have an age-out timeout associated with them. This is the length of
time the entry is maintained in the ARP table. This time is refreshed whenever
a message is received from the IP address matching an entry in the table.
Feature details / Application notes
The ARP table can consist of "static" and "dynamic" entries.
• Static entries are configured by you
• Dynamic entries are learned by the software
Dynamic entries age out if we have not seen a message from that device in the time
specified by the ARP timeout parameter. Static entries do not timeout.
Configuring an ARP entry in the IOLAN prevents the software from "arping" for a host-
name or IP address.
Terminology
ARP—Address Resolution Protocol
ARP is used for mapping a network address (e.g. IPv4 address) to a physical address
which in the case of Ethernet is call a MAC address.
Age-out
• Entries have an age-out timeout associated with them. This is the length of
time the entry is maintained in the ARP table. This time is refreshed whenever
a message is received from the IP address matching an entry in the table.
Feature details / Application notes
The ARP table can consist of "static" and "dynamic" entries.
• Static entries are ones configured by you
• Dynamic entries are learned by the software
Dynamic entries age out if no messages from that device in the time specified by the ARP
timeout parameter. Static entries do not timeout. Configuring an ARP entry in the IOLAN
prevents the software from "arping" for a hostname or IP address.
Static ARP
IPv4 address Enter the IPv4 address you want to add to the ARP
table as a static entry.
ARP Timeout
ARP Timeout If an ARP entry is not used for a specific amount of
time the entry is removed from the caching table.
Disable ARP filter If enabled the IOLAN responds to the same ARP
requests coming from multiple interfaces.
Enable ARP Accept Define the behavior for gratuitous ARP frames
who’s IP is not already present in the ARP table:
0—don’t create new entries in the ARP table
1—create new entries in the ARP table
Enable Proxy ARP Enable Proxy ARP if you need your IOLAN to
respond to local networks with its MAC address.
Default is Disabled
Network Watchdog
Overview
The network watchdog feature monitors the health status of your IOLAN. The watchdog
feature runs continuous ping tests. Each ping test is comprised of one or more ping
attempts. If all of the ping’s in a test fail, the test failed, if one ping test passes, the test is
considered to have passed.
The watchdog feature only gets triggered once there is a successful connection which is
defined as one successful ping. At that point it begins running the tests as configure.
Should any of the ping tests fail, the IOLAN can be set to notify you, or reset or both.
Feature details / Application notes
Once the maximum number of consecutive failed tests occurs the IOLAN will:
1. Start a 2 minute countdown timer to re-boot theIOLAN.
2. A message is displayed in the WebManager notifying you the watchdog timer is
activated due to failed tests.
3. When you get this message it allows you to cancel the reboot within this 2 minute
interval timer.
4. If the 2 minute interval timer expires without your intervention, the reboot occurs.
After the reboot, the watchdog feature begins to monitor the connection for health status
again.
Network Watchdog
Enable Enable or disable the Network Watchdog feature.
Routing
Introduction
This section describes how to configure routing features on your IOLAN. Some
configuration parameters may be different on some models or running software.
Default Gateway
The default gateway specifies the IP address of a node to which traffic should be sent if
the the routing engine does not know which interface to use to reach a given IP address.
This can manually configured by the user or automatically setup via protocols such as
DHCP.
Static Routing
Static routing occurs when you manually configure a routing entry in the routing table,
rather than information collected from dynamic routing traffic.
Overview
Use Static routing to:
• define an exit point from theIOLANwhen no other routes are available or
necessary. This is called a default route.
• define static routes for small networks that require only one or two
routes. This is often more efficient since a link is not being wasted by
exchanging dynamic routing information.
• as a complement to dynamic routing to provide a failsafe backup in the
event that a dynamic route is unavailable.
• help transfer routing information from one routing protocol to another
(routing redistribution).
Restrictions / Limitations
Static routing is not fault tolerant. This means when there is a change in the network or a
failure occurs between two statically defined devices, traffic is not re-routed. As a result,
the network is unusable until the failure is repaired or the static route is manually
reconfigured by an administrator. One important fact to remember is the router on the
other side (destination) must have a route back to the source. If it is not aware of the
source network there will never be a response. Just like if you don't put a return address
on an envelope
Terminology
Dynamic Routes—Dynamic routing is a networking technique that provides optimal data
routing. Unlike static routing, dynamic routing enables routers to select paths according to
real-time logical network layout changes.
Static Routing
Static Routing (Add, Edit, Delete)
Destination prefix mask The prefix mask for the destination network.
Route
Default Gateway for Interface Enable if you want this interface to obtain default
obtained by DHCP gateway though DHCP.
IPv6
Enable IPv6 Unicast Routing Enable unicast routing if your IOLANneeds to route
IPV6 traffic AND to participate in IPv6 IGPs (Interior
Gateway Protocols).
Destination prefix mask The prefix mask for the destination network.
Value is 0–128
Route
Port Forwarding
Port forwarding or port mapping redirects a communication request from one address and
port number combination to another while the packets are traversing a network gateway,
such as a router or firewall.
Overview
Port forwarding is an excellent way to preserve public IP addresses. It protects servers
and clients from unwanted access. It "hides" the services and servers available on a
network, and limits access to and from a network. Port forwarding is transparent to the
end user and adds an extra layer of security to [Link] IOLANsupports ninety-nine
port forwarding rules.
Port Forwarding
Inbound port Configure the port number for the incoming data.
Range is 1-65535
Destination address Configure the IPv4 end device address receiving the
data.
Destination port Configure the end device port number receiving the
data.
Range is 1-65535
NAT/ALG
Network Address Translation (NAT) allows a network device—usually a firewall—to
assign a public address to a computer (or group of computers) inside a private network.
NAT helps limit the number of public IP addresses an organization or company uses for
economic and security purposes.
Overview
Routers inside the private network can route traffic between private computer addresses;
however, to access resources outside the network, like the Internet, these computers
need a public address for responses to their requests to return to them.
To configure NAT, you make at least one interface on the IOLAN—NAT outside and
another interface on the IOLANNAT inside.
NAT
NAT Rules (Add, Edit, Delete)
ACL List Set the ACL from the drop-down list for the
specified interface.
Default is any
Global Address
Do not turn on firewall to drop Connections are not dropped by the firewall.
invalid connections Default is not dropped
Outside Interface Select the outside interface from the drop-down list
for this rule.
Do not turn on firewall to drop By default connections are not dropped by the
invalid connections firewall.
ALG
Enable certain protocols to transverse NAT and Firewalls.
Select the protocols to enable By default all protocols are enabled, to disable
uncheck the check box
• ftp
• gre
• h323
• nfs
• pptp
• sip
• sqlnet
• tftp
Prefix List
Prefix-list is mainly used to filter the routes – not user traffic. Therefore it is used in routing
protocols [Link] main difference in access-list and prefix-list is that access-list only
matches the bits specified by a wildcard mask but prefix-list can also match sub-net mask
and you can specify a range of subnet masks which need to be matched to be permitted
or denied.
Overview
Prefix lists work very similarly to access lists; a prefix list contains one or more ordered
entries which are processed sequentially. As with access lists, the evaluation of a prefix
against a prefix list ends as soon as a match is found.
Feature details / Application notes
Two keywords can be optionally appended to a prefix list entry: minimum prefix length
(less than or equal to) and maximum prefix length (greater than or equal to). Without
either, an entry will match an exact prefix.
Prefix-List
Sequence number Specifies the number to order entries in the prefix
list. Entries will be read from lowest to highest. It is
best practice to leave gaps between sequence
numbers such as 10, 20, 30, so that further entries
can be inserted between numbers.
Range is 1-65535
Minimum Prefix length Specify minimum prefix length (less than or equal
to).
Range is 1–32
Maximum Prefix length Specify maximum prefix length (less than or equal
to).
Range is 1–32
Route Maps
Route maps provide a way for your IOLANto evaluate optimum routes for forwarding
packets or suppressing the routing of packets to particular destinations.
Overview
Compared to access lists, route maps support enhanced packet-matching criteria. In
addition, route maps can be configured to permit or deny the addition of routes to the
routing table and make changes to routing information dynamically as defined through
route-map [Link] IOLANcompares the rules in a route map to the attributes of a route.
The rules are examined in ascending order until one or more of the rules in the route map
are found to match one or more of the route
Feature details / Application notes
• When a single matching match-* rule is found, changes to the routing
• information are made as defined through the configured rules.
• If no matching rule is found, no changes are made to the routing
information.
• When more than one match-* rule is defined, all of the defined match-*
rules must evaluate to TRUE or the routing information is not changed.
• If no match-* rules are defined, the IOLANmakes changes to the routing
information only when all of the default match-* rules happen to match
the attributes of the route.
Route Maps
Route Maps (Add, Edit, Delete)
Community List (Add, Edit, Delete) By using the BGP communities attribute, BGP
speakers with common routing policies can
implement inbound or outbound route filters based
on the community tag, rather than consult long lists
of individual permit or deny statements. A
communities attribute can contain multiple
communities. A BGP community list is used to
create groups of communities to use in a match
clause of a route map.
Community Select how the BGP routes will the advertised to the
community
• internet—advertise this route to the
Internet community; by default, all
prefixes are members of the Internet
community
Ext-Community List (Add, Edit, By using the BGP communities attribute, BGP
Delete) speakers with common routing policies can
implement inbound or outbound route filters based
on the community tag, rather than consult long lists
of individual permit or deny statements. A
communities attribute can contain multiple
communities. A BGP community list is used to
create groups of communities to use in a match
clause of a route map.
Type Select how the BGP routes will the advertised to the
community
Route Target
• VPN Extended Community ([Link])
Site of Origin
• VPN Extended Community ([Link])
An autonomous system number (ASN) is a unique
number that's available globally to identify an
autonomous system and which enables that system
to exchange exterior routing information with other
neighboring autonomous systems.
AS-Paths
The AS path is one of the BGP attributes, it’s a well-known mandatory attribute which
means that it’s included with all prefixes that are advertised through BGP.
Overview
When a BGP router advertises a prefix, it will include its own AS number to the left of the
AS path attribute. The AS path allows us to see through which autonomous systems we
have to travel to get to a certain destination and is also used in BGP for loop prevention.
When the IOLANsees its own AS number in the AS path, it will not accept the prefix.
AS-Paths
Name Configure an AS-path name.
Policy Routing
Policy-based routing overrules your routing table and changes the next hop IP address for
traffic meeting your configured specifications.
Overview
By default, the IOLANforwards packets based on the main routing table. Policy-based
routing allows you to create a Route Policy to match packets and have them use a
separate route policy to forward the packets. Policy-based routing allows you to apply
policies based on source IPv4 address, source MAC-address, destination IPv4 address,
protocol, fragment, IPSEC, recent and state. The resulting actions can include dropping
matched packets or assigning packets to a static routing table.
Policy Routing
Enable Enabled or disabled Policy routing.
Default is disabled
Log packeting matching this rule Log the packets that match this rule.
Traffic Match
Assign to routing table (default Matching packets should be assigned to this default
static) routing table.
Example
This example uses policy-based routing to route all HTTP traffic protocol TCP, destination port
80 through a route policy named http-firewall.
Route Tables
Policy based routing can be used to overrule your routing table and change the next hop
IP address for traffic meeting certain requirements.
Overview
Policy-based routing provides a tool for forwarding and routing data packets based on
policies defined by you. It is a way to have the policy override routing protocol
decisions. Policy-based routing includes a mechanism for selectively applying policies
based on source IPv4 address, source mac-address, destination IPv4 address, protocol,
fragment, IPSEC, recent and state. The resulting actions can include dropping matched
packets or assigning packets to a static routing table.
Route Tables
Route Tables (Add, Edit, Delete)
Route
Default Gateway for Interface Select this option to use the default gateway
obtained by DHCP obtained by DHCP.
Default is off
Route
RIP
Routing Information Protocol (RIP) is a dynamic routing protocol which uses hop count as
a routing metric to find the best path between the source and the destination network.
Overview
RIP prevents routing loops by implementing a limit on the number of hops allowed in a
path from source to destination. RIP messages use the User Datagram Protocol on port
520 and all RIP messages exchanged between routers are encapsulated in a UDP
segment. The routing metric used by RIP counts the number of routers that need to be
passed to reach a destination IP network. The hop count 0 denotes a network that is
directly connected to your IOLAN. A network is unreachable at 16 hops according to the
RIP hop limit.
RIP
Enable RIP Enable or disabled RIP.
Default is disabled
Timers
Network (Add, Delete) Specify the Network’s IPv4 address and netmask.
• IPv4 Address
• IPv4 Mask
ACL List or Prefix List Select ACL list from the drop-down list.
Select a Prefix List from the drop-down box
Enable Poison reverse Enabling poison reverse for split-horizon sets the
for split-horizon IOLANto actively advertise routes as unreachable
from the interface over which they were learned
by—setting the IOLAN’s metric to infinite (16 for
RIP). The effect of such an announcement is to
immediately remove most looping routes before
they can propagate through the network.
The main disadvantage of poison reverse is that it
can significantly increase the size of routing
announcements in certain fairly common network
topologies, but it allows for the improvement of the
overall efficiency of the network in case of faults.
Default is disabled.
Key Chain (Edit) Specify the set of keys that can be used on an
interface for RIP authentication.
OSPF
Overview
OSPF (Open Shortest Path First) is a router protocol used to find the best path for packets
as they pass through a set of connected networks.
Some of the most important reasons for implementing OSPF protocol are:
• Reducing routing overheads for companies
• Achieving network redundancy
• Optimizing performance of local area networks (LAN)
Terminology
OSPF (Open Shortest Path First)
Open Shortest Path First (ospf) is a protocol used to find the best paths for packets as
they pass through a set of connected networks. OSFP was designed to replace the RIP
protocol as it optimizes the updating up of the routing table. OSPF should be enabled on
your IOLAN.
Area Type
Normal area By default, when you use a multiple area design, your created area’s will be
considered “normal” area’s. This just means that these area’s support the flooding of all
standard LSA types (1,2,3,4,5). Your backbone is considered a “normal” area. The main
problem with “normal” area’s are they must carry all redistributed routes, including the
redistributed routes instability. So to limit the amount of routing information into area’s,
besides summarization, different “stubbie” area types are available.
Stub areas are areas through which or into which AS external advertisements are not
flooded. You might want to create stub areas when much of the topological database
consists of AS external advertisements. Doing so reduces the size of the topological
databases and therefore the amount of memory required on the internal routers in the stub
area. Stub areas are shielded from external routes but receive information about networks
that belong to other areas of the same OSPF domain. You can define totally stubby areas.
Routers in totally stubby areas keep their LSDB-only information about routing within their
area, plus the default route.
Not-so-stubby areas (NSSAs) are an extension of OSPF stub areas. Like stub areas,
they prevent the flooding of AS-external link-state advertisements (LSAs) into NSSAs and
instead rely on default routing to external destinations. As a result, NSSAs (like stub
areas) must be placed at the edge of an OSPF routing domain. NSSAs are more flexible
than stub areas in that an NSSA can import external routes into the OSPF routing domain
and thereby provide transit service to small routing domains that are not part of the OSPF
routing domain.
OSPF Router ID is an IPv4 address (32-bit binary number) assigned to each router
running the OSPF protocol. OSPF Router ID should not be changed after the OSPF
process has been started and the OSFP neighborships are established.
OSPF Reference Bandwidth. OSPF uses a simple formula to calculate the OSPF cost
for an interface with this formula: cost = reference bandwidth / interface bandwidth
Administrative distance determines what route to take when there are identical entries
in the routing table. OSPF uses three different administrative distances: intra-area, inter-
area, and external. Routes within an area are intra-area; routes from another area are
inter-area; and routes injected by redistribution are external. The default administrative
distance for each type of route is 110.
Border router is a router with interfaces in two (or more) different areas. An area border
router is in the OSPF boundary between two areas. Both sides of any link always belong
to the same OSPF area.
Virtual Links All areas in an OSPF autonomous system must be physically connected to
the backbone area 0). In some cases where this physical connection is not possible, you
can use a virtual link to connect to the backbone through a non-backbone area.
SPF – Shortest Path First
Interface – OSPF
• A broadcast interface behaves as if the routing device is connected to a
LAN.
• A point-to-point interface provides a connection between a single
source and a single destination (there is only one OSPF adjacency).
• A point-to-multipoint interface provides a connection between a single
source and multiple destinations.
• Non-broadcast type is used on networks that have no broadcast/multi-
cast capability, such as frame-relay, ATM, SMDS, & X.25
OSPF
Enable OSPF/OSPFv3 Enable or disabled OSPF/OSPFv3
Default is disabled
Distance
OSFP inter-area routes Sets the OSPF administrative distance by route type.
Routes from another area are inter-area.
Range is 1–255
Default is 110
OSFP intra-area routes Sets the OSPF administrative distance by route type.
Routes within an area are intra-area.
Range is 1–255
Default is 110
OSPFv3 Area
OSFP Areas
Add Range
Default cost Cost for the default summary route used for a stub
or NSSA.
Range is from 0–16777215
Hello Packet Interval Configure the hello packet time interval for hello
packets sent on an interface.
The default is 10 seconds.
Dead Router Detection Time Configures the interval during which at least one
hello packet must be received from a neighbor
before the IOLAN declares that neighbor as down
(dead).) As with the hello interval, this value must
be the same for all IOLANs attached to a common
network.
Default is 4 times the hello interval
Default is 40 seconds
Ranges
User Specified Cost Configure the metric for this area range.
Range is 0–16777215
Add IP Network
Add Neighbor
Router Map Select the router map from the drop-down list.
Interface—OSPF (Edit)
Router Priority A router with a high priority will always win the DR/
BDR election process
Priority Range is 0-255
Default is 1
Interface cost OSPF uses "Cost" as the value of metric and uses a
Reference Bandwidth of 100 Mbps for cost
calculation. The formula to calculate the cost is
Reference Bandwidth divided by interface
bandwidth.
For example, in the case of 10 Mbps Ethernet, OSPF
Metric Cost value is 100 Mbps / 10 Mbps = 10
Authentication
Add Key
Neighbor ID Pri State Dead Time Address Interface RXmtL RqstL DBsmL
[Link] 1Full/BR[Link].16.0.1Ethernet 1000
[Link] 1Full/BR[Link].168.0.2Ethernet 2000
NOTE: R1 and R3 will never establish a neighbor relationship because they reside in
different areas.
BGP
Overview
Border Gateway Protocol (BGP) is one of the key protocols used to achieve Internet
connection redundancy and optimization. It is designed as a standardized exterior
gateway protocol to exchange routing and reachability information among autonomous
systems (AS) on the Internet. BGP makes routing decisions based on paths, network
policies, or rule-sets configured by you.
When you connect your network to two different Internet service providers (ISPs), it is
called multihoming. When running BGP with more than one service provider, you run the
risk that your autonomous system (AS) will become a transit AS. Internet traffic can pass
through your AS and potentially consume all of the bandwidth and resources on the CPU
of your IOLAN. See the example below for setting up BGP with multihoming.
Terminology
BGP (Border Gateway Protocol) is a routing protocol that makes routing decisions across
the Internet—usually externally rather than internally. BGP works towards changing
routing information between gateway hosts in a network of autonomous systems—it
establishes routing between users and allows for peer and carrier networks to connect.
AS (Autonomous System)—is a set if internet routable IP prefixes belonging to a network
or a collection of networks that are all managed and controlled by a single organization.
BGP
BGP (Add, Edit, Delete)
Administrative Distance
BGP Distance
Distance for external routes to Configure the administrative distance (AS) for
AS external routes.
Values are 1–255
Default is 20
Distance for internal routes to Configure the administrative distance (AS) for
AS internal routes.
Values are 1–255
Default is 200
Distance for local routes Configure the administrative distance (AS) for local
routes.
Values are 1–255
Default is 200
Timers
All BGP attributes are Allows the IOLAN to send updates to a neighbor
propagated unchanged to this with unchanged attributes.
neighbor Default is on
Advertise capability to the peer Advertises support for Outbound Route Filtering
(OFR) for updating BGP capabilities advertised and
received from this neighbor.
Dynamic
• ORF receive
• ORF transmit
• ORF both
Default is OFR transmit
Default is session is brought up with minimal
capability on both sides
Originate default route to this Enables or disables forwarding of the default route
neighbor to a BGP neighbor.
Default is off
One-hop away EBGP peer using Enables a directly connected eBGP neighbor to peer
loopback address using a loopback address without adjusting the
default TTL of 1.
Default is off
Allow EBGP neighbors not on Allows you to establish eBGP peer relationships
directly connected networks between routers that aren’t directly connected to
one another.
Default is off.
Filter outgoing updates Filter outgoing packet updates from neighbors. You
must create the access list before it can be selected
here.
Default is off
Filter incoming routes Limit inbound BGP routes according to the specified
access list. You must create the access list before it
can be selected here.
Default is off.
Specify local as number Using a local AS number permits the routing devices
in an acquired network to appear to belong to the
former AS. This is useful if you cannot immediately
modify your peer arrangements or configuration
during a transition period of assigning a new AS
number.
Allow a maximum number of Specify the number of prefixes that have been
prefixes accepted from this received from a peer has exceeded the maximum
peer prefix limit.
Default is off
Disable the next hop This command will change next hop attribute for
calculation for this neighbor received updates to its own IP address.
Default is off
Don’t send open messages to Configure the routing device to be passive, the
this neighbor routing device will wait for the peer to issue an
open request before a message is sent.
Default is off
Neighbor’s BGP port (TCP) Specify the TCP port that BGP peers will use to
exchange BGP information.
Values 1-65535 ports
Default is 179 port
Remove private AS number Select this option to remove private ASNs from the
from outbound updates AS path if you have been using private ASNs and
you want to access the global Internet.
Default is off
Configure a neighbor as Route Configure the local router as the route reflector and
Server client the specified neighbor as one of its clients. All the
neighbors configured with this command will be
members of the client group and the remaining
iBGP peers will be members of the nonclient group
for the local route reflector.
Strict capability negotiation for By default, your IOLAN will bring up peering with
this neighbor minimal common capability for the both sides. For
example, local router has unicast and multicast
capabilities and remote router has unicast
capability. In this case, the local router will establish
the connection with unicast only capability.
Hold Time How long the IOLAN will wait for a keepalive
message before declaring a router off-line. A shorter
time will find an off-line router faster.
Values are 1–65535
Default is 180
Connect Timer How long in seconds the IOLAN will try to reach
this neighbor before declaring it off-line.
Values are 1–65535
Default is 120
Specify the maximum number Enable, then specify the number of hops for not
of hops to the BGP peer directly connected EBGP neighbors.
Values are 1–254
Set source of routing updates Select the source for routing updates.
• IP based
• Interface based
Set default weight for routes Weight is not exchanged between BGP routers.
from this neighbor Weight is only local on the router.
The path with the highest weight is preferred.
Values are 1–65535
BGP Settings
MED Attribute
Treat missing MED Treats a route without an MED as the worst possible
as the least available route due to expected unreliability.
preferred one Default is off
Configure client to client Select whether this BGP entity reflects routes
route reflection received from a client to another client.
Default is on
Default Local Preference Configure a local preference level. The higher value
is more preferred.
Values are 0–4294967295
Default is 100
Pick the best-MED path Determine the best MED-path from paths
among paths advertised advertised from the neighboring AS.
from the neighboring AS Default is off
Enforce the first AS for Enforce the first (left-most) autonomous system
EBGP routes number (ASN) is the AS-path in the previous
neighbor's ASN.
Default is off
Set the max time to Configure the time to hold stale paths of restarting
hold onto restarting neighbors
peer’s stale paths Value is 1–3600 seconds.
Default is 360 seconds
Check BGP network Check if the BGP network route exists in IGP.
route exists in IGP Default is on
Filter more specific routes from Filter longer prefixes inside of the aggregate address
update before sending BGP updates.
Filter more specific routes from Filter longer-prefixes inside of the aggregate
update address before sending BGP updates.
Border Gateway Protocol (BGP) is one of the key protocols to use to achieve Internet
connection redundancy. When you connect your network to two different Internet service
providers (ISPs) this is called mulithoming. The advantages of multihoming is it provides
both redundancy and network optimization. However, when running multihoming, you run
the risk that your autonomous system (AS) could become a transit AS—Internet traffic is
passed through your AS and consuming all the bandwidth and resource on your IOLAN
Network Diagram
This configuration allows IOLAN (R1) to peer with BGP speakers in other autonomous
systems. The route-map localonly command allows only the locally generated routes to
be advertised to both of the ISPs. This prevents Internet routes from one ISP to the other
ISP and prevents the risk that your AS becomes a transit AS for Internet traffic.
You want to accept routes that are directly connected to the ISPs, therefore you must filter
the routes that they send to you, as well as the routes that you advertise. Do you that use
this access-list and route map command.
Apply the prefix-list on the inbound updates on individual BGP neighbors like this
neighbor [Link] prefix-list filterroute in
neighbor [Link] prefix-list filterroute in
Services
Port Buffering
Serial Port Data Buffering
NFS Host The NFS host that the IOLAN will send data to for its
Remote Port Buffering feature. The IOLAN will open a
file on the NFS host for each serial port configured for
Console Management, and will send serial port data
to be written to that file(s).
Default is None
Enable Port Buffering to Syslog When enabled, buffered data is sent to the syslog
host to be viewed on the host’s monitor.
Add Time Stamp Enable/disable time stamping of the serial port buffer
data.
Default is disabled
Enable Key Stoke Buffering When enabled, key strokes that are sent from the network
host to the serial device on the IOLAN’s serial port are
buffered.
Default is disabled
50 300 or above
Default is 57600
75 300 or above
Default is 75
300 300
600 600
1200 1200
1800 1800
2400 2400
4800 4800
9600 9600
19200 19200
38400 38400
Flush Data Before Closing Serial When enabled, deletes any pending outbound data
Port when a port is closed.
Default is disabled
Deny Multiple Network Allows only one network connection at a time per
Connections serial port. Application accessing a serial port device
across a network will get a connection (socket)
refused until:
• All data from previous connections on that
serial port has drained
• There are no other connections
• Up to a 1 second interconnection poll timer
has expired
Enabling this feature automatically enables a TCP
keep-alive mechanism which is used to detect when a
session has abnormally terminated. The keep-alive is
sent after 3 minutes of network connection idle time.
Applications using this feature need to be aware that
there can be some considerable delay between a
network disconnection and the port being available
for the next connection attempt, allowing any data
sent on prior connections to be transmitted out of
the serial port. Application network retry logic needs
to accommodate this feature.
Default is disabled
Data Logging When enabled, serial data will be buffered if the TCP
connection is lost. When Logging the TCP connection
is re-established, the buffered serial data will be sent
to its destination.
If using the Trueport profile, data logging is only
supported in Lite Mode.
Default is disabled
Note: A kill line or reboot of the IOLAN causes all
buffered data to be lost.
Status Interval Specify how often, in seconds, the IOLAN will send a
TCP keep-alive to services that support TCP keep-
alive.
Default is 180 seconds
DHCP Server
The Perle IOLANcan act as a DHCP server to devices connected to its Ethernet ports or
devices which can access the network. A DHCP Server is a network server that
automatically provides and assigns IP addresses, default gateways and other network
parameters to client devices. It relies on the standard protocol known as Dynamic Host
Configuration Protocol or DHCP to respond to broadcast queries by clients Your
IOLANcan act as a DHCP server so that clients can obtain addresses from its DHCP pool.
Your IOLANhas a predefined default pool with a network address of [Link] and a
pool from [Link] to [Link].
To use DHCP/BOOTP, edit the bootp file with configuration parameters. You can use
DHCP/BOOTP to perform the following actions on a single or multiple IOLANs on boot up:
• auto-configure with minimal information; for example, only an IP address
• auto-configure with basic setup information (IP address, subnet/prefix bits, etc.)
• download a full configuration file
DHCP/BOOTP is particularly useful for multiple installations: you can do all your Perle
IOLANconfiguration in one DHCP/BOOTP file, rather than configure each IOLAN
manually. Another advantage of DHCP/BOOTP is that you can connect your IOLAN to the
network, turn on its power and let autoconfiguration take place. All the configuration is
carried out for you during the DHCP/BOOTP process.
DHCP Parameters
The following parameters can be set in the DHCP/BOOTP bootp file:
• SW_FILE—The full path, pre-fixed by hostname/IP address (IPv4 or IPv6), and
file name of the software update.
• CONFIG_FILE—The full path, pre-fixed by hostname/IP address (IPv4 or
IPv6), and file name of the configuration file.
• GUI_ACCESS—Access to the IOLAN from the HTTP or HTTPS-WebManager.
Values are on or off.
• AUTH_TYPE—The authentication method(s) employed by the IOLAN for all
users. You can specify the primary and secondary authentication servers, sep-
arated by a comma. This uses the following numeric values for the
authentication methods.
Terminology
DHCP Pool
A predefined grouping of IP addresses from which the DHCP server can assign IP
addresses to clients.
DHCP lease
• A DHCP lease defines the duration for which a valid IP address is assigned to
a DHCP client.
• When the lease expires, the DHCP client will not be able to use the IP assigned
to it unless the DHCP reassigned that IP address.
DHCP Relay Agent
A DHCP relay agent is a device which forwards DHCP requests from clients to a DHCP
server. This often is used if a central DHCP server is being used. The DHCP clients make
the local DHCP requests and these requests are forwarded by the Relay Agent to the
DHCP server which is not available on the local network
.
DHCP Server
Enable DHCP Server Enable or disabled DHCP Server.
Default is enabled.
Specify Address Range within The IOLAN’s DHCP pool will assign addresses to
Network clients starting at X.X.X.X with an end address of
X.X.X.X.
Default Gateway Specify the default gateway. This will normally be the
IP address of your IOLAN.
Destination Network Prefix Specify a destination network prefix for this static
route.
Destination Network Mask Specify a destination network mask for this static
route.
Reserved Addresses Enter reserved addresses (IP addresses that will not
be served from this pool) and their corresponding
MAC addresses.
Advanced
Domain Name Specify the Domain name of the server that has the
bootfile.
Bootp Server Name Specify the name of the bootp server that contains
the bootp file.
DHCP Relay
Overview
The IOLAN is able to act as a DHCP relay agent. The DHCP relay agent forwards DHCP
requests between the DHCP clients residing on the local subnet and a remote DHCP
server which resides outside the local physical subnet.
Terminology
DHCP Relay Agent
A Relay agent is a device which forwards DHCP requests from clients to a DHCP
server. This is often used if a central DHCP server is being used. The DHCP clients make
local DHCP requests and these requests are forwarded by the relay agent to the DHCP
server which is not available on the local network.
Feature details / Application notes
The DHCP Relay agent does not transparently forward DHCP requests to the DHCP
server. It receives the DHCP request from the client and generates a new request which
is forwarded to the DHCP server. The relay agent will include additional information in the
DHCP request which provides the remote DHCP server with information on where the
request is coming from so that the correct IP address can be assigned to the DHCP client.
DHCP Relay
Enable DHCP Relay Agent Enable or disabled DHCP Relay Agent.
Default is enabled
Hop Count Set the maximum hop count before packets are
discarded.
Range is 0–255
Default is 10
DHCP Server Specify the DHCP server associated with this relay
interface.
DHCP Option
150 TFTP server IP address. Only the first IP address is
used.
54 Server Identifier
Note: in decreasing order of precedence
DHCP Option
67 Bootfile name
The DHCP option is used for the software and protocol selection.
DHCP Option
125 Specify:
1. Software file name to be download
2. Protocol to use to retrieve the bootfile (start-up config)
TFTP:
Default if no protocol
selected
HTTPS:
When using HTTPS, you
must either disable server
certificate validation (no
http-client verify server) or
load CA certificates on the
IOLAN.
FTP:
When using FTP, username
is anonymous and the
password is <serial# of the
unit>@<oem-name>.com
Examples
DHCP Option
60 <oem-name>:<serial#> in ASCII
Vendor class Example: Perle:IOLAN SCR1618 RDAC :99-011319T001A4
identifier
SNMP
Overview
Simple Network Management Protocol is a standard management protocol which you can
use to monitor or configure all aspects of your IOLAN.
The IOLAN supports configuration and management through SNMP. SNMP Management
tools (SNMP client/MIB browser software) can be used to set IOLAN configuration
parameters and/or view statistics.
Using SNMP
Before you can connect to the IOLAN through an SNMP Management tool or MIB
browser, you need to set the following components through another configuration method.
Pre-requisites
• You must load the Perle supplied SNMP MIBs. The IOLANMIBs can be found
on the Perle web site.
Terminology
Communities
These are used to define the access level to different groups.
Traps
This is the message which SNMP uses to inform management software when an event
has occurred on a managed entity.
• Inform traps are traps which require acknowledgment from the receiver.
Inform
Since SNMP operates over UDP, there is usually no guarantee that a message has been
received by the intended recipient. Inform is a type of SNMP trap which requires the
receiving host to acknowledge the fact that it has been received and therefore giving the
sending entity a confirmation that the message was correctly received.
MIB
Management Information Base. This defines the parameters which SNMP can operate
on.
Configuring SMNP parameters
SNMP
SNMP Target Hosts Define the SNMP hosts to send traps to.
IPv4 or IPv6 address of host.
Type of notification trap or inform.
Version of trap (v2 or v3c)
UDP port UDP port the trap host is listening on. (default is
162).
Add View
Add Group
Add User
Custom Default Engine ID Specify your own custom Engine ID for your
IOLAN.
NTP Server
Network Time Protocol (NTP) is used as a method of distributing and maintaining
synchronization of time information between nodes in a network. NTP server uses UTC
(Universal Coordinated Time). When initially launched, it can take NTP as much as 5
minutes to obtain an accurate [Link] is due to the algorithm used to determine what
NTP master(s) your IOLAN should synchronize with. NTP will not synchronize with nodes
whose time is significantly even if its stratum is lower. During this “settling” period, your
IOLAN may not have the correct time. NTP can usually achieve time synchronization
between two systems in the order of a few milliseconds. This can be achieved with a time
transmission rate of as little as one packet per minute.
NTP Server
A node with an accurate clock source which is used to disseminate the time information
to the other nodes in the network. A network may contain multiple NTP servers. The client
will attempt to determine what the best clock source is and use it.
NTP Client
A node which receives its time information from an NTP Server (or an NTP peer).
UDP—User Datagram Protocol
This is the underline protocol used by NTP and SNTP for packet transmission.
Stratum
This defines the NTP. The highest stratum is 1. It is reserved for atomic clocks, GPS
clocks or radio clock which generates a very accurate time. This type of time source is
defined as the “Authoritative time source”. The stratum defines how many hops a node is
from the “authoritative time source”. Stratum x nodes are synchronized to stratum x-1
nodes. Stratum numbers range from 1 to 15.
Feature Details / Application Notes
When initially launched, it can take NTP as much as 5 minutes to obtain an accurate time.
This is due to the algorithm used to determine what NTP master(s) your IOLAN should
synchronize with. NTP will not synchronize with nodes whose time is significantly different
than the other nodes, even if its stratum is lower. During this “settling” period, your IOLAN
may not have the correct time. NTP can usually achieve time synchronization between
two systems in the order of a few milliseconds. This can be achieved with a time
transmission rate of as little as one packet per minute.
Terminology
SNTP—Simple Network Time Protocol
A subset of NTP
Uses the same protocol.
SNTP can only receive the time from NTP servers and cannot be used to provide time
services to other systems.
NTP Server
A node with an accurate clock source which is used to disseminate the time information
to the other nodes in the network. A network may contain multiple NTP servers. The client
will attempt to determine what the best clock source is and use it.
NTP Client
A node which receives its time information from an NTP Server (or an NTP peer).
UDP—User Datagram Protocol
This is the underline protocol used by NTP and SNTP for packet transmission.
Stratum
This defines the NTP. The highest stratum is 1. It is reserved for atomic clocks, GPS
clocks or radio clock which generates a very accurate time. This type of time source is
defined as the “Authoritative time source”. The stratum defines how many hops a node is
from the “authoritative time source”. Stratum x nodes are synchronized to stratum x-1
nodes. Stratum numbers range from 1 to 15.
Feature Details / Application Notes
When initially launched, it can take NTP as much as 5 minutes to obtain an
accurate time. This is due to the algorithm used to determine what NTP master(s) your
IOLAN should synchronize with. NTP will not synchronize with nodes whose time is
significantly different than the other nodes, even if its stratum is lower. During this
“settling” period, your IOLAN may not have the correct time. NTP can usually achieve time
synchronization between two systems in the order of a few milliseconds. This can be
achieved with a time transmission rate of as little as one packet per minute.
NTP Settings
Enable NTP (Network Time By default NTP is disabled globally. See reference for
Protocol NTP per interface.
Auto-negotiate broadcast delay By default, your IOLAN will set broadcast delay to
Auto-negotiate. Select the auto-negotiate broadcast
delay off if you wish to set your own broadcast
delay time in microseconds.
Act as a master NTP clock Sets your IOLAN to act as the master clock source
providing time to NTP clients.
NTP Server/Peer
Prefer this server/peer Select this option to prefer this NTP source over
another. A preferred server/peer's responses are
discarded only if they vary greatly from the other
time sources. Otherwise, the preferred server/peer
is used for synchronization without consideration of
the other time sources.
Advanced Options
Minimum poll interval 4(16s), 5(32 s), 6 (1m, 4s), 7(2m,8s), 8(4m, 16s),
9(8m, 32s), 10 (17m, 4s), 11 (34m, 8s).
Default is 6
Maximum poll interval 4(16s), 5(32 s), 6 (1m, 4s), 7(2m, 8s), 8(4m,16s),
9(8m, 32s), 10 (17m, 4s), 11 (34m, 8s).
Default is 10
Alarm Manager
Overview
TheIOLAN can monitor for global and individual port conditions. These alarms can be
configured to send alert messages to an;
• External Syslog server
• SNMP trap server
Port Status Monitoring Alarms
• Link Fault Alarm (IE loss of signal)
• Port not operating alarm (failure upon start up tests)
Global Status Monitoring Alarms
• Internal temperature alarm
Feature details / Application notes
Port Alarms
Port Alarms (Add, Edit or Delete)
Not Operational
Link Fault
Telnet/SSH
Overview
Set the VTY sessions, SSH client, and SSH server configuration parameters in this
section.
Terminal
Enable terminal history size Enter the size of the terminal history.
Range is 1–256
Default is 20
Session EXEC inactivity timeout Specify the days, hours, minutes, and seconds for
the timeout on EXCEC sessions.
SSH
Client
Enable strict host key checking When enabled, a host public key—for each host you
(install host keys) SSH to—must be downloaded into the IOLAN.
Default is enabled
Server
Your IOLAN provides you with three mechanisms for configuring QOS.
1) Priority-queuing—packets are placed in queues, high priority packets are sent first.
2) Rate-control—rate control is a classless policy that limits the packet flow to a set rate.
Traffic is filtered based on the expenditure of tokens. Tokens roughly correspond to bytes.
Short bursts can be allowed to exceed the limit. On creation, the Rate-Control traffic is
stocked with tokens which correspond to the amount of traffic that can be burst in one go.
Tokens arrive at a steady rate, until the bucket is full.
3) Traffic-limiting—traffic limiting is a mechanism that can be used to "police" incoming
traffic. The mechanism assign each traffic flow a bandwidth limit. All incoming traffic within
a flow in excess of the bandwidth is [Link] policy can be applied to both ingress
and egress packets.
With QoS, you can change your network so that certain traffic is preferred over other traffic
when it comes to bandwidth—the speed of the link in bits per second, delay—the time it
takes for a packet to get from a source to the destination and back, jitter—the variation of
one-way delay in a stream of packets and loss—the amount of lost data when packets get
dropped. What you need to configure, however really depends on the applications that
you use. Applications that benefit from defining QOS rules are those that rely on the timely
delivery of real–time data packets, for example:
• Video-on-demand
• Voice over IP (VoIP)
• Internet Protocol television (IPTV)
• Streamed media
• Video conferencing
• Online gaming
Feature Details / Application Notes
The traffic classification process consists of these steps:
1. Create a class map by configuring an ID, description, and associated match commands
for that class map. A set of match commands are match criteria related to Layer 3 and
Layer 4 traffic classifications or Layer 7 protocol classifications.
2. Create a policy map which refers to the class map and identifies a series of actions to
perform based on the traffic match criteria.
3. Activate the policy map, then attach it to a specific interface by using the service-policy
command.
Terminology
A class map defines a traffic classification—a network that is of interest to you.
Class Map—contains the following components:
• Class ID
• Description
• One or more match commands that define the match criteria for the
class map
• Instructions on how your IOLAN will evaluates match commands when
you specify more than one match command in a class such as match
any, match-all
• match criteria related to Layer 3 and Layer 4 traffic classifications or
Layer 7 protocol classifications
Policy Map— refers to the class maps and identifies a series of actions to perform based
on the traffic match criteria.
QOS
Class Maps (Add, Edit and Delete)
Match Rules
•
• Ethernet
• OpenVPN-Tunnel <0–999>
• Tunnel <0–999>
Match Type—IP • IP
• source IPv4 address and
wildcard bits
• IPv4 source port TCP/UDP
(1–65535)
• destination IPv4 address
and wildcard bits
• dscp—default
• af11
• af12
• af13
• af21
• af22
• af23
• af31
• af32
• af33
• af41
• af42
• af43
• cs1
• cs2
• cs3
• cs4
• cs5
• cs6
• cs7
• ef
• dscp
Policy Map
Rate-Control
LLDP
Overview
Link Layer Discovery Protocol (LLDP), defined in the IEEE 802.1AB standard, is a Layer
2 protocol that allows network devices to advertise their identity and capabilities on a LAN.
LLDP specifically defines a standard method for Ethernet network devices such as
switches, routers and wireless LAN access points to advertise information about
themselves to other nodes on the network and store the information they discover. LLDP
should be enabled in a multi-vendor network.
LLDP
Enable LLDP Enable or disable LLDP.
Tx Hold Multiplier Configure a value for the LLDP hold multiplier. This is
the time to cache learned LLDP information before
discarding, measured in multiples of the Timer
parameter.
For example, if the Timer is 30 seconds, and the Hold
Multiplier is 4, then the LLDP packets are discarded
after 120 seconds.
Default is 4
Values 2-10
Delay for LLDP initialization on any Sets the delay (in sec) for LLDP initializations on any
interface interface.
Default is 2 seconds
Value 1–10 seconds
Rate at which LLDP packets are Specify the rate at which LLDP packets are sent.
sent (secs) This parameter is used with the TX Hold multiplier
parameter to determine when LLDP packets are
discarded.
Default is 30 seconds
Values are 5–32768 seconds
Delay between successive LLDP Configure the amount of time in seconds that passes
frame transmissions (sec) between successive LLDP frame transmissions due
to changes in the LLDP local systems MIB.
Default is 30 seconds
Values are 1-8192 seconds
Selection for LLDP TLVs to send Select the LLDP TLVs to send.
• MAC PHY configuration and status TLV
• Port Description TLV
• System Name TLV
• Management Address TLV
Max number of LLDP neighbors Specify maximum number of LLDP neighbors for this
interface.
STP
Overview
Spanning Tree is a protocol that ensures a loop free topology for an Ethernet local area
[Link] loops are detected, the protocol blocks one of the paths so that the loop is
eliminated.
Feature Details / Application Notes
Spanning Tree Protocol (STP)—A layer 2 protocol which identifies and eliminates loops in
your network. It is detailed in the IEEE
RSTP Rapid Spanning Tree Protocol (RSTP)—RSTP (IEEE 802.1w) is inter-operable with
STP and takes advantage of point-to-point wiring and provides rapid convergence of the spanning
tree. Reconfiguration of the spanning tree can occur in less than 1 second
Multiple Spanning Tree Protocol (MSTP)—MSTP Originally defined in IEEE 802.1s and now
incorporated IEEE 802.1Q-2014, defines an extension to RSTP for use with VLANs. The Multi-
ple Spanning Tree Protocol configures a separate Spanning Tree for each VLAN group
and blocks all but one of the possible alternate paths within each Spanning Tree.
Mode • RSTP
• MSTP
• STP
Default is disabled
MST instance (Add, Edit, Configures MST instances for the region.
Delete) Each region can have multiple instances.
Map VLANs to an MST instance (0-63).
Security
User Accounts
Overview
In order to manage the IOLAN, users have to login. One of the methods which can be
used to login involves a username and password. Add names to the IOLAN’s internal
users’ database or if using an external authentication service such as RADIUS or
TACACS+, add the user names there. Some user account configuration parameters may
be different on some models or running software.
The user will be assigned one of two authorization levels.
• User EXEC—Able to perform most monitoring functions but not allowed to per-
form configuration of the IOLAN.
• Privileged EXEC—Is able to perform all supported operations on your IOLAN.
Another method you can use is two factor authentication which will require you to input a
verification code to be sent to you either as a SMS message or an email after you have
logged in. When using email for two factor authentication, some email programs require
that you set the parameter “allow less secure apps” within the email program in order to
receive SMS email messages. When using SSH with two factor authentication, you must
select Keyboard Interactive as the first method of Authentication.
User Sessions
The Sessions tab is used to configure specific connections for users who are accessing
the network through the IOLAN’s serial port. Users who have successfully logged into the
IOLAN (User Service set to DSprompt) can start up to four login sessions on network
hosts. Multiple sessions can be run simultaneously to the same host or to different hosts.
Users can switch between different sessions and also between sessions on the IOLAN
using Hotkey commands. Users with Admin or Normal privileges can define new sessions
and use them to connect to Network hosts; they can even configure them to start
automatically on login into the IOLAN.
Feature details / Application notes
Passwords can be up to 25 characters long. Blank passwords are also supported.
Passwords will be stored in the local database using MD5 encryption. This is a one way
encryption scheme. There is no way to extract the clear password from the stored value.
User password validation is performed by taking the password supplied by the user and
encrypting it using the MD5 algorithm and comparing the result to the value stored in the
database.
When viewing the text configuration of your IOLAN, the password will be displayed in its
encrypted form in ASCII printable characters. A user can cut and paste this information
into the configuration of another IOLAN. This allows the administrator to copy users from
one IOLAN to another without knowing what their passwords are.
Advanced User Session features are Serial Services, Advanced features such as session
length, the hot key for switching between sessions, callback etc, Lastly, Serial port Access
for assigning read, write and read/write access to your serial ports.
Users
Add, Edit, Delete User Specify a username.
Enable OpenVPN for this user Enable or disable OpenVPN for this user.
User Access Schedule Enter can access the IOLAN at these times.
Schedule 1–10
Enter Start time/End time/Days of the week
Two Factor authentication Enable Two Factor authentication. You must also
enable and configure email settings under System/
Email. See EMAIL for these settings.
Format • Email
Serial Configuration
Service • DSPrompt
• Telnet
• SSH
• Rlogin
• SLIP
• PPP
• TCP-Clear
• SSL-Raw
Advanced
Phone Number The phone number the IOLAN will dial to callback
the user (you must have set Enable Callback
enabled).
Restrictions enter the number without spaces.
Hot Key Prefix The prefix that a user types to control the current
session.
Data Options:
^a number—To switch from one session to another,
press ^a (Ctrl-a) and then the required session
number.
Sessions (1-4) You can configure up to four (4) sessions that the
user can select from to connect to a specific host
after that user has successfully logged into the
IOLAN (used only for serial ports configured for the
Terminal profile).
Port Specify the TCP port that you will connect to for this
session.
Terminology
AAA
Stands for Authentication, Authorization and Accounting. The three functions which are
associated with security.
Authentication
The act of verifying that a user is who they say they are.
Authorization
The act of assigning a valid user with a privilege level.
Accounting
The act of recording when users access your IOLAN to manage it. It also involves
recording when your IOLAN is re-booted.
RADIUS—Remote Authentication Dial-In User Service
A network protocol which provides AAA management for users or devices that connect to
your IOLAN.
TACACS+—Terminal Access Controller Access-Control System Plus
A network protocol developed by Cisco which provides AAA management for users or
devices that connect to your IOLAN.
Feature details / Application notes
AAA involves the following steps;
Defining methods for performing authentication, authorization and accounting.
Assign methods to be used for each management access method;
• Console
• Telnet/SSH (TTY access)
• Web browser
Authorization
Accounting
Accounting type Select the type of messages you want to log; None,
Start-Stop (login and log out) or Stop (logout).
802.1X
Accounting and Authentication
Authentication Select:
• None
• RADIUS
Accounting Select:
• None
• RADIUS
• TACACS+
System
Accounting Settings Select the type of messages you want to log; None,
Start-Stop (login and log out) or Stop (logout).
• None
• Start/Stop
AAA Management
HTTP/HTTPS Management
Number of PIN Tries Number of new two-factor PIN codes retries before
failing authentication.
Values are 1–10
Default is 3
Group
RADIUS
Overview
A RADIUS server can be used to provide authentication and accounting security for your
IOLAN. Your IOLAN supports User parameters that can be sent to the RADIUS server;
see Radius and TACACS+ for more information on the User parameters
Pre-requisites
Basic AAA has been configured on your IOLAN.
Terminology
RADIUS—Remote Authentication Dial-In User Service
A network protocol which provides AAA management for users or devices that connect to
your IOLAN.
AAA—Stands for Authentication, Authorization and Accounting. The three functions
which are associated with security
Feature details / Application notes
RADIUS can be used with your IOLAN to provide the following functions;
• Authenticate users logging into your IOLAN.
• Provide authorization information for users logging into your IOLAN.
• Returned via attribute "Service-Type"
• 1 (login) = User Exec
• 6 (administrative) = Privileged Exec
• Any other value is determined by User Exec.
• Provide accounting information for users and or devices logging in and out of
your IOLAN.
• Provide AAA functions for devices accessing a port configured for 802.1x.
The following ports are used by default;
• Authentication—1812
• Accounting—1813
• These can be changed on a per RADIUS host basis via configuration.
• User can assign different servers (if desired) for authentication, authorization
and accounting.
Radius
RADIUS Servers (Add, Edit, Delete)
Hostname or IPv4/IPv6
IPv4—A.B.C.D
IPv6—X:X:X:X::X
Authentication Port Set the UDP authentication port for the requests to
be received on the RADIUS host. Both your IOLAN
and RADIUS server must match.
Default is 1812.
Accounting Port Set the udp accounting port for the requests to be
received on the RADIUS host. Both your IOLAN and
RADIUS server must match.
Default is 1813.
Override Global RADIUS Settings You can override the global settings for the
following three parameters for this RADIUS host.
TACACS+
Overview
A TACACS+ server can be used to provide external security to your IOLAN.
Pre-requisites
Basic AAA has been configured on your IOLAN.
Terminology
TACACS+ - Terminal Access Controller Access-Control System Plus
A network protocol developed by Cisco which provides Authentication, Authorization and
Accounting services for users or devices that connect to your IOLAN.
TACACS+ is not backwards compatible with the much older TACACS protocol.
AAA
Stands for Authentication, Authorization and Accounting. The three functions which are
associated with security.
Feature details / Application notes
TACACS+ can be used with your IOLAN to provide the following functions.
• Authenticate users logging into yourIOLAN.
• Provide authorization information for users logging into your IOLAN.
• Provide accounting information for users logging in and out of your IOLAN.
• Provide accounting for devices connecting on 802.1x ports.
• The following ports are used by default; Authentication = 1812, Accounting =
1813
TACACS+
Secret (Global) Encryption key shared between the IOLAN and the
TACACS+ host.
IPv4 source interface Select the source interface from the drop-down list.
IPv6 source interface Select the source interface from the drop-down list.
TACACS+ Groups (Add, Remove) Add one or more TACACS+ server(s) to the group.
Group can be assigned to authentication,
authorization and/or accounting functions.
Firewall
Overview
A firewall is a system that provides network security by filtering incoming and outgoing
network traffic based on a set of user-defined rules. In general, the purpose of a firewall
is to reduce or eliminate the occurrence of unwanted network communications while
allowing all legitimate communication to flow freely.
Your IOLAN provides global settings for all source packet validation based on state
policies. In addition, your IOLAN allows you to configure firewall rules and zones which
can then be applied to interfaces within your IOLAN.
Source validation (strict, loose, disabled) for the following source packets types;
• IPv4 ping
• Broadcast Ping
• Handle IPv4 packet with source router option
• Handle received ICMPv6 redirected messages
• Handle IPv6 packet with routing ext-header
• Log IPv4 with invalid address
• Receive IPv4 redirect messages
• Send IPv4 redirected messages
• SYN Cookies
• RFC1337 TCP time-wait hazard protection
Incoming packet state;
• Established—the incoming packets are associated with an already existing
connection),
• Invalid—the incoming packets do not match any of the other states
• Related—the incoming packets are new, but associated with an already
existing connection.
These incoming packets can be:
Firewall
Source validation Policy for source validation by reversed path (IPv4
only).
• Disable—no source validation is
performed
• Loose—enable loose reverse path
forwarding as defined by RFC3704
• Strict—enable strict reverse path
forwarding as defined in RFC3704
Default is Disabled
Broadcast Ping Policy for handling IPv4 ICMP Echo and timestamps
requests.
Enable—system responses to broadcast IPv4
ICMP Echo and Timestamp requests
Disable—system does not respond to IPv4 Echo
and Timestamp requests
Default is disabled
Handle IPv4 packet with source Policy for handing IPv4 packets with source route
route option option.
Default is disabled
Handle received ICMPv6 Policy for handing received IPv6 ICMP redirect
redirected messages messages.
Default is disabled
Handle IPv6 packet with Policy for handling IPv6 packets with routing
routing ext-header extension header.
Default is disabled
Log IPv4 packet with invalid Policy for logging Ipv4 packets with invalid
address addresses.
Default is enabled
Receive IPv4 redirect messages Policy for handing received IPv4 ICMP redirect
messages.
Permits or denies IPv4 ICMP redirect messages.
Default is disabled
Send IPv4 redirected messages Policy for sending IPv4 only redirect messages.
Default is enabled
SYN cookies Policy for using TCP SYN cookies with IPv4.
Default is enable
State Policy
Firewall Rule
Log packets matching this rule. Log packets for default action.
Source Port (TCP/UDP) Accept packets from this source port (TCP/UDP)
port.
Destination Port (TCP/ Accept packets from this destination port (TCP/UDP)
UDP) port.
State • Established
• Invalid
• New
• Related
Fragment • fragment
• non fragment
IPSEC • ipsec
• non ipsec
Protocol • ah
• dccp
• dsr
• egp
• eigrp
• encap
• esp
• etherip
• ggp
• gre
• hmp
• icmp
• idpr
• igmp
• igp
• ip
• ipip
• ipv6
• ipv6-frag
• ipv6-icmp
• ipv6-nontxt
• ipv6-opts
• ipv6-route
• isis
• l2ip6-route
• isis
• l2tp
• manet
• mpls-in-ip
• narp
• ospf
• pim
• rdp
• roch
• rsvp
• sctp
• sdrp
• shim6
• skip
• tcp
Protocol • udp
• udplite
• vrrp
• xns-idp
• protocol number 0–255
IPv6 Firewall
Firewall Rule
Log packet hitting default Log the packets that match the default action.
action
Log packets matching this rule. Log packets for default action.
Traffic Match
Source Port (TCP/UDP) Accept packets from this source port (TCP/UDP)
port.
Destination Port (TCP/UDP) Accept packets from this destination port (TCP/UDP)
port.
State • Established
• Invalid
• New
• Related
Fragment • fragment
• non fragment
IPsec • ipsec
• non ipsec
Protocol • mpls-in-ip
• narp
• ospf
• pim
• rdp
• roch
• rsvp
• sctp
• sdrp
• shim6
• skip
• tcp
• udp
• udplite
• vrrp
• xns-idp
• protocol number 0–255
MAC Filtering
Overview
MAC filtering is a security method based on access control. Every hardware device has a
unique 48-bit MAC address, Using these MAC addresses, you can filter MAC addresses
to the list and either deny or that you don’t want on your network by adding them to the
filter list.
Feature details / Application notes
MAC address filtering should not be the only method of securing and protecting large
networks. Overall MAC filtering should be viewed as an more of an administration func-
tion rather then a security measure. MAC filtering is useful in filtering out unintentional or
intentional packet flooding thereby filtering out packets before inspection by firewall or
access-list filtering. In fact, MAC addresses are easily spoofed, making MAC address fil-
tering a poor method of security. Every packet from a client device includes their unique
MAC address, thereby enabling a third party with a spoofing program to pull off the MAC
address of the client device, thus enabling them to then change their own MAC address
to match that of the allow client device.
MAC Filtering
Name Enter the name of the access list.
MAC Addresses
Add
aabbccddeeff
ethernet interfaces
IPSEC
A Virtual Private Network (VPN) creates a secure, dedicated communications network
tunnelled through to another [Link] an IPsec tunnel becomes active, you are
requiring that all access to the IOLAN go through the configured IPsec tunnel(s), so you
must configure any exceptions first. for more information on exceptions) or you will not be
able to access the IOLAN through the network unless you are configured to go through
the IPsec tunnel (you can still access the IOLAN through the Console port).
You can configure the IOLAN for:
• a host-to-host Virtual Private Network (VPN) connection
• a host-to-network VPN connection
• a network-to-network VPN connection
• or host/network-to-router VPN connection (allowing serial devices connected to
the IOLAN to communicate data to a host/network).
IPSEC
Enable IPSEC Enable or disable IPSEC.
Connection Type When defining peer VPN gateways, one side should
be defined as Initiate (start) and the other as
Respond (listen). VPN gateways take longer when
both gateways are set to initiate, as both will
attempt to initiate the same VPN connection.
• Disable—no connection (default)
• Initiate—connection will be initiated by
the client
• Respond—the client will listen for a
connection
Any Local Address Use any local address for the tunnel or the IP
address of the IOLAN. You should select Any when
the IP address of the IOLAN is not always known
(for example, when it gets it’s IP address from
DHCP). When Any is used, a default gateway must
be configured under Routing/General Routing/
Default Gateway
Field Format is IPv4 address, IPv6 address, FQDN.
IKE Group Select an IKE group or use the default_ IKE group.
Authentication
Remote Identity The subnet mask of the local tunnel IPv4 network.
Keep the default value when you are configuring a
host-to-host VPN connection.
Default is [Link]
ESP Group Select the Default ESP group or select one from the
drop down list.
Local Address Family Select either IPv4 or IPv6 for this tunnel connection.
Default is IPv4
Remote Address Family Select either IPv4 or IPv6 for this tunnel connection.
Default is IPv4
IKE Groups
Dead Peer Detection (DPD) DPD is a method of detecting a dead Internet Key
Exchange (IKE) peer. This method uses IPsec traffic
patterns to minimize the number of messages
required to confirm the availability of a peer. DPD is
used to reclaim the lost resources in case a peer is
found dead.
Encryption • 3des
• aes128
• aes128gcm128
• aes256gcm128
• chacha20poly1305
Default is aes256
Hash • MD5
• SHA1
• SHA256
• SHA384
• SHA512
Default is SHA1
Compression for IPSEC Connection Use compression for this IPsec connection.
Perfect Forward Secrecy PFS on will improve security forcing a new key
exchange for each new session. Both sides of the
VPN tunnel must be able to support this option.
Enabling PFS by renewing keys more often will have
a little performance impact but provide further
security.
Client IP Pool Address Define the pool from which the clients are assigned
addresses
Pre shared key Enter the pre shared key for this connection. This
must match the server side.
OpenVPN
Overview
A Virtual Private Network (VPN) creates a secure, dedicated communications network
tunnelled through to another [Link] an IPsec tunnel becomes active, you are
requiring that all access to the IOLAN go through the configured IPsec tunnel(s), so you
must configure any exceptions first. for more information on exceptions) or you will not be
able to access the IOLAN through the network unless you are configured to go through
the IPsec tunnel (you can still access the IOLAN through the Console port).
You can configure the IOLAN for:
• a host-to-host Virtual Private Network (VPN) connection
• a host-to-network VPN connection
• a network-to-network VPN connection
• or host/network-to-router VPN connection (allowing serial devices connected to
the IOLAN to communicate data to a host/network).
Note: to create a connection, a tunnel must exist.
OpenVPN
Enable OpenVPN
Remote Addresses
Local Address Defines the remote tunnel local side and should be
a private IPv4 or IPv6 address or hostname.
IP Address (local)
Remote Address Defines the remote tunnel local side and should be
a private IPv4 or IPv6 address or hostname.
IP Address (remote)
Note: If using a tap device then this parameter will
be a netmask.
Ciphers • aes-128-cbc
• aes-128-gcm
• aes-192-cbc
• aes-192-gcm
• aes-256-cbc
• aes-256-gcm
• bf-cbc
• camellia-128-cbc
• camellia-192-cbc
• camellia-256-gcm
• cast-5-cbc
• des-cbc
• des-ede-cbc
• des-ede3-cbc
• desx-cbc
• rc2-40-cbc
• rc2-64-cbc
• seed-cbc
Verbosity (Logging Level) This sets the logging level for this connection and
messages will be prepended with %OVPN-XXX
where the XXX is the connection name in
uppercase.
• 0
• 1
• 2
• 3
• 4
• 5
• 6
• 7
• 8
• 9
• 10
• 11
PKI Certificate The PKI certificate used for this secure connection.
See Manage Files files to import keys and
certificates.
PKI Private Key The PKI private key used for this secure connection.
See Manage Files files to import keys and
certificates.
Manage Files
Import File
Method • Browser
• FTP
• HTTP
• HTTPS
• SCP
• SFTP
• TFTP
File Type • CA
• CERT
• Diffie-Hellman
• PKI Key
• Pre-Shared Secret Key
• Template
802.1X
Overview
802.1X defines a client-server-based access control and authentication protocol that
restricts unauthorized clients from connecting to a LAN through publicly accessible ports.
The authentication server authenticates each client connected to the IOLAN’s Ethernet
ports.
Pre-requisites
This feature requires a RADIUS host to perform the authentication for the device. The
configuration and setup of this host is beyond the scope of this document.
Restrictions / Limitations
Terminology
dot1x
This is a term that is used to refers to the 802.1x feature.
Supplicant
This refers to the device which is requesting access to the network.
Authenticator
Your IOLAN acts as the intermediary between the supplicant and the authenticating
server.
Authenticating Server
This is the server which provides the actual authentication for the supplicant.
EAP—Extensible Authentication Protocol
This is the protocol that is used to perform the basic authentication function.
For messages between the supplicant and the authenticator, this is encapsulated in
EAPoL. (EAP over LAN)
For messages between the authenticator and the authenticating server, the EAP is
encapsulated within the RADIUS messages.
MAB—MAC Authentication Bypass
This feature allows devices which do not support 802.1x to be authenticated on your
IOLAN. The authentication is done by using the MAC address of the device as both the
username and password. The authenticating server would need to have this information
configured as a valid user.
Feature details / Application notes
The RADIUS host needs to support EAP extensions in order to perform the 802.1x
authentication function Your IOLAN supports a RADIUS host as the authenticating server.
Your IOLAN can act as both a supplicant or an authenticator. You can configure this
option on a port-by-port basis.
The port is in an “unauthorized” state if the device attempting access has not
authenticated.
In this state the following applies;
• The port does not allow any traffic except for EAPOL.
• If the port is configured as a VOICE VLAN port, the port allows VoIP
traffic as well.
• Any static addresses configured are not written to your IOLAN until the
port is authorized.
802.1X Authenticator and Suppliant
Selecting the 802.1x role for a port.
802.1x enabled ports can perform one of two roles;
Authenticator
• Port will authenticate 802.1x supplicants which are
connected to it.
Supplicant
• The port will authenticate with its peer which acts as the 802.1x
authentication.
802.1X
Enable 802.1X authentication Select Enable to enable this feature.
Advanced
Mode
Authenticator Settings
Advanced Settings
Supplicant response timeout Sets the amount of time that the authenticator will
wait for the supplicant to reply to all 802.1x
messages.
Supplicant will time out after this period of waiting.
Range is 1-65535 seconds
Default is 30
Transmit timeout The tx-period timer is the time before a port will
begin the next method of authentication, and begin
the MAB process for non-authenticating devices.
Default is 30 seconds
Credential Profile (Add, Edit, Credential profiles are a username and password
Delete) which will be used by supplicants to authenticate on
802.1X authenticators. Creating a profile allows you
to assign this profile to individual ports as needed.
Methods • EAP-MD5
• EAP-MSCHAPV2
• EAP-GTC
• EAP-TLS
• TTLS-MSCHAP
• TTLS-MSCHAPV2
• TTLS-CHAP
• TTLS-EAP-MSCHAPv2
• TTLS-EAP-GTC
• PEAP-MD5
• PEAP-EAP-MSCHAPv2
• PEAP-GTC
LDAP
Overview
Lightweight Directory Access Protocol (LDAP) user authentication is the process of
validating a username and password combination with a directory server such MS Active
Directory, OpenLDAP or OpenDJ. LDAP directories are standard technology for storing
user, group, and permission information and serving that to applications in the
[Link] Directory Access Protocol (LDAP) must be integrated into
software as an authentication, authorization, and accounting (AAA) protocol alongside the
existing AAA protocols such as RADIUS and TACACS+. The AAA framework provides
tools and mechanisms such as method lists, server groups, and generic attribute lists that
enable an abstract and uniform interface to AAA clients irrespective of the actual protocol
used for communication with the AAA server. As such the IOLAN LDAP must support
authentication and authorization functions for AAA. Lightweight Directory Access Protocol
(LDAP) is an application protocol for querying and modifying directory services running
over TCP/IP. It is also used as a method of authenticating users. Microsoft Active
Directory is an LDAP-like directory service. It can be used for authenticating users in a
similar fashion to LDAP authenticating users.
LDAP
Server Name Enter a name for this LDAP server.
Base DN root-dn
bind root-dn
Secure Options
Trustpoint Name Configure the trustpoint name for this LDAP server.
Add a LDAP server Select a LDAP server from the drop-down list.
Administration
Your IOLAN provides a comprehensive range of management services.
Administration services include;
• Software Management—including checking for updates, viewing software
versions, automatically updating software, and creating backup software.
• Configuration—including backing up/restoring your configuration and booting
from a configuration file using DHCP/BOOTP.
• Import Keys and Certificate—including importing and exporting of HTTPS,
Server, SSH and SSL host/client/user keys and certificates.
• Managing Flash/NVRAM Files—including exporting and importing files to/
from flash.
• Reboot/Reset—, resetting to factory defaults and shutting down your .
Note: Some administrator services may be different on some models or running software.
Software Management
This section describes how to manage the Perle IOLAN software (images) files.
Terminology
• Startup software is the software that is stored in flash and will run the next time
the IOLAN is rebooted.
• Currently Running software is the actual software image that is executing on
your IOLAN.
• Backup software is the software that is stored in backup. A new backup is
created in the IOLAN every time the software is updated.
• Revert to backup software will delete your present software and use the saved
backup software at next reboot.
• SCP (Secure Copy Protocol) uses Secure Shell (SSH) for data transfer,
authentication and encryption.
• TFTP (Trivial File Transfer Protocol) is a common File Transfer Protocol which
allows a client to get a file from or put a file onto a remote host)
• SFTP (Secure File Transfer Protocol) is a common File Transfer Protocol which
allows a client to get a file from or put a file onto a remote host
• FTP is similar to TFTP, but requires user authentication
Automatically Check for updates option—if enabled, the IOLAN checks the Perle
repository every 7 days then informs you if your IOLAN needs a software update.
Check now option—immediately checks the Perle repository for new software updates.
If a new software image is found:
• it can be downloaded directly from the Perle repository using the Update Soft-
ware button/Direct Download feature
• it can be copied directly from our website using TFTP, SFTP, FTP, HTTP, or
HTTPS and saved to an external server to be updated to your IOLAN at a later
date. Internet access is required to obtain the latest software images from the
Perle web site at [Link]
The download function can be cancelled at any time during the download, and the IOLAN
will use the current software image.
Download configuration file using Specify the name of the BOOTP server that contains
DHCP/BOOTP the BOOTP file.
Server CA Certificate
A CA certificate is used when you use HTTPS to transfer a file to an HTTPS host. You
configure the CA certificate with a name known as a [Link] CA certificate validates
certificates presented by the HTTPS host. It can also be used to identify a RADIUS
authentication server to your IOLAN when the port is acting as an 802.1x supplicant.
• Browser
• FTP
• HTTP
• HTTPS
• SCP
• SFTP
• TFTP
Type • PEM
• PKCS#12
Method • Browser
• FTP
• HTTP
• HTTPS
• SCP
• SFTP
• TFTP
Import Options
Method • Browser
• FTP
• HTTP
• HTTPS
• SCP
• SFTP
• TFTP
SSH Hostname/IP address Enter the host name or IP address where the SSH host
key resides.
Method • Browser
• FTP
• HTTP
• HTTPS
• SCP
• SFTP
• TFTP
Method • Browser
• FTP
• HTTP
• HTTPS
• SCP
• SFTP
• TFTP
Type • PEM
• PKCS#12
Method • Browser
• FTP
• HTTP
• HTTPS
• SCP
• SFTP
• TFTP
Type • PEM
• PKCS#12
Passphrase Enter the passphrase to use with your SSL client key.
Import SSL Client Key Select the SSL Client Key to be imported into the
IOLAN.
Method • Browser
• FTP
• HTTP
• HTTPS
• SCP
• SFTP
• TFTP
Type • PEM
• PKCS#12
Import SSL Client Key Select the SSL Client Certificate to be imported into
the IOLAN.
Password Encryption
Manage Password Encryption Key
Default Key Currently Encrypt current passwords with new encryption keys.
in use You can generate, delete, upload and export [Link]
default key is currently in use.
• Generate new key
• Upload key
Reboot/Reset
Overview
Enables you to reboot the IOLAN based on:
• reboot now
• reboot in hours/minutes
Reboot/Reset
Reboot Reboot now
Shutdown
Shutdown This will shutdown the IOLAN. The Reset button will
power the IOLAN back up.
• Shutdown now
Trueport
This chapter provides information on TruePort Redirect utility.
Trueport is a com port redirector utility for the IOLAN. It can be run in two modes:
• Trueport Full Mode—This mode allows complete device control and oper-
ates exactly like a directly connected serial port. It provides a complete COM
port interface between the attached serial device and the network.
• TruePort Lite mode—This mode provides a simple raw data interface
between the device and the network. Although the port will still operate as a
COM port, control signals are ignored. In this mode, the serial communications
parameters must be configured on the IOLAN.
You use TruePort when you want to connect extra terminals to a server using the IOLAN
rather than a multi-port serial card. TruePort is especially useful when you want to improve
data security, as you can enable an SSL/TLS connection between the TruePort host port
and theIOLAN. When run on UNIX, TruePort allows you to print directly from a terminal to
an attached printer (transparent printing). You can also remap the slow baud rate of your
UNIX server to a faster baud rate.
For a complete list of the supported operating systems, see the Perle website.
PerleView
Managing large numbers of deployed network equipment poses unique challenges to the
network administrator. It requires a centralized solution with efficiencies found in a
platform that uses standard client tools, databases and protocols.
PerleVIEW Device Management System is an Enterprise-grade, multi-user, Windows
server-based centralized management package that simplifies the configuration, software
upgrade, administration, monitoring, and troubleshooting of devices managed by
Perleview in medium to large-scale deployments. Network Administrators, using their
Internet Browser, can securely access PerleVIEW and manage 10’s, 100’s or thousands
of Perle supported devices from a centralized server.
The following procedure will allow you to use the Modbus remapping feature:
Create a configuration file
• The file must be called "modbus. remap"
• One translate rule per line
• The fields on a line are separated by a comma
Line format for one UID is:
• port,master_uid,slave_uid
• port: is the port number that the slave is connected to
• master_uid: is the UID that the TCP Modbus Master uses
• slave_uid: is the UID that the Modbus slave uses
Line format for UID ranges is:
• port,master_start-master_end,slave_start-slave_end
• port: is the port number that the slave is connected to
• master_start: is the first master UID in the range
• master_end: is the last master UID in the range
• slave_start: is the first slave UID in the range
• slave_end: is the last slave UID in the range
Configuring the Modbus UID Remapping Feature
1. On the serial port Modbus Gateway, configure Modbus slave. Configuration parame-
ters such as “UID range” and UID Address Mode will be ignored in this mode of oper-
ation.
2. Download the "modbus_remap" file to the flash using the copy command.
3. With the WebManager use the Administration/Manage Flash Files page.
Key-
Full Name Exchange Auth Encryption Key-Size HMAC
EDH-DSS-DES-CBC3-SHA Kx=DH Au=DSS Enc=3DES 168 SHA1
Diagnostics
These diagnostic tools are available on your IOLAN.
Email
The email test utility allows you to test the email function.
Specify the email address you want to send the email message to. If successful, you will
receive an email with the heading of ” Test Message from “your host name” with a body
text of “Hello World”.
Ping
The ping utility accepts the following parameters.
• Host (this is the destination host)
• Specified as;
• Name (resolvable via DNS or host table)
• IPv4 address
• IPv6 address
• Count (number of repetitions)
• 1–2147483647
• Datagram size
• Valid range is 36–8024 bytes
• Default is 56 bytes
• Data pattern
• Hexadecimal pattern
If a name is specified, the utility attempts to resolve the name to an IP address. If
unsuccessful, an error message is given. Next, the utility attempts to send the ICMP
message to the destination host. If this is received by the host, the host responds to the
sender. The send / response sequence is considered one repetition of the ping
command. Each repetition is timed. This information is displayed for each successful
request. After the requested number of repetitions is completed, the utility provides a
summary of how many requests were sent, how many responses were received and the
min/avg/max round-trip times.
Traceroute
This utility displays each hop on the path to the final destination including the time it took
to reach that hop and return. If the destination is not reachable, the utility displays how far
the message travelled. Traceroute displays the path taken by a packet travelling from the
host on which the command is execute to a destination normally reachable via IP routing,
It uses ICMP messages to do this. This utility helps identify at what point the routing to the
destination failed This information can be used to provide Perle Technical support
information on your IOLAN.
The traceroute utility accepts a single parameter which is the destination address.
This parameter is specified as;
• Name
• IPv4
• IPv6
If a name is specified, the utility resolves the name to an IP address. If unsuccessful, an
error message is given.
It then attempts to communicate with the next hop in the path (i.e. default router/
gateway). If this is successful, it will attempt to communicate with the next hop in the path.
This is repeated until it either reaches the end destination or fails to reach one of the hops
on the way. As each attempt is made, the utility displays the results of that attempt—
including the timing information.
The utility displays an "*" to indicate a hop is unreachable.
Radius
RADIUS can be used strictly for external authentication, it can also be used to configure
line and user parameters. Therefore, when a user is being authenticated using RADIUS,
it is possible that the user’s configuration is a compilation of the parameters passed back
from RADIUS, the IOLAN if the user has also been set up as a local user in the IOLAN,
and the Default User’s parameters for any parameters that have not been set by either
RADIUS or the user’s local configuration.
5 NAS-Port Response If the user is connected to a physical port then the port number of the port is sent. If the user
is connected to the IOLANR itself then a port number of 0 is sent.
6 Service-Type Response Indicates the service to use to connect the user to the IOLANR. A value of 6 indicates
administrative access to the . Supported values are:
1—Login
3—Callback-Login
Equivalent to the IOLAN User Service set by Type 15, Login-
Service.
2—Framed
4—Callback-Framed
Equivalent to the IOLAN User Service set by Type 7, Framed-
Protocol.
7—NAS prompt
9—Callback NAS-prompt
Equivalent to IOLAN User Service DSLogin.
6—Administrative User
11—Callback Administrative User
Equivalent to IOLAN User Service DSLogin and the User gets
Admin privileges.
7 Framed-Protocol Response The link layer protocol to be used by this user. Determines the User Service when Service-
Type is set to Framed or Callback-Framed. Supported values are:
1—PPP
2—SLIP
8 Framed-IP-Address Response The IP Address to be assigned to this user for PPP or SLIP.
9 Framed-IP-Netmask Response The subnet to be assigned to this user for PPP or SLIP.
Table 0–1
Type Name Description
12 Framed-MTU Response Attribute indicates the Maximum Transmission Unit (MTU) to be configured for the user,
when it is not negotiated by some other means such as PPP.
13 Framed-Compression Response Indicates a compression protocol to be used for the PPP or SLIP link. Supported value is:
1—Van Jacobson TCP/IP compression.
14 Login-Host Response Indicates the host with which the user can connect to when the Service-Type is set to 1
(Login) or 3 (Callback-Login).
15 Login-Service Response Indicates the User Service to use to connect the user a a host. Supported values are:
0—Telnet
1—Rlogin
2—TCP Clear
5—SSH
6—SSL Raw
16 Login-TCP-Port Response Indicates the TCP port with which the user is to be connected when the Service-Type is set to
1 (Login) or 3 (Callback-Login).
19 Callback-Number Response Specifies the callback phone number. This is the same implementation as 20 (Callback-ID),
but takes precedence if 20 is set.
20 Callback-ID Response Specifies the callback phone number. This is the same implementation as 19 (Callback-
Number), but 19 takes precedence if both are set.
22 Framed-Route Response When the PPP IPv4 interface comes up, the IOLAN will add routes to the user’s PPP
interface in the same order they were received
25 Class Response Received attributes are send in the Accounting Reply messages.
26 Vendor-Specific Response Perle’s defined attributes for line access rights and user level.
Line Access Rights for port n (where n is the line number):
Name: Perle-Line-Access-Port-n
Type: 100 + n
Data Type: Integer
Value: Disabled (0), ReadWrite(1), ReadInput(2), ReadInputWrite (3), ReadOutput (4),
ReadOutputWrite (5), ReadOutputInput (6), ReadOutputInputWrite (7)
Name: Perle-User-Level
Type: 100
Data Type: Integer
Value: Admin(1), Normal(2), Restricted(3), Menu(4)
Name: Perle-Clustered-Port-Access
Type: 99
Data Type: Integer
Value: Disabled(0), Enabled(1)
27 Session-Timeout Response Maximum number of seconds the user will be allowed to stay logged on.
28 Idle-Timeout Response Use this timer to close a connection because of inactivity. When the Idle-Timeout expires, the
IOLAN will end the connection. The maximum value is 4294967 seconds (about 49 days). A
value of 0 (zero) means the Idle-Timeout will not expire, so the connection is permanently
open.
31 Calling-Station-Id Response For reverse telnet and reverse ssh the IP address of the client will be sent. All other server
type do not send this field.
32 NAS-Identifier Response If the identifier is configured then this field will be sent.
61 NAS-Port-Type Response For reverse telnet and reverse ssh connections, a type of Virtual (5) will be sent. For a PPP
connection type a type of Async (0) will be sent. For all direct connect service types a type of
Async (0) will be sent.
Table 0–1
Type Name Description
95 NAS-IPv6-Address Response The IPv6 address of the IOLAN.
96 Framed-Interface-Id Response The remote IPv6 interface identifier for the remote end of the PPP link.
98 Login-IPv6-Host Response8 For LOGIN and CALLBACK service types, the IPv4 address of the login host is sent to the
RADIUS accounting host.
99 Framed-IPv6-Route Response When the PPP IPv6 interface comes up, the IOLAN will add routes to the user’s PPP
interface in the same order they were received.
Accounting Message
This section describes the attributes which will be included by the IOLAN when sending
an accounting message to the RADIUS server.
Type Name Description
1 User-Name The name of the user to be authenticated.
5 NAS-Port If the user is connected to a physical port then the port number of the port is sent. If the user is
connected to the IOLAN itself then a port number of 0 is sent.
6 Service-Type Indicates the service to use to connect the user to the IOLAN. A value of 6 indicates administrative
access to the IOLAN. Supported values are:
1—Login
3—Callback-Login
Equivalent to the User Service set by Type 15, Login-Service.
2—Framed
4—Callback-Framed
Equivalent to the User Service set by Type 7, Framed-Protocol.
7—NAS prompt
9—Callback NAS-prompt
Equivalent to User Service DSPrompt.
6—Administrative User
11—Callback Administrative User
Equivalent to User Service DSPrompt and the User gets Admin privileges.
14 Login-IP-Host For LOGIN and CALLBACK service types, the IPv4 address of the login host is sent to the RADIUS
accounting host.
31 Calling-Station-Id For reverse telnet and reverse ssh the IP address of the client will be sent. All other server type do not
send this field.
40 Acct-Status-Type Indicates if this is the beginning or end of a session. Supported values are: 1 = Start 2 =Stop.
42 Acct-Input-Octets Number of bytes which were received from the user during this session.
43 Acct-Output-Octets Number of bytes where were transmitted to the user during this session.
44 Acct-Session-ID A string which identifies the session. The same string must be used in the start and stop messages.
45 Acct-Authentic Indicates how the user was authenticated. Supported values are: 1 = Local 2 = RADIUS.
46 Acct-Session-Time Number of seconds for which the user has been connected to a specific session.
47 Acct-Input-Packets Number of packets which were received from the user during this session.
48 Acct-Output-Packets Number of packets which were transmitted to the user during this session.
61 NAS-Port-Type For reverse telnet and reverse ssh connections, a type of Virtual (5) will be sent. For a PPP connection
type a type of Async (0) will be sent. For all direct connect service types a type of Async (0) will be sent.
77 Connect-Info .For reverse telnet, reverse ssh and direct serial connections the serial port baud rate is send to the
RADIUS accounting server.
98 Login-IPv6-Host For LOGIN and CALLBACK service types, the IPv4 address of the login host is sent to the RADIUS
accounting host.
Callback-ID Combination of the Enable Callback and Phone Number fields under User, Advanced
settings.
# Perle Extensions
..........
TACACS+
Although TACACS+ can be used strictly for external authentication, it can also be used to
configure Serial Port and User parameters. Therefore, when a user is being authenticated using
TACACS+, it is possible that the user’s configuration is a compilation of the parameters passed
back from the TACACS+ authentication server, the User’s IOLAN parameters if the user has
also been set up as a local user in theIOLAN, and the Default User’s parameters for any
parameters that have not been set by either TACACS+ or the User’s local configuration.
User and Serial Port parameters can be passed to theIOLAN after authentication for users
accessing the IOLAN from the serial side and users accessing the IOLAN from the Ethernet side
connections.
Service = EXEC
{
priv-lvl = x # x = 12-15 (Admin)
# x = 8-11 (Normal)
Perle_User_Service = x # x = 0 Telnet
# x = 1 Rlogin
# x = 2 TCP_Clear
# x = 3 SLIP
# x = 4 PPP
# x = 5 SSH
# x = 6 SSL_RAW
# If not specified, command prompt
service = telnet
{
addr = x.x.x.x # ipv4 or ipv6 addr
port = x # tcp_port #
}
service = rlogin
{
addr = x.x.x.x # ipv4 or ipv6 addr
}
service = tcp_clear
{
addr = x.x.x.x # ipv4 or ipv6 addr
port = x # tcp_port #
}
service = slip
{
routing=x # x = true (Send and Listen)
# x = false (None)
addr = x.x.x.x # ipv4 addr
}
service = ppp
{
routing=x # x = true (Send and Listen)
# x = false (None)
addr = x.x.x.x # ipv4 or ipv6 addr
ppp-vj-slot-compression = x # x =true or false
callback-dialstring = x # x = number to callback on
}
service = ssh
{
addr = x.x.x.x # ipv4 or ipv6 addr
port = x # tcp_port #
}
service = ssl_raw
{
addr = x.x.x.x # ipv4 or ipv6 addr
port = x # tcp_port #
}
Perle_Line_Access_# # = port number For the specified line, provides the User’s Line Access
0 (Disabled) rights.
1 (ReadWrite)
2 (ReadInput)
3 (ReadInputWrite)
4 (ReadOuptut)
5 (ReadOutputWrite)
6 (ReadOutputInput)
7 (ReadOuputWrite)
Note: Users who are accessing the IOLAN through WebManager and are being authenticated
by TACACS+ must have the Admin privilege level and the TACACS+ service level must
be set to EXEC.
Trueport Profile
The following features are not compatible when using the Data Logging feature.
• Allow Multiple Hosts to connect
• Connect to Multiple Hosts
• Monitor DTR-DSR
• Signals high when not under Trueport client control
• Message of the day
• Session timeout
RESTful API
You can use the Perle’s RESTful API to manage your IOLAN as an alternative to
configuring and managing selected features using the Command Line Interface (CLI),
WebManager, or our other configuration methods.
See Initial Setup if configuring your IOLAN for the first time.
Your IOLAN needs to have an IP address and REST API enabled before you can use the
RESTful API feature.
For Example:
1. Open from the Visual Studio Code, select File -> Open file, then select the system-
general file from the list of available api files.
2. The file is loaded into Visual Studio Code.
3. Change the @server = localcode:8000/api/v1.1/managed-devices/ line to reference
your own IP IOLAN address.
4. Change the {“myUserName”:”admin”,”myPassword”:”Perlelyn1#”} line to your own
username and password.
5. Once you have changed the username and password, click on the grayed out “Send
Request” link just above the “Post [Link] You will see the result on the
right hand panel—if the request was successful you will see the response code 200
OK.
6. For example to get the current time and date from your IOLAN, select “Send
Request”, the result will be displayed in the right column on the screen.
Appendix 1 - Regions
The following is the complete list of the regions which are supported on the WiFi interface.
• Canada
• United Kingdom
• US (default)
• Andorra
• United Arab Emirates
• Afghanistan
• Anguilla
• Albania
• Armenia
• Argentina
• American Samoa
• Austria
• Australia
• Aruba
• Azerbaijan
• Bosnia and Herzegovina
• Barbados
• Bangladesh
• Belgium
• Burkina Faso
• Bulgaria
• Bahrain
• Saint Bartholemy
• Bermuda
• Brunei
• Bolivia
• Brazil
• Bahamas
• Bhutan
• Belarus
• Canada
• Central Africa Republic
• Cote d’lvoire
• Chile
• China
• Colombia
• Costa Rica
• Cuba
• Christmas Island
• Cyprus
• Czech Republic
• Germany
• Denmark
• Dominica
• Dominican Republic
• Algeria
• Ecuador
• Estonia
• Egypt
• Spain
• Ethiopia
• Finland
• Micronesia
• France
• France
• United Kingdom
• Grenada
• Georgia
• French Guiana
• Ghana
• Greenland
• Greece
• Guatemala
• Guam
• Guyana
• Hong Kong
• Honduras
• Croatia
• Haiti
• Hungary
• Indonesia
• Ireland
• Israel
• India
• Iran
• Iceland
• Italy
• Jamaica
• Jordan
• Japan
• Kenya
• Cambodia
• Saint Kitts and Nevis
• North Korea
• South Korea
• Cayman Islands
• Kazakhstan
• Lebanon
• Saint Lucia
• Liechtenstein
• Sir Lanka
• Lesotho
• Lithuania
• Latvia
• Morocco
• Monaco
• Moldova
• Montenegro
• Saint Martin
• Marshall Islands
• Macedonia
• Mongolia
• Macau
• Northern Mariana Islands
• Mauritania
• Malta
• Mauritius
• Maldives
• Malawi
• Mexico
• Malaysia
• Nigeria
• Nicaragua
• Netherlands
• Norway
• Nepal
• New Zealand
• Oman
• Panama
• Peru
• French Polynesia
• Papua New Guinea
• Philippines
• Pakistan
• Poland
• Saint Pierre and Miquelon
• Puerto Rico
• Portugal
• Palau
• Paraguay
• Reunion
• Romania
• Serbia
• Russia
• Rwanda
• Saudi Arabia
• Sweden
• Singapore
• Slovenia
• Slovakia
• Senegal
• Suriname
• El Salvador
• Syria
• Turks and Caicos Islands
• Chad
• Togo
• Thailand
• Tunisia
• Turkey
• Trinidad and Tobago
• Taiwan
• Tanzania
• Ukraine
• Uganda
• United States
• Uruguay
• Uzbekistan
• Saint Vincent and the Grenadines
• Venezuela
• U.S. Virgin Islands
• Vietnam
• Vanuatu
• Wallis and Futuna
• Samoa
• Yemen
• Mayotte
• South African
• Zimbabwe