Drivers Liebert

Liebert Pcw free download - PCW Network, Liebert PowerSure PSA UPS, Liebert PowerSure PSP UPS, and many more programs. View and Download Vertiv Liebert MC series user manual online. 60-Hz Air-cooled Microchannel Condenser - Premium/EC Fan. Liebert MC series fan pdf manual download. Also for: Liebert mcs056, Liebert mcs028, Liebert mcm040, Liebert mcm080, Liebert mcm160, Liebert mcl055, Liebert mcl165. Hi All, I have acquired a Liebert GXT2U UPS with a 'voyager' SNMP/web card installed (note, this is NOT the same as the is-webcard). Trying to configure NUT using snmp-ups driver and receive the following output: Network UPS Tools - Gene.

Recommended to protect mission-critical equipment, Liebert® GXT4™ is a true on-line UPS that delivers continuous, high-quality AC power with no break when transferring to battery. It protects equipment from all power disturbances due to blackouts, brownouts, sags, surges or noise interference. Liebert GXT4 UPS.

nutupsdrv: generic manual for unified NUT drivers

Command to display nutupsdrv manual in Linux: $ man 8 nutupsdrv

NAME

nutupsdrv - generic manual for unified NUT drivers

SYNOPSIS

nutupsdrv-h

nutupsdrv [OPTIONS]

DESCRIPTION

nutupsdrv is not actually a driver. This is a combined man page for the shared code that is the core of many drivers within the Network UPS Tools package.

For information on the specific drivers, see their individual man pages.

UPS drivers provide a communication channel between the physical UPS hardware and the upsd(8) server. The driver is responsible for translating the native protocol of the UPS to the common format used by the rest of this package.

The core has two modes of operation which are determined by the command line switches. In the normal mode, the driver will periodically poll the UPS for its state and parameters. The results of this command is presented to upsd. The driver will also handle setting variables and instant commands if available.

The driver can also instruct the UPS to shut down the load, possibly after some delay. This mode of operation is intended for cases when it is known that the UPS is running out of battery power and the systems attached must be turned off to ensure a proper reboot when power returns.


Note

You probably don't want to use any of these options directly. You should use upsdrvctl(8) to control your drivers, and ups.conf(5) to configure them. The rest of this manual describes options and parameters that generally are not needed by normal users.

OPTIONS

-h

-aid

-q

Raise log level threshold. Use this multiple times to log more details.

The debugging comment above also applies here.

-iinterval

Print only version information, then exit.

-L

You should useupsdrvctl shutdownwhenever possible instead of calling this directly.

-rdirectory

The driver will chroot(2) todirectoryduring initialization. This can be useful when securing systems.

In addition to the state path, many systems will require /dev/null to exist withindirectoryfor this to work. The serial ports are opened before the chroot call, so you do not need to create them inside the jail. In fact, it is somewhat safer if you do not.

-uusername

If started as root, the driver will setuid(2) to the user id associated withusername.

If you do not specify this value and start it as root, the driver will switch to the default value that was compiled into the code. This is typicallynobody, and is far from ideal.

-xvar=val

Define a variable calledvarwith the value ofvarin the driver. This varies from driver to driver - see the specific man pages for more information.

This is like settingvar=valinups.conf(5), but-xoverrides any settings from that file.

DIAGNOSTICS

Information about the startup process is printed to stdout. Additional messages after that point are available in the syslog. After upsd(8) starts, the UPS clients such as upsc(8) can be used to query the status of an UPS.

PROGRAM CONTROL

You should always use upsdrvctl(8) to control the drivers. While drivers can be started by hand for testing purposes, it is not recommended for production use.

FILES

ups.conf

Note

You probably don't want to use any of these options directly. You should use upsdrvctl(8) to control your drivers, and ups.conf(5) to configure them. The rest of this manual describes options and parameters that generally are not needed by normal users.

OPTIONS

-h

-aid

-q

DriversRaise log level threshold. Use this multiple times to log more details.

The debugging comment above also applies here.

Drivers Liebert Jobs

-iinterval

Print only version information, then exit.

-L

You should useupsdrvctl shutdownwhenever possible instead of calling this directly.

-rdirectory

The driver will chroot(2) todirectoryduring initialization. This can be useful when securing systems.

In addition to the state path, many systems will require /dev/null to exist withindirectoryfor this to work. The serial ports are opened before the chroot call, so you do not need to create them inside the jail. In fact, it is somewhat safer if you do not.

-uusername

If started as root, the driver will setuid(2) to the user id associated withusername.

If you do not specify this value and start it as root, the driver will switch to the default value that was compiled into the code. This is typicallynobody, and is far from ideal.

-xvar=val

Define a variable calledvarwith the value ofvarin the driver. This varies from driver to driver - see the specific man pages for more information.

This is like settingvar=valinups.conf(5), but-xoverrides any settings from that file.

DIAGNOSTICS

Drivers Liebert Driver

Information about the startup process is printed to stdout. Additional messages after that point are available in the syslog. After upsd(8) starts, the UPS clients such as upsc(8) can be used to query the status of an UPS.

PROGRAM CONTROL

You should always use upsdrvctl(8) to control the drivers. While drivers can be started by hand for testing purposes, it is not recommended for production use.

FILES

ups.conf

Drivers Liebert Drivers
  • nutups_cgi_script_selinux (8) - Security Enhanced Linux Policy for the nutups_cgi_script processes
  • nut-ipmipsu (8) - Driver for IPMI Power Supply Units (PSU)
  • nut-recorder (8) - utility to record device status and values changes
  • nut-scanner (8) - scan communication buses for NUT devices
  • nut_selinux (8) - Security Enhanced Linux Policy for the nut processes
  • nut_upsd_selinux (8) - Security Enhanced Linux Policy for the nut_upsd processes
  • nut_upsdrvctl_selinux (8) - Security Enhanced Linux Policy for the nut_upsdrvctl processes

Drivers Liebert Wireless

Linux man pages generated by: SysTutorials. Linux Man Pages Copyright Respective Owners. Site Copyright © SysTutorials. All Rights Reserved.