32
 Release Notes for the MXL 10/40GbE Switch IO Module Dell Networking OS Version 9.7(0.0) March 2015

MXL Release Notes - Force10 · This document contains information on open and resolved caveats and operational ... All Release Notes are available on the ... (secure management mode)

Embed Size (px)

Citation preview

 Release Notes for theMXL 10/40GbE Switch

IO Module

Dell Networking OS Version 9.7(0.0) March 2015

2 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om Table of Contents

How To Use This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Supported Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

New Dell Networking OS Version 9.7(0.0) Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Accessing Boot Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Changes to Default Behavior and CLI Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

MXL Upgrade Procedures: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

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

Upgrading the CPLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Verify that a CPLD Upgrade is Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Upgrade the CPLD Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

VLT Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Documentation Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Load balancing through port channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Hash algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Caveats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Caveat Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Resolved H/W Caveats for the MXL Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Deferred S/W Caveats for the MXL Switch in Dell Networking OS Version 9.7(0.0) . . . .24

Resolved S/W Caveats for the MXL Switch in Dell Networking OS 9.7(0.0) . . . . . . . . . .25

Open S/W Caveats for the MXL Switch in Dell Networking OS Version 9.7(0.0) . . . . . .26

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Accessing Dell Networking Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

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

| 3

How To Use This Document

This document contains information on open and resolved caveats and operational information specific to the Dell Networking Operating System (OS) on the MXL 10/40GbE Switch IO module.

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

Prerequisites

The Dell Chassis Management Controller (CMC) version 4.11 or later is required in a Dell PowerEdge M1000e Enclosure to use an MXL 10/40GbE Switch IO module running Dell Networking OS version 8.3.16.3 or later.

You can use the CMC out-of-band management interface to access and manage an MXL Switch 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

Note: Customers can subscribe to caveat update reports or use the BugTrack search tool to read current information about open and closed software caveats. To subscribe or use BugTrack, visit Dell Networking support at: https://www.force10networks.com/CSPortal20/BugTrack/SearchIssues.aspx.

All Release Notes are available on the Software Center tab of Dell Networking support. The link to the relevant Release Notes for each software version is next to the link for that version:

https://www.force10networks.com/CSPortal20/Software/Downloads.aspx

Hardware

MXL 10/40GbE Switch IO Module: 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

4 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om New Dell Networking OS Version 9.7(0.0) Features

The following features have been added to the MXL switch with Dell Networking OS Version 9.7(0.0).

Accessing Boot Line Interface

Until the Dell Networking OS 9.3(0.0), any key can be used to break into Boot Line Interface (BLI) during the boot process to change any environment and boot variables. Starting from Dell Networking OS 9.4(0.0) and later releases only the ESC key can be used to break into BLI during not process. The Boot Flash and Boot Selector images needs to be upgraded to the latest versions in order to enable this feature. For more information on Upgrading Boot Code, refer to the Upgrading the Dell Networking OS Image, Boot Flash and Boot Selector Images section.

Restrictions

• An MXL 10/40GbE Switch supports only one 4-Port 10GBASE-T Module at a time.

• When configuring CAM ACL using the cam-acl l2acl 2 ipv4acl 2 ipv6acl 0 ipv4qos 1 l2qos 2 l2pt 0 ipmacacl 0 vman-qos 0 ecfmacl 2 fcoeacl 4 iscsioptacl 0 command and reloading, the system fails due to a limitation in the BCM SDK 6.3.4.

Feature Feature Description

DHCPv6 Snooping Secondary subnet feature is an extended feature of DHCP relay agent. This feature will beuseful when client fails to get IP address when the subnet pool selection by server is based onprimary address of the client connected interface of relay agent. In this case, this feature allowsthe DHCP relay agent to switch the gateway address (giaddr field of a DHCP packet) tosecondary addresses.

VLT-PVST This enhancement PVST+ is a variation of spanning tree allows the user to configure a separatespanning tree instance for each VLAN. Each instance of PVST+ on a VLAN, has a single rootbridge.

There will be only one active path for each spanning tree instance; this enhancement can beconfigured to have different active paths for different VLANs. The VLT Domain is enhanced tosupports PVST+.

MS-NLB Scalability Enhancement This enhancement provides user to increase the scalability limit.

PBR-OTM This enhancement supports the Object Tracking in PBR feature.

MXL Bypass Mode The enhancement is made to set CMC bypass mode (secure management mode) on MXL. Onceconfiguration is saved and system is rebooted, the MXL comes up in secure mode.

FCF F Port This feature provides support for direct connectivity to FC equipment’s through Fibre channelports provided by FC Flex IO optional module rather than through a FC switch for cost sensitivelow scale deployments.

Weighted ECMP The Weighted ECMP feature programs the hardware for ECMP flows using the weightsexchanged by BGP to proportionally distribute the traffic among paths based on the trafficcarrying capability that they have advertised.

Q-in-Q implementation over VLT VLT support for Q-in-Q is intended to provide resiliency to the existing Q-in-Q feature. Thisimplementation does not change any of the existing behavior of Q-in-Q in a standalone switch.To gain the benefits of VLT for the Q-in-Q feature, ensure that the VLAN stack configurationand the port modes of the member ports are symmetric across the VLT peers.

| 5

• 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 MXL 10/40GbE Switch:

• If the MXL switch is in boot-line interface (BLI) mode:

— You cannot switch to the CMC console and manage the switch using CMC.

— You cannot disconnect and reconnect to CMC from the CMC console.

Connect to the CMC console after you exit the BLI interface or after the BLI phase of the bootup finishes.

• After you upgrade the CPLD version on an MXL switch using the BLI, the new CPLD version is not displayed in show revision output if you power cycle the switch using the power-cycle stack-unit command. Instead, power cycle the MXL switch using the CMC interface.

• The MXL switch crashes and reboots when an FRU read operation fails.

Changes to Default Behavior and CLI Syntax

After you upgrade a switch to version 9.7(0.0) or later from an earlier Dell Networking OS version, the interface index value of all interfaces is offset by 16515072. For example:

Dell#show interfaces | grep index iInterface index is 33620994Interface index is 33883138Interface index is 34145282Interface index is 34407426

Dell#show interfaces | grep index iInterface index is 17105922Interface index is 17368066Interface index is 17630210Interface index is 17892354

Step Task Command Mode

1. 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:

Dell# interface tenGigabitEthernet 0/1 Dell(conf-if-te-0/1)# portmode hybridDell(conf-if-te-0/1)# switchportDell(conf-if-te-0/1)# protocol lldp Dell(conf-lldp)# dcbx port-role auto-downstreamDell(conf-lldp)# dcbx version ceeDell(conf-lldp)# exitDell(conf-if-te-0/1)# spanning-tree pvst edge-portDell(conf-if-te-0/1)# no shutdownDell(conf-if-te-0/1)# exitDell#

2. Display information on FIP-snooped sessions and check the entries in ENode Interface fields to see if you have established the FCoE session on each server-facing port.

show fip-snooping sessions EXEC Privilege

6 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om MXL Upgrade Procedures: Overview

To upgrade the Dell Networking OS to version 9.7(0.0) on an MXL 10/40GbE Switch, complete these steps:

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

• Upgrading the CPLD

• VLT Upgrade Procedure

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

Note: To upgrade the Dell Networking OS to version 9.7(0.0), you must have the Dell Networking OS version 9.2(0.0) or above.

The MXL 10/40GbE Switch is pre-loaded with default Dell Networking OS. Each MXL 10/40GbE Switch IO module must be upgraded individually to a new Dell Networking OS release.

Note: If you are using Bare Metal Provisioning (BMP), refer to the Bare Metal Provisioning chapter in the Dell Networking OS Configuration Guide.

Manual Upgrade Procedure

To upgrade your MXL 10/40GbE switch IO module, follow the below steps:

Step Task Command Mode

1. Dell Networking recommends that you back up your startup configuration and any important files or directories to an external media prior to upgrading the system.

2. Upgrade the Dell Networking OS version A: or B:

upgrade system [flash: | ftp: | scp: | tftp: | usbflash:] [A: | B:]

EXEC Privilege

Dell# upgrade system ftp: A:Address or name of remote host []: 10.16.127.35Source file name []: FTOS-XL-9.7.0.0.binUser name to login remote host: ftpuserPassword to login remote host:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Erasing IOM Primary Image, please wait.!.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................44875621 bytes successfully copiedSystem image upgrade completed successfully.Dell#

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

| 7

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.

Dell# upgrade system stack-unit all A:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Image upgrade to allDell#

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.

Dell#show boot system stack-unit allCurrent system image information in the system:==========================================Type Boot Type A B--------------------------------------------------------------------Stack-unit 0 FLASH BOOT 9.7(0.0) 9.6(0.0)[boot]Stack-unit 1 FLASH BOOT 9.7(0.0) 9.6(0.0)[boot]Stack-unit 2 is not present.Stack-unit 3 is not present.Stack-unit 4 is not present.Stack-unit 5 is not present.Dell#

5. Upgrade the MXL 10/40 GbE switch Boot Flash and Boot Selector images.

upgrade boot [all | bootflash-image | bootselector-image] stack-unit [0-5 | all]

[booted | flash: | ftp: | scp: | tftp: | usbflash:] [A: | B:]

EXEC Privilege

Step Task Command Mode

8 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om

Dell Networking OS version 9.7(0.0) requires MXL 10/40 GbE 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.

Dell#upgrade boot all stack-unit all ftp: A:Address or name of remote host []: 10.16.127.35Destination file name []: FTOS-XL-9.7.0.0.binUser name to login remote host: ftpuserPassword to login remote host:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Current Boot information in the system:============================================Card BootFlash Current Version New Version-------------------------------------------------------------------------------------Unit0 Boot Flash 4.0.1.1 4.0.1.3Unit1 Boot Flash 4.0.1.1 4.0.1.3************************************************************************** Warning - Upgrading boot flash is inherently risky and should only** be attempted when necessary. A failure at this upgrade may cause** a board RMA. Proceed with caution !**************************************************************************Proceed Boot Flash image for all units [yes/no]: yes !!!!!!!!!!!!!!!!Erasing IOM Primary Bootflash Image, please wait.!.!.!.!.!.!.!..!.......................Bootflash image upgrade for all completed successfully.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Current Boot information in the system:============================================

Card BootSelector Current Version New Version------------------------------------------------------------------------------------Unit0 Boot Selector 4.0.0.1 4.0.0.2Unit1 Boot Selector 4.0.0.1 4.0.0.2

************************************************************************** Warning - Upgrading boot selectors is inherently risky and should ** only be attempted when necessary. A failure at this upgrade may** cause a board RMA. Proceed with caution ! **************************************************************************

Proceed Boot Selector image for all units [yes/no]: yes!!!Erasing IOM Boot Selector Image, please wait.!!.!..!.!..!.!.......Bootselector image upgrade for all completed successfully.Dell#

6. Change the Primary Boot Parameter of the MXL 10/40 GbE switch to the upgraded partition A: or B:

boot system stack-unit [0-5 | all] primary [system A: | system B: | tftp://<URL>]

CONFIGURATION

7. Save the configuration so that the configuration will be retained after a reload using write memory command.

write [memory] EXEC Privilege

Step Task Command Mode

| 9

In case of a stack setup, the configuration will be saved in the Management as well as the Standby units.Dell#write memory!Synchronizing data to peer Stack-unit!!!!!!!!Dell#

8. Reload the unit. reload EXEC Privilege

Dell#reload

Proceed with reload [confirm yes/no]: yesMar 29 21:32:27: %STKUNIT0-M:CP %CHMGR-5-RELOAD: User request to reload the chassissyncing disks... done

9. Verify the MXL 10/40 GbE switch has been upgraded to the Dell Networking OS version 9.7(0.0).

show version EXEC Privilege

Dell#show versionDell Real Time Operating System SoftwareDell Operating System Version: 2.0Dell Application Software Version: 9.7(0.0)Copyright (c) 1999-2014 by Dell Inc. All Rights Reserved.Build Time: Thu Mar 27 13:19:50 PDT 2014Build Path: /work.local/build/toolSpaces/tools05/E9-4-0/SW/SRCDell Networking OS uptime is 1 minute(s)

System image file is "system://A"

System Type: MXL-10/40GbEControl Processor: MIPS RMI XLP with 2147483648 bytes of memory, core(s) 1.

256M bytes of boot flash memory.

2 34-port GE/TE/FG (XL)96 Ten GigabitEthernet/IEEE 802.3 interface(s)4 Forty GigabitEthernet/IEEE 802.3 interface(s)Dell#

10. Verify the MXL 10/40 GbE switch has been upgraded to the latest Boot Flash and Boot Selector versions.

show system stack-unit [0-5] EXEC Privilege

Dell#show system stack-unit 0

-- Unit 0 --Unit Type: Management UnitStatus: onlineNext Boot: onlineRequired Type: MXL-10/40GbE - 34-port GE/TE/FG (XL)Current Type: MXL-10/40GbE - 34-port GE/TE/FG (XL)Master priority: 0Hardware Rev: 1Num Ports: 56Up Time: 2 min, 56 secDell Networking OS Version: 9.7(0.0)Jumbo Capable: yesPOE Capable: noFIPS Mode: disabledBoot Flash: A: 4.0.1.3 [booted] B: 4.0.1.3Boot Selector: 4.0.0.2

Step Task Command Mode

10 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om SMARTSCRIPTS

To un-install and install new SMARTSCRIPTS packages after upgrading to Dell Networking OS version 9.7(0.0), refer to the Open Automation Guide - 9.7(0.0).

Upgrading the CPLD

An MXL 10/40GbE Switch IO module with Dell Networking OS version 9.7(0.0) requires CPLD image 6.

Verify that a CPLD Upgrade is Required

Figure 1-1. Verifying the CPLD version

Dell# show revision

-- Stack unit 0 --IOM SYSTEM CPLD : 6

-- Stack unit 1 --IOM SYSTEM CPLD : 6

-- Stack unit 2 --IOM SYSTEM CPLD : 6

| 11

Figure 1-2. Display the CPLD Version Included with the Dell Networking OS Image

Upgrade the CPLD Image

To upgrade the CPLD image on an MXL 10/40GbE Switch IO module:

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.

Step Task Command Command Mode

1. Shut down all of the interfaces on the system. shutdown INTERFACE

2. Upgrade the CPLD image. upgrade fpga-image stack-unit {0 - 5} booted

EXEC Privilege

Dell# show os-version

RELEASE IMAGE INFORMATION :---------------------------------------------------------------------

Platform Version Size ReleaseTimeIOM-Series: XL 9.7(0.0) 44874813 Sep 29 2014 12:24:44

TARGET IMAGE INFORMATION :---------------------------------------------------------------------

Type Version Target checksum runtime 9.7(0.0) Control Processor passed

BOOT IMAGE INFORMATION :---------------------------------------------------------------------

Type Version Target checksum boot flash 4.0.1.3 Control Processor passed

BOOTSEL IMAGE INFORMATION :---------------------------------------------------------------------

Type Version Target checksumboot selector 4.0.0.2 Control Processor passed

CPLD IMAGE INFORMATION :---------------------------------------------------------------------

Card CPLD Name VersionStack-unit 0 IOM SYSTEM CPLD 6Dell#

12 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om

3. 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.

4. Check whether the CPLD has been upgraded to the latest version.

show revision EXEC PRIVILEGE

Step Task Command Command Mode

Dell#upgrade fpga-image stack-unit 0 booted

Current FPGA information in the system:=======================================

Card FPGA Name Current Version New Version------------------------------------------------------------------------ Unit0 IOM SYSTEM CPLD 6 6

*********************************************************************** * Warning - Upgrading FPGA is inherently risky and should * * only be attempted when necessary. A failure at this upgrade may * * cause a board RMA. Proceed with caution ! * ***********************************************************************

Upgrade fpga image for stack-unit 0 [yes/no]: yes

FPGA upgrade in progress!!! Please do NOT power off the unit!!!!!!!!!!!!!!!!!

Upgrade result :================Unit 0 FPGA upgrade successful. power cycle the stack-unit to complete the upgrade.

Dell#

Dell# show revision -- Stack unit 0 --IOM SYSTEM CPLD : 6-- Stack unit 1 --IOM SYSTEM CPLD : 6-- Stack unit 2 --IOM SYSTEM CPLD : 6

| 13

VLT Upgrade Procedure

This procedure should be followed to upgrade VLT from release 9.2 to 9.7(0.0) or later:

Documentation Errata

This section describes documentation errors identified in both current as well as previous Dell Networking OS releases.

• When you reconfigure CAM allocation, you can use the nlbclusteracl number command to change the number of NLB ARP entries. The range is from 0 to 2. The default value is 0. At the default value of 0, eight NLB ARP entries are available for use. This platform supports upto 256 CAM entries. Select 1 to configure 128 entries. Select 2 to configure 256 entries. Even though you can perform CAM carving to allocate the maximum number of NLB entries, Dell Networking recommends that you use a maximum of 64 NLB ARP entries.

• The enable secure command is included in the Control and Monitoring chapter of the MXL 10/40GbE Switch IO Module Command Reference Guide. This command is not supported in the Release 9.7(0.0).

• The following note applies to the Post Configuration Script - BMP Mode section of the Configuring BMP chapter of the Open Automation Guide:

Step Task Command Command Mode

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

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.

Note: VLT Nodes can be upgraded from, 9.2 tο 9.7, 9.3 tο 9.7, 9.4 tο 9.7, 9.5 tο 9.7.

7. When all VLT ports are active on the Peer 2, repeat steps 2 through 5 for the Peer 1.

14 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om Because the rstimer utility supports only the minute-level precision, the rstimer utility cannot be used

for the first time after the ninth minute.• In the Access Control Lists (ACLs) chapter of all of the platforms' Configuration Guides, some of the show command

examples that display the sample output of standard IP ACL configurations in the erroneously contain permit and deny rules for TCP and UDP packets. TCP and UDP packets can be permitted or denied only using extended IP ACLs. The TCP and UDP-related lines contained in the sample output of standard IP ACLs are not relevant for such ACLs.

• The Interfaces chapters of Command Reference and Configuration Guides of the MXL 10/40GbE Switch IO Module of Release 9.2(0.0) fail to mention the load-balance command that is supported on the MXL Switch. This command is supported on the MXL Switch, starting with the first Dell Networking OS release that was implemented on this platform.

load-balance

By default, Dell Networking OS uses an IP 4-tuple (IP SA, IP DA, Source Port, and Destination Port) to distribute IP traffic over members of a Port Channel as well as equal-cost paths. To designate another method to balance traffic over Port Channel members, use the load-balance command.

Table 1 load-balance Command

Syntax

load-balance {ip-selection [dest-ip | source-ip]} | {mac [dest-mac | source-dest-mac | source-mac]} | {tcp-udp | ingress-port [enable]}

To return to the default setting (IP 4-tuple), use the no load-balance {ip-selection [dest-ip | source-ip]} | {mac [dest-mac | source-dest-mac | source-mac]} | {tcp-udp | ingress-port [enable]} command.

Parameters

• ip-selection {dest-ip | source-ip}—Enter the keywords to distribute IP traffic based on the following criteria:

Note: The hashing mechanism returns a 3-bit index indicating which port the packet should be forwarded.

• dest-ip — Uses destination IP address and destination port fields to hash.

• source-ip — Uses source IP address and source port fields to hash. • mac {dest-mac | source-dest-mac | source-mac}—Enter the keywords to distribute MAC traffic

based on the following criteria:

• dest-mac — Uses the destination MAC address, VLAN, Ethertype, source module ID and source port ID fields to hash.

• source-dest-mac — Uses the destination and source MAC address, VLAN, Ethertype, source module ID and source port ID fields to hash.

• source-mac — Uses the source MAC address, VLAN, Ethertype, source module ID and source port ID fields to hash.

• tcp-udp enable—Enter the keywords to distribute traffic based on the following:

• enable — Takes the TCP/UDP source and destination ports into consideration when doing hash computations. This option is enabled by default.

• ingress-port enable—Enter the keywords to distribute traffic based on the following:

• enable — Takes the source port into consideration when doing hash computations. This option is disabled by default.

Defaults IP 4-tuple (IP SA, IP DA, Source Port, Destination Port)

Command Modes CONFIGURATION

Command History Version 8.3.16.1—Introduced on the MXL 10/40GbE Switch IO Module.

| 15

Usage Information

By default, Dell Networking OS distributes incoming traffic based on a hash algorithm using the following criteria:

• IP source address

• IP destination address

• TCP/UDP source port

• TCP/UDP destination port

Table 1 load-balance Command

16 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om load-balance hg

Choose the traffic flow parameters the hash calculation uses while distributing the traffic across internal higig links.

Table 2 load-balance hg Command

Syntax

[no] load-balance hg { ip-selection | ipv6-selection [source-ip | source-ipv6 | source-port-id | source-module-id | dest-ip | dest-ipv6 | dest-port-id | dest-module-id | protocol | vlan | L4-source-port | L4-dest-port ] | mac [source-mac | source-port-id | source-module-id | dest-mac | dest-port-id | dest-module-id | vlan | ethertype | source-dest-mac ] | tunnel [ipv4-over-ipv4 | ipv4-over-gre-ipv4 | mac-in-mac]}

Parameters

• ip-selection | ipv6-selection [source-ip | source-ipv6 | source-port-id | source-module-id | dest-ip | dest-ipv6 | dest-port-id | dest-module-id | protocol | vlan | L4-source-port | L4-dest-port ]—To use IPv4 key fields in hash computation, enter the keyword ip-selection then one of the parameters. To use IPv6 key fields in hash computation, enter the keyword ipv6-selection then one of the parameters.

• source-ip — Use IPv4 src-ip field in hash calculation.

• source-ipv6 — Use IPv6 src-ip field in hash calculation

• source-port-id — Use src-port-id field in hash calculation.

• source-module-id — Use src-module-id field in hash calculation.

• dest-ip — Use IPv4 dest-ip field in hash calculation.

• dest-ipv6 — Use IPv6 dest-ip field in hash calculation

• dest-port-id — Use dest-port-id field in hash calculation.

• dest-module-id — Use dest-module-id field in hash calculation.

• protocol — Use IPv4 protocol field in hash calculation.

• vlan — Use vlan field in hash calculation.

• L4-source-port — Use IPv4 L4-source-port field in hash calculation.

• L4-dest-port — Use IPv4 L4-dest-port field in hash calculation.• mac [source-mac | source-port-id | source-module-id | dest-mac | dest-port-id |

dest-module-id | vlan | ethertype | source-dest-mac ]—To use MAC key fields in hash computation, enter the keyword mac then one of the parameters:

• source-mac — Use source-mac field in hash calculation.

• source-port-id — Use src-port-id field in hash calculation.

• source-module-id — Use src-module-id field in hash calculation.

• dest-mac — Use dest-mac field in hash calculation.

• dest-port-id — Use dest-port-id field in hash calculation.

• dest-module-id — Use dest-module-id field in hash calculation.

• vlan — Use vlan field in hash calculation .

• ethertype — Use Ethertype field in hash calculation.

• source-dest-mac — Use SMAC and DMAC fields in hash calculation.• tunnel [ipv4-over-ipv4 | ipv4-over-gre-ipv4 | mac-in-mac]—To use tunnel key fields in hash

computation, enter the keyword tunnel then one of the parameters:

• ipv4-over-ipv4 — Use ipv4-over-ipv4 field in hash calculation.

• ipv4-over-gre-ipv4 — Use ipv4-over-gre-ipv4 field in hash calculation.

• mac-in-mac — Use mac-in-mac field in hash calculation.

Defaults IP selection 5-tuples (source-ip dest-ip vlan protocol L4-source-port L4-dest-port).

Command Modes CONFIGURATION

| 17

Load balancing through port channels

Dell Networking OS uses hash algorithms for distributing traffic evenly over channel members in a port channel (LAG). The hash algorithm distributes traffic among ECMP paths and LAG members. The distribution is based on a flow, except for packet-based hashing. A flow is identified by the hash and is assigned to one link. In packet-based hashing, a single flow can be distributed on the LAG and uses one link.

Packet based hashing is used to load-balance traffic across a port-channel based on the IP Identifier field within the packet. Load balancing uses source and destination packet information to get the greatest advantage of resources by distributing traffic over multiple paths when transferring data to a destination.

Dell Networking OS allows you to modify the hashing algorithms used for flows and for fragments. The load-balance and hash-algorithm commands are available for modifying the distribution algorithms. Their syntax and implementation are somewhat different between the E-Series and the C-Series and S-Series.

Load balancing

For LAG hashing, the source IP, destination IP, source TCP/UDP port, and destination TCP/UDP port are used for hash computation by default. For packets without a Layer 3 header, Dell Networking OS automatically uses load-balance mac source-dest-mac.

IP hashing or MAC hashing should not be configured at the same time. If you configure an IP and MAC hashing scheme at the same time, the MAC hashing scheme takes precedence over the IP hashing scheme.

To change the IP traffic load balancing default, use the following command:

Command History Version 8.3.16.1—Introduced on the MXL 10/40GbE Switch IO Module.

Note: Hash-based load-balancing on MPLS does not work when packet-based hashing (load-balance ip-selection packet-based) is enabled.

Command Syntax Command Mode Purpose

[no] load-balance {ip-selection [dest-ip | source-ip]} | {mac [dest-mac | source-dest-mac | source-mac]} | {tcp-udp enable}

CONFIGURATION Replace the default IP 4-tuple method of balancing traffic over a port channel. You can select one, two, or all three of the following basic hash methodsip-selection [dest-ip | source-ip]—Distribute IP traffic based on IP destination or source address.

mac [dest-mac | source-dest-mac | source-mac]—Distribute IPV4 traffic based on the destination or source MAC address, or both, along with the VLAN, Ethertype, source module ID and source port ID.

tcp-udp enable—Distribute traffic based on TCP/UDP source and destination ports.

Table 2 load-balance hg Command

18 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om Hash algorithm

The load-balance command discussed above selects the hash criteria applied to port channels.

If even distribution is not obtained with the load-balance command, the hash-algorithm command can be used to select the hash scheme for LAG, ECMP and NH-ECMP. The 12 bit Lag Hash can be rotated or shifted till the desired hash is achieved.

The nh-ecmp option allows you to change the hash value for recursive ECMP routes independently of non-recursive ECMP routes. This option provides for better traffic distribution over available equal cost links that involve a recursive next hop lookup.

Figure 1-3 shows a sample configuration for the hash-algorithm command.

Figure 1-3. Command example: hash-algorithm

The hash-algorithm command is specific to ECMP groups and has different defaults from the E-Series. The default ECMP hash configuration is crc-lower. This takes the lower 32 bits of the hash key to compute the egress port. Other options for ECMP hash-algorithms are:

• crc-upper — uses the upper 32 bits of the hash key to compute the egress port

• dest-ip — uses destination IP address as part of the hash key

• lsb — always uses the least significant bit of the hash key to compute the egress port

Command Syntax Command Mode Purpose

hash-algorithm {algorithm-number} | {ecmp {checksum|crc|xor} [number]} lag {checksum|crc|xor][number]}nh-ecmp {[checksum|crc|xor] [number]}}| {linecard number ip-sa-mask value ip-da-mask value}

CONFIGURATION Change the default (0) to another algorithm and apply it to ECMP, LAG hashing, or a particular line card.

Note: To achieve the functionality of hash-align on the ExaScale platform, do not use CRC as an hash-algorithm method. For ExaScale systems, set the default hash-algorithm method to ensure CRC is not used for LAG. For example, hash-algorithm ecmp xor lag checksum nh-ecmp checksum

For details on the algorithm choices, see the command details in the IP Routing chapter of the Dell Networking OS Command Reference.

Dell(conf)##hash-algorithm ecmp xor 26 lag crc 26 nh-ecmp checksum 26Dell(conf)#

| 19

To change to another method, use the following command in the CONFIGURATION mode:

• The Virtual link trunking (VLT) chapter of the Command Reference Guide of the MXL platform enhances the show vlt brief command to display the VLT delay restore abort threshold value. The enhanced command is delay-restore abort-threshold <interval>.

Dell#show vlt brVLT Domain Brief------------------ Domain ID : 1 Role : Secondary Role Priority : 32768 ICL Link Status : Up HeartBeat Status : Up VLT Peer Status : Up Version : 6(3) Local System MAC address : 00:01:e8:8a:e9:91 Remote System MAC address : 00:01:e8:8a:e9:76 Remote system version : 6(3) Delay-Restore timer : 90 seconds

Delay-Restore Abort Threshold : 60 seconds Peer-Routing : Disabled Peer-Routing-Timeout timer : 0 seconds Multicast peer-routing timeout: 150 seconds Dell#

Command Syntax Command Mode Purpose

hash-algorithm ecmp {crc-upper} | {dest-ip} | {lsb}

CONFIGURATION Change to another algorithm.

20 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om delay-restore abort-threshold <interval>

Increase the Boot Up timer to some value (>60 seconds).

restore factory-defaults

Restores factory defaults.

Table 3 delay-restore abort-threshold <interval>

Syntax

delay-restore abort-threshold <interval>

To remove use:

no delay-restore abort-threshold

Defaults 60 seconds

Command Modes VLT DOMAIN

Command History Version 9.7(0.0)—Introduced on the S4820T, S4810, S6000, S5000, Z9000, Z9500, IOA, and MXL.

ParameterEnter the value (in seconds) to specify the time interval for delay restore timer to abort. This timer is applicable only during reload/boot-up and not in other scenarios (example, ICL flap)

The range is from 1 to 1800 seconds.

Usage InformationTo abort VLT delay restore timer as the maximum threshold, the maximum time interval is applied to hold down ICL peer-up in the start-up configurations during the reload.

Table 4 restore factory-defaults Command

Syntax restore factory-defaults stack-unit { 0-5 | all} {clear-all | bootvar | nvram}

Parameters

• factory-defaults—Return the system to its factory default mode.

• 0-5—Enter the stack member unit identifier to restore only the mentioned stack-unit.

• all—Enter the keyword all to restore all units in the stack.

• bootvar—Enter the keyword bootvar to reset boot line.

• clear-all—Enter the keywords clear-all to reset the NvRAM, boot environment variables, and the system startup configuration.

• nvram—Enter the keyword nvram to reset the NvRAM only.

Defaults IP selection 5-tuples (source-ip dest-ip vlan protocol L4-source-port L4-dest-port).

Command Modes EXEC Privilege

| 21

Command History

This guide is platform-specific. For command information about other platforms, refer to the relevant Dell Networking OS Command Line Reference Guide.

The following is a list of the Dell Networking OS version history for this command.

• Version 9.5(0.1)—Added bootvar as a new parameters.

• Version 9.0.2.0—Introduced on the S6000.

• Version 9.0.0.0—Introduced on the Z9000.

• Version 8.3.19.0—Introduced on the S4820T.

• Version 8.3.12.0—Introduced on the S4810.

• Version 8.3.16.0—Introduced on the MXL 10/40GbE Switch IO Module.

Usage Information

Restoring factory defaults deletes the existing startup configuration and all persistent settings (stacking, fan-out, and so forth).

When restoring all units in a stack, all the units in the stack are placed into stand-alone mode.

When restoring a single unit in a stack, that unit placed in stand-alone mode. No other units in the stack are affected.

When restoring units in stand-alone mode, the units remain in stand-alone mode after the restoration. After the restore is complete, the units power cycle immediately.

Caution: There is no undo for this command.Following are the factory-default environment variables:

• baudrate

• primary_boot

• secondary_boot

• default_boot

• ipaddr

• gatewayip

• netmask

• macaddr

• mgmtautoneg

• mgmtspeed100

• mgmtfullduplexEach boot path variable (primary_boot, secondary_boot, and default_boot) is further split into the following three independent variables:

• primary_server, primary_file, and primary_type

• secondary_server, secondary_file, and secondary_type

• default_server, default_file, and default_typeNote: For information on the default values that these variables take, refer to the Restoring Factory Default Environment Variables section in the Dell Networking OS Configuration guide.

Table 4 restore factory-defaults Command

22 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om

Example (all stack units)

Dell#restore factory-defaults stack-unit all clear-all*************************************************************** Warning - Restoring factory defaults will delete the existing * startup-config and all persistent settings (stacking, fanout, etc.)* All the units in the stack will be split into standalone units.* After restoration the unit(s) will be powercycled immediately.* Proceed with caution ! ***************************************************************Proceed with factory settings? Confirm [yes/no]:yes-- Restore status --Unit Nvram Config------------------------0 Success Success1 Success Success2 Success Success3 Not present4 Not present5 Not presentPower-cycling the unit(s).Dell#

Example (single stack)

Dell#restore factory-defaults stack-unit 0 clear-all*************************************************************** Warning - Restoring factory defaults will delete the existing ** startup-config and all persistent settings (stacking, fanout, etc.)** After restoration the unit(s) will be powercycled immediately. ** Proceed with caution ! ***************************************************************Proceed with factory settings? Confirm [yes/no]:yes-- Restore status --Unit Nvram Config------------------------0 Success SuccessPower-cycling the unit(s).Dell#

Example (NvRAM all stack units)

Dell#restore factory-defaults stack-unit all nvram*************************************************************** Warning - Restoring factory defaults will delete the existing ** persistent settings (stacking, fanout, etc.) ** All the units in the stack will be split into standalone units. ** After restoration the unit(s) will be powercycled immediately. ** Proceed with caution ! ***************************************************************Proceed with factory settings? Confirm [yes/no]:yes-- Restore status --Unit Nvram Config------------------------0 Success1 Success2 Success3 Not present4 Not present5 Not presentPower-cycling the unit(s).Dell#

Table 4 restore factory-defaults Command

| 23

Caveats

The following sections describe problem report (PR) types, and list open, closed, and rejected PRs:

• Caveat Definitions

• Resolved H/W Caveats for the MXL Switch

• Deferred S/W Caveats for the MXL Switch in Dell Networking OS Version 9.7(0.0)

• Resolved S/W Caveats for the MXL Switch in Dell Networking OS 9.7(0.0)

• Open S/W Caveats for the MXL Switch in Dell Networking OS Version 9.7(0.0)

Example (NvRAM, single unit)

Dell#restore factory-defaults stack-unit 1nvram*************************************************************** Warning - Restoring factory defaults will delete the existing ** persistent settings (stacking, fanout, etc.) ** After restoration the unit(s) will be powercycled immediately. ** Proceed with caution ! ***************************************************************Proceed with factory settings? Confirm [yes/no]:yes-- Restore status --Unit Nvram Config------------------------1 SuccessPower-cycling the unit(s).Dell#

Note: Customers can subscribe to caveat update reports or use the BugTrack search tool to read current information about open and closed software caveats. Visit the BugTrack tool on iSupport. BugTrack currently tracks software caveats opened in Dell Networking OS version 6.2.1.1 and later.

All Release Notes are available on the Software Center tab of iSupport. The link to the relevant Release Notes for each software version is next to the link for that version.

Table 4 restore factory-defaults Command

24 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om Caveat Definitions

Resolved H/W Caveats for the MXL Switch

None

Deferred S/W Caveats for the MXL Switch in Dell Networking OS Version 9.7(0.0)

None

Category Description

PR# Problem Report number that identifies the caveat.

Severity S1—Crash: A software crash occurs in the kernel or a running process that requires a restart of the router or process.S2—Critical: A caveat 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 workaround acceptable to the customer.S3—Major: A caveat that effects the functionality of a major feature or negatively effects the network for which there exists a workaround that is acceptable to the customer.S4—Minor: A cosmetic caveat or a caveat in a minor feature with little or no network impact for which there might be a workaround.

Synopsis Synopsis is the title or short description of the caveat.

Release Notes Release Notes description contains more detailed information about the caveat.

Workaround Workaround describes a mechanism for circumventing, avoiding, or recovering from the caveat. It might not be a permanent solution.

Caveats listed in the “Closed Caveats” section should not be present, and the workaround is unnecessary as the version of code for which this release note is documented has resolved the caveat.

| 25

Resolved S/W Caveats for the MXL Switch in Dell Networking OS 9.7(0.0)

The following caveats have been resolved in the Dell Networking OS version 9.7(0.0):

Forwarding (Resolved)

PR# 145436Severity: Sev 2Synopsis: Offline diag execution will report bcm init failure when ISCSI is enabled.

Release Notes: Offline diag execution will report bcm init failure when ISCSI is enabled.

Workaround: None

IP Stack (Resolved)

PR# 116354Severity: Sev 3Synopsis: Interface error statistics are not updated correctly when ping is done to

unreachable IPv6 neighborRelease Notes: NAWorkaround: NA

SNMP (Resolved)

PR# 140237Severity: Sev 2Synopsis: While executing the CLI command "clear counters", the SNMP counters

for the port-channel are cleared.Release Notes: While executing the CLI command "clear counters", the SNMP counters

for the port-channel are cleared.Workaround: None

Storage Networking (Resolved)

PR# 142530Severity: Sev 2

26 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om

Open S/W Caveats for the MXL Switch in Dell Networking OS Version 9.7(0.0)

The caveats described below are unresolved in Dell Networking OS version 9.7(0.0). To view updated information about open caveats, use the Bug Track search tool on the Dell Networking support web page. You must have a user account (see Accessing Dell Networking Technical Support) to access the Bug Track tool.

To use the Bug Track search tool:

1 Go the Main Customer Support page: https://www.force10networks.com/csportal20/Main/SupportMain.aspx.

2 Log in.

3 Click the BugTrack link, located in the Quick Links menu directly below the login bar.

This takes you to the BugTrack search page: https://www.force10networks.com/csportal20/BugTrack/SearchIssues.aspx.

4 Enter for a specific PR or select an Dell Networking OS version, platform, severity, or category to get a list of PRs.

5 Click the Search button.

The PR (or PRs) appears on the page below the tool.

The following caveats are open in Dell Networking OS version 9.7(0.0):

Synopsis: In certain scenarios, FIP snooping sessions are not load-balanced.

Release Notes: When multiple internal ports of MXL are concurrently brought up, MXL might fail to load balance FIP snooping sessions. This issue has also been noticed when you use Intel, and Broadcom CNAs.

Workaround: None.

ARP (Open)

PR# 141762Severity: Sev 2Synopsis: In some instance, when the link status of VLT ICL flap, the show ip redirect

list command may incorrectly show the unresolved next-hops as resolved.

Release Notes: In some instance, when the link status of VLT ICL flap, the show ip redirect list command may incorrectly show the unresolved next-hops as resolved.

Workaround: To display the correct ARP resolve status, re-configure the PBR redirect list after deleting it.

| 27

DCB (Open)

PR# 107320Severity: Sev 3Synopsis: ETS on PFC enabled PGID's may not confirm to the configuration, when

port-mirroring is enabled and corresponding packets are mirrored.

Release Notes: ETS on PFC enabled PGID's may not confirm to the configuration, when port-mirroring is enabled and corresponding packets are mirrored.

Workaround: No workaround.

PR# 108226Severity: Sev 3Synopsis: In DCBx-CIN version, priorities belonging to 'Strict priority priority-group'

are incorrectly listed as ETS type in the 'show ets detail' output

Release Notes: Though priorities are associated to a 'Strict priority priority-group' in a dcb-output profile that is applied to an interface,they are incorrectly listed as ETS type in the priority-level bandwidth splitup that is displayed in the 'show ets detail' output when the interface has dcbx version to be CIN

Workaround: This is just a display issue and doesn't affect the functionality in any way

PR# 114957Severity: Sev 2Synopsis: Changing the dcbx version on one port is affecting the FCoE traffic on all

portsRelease Notes: When a server blade with Intel x520 CNA is added while the Aggregator is

in operation and DCBx version CEE command is issued, other ports on the Aggregator may experience a traffic loss for 30-50 seconds under some circumstances

Workaround: None. It is recommended that you configure Intel x520 CNA while on boarding the Aggregator.

DHCP (Open)

PR# 122612Severity: Sev 1Synopsis: Setting 4000 PPS to DHCP packets using CoPP might crash the system.

28 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om Release Notes: On applying CoPP policy to increase the rate of DHCP packets to 4000

PPS, DHCP becomes busy in processing the packets that it does not give control to other tasks resulting in heart beat loss followed by crash.

Workaround: Limit the DHCP packets (Rate policing) in CoPP policy to less than 4000 PPS.

Diagnostic (Open)

PR# 147178Severity: Sev 2Synopsis: In S5000 with FC PIC module. Level2 offline diag tests like

OPTMODPHYEXTLINKTEST,PHYLNKSPEEDTEST,CPUSNAKEOPTMODPHYLPBKTEST will fail.

Release Notes: In S5000 with FC PIC module. Level2 offline diag tests like OPTMODPHYEXTLINKTEST,PHYLNKSPEEDTEST,CPUSNAKEOPTMODPHYLPBKTEST will fail.

Workaround: None.

LLDP (Open)

PR# 118185Severity: Sev 3Synopsis: Tab completion doesn't work for the last keyword in "advertise

management-tlv" command.Release Notes: Tab completion doesn't work for the last keyword in "advertise

management-tlv" command.Workaround: NA

Multicast (Open)

PR# 118133Severity: Sev 3Synopsis: Multicast data traffic to receiver connected on orphan port may get

affected when IGMP receiver on VLT LAG leaves the group and vice versa

Release Notes: Multicast data traffic to receiver(s) connected on orphan port may get affected when IGMP receiver on VLT LAG leaves the group and vice versa.

Workaround: Configure fast-leave immediate-leave on the PIM/Snooping enabled VLANs.

| 29

PR# 118195Severity: Sev 3Synopsis: After PIM DR change on a VLT node, multicast data traffic may not reach

receivers in some VLANsRelease Notes: On a VLT pair, when a PIM DR undergoes a change of status, receivers in

some VLANs stop receiving multicast traffic.Workaround: clear the pim data base by issueing command "clear pim tib".

PR# 118555Severity: Sev 3Synopsis: PIM functionality may not work reliably if PIM is enabled on more than 96

VLANs.Release Notes: PIM functionality may not work reliably if PIM is enabled on more than 96

VLANs. 96 is the known limit for max number of L3 enabled PIM interfaces in each port-pipe.

Workaround: To recover from this state, the configuration needs to be brought down to 96 VLANs or below and then disable/enable ip multicast routing.

OS / OS Infrastructure (Open)

PR# 108305Severity: Sev 3Synopsis: NTP server configured with hostname is not updating the IP change for

serverRelease Notes: NTP server configured with hostname is not updating the IP change for

serverWorkaround: Unconfigure and reconfigure the NTP server and it resolves to the new IP.

PR# 140615Severity: Sev 2Synopsis: Under rare circumstances, due to a race condition, the system may raise a

software exception leading to crash.Release Notes: Under rare circumstances, due to incorrect execution of internal threads,

the system may raise a software exception leading to crash.

Workaround: None

PR# 145415Severity: Sev 2Synopsis: The FTOS Authorization feature does not work with some AAA tools.

30 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om Release Notes: The FTOS Authorization feature does not work with some AAA tools such

as H3C iMC. The H3C iMC tool expects 'authentication method' field of Authorization request header' to be populated.

Workaround: None

PR# 146469Severity: Sev 1Synopsis: After a stack failover, the member units reboot several times which may

lead to IPC failures.Release Notes: After a stack failover, the member units reboot several times which may

lead to IPC failures, thereby displaying SWPQ error messages.

Workaround: None

OSPF (Open)

PR# 140247Severity: Sev 2Synopsis: After removing Type-7 NSSA LSAs from the database, corresponding

Self-originated Type-5 LSAs are not removed from the database.

Release Notes: OSPF self originated Type-5 LSAs are not removed from database, when the respective type-7 NSSA LSAs are removed from database

Workaround: None.

PR# 146209Severity: Sev 3Synopsis: The OSPF default route gets purged every 30 seconds.Release Notes: The OSPF default route gets purged every 30 seconds.Workaround: None.

RTM (Open)

PR# 145807Severity: Sev 2Synopsis: Executing clear ip route for multiple VRFs in quick succession might cause

BGP routes' nexthop to become unreachable in some VRFs

Release Notes: Executing clear ip route for multiple VRFs in quick succession might cause BGP routes' nexthop to become unreachable in some VRFs

| 31

Workaround: Execute clear ip route in multiple VRFs with few seconds delay Or Execute clear ip route again for the particular VRF which ran into the issue.

Spanning Tree (Open)

PR# 123322Severity: Sev 2Synopsis: PVST fails to converge between Dell-Force10 and other vendor devices

on non-default native VLAN.Release Notes: PVST fails to converge between Dell-Force10 and other vendor devices

on non-default native VLAN. This issue occurs only when the native vlan is non-default (other than VLAN-1).

Workaround: Use default vlan-1 as native VLAN when interop with other vendor device. Another workaround is to configure Dell-Force10 switch with higher priority value so that it won't become the root.

PR# 144193Severity: Sev 2Synopsis: With spanning-tree bpdu filter feature, the MXL may reload spontaneously

Release Notes: When bpdu filter feature is enabled on spanning tree the system may reload due to memory leak.

Workaround: Disable bpdu filter feature.

Stacking (Open)

PR# 125311Severity: Sev 3Synopsis: When stacked switches are configured with static IP addresses and then

removed from the stack, both IOM will be assigned the same static IP address

Release Notes: When stacked switches are configured with static IP addresses and then removed from the stack, both IOM assigned the same static IP address

Workaround: Once unstacked re-configure the IOM's ip address

Storage Networking (Open)

PR# 138279Severity: Sev 2Synopsis: FCFlexIO FC port (connected to s5k) Oper state flap multiple times during

boot up

32 |

ww

w.d

ell

.co

m|

su

pp

ort

.de

ll.c

om

Technical Support

Dell Networking Technical Support provides a range of documents and tools to assist you with effectively using Dell Networking equipment and mitigating the impact of network outages.

Accessing Dell Networking Technical Support

The URL for Dell Networking Support is www.dell.com/support.

• On the Dell Networking Support page, enter your service tag if you have it. You can also access general support information from this page.

• http://www.dell.com/support/contents/us/en/04/category/Contact-Information/Technical-Support

Release Notes: connect FCFlexIO FC port to S5k FC port.

Workaround: No Workaround.