Tripp Lite 0 Idades Manual

							131
Chapter 7: Alerts, Automated Response and Logging
• Configure SNMP v3 if required.  For SNMP v3 messages, the user’s details and security level must match\
 what the 
receiving SNMP Network Manager is expecting. SNMP v3 mandates that the m\
essage will be rejected unless the SNMPv3 
user sending the trap already exists in the user database on the SNMP Ma\
nager. The user database in a SNMP v3 
application is actually referenced by a combination of the Username and \
the Engine ID for the given SNMP application you 
are talking to.
 o Enter the Engine ID for the user sending messages as a hex number (e.g.\
 0x8000000001020304).
 o Specify the Security Level.  The level of security has to be compatible \
with the settings of the remote SNMP Network    
 Manager.
    noAuthNoPriv  No authentication or encryption. 
   authNoPriv  Authentication only. An authentication protocol (SHA or MD5) and password will be require\
d. 
   authPriv  Uses both authentication and encryption. This is the highest level of se\
curity and requires an  
      encryption protocol (DES or AES) and password in addition to the authe\
ntication protocol and password. 
 o Complete the Username.  This is the Security Name of the SNMPv3 user sen\
ding the message.  This field is  
 mandatory and must be completed when configuring the console server fo\
r SNMPv3.
 o An Authentication Protocol (SHA or MD5) and Authentication Password must be given for a Security Level of either  
 authNoPriv or authPriv.  The password must contain at least 8 characters to be valid.
 o A Privacy Protocol (DES or AES) must be specified for the authPriv l\
evel of security to be used as the encryption  
 algorithm. AES is recommended for stronger security. A password of at least 8 characters must be provided for  
 encryption to work.
• Click Apply
Note: Console Servers with V3.0 firmware (and later) embed the net-snmpd\
 daemon which can accept SNMP requests from remote 
SNMP management servers and provides information on serial port and devi\
ce status (refer Chapter 15.5 for more details).
Console servers with firmware earlier than V3.3 could only configure\
 a Primary SNMP server from the Management Console. 
Refer Chapter 15.5 for details on configuring the snmptrap daemon to s\
end traps/notifications to multiple remote SNMP servers.
Note: For firmware versions 3.10.2 and above, a new SNMP status and trap MIB\
S were created to provide more and better 
structured SNMP status and traps from console servers. There is an option in the SNMP menu to Use Legacy Notifications 
for the SNMP traps. In setting this option, the console server will send\
 SNMP traps that are compatible with those sent from 
older firmware versions before new MIBS were added. This ensures that the firmware upgrade will not upset th\
e existing SNMP 
management settings already in place.
When upgrading from an old firmware version that does not support newe\
r SNMP MIBs/traps (versions before 3.10.2) to 
firmware that does support the new MIBs/traps:
• If the SNMP service was enabled and an SNMP manager was configured bef\
ore upgrading the firmware, the console 
server will be configured to use the legacy traps after upgrading.
• If the SNMP service was not enabled or no SNMP manger was configured b\
efore the upgrade, then the console server will 
be configured to use the new SNMP traps after the upgrade. Note: this \
will not have any effect until the SNMP service is 
turned on and an SNMP manager is configured.
• When starting up using the new firmware after a config erase, the co\
nsole server will be configured to use the new SNMP 
traps. 
• When upgrading from a firmware version that supports the new traps to \
a newer version that supports the new traps, the 
‘use legacy traps’ setting should be kept the same – no checkin\
g SNMP service/manager configuration is needed.
7.2.12   Send Nagios Event alerts on Resolution
To notify the central Nagios server of Alerts, NSCA must be enabled under\
 System: Nagios and Nagios must be enabled for 
each applicable host or port under Serial & Network: Network Hosts or Se\
rial & Network: Serial Ports (refer to Chapter 10).  
						

							132
Chapter 7: Alerts, Automated Response and Logging
7.3 Remote Log Storage   
Before activating Serial or Network Port Logging on any port or UPS logging, you must specify where those log\
s are to be saved:
• Select the Alerts & Logging: Port Log menu option and specify the Server Type to be used, and the details to enable 
log server access 
7.4 Serial Port Logging  
In Console Server mode, activity logs can be maintained of all serial po\
rt activity. These records are stored on an off-server, or 
in the Console Server flash memory. To specify which serial ports are to have activities recorded and to what\
 level data is to be 
logged: 
• Select Serial & Network: Serial Port and Edit the port to be logged
• Specify the Logging Level of for each port as: 
Level 0 Turns off logging for the selected port
Level 1 Logs all User connection events to the port
Level 2 Logs all data transferred to and from the port and all changes in hardwa\
re flow control status and all User 
connection events 
Level 3 Logs all data transferred from the port and all changes in hardware fl\
ow control status and all User connection 
events 
Level 4 Logs all data transferred to the port and all changes in hardware flow control status a\
nd all User connection 
events
• Click Apply
Note: A cache of the most recent 8K of logged data per serial port is mainta\
ined locally (in addition to the Logs which are 
transmitted for remote/USB flash storage). To view the local cache of logged serial port data select Manage: Port Logs  
						

							133
Chapter 7: Alerts, Automated Response and Logging
7.5 Network TCP or UDP Port Logging  
The Console Servers can also log any access to and communications with n\
etwork attached Hosts. 
• For each Host, when you set up the Permitted Services which are authorized to be used, you also must set up \
the level of 
logging that is to be maintained for each service 
• Specify the logging level that is to be maintained for that particular T\
DC/UDP port/service on that particular Host: 
Level 0 Turns off logging for the selected TDC/UDP port to the selected Host
Level 1 Logs all connection events to the port
Level 2 Logs all data transferred to and from the port
• Click Add then click Apply 
7.6 Auto-Response Event Logging 
• Check Log Events on Alerts & Logging: Auto-Response to enable logging al\
l Auto-Response activities
 
7.7  Power Device Logging 
The Console Server also logs access and communications with network atta\
ched hosts and maintains a history of the UPS and 
PDU power status. 
To activate and set the desired levels of logging for each serial (Secti\
on 7.4) and/or network port (Section 7.5) and/or power 
and environment UPS (refer Chapter 8).  
						

							134
Chapter 8: Power and Environment
The B094-008-2E-M-F, B094-008-2E-V, B095-004/003 and B092-016 Console Servers and B096-048/032/016 
Console Server Management Switch products embed software that can be use\
d to manage connected Power Distribution 
Systems (PDU’s), IPMI devices and Uninterruptible Power Supplies (UPS’s) supplied by a number of vendors, and some the\
 
environmental monitoring devices. B092-016 Console Server with PowerAlert also embeds Tripp Lite’s PowerAlert software.
8.1 Remote Power Control (RPC) 
The Console Server Management Console monitors and controls Remote Power Control (RPC) devices using the embedded 
PowerMan and NUT open source management tool. RPC’s include power distribution units (PDU’s) and IPMI power devic\
es. 
8.1.1    RPC connection 
Serial and network connected RPC’s must first be connected to, and configured to communicate with\
, the Console Server: 
• For serial RPC’s, connect the PDU to the selected serial port on the Console Server\
. From the Serial and Network: Serial 
Port menu, configure the Common Settings of that port with the RS232 properties required by the PDU (refer to Chapter 
4.1.1 Common Settings). Then select RPC as the Device Type 
• Similarly for each network connected RPC, go to Serial & Network: Network Hosts menu and configure the RPC as a 
connected Host
• Select the Serial & Network: RPC Connections menu. This will display all the RPC connections that have already been 
configured
• Click Add RPC In Connected Via, select the pre-configured serial port or the network host address th\
at connects to the 
RPC 
• Enter a RPC Name and Description for the RPC
• Enter the Username and Password used to login into the RPC. Note that these login credentials are not r\
elated the 
Users and access privileges you will have configured in Serial & Networks: Users & Groups
• Check Log Status and specify the Log Rate (minutes between samples) if you wish the status from this RPC to be \
logged. These logs can be views from the Status: RPC Status screen 
• Click Apply  
						

							135
Now you have set up a new serially or network connected RPC device, this\
 will automatically create a corresponding new 
Managed Device with the same Name /Description as the RPC The outlet nam\
es on the RPC/PDU Managed Device will by 
default be “Outlet 1” “Outlet 2”.
You can now establish a “connection” between particular Managed Dev\
ice that draws power from the particular RPC/PDU 
outlet (using Serial & Network: Managed Devices - refer Chapter 4).  The outlet will then take up the name of the powered 
Managed Device.  
Note: The Management Console has support for a number of network and serial \
PDU’s. If your PDU is not on the default list, 
it is simple to add support for more devices. This is covered in Chapter\
 14: Advanced Configurations 
IPMI service processors and BMCs can be configured so all authorized u\
sers can use the Management Console to remotely 
cycle power and reboot computers, even when their operating system is un\
responsive. To set up IPMI power control, the 
Administrator first enters the IP address/domain name of the BMC or se\
rvice processor (e.g. a Dell DRAC) in Serial & 
Network: Network Hosts. Then in Serial & Network: RPC Connections, the Administrator specifies the RPC Type to be 
IPMI1.5 or 2.0
Chapter 8: Power and Environment  
						

							136
8.1.2 RPC alerts 
You can now set PDU and IPMI alerts using Alerts & Logging: Alerts (refer to Chapter 7)
8.1.3 RPC status 
You can monitor the current status of your network and serially connected\
 PDU’s and IPMI RPC’s
• Select the Status: RPC Status menu. A table with the summary status of all connected RPC hardware wil\
l be displayed
• Click on View Log or select the RPC Logs menu. You will be presented with a table of the history and detailed graphical \
information on the select RPC 
• Click Manage to query or control the individual power outlet. This will take you to \
the Manage: Power screen
Chapter 8: Power and Environment  
						

							137
8.1.4 User power management 
The Power Manager enables both Users and Administrators to access and control\
 the configured serial and network attached 
PDU power strips, and servers with embedded IPMI service processors or B\
MC’s:  
• Select the Manage: Power and the particular Target power device to be controlled (or click Manage on the Status: RPC 
Status menu)
• The outlet status is displayed. You can initiate the desired Action to be taken by selecting the appropriate icon:
 Power ON
 Power OFF
 Power Cycle 
 Power Status   
You will only be presented with icons for those operations that are suppo\
rted by the Target you have selected
Chapter 8: Power and Environment  
						

							138
Chapter 8: Power and Environment
8.2  Uninterruptible Power Supply Control (UPS)
The Console Servers manage UPS hardware using Network UPS Tools (refer Section 8.2.6 for an overview of embedded open 
source Network UPS Tools - NUT software) 
8.2.1    Managed UPS connections 
A Managed UPS is a UPS that is connected by serial or USB cable or by the network to \
the Console Server. The Console 
Server becomes the Master of this UPS, and runs a upsd server to allow o\
ther computers that are drawing power through the 
UPS (Slaves) to monitor its status and take appropriate action (such \
as shutdown in event of low battery).
The Console Server may or may not be drawing power through the Managed U\
PS (see the Configure UPS powering the 
Console Server section below).
When the UPS's battery power reaches critical, the Console Server signal\
s and waits for Slaves to shutdown, then powers off 
the UPS.
Serial and network connected UPS’s must first be configured on th\
e Console Server with the relevant serial control ports 
reserved for UPS usage, or with the UPS allocated as a connected Host:
• Select UPS as the Device Type in the Serial & Network: Serial Port menu for each port which has Master control over a 
UPS and in the Serial & Network: Network Hosts menu for each network connected UPS (refer to Chapter 4)
No such configuration is required for USB-connected UPS hardware.   
						

							139
Chapter 8: Power and Environment
• Select the Serial & Network: UPS Connections menu. The Managed UPSes section will display all the UPS 
connections that have already been configured. 
• Click Add UPS 
• Enter a UPS Name and Description (optional) and identify if the UPS will be Connected Via USB or over pre-configured 
serial port or via HTTP/HTTPS over the preconfigured network Host connection
• Enter the UPS login details. This Username and Password is used by Slaves of this UPS (i.e. other computers that are 
drawing power through this UPS) to connect to the Console Server for mo\
nitoring of the UPS status and shutdown when 
battery power is low. Monitoring will typically be performed using the upsmon client running on the Slave server. See 
section 8.5.4 for details on setting up upsmon on Slave servers powered by the UPS
Note: These login credentials are not related to the Users and access privil\
eges you will have configured in Serial & 
Networks: Users & Groups
• If you have multiple UPS’s and require them to be shut down in a spec\
ific order, specify the Shutdown Order for this UPS. 
This is a positive whole number, or -1. 0s are shut down first, then 1s, 2s, etc. -1s are not shut down at all. Defaults to 0  
						

							140
Chapter 8: Power and Environment
• Select the Driver that will be used to communicate with the UPS. The drop-down menu prese\
nts a full selection of drivers 
from the latest Network UPS Tools (NUT version 2.2.0) and additional information on compatible UPS \
hardware can be 
found at http://www.networkupstools.org/compat/stable.html
• Click New Options in Driver Options if you need to set driver-specific options for your selected NUT driver and hardware 
combination (more details at http://www.networkupstools.org/doc
• Check Log Status and specify the Log Rate (i.e. minutes between samples) if you wish the status from this UPS t\
o be 
logged. These logs can be views from the Status: UPS Status screen 
• Check Enable Nagios to enable this UPS to be monitored using Nagios central management
• Click Apply
You can also customize the upsmon, upsd and upsc settings for this UPS hardware directly from the command line 
8.2.2   Configure UPS powering the Console Server 
A Monitored UPS is a UPS that is providing the power to the Console Server. The purpose of configuring a Monitored UPS 
is to provide an opportunity to perform any "last gasp" actions before p\
ower is lost during a power failure. This is achieved by 
placing a script in /etc/config/scripts/ups-shutdown. You may use the /etc/scripts/ups-shutdown as a template. This script is run 
when then UPS reaches critical battery status.
• If the Console Server is drawing power through a Managed UPS that has al\
ready been configured, select Local, enter the 
Managed UPS Name and check Enabled. The Console Server continues to be the master of this UPS
• If the UPS that powers the Console Server is not a Managed UPS for that \
Console Server, then the Console Server can 
still connect to a remote NUT server (upsd) to monitor its status as a Slave. In this case, select Remote, and enter the 
address, username and password to connect.