Release Notes

Table Of Contents
4. Installation, Upgrade, and Configuration Changes
37 of 51
device might change unexpectedly:
l MLT
l SMLT
l Port-specific settings to a port belonging to an MLT or SMLT
To prevent this merge, change rows in the Enforce Preview window where MLT or
SMLT are in use from Current to Desired.
To correct the issue after enforcement, modify the service on the device via the CLI.
4.5.4 CLIP Addresses
Using the CLIP Addresses table in the Configure Device window, you can enter
addresses in both IPv4 and IPv6 formats. However, Extreme Management Center
version 8.5 only supports applying a single address (either IPv4 or IPv6) to a Loopback
Interface.
4.5.5 Gateway Address Configuration Change
In versions of Extreme Management Center prior to 8.5, the Default Gateway IP Address
is configured as part of the VLAN. In 8.5, the Default Gateway IP Address is configured
as part of the VRF.
When enforcing VRFs to a device after upgrading to version 8.5, merge any Default
Gateway IP Addresses from the device into the configuration of Extreme Management
Center to prevent incorrect configuration of the device.
4.5.6 Upgrading VSP-8600
When upgrading from Extreme Management Center version 8.2 to version 8.3. manually
reload previously discovered VSP-8600 devices to gain access to Fabric Connect
features.
4.5.7 Removing Fabric Connect Configuration
Removing a device's Fabric Connect configuration by setting the Topology Definition to
<None> may fail if the device has Logical Interfaces assigned to ISIS.
4.5.8 Password Configuration
Fabric Manager fails to onboard in Extreme Management Center if the root password
includes an ampersand (&) character. Additionally, if the Administration > Inventory