Tripp Lite 0 Idades Manual

							181
Chapter 12: Status Reports
12.4 Syslog
The Linux System Logger in the Console Server maintains a record of all \
system messages and errors: 
• Select Status: Syslog 
The syslog record can be redirected to a remote Syslog Server: 
• Enter the remote Syslog Server Address and Syslog Server Port details and click Apply 
The console maintains a local Syslog. To view the local Syslog file:
• Select Status: Syslog 
To make it easier to find information in the local Syslog file, a pat\
tern matching filter tool is provided.
• Specify the Match Pattern that is to be searched for (e.g. the search for mount is shown below) and click Apply. The 
Syslog will then be represented with only those entries that actually in\
clude the specified pattern
12.5 Dashboard
The Dashboard provides the Administrator with a summary of the status of\
 the Console Server and its Managed Devices. 
Custom dashboards can be configured for each user group.  
						

							182
Chapter 12: Status Reports
12.5.1  Configuring the Dashboard
Only users who are members of the admin group (and the root user) can \
configure and access the dashboard. To configure a 
custom dashboard:
• Select System: Configure Dashboard and select the user (or group) you are configuring this custom dashb\
oard layout 
for 
Note: You can configure a custom dashboard for any admin user or for the admin group or you can reconfigure the default 
dashboard
The Status:Dashboard screen is the first screen displayed when admin users (other than root) log into the console manager. 
If you log in as "John", and John is member of the admin group and there is a dashboard layout configured for John, then you 
will see the dashboard for John (on log-in and each time you click on t\
he Status:Dashboard menu item.
If there is no dashboard layout configured for John but there is an admin group dashboard configured then you will see the 
admin group dashboard instead. If there is no user dashboard or admin gr\
oup dashboard configured, then you will see the 
default dashboard.
The root user does not have its own dashboard.
The above configuration options are intended to enable admin users to \
setup their own custom dashboards 
The Dashboard displays a configurable number of widgets. These widgets\
 include status for major subsystems such as  
Auto-Response, Managed Devices and cellular. The admin user can configure which of these widgets is to be display\
ed where:   
• Go to the Dashboard layout panel and select which widget is to be displayed in each of the Widget Slots
• Click Apply
Note: The Alerts widget is a new screen that shows the current alerts status\
. When an alert gets triggered, a corresponding 
.XML file is created in /var/run/alerts/. The dashboard scans all these files and displays a summary status in\
 the alerts widget. 
When an alert is deleted the corresponding .XML files that belong to t\
hat alert are also deleted.  
						

							183
Chapter 12: Status Reports
To configure what is to be displayed by each widget: 
• Go to the Configure Widgets panel and configure each selected widget (e.g. specify which UPS sta\
tus is to be displayed 
on the ups widget or the maximum number of Managed Devices to be displayed in the devices widget  
• Click Apply
Note: Dashboard configuration is stored in the /etc/config/config.xml \
file. Each configured dashboard will increase the config 
file. If this file gets too big, you can run out of memory space on \
the Console Server.  
12.5.2  Creating custom widgets for the Dashboard
To run a custom script inside a dashboard widget:
Create a file called "widget-.sh" in the folder /etc/config/scripts/ where  can be anything. You can have as 
many custom dashboard files as you want.
Inside this file you can put any code you wish. When configuring the\
 dashboard, choose "widget-.sh" in the dropdown 
list. The dashboard will run the script and display the output of the sc\
ript commands directly on the screen, inside the specific 
widget. 
The best way to format the output would be to send HTML commands back to\
 the browser by adding echo commands in the 
script:
echo ''
You can of course run any command and its output will be displayed in the\
 widget window directly.
Below is an example script which writes the current date to a file, an\
d then echo's HTML code back to the browser. The HTML 
code gets an image from a specific URL and displays it in the widget. \
#!/bin/sh
date >> /tmp/test
echo ''
echo ' This is my custom script running '
echo ''
echo ''
echo ''
echo ''
exit 0  
						

							184
Chapter 13: Management
The Console Server has a small number of Manage reports and tools that are available to both Administrators and Users: \
• Access and control authorized devices 
• View serial port logs and host logs for those devices
• Use SDT Connector or the Web Terminal to access serially attached consoles
• Power control
13.1  Device Management  
Note: The Manage Devices UI has been significantly updated in firmware ve\
rsion 3.15.
To display Managed Devices and their grouped serial, network and power co\
nnections: 
• Select Manage: Devices or click the Manage Devices icon in the top right of the UI
• admin-group users are presented with a list of all configured Managed Devic\
es and their constituent connections. user-
group users only see the Managed Devices where for each Related Connecti\
on, they have been explicitly permitted access 
• The Status column displays the current most salient status for each Related Connec\
tion (e.g. Active Users for serial 
connections, and power status for RPC outlet connections) with links to\
 detailed status
• The links in the Actions column are used to control the Managed Device (e.g. connect to a conso\
le session or power 
cycle – power actions are not performed until the action has been con\
firmed via pop-up message)  
• The Administrator will be presented with a list of all configured Managed Devices where\
as the User will only see the 
Managed Devices they (or their Group) has been given access privileges\
 for
• Alternatively, select the Serial tab for an ungrouped view of permitted serial port connections for the \
current user
• An additional Signals column displays the current state of the serial pins
Note: To use the Connect: via SSH links, your computer’s operating system must recognize the ssh:/ /\
 URI scheme and have a 
protocol handler configured (e.g. an SSH client like SecureCRT).  
						

							185
Chapter 13: Management
13.2 Port and Host Log Management 
Administrators and Users can view logs of data transfers to connected de\
vices.
• Select Manage: Port Logs and the serial Port # to be displayed
• To display Host logs select Manage: Host Logs and the Host to be displayed
13.3  Terminal Connection 
There are two methods available for accessing the console server command\
 line and devices attached to the console server 
serial ports, directly from a web browser:
• The Web Terminal service uses AJAX to enable the web browser to connect to the co\
nsole server using HTTP or HTTPS, as 
a terminal - without the need for additional client installation on the \
user's PC
• The SDT Connector service launches a pre-installed SDT Connector client \
on the user's PC to establish secure SSH 
access, then uses pre-installed client software on the client PC to conn\
ect to the console server
Web browser access is available to users who are a member of the admin or\
 users groups.
13.3.1 Web Terminal
The AJAX based Web Terminal service may be used to access the console server command line or\
 attached serial devices.
Note: Any communication using the Web Terminal service using HTTP is unencrypted and not secure.  The Web Terminal 
connects to the command line or serial device using the same protocol th\
at is being used to browse to the Management 
Console, i.e. if you are browsing using an https:// URL (this is the de\
fault), the Web Terminal connects using HTTPS.
13.3.1.1 Web Terminal to Command Line
To enable the Web Terminal service for the console server 
• Select the tab in the System: Firewall menu 
• Check Enable Web Terminal and click Apply
Administrators can now communicate directly with the Console Server comm\
and line from their browser:
• Select Manage: Terminal to display the Web Terminal from which you can log in to the Console Server command line  
						

							186
Chapter 13: Management
13.3.1.2 Web Terminal to Serial Device
To enable the Web Terminal service for each serial port you want to access:
• Select Serial & Network: Serial Port and click Edit.  Ensure the serial port is in Console Server Mode
• Check Web Terminal and click Apply
Administrator and Users can communicate directly with serial port attach\
ed devices from their browser:
• Select the Serial tab on the Manage: Devices menu 
• Under the Action column, click the Web Terminal icon  to display the Web Terminal, connected directly to the 
attached serial device
Note: The Web Terminal feature was introduced in firmware V3.3.2. Earlier releases ha\
d an open source jcterm java terminal 
applet which could be downloaded into your browser to connect to the Con\
sole Server and attached serial port devices. 
However jcterm had some JRE compatibility issues and is no longer supported
13.3.2 SDTConnector access
Administrator and Users can communicate directly with the Console Server\
 command line and with devices attached to the 
Console Server serial ports using SDT Connector and their local tenet cl\
ient, or using a Web terminal and their browser
• Select Manage: Terminal 
• Click the Connect to SDT Connector button. This will to activate the SDT Connector client on the computer \
you are 
browsing and load your local telnet client to connect to the command lin\
e or serial port using SSH  
						

							187
Chapter 13: Management
Note: SDT Connector must be installed on the computer you are browsing from \
and the Console Server must be added as a 
gateway - as detailed in Chapter 6
13.4 Power Management  
Administrators and Users can access and manage the connected power devic\
es.
• Select Manage: Power
 
13.5  Remote Console Access (B092-016 only)
Administrator and Users can also connect to the B092-016 Console Server \
with PowerAlert remotely (as if they were plugged 
in locally to the KVM connectors on the B092-016). This connection will\
 enable the remote users to run the PowerAlert 
software and the other thin client programs (refer to Chapter 16) embe\
dded in the Console Server:    
• Select Manage: KVM Console Server
• Click Standard VNC Remote control and a VNC Java applet will be loaded into your browser to connect to the\
 B092-
016 Console Server. Then log in to the VNC applet and the Console Server (refer to Chapte\
r 16.3 for more details)  
						

							188
Chapter 14: Command Line Configuration
For those who prefer to configure their Console Server at the Linux com\
mand line level (rather than use a browser and the 
Management Console), this chapter describes using command line access a\
nd the config tool to manage the Console Server 
and configure the ports etc.
This config documentation in this chapter walks thru command line configuration t\
o deliver the functions provided otherwise 
using the Management Console GUI. 
For advanced and custom configurations and for details using other tool\
s and commands refer to the next chapter 
When displaying a command, the convention used in the rest of this chapt\
er is to use single quotes ('') for user defined values 
(e.g. descriptions and names). Element values without single quotes mu\
st be typed exactly as shown.
After the initial section on accessing the config command the menu ite\
ms in this document follow the same structure as the 
menu items in the web GUI.
14.1 Accessing config from the command line
The Console Server runs a standard Linux kernel and embeds a suite of op\
en source applications. So if you do not want to 
use a browser and the Management Console tools, you are free to config\
ure the Console Server and to manage connected 
devices from the command line using standard Linux and Busybox commands \
and applications such as ifconfig, gettyd, stty, 
powerman, nut etc. However without care these configurations may not withstand a power-cycle-reset or reconfigure.   
So Tripp Lite provides a number of custom command line utilities and scripts\
 to make it simple to configure the Console Server 
and ensure the changes are stored in the Console Server's flash memory\
 etc. 
In particular the config utility allows manipulation of the system configuration from the comm\
and line. With config a new 
configuration can be activated by running the relevant configurator, which performs the action necessary to make the 
configuration changes live. 
To access config from the command line:
• Power up the Console Server and connect the “terminal” device: 
  o If you are connecting using the serial line, plug a serial cable between\
 the Console Server local DB-9 console port  
    and terminal device. Configure the serial connection of the terminal d\
evice you are using to 115200bps, 8 data  
   bits, no parity and one stop bit
 o If you are connecting over the LAN then you will need to interconnect th\
e Ethernet ports and direct your terminal  
    emulator program to the IP address of the Console Server (192.168.0.1 b\
y default)  
• Log on to the Console Server by pressing ‘return’ a few times. The\
 Console Server will request a username and password. 
Enter the username root and the password default. You should now see the command line prompt which is a hash (#)
 
This chapter is not intended to teach you Linux. We assume you already have a certain level of 
understanding before you execute Linux kernel level commands.  
						

							189
Chapter 14: Command Line Configuration
The config tool
Syntax
config [ -ahv ] [ -d id ] [ -g id ] [ -p path ] [ -r configurator ] \
[ -s id=value ] [ -P id ]
Description      
The config tool is designed to perform multiple actions from one command if need b\
e, so if necessary options can be chained 
together.
The config tool allows manipulation and querying of the system configuration fro\
m 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.
The custom user configuration is saved in the /etc/config/config.xml file. This file is transparently accessed and edited when 
configuring the device using the Management Console browser GUI. Only \
the user 'root' can configure from the shell.
By default, the config elements are separated by a '.' character. The root of the config tree is called . To address a 
specific element place a '.' between each node/branch e.g. to access a\
nd display the description of user1 type:
 # config -g config.users.user1.description  
The root node of the config tree is . To display the entire config tree, type:
 # config -g config
To display the help text for the config command, type:
 # config -h
The config application resides in the /bin directory. The environmental variable called PAT H contains a route to the /bin 
directory. This allows a user to simply type config at the command prompt instead of the full path /bin/config.
Options
-a –run-all Run all registered configurators. This performs every configuration \
synchronization action pushing 
all changes to the live system
-h –help  Display a brief usage message
-v –verbose Log extra debug information
-d –del=id  Remove the given configuration element specified by a '.' separated \
identifier
-g –get=id Display the value of a configuration element
-p –path=file Specify an alternate configuration file to use. The default file i\
s located at /etc/config/config.xml
-r  –run=configurator  Run the specified registered configurator. Registered configurators are listed below.
-s –set=id=value   Change the value of configuration element specified by a '.' separat\
ed identifier
-e –export=file     Save active configuration to file
 -i –import=file        Load configuration from file
 -t –test-import=file  Pretend to load configuration from file
 -S –separator=char  The pattern to separate fields with, default is '.'
-P –password=id  Prompt user for a value. Hash the value, then save it in id  
						

							190
Chapter 14: Command Line Configuration
The registered configurators are:
alerts
auth
cascade
console
dhcp
dialin
eventlog
hosts
ipaccess
ipconfig
nagios
power
serialconfig
services
slave
systemsettings
time
ups
users
There are three ways to delete a config element value. The simplest wa\
y is use the delete-node script detailed later in Chapter 
15. You can also assign the config element to "", or delete the entire confi\
g node using -d:
# /bin/config -d 'element name'
All passwords are saved in plaintext except the user passwords and the s\
ystem passwords, which are encrypted.
Note: The config command does not verify whether the nodes edited/added by the user are \
valid. This means that any node 
may be added to the tree. If a user were to run the following command:
# /bin/config -s config.fruit.apple=sweet
The configurator will not complain, but this command is clearly useles\
s. When the configurators are run (to turn the config.xml 
file into live config) they will simply ignore this  node. A\
dministrators must make sure of the spelling when typing config 
commands. Incorrect spelling for a node will not be flagged.
Most configurations made to the XML file will be immediately active.\
 To make sure that all configuration changes are active, 
especially when editing user passwords, run all the configurators:
# /bin/config -a
For information on backing up and restoring the configuration file r\
efer Chapter 15 Advanced Configuration.
14.1.1 Serial Port configuration
The first set of configurations that needs to be made to any serial \
port are the RS232 common settings. For example to setup 
serial port 5 to use the following properties:
Baud Rate  9600
Parity None
Data Bits 8
Stop Bits 1
label Myport
log level 0
protocol RS232
flow control None
To do this use the following commands:
# config -s config.ports.port5.speed=9600
# config -s config.ports.port5.parity=None
# config -s config.ports.port5.charsize=8
# config -s config.ports.port5.stop=1
# config -s config.ports.port5.label=myport
# config -s config.ports.port5.loglevel=0
# config -s config.ports.port5.protocol=RS232
# config -s config.ports.port5.flowcontrol=None