Oracle Dual Port 25 Gb, Руководство пользователя

Страница: 78 / 88

Analyze Why the Link Is Not Up After Back-To-Back Cable Connection (Oracle Solaris x86)
# truss -p
PID
2. Look for NIS , DNS , and network routing outages.
If you find any issues, fix them before proceeding.
3.
View the I/O statistics to ensure that there are no bottlenecks on the disk.
# iostat -xcn 5
If you discover a bottleneck, set the logging to dump to the
/tmp
directory. Then retest to ensure
that the new configuration improved performance.
4.
Use the
vmstat
and the
mpstat
commands to check that none of these conditions
exist:
■
CPU is pegged.
■
CPU is receiving too many interrupts.
■
Memory is low.
■
Page faults are occurring.
■
Contention for resources causes too many spins on mutex (
smtx
).
For more information, refer to the Oracle Solaris
vmstat
(1M) man page or the
mpstat
(1M) man
page.
If the performance issue points to the driver, profile the call stack for
bnxt
by using the
DTrace
script. For more information about the
DTrace
script, go to My Oracle Support .
Related Information
■
“Analyze Why the Device Link Is Missing (Oracle Solaris x86)” on page 75
■
“Recover From a Port Hang (Oracle Solaris x86)” on page 76
■
“Analyze Why the Link Is Not Up After Back-To-Back Cable Connection (Oracle Solaris
x86)” on page 78
■
“Analyze Why Changing the MTU Does Not Correctly Set the Link Property (Oracle
Solaris x86)” on page 79
Analyze Why the Link Is Not Up After Back-To-Back
Cable Connection (Oracle Solaris x86)
1. Ensure that the correct cable type is being used.
See “Adapter Description” on page 32 .
78 Oracle Dual Port 25 Gb Ethernet Adapter User's Guide • September 2017