Beruflich Dokumente
Kultur Dokumente
A00
2017 - 02
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.
For more information about hardware and software features, commands, and capabilities, see the Dell Networking website at: http://
www.dell.com/en-us/work/learn/networking.
Topics:
Contents
Date Description
2017–02 Initial release.
Requirements
The following requirements apply to the Z9100-ON system.
Hardware Requirements
The following lists the Dell Z9100-ON system hardware requirements:
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.
Software Requirements
Table 2. Software Requirements
Software Minimum Release Requirement
Dell Networking OS 9.11.(0.0P2)
NOTE: For information about non-Dell OS versions, see Dell Z9100-Open Networking (ON) System Release Notes.
Features Description
Support for Static VXLAN Using Static VXLAN, you can configure the VXLAN using CLIs instead of using the NVP Controller.
BFD over static route Support for enabling or disabling BFD on specific neighbors. Support to selectively enable or disable
BFD on specific next hops based on the configured static route.
FRRP support on VLT Support for inter-connecting VLT domains across data centers using FRRP ring through VLTi.
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 Introduced MIB objects to display the information corresponding to various partitions such as /
available partitions on flash flash, /tmp, /usr/pkg, and /f10/Conf.
MIB support to Introduced MIB objects to retrieve the configured LACP information. Introduced MIB objects to map
entAliasMappingTable and LAG the physical interfaces to its corresponding ifIndex value.
OSPF throttling Support for specifying SPF timer values in milli seconds.
Ability to mirror PFC pause frames Support to mirror PFC pause frames in RX direction.
in RX direction
Ability to create multiple monitor Support to create multiple monitor sessions per interface.
sessions per interface
Multicast traceroute Support for multicast traceroute (mtrace). mtrace is a multicast diagnostic facility used for tracing
multicast paths.
Monitoring transceiver data MIB support added for the feature Introduced a new MIB to retrieve transceiver details.
through SNMP
SupportAssist enhancements Included support for transferring core files and event logs to the SupportAssist server.
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, and
diagnostic information. Dell Networking OS 9.11(0.0P2) introduces support for transferring core files
and event logs to the SupportAssist server.
ACL range profiles You can configure range of L4 source and destination ports as part of L3 ACLs, which results in only
one ACL entry. This reduces the space used by ACL entries in the forwarding tab You can configure
range of L4 source and destination ports as part of L3 ACLs which results in multiple ACL entires in
TCAM. You can use the acl range command to ensure that only one TCAM entry is used in the
forwarding table.
AAA re-authentication Enable re-authentication of user whenever there is a change in the authentication.
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.
BGP peer shutdown Support for shutting down BGP neighbors in global configuration mode. Introduced support for
shutting down BGP neighbors across all address families and individual address families.
VLT port monitoring Support for applying port monitoring function on the VLT devices in the network. Introduced support
for remote port-monitoring (RSPAN) with VLT.
Configurable CoPP queues Introduced support for mapping protocols to CPU queues in control plane policing.
PFC storm control Introduced support to disable traffic based on specific priority if PFC storm is received. Introduced
support to drop L2 unicast PFC packets instead of flooding them. Also, introduced new MIBs for
these feature.
Viewing uRPF status Enhanced the show ipv4 interface and show ipv6 interface commands to display unicast reverse path
forwarding (uRPF) status.
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.
Monitoring the overall buffer MIB support added for this feature Introduced new command and SNMP support to display the used
usage for lossy and lossless traffic and available buffer for both lossy and lossless traffic.
Show QoS Statistics to show Enhanced the show qos statistics egress-queue command output to display per-queue per-port TX
egress per Q per Interface drop and drop rates. Added MIB support to retrieve the same information using SNMP.
rate
Global rate interval configuration Support for configuring traffic sampling interval global 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.
SNMP supoprt for WRED drop Introduced MIB support for green, yellow, and red drop counters.
counters
Secured CLI mode Introduced the secured CLI mode to prevent users from enhancing the permissions or promoting the
privilege levels.
VRRP priority 255 Introduced support for VRRP Priority 255 in the VLT environment.
Two-factor authentication Introduced two-factor authentication (2FA) in RADIUS deployments to enhance security.
Restrictions
• BIOS version can also be 3.23.0.0-6,3.23.0.10-1.
• ONIE version can also be 3.23.1.3, 3.23.1.10-2.
• DIAG OS version can also be V3.23.3.3 (APR 8 build), 3.23.3.10-4.
• 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.
• Dell Networking OS does not support encapsulated remote switched port analyzer (ERSPAN) and remote switched port analyzer
(RSPAN) in a VLT setup.
• The following features are not available in Dell Networking OS versions 9.8(1.0P1) and 9.11(0.0P2):
• Protocol-independent multicast (PIM) equal cost multi path (ECMP)
• Static Internet group management protocol (IGMP) join (ip igmp static-group)
• IGMP querier timeout configuration (ip igmp querier-timeout)
• IGMP group join limit (ip igmp group join-limit)
• When 1024 or more VNI profiles are configured, the system takes more time to load. Dell recommends to restrict the VNI profiles to be
less than 1000.
• If you use the interface range command to select multiple interfaces that are added to the management VRF, the ipv6
address 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 nd
command displays the following options but they do not take effect if you use them:
• dns-server
• hop-limit
• managed-config-flag
• max-ra-interval
• mtu
• other-config-flag
• prefix
• ra-guard
• ra-lifetime
• reachable-time
• retrans-timer
• suppress-ra
• While configuring a password using the command line interface, the ~ character is supported.
• The system displays whether there is a change in privilege or role to the administrator’s account since last login.
• DNS Query support for both IP and IPv6: In a dual stack setup, the system sends both A (request for IPv4 — RFC 1035) and AAAA
(request for IPv6 — RFC 3596) record requests to a DNS server even if only the ip name-server command is configured.
• You can use the show pfc statistics command even without enabling DCB on the system.
• When you reload the system, you can use Dell Networking OS CLI and select whether to reload into Dell Networking OS or ONIE.
• Support for hmac-sha2-256-96 hashing algorithm option is discontinued.
• SupportAssist is enabled by default on the system.
Documentation Corrections
In the Dell Networking Command Line Reference Guide for the Z9100–ON System, the version number in the document title and the
command history tables for all the commands is incorrectly mentioned as 9.10(0.0). The correct version number for all the commands
introduced in Z9100-ON is 9.8(1.0P1).
In the Dell Networking OS Configuration Guide for the Z9100–ON System, the version number in the document title is incorrectly
mentioned as 9.10(0.0). The correct version number is 9.8(1.0P1).
The Dell Networking Command Line Reference Guide for the Z9100–ON System and Dell Networking OS Configuration Guide for the
Z9100–ON System mention that the system supports up to eight ACL VLAN groups. But the system supports up to 31 ACL VLAN groups.
Deferred Issues
Issues that appear in this section were reported in Dell Networking OS version 9.10(0.0) as open, but have since been deferred. Deferred
issues are those that are found to be invalid, not reproducible, or not scheduled for resolution.
Deferred issues are reported using the following definitions.
Category Description
PR# Problem Report number that identifies the issue.
Severity S1 — Crash: A software crash occurs in the kernel or a running process that requires a restart of AFM, the router,
switch, or process.
S2 — Critical: An issue that renders the system or a major feature unusable, which can have a pervasive impact on
the system or network, and for which there is no work-around acceptable to the customer.
S3 — Major: An issue that affects the functionality of a major feature or negatively effects the network for which
there exists a work-around that is acceptable to the customer.
S4 — Minor: A cosmetic issue or an issue in a minor feature with little or no network impact for which there might
be a work-around.
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.
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: The clear ipv6 neighbor command could be used to remove stale entries.
PR# 160934
Severity: Sev 2
Synopsis: If we disable and enable DCB when available buffer for lossy service-pool is 0, buffer allocations goes
wrong.
Release Notes: If we disable and enable DCB when available buffer for lossy service-pool is 0, buffer allocations?goes
wrong. Lossy buffer holds 280 KB, when it should stay at 0. No real deployment impact since it is
unlikely for deployments to have all buffer allocated to lossless traffic, and have 0 buffers for lossy
traffic.
Workaround: None.
PR# 161923
Severity: Sev 2
Synopsis: With WRED configured, ACL permit counter shows lesser number of packets hit even though the
entire stream is permitted.
Release Notes: With WRED configured, L2/L3 permit ACL counter on a vlan interface shows lesser than 1000
packets when 1000 packets ingress on a vlan member port even though all the 1000 packets are
allowed. The issue occurs for the first instance of show acl counters after a “clear counter”, with
continuous traffic.
Workaround: Using a more specific clear command, like clear counter would circumvent the issue. None,
otherwise.
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.
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.
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# 160879
Severity: Sev 1
Synopsis: Connecting to the switch frequently using telnet can cause the device to reboot.
PR# 160890
Severity: Sev 3
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: 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
Release Notes: The system displays a configuration error when resume-offset is configured to be
higher than pause-threshold.
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.
PR# 161785
Severity: Sev 1
Synopsis: CRC errors seen with mellanox when connected with DAC cables of length >= 4m.
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: None.
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# 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
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
Release Notes: In certain scenarios, after booting up, DHCP does not work.
PR# 162257
Severity: Sev 2
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# 162290
Severity: Sev 2
Synopsis: The system crashes when rest-server http is enabled, with more than 28 ports
assigned to a vlan in a 40G port configuration.
Release Notes: The system crashes when rest-server http is enabled, with more than 28 ports
assigned to a vlan in a 40G port configuration.
Workaround: None.
PR# 162430
Severity: Sev 2
Release Notes: In certain scenarios load balance settings do not persist after a failover or reload.
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.
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.
BGP (Resolved)
PR# 160978
Severity: Sev 1
Synopsis: System reloads when same BGP route prefix is learned and aggregated through multiple neighbors.
Release Notes: System reloads when same BGP route prefix is learned and aggregated through multiple neighbors.
Workaround: None.
DHCP (Resolved)
PR# 160890
Severity: Sev 3
Release Notes: Client do not get an IP address when dhcp snooping is enabled on a second router from the the dhcp
client.
Workaround: NA
Fipsnooping (Resolved)
PR# 158518
Severity: Sev 2
Synopsis: In DCBX manual mode, spurious DROP_Q_EXCEEDS_LIMIT log may be seen with a DCBX peer with
incompatible DCB configuration. No functionality impact.
Release Notes: If the interface is in DCBX manual mode, spurious PFC_NUM_NO_DROP_Q_EXCEEDS_LIMIT log
could be seen upon processing PDU from a DCBX peer with incompatible DCB configuration. There is
no functionality impact.
FTSA (Resolved)
PR# 160967
Severity: Sev 2
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.
PR# 158658
Severity: Sev 2
Release Notes: For Tomahawk based platforms, Priority from Customer (Inner) Vlan tag will not be copied on to the
Service Provider (Outer) Vlan tag. So for a typical QinQ ISP network, traffic would be carried within
the service provider network with .1p set to zero on the outer van tag.
Workaround: None
LLDP (Resolved)
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.
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# 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.
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# 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.
OSPF (Resolved)
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# 161365
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.
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.
PR# 161393
Severity: Sev 2
Synopsis: Port monitoring direction is not configurable when traffic is mirrored on to fifty gigabit ports.
Release Notes: In the source command used to mirror traffic on to fifty gigabit ports, the parameter that specifies
the direction of source traffic is incorrectly mentioned as destination. The correct parameter is
direction. The default direction is Tx.
Workaround: None.
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.
Telnet (Resolved)
PR# 158792
Severity: Sev 2
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
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
VLT (Resolved)
PR# 158985
Severity: Sev 2
Synopsis: VLT does not function correctly when one peer runs Dell Networking OS version below 9.9(0.0) and
the other runs version 9.9(0.0) or above.
Release Notes: When one VLT device is upgraded to Dell Networking OS version 9.9(0.0) or later from an earlier
version, and the peer VLT device still runs a version less than 9.9(0.0), VLT does not function
correctly for some features due to certain mismatch in the feature related VLT message exchanges.
The affected features include: 1. PVST 2. VLT Q-in-Q 3. CLI batch 4. Provider bridge group Once the
problem manifests, the behavior persists even after the peer VLT device is upgraded to the same
version. It recovers only when both the VLT peers reboot simultaneously.
Workaround: - Upgrade the VLT secondary switch and reboot. - Before VLT secondary switch comes up and
establishes VLT, shutdown VLTi link on the primary device. - Upgrade the VLT primary and reboot. -
Once the VLT primary device is up, use the no shutdown command to enable the VLTi link.
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.
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.
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.
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.
BCM
PR#157586
Severity Sev 2
Release Notes: When using 1G Cu SFP with QSA in S6100, LED does not reflect the port oper status in the following
scenario 1) LED glows amber if the peer port is shut 2) LED glows amber if the peer goes for a reload
This is due to limited space in LED datagram.
Workaround: None.
DCB (Open)
PR# 154978
Severity: Sev 3
Synopsis: Shared cells could get corrupted when dot1p to queue mappings are changed, and shared buffer size
is set to 0.
Release Notes: Shared cells could get corrupted when "dot1p to queue mappings are changed" or "remove and re-
apply of the dcb-map on interface", when the shared buffer size is set to 0.
PR# 155542
Severity: Sev 2
Synopsis: With DCB disabled, Heavy packet drops will be seen on Z9100 during iSCSI Read
Release Notes: In a Non-DCB environment, with Flow control turned on(Tx-Off/Rx-On), when iSCSI read operations
are performed by Windows Servers from EQL storage arrays connected via Z9100s, with 256K I/O
size, and 9k Jumbo frames, heavy egress queue drops are experienced at the Z9100 server facing
ports.
Workaround: Enable Tx Flow control (or) Leave Tx Flow control off, Set server NIC to iSOE mode (iSCSI Offload
Engine)
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
Forwarding (Open)
PR# 154871
Severity: Sev 3
Release Notes: For large packet sizes greater than 1024, you may notice cut-through latency as high as store-and-
forward latency when a port is operating in 10G.
Workaround: No workaround
IP Stack (Open)
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.
PR# 154724
Severity: Sev 3
Synopsis: "% Error: Ipv4acl size should be a multiple of 2" error log seen on carving odd blocks for ipv4 acl
Release Notes: IPV4 acl region should be carved in multiples of 2. If ipv4udfenable option is enabled in cam-acl CLI
for udf-acl, ipv4 acl region should be carved in multiple of 3. In the latter case, "% Error: Ipv4acl size
should be a multiple of 2" error message will be seen after reload
Workaround: None
PR# 160559
Severity: Sev 2
Synopsis: In certain scenarios, the system displays the following error message:
ACL_AGENT_HW_WRITE_ERROR.
Workaround: None.
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# 154903
Severity: Sev 2
Synopsis: On Disable/Enable Multicast routing, traffic drops may be seen due to missing VLAN's in the outgoing
interface list on secondary VLT peer.
Release Notes: In a Multicast VLT environment, after executing disable/enable multicast-routing or after executing
disable/enable PIM on an interface, traffic loss is seen for few of the multicast groups, as few VLAN's
may be missing in the outgoing interface list for these multicast group entries in the secondary VLT
peer.
Workaround: Option 1:- Execute clear ip pim tib for these routes in the primary VLT peer. Option 2:- shut/no shut
on the incoming VLAN interface in the primary VLT peer.
OS / OS Infrastructure (Open)
PR# 108305
Severity: Sev 3
Synopsis: NTP server configured with hostname is not updating the IP change for server
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.
PR# 158152
Severity: Sev 2
Synopsis: UVM pagefault might occur at times during reload of S4K and S6100 chassis.
Release Notes: Issue occurs during reload whenever there is a heavy file activity. Whenever issue occurs box will
automatically reload and core file will get generated.
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 criterias 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.
SSH (Open)
PR# 160683
Severity: Sev 1
Release Notes: SSH Server Terminates Connection with BAD Termination Status
Workaround:
• Zero touch (dynamic): Copy the updated 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_z9100_c2538-r0). The supported URL types are: HTTP,
FTP, TFTP, and FILE.
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 1.99~rc1 (Dell Inc)
Built by build at bsdlab on Fri_Jan_29_04:53:46_UTC_2016
Z9100 Boot Flash Label 3.23.2.8 NetBoot Label 3.23.2.8
2 At this prompt message, press the Esc key. The following menu appears:
+----------------------------------------------- --+
|FTOS |
NOTE: To choose an option from the menu, highlight one of the options using the up or down arrow key and press
Enter.
+-------------------------------------------------+
| ONIE: Install OS |
| ONIE: Rescue |
| ONIE: Uninstall OS |
|*ONIE: Update ONIE |
| ONIE: Embed ONIE |
| EDA-DIAG |
| |
+-------------------------------------------------+
NOTE: To choose an option from the menu, highlight one of the options using the up or down arrow key and press
Enter.
The ONIE update mode is enabled and the ONIE prompt appears, as shown:
ONIE: ONIE Update Mode ...
Version : 3.23.1.3
Build Date: 2015-08-17T14:41-0700
Info: Mounting kernel filesystems... done.
Info: Mounting LABEL=ONIE-BOOT on /mnt/onie-boot ...
Info: Using eth0 MAC address: 90:b1:1c:f4:23:56
Info: eth0: Checking link... up.
Info: Trying DHCPv4 on interface: eth0
DHCPv4 on interface: eth0 failedONIE: Using default IPv4 addr: eth0:
192.168.3.10/255.255.255.0
Starting: 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
NOTE: You must copy the onie-updater-x86_64-dell_z9 100_c2538-r0 file to the /tftpboot folder in the
server.
POST Configuration
CPU Signature 406D8
CPU FamilyID=6, Model=4D, SteppingId=8, Processor=0
Microcode Revision 125
Platform ID: 0x10041A57
PMG_CST_CFG_CTL: 0x40006
BBL_CR_CTL3: 0x7E2801FF
Misc EN: 0x840081
Gen PM Con1: 0x203808
Therm Status: 0x88440000
POST Control=0xEA010303, Status=0xE6009F00
• 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_z9100_c2538-r0-2016-04-08.bin). The
supported URL types are: HTTP, FTP, TFTP, and FILE.
NOTE: If Dell Networking OS is already installed on the Z9100-ON system, before upgrading the DIAG package, you must first
uninstall Dell Networking OS. For more information on uninstalling Dell Netowkring OS, see UninstallingDell Networking OS on
the Z9100-ON.
To upgrade DIAG, 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 1.99~rc1 (Dell Inc)
Built by build at bsdlab on Fri_Jan_29_04:53:46_UTC_2016
Z9100 Boot Flash Label 3.23.2.8 NetBoot Label 3.23.2.8
2 At this prompt message, press the Esc key. The following menu appears:
+----------------------------------------------+
|FTOS |
|FTOS-Boot Line Interface |
|DIAG-OS |
|ONIE |
| |
+----------------------------------------------+
NOTE: To choose an option from the menu, highlight one of the options using the up or down arrow key and press
Enter.
+----------------------------------------------+
|*ONIE: Install OS |
| ONIE: Rescue |
| ONIE: Uninstall OS |
| ONIE: Update ONIE |
| ONIE: Embed ONIE |
| |
NOTE: To choose an option from the menu, highlight one of the options using the up or down arrow key and press
Enter.
The ONIE Installer mode is enabled and the ONIE prompt appears, as shown:
ONIE: OS Install Mode ...
Version : 3.23.1.3
Build Date: 2015-08-17T14:41-0700
Info: Mounting kernel filesystems... done.
ERROR: fsck corrected errors.
Info: Mounting LABEL=ONIE-BOOT on /mnt/onie-boot ...
Info: Using eth0 MAC address: 90:b1:1c:f4:23:56
Info: eth0: Checking link... up.
Info: Trying DHCPv4 on interface: eth0
DHCPv4 on interface: eth0 failedONIE: Using default IPv4 addr: eth0:
192.168.3.10/255.255.255.0
Starting: dropbear ssh daemon... done.
Starting: telnetd... done.
discover: installer mode detected. Running installer.
Starting: discover... done.
Please press Enter to activate this console. Info: eth0: Checking link... up.
Info: Trying DHCPv4 on interface: eth0
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 1.99~rc1 (Dell Inc)
Built by build at bsdlab on Tue_Jul_12_06:57:56_UTC_2016
Z9100 Boot Flash Label 3.23.2.8 NetBoot Label 3.23.2.8
2 At this prompt message, press the Esc key. The following menu appears:
+----------------------------------------------+
|FTOS |
|FTOS-Boot Line Interface |
|DIAG-OS |
|ONIE |
| |
+----------------------------------------------+
NOTE: To choose an option from the menu, highlight one of the options using the up or down arrow key and press
Enter.
+----------------------------------------------+
|*ONIE: Install OS |
| ONIE: Rescue |
| ONIE: Uninstall OS |
| ONIE: Update ONIE |
| ONIE: Embed ONIE |
| |
+----------------------------------------------+
NOTE: To choose an option from the menu, highlight one of the options using the up or down arrow key and press
Enter.
The ONIE Installer mode is enabled and the ONIE prompt appears, as shown:
ONIE: OS Install Mode ...
Version : 3.23.1.3
Build Date: 2015-08-17T14:41-0700
Info: Mounting kernel filesystems... done.
ERROR: fsck corrected errors.
Info: Mounting LABEL=ONIE-BOOT on /mnt/onie-boot ...
Info: Using eth0 MAC address: 90:b1:1c:f4:23:56
Info: eth0: Checking link... up.
Info: Trying DHCPv4 on interface: eth0
DHCPv4 on interface: eth0 failedONIE: Using default IPv4 addr: eth0:
192.168.3.10/255.255.255.0
Starting: dropbear ssh daemon... done.
Starting: telnetd... done.
discover: installer mode detected. Running installer.
Starting: discover... done.
Please press Enter to activate this console. Info: eth0: Checking link... up.
Info: Trying DHCPv4 on interface: eth0
NOTE: You must copy the ONIE-FTOS-Z9100-ON-9.11.0.0P2.bin file to the /tftpboot folder in the server.
NOTE: After the Dell Networking OS installation completes, the system automatically reboots.
POST Configuration
CPU Signature 406D8
CPU FamilyID=6, Model=4D, SteppingId=8, Processor=0
BIOS initializations...
POST:
RTC Battery OK at last cold boot
RTC date Monday 12/7/2015 8:07:08
SM Bus1 PHY...done
DxE POST
NVRAM: 00 9F 00 E6 03 03 01 EA
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 ...
00:00:40: %STKUNIT1-M:CP %SYS-5-CONFIG_LOAD: Loading configuration file
00:00:41: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Ma 1/1
00:00:41: %STKUNIT1-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Ma 1/1
00:00:41: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/34
00:00:41: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Te 1/33
00:00:41: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/32
00:00:41: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/31
00:00:41: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/30
00:00:41: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/29
00:00:41: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/28
00:00:42: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/27
00:00:42: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/26
00:00:42: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/25
00:00:42: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/24
00:00:42: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/23
00:00:42: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/22
00:00:42: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/21
00:00:42: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/20
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/19
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/18
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/17
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/16
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/15
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/14
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/13
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/12
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/11
00:00:43: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/10
00:00:44: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/9
00:00:44: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/8
00:00:44: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/7
00:00:44: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/6
00:00:44: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/5
00:00:44: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/4
00:00:44: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/3
00:00:44: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/2
00:00:44: %STKUNIT1-M:CP %IFMGR-5-ASTATE_DN: Changed interface Admin state to down: Hu 1/1
00:00:46: %STKUNIT1-M:CP %SYS-5-CONFIG_LOAD: Loading configuration file
00:00:46: %STKUNIT1-M:CP %IFMGR-5-ASTATE_UP: Changed interface Admin state to up: Ma 1/1
00:00:46: %STKUNIT1-M:CP %SEC-5-LOGIN_SUCCESS: Login successful on console
Dell-BMP>00:00:49: %STKUNIT1-M:CP %IFMGR-5-OSTATE_UP: Changed interface state to up: Ma 1/1
00:00:49: %STKUNIT1-M:CP %SYS-5-CONFIG_I: Configured from EOA0
00:00:50: %STKUNIT1-M:CP %BMP-5-PROCESS_COMPLETED: BMP process is complete. The
configuration/script must be saved in order to use it after subsequent reloads
8 After the installation completes, the system displays the following DELL prompt:
Dell>
Dell#show revision
-- Stack unit 1 --
Z9100-ON CPLD 1 : 6
Z9100-ON CPLD 2 : 4
Z9100-ON CPLD 3 : 4
Z9100-ON CPLD 4 : 4
To view the CPLD version that is associated with the Dell Networking OS image, use the following command:
Dell#show os-version
shutdown
2 Upgrade the CPLD image.
EXEC Privilege Mode
***********************************************************************
* 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 result :
================
Unit 1 FPGA upgrade successful Unit 1. Please power cycle to take effect.
Dell#
NOTE: You can either manually power-cycle the switch as described in Step 3 or use the following command to power-
cycle the switch from the Dell Networking OS prompt: power-cycle stack-unit 1.
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 OFF.
NOTE: Do not switch on the system with the PSU–Rear LED glowing AMBER.
show revision
Dell#show revision
-- Stack unit 1 --
Z9100-ON CPLD 1 : 6
Z9100-ON CPLD 2 : 4
Z9100-ON CPLD 3 : 4
Z9100-ON CPLD 4 : 4
Dell#
NOTE: Do not power off the system while the FPGA upgrade is in progress. For any queries, contact Technical
Support.
shutdown
2 Upgrade the SMF MSS-IAP image.
EXEC Privilege Mode
***********************************************************************
* 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 ! *
***********************************************************************
Warning - PSU and FANTRAYS Syslog messages may appear during SMF FPGA upgrade.
Please ignore these messages !!!
SMF MSS upgrade in progress!!! Please do NOT power off the unit!!! Auto Reset will happen at
the end of Upgrade!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upgrade result :
================
UNIT1 SMF MSS upgrade successful UNIT1. will go for reboot to complete the upgrade.
After the SMF MSS-IAP upgrade is successfully completed, the system re-boots automatically.
3 After the system re-boots, wait for the Dell prompt. Verify the MSS-IAP version using the show revision command output.
EXEC Privilege Mode
show revision
Dell#show revision
-- Stack unit 1 --
Z9100-ON CPLD 1 : 6
Z9100-ON CPLD 2 : 4
Z9100-ON CPLD 3 : 4
Z9100-ON CPLD 4 : 4
Dell#
shutdown
2 Upgrade the SMF MSS-FPGA image.
EXEC Privilege Mode
***********************************************************************
* 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 ! *
***********************************************************************
SMF FPGA upgrade in progress!!! Please do NOT power off the unit!!! Auto Reset will happen
at the end of Upgrade!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upgrade result :
================
UNIT1 SMF FPGA upgrade successful UNIT1. will go for reboot to complete the upgrade.
NOTE: Upgrade takes approximately five minutes and the system may appear unresponsive or powered off. During this
time, if you remove power from the system, you might need to return the unit to Dell for repair. For any queries, contact
Technical Support.
3 After the system re-boots, wait for the Dell prompt. Verify the MSS FPGA version using the show revision command output.
EXEC Privilege Mode
Dell#show revision
-- Stack unit 1 --
Z9100-ON CPLD 1 : 6
Z9100-ON CPLD 2 : 4
Z9100-ON CPLD 3 : 4
Z9100-ON CPLD 4 : 4
Dell#
NOTE: Do not power off the system while the FPGA upgrade is in progress. For any queries, contact Technical
Support.
shutdown
2 Upgrade the OOB-FPGA image.
EXEC Privilege Mode
***********************************************************************
* 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 ! *
***********************************************************************
OOB FPGA upgrade in progress!!! Please do NOT power off the unit!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upgrade result :
================
UNIT1 OOB FPGA upgrade successful. Power cycle the UNIT1 to complete the upgrade.
Dell#power-cycle stack-unit 1
Proceed with power-cycle? Confirm [yes/no]:yes
Dell#00:19:56: %STKUNIT1-M:CP %CHMGR-5-STACKUNIT_RESET: stack-unit 1ÿ
To upgrade OOB-FPGA on the local region, use the upgrade fpga-image system fpga stack-unit <stack–unit–id>
booted command.
To upgrade OOB-FPGA on the global region, use the upgrade fpga-image system backup-fpga stack-unit <stack–
unit–id> booted command.
NOTE: If the current version of the OOB-FPGA is less than 0.4, upgrade the OOB-FPGA on the global region first using
the upgrade fpga-image system backup-fpga stack-unit <stack–unit–id> booted command and
then power-cycle the system. After upgrading OOB-FPGA on the global region, upgrade it again on the local region
using the upgrade fpga-image system fpga stack-unit <stack–unit–id> booted command. Power-
cycle the system once again after upgrading the OOB-FPGA on the local region.
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
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
EXEC Privilege
CONFIGURATION
5 Save the configuration so that the configuration will be retained after a reload using write memory command.
write [memory]
EXEC PRIVILEGE
Dell#write memory
!
Dec 7 18:58:59: %STKUNIT1-M:CP %FILEMGR-5-FILESAVED: Copied running-config to startup-config
in flash by default
Dell#
Dell#
6 Reload the unit
reload
EXEC PRIVILEGE
Command : reload
Mode : EXEC PRIVILEGE
Dell#reload
Proceed with reload [confirm yes/no]: y
7 Verify the Z9100–ON has been upgraded to the Dell Networking OS version 9.11(0.0)P2
show version
Dell#show version
Dell Real Time Operating System Software
Dell Operating System Version: 2.0
Dell Application Software Version: 9.11(0.0P2)
Copyright (c) 1999-2016 by Dell Inc. All Rights Reserved.
Build Time: Tue Dec 13 00:15:53 2016
Build Path: /build/build07/SW/SRC
Dell Networking OS version 9.11(0.0P2) requires the Z9100-ON Boot Selector image version 3.23.0.0-6. To upgrade the Boot Selector
image to the image version packed with the loaded Dell Networking OS image, use the booted option. You can find the Boot Selector
image version packed with the loaded Dell Networking OS using the show os-version command in EXEC Privilege mode.
***********************************************************************
* 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 ! *
***********************************************************************
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Bootselector image upgrade for stack-unit 1 completed successfully.
2 Reload the unit
EXEC Privilege Mode
reload
3 Verify the Boot Selector image
EXEC Privilege Mode
-- Unit 1 --
Unit Type : Management Unit
Status : online
Next Boot : online
Required Type : Z9100-ON - 34-port TE/TF/FO/FI/HU G (Z9100-ON)
Current Type : Z9100-ON - 34-port TE/TF/FO/FI/HU G (Z9100-ON)
Master priority : NA
Hardware Rev : 0.0
Num Ports : 130
Up Time : 3 min, 41 sec
Dell Networking OS Version : 9.11(0.0P2)
Jumbo Capable : yes
POE Capable : no
FIPS Mode : disabled
Boot Flash : 3.23.2.8
Boot Selector : 3.23.0.0-6
Memory Size : 3177226240 bytes
Temperature : 29C
Voltage : ok
Serial Number : NA
Part Number : 03GT5N Rev X02
Vendor Id : NA
Date Code : NA
Country Code : NA
Piece Part ID : CN-03GT5N-77931-58H-0004
PPID Revision : X02
Service Tag : 20JQG02
Expr Svc Code : 438 671 117 0
Auto Reboot : enabled
Burned In MAC : 4c:76:25:e5:d9:40
No Of MACs : 3
-- Power Supplies --
Unit Bay Status Type FanStatus FanSpeed(rpm)
---------------------------------------------------------------------------
1 1 up AC up 9104
1 2 down UNKNOWN down 0
-- Fan Status --
Unit Bay TrayStatus Fan1 Speed Fan2 Speed
------------------------------------------------------------------------------------
1 1 up up 8492 up 8936
1 2 up up 8511 up 8699
1 3 up up 8511 up 8757
1 4 up up 8604 up 8680
1 5 up up 8529 up 8816
Speed in RPM
4 Upgrade the Dell Networking OS GRUB.
EXEC Privilege Mode
!!!
Bootflash image upgrade for stack-unit 1 completed successfully.
Dell#
5 Reload the unit
EXEC Privilege Mode
reload
6 Verify whether the upgrade is successful.
Dell#show system stack-unit 1
-- Unit 1 --
Unit Type : Management Unit
Status : online
Next Boot : online
Required Type : Z9100-ON - 34-port TE/TF/FO/FI/HU G (Z9100-ON)
Current Type : Z9100-ON - 34-port TE/TF/FO/FI/HU G (Z9100-ON)
Master priority : NA
Hardware Rev : 0.0
Num Ports : 130
Up Time : 1 min, 7 sec
Dell Networking OS Version : 9.11(0.0P2)
Jumbo Capable : yes
POE Capable : no
FIPS Mode : disabled
Boot Flash : 3.23.2.8
Boot Selector : 3.23.0.0-6
Memory Size : 3177226240 bytes
Temperature : 32C
Voltage : ok
Serial Number : NA
Part Number : 11ABCD Rev X02
Vendor Id : NA
Date Code : NA
Country Code : NA
Piece Part ID : CN-11ABCD-12345-6AQ-0026
PPID Revision : X02
Service Tag : 20HRG02
Expr Svc Code : 438 339 859 4
Auto Reboot : enabled
Burned In MAC : 00:12:32:12:42:11
No Of MACs : 3
-- Power Supplies --
Unit Bay Status Type FanStatus FanSpeed(rpm)
---------------------------------------------------------------------------
1 1 up AC up 9200
1 2 down UNKNOWN down 0
-- Fan Status --
Unit Bay TrayStatus Fan1 Speed Fan2 Speed
------------------------------------------------------------------------------------
1 1 up up 8366 up 8642
1 2 up up 8529 up 8680
1 3 up up 8623 up 8699
1 4 up up 8492 up 8623
1 5 up up 8366 up 8757
Dell#
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 1.99~rc1 (Dell Inc)
Built by root at bsdlab on Tue_Jul_12_06:57:56_UTC_2016
Z9100 Boot Flash Label 3.23.2.8 NetBoot Label 3.23.2.8
2 At this prompt message, press the Esc key. The following menu appears:
+-------------------------------------------+
|FTOS |
|FTOS-Boot Line Interface |
|DIAG-OS |
|ONIE |
| |
+-------------------------------------------+
NOTE: To choose an option from the menu, highlight one of the options using the up or down arrow key and press
Enter.
+--------------------------------------------+
| ONIE: Install OS |
| ONIE: Rescue |
|*ONIE: Uninstall OS |
| ONIE: Update ONIE |
| ONIE: Embed ONIE |
| EDA-DIAG |
| |
+--------------------------------------------+
NOTE: To choose an option from the menu, highlight one of the options using the up or down arrow key and press
Enter.
POST Configuration
CPU Signature 406D8
CPU FamilyID=6, Model=4D, SteppingId=8, Processor=0
Microcode Revision 125
Platform ID: 0x10041A57
PMG_CST_CFG_CTL: 0x40006
BBL_CR_CTL3: 0x7E2801FF
Misc EN: 0x840081
Gen PM Con1: 0x203808
Therm Status: 0x88440000
POST Control=0xEA010303, Status=0xE6009F00
BIOS initializations...
POST:
RTC Battery OK at last cold boot
RTC date Sunday 12/13/2015 8:49:12
Support Resources
The following support resources are available for the Z9100–ON system.
Documentation Resources
This document contains operational information specific to the Z9100–ON system.
For information about using the Z9100–ON, see the following documents at http://www.dell.com/support:
For more information about hardware features and capabilities, see 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, see 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.
• For information about using the Z9100–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 Dell
NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip,
bill, or Dell product catalog.
Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services
may not be available in your area. To contact Dell for sales, technical support, or customer service issues:
Go to www.dell.com/support.
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.