Tripp Lite B0930082E4U Owners Manual for B093- B097- and B098-Series Console S - Page 266

15. Advanced Configuration fru Print built-in FRU and scan SDR for FRU locators sel Print System Event Log (SEL) pef Configure Platform Event Filtering (PEF) sol Configure IPMIv2.0 Serial-over-LAN isol Configure IPMIv1.5 Serial-over-LAN user Configure Management Controller users channel Configure Management Controller channels session Print session information exec Run list of commands from file set Set runtime variable for shell and exec ipmitool chassis help Chassis Commands: status, power, identify, policy, restart_cause, poh, bootdev ipmitool chassis power help chassis power Commands: status, on, off, cycle, reset, diag, soft You will find more details on ipmitools at http://ipmitool.sourceforge.net/manpage.html. 15.11 Custom Development Kit (CDK) Copy scripts, binaries and configuration files directly to the console server. Tripp Lite also provides a free development kit that allows changes to be made to the software in console server firmware image. The customer can use the CDK to: • Generate a firmware image without certain programs such as telnet, which may be banned by company policy. • Generate an image with new programs such as custom Nagios plug-in binaries or company specific binary utilities. • Generate an image with custom defaults (e.g., it may be required that the console server be configured to have a specific default serial port profile which is reverted to in the event of a factory reset. • Place configuration files into the firmware image, which cannot then be modified. For example, # /bin/config --set= tools update the configuration files in /etc/config which are read/write, whereas the files in /etc are read only and cannot be modified. The CDK provides a snapshot of the Tripp Lite build process (taken after the programs have been compiled and copied to a temporary directory romfs) just before the compressed file systems are generated. When the console servers are cascaded, the Primary unit is in control of the serial ports on the Secondary units, and the primary's management console provides a consolidated view of the settings for both its own and all the secondary unit's serial ports. However, the Primary unit does not provide a fully consolidated view. For example, Status: Active Users only displays those users active on the Primary unit's ports; you will need to write a custom bash script that parses the port logs if you want to find out who's logged in to cascaded serial ports from the Primary. You will also want to enable remote or USB logging. Local logs only buffer 8K of data and do not persist between reboots. This script would parse each port log file line by line. For example, each time it sees 'LOGIN: username', it adds username to the list of connected users for that port, and each time it sees 'LOGOUT: username' it removes it from the list. In doing this, the list can be neatly formatted and displayed. It is also possible to run this as a CGI script on the remote log server. To enable log storage and connection logging: • Select Alerts & Logging: Port Log. • Configure log storage. • Select Serial & Network: Serial Port. Edit the serial port(s). • Under Console server, select Logging Level 1 and click Apply. A useful tutorial on creating a bash script CGI can be found at: http://www.yolinux.com/TUTORIALS/ LinuxTutorialCgiShellScript.html 266