Lantronix SCS100/200/400 SCS100 / SCS200 / SCS400 - User Guide - Page 9

Protocol Support, SNMP Simple Network Management Protocol

Page 9 highlights

SCS100/200/400 User Guide 1: Introduction to the SCS Family Note: See Using Menu/Connection Commands for information on how to send intentional breaks to connected equipment. Protocol Support The SCS supports the TCP/IP network protocol as well as: SSH, Telnet, and Rlogin for connections in and out of the SCS DNS and WINS for text-to-IP address name resolution SNMP for remote monitoring and management FTP for file transfers and firmware upgrades TFTP for firmware upgrades BOOTP, RARP, and DHCP for IP address assignment HTTP for easy browser-based configurations NTP for time synchronization and authentication NAT for enabling private networks to share a connection to the Internet. SSH (Secure Shell): A secure transport protocol based on public-key cryptography. Telnet: A terminal protocol that provides an easy-to-use method of creating terminal connections to any network host supporting Telnet. Rlogin: Allows you to initiate a TCP/IP login session. DNS (Domain Name Servers): Lets a network nameserver translate text node names into numeric IP addresses. SNMP (Simple Network Management Protocol): Commands that allow system administrators to monitor and manage nodes on a LAN (Local Area Network) and respond to queries from other network hosts. One community name can be configured with read/write access. Refer to the SCS Reference Manual for SNMP configuration instructions. BOOTP, RARP, and DHCP: Methods for automatically assigning an IP address and network settings. NTP (Network Time Protocol): Used to synchronize time on networked computers and equipment. NAT (Network Address Translation): Allows private networks to share a single connection to the Internet. With Port Mapping, specific IP Ports can be mapped from the Internet to a private IP address and port. 1-2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61

SCS100/200/400 User Guide
1: Introduction to the SCS Family
Note:
See
Using Menu/Connection Commands
for information on how to send
intentional breaks to connected equipment.
Protocol Support
The SCS supports the TCP/IP network protocol as well as:
±
SSH, Telnet, and Rlogin for connections in and out of the SCS
±
DNS and WINS for text-to-IP address name resolution
±
SNMP for remote monitoring and management
±
FTP for file transfers and firmware upgrades
±
TFTP for firmware upgrades
±
BOOTP, RARP, and DHCP for IP address assignment
±
HTTP for easy browser-based configurations
±
NTP for time synchronization and authentication
±
NAT for enabling private networks to share a connection to the Internet.
SSH (Secure Shell):
A secure transport protocol based on public-key cryptography.
Telnet:
A terminal protocol that provides an easy-to-use method of creating terminal
connections to any network host supporting Telnet.
Rlogin:
Allows you to initiate a TCP/IP login session.
DNS (Domain Name Servers):
Lets a network nameserver translate text node names
into numeric IP addresses.
SNMP (Simple Network Management Protocol):
Commands that allow system
administrators to monitor and manage nodes on a LAN (Local Area Network) and
respond to queries from other network hosts. One community name can be configured
with read/write access. Refer to the
SCS Reference Manual
for SNMP configuration
instructions.
BOOTP, RARP, and DHCP:
Methods for automatically assigning an IP address and
network settings.
NTP (Network Time Protocol):
Used to synchronize time on networked computers and
equipment.
NAT (Network Address Translation):
Allows private networks to share a single
connection to the Internet. With Port Mapping, specific IP Ports can be mapped from the
Internet to a private IP address and port.
1-2