Syntax
connect terminate <connect ID> <one or more parameters> Parameters
You must specify connection ID (inbound ID) to terminate an outbound connection. Use show connection to view the current connections and their ID.
Examples
connect terminate 3
connect terminate 3 outbound 1 Description
Terminates a user connection to the SLM session. Use show connection to view the current
connections and IDs.
show connection Syntax
show connection Description
To best use the SLM, review the setup and configuration process outlined below before undertaking the tasks detailed in Chapters 6-10.
Note: Throughout this user guide, the term "administrator" means the person using the
sysadmin user name and those members of the Administrators Account Group permitted
to perform the task.
Following is an overview of the tasks the administrator and other users perform to configure and use the SLM, in roughly the order performed.
The typical user employs SLM as follows:
Searches for Lantronix Devices and other Ethernet devices.
Connects by browser, SSH, or Telnet to Lantronix Devices and other Ethernet devices, and
additionally, by secure channel to SLCs and other SLMs.
Accesses notes and logs about the management devices and their ports.
The administrator performs the following configuration and maintenance activities:
Updates SLM firmware and configurations. Configures properties of the log files.
Manages syslog, portlog, auditlog, upgrade, configuration, session, and trap files. Configures an SNMP agent.
Configures and views events.
Updates firmware on Lantronix Ethernet devices (SLM, WiBox, UDS, Spider, SLP, and SLC).
Step 1: Configure Network Settings
The administrator enters the network settings that enable the SLM to access the network, manages modems, and sets up IPv4 filter sets
Step 2: Define Authentication Methods
The SLM supports LDAP, RADIUS, NIS, Kerberos, TACACS+, SecurID, and SSH public key authentication. Remote authentication is optional. The administrator can opt to use only local authentication.
Step 3: Set Up User Account Groups and Accounts
The SLM comes with four types of account groups: Administrators, Ethernet Device, Managed Device, and Menu Only users. Administrators create account groups of each type (except Administrators) and create and assign accounts to the account groups.
The administrator can create additional administrator accounts that have the following rights enabled or disabled:
Network Settings Authentication
Services (e.g., SNMP and syslog, Date and Time, and Maintenance) Device Management
Accounts Events
File Management
Step 4: Auto-Detect Devices
The administrator uses auto-detection methods to find Lantronix devices and other devices on the network and to add them to the SLM database for the SLM to manage. There is no need to add a device manually, although that option is available. Currently, auto-detect supports Lantronix Discovery Protocol (LDP) for SLCs and other Lantronix devices, the Lantronix SCS05/20 device discovery protocol, and SNMP for SLPs, SLKs, and all other Ethernet devices.
Step 5: Associate Account Groups with Ethernet and Managed
Devices
Once the SLM administrator adds account groups and Ethernet devices, the next step is to associate the account groups with the Ethernet devices and managed devices (devices attached to Ethernet device's ports) to which they will have access. In the case of SLC/SCS Console Servers, permissions also allow specific account groups listen-only access or full bidirectional control.
Step 6: Manage Devices
The user selects Ethernet devices from the menu's tree structure or enters search criteria to search for Ethernet devices, ports, and managed devices. The user then views port settings (if the device has ports) and can connect to an attached device through a web browser or the CLI. For ease of communication and management, managed devices that link together device ports (e.g., SLC, SCS, SLK, and SLP) may be created or "fused'' together. Users may then manage all of these ports through the managed device on a single web page. In the case of an SLC or another SLM, the user can make a secure channel connection through which the SLM forwards user permission information so a secondary login is not required. For SLCs, once a secure channel has been set up, the user can make a web channel connection.
Step 7: Maintain the SLM
The SLM enables the following maintenance tasks:
Auto-Save: The administrator saves the configuration of one SLM on another SLM. If there is a need, the second SLM can "become" the first SLM.
Configuration Save and Restore: The administrator saves and restores system configurations, providing rapid recovery of inadvertent configuration changes.
User Log (Audit Trail): Every successful login, logout, and command on the command line interface and web is logged into a database table. The administrator reads this information from the CLI or web and creates an audit report for one or multiple users.
Events: The administrator defines alarms and triggers that constitute an event. Events are sent to specific users or recorded on the syslog or on another device through an SNMP trap.
Files: The administrator manages (imports, exports, deletes, and renames) and views upgrade, configuration, syslog, audit log, port log, sysconfig, device session, and trap files.
This chapter is primarily for the administrator. It explains how to enter the network configuration, IPv4 filters, and modem settings for the SLM using the SLM web interface or the CLI. If you used a procedure in Chapter 3: Quick Setup to get your unit up and running on the network, you can add or update settings here.