Release Notes
Table Of Contents
- Dell EMC System S4048–ON 9.14(2.10) Release Notes
- Document Revision History
- Supported Hardware
- Supported Software
- New Dell EMC Networking OS Version 9.14(2.10) Features
- Restrictions
- Changes to Default Behavior and CLI Syntax
- Documentation Corrections
- Deferred Issues
- Fixed Issues
- Known Issues
- Upgrading the sub-components
- Upgrading ONIE on the S4048-ON
- Upgrading the S4048-ON Dell EMC Networking OS Image using the Dell EMC Networking OS CLI
- Installing Dell EMC Networking OS on the S4048-ON using ONIE
- Uninstalling Dell EMC Networking OS from the S4048-ON
- Support Resources
● If you use the interface range command to select multiple interfaces that are added to the management VRF, the
ipv6 nd command displays the following options but they do not take effect if you use them:
○ dns-server
○ hop-limit
○ managed-config-flag
○ max-ra-interval
○ mtu
○ other-config-flag
○ prefix
○ ra-guard
○ ra-lifetime
○ reachable-time
○ retrans-timer
○ suppress-ra
● When FRRP is enabled in a VLT domain, no flavor of Spanning tree should concurrently be enabled on the nodes of that
specific VLT domain. In essence FRRP and xSTP should not co-exist in a VLT environment.
● Do not configure the vxlan-instance command on the port, which is configured with the portmode hybrid
command. Do not configure the vxlan-instance enabled port as a member of VLAN, which does not have VXLAN-VNI
configuration.
Changes to Default Behavior and CLI Syntax
The following behavior and CLI changes are applicable to the S4048–ON switch with Dell EMC Networking OS version
9.14(2.10):
None.
Documentation Corrections
This section describes the errors identified in the current release of the Dell EMC Networking OS.
None.
Deferred Issues
Issues that appear in this section were reported in Dell EMC Networking OS version 9.14(2.0) as open, but have since been
deferred. Deferred caveats are those that are found to be invalid, not reproducible, or not scheduled for resolution.
Deferred issues are reported using the following definitions.
Category
Description
PR# Problem Report number that identifies the issue.
Severity
S1 — Crash: A software crash occurs in the kernel or a running process that requires a restart of AFM,
the router, switch, or process.
S2 — Critical: An issue that renders the system or a major feature unusable, which can have a pervasive
impact on the system or network, and for which there is no work-around acceptable to the customer.
S3 — Major: An issue that affects the functionality of a major feature or negatively effects the network
for which there exists a work-around that is acceptable to the customer.
S4 — Minor: A cosmetic issue or an issue in a minor feature with little or no network impact for which
there might be a work-around.
Synopsis Synopsis is the title or short description of the issue.
Release Notes Release Notes description contains more detailed information about the issue.
4