beautypg.com

HP NC532m Dual Port 10GbE Multifunction BL-c Adapter User Manual

Page 13

background image

Installation and configuration 13

WARNING indicates a warning such as too many MACs configured for iSCSI offload.
INFO indicates an informative event such as hp-pbl starting and stopping.
SP is one or more spaces.
DATE is the current date stamp in the format Sat Feb 17 12:54:35 CST 2007.
TEXT is free form text that may or may not exist in every message. Lines that do not start with a tag
are a continuation of the previous line.

The following represent sample text lines.

[INFO] [Thu Feb 10 10:34:15 CST 2007] hp-pbl started - v1.0.0-1.rhel5

[INFO] [Thu Feb 10 12:54:36 CST 2007]

first text line of second info message

second text line of second info message

Troubleshoot known issues for HP port-based Linux iSCSI offload

Complete the following steps to troubleshoot the hp-pbl licensing.

1.

Run the following command in a separate window to monitor the hp-pbl.log file for messages.
tail -f /var/opt/hp/hp-pbl/hp-pbl.log

2.

Run the following command in a separate window to monitor the messages file.
tail -f /var/log/messages

Potential problems, causes and solutions
Problem:
Does not appear to create an iSCSI offloaded connection when configured for offload.
Possible cause:
The initiator needs to be restarted after the transport name is changed for offload, and the bnx2i driver

needs to be reloaded so that the configuration changes are realized. Both of these events occur when hp-

pbl is restarted.
Possible solution:
Run the following command to restart hp-pbl:

/opt/hp/hp-pbl restart

Problem:
Does not appear to create an iSCSI offloaded connection when configured for offload and

/var/log/messages lists the following information:

bnx2i: conn bind, ep=0x... ($ROUTE_HBA) does not belong to hba

$USER_CHOSEN_HBA

Possible cause:
A potential problem with the link layer address to IP address mapping occurs when a server with multiple
network cards is connected to the same network segment. This issue is commonly known as the Arp Flux

Problem.
Possible solution:
Set up the network so that network cards are on separate network segments or broadcast domains.