Sponsored Content
Operating Systems AIX DUAL VIOS & Client LPAR hangs at 25b3 Post 302395652 by kah00na on Tuesday 16th of February 2010 02:46:40 PM
Old 02-16-2010
I had a similar problem and below is how I was able to finally get it fixed. We had two vio servers as well.

Shutdown vio2
Boot up the LPAR with only vio1 connection
Remove the non-rootvg disks from the LPAR that is unable to boot
Copy vio2's HMC profile to "vio2_no_fiber_cards"
Remove the fiber cards from vio2's "vio2_no_fiber_cards" profile
Boot up vio2 from the "vio2_no_fiber_cards" profile so that it boots with no fiber cards.
On vio2, remove the non-rootvg VTDs for the LPAR. They will be in the defined state.
Shutdown vio2
Boot up vio2 from the "vio2_normal" profile so the fibercards are back in the game
Verify that the disks are all back with the correct hdisk numbers (compare against vio1)
Verify that all the other VTDs (virtual target devices) are still there and now "Available" (lsmap –all)
Re-create the LPAR's VTDs (the one that was getting the 25b3 error)
Run cfgmgr on the LPAR and verify it can see the paths (lspath) through vio2.
Try and reboot the LPAR and see if it can come back up.
After a successful reboot, call vioc2 good

To summarize... some how the vio2 server's mapping got messed up. By booting the vio2 server with no fibercards, I could remove the then "defined" disk mappings and the disks without messing anything up. I then rebooted vio2 with fibercards and in the process of doing so, the vio2 server "refound" the disks. I re-created the VTD mappings on the vio2 server, then ran cfgmgr on the LPAR and then the problem went away. I was able to see both paths again with "lspath" and was able to reboot the LPAR with no hangups.

Last edited by kah00na; 02-16-2010 at 04:10 PM..
 

10 More Discussions You Might Find Interesting

1. AIX

Setting Dual Ip address on LPAR AIX 5.3

Hi Guys, Can somebody help me how to add and activate addtional ip address on AIX. My server is IBM p5-570 i already set ipadress on ent1 ent0 -- 192.168.206.105 ( default ) ent1 -- 192.168.0.89 (additional) i can ping from outside to 192.168.0.89 but i can not telnet or ftp. for... (6 Replies)
Discussion started by: cahyo3074
6 Replies

2. AIX

Problem mapping LUN disk from VIOS to the LPAR

Hello guys, It would be so nice of you if someone can provide me with these informations. 1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies

3. AIX

VIOS to lpar Mapping

Hello, I have created mapping of 2 virtual adapters for Lpars using following command: mkvdev -vdev ipanalyzerlv1 -vadapter vhost11 mkvdev -vdev ipanalyzerlv -vadapter vhost13 The above two commands were succesfull but when I want to map the third virtual device to the same Lpar than... (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies

4. AIX

What's the difference between VIOS and LPAR?

Hi All, Besides the licenses on VIO and LPAR. What's the main difference with the two? I have installed VIO, my manager told me so, because it's like a free hypervisor but I never installed LPAR before. How do you install it? And if you can give more info on the two, that would be great. ... (5 Replies)
Discussion started by: itik
5 Replies

5. AIX

List LPAR from VIOS

Hi guys, does anyone know how to get a list of the LPAR running on VIOS? Thanks! (5 Replies)
Discussion started by: cecco16
5 Replies

6. AIX

VIOS LPAR Error 0518

I am trying to install AIX 5.3 on one of the LPARs through VIOS but I get this error 0518 Reference Code Selection 0518 (Time stamp: 12/18/12 12:10:20 AM UTC) Starting kernel (Time stamp: 12/18/12 12:10:15 AM UTC) AIX is starting. (Time stamp: 12/18/12 12:10:15 AM... (10 Replies)
Discussion started by: filosophizer
10 Replies

7. AIX

Moving VIOS, LPAR's, HMC to different subnet

Hi, Just joined to new company with one Power 720 Express (8202-E4C) server and have no much experience with IBM systems. I am trying to move everything I mentioned to different subnet as required by customer contract (currently sitting on same subnet as company lan). Access to this subnet will... (8 Replies)
Discussion started by: spricer
8 Replies

8. AIX

VIOS: Extend virtual disk assigned to running lpar?

Hello, VIOS 2.2.1.4 using IVM. I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user. Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Discussion started by: j_aix
2 Replies

9. UNIX for Advanced & Expert Users

Unable to install client AIX LPAR to vscsi hdisk provided from VIOS

Hi everybody, I have Power5 server with 4 internal hdisks each of 70Gb. VIOS server was installed via Virtual I/O Server Image Repository on the HMC. HMC release - 7.7.0 VIOS rootvg installed on 2 disk(these disks merged to one storage pool during VIOS install process),and 2 others hdisks... (2 Replies)
Discussion started by: Ravil Khalilov
2 Replies

10. AIX

Chef client on VIOs? How do you manage your VIO configs?

I know the VIOs are generally to be treated as an appliance and one should never drop down to oem_setup_env. In reality however, oem is a very useful tool to get the job done. So that leads me into the question of using the Chef client on a VIO. Currently a big push to manage all our *nix... (4 Replies)
Discussion started by: RecoveryOne
4 Replies
IXL(4)							   BSD Kernel Interfaces Manual 						    IXL(4)

NAME
ixl -- Intel XL710 Ethernet 40Gb Base driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device ixl To load the driver as a module at boot time, place the following lines in loader.conf(5): if_ixl_load="YES" DESCRIPTION
The ixl driver provides support for PCI Express adapters or LOMs in the XL710 Family of ethernet devices. The driver supports Jumbo Frames, TX/RX checksum offload, TCP segmentation offload (TSO), Large Receive Offload (LRO), VLAN tag insertion/extraction, VLAN checksum offload, VLAN TSO, and Receive Side Steering (RSS), all for both IPv4 and IPv6. For further hardware information and questions related to hardware requirements, see http://support.intel.com/. Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 9706. Offloads are also controlled via the interface, for instance, checksumming for both IPv4 and IPv6 can be set and unset, TSO4 and/or TSO6, and finally LRO can be set and unset. For more information on configuring this device, see ifconfig(8). HARDWARE
The ixl driver supports these SFP+ Pluggable Optics: o Intel TRIPLE RATE 1G/10G/40G QSFP+ SR (bailed) E40GQSFPSR o Intel TRIPLE RATE 1G/10G/40G QSFP+ SR (bailed) E40GQSFPLR The ixl driver supports 10Gb and 1Gb Ethernet adapters with SR Modules: o Intel DUAL RATE 1G/10G SFP+ SR (bailed) FTLX8571D3BCV-IT o Intel DUAL RATE 1G/10G SFP+ SR (bailed) AFBR-703SDZ-IN2 The ixl driver supports 10Gb and 1Gb Ethernet adapters with LR Modules: o Intel DUAL RATE 1G/10G SFP+ LR (bailed) FTLX1471D3BCV-IT o Intel DUAL RATE 1G/10G SFP+ LR (bailed) AFCT-701SDZ-IN2 Note that X710/XL710 Based SFP+ adapters also support all passive and active limiting direct attach cables that comply with SFF-8431 v4.1 and SFF-8472 v10.4 specifications. LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.ixl.enable_msix Allows one to enable/disable MSIX, thus forcing MSI instead. hw.ixl.ringsz Set the number of descriptors in the rings, note that this changes BOTH the TX and RX rings, they cannot be set independly. hw.ixl.max_queues Set the number of queues (each a TX/RX pair) for the port, this allows one to override the autocalculation if its set to 0. hw.ixl.dynamic_rx_itr The dynamic RX interrupt control, set to 1 to enable. hw.ixl.dynamic_tx_itr The dynamic TX interrupt control, set to 1 to enable. hw.ixl.rx_itr The RX interrupt rate value, set to 8K by default. hw.ixl.tx_itr The TX interrupt rate value, set to 4K by default. SYSCTL PROCEDURES
hw.ixl.fc Allows one to set the flow control value. A value of 0 disables flow control, 3 enables full, 1 is RX, and 2 is TX pause. hw.ixl.advertise_speed Allows one to set advertised link speeds, this will then cause a link renegotiation. With the appropriate adapter this can cause a link at 10GB, 1GB, or 100MB. hw.ixl.current_speed This is a display of the current setting. hw.ixl.fw_version This is a display of the Firmware version. Interrupt Storms It is important to note that 40G operation can generate high numbers of interrupts, often incorrectly being interpreted as a storm condition in the kernel. It is suggested that this be resolved by setting: hw.intr_storm_threshold: 0 SUPPORT
For general information and support, go to the Intel support website at: http://support.intel.com/. If an issue is identified with this driver with a supported adapter, email all the specific information related to the issue to <freebsd@intel.com>. SEE ALSO
arp(4), netintro(4), ng_ether(4), vlan(4), ifconfig(8) HISTORY
The ixl device driver first appeared in FreeBSD 10.1. AUTHORS
The ixl driver was written by Jack Vogel <jfv@FreeBSD.org> and Eric Joyner <ricera10@gmail.com>. BSD
January 14, 2015 BSD
All times are GMT -4. The time now is 02:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy