Released: February 2016
Uplogix, Inc. is pleased to announce the release of version 5.3.0 software for all models of the Uplogix Local Manager and for the Uplogix Control Center.
The following software features, improvements, and fixes have been made in both the Local Manager and the Control Center software.
Uplogix Local Manager Updates
New Features and Improvements
New Hardware: European/Australian LTE Internal Cellular Modem
Uplogix now offers an internal LTE modem for the 500 and 5000 platforms that is certified for the European, Great Britain, Australia, and New Zealand markets.
New Feature: Support for MRV LX Series Switched Power Controllers
The Uplogix Local Manager now supports advanced management of MRV’s LX series switched power controllers.
Improvement: More Efficient Configuration Backup for Cisco Devices
The advanced Cisco device driver now calculates the checksum of configuration files on Cisco devices during a configuration backup operation to determine if the device configuration is different than the current configuration stored on the Local Manager – time is not wasted backing up the configuration if it is the same.
Issues Addressed in This Release
- Advanced Cisco IOS/IOS-XE Driver Fixes and Improvements
- Configuring a Local Manager port to manage a Cisco IOS/IOS-XE device, where the pull and push configuration methods uses a file transfer method rather than the console/CLI interface, now takes less time to fail over to using the console if there is no network connectivity between the Local Manager and the managed device.
- Lengthened an OS update timeout value to avoid aborting an OS update due to longer than usual upgrade times (for example, microcode updates to Cisco 3750X or 3850 switches).
- Fixed an issue that might cause an OS update via TFTP to a 3750 stack of switches to fail to initiate.
- Fixed an issue that could randomly cause the Cisco IOS driver to report that an OS update failed when it actually succeeded.
- Fixed an issue that can cause a configuration update to fail on Cisco IOS-XE devices when the configuration snippet being pushed deletes a locally defined username from the configuration.
- Fixed an issue that can cause the Cisco IOS advanced driver to fail to back up an IOS-XE OS file from a device in the case of a longer OS filename.
- Advanced Cisco NX-OS Driver Fixes and Improvements
- Fixed an issue that caused a longer Nexus 7K Dual Supervisor OS upgrade operation to time out before it was complete.
- Fixed an issue that can cause the state of the Local Manager port connected to the console port of the new active/old standby Nexus 7K supervisor to be listed as “unknown” after an NX-OS upgrade.
- Fixed an issue that caused pushing a startup-config to a Cisco Nexus switch via TFTP over a dedicated Ethernet connection to fail.
- Fixed an issue that can cause the Local Manager to report a failure while updating a Cisco Nexus switch running-configuration when the configuration update was successful.
- Fixed an issue that could cause an OS policy alarm on a Cisco Nexus switch when the standard OS matches the current OS.
- Fixed Cisco IOS and NX-OS drivers so they can successfully upgrade a device that has no OS stored in flash because it previously loaded its OS via TFTP (i.e. boot TFTP).
- An SSH pass-through session to a managed device via the UCC CLI Applet (blue CLI button at port level) will not time out if port forwarding is active.
- Fixed an uncommon issue that can cause a Local Manager syncing its time with the UCC (rather than using NTP) to report that its clock is out of sync with the UCC.
- Fixed an issue that prevented the configuration of multiple secure virtual ports to Avocent Universal Management Gateway devices.
Known Issues in This Release
- The push startup-config function is not currently supported for dual supervisor Nexus switches
Uplogix Control Center (UCC) Updates
New Feature: Uplogix Deployment Overview
The Administration section of the UCC now provides a deployment overview page that lists all of the Uplogix Local Managers with helpful information such as status (alarming or out-of-band), serial number, model number, IP address, uptime, software version, last heartbeat timestamp, heartbeat state (not currently heartbeating, full heartbeat, or minimal heartbeat), number of physical and virtual ports, and SLV license information. This page also includes sorting and filtering capabilities.
Improvement: Users Can Now Export User Session Logs, Device Configuration Files, Show Tech and POST Output
User session logs are a complete log of everything a user does when logged into a Local Manager or passing through it to manage a connected device – this information is accessed in the ‘Session Logs’ section of the Local Manager summary page. In addition to being viewable for auditing purposes, session logs can now be exported as well.
Users can also now export a running configuration, a startup configuration, and the output of the show tech command or the Power on Self Test (POST) log if these artifacts are available on the Local Manager ports.
Improvement: Port Forwarding Defaults Local Port Selection to Forwarded Port If Available
Users who use the CLI button to open an SSH session to a Local Manager and activate port forwarding will now find that the applet will set the local port on the user’s workstation to the same port as the forwarded port number if that port is available on their workstation. For example, if a user forwards port 443 on a managed device to their workstation, the applet will use port 443 on the local workstation if it is available (i.e. https://127.0.0.1:443 on the local workstation).
Issues Addressed in This Release
- Fixed CLI Applet to show the green and red status colors for port forwarding when setting and applying the local port number.
- Fixed the DNS settings page to allow domain name in the Domain Search field to begin with a number.
- Fixed the Local Manager Properties page to ask if you want to save changes if you navigate away without saving changes.
Known Issues in This Release
- Resizing the CLI applet window (i.e. SSH session to a Local Manager using the CLI button) while it is streaming/writing output to the screen may cause the applet screen to go blank or stop responding.