This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
See case TS002260514:LPM/HMC does mess up the AIX device names on target VIOS.Especially if using the "vios-virtual-slot-number" on the target VIOSs i would assume the device naming is the same on both. But it is not as we know.
Following a request from a customer about VIOS 3.1 and iSCSI support.https://www.ibm.com/support/knowledgecenter/9223-22H/p9hb1/p9hb1_vios_concepts_iscsi.htmThis webpage is confusing when "limitations" paragraph is read:--Currently, the iSCSI disk...
Code enhancement to handle VIOS Path loss issues during Brocade haReboot - There have been multiple outages experienced in IBM VIO Server(VIOS) managed environment, during storage related events. The haReboot performed on Brocade SAN switches are supposed to be non-disruptive, but in reality they do take a finite amount of time. In VIO managed environments, this has sometimes resulted in impact and affected availability. During a haReboot the fabric services are not available and hence when the VIOS queries the Name server on the switch, it may not get the desired response due to the haReboot in progress. This results in the VIOS logging out and attempting to log back in again, resulting in path failures at the VIOS. To prevent the same from happening, the VIOS code can be updated to include an appropriate time interval that kicks in as and when the haReboot is in progress. The VIOS will then wait for this interval and pause any activity, before querying the name server again. The assumption is that the haReboot RSCN notification is sent correctly by the Brocade switches and received by the VIO servers. If not, then this can be worked out jointly by Brocade and IBM, to prevent outages in the future. The referenced Support Case has additional information.
among all the different vendor servers, the IBM VIOS managed AIX server environments seem to be susceptible and have experienced outages as and when haReboot is performed.
'VIOS/AIX notify client partitions that a VIOS dump is about to occur
VIOS/AIX needs to somehow notify client partitions that a VIOS dump is going to occur and allow the clients to immediately close their connections so that they can route to another VIOS server for processing during the dump See customer outage: TS...
In powerVM,the transmit speed of the virtual ethernet adapter is too low ,which is usting the 10GB physical adapter
Dear IBM， we encounter a performance issue in VIOS and VIOC.we found we have nothing to do to improve the virtual network adapter transmit speed,based on the 10GB physical adapter.BUT in our datacenter ,there is 140+ 780 &880 facing the same i...
PowerVM VIOS, the Shared Ethernet Adapter device (SEA) needs support for IEEE802.3 Ethernet frame type
The SEA device in all VIOS releases is only designed for handling the EthernetV2 frame type with TCP/IP checksum offloading and the largesend/large_receive features.If a VIO client LPAR (IBMi or AIX or Linux) is configured to use IP interfaces wit...
Better troubleshooting when HMC doesn't display devices like disks when it should.
When the CMDB on the VIOS server is wrong, then the HMC simply does not display what you should see, and you have zero insight into why. We had issues with disks, missing UUIDs, or other errors. There should be a command, maybe a little more refin...
NFS based files as BackingDevices for vSCSI mapping
Allow files located on NFS shares mounted on the VIOs to be used as BackingDevice for vSCSI mapping (similar to VMware data store). Until now file based BackingDevices are only possible using StoragePools or ISOs.
almost 3 years ago
in PowerVM VIOS
Not under consideration
Do not place IBM confidential, company confidential, or personal information into any field.