DELL PowerEdge M I/O Aggregator Release Notes OS Version 9.14(1.12) User Guide

DELL PowerEdge M I/O Aggregator Release Notes OS Version 9.14(1.12)

This document contains information on open and resolved caveats and operational information specific to the Dell Networking OS on the Dell PowerEdge M I/O Aggregator.

• Current Release Version: 9.14(1.12)
• Release Date: 2022-05-20
• Previous Release Version: 9.14(1.10)

For more information on hardware and software features, commands, and capabilities, refer to the Dell Networking support website at: https://www.dell.com/support

Document Revision History

Table 1. Revision History

Prerequisites

The Dell Chassis Management Controller (CMC) version 4.11 or later is required in a Dell PowerEdge M1000e Enclosure to use an M I/O Aggregator module running Dell Networking OS version 9.3(0.0) or later. You can use the CMC out-of-band management interface to access and manage an M I/O Aggregator using the Dell Networking OS command-line interface. For more information, refer to the Dell Chassis Management Controller Firmware User’s Guide on the Dell Support website at http://support.dell.com/support/edocs/systems/pem/en/index.htm.

Supported Hardware

The following hardware is supported with this platform:

Hardware

M I/O Aggregator: base module
4-Port 10-Gigabit Ethernet SFP+ module
2-Port 40-Gigabit Ethernet QSFP+ module
4-Port 10GBASE-T module
4-port 2/4/8G FC Flex IO Module

New Dell Networking OS Version 9.14(1.12) Features

The following features have been added to M IOA with Dell Networking OS version 9.14(1.12): None.

Important Points to Remember

When an Aggregator is installed in an M1000e chassis:

• After you insert any FlexIO module into an empty slot, you must reload the Aggregator for the module to be operational; for example:

• If you remove an installed module and insert a different module type, an error message is displayed to remind you that the slot has been configured for a different type of FlexIO module; for example:

• You must reload the switch to make the FlexIO module operational.
• You can hot swap FlexIO modules of the same type without having to reboot the Aggregator.
• In Dell Networking OS version 9.4(0.0) and later releases, only ESC key can be used to break into the BLI/X-loader of the I/O Aggregator during boot/reload procedure. To use the feature, the user has to upgrade the boot selector as mentioned in the Upgrading the Dell Networking OS Image, Boot Flash and Boot Selector Images.

Restrictions and Known Issues with Other Devices

• While deploying the system in the normal-reload mode in BMP configuration, use the ip ssh server enable command at the beginning of the startup configuration if the write memory command is used at the end of the configuration.
• If you want to downgrade from Dell Networking OS version 9.14(1.12) to an earlier version, you must power cycle the I/O modules using CMC.
• An Aggregator supports only one 4-Port 10GBASE-T Module at a time.
• Connections between an Aggregator and the following devices are not supported:
  • Cisco fabric extenders (FEXes): Storage deployments are not supported; LAN deployments are supported.
• When an Aggregator interoperates with a Brocade B8000 switch, rebooting the Aggregator results in the B8000 switch generating more PFC frames, which may result in the failure to establish the iSCSI sessions.
• In connections with a server using a Q-LOGIC CNA for converged traffic, a FIP snooping session may flap when nonstandard LAN traffic is transmitted with SAN traffic.
• In connections with a server using an Intel X520 CNA, the server may fail to boot from the SAN network if a Brocade CNA is also installed in the server.
• If an Intel X520 CNA adapter is used as an FCoE initiator, follow these steps to establish FCoE sessions to send and receive traffic on an Aggregator:
  1. On a server connected to the Aggregator, uninstall the old Intel driver (version 13.0.0 or older).
  2. Re-install the Intel driver using version 13.5 A00 (or later) from the http://www.dell.com website.
  • Important: During the installation, do not select the ISCSI part of the driver; select only the FCoE check box.
  3. On each server-facing port, enter the following commands in interface configuration mode. The dcbx version cee command configures a port to use the CEE (Intel 1.01) version of DCBX. Configure server-facing ports with the shutdown and no shutdown commands, as needed. For example:
  4. Display information on FIP-snooped sessions and check the entries in ENode Interface fields to see if you have established the FCoE session on a server-facing port.
  • show fip-snooping sessions
  • EXEC Privilege
• To ensure interoperability, the recommended LLDP and LACP timeout values that should be configured in devices to which the Aggregator connects (such as ToR switch and servers) are:
  • LLDP timeout: 30 seconds
  • LACP long timeout
• When 68-byte frames are sent at line rate to a server, the server-facing LACP connection may flap. This behavior is due to the server’s inability to send LACP control packets when handling incoming line-rate traffic.

Changes to Default Behavior and CLI Syntax

Following default behavior and CLI syntax changes occurred during the Dell Networking OS release:

• To enhance security, the default RSA key size has been changed to 2048 bits from 1024 bits from 9.14.1.10 onwards.

Documentation Corrections

• None.

Deferred Issues

• Issues that appear in this section were reported in Dell Networking OS version 9.14(1.0) as open, but have since been deferred.
• Deferred issues 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.
• Work around: Work around describes a mechanism for circumventing, avoiding, or recovering from the issue. It might not be a permanent solution.
  • Issues listed in the “Fixed Issues” section should not be present, and the work-around is unnecessary, as the version of code for which this release note is documented has resolved the issue.

Deferred M I/O Aggregator 9.14(1.0) Software Issues

Issues that appear in this section were reported in Dell Networking OS version 9.14(1.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.

The following issues have been deferred in the Dell Networking OS version 9.14(1.0):

• None

Fixed Issues

Fixed 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.
• Work around: Work around describes a mechanism for circumventing, avoiding, or recovering from the issue. It might not be a permanent solution.
  • The work-around is unnecessary, as the version of code for which this release note is documented has resolved the issue.

Fixed S/W Issues for the M I/O Agg in Dell Networking OS Version 9.14(1.12)

_ NOTE: _Dell Networking OS 9.14(1.12) includes fixes for issues addressed in previous 9.14 releases. Refer to the respective release notes documentation for the list of issues fixed in earlier 9.14 releases.

The following issues are fixed in Dell Networking OS version 9.14(1.12):

PR#169841

• Severity: Sev 2
• Synopsis: In certain scenarios, an MSDP learnt PIM TIB entry stays in registering state indefinitely.
• Release Notes: In certain scenarios, an MSDP learnt PIM TIB entry stays in registering state indefinitely.
• Workaround: Set the affected node as a non-designated router in the RPF neighbor interface.

PR#170240

• Severity: Sev 2
• Synopsis: AAA accounting request displays an incorrect calling station id.
• Release Notes: AAA accounting request displays an incorrect calling station-id.
• Workaround: None

PR#170255

• Severity: Sev 2
• Synopsis: The switch encounters an exception when saving the configuration on VLT pair switches simultaneously.
• Release Notes: The switch encounters an exception when saving the configuration on VLT pair switches simultaneously.
• Workaround: None

PR#170301

• Severity: Sev 3
• Synopsis: The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli(CVE-2022-0778)
• Release Notes: The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli(CVE-2022-0778)
• Workaround: None

Known Issues

Known 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.
• Work around: Work around describes a mechanism for circumventing, avoiding, or recovering from the issue. It might not be a permanent solution.
  • Issues listed in the “Fixed Issues” section should not be present, and the work-around is unnecessary, as the version of code for which this release note is documented has resolved the issue.

Known S/W Issues for the M I/O Switch in Dell Networking OS Version 9.14(1.12)

The following issues are open in Dell Networking OS version 9.14(1.12):

• None

Dell PowerEdge M I/O Aggregator Procedures Overview

To upgrade to the latest Dell Networking OS on a Dell PowerEdge M I/O Aggregator, complete these steps:

• Upgrading the Dell Networking OS Image, Boot Flash and Boot Selector Images
• Upgrading the CPLD

Upgrading the Dell Networking OS Image, Boot Flash and Boot Selector Images

• This section describes the procedure to upgrade Boot Flash and Boot Sector Images in Dell PowerEdge M I/O Aggregator.
• The Aggregator is pre-loaded with default Dell Networking OS. Each Aggregator must be upgraded individually to a new Dell Networking OS release.

NOTE: Upgrading to Dell Networking OS version 9.14(1.12) from a version prior to Dell Networking OS version 8.3.17.3 via TFTP is a two step process.

1. The Dell PowerEdge M I/O Aggregator with Dell Networking OS version prior to 8.3.17.3 must be upgraded to Dell Networking OS 8.3.17.3 to support copy of files greater than 32MB via TFTP.
2. The switch can then be upgraded to Dell Networking OS version 9.14(1.12).

NOTE

• The Dell PowerEdge M I/O Aggregator can be upgraded to Dell Networking OS version 9.14(1.12) via TFTP from versions 8.3.17.3 and later without any upgrades to intermediate releases
• The Dell PowerEdge M I/O Aggregator can be upgraded to Dell Networking OS version 9.14(1.12) via FTP and other locations from any previous Dell Networking OS version without any upgrades to intermediate releases.

To upgrade the Dell Networking OS, Boot Flash and Boot Selector Images, follow the below steps:

1. Dell Technologies recommends that you back up your startup configuration and any important files and directories to an external media prior to upgrading the system.
2. Upgrade the Dell Networking OS in flash partition A: or B:
   • upgrade system [flash: | ftp: | scp: | tftp: | usbflash:] [A:| B:]
   • EXEC Privilege
3. In case of a stack setup, upgrade the Dell Networking OS for the stacked units.
   • upgrade system stack-unit [0-5 | all] [A: | B:]
   • EXEC Privilege
   • If A: is specified in the command, the Dell Networking OS version present in Management unit’s A: partition will be pushed to the stack units. If B: is specified in the command, the Management unit’s B: will be pushed to the stack units. Upgrade of stack units can be done on individual units by specifying the unit id [0-5] or on all units by using all in the command.
4. Verify the Dell Networking OS has been upgraded correctly in the upgraded flash partition
   • show boot system stack-unit [0-5 | all]
   • EXEC PRIVILEGE
   • The Dell Networking OS versions present in A: and B: can be viewed for individual units by specifying the stack unit id [0-5] in the command or for all the stack units by specifying all in the command.
5. Upgrade the M I/O Aggregator Boot Flash and Boot Selector image.
   • upgrade boot [all | bootflash-image | bootselector-image] stack-unit [0-5 | all] [booted | flash: | ftp: | scp: | tftp: | usbflash:] [A: | B:]
   • EXEC Privilege
   • Dell Networking OS version 9.14(1.12) requires M I/O Aggregator Boot Flash image version 4.0.1.3 and Boot Selector image version 4.0.0.2. If any higher versions of Boot Flash or Boot Selector versions are present in the unit, do not upgrade the Boot Flash and Boot Selector images respectively. The Boot Flash and Boot Selector images can be upgraded at the same time by specifying all in the command. These can be upgraded separately by selecting bootflash-image or bootselector-image respectively. The Boot Flash and Boot Selector images can be upgraded for individual stack units by specifying the particular stack unit ID from the range [0-5] in the command. These can be upgraded to all the stack units together by selecting all option instead of the stack unit ID. The Boot Flash and Boot Selector images can be saved in two partitions A: and B: and the user can select the partition to be upgraded by specifying A: or B: in the command.
6. Change the Primary Boot Parameter of the M I/O Aggregator to the upgraded partition A: or B:
   • boot system stack-unit [0-5 | all] primary [system A: | system B: | tftp://]
   • CONFIGURATION
7. Save the configuration so that the configuration will be retained after a reload using write memory command.
   • write [memory]
   • EXEC Privilege
8. Reload the unit.
   • reload
   • EXEC Privilege
9. Verify the M I/O Aggregator has been upgraded to the Dell Networking OS version 9.14(1.12).
   • show version
   • EXEC Privilege
10. Verify the M I/O Aggregator has been upgraded to the latest Boot Flash and Boot Selector versions.
    • show system stack-unit [0-5]
    • EXEC Privilege

Upgrading the CPLD

An Aggregator with Dell Networking OS version 9.14(1.12) requires CPLD image 6.

Verify that a CPLD upgrade is required

Use the following command to identify the CPLD version:

Use the following command to view CPLD version that is associated with the Dell Networking OS image:

Upgrading the CPLD Image

NOTE: The upgrade fpga-image stack-unit 0 booted command is hidden when using the ? feature in the CLI. However, it is a supported command and will be accepted when entered as documented.

To upgrade the CPLD image on an Aggregator

1. Upgrade the CPLD image.
   • upgrade fpga-image stack-unit [0-5] booted
   • EXEC Privilege
2. Power cycle the switch (IO module) using the CMC interface or remove and re-insert the switch (OIR) from the chassis so that the CPLD upgrade takes effect.
   • NOTE: The powercycle stack-unit 0 command does not load the latest CPLD version.
3. Check whether the CPLD has been upgraded to the latest version.
   • show revision
   • EXEC PRIVILEGE

VLT Upgrade Procedure

To upgrade the Dell Networking OS in a VLT setup from version 9.2(0.0) to 9.14(0.1) or later, upgrade the Dell Networking OS to version 9.3(0.0) first. If you are running the Dell Networking OS version 9.3(0.0) or later, you can upgrade the Dell Networking OS to the latest version. To upgrade the Dell Networking OS, on systems running VLT, perform the following steps:

1. Upgrade the system-flash partition A or B with the new image on both VLT peers.On both the VLT peers, set Primary boot parameter to boot the system from upgraded system flash partition [A or B]. You can enter one of the following options: flash — Copies from flash file system (flash://filepath).ftp — Copies from remote file system (ftp://userid:password@hostip//filepath).scp — Copies from remote file system (scp://userid:password@hostip//filepath).tftp — Copies from remote file system (tftp://hostip/filepath).
   • upgrade system [flash: | ftp: | scp: | tftp: | usbflash:] [A: | B:]
   • EXEC Privilege
2. Reload or power-cycle one of the VLT peers (For Example, Peer 2). reload or power cycle
3. Wait for Peer 2 to come up; VLT adjacency will be established. (Peer 2 – new image and Peer 1 – old image).
4. Wait for the Peer 2 to bring up all VLT LAG ports. Use the command show vlt detail to confirm all VLT ports in the local chassis are active.
   • show vlt detail
   • EXEC Privilege
5. Following upgrade, use the write memory command to save the running-config to memory.
   • write memory
   • EXEC Privilege
6. Ensure both the nodes are now forwarding traffic.
7. When all VLT ports are active on the Peer 2, repeat steps 2 through 5 for the Peer 1.

Support Resources

The following support resources are available for the M I/O system.

Documentation Resources

This document contains operational information specific to the M I/O system. For information about using the M I/O, refer to the following documents at http://www.dell.com/support:

• Installing the M I/O System
• Quick Start Guide
• Dell Networking Command Line Reference Guide for the M I/O System
• Dell Networking Configuration Guide for the M I/O System

For more information about hardware features and capabilities, refer to the Dell Networking website at https://www.dell.com/networking.
For more information about the open network installation environment (ONIE)-compatible third-party operating system, refer to http://onie.org.

Issues

• Issues are unexpected or incorrect behavior and are listed in order of Problem Report (PR) number within the appropriate sections.

Finding Documentation

This document contains operational information specific to the M I/O system.

• For information about using the M I/O, refer to the documents at http://www.dell.com/support.
• For more information about hardware features and capabilities, refer to the Dell Networking website at https://www.dellemc.com/networking.
• For more information about the open network installation environment (ONIE)-compatible third-party operating system, refer to http://onie.org.

Contacting Dell

NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog.

Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues: Go to www.dell.com/support.

Notes, cautions, and warnings

• NOTE: A NOTE indicates important information that helps you make better use of your product.
• CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
• WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

References

• Computers, Monitors & Technology Solutions | Dell USA
• Support | Dell US
• Support | Dell US
• Dell Networking Solutions | Dell USA
• Dell Networking Solutions | Dell USA

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>