H3C S9820 Series User manual

H3C S9820 Switch Series
Troubleshooting Guide
Document version: 6W100-20190815
Copyright © 2019 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New
H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are
the property of their respective owners.
The information in this document is subject to change without notice

i
Contents
Introduction·····················································································1
General guidelines ·····················································································································1
Collecting log and operating information ·························································································2
Collecting common log messages···························································································2
Collecting diagnostic log messages·························································································3
Collecting operating statistics·································································································4
Troubleshooting hardware··································································5
Unexpected switch reboot············································································································5
Symptom···························································································································5
Troubleshooting flowchart ·····································································································6
Solution·····························································································································6
Operating power module failure ····································································································7
Symptom···························································································································7
Solution·····························································································································7
Newly installed power module failure······························································································8
Symptom···························································································································8
Solution·····························································································································8
Fan tray failure ··························································································································8
Symptom···························································································································8
Solution·····························································································································9
Related commands ····················································································································9
Troubleshooting ACL ······································································10
ACL application failure with an error message················································································10
Symptom·························································································································10
Solution···························································································································10
ACL application failure without an error message············································································10
Symptom·························································································································10
Troubleshooting flowchart ···································································································11
Solution···························································································································11
Related commands ··················································································································12
Troubleshooting IRF ·······································································13
IRF fabric setup failure··············································································································13
Symptom·························································································································13
Troubleshooting flowchart ···································································································14
Solution···························································································································15
Related commands ··················································································································17
Troubleshooting Ethernet link aggregation···········································17
Link aggregation failure·············································································································17
Symptom·························································································································17
Troubleshooting flowchart ···································································································18
Solution···························································································································18
Related commands ··················································································································19
Troubleshooting ports ·····································································20
A QSFP28 fiber port fails to come up ···························································································20
Symptom·························································································································20
Troubleshooting flowchart ···································································································21
Solution···························································································································21
Non-H3C transceiver module error message ·················································································22
Symptom·························································································································22
Troubleshooting flowchart ···································································································23
Solution···························································································································23
Transceiver module does not support digital diagnosis·····································································24

ii
Symptom·························································································································24
Troubleshooting flowchart ···································································································24
Solution···························································································································24
Error frames (for example, CRC errors) on a port············································································25
Symptom·························································································································25
Troubleshooting flowchart ···································································································26
Solution···························································································································26
Failure to receive packets··········································································································27
Symptom·························································································································27
Troubleshooting flowchart ···································································································28
Solution···························································································································28
Failure to send packets ·············································································································29
Symptom·························································································································29
Troubleshooting flowchart ···································································································30
Solution···························································································································30
Related commands ··················································································································31
Troubleshooting EVPN····································································32
EBGP or IBGP neighbor relationship setup failure···········································································32
Symptom·························································································································32
Troubleshooting flowchart ···································································································32
Solution···························································································································33
Related commands ··················································································································33
Troubleshooting system management ················································34
High CPU utilization··················································································································34
Symptom·························································································································34
Troubleshooting flowchart ···································································································34
Solution···························································································································35
High memory utilization·············································································································36
Symptom·························································································································36
Troubleshooting flowchart ···································································································37
Solution···························································································································37
Related commands ··················································································································38
Troubleshooting other problems························································38
Layer 2 forwarding failure ··········································································································38
Symptom·························································································································38
Troubleshooting flowchart ···································································································39
Solution···························································································································39
Related commands············································································································45
Layer 3 forwarding failure ··········································································································46
Symptom·························································································································46
Troubleshooting flowchart ···································································································47
Solution···························································································································47
Related commands············································································································48
Protocol flapping······················································································································48
Symptom·························································································································48
Troubleshooting flowchart ···································································································49
Solution···························································································································49

1
Introduction
This document provides information about troubleshooting common software and hardware
problems with the S9820 switch series.
This document is not restricted to specific software or hardware versions.
General guidelines
IMPORTANT:
To prevent a problem from causing loss of configuration, save the configuration each time you finish
configuring a feature. For configuration recovery, regularly back up the configuration to a remote
server.
When you troubleshoot the switch, follow these general guidelines:
•To help identify the cause of the problem, collect system and configuration information,
including:
{Symptom, time of failure, and configuration.
{Network topology information, including the network diagram, port connections, and points
of failure.
{Common log messages and diagnostic log information. For more information about
collecting this information, see "Collecting log and operating information."
{Physical evidence of failure:
−Photos of the hardware.
−Status of the LEDs.
{Steps you have taken, such as reconfiguration, cable swapping, and reboot.
{Output from the commands executed during the troubleshooting process.
•To ensure safety, wear an ESD wrist strap when you replace or maintain a hardware
component.
•If hardware replacement is required, use the release notes to verify the hardware and software
compatibility.

2
Collecting log and operating information
IMPORTANT:
To facilitate quick troubleshooting, execute the following commands:
•info-center enable—Enables the information center. By default, the information center is enabled.
•info-center logfile enable—Enables the log file feature so the system outputs logs to log files. By default,
the log file feature is enabled.
•info-center diagnostic-logfile enable—Enables saving diagnostic logs to the diagnostic log file. By
default, saving diagnostic logs to the diagnostic log file is enabled.
During operation, the device generates common log messages and diagnostic log messages to
record information about routine operations and operating status. Table 1 shows the types of files
that the system uses to store the log messages. You can export these files by using FTP, TFTP, or
USB.
In an IRF system, log files are stored on the master device. Multiple devices will have log files if
master/subordinate switchovers have occurred. You must collect log files from all member devices.
To more easily identify log files from different member devices, use two directories to save the log
files from each member device and include member IDs in the directory names.
Table 1 Log and operating information
Category File name format Log file
directory Content
Common log logfile.log flash:/logfile Command execution, events, and status
changes log messages.
Diagnostic
log diagfile.log flash:/diagfile
Diagnostic log messages about device operation,
including the following items:
•Parameter settings in effect when an error
occurs.
•Information about a card startup error.
•Handshaking information between member
devices when a communication error
occurs.
Operating
statistics file-basename.tar.gz N/A
Current operating statistics for feature modules,
including the following items:
•Device status.
•CPU status.
•Memory status.
•Configuration status.
•Software entries.
•Hardware entries.
Collecting common log messages
1. Save common log messages from the log buffer to a log file.
By default, the log file is saved in the logfile directory of the flash memory on each member
device.

3
<Sysname> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
2. Identify the common log file on each member device:
# Display the common log file on the master device.
<Sysname> dir flash:/logfile/
Directory of flash:/logfile
0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log
1048576 KB total (38812 KB free)
# Display the common log file on each subordinate device:
<Sysname> dir slot2#flash:/logfile/
Directory of slot2#flash:/logfile
0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log
1048576 KB total (38812 KB free)
3. Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)
Collecting diagnostic log messages
1. Save diagnostic log messages from the diagnostic log file buffer to a diagnostic log file.
By default, the diagnostic log file is saved in the diagfile directory of the flash memory on each
member device.
<Sysname> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
flash:/diagfile/diagfile.log
2. Identify the diagnostic log file on each member device:
# Display the diagnostic log file on the master device.
<Sysname> dir flash:/diagfile/
Directory of flash:/diagfile
0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log
1048576 KB total (38812 KB free)
# Display the diagnostic log file on each subordinate device:
<Sysname> dir slot2#flash:/diagfile/
<Sysname> dir slot2#flash:/diagfile/
Directory of slot2#flash:/diagfile
0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log
1048576 KB total (38812 KB free)
3. Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)

4
Collecting operating statistics
You can collect operating statistics by saving the statistics to a file or displaying the statistics on the
screen.
When you collect operating statistics, follow these guidelines:
•Log in to the device through a network or management port instead of the console port, if
possible. Network and management ports are faster than the console port.
•Do not execute commands while operating statistics are being collected.
•Hewlett Packard Enterprise recommends saving operating statistics to a file to retain the
information.
NOTE:
The amount of time to collect statistics increases along with the number of IRF member devices.
To collect operating statistics:
1. Collect operating statistics for multiple feature modules.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N] :
2. At the prompt, choose to save or display operating statistics:
# To save operating statistics, enter yat the prompt and then specify the destination file name.
Save or display diagnostic information (Y=save, N=display)? [Y/N] :y
Please input the file name(*.tar.gz)[flash:/diag_Sysname_20160101-000704.tar.gz] :
Diagnostic information is outputting to flash:/diag_Sysname_20160101-000704.tar.gz.
Please wait...
Save successfully.
<Sysname> dir flash:/
Directory of flash:
...
6 -rw- 898180 Jun 26 2013 09:23:51 diag.tar.gz
1048576 KB total (38812 KB free)
# To display operating statistics on the monitor terminal, enter nat the prompt. (The output from
this command varies by software version.)
Save or display diagnostic information (Y=save, N=display)? [Y/N] :N
===============================================
===============display clock===============
23:49:53 UTC Tue 01/01/2016
=================================================
...
3. Extract and decompress the operating statistics file.
<Sysname> tar extract archive-file diag_Sysname_20160101-000704.tar.gz
Extracting archive flash:/diag_Sysname_20160101-000704.tar.gz Done.
<Sysname> gunzip diag_Sysname_20160101-000704.gz

5
Decompressing file flash:/diag_Sysname_20160101-000704.gz.... Done.
4. Display the content of the operating statistics file.
<Sysname> more diag_Sysname_20160101-000704
===============================================
===============display clock===============
23:49:53 UTC Tue 01/01/2016
=================================================
---- More ----
Troubleshooting hardware
This section provides troubleshooting information for common hardware problems.
NOTE:
This section describes how to troubleshoot unexpected switch reboot, power module failure, and fan
tray failure. To troubleshoot ports, see "Troubleshooting ports."
Unexpected switch reboot
Symptom
The switch reboots unexpectedly when it is operating.

6
Troubleshooting flowchart
Figure 1 Troubleshooting unexpected switch reboot
Solution
To resolve the problem:
1. Verify that you can access the CLI after the switch reboots.
{If you can access the CLI, execute the display diagnostic-information command to
collect operating information.
{If you cannot access the CLI, go to step 2.
2. Verify that the system software image on the switch is correct.
Connect to the switch through the console port and restart the switch. If BootWare reports that
a CRC error has occurred or that no system software image is available, perform the following
steps:
Unexpected switch reboot
Can you
access the CLI?
Collect operating
information Reload the system software image
Yes
No
Resolved?
End
Contact the support
Yes No
Yes
No
Is the system software
image correct?

7
a. Use the BootWare menu to reload the system software image.
b. Configure it as the current system software image.
3. If the problem persists, contact H3C Support.
Operating power module failure
Symptom
A trap or log is generated indicating that an operating power module is faulty.
Solution
To resolve the problem:
1. Execute the display power command to display power module information.
<H3C>display power
Slot 3:
Input Power: 301(W)
PowerID State Mode Current(A) Voltage(V) Power(W) FanDirction
1 Absent -- -- -- -- --
2 Absent -- -- -- -- --
3 Absent -- -- -- -- --
4 Normal AC 24.91 12.10 301 PowerToPort
If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to
step 3.
2. Remove and reinstall the power module to make sure the power module is installed securely.
Then, execute the display power command to verify that the power module has changed to
Normal state. If the power module remains in Absent state, replace the power module.
3. When the power module is in Fault state, do the following:
a. Verify that the power module is connected to the power source securely. If it has been
disconnected from the power source, connect the power source to it.
b. Determine whether the power module is in high temperature. If dust accumulation on the
power module causes the high temperature, remove the dust. Then remove and reinstall
the power module. Execute the display power command to verify that the power module
has changed to Normal state. If the power module remains in Fault state, go to step c.
c. Install the power module into an empty power module slot. Then execute the display power
command to verify that the power module has changed to Normal state in the new slot. If
the power module remains in Fault state, replace the power module.
4. If the problem persists, contact H3C Support.

8
Newly installed power module failure
Symptom
A trap or log is generated indicating that a newly installed power module is faulty.
Solution
To resolve the problem:
1. Execute the display power command to display power module information.
<H3C>display power
Slot 3:
Input Power: 301(W)
PowerID State Mode Current(A) Voltage(V) Power(W)
1 Absent -- -- -- -- --
2 Absent -- -- -- -- --
3 Absent -- -- -- -- --
4 Normal AC 24.91 12.10 301 PowerToPort
If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to
step 3.
2. When the power module is in Absent state, do the following:
a. Remove and reinstall the power module to make sure the power module is installed
securely. Then execute the display power command to verify that the power module has
changed to Normal state. If the power module remains in Absent state, go to step b.
b. Remove and install the power module into an empty power module slot. Then execute the
display power command to verify that the power module has changed to Normal state in
the new slot. If the power module remains in Absent state, go to step 4.
3. Remove and install the power module into an idle power module slot. Then execute the display
power command to verify that the power module has changed to Normal state in the new slot.
If the power module remains in Fault state, go to step 4.
4. If the problem persists, contact H3C Support.
Fan tray failure
Symptom
A trap or log indicates that a fan tray is faulty, or the display fan command shows that a fan tray is
not in Normal state.

9
Solution
To resolve the problem:
1. Execute the display fan command to display the operating states of the fan tray.
[H3C]display fan
Slot 3:
Fan 1:
State : FanDirectionFault
Airflow Direction: Power-to-port
Prefer Airflow Direction: Port-to-power
Fan 2:
State : FanDirectionFault
Airflow Direction: Power-to-port
Prefer Airflow Direction: Port-to-power
Fan 3:
State : FanDirectionFault
Airflow Direction: Power-to-port
Prefer Airflow Direction: Port-to-power
{If the fan tray is in FanDirectionFault state, the airflow direction of the fan tray is not as
configured. Replace the fan tray with a fan tray that has the same airflow direction as the
equipment room, or use the fan prefer-direction command to change the preferred airflow
direction.
{If the fan tray is in Absent state, go to step 2.
{If the fan tray is in Fault state, go to step 3.
2. Remove and reinstall the fan tray to make sure the fan tray is installed securely. Then execute
the display fan command to verify that the fan tray has changed to Normal state. If the fan tray
remains in Absent state, replace the fan tray.
3. Execute the display environment command to display temperature information. If the
temperature continues to rise, put your hand at the air outlet to feel if air is being expelled out of
the air outlet. If no air is being expelled out of the air outlet, remove and reinstall the fan tray.
Then execute the display fan command to verify that the fan tray has changed to Normal state.
If the fan tray remains in Fault state, replace the fan tray.
You must make sure the switch operating temperature is below 60°C (140°F) while you replace
the fan tray. If a new fan tray is not readily available, power off the switch to avoid damage
caused by high temperature.
4. If the problem persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting the hardware.
Command Description

10
Command Description
dir Displays information about files and directories.
display boot-loader Displays current configuration files and system software
images.
display environment Displays temperature information.
display fan Displays the operating states of the fan tray.
display logbuffer Displays the state of the log buffer and the log information in
the log buffer.
display power Displays power module information.
fan prefer-direction slot slot-number
{ power-to-port |port-to-power }Specifies the preferred airflow direction.
Troubleshooting ACL
This section provides troubleshooting information for common problems with ACLs.
ACL application failure with an error message
Symptom
The system fails to apply a packet filter or an ACL-based QoS policy to the hardware. It also displays
the "Reason: Not enough hardware resource" message.
Solution
To resolve the problem:
1. Execute the display qos-acl resource command, and then check the Remaining field for ACL
resources insufficiency.
If this field displays 0, the ACL hardware resources are exhausted.
2. To free hardware resources, delete unnecessary ACLs.
3. If the problem persists, contact H3C Support.
ACL application failure without an error message
Symptom
The system applies a packet filter or an ACL-based QoS policy to the hardware. However, the ACL
does not take effect.

11
Troubleshooting flowchart
Figure 2 Troubleshooting ACL application failure
Solution
Choose a solution depending on the module that uses the ACL.
ACL used in a QoS policy
To resolve the problem when theACL is used in a QoS policy:
1. Verify that the QoS policy is configured correctly:
a. Use one of the following commands to check the QoS policy for configuration errors,
depending on the policy application destination:
Destination Command
Interface display qos policy interface
VLAN display qos vlan-policy
Global display qos policy global
Control plane display qos policy control-plane slot slot-number
b. If the QoS policy does not contain a class-behavior association, associate the traffic
behavior with the traffic class.

12
c. If the QoS policy contains a class-behavior association, execute the display traffic
classifier user-defined command and the display traffic behavior user-defined
command to check for traffic class and behavior configuration errors, respectively.
−If they are configured incorrectly, reconfigure them.
−If they are configured correctly, go to step 2.
2. Verify that the ACL is configured correctly.
Execute the display acl command to check whether the ACL is configured correctly.
{If the ACL is configured incorrectly, reconfigure it.
{If the ACL is configured correctly, go to step 3.
3. If the problem persists, contact H3C Support.
ACL used in a packet filter
To resolve the problem when theACL is used in a packet filter:
1. Verify that the packet filter is configured correctly.
Execute the display packet-filter command to check whether the packet filter is configured
correctly.
{If there are any configuration errors, reconfigure the packet filter.
{If there is no configuration error, go to step 2.
2. Verify that the ACL is configured correctly.
Execute the display acl command to check whether the ACL is configured correctly.
{If the ACL is configured incorrectly, reconfigure it.
{If the ACL is configured correctly, go to step 3.
3. If the problem persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting ACLs.

13
Command Description
display acl Displays configuration and match statistics for ACLs.
display diagnostic-information Displays operating statistics for multiple feature modules in the
system.
display packet-filter Displays whether an ACL has been successfully applied to an
interface for packet filtering.
display qos-acl resource Displays QoS and ACL resource usage.
display qos policy control-plane Displays information about the QoS policies applied to the
specified control plane.
display qos policy global Displays information about global QoS policies.
display qos policy interface Displays information about the QoS policies applied to an
interface or to all interfaces.
display qos policy user-defined Displays user-defined QoS policies.
display qos vlan-policy Displays information about QoS policies applied to VLANs.
display traffic classifier user-defined Displays traffic class configuration.
display traffic behavior user-defined Displays traffic behavior configuration.
Troubleshooting IRF
This section provides troubleshooting information for common problems with IRF.
IRF fabric setup failure
Symptom
An IRF fabric cannot be set up.

14
Troubleshooting flowchart
Figure 3 Troubleshooting IRF fabric setup failure
Member ID unique?
IRF port bindings
or physical IRF connections
correct?
Assign a unique member
ID to each member
device
Modify IRF port bindings
or reconnect physical
interfaces
Are specific settings same
across member devices? Modify the settings to be the same
No
Yes
Resolved?
No Yes
Yes No
Resolved?
No
Yes No
Yes
Correct
transceiver modules or cables
used? Resolved?
No Yes
Yes No
Upgrade software to the
same version in the fabric Resolved?
Yes
No
No
Yes
Same software version?
IRF links up? Resolved?
No Yes
Yes
No
Replace with correct
cables or transceiver
modules
Bring up the IRF links or
activate IRF port
configuration
IRF setup failure
Number of members fewer
than the upper limit? No You cannot add
additional devices to the
IRF fabric or complete
IRF merge
Yes
Resolved? Yes
No
Contact the support End

15
Solution
To resolve the problem:
1. Verify that the number of member devices does not exceed the upper limit (10).
If you are adding a new member device to an existing IRF fabric or merging IRF fabrics, use the
display irf command to identify the number of member devices in the IRF fabrics. If the total
number of member devices exceeds the upper limit, the IRF setup will fail.
2. Verify that the member ID of each member device is unique:
a. Execute the display irf command to view the member ID of each member device.
b. Use the irf member renumber command to assign a unique member ID to each member.
−If you are adding a new member device to an existing IRF fabric, assign the member
device a member ID that is not being used in the IRF fabric.
−If you are merging IRF fabrics, make sure each member device in these IRF fabrics has
a unique member ID.
3. Verify that the IRF port bindings and physical IRF link connections are correct:
a. Execute the display irf configuration command, and check the IRF-Port1 and IRF-Port2
fields for IRF port bindings.
b. Verify that the physical interfaces bound to IRF ports are IRF capable. You can use
QSFP28 ports on the front panel of the S9820-64H switch as IRF physical interfaces. The
10-GE or 25-GE breakout interfaces of a QSFP28 port cannot be used as IRF physical
interfaces. If there are binding errors, reconfigure the IRF port bindings.
c. Verify that the IRF physical interfaces are correct connected. When you connect two
neighboring IRF members, you must connect the physical interfaces of IRF-port 1 on one
member to the physical interfaces of IRF-port 2 on the other.
4. Verify that the correct transceiver modules and cables are used:
{Use QSFP28 transceiver modules and fibers to connect IRF physical interfaces for a
long-distance connection.
{Use QSFP28 AOC or DAC cables to connect IRF physical interfaces for a short-distance
connection.
IMPORTANT:
Except the above listed transceiver modules and fibers or cables, do not use any other
transceiver modules and fibers or cables to connect IRF physical interfaces on the switch
series.
If you are using transceiver modules and fibers, verify that the transceiver modules at the two
ends of an IRF link are the same type. If the transceiver modules are not the same type, replace
them to be the same type.
5. Verify that all IRF links are up:
a. Execute the display irf topology command, and then check the Link field.

16
−If the Link field for each IRF port does not display DOWN, go to step 6.
−If the Link field for an IRF port displays DOWN, go to step b.
b. Execute the display irf link command, and then check the Status field of the physical
interfaces bound to the IRF port.
−If the field displays DOWN or ADM (administratively down) for all the physical interfaces,
remove the link failures or use the undo shutdown command to bring up the
administratively down physical interfaces.
−If the field displays UP for at least one of the physical interfaces, go to step c.
c. Save the configuration, and then execute the irf-port-configuration active command in
system view to activate the IRF port configuration.
IMPORTANT:
Activating IRF port configuration requires a reboot. To prevent configuration loss, you must
save the configuration before you execute the irf-port-configuration active command.
6. Verify that all member devices use the same software version:
a. Execute the display version command to identify the software version of each member
device.
b. Upgrade the software of all member devices to the same version.
NOTE:
Typically, the irf auto-update enable command can automatically synchronize a member
device with the software version of the master device. However, the synchronization might fail
when the gap between the software versions is too large. For more information, see the release
notes.
7. Execute display commands to verify that all member devices use the same settings for the
following features:
{System operating mode (set by using the system-working-mode command).
{Hardware resource mode for the MAC address table,ARP and ND tables, and routing
tables (set by using the hardware-resource switch-mode command).
{Enhanced ECMP mode (set by using the ecmp mode enhanced command).
{Support for the IPv6 routes with prefixes longer than 64 bits (set by using the
hardware-resource routing-mode ipv6-128 command).
{Enabling status of packet loss prevention for OpenFlow forwarding (set by using the
openflow lossless enable command).
{VXLAN hardware resource allocation mode (set by using the hardware-resource vxlan
command).
8. If the problem persists, contact H3C Support.

17
Related commands
This section lists the commands that you might use for troubleshooting IRF.
Command Description
display irf Displays IRF fabric information, including the member ID, role, priority,
bridge MAC address, and description of each IRF member.
display irf configuration Displays basic IRF settings, including the current member ID, new member ID, and physical interfaces bound to the IRF ports on each IRF
member device. The new member IDs take effect at reboot.
display irf link Displays IRF link information.
Use this command to verify that each IRF port has a minimum of one
physical interface in up state.
display irf topology Displays the IRF fabric topology, including the member IDs, IRF port
state, and adjacencies of IRF ports.
display version Displays system version information.
irf-port-configuration active Activates IRF configuration on IRF ports.
Troubleshooting Ethernet link
aggregation
This section provides troubleshooting information for common problems with Ethernet link
aggregation.
Link aggregation failure
Symptom
Some member ports fail to be placed in Selected state, and link aggregation does not operate
correctly.