Line Service Commands

ipaddr-neg

Specifies whether or not IP address negotiation will take place. IP address negotiation is where the IOLAN allows the remote end to specify its IP address. The default value is Off. When On, the IP address specified by the remote end will be used in preference to the Remote IP Address set for a Line. When Off, the Remote IP Address set for the Line will be used.

ipv6-global-network-prefix

You can optionally specify an IPv6 global network prefix that the IOLAN will advertise to the device at the other end of the PPP link. Enter the IPv6 network prefix in the

aaaa:bbbb:cccc:dddd:: format.

ipv6-local-interface

The local IPv6 interface identifier 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. Do not use the IOLAN’s (main) IP address in this field; if you do so, routing will not take place correctly. The first 64 bits of the Interface Identifier must be zero, therefore, ::abcd:abcd:abcd:abcd is the expected format.

ipv6-remote-interface

The remote IPv6 interface identifier 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

PPPparameter 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-Interface-IDis set in the RADIUS file, the IOLAN will use the value in the RADIUS file in preference to the value configured here. The first 64 bits of the Interface Identifier must be zero, therefore, ::abcd:abcd:abcd:abcd is the expected format.

lipaddr

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 192.101.34.146, your local IP address can be 192.101.34.145. Do not use the IOLAN’s (main) IP address in this field; if you do so, routing will not take place correctly.

magic-neg

Determines if a line is looping back. If enabled (On), random numbers are sent on the link. The random numbers should be different, unless the link loops back. The default is Off.

mru

The Maximum Receive Unit (MRU) parameter specifies the maximum size of PPP packets that the IOLAN’s port will accept. Enter a value between 64 and 1500 bytes; for example, 512. The default value is 1500. If your user is authenticated by the IOLAN, the MRU value will be overridden if you have set a Framed MTU value for the user. If your user is authenticated by RADIUS and the RADIUS parameter Framed-MTUis set in the RADIUS file, the IOLAN will use the value in the RADIUS file in preference to the value configured here.

nak-retry

The maximum number of times a configure NAK packet will be re-sent before the link is terminated.

82

IOLAN SDS/SCS/STS/MDC CLI Reference Guide, Version 3.7

Page 82
Image 82
Perle Systems SDS Ipaddr-neg, Ipv6-global-network-prefix, Ipv6-local-interface, Ipv6-remote-interface, Lipaddr, Magic-neg

SDS, MDC specifications

Perle Systems is a leading provider of connectivity solutions, renowned for its robustness and reliability in networking hardware. Among its expansive product offerings, the MDC (Multiport Device Converter) and SDS (Serial Device Server) stand out as pivotal solutions for industries requiring seamless data communication and device management.

The Perle MDC serves as a powerful multi-port device converter, providing the ability to connect multiple serial devices to a computer network without needing a separate connection for each device. This is particularly useful in environments with limited computing resources or high device density, such as railways, manufacturing plants, or remote field operations. It is designed to convert serial communication, which is commonly used in legacy devices, into Ethernet/IP or TCP/IP protocols, ensuring that older devices can integrate into modern networks.

Main features of the MDC include its robust design for industrial environments, support for a variety of serial protocols, and multiple device connections. It supports data rates of up to 115200 bps and provides easy monitoring and configuration via a web-based interface. Additionally, the MDC incorporates advanced security features including SSL and SSH encryption, ensuring data integrity and protection against unauthorized access.

On the other hand, the Perle SDS model exemplifies advanced serial device hosting capabilities, allowing users to connect Ethernet networks to serial devices. It acts as a bridge, enabling remote devices to be configured and managed over IP networks. The SDS series is known for its versatility, supporting a range of serial communication protocols, including RS-232, RS-422, and RS-485, making it suitable for various applications such as point-of-sale systems, industrial automation, and remote monitoring.

The SDS boasts several characteristics that enhance its functionality, such as automatic device discovery, real-time monitoring, and local or cloud-based management options. Its feature set also includes traffic management capabilities, allowing the optimization of device communication by controlling the flow of data, which is critical for applications requiring high reliability and low latency.

Both the MDC and SDS benefit from a strong emphasis on ease of deployment and management. They support a range of network topologies, facilitating seamless integration into existing infrastructures. Furthermore, these devices are backed by Perle Systems' reputation for customer support and a commitment to ongoing innovation, ensuring that organizations can rely on these solutions for future growth and technological advancement.