Avocent ASK - 4000 Release-opmerkingen - Pagina 14
Blader online of download pdf Release-opmerkingen voor {categorie_naam} Avocent ASK - 4000. Avocent ASK - 4000 15 pagina's. Universal management gateway
Ook voor Avocent ASK - 4000: Brochure (2 pagina's)
Pagina afdrukken
Power Distribution Unit (PDU)
If a PDU has an issue where it is not responding to the appliance, the non-responsive status is not shown
in the outlets of the PDU within the appliance Web interface or DSView™ 4 software.
An auto detected Serial PDU port cannot currently be reconfigured as a Serial Console port.
When a network PDU is added to the Avocent® Universal Management Gateway appliance, its port may
have an incorrect value for the port number in the associated event message.
If the Energy Consumption start time is unknown, a 01/01/70 12:00 AM value will be displayed.
Before adding the Liebert® MPH/MPX PDU to the Avocent® Universal Management Gateway appliance
for power control or configuration, please ensure that the PDU has a unique community name with RW
permissions. The Liebert® MPH/MPX PDU will allow duplicate community names to be configured with RO
and RW permissions, but then will only allow RO operations.
If both serially-connected (such as the Avocent Power Management PM 1000, PM 2000 and PM 3000
Power Distribution Units) and IP-connected (such as Liebert® MPH/MPX) PDUs are connected to the
Avocent® Universal Management Gateway appliance, a reboot of one of the serially-connected PDUs will
cause the rebooted PDU to be displayed with a duplicate name of one of the IP-connected PDUs.
Restarting the Web interface session will restore the display of the correct name to the serially-connected
PDU.
Power cycle operations to Liebert® PDU outlets will always fail when launched through the command-line
interface and will occasionally fail when launched through the Web interface. Please launch the on/off
operations separately to achieve the cycle operation.
The SNMP community settings for each Liebert® MPH/MPX PDU shown on the
Administration/Targets/Rack PDU/Network PDU tab will be displayed as LiebertEM name and RO type
following a reboot of the appliance.
The default name assigned to a Liebert® MPH2 or MPX2 PDU does not follow the default naming
convention to prefix the name with the appliance MAC address. When the appliance is used with the
DSView™ software and there are multiple appliances managing the same PDU target, each instance of
that same PDU target must be assigned a unique name.
The Web interface display for Liebert® MPH2 or MPX2 PDU Phases does not include voltage, power
consumption, apparent power or power factor.
The Web interface display for Liebert® MPH2 or MPX2 PDU Branches always displays zero for power
consumption, apparent power and power factor.
The Web interface setting of outlet thresholds for Liebert® MPH2 or MPX2 PDUs is currently not functional.
Please launch a Browser session to the native Liebert® MPH2 or MPX2 PDU Web interface to set outlet
thresholds.
PDUs may be deleted from the Avocent® Universal Management Gateway 2000 appliance only when the
PDU is in a No Response state. When the PDU is deleted, all its outlets are also deleted. Individual outlets
cannot be deleted from the appliance.
When connecting the Liebert® MPH/MPX PDU to a private port of the Avocent® Universal Management
Gateway appliance for discovery, please ensure that the PDU is power-cycled or reset after connection so
that the appliance can be assigned a network address through DHCP to the PDU. If the appliance firmware
is updated by USB boot or net boot, please power-cycle or reset the PDU after the appliance is restored to
normal operation. If the PDU is power-cycled or reset before the appliance is restored, it may be necessary
to manually discover the PDU by defining and launching a SP discovery range including the IP address
range for the private port.
The Avocent® Universal Management Gateway appliance can support up to 32 total network-based PDUs
(such as the Liebert® MPH/MPX/MPH2/MPX2) in the Avocent® Universal Management Gateway 2000
appliance, 64 total network-based PDUs in the Avocent® Universal Management Gateway 4000 appliance,
and 128 total network-based PDUs in the Avocent® Universal Management Gateway 6000 appliance. Up
to four PDUs may be daisy-chained per appliance port.
Target state transition events may be generated when a PDU is added to the appliance.
14