Recover From a Port Hang (Oracle Solaris)
■
If the interface encounters a soft hang, replumb the device.
Use the ipadm command.
■
If the interface encounters a hard hang, reboot the server.
■
If the interface encounters another hard hang, try to capture the trace information by using
the dtrace command. For example:
# detrace -F -m 'i40e{trace(timestamp)}'
>/tmp/dtrace.out
■
If the server is panicked, retrieve the crash dump in /var/crash.
■
If the interface encountered a hard hang or a panic, file a CR at My Oracle Support.
Attach the last page of the dtrace command output or the crash dump file to the CR.
2.
Check for the driver statistics.
# kstat i40e:* :statistics
3.
Use the following parameters for performance tuning in i40e.conf:
Parameters Description
rx_itr Interval of receive interrupts 0 to 4080, 25 (50 usec) by default .
tx_itr
Interval of transmit interrupts 0 to 4080, 25 (50 usec) by default.
rx_limit_per_intr
Maximum number of packet to receive per interrupt16 ~ 4096, 1024 by
default.
rx_copy_threshold
Packet size to determine bcopy or not during receive0 ~ 9216, 128 by
default.
tx_copy_threshold
Packet size to determine bcopy or not during transmit0 ~ 9216, 128 by
default
Related Information
■
“Analyze Why the Device Link Is Missing (Oracle Solaris)” on page 84
■
“Analyze Slow Network Performance (Oracle Solaris)” on page 86
■
“Analyze Why the Link Is Not Up After Back-To-Back Cable Connection (Oracle
Solaris)” on page 87
■
“Analyze Why Changing the MTU Does Not Correctly Set the Link Property (Oracle
Solaris)” on page 87
Troubleshooting the Adapter (Oracle Solaris) 85
To Next Page
Loading...
General