Hitachi CB 520H A1 User Manual page 515

Logical partitioning manager, compute blade 500 series
Hide thumbs Also See for CB 520H A1:
Table of Contents
Timestamp Module Level System event log Message
------------------- ------ ------- -----------------------------
yyyy-mm-dd hh:mm:ss PX Info 007B D2 7400 32 37XX 39FFFFFF An error was
detected in H/W agent.
This appears only when 37XX 39FFFFFF (XX depends on the LPAR number) is
output.
5
When a guest OS enables promiscuous mode to VF NIC, at tcpdump startup for
.
example, the following messages may appear in /var/log/messages and in the
system event log if SIMT log monitor is running. They do not affect the guest OS
operation.
[/var/log/messages]
be2net 0000:XX:XX.X: opcode 34-1 failed:status 3-8
XX:XX.X: Bus: Dev. Func
[System event log]
Timestamp Module Level System event log Message
------------------- ------ ------- -----------------------------
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 adaptive-rx off
/sbin/ethtool -C eth rx-usecs 128
Specify a network device name of target VF NIC in "eth".
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.
Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide
Item
Setting Item Catalogue
Support (version)
Table A-6 Setting value
A-22.
A-21

Hide quick links:

Table of Contents
loading

Table of Contents