18–Troubleshooting
Possible Problems and Solutions
252
83840-546-00 E
if you loaded a new driver but have not yet booted, the
modinfo
command will
not show the updated driver information. Instead, you can view the logs to verify
that the proper driver is loaded and will be active upon reboot:
dmesg | grep -i "QLogic" | grep -i "bnx2"
Possible Problems and Solutions
This section presents a list of possible problems and solutions for the components
and categories:
Multi-boot Agent
Problem
: Unable to obtain network settings through DHCP using PXE.
Solution
: For proper operation make sure that the STP is disabled or that portfast
mode (for Cisco) is enabled on the port to which the PXE client is connected. For
instance, set spantree portfast 4/12 enable.
QLASP
Problem
: After physically removing a NIC that was part of a team and then
rebooting, the team did not perform as expected.
Solution
: To physically remove a teamed NIC from a system, you must first delete
the NIC from the team. Not doing this before shutting down could result in
breaking the team on a subsequent reboot, which may result in unexpected team
behavior.
Problem
: After deleting a team that uses IPv6 addresses and then re-creating the
team, the IPv6 addresses from the old team are used for the re-created team.
Solution
: This is a third-party issue. To remove the old team’s IPv6 addresses,
locate the General tab for the team’s TCP/IP properties from your system’s
Network Connections. Either delete the old addresses and type in new IPv6
addresses or select the option to automatically obtain IP addresses.
Problem
: Adding an NLB-enabled 8400/3400 Series adapter to a team may
cause unpredictable results.
Solution
: Prior to creating the team, unbind NLB from the 8400/3400 Series
adapter, create the team, and then bind NLB to the team.
Summary of Contents for FastLinQ 3400 Series
Page 286: ......