Avocent ASK - 4000 Catatan Rilis - Halaman 5
Jelajahi secara online atau unduh pdf Catatan Rilis untuk Beralih Avocent ASK - 4000. Avocent ASK - 4000 15 halaman. Universal management gateway
Juga untuk Avocent ASK - 4000: Brosur (2 halaman)
Halaman Cetak
New Feature / SP
Supported feature
G
Get only
Only via DirectCommand support in DSView™ 4 software
D
General Notes and Known Issues
Do not manage the same Service Processor from multiple Avocent® Universal Management Gateway
appliances at the same time. Some Service Processors may show erratic behavior when sessions limits
are exceeded, or with simultaneous access. This may manifest in the appliance Web interface as being
unable to discover, manually add Service Processors or errors when viewing and managing SP settings.
When upgrading the appliance firmware, Service Processors previously added with IPMI 2.0 profiles will
not be updated, even if the Service Processor is now a newly supported profile in the upgraded Avocent®
Universal Management Gateway appliance release. If the full capabilities of the specific Service Processor
are needed, delete and then re-add the Service Processor to use the newly defined profile.
When attaching a Service Processor chassis on one of the private ports on the back of the Avocent®
Universal Management Gateway appliance for automatic discovery, make sure the chassis and all the
blade servers in the chassis are configured for DHCP. All manageable components must be configured for
DHCP for automatic discovery to work correctly.
Some Service Processors may take several minutes to query SEL records. If the command takes more
than 1 minute, the Web interface query may timeout. If this occurs, check the SEL record list via the SP's
native Browser UI or CLI and empty the list.
Service Processors that support virtual media may have problems mapping removable media devices
when the client is the Avocent® Universal Management Gateway appliance local port or a PC running a
Linux operating system. Potential workarounds include:
a. Make sure the Service Processor's firmware is the latest supported by the Avocent® Universal
Management Gateway appliance (see table at the beginning of the Service Processor Support
section in these release notes).
b. Create a CD (ISO) or disk (IMG) image file containing the data to be accessed by the server.
Service Processors that do not properly mount a remote block device will usually mount an image
file, even if the file is stored on that same block device.
NOTE: On the IBM BladeCenter, only ISO images map correctly.
After many SPAccess sessions in some browsers, it is possible that all available cookies may be
consumed. If the browser presents an error message that no more cookies are available, please close all
open tabs and windows for that browser to clear the cookies.
When adding a Service Processor, the alias does not accept a space. If a user needs a space in the name,
after adding, they can modify the name via Administration/Targets.
When a Service Processor SP Console session is launched, an SoL Session Launched event is logged in
the appliance event log, and in the DSView™ 4 software event log if the appliance is managed using
DSView™ 4 software.
Power state transitions from Service Processors may not be identified and displayed in the appliance Web
interface or DSView™ 4 software for up to fifteen minutes after the transition occurs.
The Serial-over-LAN Data Buffering Download Log button in the Web interface is currently not functional,
but the log can be manually downloaded from the appliance. An example method to retrieve a log of SoL
history from the appliance shell is:
ssh -t admin:<SP_Name>@<UMG_IP> targetexec solhistory | tee sol.log
New command support
Supported if available
*
Set only
S
5
Unsupported
†
Features inherited from Chassis
G/S
Get and Set