Hitachi Compute Blade 500 Series User Manual page 418

yyyy-mm-dd hh:mm:ss PX WARNING 007B D2 7400 32 37XX 34FFFFF An error was
detected
in H/W agent.
This appears only when 37XX 39FFFFFF (XX depends on the LPAR number) is
output.
6 When a VF NIC device is isolated, the following message appears in /var/log/
.
messages. Immediately reboot the guest OS to which the VF NIC device is assigned
to release the isolation.
[/var/log/messages]
clocksource tsc unstable (delta = -8589944970 ns)
7 For RX-ERR RX-DRP RX-OVR and TX-ERR TX-DRP TX-OVR in output results of
.
netstat –i command, a value of the physical port are displayed.
8 This representative value is based on measurement results at Hitachi's environment.
.
Actual throughput value differs depending on measuring environment and measuring
method.
9 Network throughput value may not be get enough when the following situations
.
occur:
- Network traffic of VF NIC is high
- A lot of interrupts occur for a short time, and CPU utilization is high.
Reboot the OS after adding the following commands on "/etc/rc.d/rc.local" file.
(is set automatically when rebooting the OS.)
/sbin/ethtool -C eth<N> adaptive-rx off
/sbin/ethtool -C eth<N> rx-usecs 128
Specify a network device name of target VF NIC in "eth<N>".
10 If a NIC where Emulex Blade Engine 3 is installed and a NIC where Emulex XE104 is
.
installed co-exist, this number is 15 per port for both NICs.
11 When using path redundancy and VLAN, set the values in
.
when using path redundancy and VLAN on page
However, set the same VF NIC to primary devices each LPAR when setting
"fail_over_mac=0".
12 When using inter-LPAR communication with VF NIC, set "fail_over_mac=1" to the
.
bonding option. If not, the inter-LPAR communication may not be available at
switching bonding.
13 Inter-LPAR communications are not available between VF NIC and Shared NIC used
.
the same physical port.
14 You cannot perform Migration between different versions. (both of shut-down mode
.
and concurrent maintenance mode)
15 When you need to execute Force Recovery, shutdown the OS on the LPAR to be
.
deactivated before the execution. If Force Recovery is executed while the LPAR is
running, VF NIC will be unavailable on the OS on the LPAR. To recover VF NIC,
reboot the OS on the LPAR after Force Recovery is completed.
16 Do not specify the TagVLAN setting in the OS of the VF NIC for which Untagged is
.
set.
A-16
Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide
Item
Setting Item Catalogue
Support (version)
Table A-6 Setting value
A-17.