Support FAQ

FAQ

Command line configuration

System admins and network managers with Linux/UNIX experience can configure their Opengear console servers at the command line. Only the Administrator class user has command line access and it can accessed using a terminal emulator connected directly (or via a modem) to the local console serial port or by SSH/Telnet connecting to the console server through the LAN. Once logged in, the Administrator can configure the console server and access attached serial consoles and hosts using Linux/Busybox/Opengear commands. To get command line access you must power up the console server and connect the “terminal” device:

If you are connecting using the serial line, plug a serial cable between the IM/CM/SD4000 Local/Modem port and terminal device. Configure the serial connection of the “terminal” device/program you are using to 115200bps, 8 data bits, no parity, one stop bit and software (Xon-Xoff) flow control. If you are using a program running on a Windows PC as the terminal device, then the connecting cable to the DB9 Local/Modem connector is made up from a Cat5 UTP (#440016) cable and two DB-9 to RJ-45 adapters (#319000 and #319001)
To enable dial-in access to the console port you will then need to activate and configure ppp. Authenticated remote dial-in access can also be configured using the web Console Manager by selecting the Network: Dial In menu option
If you are connecting over the LAN then you will need to interconnect the Ethernet ports and direct your terminal emulator program to the IP address of the console server (192.168.0.1 by default)

Command line access

Log on to the console server by pressing ‘return’ a few times. The console server will request a user name and password. Enter the user name root and the password default. You should now see the command line prompt which is a hash (#).

The Opengear console server family all run an embedded Linux operating system enabling Administrators to operate at the command line. Listed below are the standard Linux and Busybox commands and applications that are in the default Opengear build tree. It is possible to configure the console server just using these commands.

Opengear has also developed a number of custom command line utilities to make changes easier, and to ensure they are permanent i.e. stored in the IM/CM/SD4000 flash memory. The config tool allows manipulation and querying of the system configuration from the command line. Using config the new configuration can be activated by running the relevant configurator, which performs the action necessary to make the configuration changes live. Similarly the portmanager application provides a buffered interface to each serial port. It is supported by the pmchat (similar to the chat) and pmshell (similar to the tip or cu) commands, which ensure all serial port access is directed via the portmanager.

Default commands

adduser *, agetty, bash, busybox, cat *, chat, chgrp *, chmod *, chown *, config, cp *, date *, dd *, deluser *, df *, dhcpcd, discard, dmesg *, echo *, erase, eraseall, false *, flashw, flatfsd, ftp, gen-keys, getopt *, gettyd, grep *, gunzip *, gzip *, hd, hostname *, httpd, hwclock, inetd, inetd-echo, init, ip, iptables, iptables-restore, iptables-save, kill *, ln *, login, loopback, loopback16, loopback48, loopback8, ls *, mail, mkdir *, mkfs.jffs2 mknod *, more *, mount *, msmtp, mv *, nc, netflash, netstat, ntpd, pgrep, ping, pkill, pmchat, pmdeny, pminetd, pmloggerd, pmshell, pmusers, portmanager, portmap, pppd, ps *, pwd *, rm *, rmdir *, routed, routef, routel, rtacct, rtmon, scp, sed *, setmac, setserial, sh, showmac, sleep *, smbmnt, smbmount, smbumount, snmpd, ssh, ssh-keygen, sshd, sslwrap, stty, stunnel, sync *, sysctl, tar *, tc, tcpdump, telnetd, tftp, tip, top, touch *, traceroute, true *, umount *, uname *, usleep *, vi *, w, zcat *
Commands which are appended with * above all come from BusyBox

For more information on the command line interface refer to Chapters 13 and 14 in the User Manual which can be found on the CDROM or online.