321
1. 8 7 7. 8 7 7. 2 26 9 BLACKBOX.COM
NEED HELP?
LEAVE THE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.87 7.2269
CHAPTER 16: ADVANCED CONFIGURATION
16.11 CUSTOM DEVELOPMENT KIT (CDK)
As detailed in this manual, customers can copy scripts, binaries and configuration files directly to the console server.
Black Box also freely provides a development kit which 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 even in event of a factory reset
place configuration files into the firmware image, which cannot then be modified.
For example:
# /bin/config –-set= tools
updates the configuration files in /etc/config which are read/write, whereas the files in /etc are read only and cannot be modified.
The CDK essentially provides a snapshot of the Black Box build process (taken after the programs have been compiled and copied
to a temporary directory, romfs) just before the compressed file systems are generated.
You can obtain a copy of the Black Box CDK for the particular appliance you are working with from ftp://ftp.Black Box.com/cdk.
Further information is avalable at http://Black Box.com/faq284.html.
16.12 SCRIPTS FOR MANAGING SLAVES
When the console servers are cascaded, the Master is in control of the serial ports on the Slaves, and the Master’s Management
Console provides a consolidated view of the settings for its own and all the Slave’s serial ports.
The Master does not provide a fully consolidated view. Status > Active Users only displays those users active on the Master’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 master.
You will probably also want to enable remote or USB logging, as local logs only buffer 8K of data and don’t persist between reboots.
This script would, for example, parse each port log file line by line.
Each time it sees LOGIN: username, it adds username to the list of connected users for that port. Each time it sees LOGOUT:
username, it removes it from the list.
The list can then be nicely formatted and displayed. It’s 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.
click Apply.
NOTE: A useful tutorial on creating a bash script CGI is at http://yolinux.com/TUTORIALS/LinuxTutorialCgiShellScript.html.
Similarly, the Master maintains a view of the status of the slaves:
select Status > Support Report.
scroll down to Processes.
To Next Page
Loading...
