Release Notes

3. Known Issues and Vulnerabilities Addressed
39 of 69
Applying a port template was a one-time import of settings to
that port. Ports assigned a port template now always reflect that
port template's settings. To override port settings, you must
create a new template and assign it to the port or set the port's
template value to Use Local Settings, which enables you to apply
any setting to that port.
------
Users were able to create an L3VSN service using either the
MgmtRouter or GlobalRouter, which cannot support these
services.
------
After successful enforcement to an ExtremeXOS device, the
enforcement preview panel was showing that there were VLAN
differences.
------
Users were able to create Switched UNI or Transparent UNI
services in a Service Application that shares the same Service ID
as an L3VSN service.
------
When there was no Authorization Group Device Mapping for a
device, the Contact Device by Group's Profile action was using
NA. Now, the Device Mapping’s “<*>” designation is respected,
and the default Profile for the device is used.
------
Editing an inherited configuration from a Service Application or
Site was occasionally changing the Source ID of that edited item.
l Items that exactly match the inherited configuration now
have their Source ID revert to the original location of that
item.
l Items that do not exactly match the inherited configuration
now have their Source ID marked as Local.
------
Users were unable to create L2 or L3 Services that did not have a
name associated with them.
------
While editing a device, the CLIP Addresses table were not
displaying all IPv4 and IPv6 addresses associated with a VSP
device (CLIP, VLAN, BROUTER, MGMT). Now the user will be able
to create, edit and delete CLIP addresses in this table, while the
other address types (MGMT, VLAN, BROUTER) will not be editable
by the user.
------