NOTE: The following external sensors were tested with the port connection and test scenarios where sensors were automatically
discovered and monitored by the appliance.
Tested External Sensors
EXTERNAL SENSORS PORT CONNECTION TEST SCENARIOS
SN-Z01 Single
Temperature Probe
TH1/TH2
• Single SN-Z01 sensor connected to each port sequentially.
• Reported as SN-T as it cannot be distinguished from the corresponding
SN-T sensors from the info returned.
• Not chainable as limited by cabling.
Page 7 of 39
Temperature 1 Humidity
simultaneously, where
EXTERNAL SENSORS PORT CONNECTION TEST SCENARIOS
SN-Z02 Three
Temperature Probe
SN-Z03 Three
SN-3C Modular Dry
Contact
SN-2D Modular 2-Door
Contact
SN-TH Modular
Temp/Humidity Sensor
TH1/TH2
TH1/TH2
TH1/TH2
TH1/TH2
TH1/TH2
• Single SN-Z02 sensor connected to each port sequentially.
• Reported as three SN-T sensors as it cannot be distinguished from the
corresponding SN-T sensors from the info returned.
• Not chainable as limited by cabling.
• Single SN-Z03 sensor connected to each port sequentially.
• Reported as two SN-T and one SN-TH as it cannot be distinguished from
the corresponding SN-T/SN-TH sensors from the info returned.
• Not chainable as limited by cabling.
• Single SN-3C sensor connected to each port sequentially.
• Chain of five SN-3C sensors connected to each port sequentially, where
the cable was less than 20 meters in total length.
• Single SN-2D sensor connected to each port sequentially.
• Chain of ten SN-2D sensors connected to both ports
each cable was less than 20 meters in total length.
• Single SN-TH sensor connected to each port sequentially.
• Chain of five SN-TH sensors connected to each port sequentially, where
the cable was less than 20 meters in total length.
SN-T Modular
Temperature Sensor
SN-L Leak Sensor
IRM-S01T Temperature SNSR
IRM-S02TH Temperature
+ Humidity
AD-S Smoke DI1/DI2 Single AD-S sensor connected to each port sequentially.
AD-IM Motion DI1/DI2 Single AD-IM sensor connected to each port sequentially.
TH1/TH2
TH1/TH2
SNSR Single IRM-S02TH sensor connected to the port.
• Single SN-T sensor connected to each port sequentially.
• Chain of five SN-T sensors connected to each port sequentially, where the
cable was less than 20 meters in total length.
• Single SN-T sensor connected to each port
• Not chainable.
• Single IRM-S01T sensor connected to the port
• Chain of two IRM-S01T sensors connected to the port, where the cable
was less than 20 meters in total length.
Page 8 of 39
COMMENTS
7 PDU Support
Tested PDUs and Firmware
CARD READER ALIAS FIRMWARE VERSION
Geist I-02 3.3.3
Geist I-03 5.2.3
Vertiv™ RPC2 (MPX,
MPH, MPH2)
13.0.0.3
Supported in a limited manner, including firmware upgrade and web
access through an SPAccess browser session. Outlet control and
monitoring are not yet supported.
Supported in a limited manner, including firmware upgrade and web
access through an SPAccess browser session. Outlet control and
monitoring are not yet supported.
The PDU userid/password must be supplied to enable firmware upgrade
functionality.
8 Service Processor Support
Tested Service Processors/Servers and Firmware
SERVICE PROCESSOR FIRMWARE VERSION COMMENTS
Cisco UCS-B Chassis and Blades 4.0(1d) N/A
Cisco UCS CIMC/Monolithic (C210) 1.4(3z)
Cisco UCS CIMC/Monolithic (C220) 4.0(1a) N/A
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
Dell C Series (PowerEdge C6220) 2.53 N/A
Dell DRAC 4 (PowerEdge 1850) 1.75 (Build 06.03)
Dell DRAC 5 (PowerEdge 2950) 1.65 (12.08.16)
Dell DRAC/MC 1.6.0
Dell iDRAC blades
(M600/M605/M805)
Dell iDRAC6 blades (M610/M710) 3.85
Dell iDRAC6 monolithics
(R210/R410/R710)
Dell iDRAC7 blade (M520, M620) 2.61.60.60 N/A
1.65
2.91 N/A
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
SSH sessions to the iDRAC6 blades are not functional;
iDRAC6 is only supporting ciphers that are blocked from the
appliance for security reasons. Telnet must be enabled to
discover these iDRAC6 blades. We recommend that Telnet
be disabled by default and disabled following discovery.
Page 9 of 39
SERVICE PROCESSOR FIRMWARE VERSION COMMENTS
Dell iDRAC7 monolithic (R320) 2.61.60.60 N/A
Dell iDRAC8 blade (M630, FC630) 2.61.60.60 N/A
Dell iDRAC8 monolithic (R430) 2.61.60.60 N/A
Dell iDRAC9 blade (M640) and
monolithic (R640)
Dell M1000E Chassis 6.20 N/A
Dell FX2s Chassis 2.20 N/A
Dell VRTX Chassis (Express) 3.20 N/A
FSC iRMC (BX630 S2) 2.30G
FSC iRMC S2 (RX300 S4) 5.76A
FSC iRMC S4 (RX200 S8) 9.08F N/A
HP BladeSystem 4.85 N/A
HP iLO 2 (DL580 G5) 2.33 N/A
HP iLO 3 (DL380 G7) 1.90 N/A
HP iLO 4 (DL360p Gen8) 2.61 N/A
HP iLO 5 (DL360p Gen10) 1.37 N/A
3.21.23.22 N/A
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
IBM BladeCenter (E/8677) BPET68C
IBM IMM (x3550 M2, x3650 M2) YUOOH2B
IBM IMM2 (x3250 M4) 1AOO82E
IBM RSA II (x3550, x3850) GGEP42A
IPMI 1.5 N/A N/A
IPMI 2.0 N/A N/A
Lenovo Flex Chassis 1AON24A(2.0.0) N/A
Lenovo IMM2 (x240 M5) TCOO46E(5.10) N/A
Lenovo XCC CDI328M(2.10) N/A
Page 10 of 39
Support for blades connected to this Service Processor has
been obsoleted. The blades are not tested or maintained
Support for this Service Processor has been obsoleted. It is
not tested or maintained
Support for this Service Processor has been obsoleted. It is
not tested or maintained
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
G (Get only)
S (Set only)
G/S (Get and Set)
Information
Power Control
Alert Destination
Status/Control
Log
Configuration
vKVM
G
SERVICE PROCESSOR FIRMWARE VERSION COMMENTS
Oracle ILOM3 (Sun Server
X3-2)
4.0.4.22
N/A
SUN ALOM (Netra 240) 1.6.10
SUN ELOM (x2200 M2) 3.2
SUN ILOM (Sun Fire x4250) 3.0.6.15f
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
Support for this Service Processor has been obsoleted. It is
not tested or maintained.
Supported Service Processor Features Table
TABLE KEY
(Supported feature)
* (Supported if available)
† (Features inherited from chassis)
D (Only via Direct Command support in the Avocent® DSView™ software)
Power Capping
Sensors
Power
FRU Information
Service Processor
SP Time
LED
System Event
SoL Session
Browser UI
SOL
Telnet Session
SSL
Auto Login SSH
SSH Session
Virtual Media
IPMI 1.5
IPMI 2.0
IDRAC 9 (14G)
IDRAC 8 (13G)
IDRAC 7 (12G)
IDRAC 6 (11G)
Dell C Series
Dell DRAC 5
G* G*/S*
G G/S
G G/S
G G/S
G* G*/S*
G* G*
Dell DRAC 4
G G/S
G G/S
G G/S
G
HP ILO 5
HP ILO 4
HP ILO3
HP ILO2
Page 11 of 39
G/S S*
G/S S*
G/S G/S
G/S G/S
G/S G/S
G/S G/S
G/S
G/S G/S
G G/S
G G/S
G G/S
G/S
* *
* * * *
* * * * * * *
* * * * * * *
* * * * * * *
* * * * * * *
* *
* * * * *
D * * * * D D
* *
* *
* *
* * * * *
* *
* * * *
* *
* *
* *
Information
Power Control
Alert Destination
Status/Control
Log
Configuration
vKVM
Service Processor
Oracle ILOM3
Sun ELOM
Sun ILOM
Sun ALOM
IBM IMM2
IBM IMM
IBM RSA II
Cisco UCS-C
(Monolithic)
FSC IRMC
FSC IRMC II
FSC IRMC S4
Sensors
Power Capping
Power
G
G
G G/S
G* G*/S*
G* G*/S*
FRU Information
SP Time
LED
G/S G/S
G/S G/S
G/S G/S
G/S G/S
G/S G/S
G/S G/S
G/S G/S
G/S
G/S G/S
G/S G/S
System Event
SoL Session
SOL
*
Browser UI
Telnet Session
Auto Login SSH
SSH Session
SSL
D *
D * * * * D D
D *
* * * * * * *
* * * * * * *
D * * * * D D
* * * * *
D * * * * D D
* * * * *
* * * * *
* * D D
* * D D
* * *
Virtual Media
Dell M1000E
Dell M1000E (Blade)
Dell FX2
Dell FX2 (Blade)
Dell VRTX
Dell VRTX (Blade)
Dell DRAC/MC
Dell DRAC/MC
(Blade)
HP BS
HP BS (Blade)
IBM BC
IBM BC (Blade)
Lenovo Flex
Lenovo Flex (Blade)
G G/S
G
G G/S
G
G G/S
G
G
G
G G/S
G
G
G G/S
G
G G/S
G/S G/S
G/S G/S
G/S G/S
G/S G/S
G/S G/S
G/S G/S
G/S
G/S
G/S
G/S
G/S
G/S
G/S
* * * * *
† † † †
* * * * *
† † † †
* * * * *
† † † †
* * *
D
D
* * * * *
† † † †
* * * * *
* * * * *
* * * * * †
*
*
D D
*
† † †
Lenovo XCC
Page 12 of 39
G G/S
G/S G/S
* * * * * †
Information
Power Control
Alert Destination
Status/Control
Log
Configuration
vKVM
Power Capping
Sensors
Power
FRU Information
SP Time
LED
System Event
SoL Session
Browser UI
SOL
Telnet Session
SSL
Auto Login SSH
SSH Session
Virtual Media
Service Processor
Cisco UCS-B
(Chassis)
Cisco UCS-B
(Blade)
Accessible Target
(Generic)
G G
G G
G G/S
G/S
* * * *
*
* * *
*
General Notes and Issues
• Service Processor vKVM access through the Microsoft Edge browser is not supported, unless noted, for the specific Service
Processor.
• Service Processor SSH, Telnet and SoL sessions through the Microsoft Edge browser are not supported.
• 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:
o 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).
o 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.
Page 13 of 39
• 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.
• If the SPAccess port range is modified prior to appliance firmware upgrade, the port range must be reconfigured to the desired value
after the appliance upgrade is completed.
• The SPAccess design assumes that the Service Processor port assignments will not be reconfigured to use different port(s). Please
retain the default port assignments for correct operation.
• Termination of an SPAccess session from within the appliance session tab on a factory restored appliance may cause the appliance
Web interface to become unresponsive. Please use other interfaces to close the SPAccess sessions.
• 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 Avocent® DSView™ software event log if the appliance is managed using DSView™ software.
• Currently, an SoL session cannot be disconnected by clicking the X button at the top right of the viewer window. Please disconnect
the session from the appliance Web interface on the Service Processor session screen.
• Power state transitions from Service Processors may not be identified and displayed in the appliance Web interface or DSView™
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
• The default state of the IPMI/DCMI privilege for IPMI-based SPs managed by the appliance is not displayed for Service Processors
that were discovered prior to appliance firmware upgrade, although any Service Processor added to the appliance prior to appliance
version 2.5.0.8 will use the Administrator IPMI/DCMI Privilege. Please delete and re-add the Service Processor to restore the
correct display.
• HP iLO3 and iLO4 Service Processors may be added or discovered using credentials with an IPMI/DCMI privilege of Administrator,
Operator or User. The management capability of the HP iLO3 and iLO4 Service Processor through the appliance will be limited by
the privilege of the credential used to add the Service Processor. All other Service Processors supported by the appliance can be
added or discovered using credentials with an IPMI/DCMI Administrator privilege.
• The Java 7 Update 51 has introduced strict security requirements where native Service Processor vKVM applets will fail to launch
until the Service Processor supports the Java security requirements. The Service Processor vendor should provide firmware
updates to resolve these issues. Until the updates are in place, consider workaround options that are consistent with your corporate
security requirements.
• When connecting a Service Processor to a private port of the Avocent® Universal Management Gateway appliance for discovery,
ensure that the Service Processor has been configured for DHCP address assignment and reset prior to connection for successful
discovery. If the appliance firmware is updated by USB boot or net boot, it may be necessary to disconnect the Service Processor
and power-cycle or reset it, then reconnect the Service Processor for rediscovery after the appliance is restored to normal operation.
Page 14 of 39
If the Service Processor is reconnected before the appliance is restored, it may be necessary to manually discover the Service
Processor by defining and launching an SP discovery range including the IP address range for the private port.
• After a Service Processor has been added or discovered into the Avocent® Universal Management Gateway appliance, dynamic
data may not be available from the Web interface for up to five minutes and time-outs may be seen during this initial five minute
period, depending on network delays between the Service Processor and the Avocent® Universal Management Gateway appliance.
• When manually adding or discovering Service Processors, occasionally the Service Processor is displayed on the
Administration/Targets/Service Processors page but not in the Targets or the Administration/Targets page of the appliance Web
interface. Close the browser and re-open it to resolve the issue.
•If the Rescue action is taken to restore management of a Service Processor set for automatic periodic password change, please
wait several minutes for the Rescue action to complete.
Service Processor Firmware Upgrade
• The firmware files from the Service Processor vendors can be extracted for upgrade as follows:
o Cisco UCS-B: Use the ucs*.bin file provided by Cisco.
o Cisco UCS-C: Extract the upd-pkg-<model>.cimc.full.<version>.bin file from the <model>-cimc-.<version>.zip file from the
<version>\cimc folder within the compressed executable provided by Cisco. For example, for version 1.4(3t), the upd-pkg-c200-
m1-cimc.full.1.4.3t.bin file is extracted from the c200-m1-cimc.1.4.3t.zip file.
o Dell DRAC5: Extract the firmimg.d5 file from the payload folder within the compressed executable provided by Dell.
o Dell iDRAC6: Extract the firmimg.d6 file from the payload folder within the compressed executable provided by Dell.
o Dell iDRAC7/iDRAC8: Extract the firmimg.d7 file from the payload folder within the compressed executable provided by Dell.
o Dell iDRAC9: Extract the firmimgFIT.d9 file from the payload folder within the compressed executable provided by Dell.
o Dell iDRAC7/8/9 blade programmed through the chassis: Provide the entire update package from Windows. For example, for
version 3.21.26.22, the file is iDRAC-with-Lifecycle-Controller_Firmware_FDMV1_WN64_3.21.26.22.EXE. The Dell CMC
Extended Storage Card must be installed and the Extended Storage feature must be enabled.
o Dell M1000e: Extract the firmimg-<version>-A00.cmc file from the compressed executable provided by Dell. For example, for
version 4.5, the extracted file is fmrimg-4.5-A00.cmc.
o HP iLO2, iLO3, iLO4, and iLO5: Extract the ilox_<version>.bin file from the root folder or the image folder from the compressed
executable provided by HP. For example, for version 2.03 for iLO4, the extracted file is ilo4_203.bin.
o HP BladeSystem: The upgrade file is specifically provided by HP. For example, for version 4.30, the downloaded file is
hpoa430.bin.
o IBM IMM, IMM2: Extract the *.upd from the root folder within the compressed executable provided by IBM.
o Lenovo IMM2: Extract the *.upd from the root folder within the compressed executable provided by Lenovo.
o Oracle ILOM3 Extract the *.pkg from the Model/Firmware/service-processor folder within the compressed executable provided by
Oracle.
Page 15 of 39
• Service Processor firmware maintained in a remote share must be reinstalled in the remote share starting with appliance firmware
version 3.2.0.30.
• Service Processor firmware for an iDRAC7 blade must be downloaded separately from firmware for an iDRAC7 monolithic or tower,
even though the firmware is the same for blades, monolithics and towers.
• Service Processor firmware for an iDRAC8 blade must be downloaded separately from firmware for an iDRAC8 monolithic or tower,
even though the firmware is the same for blades, monolithics and towers.
• The current firmware version of a Service Processor will be displayed as “---“ if the version cannot be identified. Please either re-
discover or delete and re-add the Service Processor to the appliance to try to resolve this issue.
• The alert and optional trap indicating that the Service Processor is not using supported firmware does not currently include the
Service Processor target name.
Cisco UCS-B Chassis and Blades
• If all blades within a Cisco UCB-B chassis are not present following upgrade to this firmware version, please delete the chassis and
any blades that were discovered as standalone Service Processors and rediscover the chassis only to restore access to all blades.
• Blade Virtual Media launches can only be supported if the blade credentials are passed from the viewer back to the Service
Processor unencrypted. A second Virtual KVM / Media button is presented in the Web interface to launch the vKVM session so that
a Virtual Media session can be launched from the vKVM session using the unencrypted credentials. There is a confirmation prompt
to continue the launch. If the Virtual KVM button is used to launch the vKVM session, a Virtual Media session launch from that
vKVM session will fail as the Virtual Media credentials will be encrypted. The Avocent® DSView™ software does not support the
unencrypted Virtual Media launch. Also, launching a blade vKVM through a chassis login does not support the unencrypted Virtual
Media launch.
• Blade vKVM sessions launched through the chassis are not currently supported. Please launch blade vKVM sessions through the
blade underneath the chassis.
• Chassis auto login sessions are not supported.
• An HTML5 vKVM session to the Cisco blade will freeze if virtual media is activated. Please use one of the other viewers for this
function.
• Power capping for the Cisco chassis cannot currently be set to more than 1100 watts. Please access the Cisco UCS Manager
directly to control this function.
• The Cisco blade firmware cannot be updated when the Host Firmware Package within the Firmware Policy is configured to the
Blade Package setting. Please remove this configuration in the Service Processor for proper firmware update operation.
• Power threshold for the Cisco blade cannot currently be configured. Please access the Cisco UCS Manager directly to control this
function.
Cisco UCS-C210 Monolithics
The SPAccess vKVM session is not accessible when launched from the appliance local port interface.
Page 16 of 39
Dell C Series
• The Dell C Series default username and password of root/root is not included in the appliance default names list. If discovery of
these Service Processors is needed, please add the appropriate credentials to the default names list.
• The Dell C Series vKVM and Virtual Media applets fail when launched using Java 8 and when using the VGA console of the
Avocent® Universal Management Gateway appliance. Please use Java 7 Update 71 for these operations.
• Occasionally power control failures are seen on the Dell C Series. Retry these power control operations.
Dell DRAC4 and DRAC5
• When the maximum number of sessions in DRAC4 or DRAC5 has been reached, a new Auto Login or vKVM SPAccess session will
fail. The failure can be recovered by resetting the SP via Telnet or SSH. The command for SP reset is ‘racadm racreset’.
• DRAC5 firmware supports only IE7 and Firefox2 browsers. SP Access sessions, especially vKVM and Virtual Media sessions may
not work in newer versions of Firefox and Chrome and are not supported. SP Access to the DRAC5 is possible with IE9.
• The Dell DRAC5 vKVM and Virtual Media applets fail when launched using Java 8 and using the VGA console of the Avocent®
Universal Management Gateway appliance. Please use the remote Web interface from a Windows client running Java 7 Update 71
for these operations.
• The DRAC5 firmware version may not be displayed properly on the Properties screen through the Web interface following an
appliance upgrade.
• The server type associated with the DRAC5 Service Processor is currently not displayed on the Administration/Targets/SP
Management page.
• The DRAC5 does not support use of the forward slash (“/”) in login passwords. Avoid use of the forward slash in the password
definition.
Dell iDRAC6 Monolithics
• SPAccess vKVM is supported using the Edge browser for this Service Processor.
• SPAccess vKVM sessions using the Java viewer to this Service Processor are failing when Java JRE8u131 and newer is running on
the client. Use the ActiveX viewer or Java JRE8u121 on the client.
• Sensor data is not returned from iDRAC6 monolithics when the Dell server is turned off. After the server power is restored, refresh
the Targets/SP/Sensors tab display, if needed, to update the sensor display.
• Some lower-cost servers using the iDRAC6 Service Processor have a shared network port for the Service Processor and the server.
If these servers are connected to the Avocent® Universal Management Gateway appliance on the public Ethernet port, the server
functions are more easily available to the users. The servers may still be connected to the Avocent® Universal Management
Gateway appliance on a private network port, but there may be firewall configuration needed to enable all the server functions.
Page 17 of 39
Dell iDRAC6 Blades
• SPAccess sessions for the M600, M605 and M805 blade servers are currently not supported. The M600, M605 and M805 blade
servers use a certificate with MD5 signature which is blocked from the Avocent® Universal Management Gateway appliance for
security reasons.
• The Java vKVM viewer within current M610 and M710 blade Service Processor firmware is not compatible with the current Java
8u181 release, so SPAccess vKVM is not functional through the appliance local or remote Web interface.
• SSH Auto Login sessions are currently failing on the M610 and M710 blade Service Processor running v3.75 firmware due to an
extended response delay in the Service Processor. Please use v3.60 of the Service Processor firmware to avoid this issue.
• SPAccess vKVM is supported using the Edge browser for the M600, M605 or M805 blade Service Processors.
• SPAccess vKVM is not supported with the Internet Explorer 11 browser in Windows 10 for the M600, M605 or M805 blade Service
Processors, as this browser is not supported through the native Service Processor interface directly.
• On the M1000e, occasionally clicking the Launch iDRAC GUI button for one of the blades will not complete a single sign-on login
due to a Dell limitation. Please log in manually in these cases.
• When M600, M605 or M805 blades are discovered by the appliance as standalone Service Processors, occasionally the SPAccess
Browser and SPAccess Browser-Auto Login buttons are not enabled in the Web interface or in the Avocent® DSView™ software. If
this occurs, please delete the Service Processor from the appliance, reset the Service Processor, and then add the Service
Processor back into the appliance.
• Power information is not available from M600, M605 or M805 blades.
• The M600, M605 and M805 blade Virtual KVM Java applets now fail when launched from a client running Java 8, which means they
will fail using the VGA console of the Avocent® Universal Management Gateway appliance. Please use the remote Web interface
with the client running Java 7 Update 71 for these operations.
• When a Virtual KVM session is launched for a M610 and M710 blade that is discovered through the M1000e chassis, the chassis
vKVM preference is not used. If the alternate viewer is preferred, please launch the desired viewer through the blade native Web
interface.
• Virtual Media connections to the iDRAC6 blade Service Processors are not supported from the appliance local port interface as the
Service Processors do not natively support this environment.
Dell M1000e CMC
• The login process for the M1000e may take up to 20 seconds after proper username and credentials are presented, so it may take
several seconds to access some features in the Avocent® Universal Management Gateway appliance Web interface. For example,
displaying power information may take 15-20 seconds for an M1000e chassis.
• When connecting an M1000e chassis to a private port of the appliance, SPAccess Auto Login sessions to blades either directly or
through the chassis may intermittently abort if using FF or IE. If this is seen, try using Chrome.
• Each SPAccess session launched to blades in a blade chassis using blade-through-chassis (use of the single sign-on feature of the
chassis to access the blades indirectly through the chassis) opens a separate session on the chassis, so it is possible that all active
Page 18 of 39
sessions for the chassis may be consumed if multiple sessions are launched in a short period of time. If this happens, please log out
of active blade sessions and allow time for the chassis to time out its sessions.
• An HTML5 vKVM session launched from a blade installed in an M1000e blade chassis when the session was initiated by logging
into the chassis is failing in the native Service Processor Web interface due to a limitation in the Service Processor firmware. The
SPAccess sessions that operate in this scenario are also failing. To work around the Service Processor limitation, either use the
Java or ActiveX viewers, or add the blade to the appliance as a standalone target.
• SPAccess sessions may now be successfully launched directly to Dell M610/M710 (iDRAC6) blade servers with iDRAC6 Service
Processor firmware 3.50; however, sessions launched through the chassis are still failing. Please add or discover the individual
iDRAC6 blades separately from the chassis (if this has not already been done), then launch SPAccess sessions directly to the
iDRAC6 blade server.
• SPAccess sessions launched to iDRAC blades in an M1000e blade chassis are currently not functional. Please add or discover the
individual iDRAC blades separately from the chassis (if this has not already been done), then launch SPAccess sessions directly to
the iDRAC blade server.
• SoL data buffering to blades installed in an M1000e blade chassis is currently not functional.
• SPAccess vKVM is not supported with the Internet Explorer 11 browser in Windows 10 for the M600, M605 or M805 blade Service
Processors, as this browser is not supported through the native Service Processor interface directly.
• SPAccess is not supported with the Internet Explorer 11 browser in Windows 10 for the M610 and M710 blade Service Processors.
Dell iDRAC7 Monolithics and Blades
• SPAccess vKVM is supported using the Edge browser for the monolithic Service Processors.
• Java vKVM sessions for iDRAC7 blades discovered thru the chassis are currently not functional. Please use the HTML5 vKVM
viewer for these sessions.
• The Virtual Console plug-in in the native iDRAC7 Web interface cannot be selected during an SPAccess autologin or browser
session. Please use the SPAccess vKVM to launch the vKVM (Virtual Console) session.
• SPAccess is not supported using the Internet Explorer 11 browser in Windows 10 for the monolithic or blade Service Processors, as
this browser is not supported through the native Service Processor interface directly.
• SPAccess Browser-only sessions may not work to an iDRAC7 when using the VGA Console. Manually launch a new tab and
browse using (https://<IP>) to the SP using the Browser Tabs on the VGA Console.
• The Dell iDRAC7 Service Processor does not natively support Internet Explorer 11 without compatibility mode set in the browser.
Please also set compatibility mode when SPAccess sessions are launched.
• Some lower-cost servers using the iDRAC6 Service Processor have a shared network port for the Service Processor and the server.
If these servers are connected to the Avocent® Universal Management Gateway appliance on the public Ethernet port, the server
functions are more easily available to the users. The servers may still be connected to Avocent® Universal Management Gateway
appliance on a private network port, but there may be firewall configuration needed to enable all the server functions.
Page 19 of 39
• The iDRAC7 Basic Management Service Processor is currently not automatically discovered. Please manually add as an IPMI
Service Processor.
Dell iDRAC8 Monolithics and Blades
• SPAccess vKVM is supported using the Edge browser for these Service Processors.
• SPAccess vKVM is not supported with the Internet Explorer 11 browser in Windows 10, as this browser is not supported through the
native Service Processor interface directly.
• The Virtual Console plug-in in the native iDRAC8 Web interface cannot be selected during an SPAccess autologin or browser
session. Please use the SPAccess vKVM to launch the vKVM (Virtual Console) session.
• The SSH button may be disabled for these Service Processors. If so, please use the Command Line Interface (CLI) to initiate the
SSH session.
• An SPAccess vKVM session is currently not launching to the iDRAC8 blade when the appliance is operating in DSView™ software
proxy mode. Please use the appliance Web interface or DSView™ software non-proxy mode for this function.
• A SPAccess HTML5 vKVM session is currently not launching to the iDRAC8 monolithic server through the local Web interface.
Please either use the remote Web interface or the Java or ActiveX viewers on the local Web interface for this function.
• A Virtual Media device cannot be mapped during a SPAccess HTML5 vKVM session. Please use the Java or ActiveX viewers for
this function.
Dell iDRAC9 Blades
• An SPAccess HTML5 vKVM session is currently not launching to the iDRAC9 blade. To work around this limitation, please use the
Java or ActiveX viewers.
• An SPAccess vKVM session is currently not launching to the iDRAC9 blade when the appliance is operating in DSView™ software
proxy mode. Please use the appliance Web interface or DSView™ software non-proxy mode for this function.
• The Backspace and Delete keys are not functional during a Telnet session to the iDRAC9 blade or monolithic Service Processor.
Please use the SSH session instead of Telnet, or press CTRL+Backspace to delete characters.
Dell iDRAC9 Monolithics
The Backspace and Delete keys are not functional during a Telnet session to the iDRAC9 blade or monolithic Service Processor.
Please use the SSH session instead of Telnet, or press CTRL+Backspace to delete characters.
Dell FX CMC and Blades
An SPAccess vKVM session is currently not launching to the FX blade when the appliance is operating in DSView™ software proxy
mode. Please use the appliance Web interface or DSView™ software non-proxy mode for this function.
FTS iRMC
Power data can be retrieved from FSC iRMC Service Processors only if their firmware includes the DCMI IPMI extensions (such as the
Intel Node Manager).
Page 20 of 39
FTS iRMC S2
• Power data can be retrieved from FSC iRMC S2 Service Processors only if their firmware includes the DCMI IPMI extensions (such
as the Intel Node Manager).
• The Java vKVM viewer within the current iRMC S2 Service Processor firmware is not compatible with the current Java 8u131
release, so SPAccess vKVM is not functional through the appliance local or remote Web interface. The previous Java 8u121 release
appears to remain compatible with the Service Processor firmware, if use of a previous Java release is consistent with the security
policy of the customer.
• iRMC S2 SPs that use login passwords containing the ampersand (&) character cannot be discovered or managed by the Avocent®
Universal Management Gateway appliance. The SP can be discovered and managed when the login passwords do not contain the
ampersand character.
• The vKVM (Video Redirection) viewer will not start if the user starts a Browser or Auto Login session and manually browses to the
Video Redirection (non-Java Web Start) in the iRMC browser UI. The user should instead use the JWS launcher for video
redirection.
• The FSC iRMC S2 Service Processor only supports firmware upgrade through its native Web interface, so automated firmware
upgrade through the Avocent® Universal Management Gateway appliance is not supported.
• SPAccess is not supported with the Internet Explorer 11 browser in Windows 10, as this browser is not supported through the native
Service Processor interface directly.
FTS iRMC S4
• When launching an Auto Login SPAccess session, an extra prompt appears that the user must click to continue the log in to the
Service Processor.
• The Java vKVM viewer within the current iRMC S4 Service Processor firmware is not compatible with the current Java 8u131
release, so SPAccess vKVM is not functional through the appliance local or remote Web interface. The previous Java 8u121 release
appears to remain compatible with the Service Processor firmware, if use of a previous Java release is consistent with the security
policy of the customer.
• The Java vKVM viewer within the current iRMC S4 Service Processor firmware is not compatible with the current Java 8u131
release, so SPAccess vKVM is not functional through the appliance local or remote Web interface. The previous Java 8u121 release
appears to remain compatible with the Service Processor firmware, if use of a previous Java release is consistent with the security
policy of the customer.
• SPAccess vKVM is not supported when the HTML5 viewer is selected for this Service Processor. Please configure the Service
Processor to use either the Java or ActiveX viewers for this functionality.
• Virtual Media connections to the FTS iRMC S4 Service Processor are not supported from the appliance local port interface as the
Service Processor does not natively support this functionality in a Linux environment.
• SoL configuration for the FTS iRMC S4 Service Processor is currently not functional.
• Power capping configuration for the FTS iRMC S4 Service Processor is currently not functional.
Page 21 of 39
HP iLO2
• SoL sessions to iLO2 blades are currently not functional.
• SPAccess sessions for the iLO2 servers launch very slowly. Please wait up to three minutes for the launch to complete.
• SPAccess vKVM is not supported with the Internet Explorer 11 browser in Windows 10.
HP iLO3
• Single quotation mark characters are not permitted in username and passwords entered in the SP browser UI for the iLO 3.
• The indicator blink control should not be enabled in the appliance Web interface since the iLO3 does not support this function.
• The SoL baud rate selection should not be enabled in the appliance Web interface since the iLO3 does not support this function.
• The currently supported iLO3 firmware has compatibility issues with the Firefox browser version 33, which also impacts the
SPAccess vKVM operation.
• The currently supported iLO3 firmware has compatibility issues with the Chrome browser version 45. Please use either the Internet
Explorer or Firefox browsers for SPAccess vKVM operation.
• SPAccess vKVM is only supported using the Java viewer with the Internet Explorer 11 browser in Windows 10.
• An iLO3 with a password containing the ampersand special character (&) cannot currently be added, discovered or monitored by the
appliance. Please use a password without this special character.
HP iLO4
• Single quotation mark characters are not permitted in username and passwords entered in the SP Browser UI for the iLO 4.
• The indicator blink control should not be enabled in the appliance Web interface since the iLO4 does not support this function.
• The HP iLO4 Service Processor appears to have a limitation where the vKVM applet is not launched when clicking the Java
launcher buttons after logging into the Service Processor directly using the Firefox browser. This function works correctly when the
iLO4 is directly accessed using Internet Explorer and Chrome browsers, and when the SPAccess vKVM launch in the Avocent®
Universal Management Gateway appliance Web interface.
• The Virtual KVM Native ActiveX preference selection for iLO4 should actually be labeled as “Native .Net”.
• The HP iLO3 and iLO4 Service Processors can connect virtual media sessions when the client is the Avocent® Universal
Management Gateway appliance local port or a PC running a Linux operating system using these steps:
o Select Java IRC within the Remote Console section.
o Enter the physical USB drive name in the Local Image File textbox in the iLO3/4 UI. The drive name will be similar to
“/dev/sdc1”, where the sdc1 would be replaced with the actual drive name associated with the USB slot.
NOTE: After a Virtual Media session is complete, the vKVM session window will disappear and the vKVM session must be restarted.
• The currently supported iLO4 firmware has compatibility issues with the Chrome browser version 45. Please use either the Internet
Explorer or Firefox browsers for SPAccess vKVM operation.
• SPAccess vKVM is only supported using the Java viewer with the Internet Explorer 11 browser in Windows 10.
Page 22 of 39
• An iLO4 with a password containing the ampersand special character (&) cannot currently be added, discovered or monitored by the
appliance. Please use a password without this special character.
• Configuration of alert destinations for iLO4 Service Processors is currently not functional.
HP BladeSystem and Blades
• The HP Integrity blade product line is not supported as these blades use a different management interface than the ProLiant blades.
• The HP BladeSystem firmware supported by the Avocent® Universal Management Gateway appliance does not support the
Chrome browser. Use Firefox or IE browsers for SP Access sessions to the BladeSystem.
• Occasionally, all HP iLO blades within a HP BladeSystem chassis are not discovered as standalone targets when adding these
blades as new targets. Please attempt to discover these blades again to complete the add target operation.
• Each SPAccess session launched to blades in a blade chassis using blade-through-chassis (use of the single sign-on feature of the
chassis to access the blades indirectly through the chassis) opens a separate session on the chassis, so it is possible that all active
sessions for the chassis may be consumed if multiple sessions are launched in a short period of time. If this happens, please logout
of active blade sessions and allow time for the chassis to timeout its sessions.
• SPAccess sessions are not functioning to the HP BladeSystem chassis or blades due to an obsolete default certificate. Update the
HP Blade System chassis certificate in the Service Processor Web interface by selecting Active Onboard Administrator - Certificate
Administration - Certificate Request - Generate a self-signed certificate.
• SPAccess vKVM sessions using the Java viewer launched to blades in an HP BladeSystem blade chassis are not currently
supported in a direct connection to the blade chassis or through the appliance. Please either use the ActiveX viewer or manage the
blade as a standalone Service Processor.
• SPAccess vKVM is not supported with the Internet Explorer 11 browser in Windows 10 when an iLO2 blade is discovered through
the BladeSystem chassis.
• SoL data buffering to blades installed in a HP blade chassis is currently not functional.
IBM RSA-II
• When a vKVM session is connected on an RSA-II server, a second login with the same user ID will cause the original vKVM session
to be disconnected. This includes a second login through the Avocent® Universal Management Gateway appliance which will use
the same user ID. This behavior is by design in the RSA-II servers.
• Intermittent load failures of the vKVM and Virtual Media applets on RSA-II servers have been recorded when the JRE is allowed to
keep temporary files on the computer. When using these vKVM and Virtual Media applications on RSA-II servers, Avocent®
recommends setting the JRE to disallow temporary file storage through the Java Control Panel.
• vKVM operation to RSA-II servers is incompatible with JRE-6u13. Clients should use JRE-6u14 or later for these applications.
• The native browser UI for the IBM 3950 RSA-II server will not allow log in if the password contains special characters unless the SP
firmware is upgraded to A3EP40A or later.
Page 23 of 39
IBM BladeCenter and Blades
• If the SP discovery feature is used to manage the IBM BladeCenter, the IBM BladeCenter needs to be configured so that its lockout
period after five login failures is one minute, if this setting is consistent with corporate security requirements. This setting is located
within the IBM BladeCenter web interface under System-MM Control-Login Profiles-Global Login Settings. Otherwise, the IBM
BladeCenter must be manually added to the appliance.
• The vKVM viewer within the IBM BladeCenter will not load when launched under the latest Chrome and Firefox browsers. Please
use the Internet Explorer browser for this functionality. The SPAccess vKVM even using the Internet Explorer browser is failing to
load when using the latest (Java 8 or 9) run-time environments. The previous Java 7u60 release appears to remain compatible with
the Service Processor firmware, if use of a previous Java release is consistent with the security policy of the customer.
• When adding an IBM BladeCenter to an Avocent® Universal Management Gateway appliance, the user account of the IBM
BladeCenter provided to the Avocent® Universal Management Gateway appliance must have its “Maximum simultaneous active
sessions” set to 0.
IBM IMM Monolithics
• The password set functionality does not support the double quote ( ” ) special character as the character is not supported by the
Service Processor.
• Remote SPAccess sessions for the IMM monolithic servers are currently not functional directly to the Service Processor or thru the
appliance. SPAccess sessions launched through the appliance local port are functional.
• SPAccess vKVM is supported using the Edge browser for this Service Processor.
• SPAccess vKVM is only supported using the Java viewer with the Internet Explorer 11 browser in Windows 10.
• IMM-based monolithic servers purchased with the “IMM Standard” option do not support vKVM. The Avocent® Universal
Management Gateway appliance cannot detect the “IMM Standard” configuration prior to web interface login, so the user is not
notified until after the vKVM login attempt.
• The IMM Monolithic servers do not support use of the special characters ':', '&', '\' and '<' in login passwords.
• If the SP discovery feature is used to manage any type of IBM IMM or BC server, the IMM needs to be configured so that its “lockout
period 5 login failures” is one minute. This setting is located within the IMM web user interface under System -IMM Control-Login
Profiles-Global Login Settings.
• SPs may deny login requests if there are too many users/connections; this can result in 500-Internal Server Error messages being
displayed when starting SPAccess sessions to the IMM. Check if there are multiple sessions connected to the SP using the SP's
native Web interface and close them. It may also be necessary to reset the SP to restore connectivity.
• Remote Control sessions launched from the IMM’s native Web Page in an SPAccess Browser or Auto Login session may fail to start
using the Chrome browser. If this issue is seen, try using Firefox or IE9.
IBM IMM2 Monolithics
• SPAccess vKVM is supported using the Edge browser for this Service Processor.
Page 24 of 39
• SPAccess vKVM is not supported with the Internet Explorer 11 browser in Windows 10, as this browser is not supported through the
native Service Processor interface directly.
• SPAccess sessions to IMM2-based monolithic servers may not function correctly using the Google Chrome version 28 browser.
Please upgrade the browser to version 29 or later.
• The IBM IMM2 Service Processor does not natively support Internet Explorer 11 without compatibility mode set in the browser.
Please also set compatibility mode when SPAccess sessions are launched.
• When logging out of an SPAccess session to a IMM2-based server, all page elements are not downloaded. Refreshing the browser
window will restore all page elements.
• Configuration of alert destinations for IBM IMM2 monolithic Service Processors is currently not functional.
IPMI 2.0 Service Processor
SPAccess vKVM sessions are not supported for this generic Service Processor, but this option is presented for some generic Service
Processors. Please ignore this option.
Lenovo Flex Chassis
• Serial-over-LAN (SoL) configuration is currently not supported for the Lenovo Flex chassis or its blades.
• Configuration of alert destinations for the Lenovo Flex chassis is currently not functional.
• When attempting to launch a blade-through-chassis login from an SPAccess session to the chassis, the blade login must use https.
Lenovo IMM2 Blades
• SPAccess vKVM is not supported with the Internet Explorer 11 browser in Windows 10, as this browser is not supported through the
native Service Processor interface directly.
• ActiveX vKVM sessions for IMM2 blades discovered thru the chassis are currently not functional. Please use the Java vKVM viewer
for these sessions.
• SPAccess vKVM using the ActiveX viewer does not successfully launch with the initial launch action. The viewer must be launched
again manually for proper operation.
• SPAccess vKVM is not supported when the HTML5 viewer is selected for this Service Processor and a blade-thru-chassis session
is launched. Please discover the IMM2 blade as a separate Service Processor for this functionality.
Lenovo XCC
• Occasionally, the desktop screen is not displayed at the launch of a vKVM session using the Chrome browser. Please terminate and
relaunch the session to restore the desktop display.
• SPAccess vKVM sessions to the XCC will disconnect if the XCC is connected to one of the private IP ports of the appliance.
Please orient the XCC on the public IP ports to support this function.
Page 25 of 39
Oracle ILOM3 Monolithics
• The Oracle ILOM3 can only be managed when connected to a public interface of the Avocent® Universal Management Gateway
appliance.
• The Oracle ILOM3 viewer CD-ROM redirection is not compatible with the appliance local port environment. Please use the remote
Web interface for this function.
Sun ALOM, ELOM, ILOM
• ILOM servers must have their http service running to be properly discovered using the SP Auto-Discovery or IP Discovery features.
If the http server is not running, the ILOM must be added to the Avocent® Universal Management Gateway appliance using the
Manual SP Add feature.
• ALOM servers lack a management web interface natively. The Avocent® Universal Management Gateway appliance does not
support custom implementations of ALOM that include a Web interface.
• ELOM and ALOM SPs that use login passwords containing special characters cannot be discovered or managed by the Avocent®
Universal Management Gateway appliance. These SPs can be discovered and managed when the login passwords do not contain
special characters.
IPMI 2.0
SP Access Browser sessions to LO100 servers added to the appliance with IPMI 2.0 profiles are not supported.
9 External Network Port Usage
The table below identifies the network port range, the built-in service name defining the port range, and a description of the port range
usage.
NOTE: Incoming connections on all ports are blocked by default, and these firewall policies are exceptions to that default policy.
PORT RANGE SERVICE NAME FIREWALL POLICY DESCRIPTION AND USAGE
0 srv-PING
20 srv-FTP-Data Open to allow appliance firmware upgrade.
21 srv-FTP-Commands Open to allow appliance firmware upgrade.
22 srv-SSH-Serial-Session Open to allow SSH sessions to appliance and Service Processor Management.
23 srv-Telnet-Session Open to allow Telnet sessions to appliance.
53 srv-DNS Open to allow DNS connectivity.
67-68 srv-DHCPD Blocked to disallow DHCP requests to the appliance over the public interfaces.
69 srv-TFTP-Services Open to allow UMIQ module and Service Processor firmware update.
Open to allow network connectivity verification over icmp. If Related or
Established connections are blocked, Service Processor discovery will fail.
80 srv-HTTP-Services Open to allow Service Processor firmware update.
Page 26 of 39
PORT RANGE SERVICE NAME FIREWALL POLICY DESCRIPTION AND USAGE
137 srv-NetBIOS-NS Used for Samba client connectivity initiated by the appliance.
138 srv-NetBIOS-DS Used for Samba client connectivity initiated by the appliance.
139 srv-NetBIOS-SS Used for Samba client connectivity initiated by the appliance.
161 srv-SNMP Open to allow connectivity to PDUs and other SNMP-based targets.
162 srv-SNMP-Traps Open to accept SNMP traps from PDUs and other SNMP-based targets.
443 srv-Web-UI
445
502 srv-Modbus
514 srv-External-syslog Open to allow Syslog server functionality.
623 N/A Used for IPMI client connectivity initiated by the appliance.
843 srv-Adobe-Flex Not included in firewall policy, no longer required by appliance.
1078 srv-DS-View-proxy
2068 srv-KVM-session Open to allow KVM sessions.
3211 srv-Discovery-protocol Open to allow the DSView™ software to discover the appliance.
3212 srv-DRIP-protocol Open to allow UMIQ module connectivity.
3502 srv-DS-View-plug-in Open to allow DSView™ software connectivity.
3871 srv-Security-protocol
srv-MS-DirectoryService
Open to allow Web interface operation, HTML5 KVM and serial sessions, and
Service Processor Management using Redfish.
Used for Samba client connectivity initiated by the appliance.
Open to allow connectivity to Modbus-based devices scanned by the Trellis™
platform.
Open to allow KVM and serial sessions to be proxied through the DSView™
software.
Open to allow DSView™ software -launched sessions and appliance
authentication using DSView™ software.
4011 srv-PXE-boot-server
4112
4206
4321 srv-UMG-Service-1 Blocked by default, policy and service defined for ease of debug.
4440 srv-UMG-Service-2 Open to allow Trellis™ platform connectivity.
6379 srv-UMG-Service-14 Not included in firewall policy, service defined for ease of debug.
6443 srv-Trellis-Platform-OHS Open to allow Trellis™ platform connectivity.
7001 srv-UMG-Service-9 Open to allow Telnet access to serial port connections.
Page 27 of 39
srv-Data-loggingDSView
srv-KVM-websocksession
Open to enable PXE boot server functionality for Service Processors (currently not
supported)
Open to allow serial port logging to DSView™ software (currently not supported).
Open to allow HTML5 KVM sessions using this alternate port.
PORT RANGE SERVICE NAME FIREWALL POLICY DESCRIPTION AND USAGE
8011 srv-UMG-Service-3 Open to allow Trellis™ platform connectivity.
8012 srv-UMG-Service-4 Open to allow Trellis™ platform connectivity.
8080 srv-UMG-Service-6 Open to allow Java viewer download to client.
8123 srv-UMG-Service-7 Open to allow Service Processor firmware upgrade.
8128 srv-UMG-Service-8 Blocked by default, policy and service defined for ease of debug.
8161 srv-UMG-Service-13 Blocked by default, policy and service defined for ease of debug.
9002 srv-Trellis-Event Open to allow Trellis™ platform connectivity.
9003 srv-Trellis-Event-2 Open to allow Trellis™ platform connectivity.
10191 srv-UMG-Service-5 Blocked by default, policy and service defined for ease of debug.
11099 srv-UMG-Service-10 Blocked by default, policy and service defined for ease of debug.
32123 srv-UMG-Service-11 Blocked by default, policy and service defined for ease of debug.
47777-48177 srv-Velocity-BACNet
Open to allow connectivity to BACNet and Velocity-based devices managed by
the Trellis™ platform.
50000-59999 srv-SPAccess Open to allow SPAccess sessions.
61616 srv-UMG-Service-12 Blocked by default, policy and service defined for ease of debug.
10 Known Issues
Upgrading
• KVM sessions may fail after the upgrade of an appliance that had been previously added to the Avocent® DSView™ management
software prior to the upgrade. Resyncing the Avocent® Universal Management Gateway appliance in question will restore KVM
functionality.
• An appliance firmware version that is older than the currently installed appliance firmware should not be used in an upgrade
operation. Please use the rollback operation to revert to an older firmware version.
• When performing a local port upgrade using the CLI, please format the USB drive using the FAT32 format.
Command Line Interface (CLI)
• Event syslog enable/disable configuration using the command line interface is currently not functional. Please use the appliance
Web interface for this function.
• When disabling DSView™ software access, please reboot the appliance after the operation to ensure that all active connections to
the DSView™ software are terminated.
• When enabling DSView™ software access, please delete the appliance and re-add it to the DSView™ software to restore secure
mode operation.
Page 28 of 39
Local Serial Console
If there is a need to execute a downloaded script through the local serial console or from a SSH session, the script to execute must be
in the /download folder of the appliance. Scripts contained within the /diag folder can no longer be executed.
VGA Console
NOTE: Enabling the URL bar will allow anyone with access to the VGA console to use the browser.
• When rebooting the system, there is a small chance that the Restarting system message followed by machine restart will appear on
the VGA Console. If this occurs, a power cycle of the Avocent® Universal Management Gateway appliance will be needed to
recover the KVM appliance.
• The VGA console does not support the Avocent® Universal Management Gateway appliance firmware upgrade feature. You can,
however, use the firmware upgrade feature via the Avocent® Universal Management Gateway appliance Command Line Interface
(CLI) console by logging in as an admin user and selecting Update Firmware from the menu.
• If the user attempts to log in to the appliance with an expired account when the language is set to non-US English, an Account has
Expired error message is not displayed.
• If the KVM session window is sent to the background by the Web interface session window, please press Alt+Tab to restore the
KVM session window to the foreground.
Authentication
• SSH connections can be made to disabled Serial Ports; however, the connection to the Serial Target itself will not be established.
• LDAP authentication will fail if not working if DNS servers are configured, but are not accessible by the appliance. Remove the DNS
server configuration as a workaround if needed.
Networking
• You cannot set a bridged interface as the default gateway. Likewise, if you add the default gateway to a bridged connection, you will
lose your default gateway.
• When switching networking mode from Failover to Failover-Routed, please switch to Normal mode first.
• When using the appliance in a failover scenario, Service Processors, PDUs and any other IP-based targets should be connected to
a private port of the appliance and a public port so that access to those targets is retained following a failover.
• If the appliance was configured to use a static IP address prior to an appliance firmware upgrade, then the DNS settings are not
retained after the upgrade is complete. Re-enter the DNS settings manually as a workaround.
• On the initial attempt to set the first valid firewall policy, an Unknown Policy error occurred error may appear, but the policy is
actually defined. This error does not reoccur on subsequent valid policy definitions.
• When changing the DHCP server for private interfaces to be internal or external from the Administration/Targets/Port
Configuration/DHCP Settings screen of the Web interface, network communication to the IP-based targets may be lost as the IP-
based targets will retain the assigned network addresses from the previous DHCP server. To restore communication, reset the
targets or disconnect and then reconnect the targets to the private port of the appliance so that the targets will request a new IP
address from the new DHCP server.
Page 29 of 39
Web Interface
• You cannot set a bridged interface as the default gateway. Likewise, if you add the default gateway to a bridged connection, you will
lose your default gateway.
• Occasionally the Web interface may stop responding and the cursor will continuously spin when hovering over the Web interface. If
this occurs, please refresh or reload the browser tab to continue.
• Occasionally when multiple clients are actively logged into the Avocent® Universal Management Gateway appliance, an exception
error may be seen on one of the clients. Select OK to bypass the error and continue the session
• The password strength setting is not functional and will cause errors if set. As a workaround, please keep the strength setting to
None and maintain the desired password strength through assignment convention.
• If a default user (admin/operator/user) is deleted from the appliance, that deleted user cannot be re-created.
• If the default user operator or user is deleted from the appliance, their corresponding Power User or User roles will not operate
correctly.
• The contents of the Targets page are not always automatically refreshed when running the Firefox browser. If this occurs, please
manually refresh or use the Internet Explorer or Chrome browsers.
• If a Discovery Range cannot be set following an appliance time configuration, please reboot the appliance to restore Discovery
Range configuration.
• Events are not currently generated after scheduled backup.
• If the system date is set to January 1, 1970 (maybe through expiration of the clock battery), a user cannot log in to the Web interface
using the Internet Explorer browser. Please use the Firefox or Chrome browsers to log in and correct the date. Use an NTP server, if
possible, to automatically adjust the date.
• The USB ports cannot currently be disabled using the Web interface.
• The Avocent® Universal Management Gateway appliance uses a polling mechanism to determine the Service Processor power
state. Due to this, there will likely be a delay between when the state changes and the Avocent® Universal Management Gateway
appliance updates its user interface.
• A Server Processor’s status may remain as Powered On if that Service Processor has lost power. If there is a concern about the
power status, perform a ping test against the IP address of the Service Processor to validate.
• The default login page of a Web interface session does not match the default language setting of the browser and must be set
manually when using the Internet Explorer browser.
• When performing a Factory Reset on a UMIQ module, an exception error may be displayed.
• An incorrect error message is displayed when an invalid DHCP range is entered in the Dynamic Ranges table of the