User`s guide

Chapter XIX. Appendix
Chelsio T5/T4 Unified Wire For Linux Page 448
1. Troubleshooting
Cannot bring up Chelsio interface
Make sure you have created the corresponding network-script configuration file as stated in
Section 5.2 of Cheslsio Unified Wire chapter (Click here). If the file does exist, make sure the
structure and contents are correct. A sample is given in Section 5.1 of Chelsio Unified Wire
chapter (Click here). Another reason may be that the IP address mentioned in the configuration
file is already in use on the network.
Cannot ping through Chelsio interface
First, make sure the interface was successfully brought up using ifup ethX (where ethX is your
interface) and that it is linked to an IP address, either static or obtained through DHCP.
You then may want to check whether the destination host (i.e. the machine you are trying to
ping) is up and running and accepts ICMP requests such as ping. If you get a return value of 0
when doing a cat /proc/sys/net/ipv4/icmp_echo_ignore_all on the remote host that
means it is configured to reply to incoming pings. Change ipv4 to ipv6 in the path if you are
using IPv6. Note that this is a Linux-only tip.
If you have more than one interface wired to the network, make sure you are using the right one
for your outgoing ping requests. This can be done by using the -I option of the ping command,
as shown in the following example:
[root@host]# ping -I eth1 10.192.167.1
Where 10.192.167.1 is the machine you want to ping.
Configuring firewall for your application
In many cases the firewall software on the systems may prevent the applications from working
properly. Please refer to the appropriate documentation for the Linux distribution on how to
configure or disable the firewall.
FCoE link not up
Always enable LLDP on the interfaces as FCoE link won’t come up until and unless a
successful LLDP negotiation happens.