dell system s4048t–on 9.11(0.0p8) release notes · this document contains information on open and...

Dell System S4048T–ON 9.11(0.0P8)Release NotesThis document contains information on open and resolved caveats, and operational information specific to the Dell Networking OS software and the S4048T-ON platform.

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

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 iSupport at: https://www.force10networks.com/CSPortal20/BugTrack/SearchIssues.aspx. 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: https://www.force10networks.com/CSPortal20/Software/Downloads.aspx.

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

Current Version: 9.11.0.0P8Release Date: 2017-03-22Previous Version: 9.11.0.0P4

Topics:

• Document Revision History

• Supported Hardware

• Supported Software

• New Dell Networking OS Version 9.11(0.0) Features

• Restrictions

• Documentation Corrections

• Changes to Default Behavior and CLI Syntax

• Deferred Issues

• Fixed Issues

• Known Issues

• Upgrading the ONIE Package for the S4048T-ON System

• Upgrading the DIAG Package for the S4048T-ON System

• Installing Dell Networking OS on the S4048T-ON using ONIE

• Upgrading the S4048T-ON Dell Networking OS Image using the Dell Networking OS CLI

• Upgrade the Boot Flash and BIOS from Dell Networking OS

• Upgrading the CPLD

• Uninstalling Dell Networking OS on the S4048T-ON

• Installing a Third Party Operating System

• Support Resources

• Contacting Dell

Rev. A002017 - 03

Dell System S4048T–ON 9.11(0.0P8)Release Notes

1

HTTPS://WWW.FORCE10NETWORKS.COM/CSPORTAL20/BUGTRACK/SEARCHISSUES.ASPX


HTTPS://WWW.FORCE10NETWORKS.COM/CSPORTAL20/SOFTWARE/DOWNLOADS.ASPX

HTTPS://WWW.FORCE10NETWORKS.COM/CSPORTAL20/SOFTWARE/DOWNLOADS.ASPX

HTTPS://WWW.DELL.COM/NETWORKING

HTTPS://WWW.DELL.COM/NETWORKING

Contents

Document Revision History...............................................................................................................................................2Supported Hardware..........................................................................................................................................................2Supported Software.......................................................................................................................................................... 3New Dell Networking OS Version 9.11(0.0) Features..................................................................................................... 4Restrictions.........................................................................................................................................................................5Documentation Corrections..............................................................................................................................................6Changes to Default Behavior and CLI Syntax................................................................................................................ 6Deferred Issues................................................................................................................................................................... 7Fixed Issues......................................................................................................................................................................... 7Known Issues.................................................................................................................................................................... 21Upgrading the ONIE Package for the S4048T-ON System....................................................................................... 24Upgrading the DIAG Package for the S4048T-ON System........................................................................................27Installing Dell Networking OS on the S4048T-ON using ONIE.................................................................................. 29Upgrading the S4048T-ON Dell Networking OS Image using the Dell Networking OS CLI.................................. 40Upgrade the Boot Flash and BIOS from Dell Networking OS.................................................................................... 42Upgrading the CPLD....................................................................................................................................................... 44Uninstalling Dell Networking OS on the S4048T-ON.................................................................................................. 46Installing a Third Party Operating System.....................................................................................................................47Support Resources.......................................................................................................................................................... 48Contacting Dell.................................................................................................................................................................48

Document Revision History

Table 1. Revision History

Date Description

2017–03 Initial release.

Supported HardwareThe following hardware is supported with this platform:

Hardware

Forty-eight fixed 10GBase-T ports supporting 1G/10G speeds

Six fixed QSFP+ ports supporting either one port of 40G or four ports of 10G in breakout mode

Two PSUs

Four fan modules

One MicroUSB serial console port

One universal serial bus (USB Type-A) port for additional file storage

2 Dell System S4048T–ON 9.11(0.0P8)Release Notes

Hardware

Management Ethernet interface

RS-232 Serial interface

Dual core 1.7GHz Rangeley central processing unit (CPU) system

Temperature monitoring

Software-readable thermal monitor

Real time clock (RTC) support

Two hot pluggable redundant power supplies

Power management monitoring

Four removable fans

Standard 1U chassis

The following lists the individual Dell S4048T–ON system hardware components that are available to order:

Table 2. Hardware Components Available to Order

Fan with airflow from I/O side to PSU side (red — normal air flow direction)

Fan with airflow from PSU side to I/O side (blue — reversed air flow direction)

AC or DC power supply with airflow from I/O side to PSU side

AC or DC power supply with airflow from PSU side to I/O side

NOTE: Fan modules and power supplies are field replaceable units.

NOTE: All fans and PSUs must have the same airflow direction. If you mix the airflow direction, the switch detects the discrepancy, issues an alarm, and may auto-shutdown to avoid heat damage to components. You must correct the mixed airflow direction.

Supported SoftwareThe following software is supported with this platform:

Software Minimum Release Requirement

Dell Networking OS 9.11(0.0)

ONIE v3.27.1.0

NOTE: For information on non-Dell OS versions, refer the Release Notes for the Hardware Platform S4048T–ON.


3

New Dell Networking OS Version 9.11(0.0) FeaturesThe following new software features have been added in Dell Networking OS version 9.11(0.0) on the S4048T-ON. Please see the Dell Networking OS Configuration Guide and Dell Networking OS Command-Line Reference Guide for details regarding configurations, restrictions, and usage.

Feature Description

802.1x re-authentication The re-authentication is applicable for authenticated 802.1x devices. When there is a change in the authentication servers, the supplicants connected to all the ports are forced to re-authenticate.

AAA re-authentication Enable re-authentication of user whenever there is a change in the authentication.

Ability to configure GRE protocol type in ERPM

Introduced an option to configure GRE protocol type in ERPM.

Ability to create multiple monitor sessions per interface

Support to create multiple monitor sessions per interface.

Ability to mirror PFC pause frames in RX direction

Support to mirror PFC pause frames in RX direction.

BFD over static route Support to selectively enable or disable BFD on specific next hops based on the configured static route.

BGP peer shutdown Introduced support for shutting down BGP neighbors across all address families and individual address families.

ECMP group count The show cam-usage command now displays the amount of used and available CAM space for ECMP groups in each CAM partition.

FRRP support on VLT Support for inter-connecting VLT domains across data centers using FRRP ring through VLTi.

Global rate interval configuration Ability to configure rate-interval globally. This configuration replaces the default rate-interval value of all physical and portchannel interfaces from its default value to the new configured value.

ICMP vulnerabilities Introduced support to drop icmpv4 or icmpv6 reply messages.

IP PIM RP Candidate Support for configuring a PIM router to act as an RP for a specific set of multicast group address.

MIB support to display the available partitions on flash

Introduced MIB objects to display the information corresponding to various partitions such as /flash, /tmp, /usr/pkg, and /f10/Conf.

MIB support to entAliasMappingTable and LAG

Introduced MIB objects to retrieve the configured LACP information. Introduced MIB objects to map the physical interfaces to its corresponding ifIndex value.

Monitoring transceiver data through SNMP

Introduced a new MIB to retrieve transceiver details.

Multicast traceroute Support for multicast traceroute (mtrace). mtrace is a multicast diagnostic facility used for tracing multicast paths.

OSPF throttling Support for specifying SPF timer values in milli seconds.


Secured CLI mode Introduced the secured CLI mode to prevent users from enhancing the permissions or promoting the privilege levels.

Show QoS Statistics to show egress per queue per Interface drop rate and per queue per port TX rate

Enhanced the show qos statistics egress-queue command output to display per-queue per-port TX and drop rates. Added MIB support to retrieve the same information using SNMP.

SNMP support for WRED drop counters

Introduced MIB support for green, yellow, and red drop counters.

Support for Static VXLAN Using Static VXLAN, you can configure the VXLAN using CLIs instead of using the NVP Controller.

SupportAssist SupportAssist is enabled by default and can be disabled using CLI. When SupportAssist is enabled, the switch periodically sends information to an external SupportAssist server. The information sent includes the identity of the switch like service tag and serial number, configuration, logs, status, core files, event logs and diagnostic information.

Two-factor authentication Introduced two-factor authentication (2FA) in RADIUS deployments to enhance security.

Viewing uRPF status Enhanced the show ipv4 interface and show ipv6 interface commands to display unicast reverse path forwarding (uRPF) status.

VLT port monitoring Introduced support for remote port-monitoring (RSPAN) with VLT.

VRRP priority 255 Introduced support for VRRP Priority 255 in the VLT environment.

X.509v3 Support for X.509v3 Digital Certificates on Dell Networking OS.

Restrictions• You can use non-Dell qualified cables, adapters, and optics in a S4048T-ON switch, but Dell Networking does not guarantee their

performance as the S4048T-ON does not support non-Dell qualified 40G transceivers. If you insert a non-Dell qualified 40G transceiver into a S4048T-ON 40GbE port, the switch places the interface in an error-disabled (operationally down) state and generates a syslog message, such as: %S4048LC0640:8 %IFAGT-2-TRANSCEIVER_UNSUPPORTED_ERROR: Transceiver in slot 1 port 49 unrecognized, putting interface in operational-down state.

To verify the error-disabled status of an interface, enter any of the following show commands.

Dell# show inventory mediaSlot Port Type Media Serial Number F10Qualified-------------------------------------------------------------------- 1 49 UNKNOWN UNKNOWN USC1D6J No** 1 50 QSFP 40GBASE-LR4 UQ90C7B No** 1 51 QSFP 40GBASE-SR4 7503835V009Y Yes 1 52 QSFP 40GBASE-CR4 10190002 No 1 53 QSFP 40GBASE-SR4 FE2429470007 Yes 1 54 Media not present or accessible** Interface is down(error disabled) as transceiver is not F10Qualified

Dell# show interfaces fortyGigE 1/49 fortyGigE 1/49 is up, line protocol is down(error-disabled[Transceiver Unsupported])...

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

• The following features are not available in the Dell Networking OS from version 9.7(0.0):

• PIM ECMP

• Static IGMP join (ip igmp static-group)


5

• IGMP querier timeout configuration (ip igmp querier-timeout)

• IGMP group join limit (ip igmp group join-limit)

• You can use the negotiation auto command to turn auto-negotiation on or off only on fiber interfaces operating at 1G speed.

• If you use the interface range command to select multiple interfaces that are added to the management VRF, the ipv6address command does not display the autoconfig option. You can configure the autoconfig command on individual

interfaces.

• If you use the interface range command to select multiple interfaces that are added to the management VRF, the ipv6 ndcommand 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

• BIOS versions can also be 3.27.0.3 or 3.27.0.10-3.

• ONIE version can also be 3.27.1.0 or 3.27.1.10-0.

• Diag OS version can also be 3.27.3.3 or 3.27.3.10-3.

Documentation CorrectionsThis section describes the error identified in the current releases of the Dell Networking OS.

• The Dell Networking OS Command Line Reference Guide incorrectly mentions a note on multi-process OSPF. It will be corrected in thenext release by including the following note:

• The Dell Networking OS versions 9.4(0.0) and 9.7(0.0) introduce support for VRF on OSPFv2 and OSPFv3 respectively. The multi-process OSPF feature supported on Dell Networking OS version 7.8.1.0 is modified. In earlier versions, multiple OSPF processeswere created without VRF (prior to 9.4(0.0)). In the Dell Networking OS versions 9.4(0.0) and 9.7(0.0) (for OSPFv3), multiple OSPFprocesses can be created on a router, but with only one OSPF process per VRF. However, there can be one OSFPv2 and oneOSPFv3 on the same VRF.

• The following note will be added to Open Shortest Path First (OSPFv2 and OSPFv3) topic of the Dell Networking OS Command LineReference Guide:

• OSPFv2 is supported on IPv6 tunnels only and OSPFv3 is supported on IPv4 tunnels only.

• The following Usage Information will be added to router ospf command of the Dell Networking OS Command Line ReferenceGuide:

• You can create only one OSPFv2 process per VRF.

• When FRRP is enabled in a VLT domain, no flavor of Spanning tree should concurrently be enabled on the nodes of that specific VLTdomain. In essence FRRP and xSTP should not co-exist in a VLT environment.

• Dynamic fan out is supported in S4048T-ON.

Changes to Default Behavior and CLI SyntaxThe following behavior and CLI changes are applicable to the S4048T—ON switch with Dell Networking OS version 9.11(0.0):

While configuring a password using the command line interface, the ~ character is supported.


Deferred IssuesIssues that appear in this section were reported in Dell Networking OS version 9.11(0.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.

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 “Closed Caveats” 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 caveat.

Deferred S4048T-ON 9.11(0.0) Software IssuesThe following caveats are deferred in Dell Networking OS version 9.11(0.0)

IP Stack (Deferred)

PR# 161657

Severity: Sev 2

Synopsis: When ND entries are deleted in one of the VLT peer, it is not synced to other VLT peer.

Release Notes: If ND in VLT-Node-1 ND is deleted, it is not synced to VLT-Node-2. But as soon as node-1 learns ND again due to any pkt being received for that station it will be synced to node-2. Since traffic is hashed across both nodes the time will be less.

Workaround: ”Clear ipv6 neighbor” command could be used to remove stale entries.

Fixed IssuesFixed issues are reported using the following definitions.


7











Fixed S4048T-ON 9.11(0.0P8) Software IssuesThe following issues have been resolved in the Dell Networking OS version 9.11(0.0P8):

PR# 160864

Severity: Sev 2

Synopsis: In certain scenarios, IPv6 processing may take a long time causing high CPU usage.

Release Notes: A software exception causes the IPv6 processing to take a long time. This behavior results in high CPU usage and the switch may reboot.

Workaround: None.

PR# 161297

Severity: Sev 2

Synopsis: Router advertisement (RA) flooding on a layer 3 IPv6 interface causes the system to reboot.

Release Notes: The system experiences a software exception when a layer 3 IPv6 interface is flooded with too many router advertisements.

Workaround: None.

PR# 162254


Severity: Sev 2

Synopsis: With BFD configured, static route stays up even though the next-hop is unreachable.

Release Notes: With BFD configured, static route stays up even though the next-hop is unreachable. In this scenario, the next-hop is unreachable due to the removal of the IP address by the neighbor.

Workaround: None.

PR# 162464

Severity: Sev 1

Synopsis: In certain scenarios, the LSA delay origination timer is set to a very high value.

Release Notes: In certain scenarios, the LSA delay origination timer is set to a very high value. This causes a very long delay to the originating LSA and this results in removal of routes. The large delay is shown in the BACKOFF transmit logs with either a negative or large timer.

Workaround: None.

PR# 162484

Severity: Sev 3

Synopsis: VLT mismatch occurs when the private VLANS are configured on the system.

Release Notes: When secondary VLANs are configured on both local and peer VLT devices, VLT mismatch occurs on the local system.

Workaround: None.

PR# 162694

Severity: Sev 1

Synopsis: In certain scenarios, an extra VLT NDP sync packets are observed between the VLT peers.

Release Notes: When NDP packets are synchronized between VLT peers, sometimes, a VLT node mistakenly synchronizes the same packet to the original VLT Peer. This may result in a loop if the original NDP detail is changed in the first VLT peer.

Workaround: None.

PR# 162736

Severity: Sev 2

Synopsis: After passing through the switch, DHCPv6 packets have extra 4 bytes.

Release Notes: After passing through the switch, DHCPv6 packets have extra 4 bytes.

Workaround: None.

PR# 162737

Severity: Sev 1


9

Synopsis: In certain scenarios, duplicate address and routing loop issues are observed because of stale routes in the kernel.

Release Notes: In certain scenarios, the system cannot remove routes with a different prefix, from the kernel. This causes stale routes which causes the duplicate address and routing loop issues.

Workaround: None.

PR# 162783

Severity: Sev 2

Synopsis: In certain scenarios, passive-interface default command is not added under the OSPF configuration.

Release Notes: In certain scenarios, passive-interface default command is not added under the OSPF configuration.

Workaround: Remove the passive-interface default configuration and then re-apply it.

PR# 162881

Severity: Sev 1

Synopsis: When a stack-unit or line card fails and comes up, system fails to recover automatically.

Release Notes: When a stack-unit splits and rejoins the stack, or when a line card fails and comes up, the system fails to recover automatically as hardware watchdog timer does not work.

Workaround: None.

Fixed S4048T-ON 9.11(0.0P4) Software IssuesThe following issues have been resolved in the Dell Networking OS version 9.11(0.0P4):

PR# 153839

Severity: Sev 1

Synopsis: Incorrect counter increments corresponding to the protocol queue causes the system to reload.

Release Notes: Incorrect counter increments corresponding to the protocol queue causes the system to reload.

Workaround: None.

PR# 158503

Severity: Sev 2

Synopsis: In certain scenarios, the SSH process remains active even after the session is closed, causing high CPU usage.

Release Notes: In certain scenarios, the SSH process remains active even after the session is closed, causing high CPU usage.


Workaround: None.

PR# 160879

Severity: Sev 1

Synopsis: Connecting to the switch frequently using telnet can cause the device to reboot.

Release Notes: The system may experience a software exception and reboot if connected through telnet or SSH very frequently.

Workaround: Decrease the frequency of telnet or SSH connections.

PR# 160890

Severity: Sev 3

Synopsis: The DHCP client, does not get the IP address.

Release Notes: When DHCP snooping is enabled on the second-hop router from the DHCP client, the client does not get the IP address.

Workaround: NA

PR# 161181

Severity: Sev 2

Synopsis: Communication failures happen in some of the member units.

Release Notes: In certain rare scenarios, after the stack failover, communication failures happen in some of the member units.

Workaround: None

PR# 161408

Severity: Sev 2

Synopsis: When the cam-ipv6 extended-prefix command is configured, the used value in the show cam-usage command output is incorrect.

Release Notes: When the cam-ipv6 extended-prefix command is configured, the used value in the show cam-usage command output is incorrect for the ipv6 routes with prefixes from 0/65 to 0/127.

Workaround: None

PR# 161752

Severity: Sev 2

Synopsis: The system displays a configuration error when resume-offset is configured to be higher than pause-threshold.

Release Notes: The system displays a configuration error when resume-offset is configured to be higher than pause-threshold.


11

Workaround: Set the pause-threshold higher than or equal to the resume-offset.

PR# 161761

Severity: Sev 2

Synopsis: BFD session goes down, when a new MAC address is received for the existing session.

Release Notes: BFD session goes down, when a new MAC address is received for the existing session.

Workaround: Remove and add the static route configuration.

PR# 161785

Severity: Sev 1

Synopsis: CRC errors seen with mellanox when connected with DAC cables of length >= 4m

Release Notes: 40G DAC cables of length greater than or equal to 4M when connected to mellanox resulted in CRC errors.

Workaround: Fixed with new preemphasis settings for DAC cables >=4m

PR# 162030

Severity: Sev 2

Synopsis: TCP load balancing always remains in enabled state after the load-balance tcp-udp command is used.

Release Notes: When the load-balance tcp-udp enable command is issued followed by the no load-balance tcp-udp command, the TCP load balancing mechanism does not revert to a disabled state.

Workaround:

PR# 162046

Severity: Sev 2

Synopsis: If the MTU size is changed after shutting down the interface, the OSPF network type moves back to the default, which causes the OSPF routes to fail.

Release Notes: When the OSPF network type is set to P2P, if the MTU size is changed after shutting down the interface, the OSPF network type moves back to the default (broadcast), which causes the OSPF routes to fail.

Workaround: Change the MTU size without shutting down the interface or reconfigure the network type after MTU change.

PR# 162070

Severity: Sev 2

Synopsis: In certain scenarios, system hangs.

Release Notes: In certain scenarios, system hangs due to simultaneous access to certain hardware registers.

Workaround: None.


PR# 162086

Severity: Sev 2

Synopsis: In a VLT setup, some DHCP packets are dropped as the VLT peers act as DHCP relay agents.

Release Notes: When a DHCP discover message is received on one peer and the response is sent by the other peer through the VLTi, some DHCP packets are dropped.

Workaround: None.

PR# 162120

Severity: Sev 2

Synopsis: The system experiences a software exception during the Codenomicon OSPFv3 Test Suite 5.1.0.

Release Notes: The system experiences a software exception during the Codenomicon OSPFv3 Test Suite 5.1.0.

Workaround: None.

PR# 162121

Severity: Sev 2

Synopsis: BGP router-ID is not included in the startup and running configuration.

Release Notes: BGP router-ID is not included in the startup and running configuration.

Workaround: None.

PR# 162147

Severity: Sev 2

Synopsis: 802.1x authentication does not work on stack standby and member units.

Release Notes: 802.1x authentication does not work on stack standby and member units.

Workaround: None.

PR# 162197

Severity: Sev 2

Synopsis: In certain scenarios, DHCP does not work.

Release Notes: In certain scenarios, after booting up, DHCP does not work.

Workaround: Flap the L3 VLAN interfaces.

PR# 162257

Severity: Sev 2


13

Synopsis: Openflow action Groupmod fails, and returns a false error to the controller for the un-supported groupMod type, Fastfailover.

Release Notes: Openflow action Groupmod fails, and returns a false error to the controller for the un-supported groupMod type, Fastfailover.

Workaround: None.

PR# 162430

Severity: Sev 1

Synopsis: In certain scenarios, load balance settings do not persist after a failover or reload.

Release Notes: In certain scenarios load balance settings do not persist after a failover or reload.

Workaround: Use the load-balance command to reconfigure the switch.

PR# 162485

Severity: Sev 2

Synopsis: Modifying the MIB table dot1qVlanStaticTable does not work for interfaces configured as 'portmode hybrid'.

Release Notes: Modifying the MIB table dot1qVlanStaticTable does not work for interfaces configured as 'portmode hybrid'.

Workaround: None.

Fixed S4048T-ON 9.11(0.0) Software IssuesThe following issues have been resolved in the Dell Networking OS version 9.11(0.0):

ARP (Resolved)

PR# 152155

Severity: Sev 3

Synopsis: BFD over static route fails to come up when a management route with subnet 0.0.0.0/0 is configured on the management interface.

Release Notes: BFD over static route fails to come up when a management route with subnet 0.0.0.0/0 is configured on the management interface.

Workaround: None.

DHCP (Resolved)

PR# 160885

Severity: Sev 2

Synopsis: In BMP mode, DHCP request from the device does not include option 54.

Release Notes: In BMP mode, DHCP request from the device does not include option 54.

Workaround: None.


FIB (Resolved)

PR# 159617

Severity: Sev 2

Synopsis: Communication between hosts connected to same numbered ports across stack units is not working

Release Notes: Communication between hosts connected to same numbered ports across stack units is not working. For example, hosts connected to 0/1 may not be able to contact host connected to 2/1 in a stack setup and so on.

Workaround: None

FTSA (Resolved)

PR# 160967

Severity: Sev 2

Synopsis: SupportAssist does not work behind a proxy server.

Release Notes: SupportAssist does not work behind a proxy server.

Workaround: None.

IP Stack (Resolved)

PR# 160829

Severity: Sev 2

Synopsis: In certain scenarios, if the next hop for the management VRF route is reachable also through default VRF, then management route is not reachable.

Release Notes: In certain scenarios, if the next hop for the management VRF route is reachable also through default VRF, then management route is not reachable. The issue is dependent on the order in which the management VRF is created.

Workaround: Use interface name, that is "managementethernet" instead of the next-hop address in the route configuration.

Linecards (Resolved)

PR# 159427

Severity: Sev 1

Synopsis: When an untagged VLAN which is part of an ACL-vlan group is removed and reapplied as a member, traffic from tagged VLANs is dropped.

Release Notes: When an untagged VLAN which is part of an ACL-vlan group is removed and reapplied as a member, traffic from tagged VLANs is dropped. This issue happens when the same ports are members of tagged and untagged VLANs.

Workaround: Use the shutdown and no shutdown commands on the interfaces.

PR# 160101

Severity: Sev 1

Synopsis: When the system is connected to certain devices with autonegotiation configured on the interface, the system may drop a few incoming packets.

Release Notes: When the system is connected to certain devices with autonegotiation configured on the interface, the system may drop a few incoming packets due to incorrect port settings.


15

Workaround: Disable autonegotiation configuration and set the port speed manually on both ends.

LLDP (Resolved)

PR# 158462

Severity: Sev 2

Synopsis: In rare scenarios, LLDP VLAN name TLV values are interpreted wrongly.

Release Notes: In rare scenarios, LLDP VLAN name TLV values are interpreted wrongly.

Workaround: None.

PR# 160705

Severity: Sev 3

Synopsis: LLDP fails when the management interface on the switch is assigned to the management VRF.

Release Notes: LLDP fails when the management interface on the switch is assigned to the management VRF. However, LLDP works without any issue when the management interface is assigned to the default VRF.

Workaround: None.

Microcode (Resolved)

PR# 150842

Severity: Sev 2

Synopsis: In certain scenarios, VRRP sessions flap when storm control is configured on the switch.

Release Notes: In certain scenarios, VRRP sessions flap when storm control is configured on the switch.

Workaround: None.

OS / OS Infrastructure (Resolved)

PR# 151003

Severity: Sev 3

Synopsis: Intel based platforms that use GRUB do not have some entries in the environment variables.

Release Notes: Intel based platforms that use GRUB do not have some entries in the environment variables. The following entries are missing in the environment variables: ethaddr, ipaddr, ipmask, ntaddr and gwaddr.

Workaround: None.

PR# 154390

Severity: Sev 1

Synopsis: Under certain circumstances, an SNMP request packet with the following OID causes the system to crash: 1.3.6.1.2.1.4.34.1.3.2.2.0x112.0xfe.

Release Notes: Under certain circumstances, an SNMP request packet with the following OID causes the system to crash: 1.3.6.1.2.1.4.34.1.3.2.2.0x112.0xfe.

Workaround: None.


PR# 158135

Severity: Sev 2

Synopsis: If a blank password is used to establish a telnet session over port 21, the system crashes.

Release Notes: If a blank password is used to establish a telnet session over port 21, the system crashes.

Workaround: None.

PR# 158797

Severity: Sev 1

Synopsis: In a two-unit stack configuration, heartbeat timeout causes the standby unit to become irresponsive.

Release Notes: In a two-unit stack configuration, heartbeat timeout causes the standby unit to become irresponsive until it is power cycled.

Workaround: None.

PR# 158812

Severity: Sev 2

Synopsis: Under certain scenarios, NLB Multicast traffic is not sent to the range of interfaces specified in the static MAC entry.

Release Notes: Under certain scenarios, NLB Multicast traffic is not sent to the range of interfaces specified in the static MAC entry.

Workaround: None.

PR# 159000

Severity: Sev 2

Synopsis: The system does not allow IPv6 addresses ending with 0 using /128 bit mask

Release Notes: The system does not allow IPv6 addresses ending with 0 using /128 bit mask.

Workaround: None.

PR# 159149

Severity: Sev 1

Synopsis: After upgrading to 9.9.0.0P9, the switch does not come up.

Release Notes: After upgrading to 9.9.0.0P9 and rebooting, the switch does not come up due to corruption in the file system.

Workaround: None.

PR# 159840

Severity: Sev 3

Synopsis: VLAN Name displays an extra space.

Release Notes: VLAN Name displays an extra space.


17

Workaround: None.

PR# 160431

Severity: Sev 3

Synopsis: In certain scenarios, the system displays unwanted error messages when it reloads.

Release Notes: In certain scenarios, the system displays unwanted error messages when it reloads.

Workaround: None.

PR# 160609

Severity: Sev 3

Synopsis: In certain scenarios, the fan runs at 10000 RPM.

Release Notes: In certain scenarios, the fan runs at 10000 RPM, even though the temperature is below the upper threshold limit.

Workaround: None.

PR# 160787

Severity: Sev 3

Synopsis: After upgrading to Dell Networking OS version 9.9(0.0) or later, the system may display EAPOL error messages.

Release Notes: After upgrading to Dell Networking OS version 9.9(0.0) or later, the system may display the following EAPOL error message if Dot1x is disabled in the previous version: EAPOL Frame MsgQ Send Err.

Workaround: None.

PR# 160879

Severity: Sev 1

Synopsis: Connecting to the switch frequently using telnet can cause the device to reboot.

Release Notes: The system may experience a software exception and reboot if connected through telnet or SSH very frequently.

Workaround: Decrease the frequency of telnet or SSH connections.

OSPF (Resolved)

PR# 156122

Severity: Sev 2

Synopsis: System chooses a static route with Administrative Distance (AD) greater than 110 over external OSPF routes.

Release Notes: System chooses a static route with Administrative Distance (AD) greater than 110 over external OSPF routes.

Workaround: None.


PR# 158232

Severity: Sev 1

Synopsis: In a VLT environment, routes leaked between VRFs are incorrectly learnt without taking Administrative Distance into account.

Release Notes: In a VLT environment, routes leaked between VRFs are incorrectly learnt without taking Administrative Distance into account.

Workaround: None.

PR# 160892

Severity: Sev 2

Synopsis: If the default-information-originate always command is configured, route loops may occur.

Release Notes: In certain scenarios, if the default-information-originate always command is configured on OSPF neighbors, route loops can occur.

Workaround: None.

PR# 161209

Severity: Sev 2

Synopsis: In certain scenarios, the system experiences a software exception on reboot when the max-metric router-lsa on-startup command is configured.

Release Notes: The system experiences a software exception on reboot when max-metric router-lsa on-startup command is configured. This issue happens when the no passive-interface command is configured on an interface without an IP address.

Workaround: Assign an IP address to the interface on which the no passive-interface command is configured.

PR# 161365

Severity: Sev 2

Synopsis: The system experiences a software exception during the OSPFv2 test of Codenomicon Defensics 11.11.0 test number 94307.

Release Notes: The system experiences a software exception during the OSPFv2 test of Codenomicon Defensics 11.11.0 test number 94307. It tests the system's ability to handle LSU packet with zero LSA length and nonzero LSA count.

Workaround: None.

Port Monitoring (Resolved)

PR# 158903

Severity: Sev 3

Synopsis: The show monitor session command does not display the session status.

Release Notes: The show monitor session command has been enhanced to display whether the remote monitoring session is enabled or disabled in the system.

Workaround: None.

SNMP (Resolved)


19

PR# 159437

Severity: Sev 2

Synopsis: The system displays an authentication error with SNMP v3.

Release Notes: While using SNMP v3 Get request, the system displays an authentication error even if it is in the discovery phase and hence, it is not valid error condition.

Workaround: None.

Spanning Tree (Resolved)

PR# 159697

Severity: Sev 1

Synopsis: When a large number of VLANs are configured using MSTP, the output of the show running-config command does not display all the configured VLANs.

Release Notes: When a large number of VLANs are configured using the msti vlan command, the output of the show running-config spanning-tree mstp command does not display all the configured VLANs.

Workaround: None.

Stacking (Resolved)

PR# 155356

Severity: Sev 3

Synopsis: The show hardware stackunit 0 stack-ports command incorrectly displays valid stack ports as invalid.

Release Notes: The show hardware stackunit 0 stack-ports command incorrectly displays valid stack ports as invalid.

Workaround: None.

Telnet (Resolved)

PR# 158792

Severity: Sev 2

Synopsis: In certain rare scenarios, the telnet process experiences a software exception.

Release Notes: In certain rare scenarios, the telnet process experiences a software exception. This does not affect user traffic.

Workaround: None.

PR# 161065

Severity: Sev 2

Synopsis: In BMP mode, the telnet server cannot be disabled.

Release Notes: The no ip telnet server enable command does not work in BMP mode.

Workaround: Use the following commands to disable the telnet server: 1. ip telnet server enable 2. no ip telnet server enable

VRRP (Resolved)

PR# 159635

Severity: Sev 2

Synopsis: Using VRRP version 3 for IPv4 VRRP groups is not interoperable with other vendor routers


Release Notes: This release fixes an issue that prevented interoperability of Dell OS9 routers with other vendor routers when using VRRP version 3 for IPv4 VRRP groups. Typically VRRPv2 is used for IPv4 VRRP groups and VRRPv3 for IPv6 groups. Those have always been interoperable. With this fix, using VRRPv3 for IPv4 VRRP groups will be interoperable as well.

Workaround: When interoperating with other vendor routers use VRRP version 2 for all IPv4 VRRP groups.

Known IssuesKnown issues are reported using the following definitions.











Known S4048T–ON Software IssuesThe latest information related to Open Caveats is available on support site through the BugTrack search tool. BugTrack currently tracks software caveats opened in Dell Networking OS version 6.2.1.1 and later.

NOTE: You must have a user account to access the BugTrack tool.

To use the 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.

6 Click the PR number to view specific PR details.

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


21

HTTPS://WWW.FORCE10NETWORKS.COM/CSPORTAL20/MAIN/SUPPORTMAIN.ASPX


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

BGP (Open)

PR# 159068

Severity: Sev 3

Synopsis: The neighbor update-source BGP command supports all Layer 3 interfaces.

Release Notes: The neighbor update-source BGP command supports all Layer 3 interfaces.

Workaround: None.

Diagnostic (Open)

PR# 162146

Severity: Sev 2

Synopsis: CPUSNAKECU10GPHYLDBKTEST fails in offline diag

Release Notes: In S4048T, phy loop back test fails in snake configuration through all 10G ports.

Workaround: None.

FIB (Open)

PR# 138294

Severity: Sev 2

Synopsis: The maximum number of supported Microsoft NLB cluster IPs is increased from 8 to 11

Release Notes: The maximum number of supported Microsoft NLB cluster IPs is increased from 8 to 11

Workaround: None

IP Stack (Open)

PR# 160864

Severity: Sev 2

Synopsis: In certain scenarios, IPv6 processing may take a long time causing high CPU usage.

Release Notes: A software exception causes the IPv6 processing to take a long time. This behavior results in high CPU usage and the switch may reboot.

Workaround: None.

PR# 160891

Severity: Sev 2

Synopsis: The system may experience a software exception if an interface receives router advertisements with multiple IPv6 prefixes.

Release Notes: The system may experience a software exception if an interface receives router advertisements with multiple IPv6 prefixes.

Workaround: None.

PR# 161297

Severity: Sev 2


Synopsis: Router advertisement (RA) flooding on a layer 3 IPv6 interface causes the system to reboot.

Release Notes: The system experiences a software exception when a layer 3 IPv6 interface is flooded with too many router advertisements.

Workaround: None.

PR# 161469

Severity: Sev 2

Synopsis: IPV6 VLT convergence time is more than 2 seconds during ICL no shut/ primary node reboot

Release Notes: When STP/PVSTP is enabled and ICL is flapped, STP detects topology change. This topology change event will flush ND entries. ND entries has to be relearned for data traffic to resume.

Workaround: None. Traffic loss is seen during the interval of deleting and relearning ND entries. Also issue will be happen only with STP/PVSTP enabled

Layer 2 (Open)

PR# 152033

Severity: Sev 3

Synopsis: In Dell Networking OS release 9.9(0.0), VLT mismatch occurs with the default VLAN ID (VLAN ID 1) when VLT is activated.

Release Notes: In Dell Networking OS release 9.9(0.0), VLT mismatch occurs with the default VLAN ID (VLAN ID 1) when VLT is activated.

Workaround: Change the default VLAN ID to anything other than 1.

LLDP (Open)

PR# 118185

Severity: Sev 3

Synopsis: 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# 155900

Severity: Sev 2

Synopsis: In certain scenarios, the static multicast mac address command exceeds the maximum characters (256) that can be entered at the command prompt.

Release Notes: In certain scenarios, the static multicast mac address command exceeds the maximum characters (256) that can be entered at the command prompt. This limitation causes less number of interfaces to be configured.

Workaround: None.

OS / OS Infrastructure (Open)

PR# 108305

Severity: Sev 3

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


23

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

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

QoS (Open)

PR# 159890

Severity: Sev 2

Synopsis: If first match criteria of a match-any class map is an L3 acl, and if it's not a match, traffic matching the other criteria are not honoring the policy

Release Notes: In a class map created with a match-any option, the "any" does not take effect, if the first match criteria is a different L3 ACL created using "ip access-list" instead of an explicit rule. Policy takes effect only if the first match criteria is satisfied.

Workaround: While using match-any option in a class-map, use explicit rules instead of using an ACL created using "ip access-list".

Spanning Tree (Open)

PR# 159166

Severity: Sev 2

Synopsis: Observing traffic loss for ~10 sec during failover in S4048T mixmode stacking

Release Notes: In S4048T mixed mode stacking, with RSTP enabled, traffic loss of ~10 seconds seen at times upon fail over.

Workaround: None.

SSH (Open)

PR# 160683

Severity: Sev 1

Synopsis: SSH Server Terminates Connection with BAD Termination Status

Release Notes: SSH Server Terminates Connection with BAD Termination Status

Workaround: None.

Upgrading the ONIE Package for the S4048T-ON SystemTo upgrade the ONIE package, use one of the following two processes:

• Zero touch (dynamic): Copy the update ONIE installer for your system to the TFTP/HTTP server. Configure the DHCP options using the ONIE specifications shown at the following link: https://github.com/opencomputeproject/onie/wiki/Design-Spec-SW-Updating-ONIE.

• Manual: Copy the image onto the TFTP/HTTP servers and boot ONIE. Update the ONIE using the onie-self-update command, then download and run an ONIE updater image (onie-updater-x86_64-dell_s4048t_c2338-r0). The supported URL types are: HTTP, FTP, TFTP, and FILE.


https://github.com/opencomputeproject/onie/wiki/Design-Spec-SW-Updating-ONIE


To upgrade ONIE, perform the following steps:

1 Reboot the system. During the reboot process, the system displays the following message prompting you to press the Esc key in order to stop the auto-boot process:

Press Esc to stop autoboot ... 5 Grub 2.02~beta2 (Dell Inc) Built by root at ubuntu on Wed_Apr_20_06:23:40_UTC_2016

2 At this prompt message, press the Esc key. The following menu appears:

Grub 2.02~beta2 (Dell Inc) Built by root at ubuntu on Wed_Apr_20_07:13:20_UTC_2016

+----------------------------------------------------------------------------+ | FTOS | | FTOS-Boot Line Interface | | DIAG-OS | |*ONIE | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+

Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'f' to boot FTOS, 'b' to go to BLI, 'o' to boot ONIE, 'd' to boot DIAG-OS, 'e' to edit the commands before booting or 'c' for a command-line.

3 From the menu, choose the ONIE option.

NOTE: To choose an option from the menu, highlight one of the options using the up or down arrow key and press Enter.

The following menu appears:

GNU GRUB version 2.02~beta2+e4a1fe391

+----------------------------------------------------------------------------+ | ONIE: Install OS | | ONIE: Rescue | | ONIE: Uninstall OS | |*ONIE: Update ONIE | | ONIE: Embed ONIE | | EDA-DIAG | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line.

4 From this menu, choose the ONIE : Update ONIE option.



25

The ONIE update mode is enabled and the ONIE prompt appears, as shown:

ONIE: ONIE Update Mode ...Version : 3.27.1.0Build Date: 2015-10-08T09:43-0700Info: Mounting kernel filesystems... done.Info: Mounting LABEL=ONIE-BOOT on /mnt/onie-boot ...Info: Using eth0 MAC address: 00:a0:c9:00:00:36Info: Using eth1 MAC address: 00:a0:c9:00:00:37Info: eth0: Checking link... up.Info: Trying DHCPv4 on interface: eth0DHCPv4 on interface: eth0 failedONIE: Using default IPv4 addr: eth0: 192.168.3.10/255.255.255.0Info: eth1: Checking link... down.ONIE: eth1: link down. Skipping configuration.ONIE: Failed to configure eth1 interfaceStarting: dropbear ssh daemon... done.Starting: telnetd... done.discover: ONIE update mode detected. Running updater.Starting: discover... done.

Please press Enter to activate this console. Info: eth0: Checking link... up.Info: Trying DHCPv4 on interface: eth0

ONIE:/ #5 At the ONIE prompt, to stop the ONIE discovery process, enter the following command:

ONIE:/ # onie-discovery-stop

The ONIE discovery stops, as shown:

discover: ONIE update mode detected.Stopping: discover... done.ONIE:/ # ONIE:/ #

6 Configure an interface and assign an IP address to that interface using the following command:

ONIE:/ # ifconfig eth0 10.16.133.213/167 Enter the following command to upgrade ONIE:ONIE:/ # onie-self-update tftp://<tftp-server–address>/onie-

updater-x86_64-dell_s4048t_c2338-r0.

NOTE: You must copy the onie-updater-x86_64-dell_s4048t_c2338-r0 file to the /tftpboot folder in the

server.

ONIE is updated on the system, as shown:

ONIE:/ # onie-self-update tftp://10.16.127.86/tftpboot/onie-updater-x86_64-dell_s4048t_c2338-r0discover: ONIE update mode detected.Stopping: discover... done.Info: Fetching tftp://10.16.127.86/tftpboot/onie-updater-x86_64-dell_s4048t_c2338-r0 ...Eswar/onie-updater-x 100% |*******************************| 8561k 0:00:00 ETAONIE: Executing installer: tftp://10.16.127.86/tftpboot/onie-updater-x86_64-dell_s4048t_c2338-r0Verifying image checksum ... OK.Preparing image archive ... OK.ONIE: Version : 3.27.1.0ONIE: Architecture : x86_64ONIE: Machine : dell_s4048t_c2338ONIE: Machine Rev : 0ONIE: Config Version: 1Installing ONIE on: /dev/sdaRebooting...ONIE:/ # discover: ONIE update mode detected.Stopping: discover...start-stop-daemon: warning: killing process 533: No such process done.Stopping: dropbear ssh daemon... done.


Stopping: telnetd... done.Stopping: syslogd... done.Info: Unmounting kernel filesystemsThe system is going down NOW!Sent SIGTERM to all processesSent SIGKILL tosd 4:0:0:0: [sda] Synchronizing SCSI cacheRestarting system.machine restart

Upgrading the DIAG Package for the S4048T-ON SystemTo upgrade the DIAG package, use one of the following two processes:

• Zero touch (dynamic): Copy the update ONIE installer for your system to the TFTP/HTTP server. Configure the DHCP options using the ONIE specifications shown at the following link: https://github.com/opencomputeproject/onie/wiki/Design-Spec-SW-Updating-ONIE.

• Manual: Copy the image onto the TFTP/HTTP servers and boot ONIE. Update the ONIE using the onie-self-update command, then download and run an ONIE updater image (diag-installer-x86_64- dell_s4048t_c2338-r0-2016-03-22.bin). The supported URL types are: HTTP, FTP, TFTP, and FILE.

To upgrade DIAG, perform the following steps:


Press Esc to stop autoboot ... 5 Grub 2.02~beta2 (Dell Inc) Built by root at ubuntu on Wed_Apr_20_06:23:40_UTC_2016


Grub 2.02~beta2 (Dell Inc) Built by root at ubuntu on Wed_Apr_20_07:13:20_UTC_2016 +----------------------------------------------------------------------------+ | FTOS | | FTOS-Boot Line Interface | | DIAG-OS | |*ONIE | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'f' to boot FTOS, 'b' to go to BLI, 'o' to boot ONIE, 'd' to boot DIAG-OS, 'e' to edit the commands before booting or 'c' for a command-line.





+----------------------------------------------------------------------------+


27



|*ONIE: Install OS | | ONIE: Rescue | | ONIE: Uninstall OS | | ONIE: Update ONIE | | ONIE: Embed ONIE | | EDA-DIAG | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line.

4 From this menu, choose the ONIE : Install OS option.


The ONIE Installer mode is enabled and the ONIE prompt appears, as shown:

GRUB loading. ONIE: OS Install Mode ...Version : 3.27.1.0Build Date: 2015-10-08T09:43-0700Info: Mounting kernel filesystems... done.Info: Mounting LABEL=ONIE-BOOT on /mnt/onie-boot ...Info: Using eth0 MAC address: 00:a0:c9:00:00:36Info: Using eth1 MAC address: 00:a0:c9:00:00:37Info: eth0: Checking link... up.Info: Trying DHCPv4 on interface: eth0Info: eth1: Checking link...down.ONIE: eth1: link down. Skipping configuration.ONIE: Failed to configure eth1 interfaceStarting: dropbear ssh daemon... done.Starting: telnetd... done.discover: installer mode detected. Running installer.Starting: discover... done.ONIE:/ #

5 At the ONIE prompt, to stop the ONIE discovery process, enter the following command:



ONIE:/ # onie-discovery-stopdiscover: installer mode detected.Stopping: discover... done.ONIE:/ #


ONIE:/ # ifconfig eth0 10.16.133.213/167 Enter the following command to upgrade DIAG on the S4048T-ON system:

onie-nos-install tftp://<tftp-server-adress>/tftpboot/diag-installer-x86_64-dell_s4048t_c2338-r0-2016-03-22.bin

NOTE: You must copy the diag-installer-x86_64-dell_s4048t_c2338-r0-2016-03-22.bin file to the /tftpboot folder in the server.


The DIAG is updated on the system, as shown:

ONIE:/ # onie-nos-install tftp://10.16.127.86/diag-installer-x86_64-dell_s4048t_c2338-r0-2016-03-22.bindiscover: installer mode detected.Stopping: discover... done.Info: Fetching tftp://10.16.127.86/diag-installer-x86_64-dell_s4048t_c2338-r0-2016-03-22.bin ...Eswar/diag-installer 100% |*******************************| 148M 0:00:00 ETAONIE: Executing installer: tftp://10.16.127.86/diag-installer-x86_64-dell_s4048t_c2338-r0-2016-03-22.binIgnoring Verifying image checksum ... OK.cur_dir / archive_path /installer tmp_dir /tmp/tmp.a5KpaxPreparing image archive ...sed -e '1,/^exit_marker$/d' /installer | tar xf - OK.Diag-OS Installer: platform: x86_64-dell_s4048t_c2338-r0 Found EDA-DIAG partition at (/dev/sda3) /tmp/diag_os_install_mode does not exist, installer would run in update mode

Diag OS Installer Mode : UPDATE

EDA-DIAG dev is /dev/sda3

Mounted /dev/sda3 on /tmp/tmp.jZpckMUpdate mode: Copying rootfs.....

Preparing /dev/sda3 EDA-DIAG for rootfs installuntaring into /tmp/tmp.jZpckM

rootfs copy doneSuccess: Support tarball created: /tmp/tmp.jZpckM/onie-support.tar.bz2

INSTALLER DONE...Removing /tmp/tmp.a5KpaxRebooting...ONIE:/ # discover: installer mode detected.Stopping: discover...start-stop-daemon: warning: killing process 546: No such process done.Stopping: dropbear ssh daemon... done.Stopping: telnetd... done.Stopping: syslogd... done.Info: Unmounting kernel filesystemsThe system is going down NOW!Sent SIGTERM to all processesSent SIGKILL tosd 4:0:0:0: [sda] Synchronizing SCSI cacheRestarting system.machine restart

Installing Dell Networking OS on the S4048T-ON using ONIE

NOTE: You will need the Dell Networking OS installer package, ONIE-FTOS-SK-9.11.0.0.bin to install the Dell Networking OS on your S4048T-ON system that has only ONIE.

To install the Dell Networking OS version 9.11(0.0) on a new S4048T-ON device, perform the following steps:


Press Esc to stop autoboot ... 5

Grub 2.02~beta2 (Dell Inc)


29

Built by root at ubuntu on Tue_Jul_12_07:05:39_UTC_2016S4048T Boot Flash Label 3.27.2.7 NetBoot Label 3.27.2.7



+----------------------------------------------+ |FTOS | |FTOS-Boot Line Interface | |DIAG-OS | |ONIE | | | +----------------------------------------------+

Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'f' to boot FTOS, 'b' to go to BLI, 'o' to boot ONIE, 'd' to boot DIAG-OS, 'e' to edit the commands before booting or 'c' for a command-line.





+----------------------------------------------------------------------------+ |*ONIE: Install OS | | ONIE: Rescue | | ONIE: Uninstall OS | | ONIE: Update ONIE | | ONIE: Embed ONIE | | EDA-DIAG | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line.

4 From this menu, choose the ONIE : Install OS option.


The ONIE Installer mode is enabled and the ONIE prompt appears, as shown:

ONIE: OS Install Mode ...Version : 3.27.1.0Build Date: 2015-10-08T09:43-0700Info: Mounting kernel filesystems... done.Info: Mounting LABEL=ONIE-BOOT on /mnt/onie-boot ...Info: Using eth0 MAC address: 00:a0:c9:00:00:36Info: Using eth1 MAC address: 00:a0:c9:00:00:37Info: eth0: Checking link... up.Info: Trying DHCPv4 on interface: eth0Info: eth1: Checking link...down.ONIE: eth1: link down. Skipping configuration.ONIE: Failed to configure eth1 interface


Starting: dropbear ssh daemon... done.Starting: telnetd... done.discover: installer mode detected. Running installer.Starting: discover... done.

ONIE:/ # 5 At the ONIE prompt, to stop the ONIE discovery process, enter the following command:



ONIE:/ # onie-discovery-stopdiscover: installer mode detected.Stopping: discover... done.ONIE:/ #


ONIE:/ # ifconfig eth0 ip-address/prefix7 Enter the following command to begin the installation process:

ONIE:/ # onie-nos-install tftp://<tftp-server-address>/ONIE-FTOS-SK-9.11.0.0.bin

NOTE: You must copy the ONIE-FTOS-SK-9.11.0.0.bin file to the /tftpboot folder in the server.

NOTE: After the Dell Networking OS installation completes, the system automatically reboots.

Following is the installation and boot log of Dell Networking OS:

ONIE:/ # onie-nos-install tftp://10.16.127.143/ONIE-FTOS-SK-9.11.0.0.bindiscover: Rescue mode detected. No discover stopped.Info: Fetching tftp://10.16.127.143/ONIE-FTOS-SK-9.11.0.0.bin ...ONIE-FTOS-SK-9.11.0. 100% |*******************************| 112M 0:00:00 ETAONIE: Executing installer: tftp://10.16.127.143/ONIE-FTOS-SK-9.11.0.0.binVerifying image checksum ... OK.Preparing image archive from /installer ... Done.Verifying Product Platform...Product Name : S4048T-ONImage Platform : FTOS-SKImage File : FTOS-SK-9.11.0.0.binImage Compatibility : VerifiedVerifying MAC Address...MAC Address is ConfiguredImage Platform : FTOS-SKDeleting Extra partitions... Done.Creating New partitions... Done.Creating Hybrid MBR... Done.Mouting /dev/sda4,/dev/sda5 and /dev/sda6... Done.Installing GRUB on /dev/sda4...Done.Copying Images... Done.Rebooting...ONIE:/ # discover: Rescue mode detected. No discover stopped.Stopping: dropbear ssh daemon... done.Stopping: telnetd... done.Stopping: syslogd... done.Info: Unmounting kernel filesystemsThe system is going down NOW!Sent SIGTERM to all processesSent SIGKILL tosd 4:0:0:0: [sda] Synchronizing SCSI cacheRestarting system.machine restart

BIOS (Dell, Inc.) Boot SelectorS4048T 3.27.0.348 x 10GBase-T / 6 x 40G QSFP


31

POST Configuration CPU Signature 406D8 CPU FamilyID=6, Model=4D, SteppingId=8, Processor=0 Microcode Revision 125 Platform ID: 0x10041841 PMG_CST_CFG_CTL: 0x40006 BBL_CR_CTL3: 0x7E2801FF Misc EN: 0x4000840081 Gen PM Con1: 0x203808 Therm Status: 0x884F0000 POST Control=0xEA000303, Status=0xE6009F00

BIOS initializations...

CPGC Memtest ................................ PASS

POST: RTC Battery OK at last cold boot RTC date Tuesday 12/6/2016 7:45:44

POST SPD test ............................... PASS

POST Lower DRAM Memory test.... Perf cnt (curr,fixed): 0x153F6E8A4,0x1FDEFBEB2

POST Lower DRAM Memory test ................. PASSPOST Lower DRAM ECC check ................... PASSSM Bus1 PHY...doneDxE POST

POST Upper DRAM Memory test Short memory cell test....POST Upper DRAM Memory test ................. PASSPOST PCI test ............................... PASSPOST NVRAM check ............................ PASSPOST overall test results ................... PASS

NVRAM: 00 9F 00 E6 03 03 00 EA

Version 2.17.1245. Copyright (C) 2016 American Megatrends, Inc.BIOS Date: 02/22/2016 18:21:39 Ver: 0ACBZ028Press <DEL> or <F2> to enter setup.GRUB loading.Welcome to GRUB!

Grub 2.02~beta2 (Dell Inc) Built by root at ubuntu on Tue_Jul_12_07:05:39_UTC_2016 S4000 Boot Flash Label 3.27.2.7 NetBoot Label 3.27.2.7

Press Esc to stop autoboot ... 0

Primary Boot not ConfiguredSecondary Boot not Configured

Booting DEFAULT configuration...

boot device : flashfile : systema (Dell Networking OS system://APartition)Image Product name FTOS-SK MatchWARNING: skipping large memory map entry: 0x100000000/0x40000000/0x1Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 The NetBSD Foundation, Inc. All rights reserved.


Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved.

Dell Networking OS Release 9.11(0.0) NetBSD 5.1_STABLE (S4000) #0: Fri Dec 2 17:13:27 PST 2016Detecting hardware...: EMC230x RPM based fan controller 0: EMC230x RPM based fan controller 1swwdog0: software watchdog initializeddone.WARNING: 4 errors while detecting hardware; check system log.WARNING: CHECK AND RESET THE DATE!route: writing to routing socket: File exists/etc/8g.disklabel.s4048t -> /etc/8g.disklabel.s4000INFO: Force formatting flash is enabledPartitioning 7641mb flash ....Pass!wd0e Fat32 filesystem not formatted. Formatting...Pass!Mounting /boot

RELEASE IMAGE HEADER DATA :--------------------------Release Image SW Image Count : 9Release Image Major-Version : 9Release Image Minor Version : 11Release Image Maint Version : 0Release Image Patch-Version : 0Release Image Header Size : 140Release Image Data Size : 66927571Release Image Platform Type : 23Release Image Product Name : FTOS-SKRelease Image Checksum Value : 0x71b56405Release Image Header Checksum: 0x163daadfRelease Image Create Year : 2016Release Image Create Month : 12Release Image Create Date : 2Release Image Create Hour : 17Release Image Create Minute : 17Release Image Create Second : 19

SOFTWARE IMAGE HEADER DATA :----------------------------Software Image[1] Major Version : 9Software Image[1] Minor Version : 11Software Image[1] Maint Version : 0Software Image[1] Patch Version : 0Software Image[1] Image type : 2Software Image[1] Header Size : 100Software Image[1] Img Data Size : 16141057Software Image[1] Img Orig Size : 16141057Software Image[1] Family Code : cpSoftware Image[1] Img file Name : CPRPLP-RPM-AP-9.11.0.0.binSoftware Image[1] Hdr Checksum : 0x1ea518a0Software Image[1] Data Checksum : 0xe68bed68

SOFTWARE IMAGE HEADER DATA :----------------------------Software Image[2] Major Version : 9Software Image[2] Minor Version : 11Software Image[2] Maint Version : 0Software Image[2] Patch Version : 0Software Image[2] Image type : 2Software Image[2] Header Size : 100Software Image[2] Img Data Size : 20442016Software Image[2] Img Orig Size : 85022720Software Image[2] Family Code : nbsdpcprplpSoftware Image[2] Img file Name : NBSDPCPRPLP-RPM-AP-9.11.0.0.bin


33

Software Image[2] Hdr Checksum : 0x6bcebe29Software Image[2] Data Checksum : 0xed7e7388

SOFTWARE IMAGE HEADER DATA :----------------------------Software Image[3] Major Version : 9Software Image[3] Minor Version : 11Software Image[3] Maint Version : 0Software Image[3] Patch Version : 0Software Image[3] Image type : 2Software Image[3] Header Size : 100Software Image[3] Img Data Size : 15659296Software Image[3] Img Orig Size : 42741760Software Image[3] Family Code : nbsdlibSoftware Image[3] Img file Name : NBSDLIB-RPM-AP-9.11.0.0.binSoftware Image[3] Hdr Checksum : 0x5c86a3a5Software Image[3] Data Checksum : 0x133d0715

SOFTWARE IMAGE HEADER DATA :----------------------------Software Image[4] Major Version : 3Software Image[4] Minor Version : 21Software Image[4] Maint Version : 2Software Image[4] Patch Version : 6Software Image[4] Image type : 1Software Image[4] Header Size : 100Software Image[4] Img Data Size : 2631886Software Image[4] Img Orig Size : 2631886Software Image[4] Family Code : cpSoftware Image[4] Img file Name : CPRPLP-RPM-BT-3.21.2.6.binSoftware Image[4] Hdr Checksum : 0x87712bcSoftware Image[4] Data Checksum : 0x9a788e43

SOFTWARE IMAGE HEADER DATA :----------------------------Software Image[5] Major Version : 3Software Image[5] Minor Version : 27Software Image[5] Maint Version : 2Software Image[5] Patch Version : 7Software Image[5] Image type : 1Software Image[5] Header Size : 100Software Image[5] Img Data Size : 1041992Software Image[5] Img Orig Size : 1041992Software Image[5] Family Code : cpSoftware Image[5] Img file Name : GRUB202CPRPLP-RPM-BT-3.27.2.7.binSoftware Image[5] Hdr Checksum : 0xb46ef8e5Software Image[5] Data Checksum : 0x141587df

SOFTWARE IMAGE HEADER DATA :----------------------------Software Image[6] Major Version : 3Software Image[6] Minor Version : 21Software Image[6] Maint Version : 0Software Image[6] Patch Version : 4Software Image[6] Image type : 3Software Image[6] Header Size : 100Software Image[6] Img Data Size : 2499100Software Image[6] Img Orig Size : 2499100Software Image[6] Family Code : cpSoftware Image[6] Img file Name : CPRPLP-RPM-SL-3.21.0.4.binSoftware Image[6] Hdr Checksum : 0x7a8fd3bSoftware Image[6] Data Checksum : 0x3289635c

SOFTWARE IMAGE HEADER DATA :----------------------------Software Image[7] Major Version : 3Software Image[7] Minor Version : 27


Software Image[7] Maint Version : 0Software Image[7] Patch Version : 2Software Image[7] Image type : 3Software Image[7] Header Size : 100Software Image[7] Img Data Size : 3009456Software Image[7] Img Orig Size : 3009456Software Image[7] Family Code : cpSoftware Image[7] Img file Name : S4048TCPRPLP-RPM-SL-3.27.0.3.binSoftware Image[7] Hdr Checksum : 0xc9409a22Software Image[7] Data Checksum : 0x8ed9cfb4

SOFTWARE IMAGE HEADER DATA :----------------------------Software Image[8] Major Version : 3Software Image[8] Minor Version : 21Software Image[8] Maint Version : 0Software Image[8] Patch Version : 10Software Image[8] Image type : 3Software Image[8] Header Size : 100Software Image[8] Img Data Size : 2499156Software Image[8] Img Orig Size : 2499156Software Image[8] Family Code : cpSoftware Image[8] Img file Name : ALTCPRPLP-RPM-SL-3.21.0.10-1.binSoftware Image[8] Hdr Checksum : 0xc122fb78Software Image[8] Data Checksum : 0x2a44777

SOFTWARE IMAGE HEADER DATA :----------------------------Software Image[9] Major Version : 3Software Image[9] Minor Version : 27Software Image[9] Maint Version : 0Software Image[9] Patch Version : 10Software Image[9] Image type : 3Software Image[9] Header Size : 100Software Image[9] Img Data Size : 3002712Software Image[9] Img Orig Size : 3002712Software Image[9] Family Code : cpSoftware Image[9] Img file Name : ALT2CPRPLP-RPM-SL-3.27.0.10-2.binSoftware Image[9] Hdr Checksum : 0x79805f83Software Image[9] Data Checksum : 0x4e6657eStarting Dell Networking OS

Dec 6 07:46:56: %S4048T-ON:1 %POLLMGR-6-USER_FLASH_INFO: model: SanDisk Cruzer Blade firmware: 1.26 serial no: 218631921Dec 6 07:46:56: %STKUNIT1-M:CP %RAM-6-ELECTION_ROLE: Stack-unit 1 is transitioning to Management Stack-unit.Dec 6 07:46:56: %STKUNIT1-M:CP %CRYPTO-5-FIPS_SELF_TEST_PASSED: [sysd] FIPS crypto module self-test passedDec 6 07:46:56: %STKUNIT1-M:CP %CHMGR-5-STACKUNIT_DETECTED: stack-unit 1 present

Dec 6 07:46:57: %STKUNIT1-M:CP %CHMGR-5-LPM_CONFIG: Applying the default IPv6 LPM partition configDec 6 07:46:57: %STKUNIT1-M:CP %CHMGR-5-CHECKIN: Checkin from stack-unit 1 (type S4048T-ON, 72 ports)Dec 6 07:47:00: %STKUNIT1-M:CP %CHMGR-5-PEM_INSERTED: Power entry module 1 of unit 1 is insertedDec 6 07:47:00: %STKUNIT1-M:CP %CHMGR-0-PS_UP: Power supply 1 in unit 1 is upDec 6 07:47:02: %STKUNIT1-M:CP %CHMGR-5-PEM_INSERTED: Power entry module 2 of unit 1 is insertedDec 6 07:47:02: %STKUNIT1-M:CP %CHMGR-0-PS_UP: Power supply 2 in unit 1 is upDec 6 07:47:02: %S4048T-ON:1 %CHMGR-5-FAN_SPEED_CHANGE: Fan speed changed to 50 % of the full speedDec 6 07:47:02: %S4048T-ON:1 %CHMGR-2-PSU_FAN_SPEED_CHANGE: PSU_Fan speed changed to 50 % of the full speedDec 6 07:47:02: %STKUNIT1-M:CP %CHMGR-5-FANTRAY_INSERTED: Fan tray 1 of Unit 1 is insertedDec 6 07:47:02: %STKUNIT1-M:CP %CHMGR-5-FANTRAY_INSERTED: Fan tray 2 of Unit 1 is insertedDec 6 07:47:03: %STKUNIT1-M:CP %CHMGR-5-FANTRAY_INSERTED: Fan tray 3 of Unit 1 is inserted


35

Dec 6 07:47:03: %STKUNIT1-M:CP %CHMGR-5-FANTRAY_INSERTED: Fan tray 4 of Unit 1 is insertedDec 6 07:47:03: %STKUNIT1-M:CP %SEC-6-CERT_UPDATED: Host certificate updated for Non-FIPS modeDec 6 07:47:03: %STKUNIT1-M:CP %CHMGR-5-PSU_FAN_STATUS: Fan 1 in PSU 1 of Unit 1 is upDec 6 07:47:03: %STKUNIT1-M:CP %CHMGR-5-PSU_FAN_STATUS: Fan 1 in PSU 2 of Unit 1 is up

Dec 6 07:47:06: %STKUNIT1-M:CP %RAM-5-STACKUNIT_STATE: Stack-unit 1 is in Active State.

This device is configured to enter Bare Metal Provisioning (BMP).BMP will now attempt to download an image, configuration file or boot script using DHCP.

Dec 6 07:47:06: %STKUNIT1-M:CP %CRYPTO-5-FIPS_SELF_TEST_PASSED: [bmp] FIPS crypto module self-test passedDec 6 07:47:07: %STKUNIT1-M:CP %CHMGR-5-STACKUNIT_UP: stack-unit 1 is upDec 6 07:47:07: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Ma 1/1Dec 6 07:47:08: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Ma 1/1Dec 6 07:47:09: %STKUNIT1-M:CP %CHMGR-2-SYSTEM_READY: System ready

This device is in Bare Metal Provisioning (BMP) mode.BMP is attempting to download an image, configuration file or boot script using DHCP.

To continue with the standard manual interactive mode, it is necessary to abort BMP.Press A to abort BMP now.Press C to continue with BMP.Press L to toggle BMP syslog and console messages.Press S to display the BMP status.[A/C/L/S]:% Warning: The bmp process will stop ...Dec 6 07:47:22: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/46Dec 6 07:47:22: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/45Dec 6 07:47:23: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/44Dec 6 07:47:23: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/43Dec 6 07:47:23: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/42Dec 6 07:47:23: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/41Dec 6 07:47:23: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/40Dec 6 07:47:23: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/39Dec 6 07:47:23: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/38Dec 6 07:47:23: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/37Dec 6 07:47:23: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/36Dec 6 07:47:24: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/35Dec 6 07:47:24: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/34Dec 6 07:47:24: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/33Dec 6 07:47:24: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/32Dec 6 07:47:24: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/31Dec 6 07:47:24: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/30Dec 6 07:47:24: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/29Dec 6 07:47:24: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/28


Dec 6 07:47:24: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/27Dec 6 07:47:25: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/26Dec 6 07:47:25: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/25Dec 6 07:47:25: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/24Dec 6 07:47:25: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/23Dec 6 07:47:25: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/22Dec 6 07:47:25: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/21Dec 6 07:47:25: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/20Dec 6 07:47:25: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/19Dec 6 07:47:25: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/18Dec 6 07:47:26: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/17Dec 6 07:47:26: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/16Dec 6 07:47:26: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/15Dec 6 07:47:26: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/14Dec 6 07:47:26: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/13Dec 6 07:47:26: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/12Dec 6 07:47:26: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/11Dec 6 07:47:26: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/10Dec 6 07:47:26: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/9Dec 6 07:47:27: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/8Dec 6 07:47:27: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/7Dec 6 07:47:27: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/6Dec 6 07:47:27: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/5Dec 6 07:47:27: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/4Dec 6 07:47:27: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/3Dec 6 07:47:27: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/2Dec 6 07:47:27: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Te 1/1Dec 6 07:47:27: %STKUNIT1-M:CP %CLI-6-SECURE_CLI_NOT_ENABLED: CLI security mode not enabledDec 6 07:47:28: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Fo 1/51Dec 6 07:47:28: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Fo 1/52Dec 6 07:47:28: %STKUNIT1-M:CP %BMP-5-BMP_DISCOVER: DHCP DISCOVER sent on Ma 1/1.Dec 6 07:47:28: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Te 1/45Dec 6 07:47:28: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Te 1/46Dec 6 07:47:28: %STKUNIT1-M:CP %SYS-5-CONFIG_LOAD: Loading configuration fileDec 6 07:47:28: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Ma 6/1Dec 6 07:47:28: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Ma 5/1Dec 6 07:47:28: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Ma 4/1


37

Dec 6 07:47:29: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Ma 3/1Dec 6 07:47:29: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Ma 2/1Dec 6 07:47:29: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Ma 1/1Dec 6 07:47:29: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Ma 1/1Dec 6 07:47:29: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Fo 1/54Dec 6 07:47:29: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Fo 1/53Dec 6 07:47:29: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Fo 1/52Dec 6 07:47:29: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Fo 1/51Dec 6 07:47:29: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Fo 1/50Dec 6 07:47:30: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Fo 1/49Dec 6 07:47:30: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/48Dec 6 07:47:30: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/47Dec 6 07:47:30: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/46Dec 6 07:47:30: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/45Dec 6 07:47:30: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/44Dec 6 07:47:30: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/43Dec 6 07:47:30: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/42Dec 6 07:47:30: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/41Dec 6 07:47:31: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/40Dec 6 07:47:31: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/39Dec 6 07:47:31: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/38Dec 6 07:47:31: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/37Dec 6 07:47:31: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/36Dec 6 07:47:31: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/35Dec 6 07:47:31: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/34Dec 6 07:47:31: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/33Dec 6 07:47:31: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/32Dec 6 07:47:32: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/31Dec 6 07:47:32: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/30Dec 6 07:47:32: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/29Dec 6 07:47:32: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/28Dec 6 07:47:32: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/27Dec 6 07:47:32: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/26Dec 6 07:47:32: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/25


Dec 6 07:47:32: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/24Dec 6 07:47:32: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/23Dec 6 07:47:33: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/22Dec 6 07:47:33: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/21Dec 6 07:47:33: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/20Dec 6 07:47:33: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/19Dec 6 07:47:33: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/18Dec 6 07:47:33: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/17Dec 6 07:47:33: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/16Dec 6 07:47:33: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/15Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/14Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/13Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/12Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/11Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/10Dell-BMP>Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/9Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/8Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/7Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/6Dec 6 07:47:34: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/5Dec 6 07:47:35: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/4Dec 6 07:47:35: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/3Dec 6 07:47:35: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/2Dec 6 07:47:35: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/1Dec 6 07:47:35: %STKUNIT1-M:CP %CLI-6-SECURE_CLI_NOT_ENABLED: CLI security mode not enabledDec 6 07:47:35: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Te 1/39Dec 6 07:47:35: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Te 1/40Dec 6 07:47:35: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Fo 1/52Dec 6 07:47:35: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Fo 1/51Dec 6 07:47:36: %STKUNIT1-M:CP %CHMGR-4-TEMP_STATUS_CHANGE: Unit 1 temperature state changed to 1 (Current temperature 30C).Dec 6 07:47:36: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 1/46Dec 6 07:47:36: %STKUNIT1-M:CP %SYS-5-CONFIG_I: Configured from EOA0Dec 6 07:47:36: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 1/45Dec 6 07:47:36: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Te 1/41Dec 6 07:47:36: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 1/41Dec 6 07:47:36: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 1/40Dec 6 07:47:36: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 1/39Dec 6 07:47:36: %STKUNIT1-M:CP %SYS-5-CONFIG_LOAD: Loading configuration fileDec 6 07:47:37: %STKUNIT1-M:CP %CLI-6-SECURE_CLI_NOT_ENABLED: CLI security mode not enabledDec 6 07:47:37: %STKUNIT1-M:CP %SEC-5-LOGIN_SUCCESS: Login successful on console

8 After the installation completes, the system displays the following DELL prompt:

Dell>


39

Upgrading the S4048T-ON Dell Networking OS Image using the Dell Networking OS CLIBare Metal Provisioning

NOTE: If you are using Bare Metal Provisioning (BMP), see the Bare Metal Provisioning topic in the Dell Networking OS Configuration Guide or the Open Automation Guide.

Manual Upgrade Procedure

Follow these steps carefully to upgrade your S4048T-ON systems:

1 Dell Networking 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: stack-unit <1-6> | tftp: | scp: | usbflash:] [A: | B:]

EXEC Privilege

Dell#upgrade system ftp: a:Address or name of remote host []: 10.16.127.86Source file name []: /tftpboot/ONIE-FTOS-SK-9.11.0.0.binUser name to login remote host: veswarPassword to login remote host: !!!!!!!!!Dec 6 06:10:47: %S4048T-ON:1 %KERN-6-INT: CP Mgmt port receiving excessive traffic; will be rate controlled!!!!!!!!!!!Dec 6 06:10:58: %S4048T-ON:1 %KERN-6-INT: CP Mgmt port receiving excessive traffic; will be rate controlled - repeated 3 times!!!!!!!!!!!!!!!!!!!!!!!Jul 19 06:11:22: %S4048T-ON:1 %KERN-6-INT: CP Mgmt port receiving excessive traffic; will be rate controlled - repeated 5 times!!!!!!!!.........................................................................................................................!.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................!66927711 bytes successfully copiedSystem image upgrade completed successfully.Dell#Dec 6 06:12:19: %STKUNIT1-M:CP %DOWNLOAD-6-UPGRADE: Upgrade completed successfully

3 Verify that the Dell Networking OS has been upgraded correctly in the upgraded flash partition

show boot system stack-unit [1-6] | all]

EXEC Privilege

Dell#show boot system stack-unit all

Current system image information in the system:===============================================

Type Boot Type A B


----------------------------------------------------------------------------------------------stack-unit 1 FLASH BOOT 9.11(0.0)[boot] 9.10(0.1) stack-unit 2 is not present.stack-unit 3 is not present.stack-unit 4 is not present.stack-unit 5 is not present.stack-unit 6 is not present.Dell#Dell#

4 Change the Primary Boot Parameter of the S4048T-ON to the upgraded partition A: or B:

boot system stack-unit 1 primary system: [A: | B: | tftp: | ftp:]

CONFIGURATION

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

write [memory]

EXEC PRIVILEGE

Dell#Dell#write memory !Dec 6 06:15:48: %STKUNIT1-M:CP %FILEMGR-5-FILESAVED: Copied running-config to startup-config in flash by default

Dell#6 Reload the unit

reload

EXEC PRIVILEGE

Dell#reload

Proceed with reload [confirm yes/no]: yesDec 6 06:16:55: %STKUNIT1-M:CP %CHMGR-5-RELOAD: User request to reload the chassissyncing disks... doneunmounting file systems...unmounting /f10/ConfD/db (mfs:487)...unmounting /f10/flash (/dev/wd0e)...unmounting /usr/pkg (/dev/wd0i)...unmounting /boot (/dev/wd0b)...unmounting /usr (mfs:29)...unmounting /force10 (mfs:24)...unmounting /lib (mfs:21)...unmounting /f10 (mfs:18)...unmounting /tmp (mfs:9)...unmounting /kern (kernfs)...unmounting / (/dev/md0a)... donerebooting...

7 Verify the S4048T-ON has been upgraded to the Dell Networking OS version 9.11(0.0)

show version

EXEC PRIVILEGE

Dell#show version Dell Real Time Operating System SoftwareDell Operating System Version: 2.0Dell Application Software Version: 9.11(0.0)Copyright (c) 1999-2016 by Dell Inc. All Rights Reserved.


41

Build Time: Fri Dec 2 16:58:08 2016Build Path: /build/build01/SW/SRCDell Networking OS uptime is 2 minute(s)

System image file is "system://A"

System Type: S4048T-ON Control Processor: Intel Rangeley with 3 Gbytes (3177037824 bytes) of memory, core(s) 2.

8G bytes of boot flash memory.

1 48x10G, 6x40G TE/FO G (S4048T-ON) 48 Ten GigabitEthernet/IEEE 802.3 interface(s) 6 Forty GigabitEthernet/IEEE 802.3 interface(s)Dell#Dell#

Upgrade the Boot Flash and BIOS from Dell Networking OSTo upgrade the Boot Flash and BIOS from Dell Networking OS, perform the following steps:

1 Upgrade the S4048T-ON Boot Flash image.

upgrade boot bootflash-image stack-unit [<id> | all] [booted | flash: | ftp: | scp: | tftp: | usbflash:]

EXEC Privilege

Dell#Dell#upgrade boot bootflash-image stack-unit 1 booted

Current Boot information in the system:============================================

Card BootFlash Current Version New Version------------------------------------------------------------------------ Unit1 Boot Flash 3.27.2.7 3.27.2.7

*********************************************************************** * 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 upgrade Boot Flash image for stack-unit 1 [yes/no]: y

Bootflash image upgrade for stack-unit 1 completed successfully.Dell#

2 Upgrade the S4048T-ON Boot Selector image.

upgrade boot bootseletor-image stack-unit [<id> | all]

EXEC Privilege

Dell Networking OS version 9.11(0.0) requires S4048T-ON Boot Selector image version 3.27.0.3 or higher. The booted option is used to upgrade the Boot Selector image to the image version packed with the loaded Dell Networking OS image. The Boot Selector image version packed with the loaded Dell Networking OS can be found using the show os-version command in EXEC Privilege mode.

Dell#upgrade boot bootselector-image stack-unit 1 booted

Current Boot information in the system:============================================


Card BootSelector Current Version New Version------------------------------------------------------------------------ Unit1 Boot Selector 3.27.0.2 3.27.0.3

*********************************************************************** * 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 upgrade Boot Selector image for stack-unit 1 [yes/no]: y

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Bootselector image upgrade for stack-unit 1 completed successfully.Dell#

3 Reload the unit

reload

EXEC Privilege

4 Verify the Boot Selector image

show system stack-unit <id>

EXEC Privilege

Dell#show system stack-unit 1

-- Unit 1 --Unit Type : Management UnitStatus : onlineNext Boot : onlineRequired Type : S4048T-ON - 48x10G, 6x40G TE/FO G (S4048T-ON)Current Type : S4048T-ON - 48x10G, 6x40G TE/FO G (S4048T-ON)Master priority : 0Hardware Rev : 3.0Num Ports : 72Up Time : 14 min, 11 secDell Networking OS Version : 9.11(0.0)Jumbo Capable : yesPOE Capable : noFIPS Mode : disabledBoot Flash : 3.27.2.7Boot Selector : 3.27.0.3Memory Size : 3177156608 bytesTemperature : 34CVoltage : okSerial Number : NAPart Number : 0YVCK0 Rev X01Vendor Id : DGDate Code : 04022016Country Code : TWPiece Part ID : TW-0YVCK0-28298-624-0029PPID Revision : X01Service Tag : 64X8VS1Expr Svc Code : 133 584 004 81Auto Reboot : enabledBurned In MAC : 14:18:77:0a:53:80No Of MACs : 3

-- Power Supplies --Unit Bay Status Type FanStatus FanSpeed(rpm)--------------------------------------------------------------------------- 1 1 up AC up 14656 1 2 up AC up 8272


43

-- Fan Status --Unit Bay TrayStatus Fan1 Speed Fan2 Speed------------------------------------------------------------------------------------ 1 1 up up 7840 up 7546 1 2 up up 7840 up 7546 1 3 up up 7840 up 7546 1 4 up up 7840 up 7546

Speed in RPM

Dell#

Upgrading the CPLDThe S4048T-ON system with Dell Networking OS Version 9.11(0.0) requires System CPLD revision 12 and Master CPLD revision 12.

NOTE: If your CPLD revisions are higher than the ones shown here, DO NOT make any changes. If you have questions regarding the CPLD revision, contact technical support.

Verify that a CPLD upgrade is requiredUse the following command to identify the CPLD version:

Dell#show revision

-- Stack unit 1 --S4048TON SYSTEM CPLD : 12S4048TON MASTER CPLD : 12

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

Dell#show os-version

RELEASE IMAGE INFORMATION :--------------------------------------------------------------------- Platform Version Size ReleaseTime S-Series:S4048T-ON 9.11(0.0) 66927711 Dec 2 2016 17:17:19

TARGET IMAGE INFORMATION :--------------------------------------------------------------------- Type Version Target checksum runtime 9.11(0.0) Control Processor passed

BOOT IMAGE INFORMATION :--------------------------------------------------------------------- Type Version Target checksum boot flash 3.27.2.7 Control Processor passed

BOOTSEL IMAGE INFORMATION :--------------------------------------------------------------------- Type Version Target checksum boot selector 3.27.0.3 Control Processor passed

FPGA IMAGE INFORMATION :--------------------------------------------------------------------- Card FPGA Name Version stack-unit 1 S4048TON SYSTEM CPLD 12 stack-unit 1 S4048TON MASTER CPLD 12Dell#


Upgrading the CPLD ImageNOTE: The upgrade fpga-image stack-unit 1 booted command is hidden when using the FPGA Upgrade feature in the CLI. However, it is a supported command and will be accepted when entered as documented.

NOTE: Ensure that the BIOS version is 3.27.0.3 or above. You can verify this version using show system stack-unit 1 command.

To upgrade the CPLD image on S4048T-ON, follow these steps.

1 Shut down all of the interfaces on the system.

shutdown

INTERFACE

2 Upgrade the CPLD image.

upgrade fpga-image stack-unit <id> booted

EXEC Privilege

Dell#upgrade fpga-image stack-unit 1 booted

Current information for the system:=======================================

Card Device Name Current Version New Version------------------------------------------------------------------------ Unit1 S4048TON SYSTEM CPLD 12 12 Unit1 S4048TON MASTER CPLD 11 12

*********************************************************************** * 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 image for stack-unit 1 [yes/no]: yes

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

Upgrade result :================Unit 1 FPGA upgrade successful Unit 1. Please power cycle to take effect.

Dell#Jul 19 06:35:00: %S4048T-ON:1 %DOWNLOAD-6-FPGA_UPGRADE: stack-unit 1 fpga upgrade success.

Dell#3 Power cycle the system physically.Switch off the system by unplugging the power chords from the REAR PSUs and wait until the PSU

FAN–REAR STATUS LED is completely OFF.

NOTE: Do not switch on the system with PSU–REAR LED glowing AMBER.

4 Switch on the system and wait for the Dell prompt. The CPLD version can be verified using show revision command output :

show revision


45

EXEC PRIVILEGE

Dell#sh revision

-- Stack unit 1 --S4048TON SYSTEM CPLD : 12S4048TON MASTER CPLD : 12

Dell#Dell#

NOTE: Do not use power-cycle stack-unit <id> command to power cycle the system and do not power off the system while FPGA upgrade is in progress. For any queries, contact technical support.

Uninstalling Dell Networking OS on the S4048T-ONTo uninstall the Dell Networking OS version 9.11(0.0) on to the new S4048T-ON device, perform the following steps:


Version 2.17.1245. Copyright (C) 2016 American Megatrends, Inc. BIOS Date: 02/22/2016 18:21:39 Ver: 0ACBZ028 Press DEL or F2 to enter setup. GRUB loading. Welcome to GRUB!

Grub 2.02~beta2 (Dell Inc) Built by root at ubuntu on Tue_Jul_12_07:05:39_UTC_2016 S4000 Boot Flash Label 3.27.2.7 NetBoot Label 3.27.2.7

Press Esc to stop autoboot ... 02 At this prompt message, press the Esc key. The following menu appears:

+-------------------------------------------------------------------------+ | FTOS | FTOS-Boot Line Interface | DELL-DIAG | ONIE

+-------------------------------------------------------------------------+3 From the menu, choose the ONIE option.



+---------------------------------------------------------------------+ | ONIE: Install OS | | ONIE: Rescue | |*ONIE: Uninstall OS | | ONIE: Update ONIE | | ONIE: Embed ONIE | | ONIE: Diag ONIE | | DELL-DIAG |+---------------------------------------------------------------------+

4 From this menu, choose the ONIE : Uninstall OSoption.



The uninstall process begins. Following is the log generated by the system while Dell Networking OS 9.11(0.0) uninstalls:

Version : 3.27.2.7Build Date: 2016-07-12T09:43-0700

Info: Mounting kernel filesystems... done.Info: Mounting LABEL=ONIE-BOOT on /mnt/onie-boot ...Info: Using eth0 MAC address: 00:a0:c9:00:00:36Info: Using eth1 MAC address: 00:a0:c9:00:00:37Info: eth0: Checking link... up.Info: Trying DHCPv4 on interface: eth0DHCPv4 on interface: eth0 failedONIE: Using default IPv4 addr: eth0: 192.168.3.10/255.255.255.0Info: eth1: Checking link... down.ONIE: eth1: link down. Skipping configuration.ONIE: Failed to configure eth1 interfaceStarting: dropbear ssh daemon... done.Starting: telnetd... done.discover: Uninstall mode detected. Running uninstaller.Erasing internal mass storage device: /dev/sda4 (32MB) Percent complete: 100%Erase complete.Deleting partition 4 from /dev/sdaErasing internal mass storage device: /dev/sda5 (300MB) Percent complete: 100%Erase complete.Deleting partition 5 from /dev/sdaErasing internal mass storage device: /dev/sda6 (300MB) Percent complete: 100%Erase complete.Deleting partition 6 from /dev/sdaErasing internal mass storage device: /dev/sda7 (5854MB) Percent complete: 100%Erase complete.Deleting partition 7 from /dev/sdaInstalling for i386-pc platform.Installation finished. No error reported.Uninstall complete. Rebooting...discover: Uninstall mode detected. No discover stopped.Stopping: dropbear ssh daemon... done.Stopping: telnetd... done.Stopping: syslogd... done.Info: Unmounting kernel filesystemsThe system is going down NOW!Sent SIGTERM to all processesSent SIGKILL to all processesRequesting system rebootsd 4:0:0:0: [sda] Synchronizing SCSI cacheRestarting system.machine restart

5 After the installation completes, the system displays the following ONIE prompt:

ONIE:/ #

Installing a Third Party Operating SystemApart from the Dell Networking OS, you can also install a supported third party operating system on the S4048T-ON system. For more information on installing a third party operating system, refer to the third party OS vendor's website for OS installation instructions.


47

Support ResourcesThe following support resources are available for the S4048T-ON system.

Documentation ResourcesThis document contains operational information specific to the S4048T-ON system.

For information about using the S4048T-ON, refer to the following documents at http://www.dell.com/support:

• Installing the S4048T-ON System

• Quick Start Guide

• Dell Networking Command Line Reference Guide for the S4048T-ON System

• Dell Networking Configuration Guide for the S4048T-ON 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.

NOTE: You can subscribe to issue update reports or use the BugTrack search tool to read current information about open and closed issues. To subscribe or use BugTrack, visit Dell Support at: https://www.force10networks.com/CSPortal20/BugTrack/SearchIssues.aspx.

Finding DocumentationThis document contains operational information specific to the S4048T-ON system.

• For information about using the S4048T-ON, 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.dell.com/networking.

• For more information about the open network installation environment (ONIE)-compatible third-party operating system, refer to http://onie.org.

Contacting DellNOTE: 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.


http://www.dell.com/support/home/us/en/19?~ck=mn&#19/Products/ser_stor_net/networking

https://www.dell.com/networking

http://onie.org/

http://onie.org/

https://www.force10networks.com/CSPortal20/BugTrack/SearchIssues.aspx

https://www.force10networks.com/CSPortal20/BugTrack/SearchIssues.aspx

http://www.dell.com/support/home/us/en/19?~ck=mn&#19/Products/ser_stor_net/networking



http://onie.org/

http://onie.org/

http://support.dell.com/

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


49

dell system s4048t–on 9.11(0.0p8) release notes · this document contains information on open and...

Documents