HP Integrity Virtual Machines 4.2.5 - HP Business Support Center

More documents

Recommendations

Info

NOTE: The lanadmin command is deprecated and will be removed in a future HP-UX release. HP recommends that you use the nwmgr command to perform all network interface-related tasks. The following table shows the nwmgr command that performs the same task as the lanadmin command: Task Check the status of the transmit CKO. Legacy Command # lanadmin -x cko 4 Hardware TCP/UDP (IPv4) transmit checksum offload is currently enabled. Hardware TCP/UDP (IPv4) receive checksum offload is currently disabled. nwmgr Command # nwmgr -g -A all -c lan4 | grep Checksum Transmit Checksum Offload=Off Receive Checksum Offload=On In this example, the VLANs are configured over the vswitch vmlan4. This vswitch is created on PPA 4 on the VM Host. The following table shows the nwmgr command that performs the task as the lanadmin command: Task Turn off CKO on PPA 4 by entering this command on the VM Host. Legacy Command # lanadmin -X send_cko_off 4 Hardware TCP/UDP (IPv4) transmit checksum offload is currently disabled. nwmgr Command # nwmgr -s -A tx_cko=off -c 4 lan2 current values: Transmit Checksum Offload=Off 7.2.21 Do Not Turn on TSO on the VM Host and on HP-UX Guests When Using VIO TCP Segmentation Offload (TSO) is turned off by default in HP-UX. HP recommends that you leave it turned off on both the VM Host system and on HP-UX guests if you are using the VIO interface. This applies to both the virtual network interface cards in the guest and any physical network interface cards in the VM Host that are used by vswitches. When TSO is enabled, guest networks are interrupted. Note that this restriction applies to VIO interfaces. NOTE: The lanadmin command is deprecated and will be removed in a future HP-UX release. HP recommends that you use the nwmgr command to perform all network interface-related tasks. The following table shows the comparable nwmgr command to use to replace the lanadmin command: Task Verify whether TSO is turned on. n is the VM Host interface, as displayed by the hpvmnet command. Verify that TSO is on for lan0. 76 Networking Information Legacy Command # lanadmin -x vmtu n # lanadmin -x vmtu 0 Driver/Hardware supports TCP Segmentation Offload, Current VMTU = 32160 nwmgr Command # nwmgr -g -A vmtu -c lann # nwmgr -g -A vmtu -c lan0 lan0 current values: Virtual MTU = 32160 TCP Segmentation Offload is now disabled.
Task Turn TSO off on lan0. Allow the TSO attribute change along with the rest of the lan attributes to be perserved between system reboots by saving the current attributes to the lan configuration file. 7.2.22 Restarting Vswitches Legacy Command It is necessary to restart the vswitch when: # lanadmin -X vmtu 0 0 Virtual MTU is set to 0 Manually edit the configuration file in /etc/rc.config.d, or use SAM interface. See the Ethernet Support Guide for details. • You replace the physical network card associated with the vswitch. nwmgr Command # nwmgr -s -A vmtu=0 -c lan0 lano current values: New Virtual MTU=0 # nwmgr -s -c lan0 -A all --sa -fr cu • You change a VM Host IP address associated with the vswitch's network interface card. • You change the network interface characteristics on the VM Host; for example, by using the nwmgr command to change checksum offloading (CKO). • You notice that there is no communication from an avio_lan interface to a lan interface after booting the guest(s) while the vswitch is down. For information about how to restart vswitches, see the HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration manual. When you restart a vswitch, it is not necessary to restart the guests using the vswitch. 7.2.23 Guest AVIO Interface Behavior The following list describes the guest AVIO interface behavior when guest boots while vswitch is down or resetting: • If you boot a guest while the vswitch is not up, AVIO interfaces associated with the vswitch might not be claimed in the guest. For example, this might occur if the guest is booted prior to booting the vswitch or if the corresponding network interface on the VM Host is not cabled. If you encounter this problem, first fix the vswitch state (that is, ensure that hpvmnet displays its state as Up), and then execute the ioscan command in the guest. These actions will claim the AVIO interfaces. • After ioscan claims the AVIO devices in the guest, you might notice that the AVIO devices cannot communicate with another VIO guest interface configured on the same vswitch. When this occurs, invoke the hpvmnet -r option on the vswitch to restore connectivity. • If the vswitch is in an unstable state while the guest is booting, guest AVIO interfaces might fail initialization and move to the DOWN state (as displayed by thelanscan command). When this occurs, first ensure that the vswitch enters a stable state, then reset the guest interface using nwmgr. 7.2.24 AVIO LAN Devices Not Claimed by Guest with DOWN vswitch at Boot Time In addition to running ioscan, you must re-run the necessary network startup scripts, so that IP addresses can be reconfigured on the network interface cards (NICs). For example: /sbin/rc2.d/S340net start /sbin/rc2.d/S340net-ipv6 start 7.2.25 Do Not Use TCP Software Packet Reassembly in IGSSN Driver For AVIO, there have been problems with TCP Software Packet reassembly in the igssn driver in a guest HP-UX image. For this release, do not enable it on a guest. By default, software packet 7.2 Known Issues and Information 77
Page 1 and 2:
HP Integrity Virtual Machines 4.2.5
Page 3 and 4:
Contents About This Document.......
Page 5 and 6:
4.3.2 Known Issues and Information.
Page 7 and 8:
7.2.3 Known Limitation on OpenVMS G
Page 9 and 10:
11.9 Network Interface Support.....
Page 11 and 12:
About This Document The HP Integrit
Page 13 and 14:
Publication Number T2767-90076 T276
Page 15 and 16:
1 Introduction Thank you for instal
Page 17 and 18:
Table 1 Guest and VM Host Support (
Page 19 and 20:
2 Installation Notes This chapter c
Page 21 and 22:
• You might receive a read error
Page 23 and 24:
2.3.10 Failures in Key Applications
Page 25 and 26: Serviceguard, as documented in the
Page 27 and 28: to properly run or even boot. If th
Page 29 and 30: Table 3 VM Host Patches (continued)
Page 31 and 32: Table 3 VM Host Patches (continued)
Page 33 and 34: 11i v2 0505 or later 11i v2 Intel I
Page 35 and 36: Table 5 HP-UX Guest Patches (contin
Page 37 and 38: 3 Creating Virtual Machines This ch
Page 39 and 40: 4 Installing Guests This chapter de
Page 41 and 42: • After the automatic reboot, Win
Page 43 and 44: [my_guest] vMP> in Insertable Guest
Page 45 and 46: • HP-UX 11i v2: PHCO_40685 and PH
Page 47 and 48: • Red Hat Enterprise Linux 4 Inst
Page 49 and 50: 4.3.2.5 Before Installing the SUSE
Page 51 and 52: Use ^ and v to change option(s). Us
Page 53 and 54: ***********************************
Page 55 and 56: 5 Using Integrity VM Commands This
Page 57 and 58: 5.2.6.1 The hpvmdevtranslate Comman
Page 59: hpvmmodify: WARNING (test_duperr):
Page 62 and 63: NOTE: If you add new devices in the
Page 64 and 65: # useradd -r no -g users -s /opt/hp
Page 66 and 67: used by guests but requires users t
Page 69 and 70: 7 Networking Information This chapt
Page 71 and 72: 7.2.2 AVIO LAN Devices Left Unclaim
Page 73 and 74: incorrectly. To help mitigate this
Page 75: By default, Integrity VM makes thre
Page 79 and 80: 8 Storage Information This chapter
Page 81 and 82: GuestAVIOStor: Instance numbers for
Page 83 and 84: 8.2.14 The hpvmmodify Command Fails
Page 85 and 86: -H of the lunpath or tgtpath H/W Pa
Page 87: 1. In the guest, execute rmsf for t
Page 90 and 91: Can't open VM /var/opt/hpvm/uuids/c
Page 93 and 94: 10 Error Logging This chapter conta
Page 95 and 96: 11 Integrity VM Support Policy This
Page 97 and 98: 11.4 HP-UX Guest Support Type of Gu
Page 99 and 100: 1 Intel® Itanium® 2 9000 Series a
Page 101 and 102: 11.8.1 Guest Attached Device Suppor
Page 103 and 104: can be configured with Auto Port Ag
Page 105 and 106: A hpvmhostgdev Manpage 105
Page 107 and 108: -l Lists unused devices that can be
show all

HP Integrity Virtual Machines 4.2.5 - HP Business Support Center

Create successful ePaper yourself

Delete template?

Save as template?