Technical data

NOTE: These change are not carried over to subsequent reboots of the system. To maintain the
configuration over reboots of the guest, the administrator must edit the guest file, /etc/
rc.config.d/hpigssnconf.
For each igssn device that must have drv_pr disabled, you must construct a block of information
in the hpigssnconf file. For example, if your guest needed to have both lan0 and lan3 disable
drv_pr, you might have:
HP_IGSSN_INTERFACE_NAME[0]=lan0
HP_IGSSN_STATION_ADDRESS[0]=
HP_IGSSN_MTU[0]=
HP_IGSSN_DRV_PR[0]=0
HP_IGSSN_INTERFACE_NAME[3]=lan3
HP_IGSSN_STATION_ADDRESS[3]=
HP_IGSSN_MTU[3]=
HP_IGSSN_DRV_PR[3]=0
7.2.26 Other Issues and Notes
The following list provides additional issues with the Integrity VM V4.2.5 release of which you
should be aware :
• If you modify the MAC address of an interface in the guest, the hpvmstatus command
in the VM Host does not display the current MAC address correctly. There is no fix or
workaround for this problem at this time.
• Just as with physical devices on a network, for communication to occur uninterrupted
between all stations on a LAN segment, the MTUs of all the systems on the LAN segment
or VLAN must match, whether they are physical systems or guests. The VM Host does not
check for MTU mismatches for its guests.
• The lanadmin card specific options that are supported on igssn on the guest are:
— -x:speed,fctrl,cko,type,card_info,stats drv,vmtu,and drv_pr.
— -X:drv_pr_on,drv_pr_off,stats clear
78 Networking Information