Questions Log from aix vug webinar on October 2, 2015 aix featuring Jay Kruemcke & Dave Sheffield
Yüklə 158,49 Kb.
|
|
Questions Log from AIX VUG Webinar on October 22, 2015 AIX 7.2 featuring Jay Kruemcke & Dave Sheffield Q: Url to download the material A: The AIX VUG Wiki is: www.tinyurl.com/ibmaixvug
A: December 6 is the planned GA date Q: Does AIX 7.2 have human readable flags available in commands like Linux does, like "df –h A: The commend syntax for AIX 7.2 is the same as in previous AIX releases Q: Do you plan the same session for PowerHA 7.2 A: No plans to cover PowerHA yet, but if enough people want to see it, I can put it on the schedule Q: do you have to have a "free" disk available for the Alt disk copy A: for live update, yes. That disk will be allocated to the new lpar. Q: are any additional resource are needed to create surrogate LPAR A: it needs CPU and memory to run the workload that will be moved over Q: Currently if the customer has AIX 6.1 Support contract, they do have the ability get the software for updating to AIX 7.1 - Will they be able to update to AIX 7.2 as well under the same support contract A: Yes, clients with AIX 6.1 SWMA can upgrade to AIX 7.1 or AIX 7.2 for no additional charge Q: What if rootvg is already mirrored A: alt disk is possible on a mirrored rootvg Audience Question: Q: so we would need to have an extra disk attached to the server A: Yes
A: not yet. The live kernel replacement only applies to the kernel. it cannot be used for service packs or technology levels at this time Q: What about if we have multibos copy and do not have alt-disk-install as we have all virtual disk only. Would the live udpate still work? A: live update assumes you have a disk that can be given to a new lpar, which will boot and into wich the runninmg lpar will be moved via LPM. I don't think multibos would let you do that, even if its a mirrored multibos rootvg Q: For TL changes, some upgrades like perl will need additional work like perl modules reinstalled. How will that be handled? A: This technology will not support TL upgrades at this time. Q: For TL changes, some upgrades like perl will need additional work like perl modules reinstalled. How will that be handled? A: At the moment, live update only handles interim fixes. Q: According to the latest announcements end of support AIX EE 6.1 is April 30, 2017 and end of support for AIX 7.1 EE is September 30, 2016 (sooner than 6.1). Can you elaborate on it? A: I will later in the preesntation Q: end of service on AIX 6.1 A: April 2017 is the announced end of standard support Q: Support GPFS? A: Nope
A: We intend to expact the capabilities over time.
A: if FW updates are needed, they can be applied as you normally would. If they are disruptive, ie a reboot is required, your live AIX update would be done before or after. Q: we have a p770 running 7.1.0.0 we don't run VIOS would this upgrade work for us? A: Virtualized IO is a hard requirement Q: when 7.2 will be releasing officially? A: December 6 is the planned GA date Q: Is live update only for WPAR or is it for LPAR also ? A: this is for LPARs. No need to use WPARs Q: what about if we are running in a limited amount of available resources like MEM/CPU and the surrogate LPAR can not be created ? A: If yoiu can temporarily reduce resource by other lpars, that might be the way to go. COD or processor pooling may help. Otherwise, you'll have to acquire the resources necessary to execute the update. Q: so if I have a LPAR with 5CPU and 128G memory.. with thte live update do you need to have that much available? A: Yes, you must have the same amount of memory and cpu Q: will this work across servers in an enterprise pool or only on single server A: Single server Q: Support PowerVC now or in future or never support? A: not sure of your question. Live update is orthogonal to PowerVC Q: So No VIOS means no upgrade path to 7.2 at all? A: sorry - No vios means no live update. Updating to AIX 72. still possible using normal methods Q: For the customer who asked"what about possible needed firmware-updates" = I use LPM and then perform the firmware update/reboot - there have been 99.99999% success rate with that approach A: Excellent point. LPM is your friend for dealing with firmware updates Q: what about the compatibility with other products such as TSM and DB2 A: from the point of view of applications, the LPAR didn't change unless they are aware of the LPAR ID Q: what is the tool being displayed? A: it is a tool called swingbench. It creates an Oracle load and does monitoring. Q: Any word on VIO 3? A: Sorry can only discuss that under non-disclosure agreement. Q: Will TL and SP live updates be possible at some point? A: We hope to improve over time. Q: If AIX 7.1 is good for 5years. When is its expected end of server? A: Sorry can only discuss that under non-disclosure agreement. Q: NDA topic means ? A: means it is not announced yet, so we can't talk about it here. Q: what about oracle rack file system A: Oracle RAC already has a non-disruptive update capability so this technology is not targeting RAC or DB3 Purescale Q: 7.2 Benefits for non-VIOS environments? A: Stay tuned Q: With the live update, after the alt-disk-install is kicked off but before the switch over, what will happen to any changes to rootvg (logs, home directories, etc.) Will those be synced or lost? A: this is the reason for the mirrored rootvg on the original -- all rootvg updates will be maintained because the processes will be restarted chrooted on the original rootvg. Q: For how long the workload is paused during migration? A: workload- dependent, but rule of thumb will be 30 seconds for an idle system, and it will increase based on number of processes Q: how much cpu and memoryrequired for surrogate lpar A: same as on the original Q: is there an estimate about how long the workload would be paused during the live update process? A: see above Q: Since it's creating what seems like a direct mirror of the lpar, does this mean I need to have twice the resources of my lpar in order to live update? 1 for the lpar itself, 1 for the surrogate? A: yes, for the duration of the live update. Once the Live Update completes, those cpu and memory resources will be available again Q: Will NIM be able to push these updates. A: yes, fully integrated with NIM Q: I noticed that the VIOS flash cache supported VSCSI. Can flash cache also use NPIV? A: Yes
A: Yes
A: no SP support in initial release, but stay-tuned ... SP/TL support is what's really driving this approach Q: No FCoE support?? A: No
A: VIOS doesn’t support iSCSI currently, so No.
A: not sure I followed that question. Q: Since PowerHA uses "IP over FC" for the SAN heartbeat; is SAN heartbeating being removed for PowerHA ? A: Sorry, not PowerHA expert. Q: Can we do live update if the rootvg is a NAS disk? A: If this means this is a "thin server" model (NFS-mounted root file systems), the answer is no. We can't support that model. Q: Is it correct to assume that Migrating to AIX 7.2 with nimadm is supported from both AIX 6.1 and AIX 7.1 ? A: correct Q: Could you repeat which filesystems need to unmount ? A: Live Update can only support JFS2 or NFS. Anything else would have to be unmounted (GPFS, VxFS, etc) Q: does the black out period depend on the workload of the LPAR? Also how much downtime to expect reasonably? can I take LPM as an example for black out period? A: Mostly answered above. The blackout will be longer than with LPM. Q: You can keep the sam vhostx VIOS slot? A: yes, because of the way we remove half the paths to configure on the surrogate, we can keep everything the same Q: Hi,If we change LparID,Does it affect exsistig VIOS Disk mappings? A: No impact on the VIOS mappings because Live Udpate will create them exactly the same on the surrogate Q: According to Withdrawal Announcement 915-204 it looks like AIX 7.1 is going end of support prior to AIX 6.1?!? So if we are only at 6.1 today, it seems to only make sense to go to 7.2 but concerned about ISV support (Oracle, SAP, etc) A: The old AIX 7.1 Enterprise Edition was withdrawn because it was replaced by a new AIX 7.1 Enterprise Edition. AIX 7.1 has not been withdrawn. You can move to AIX 7.1 Q: If lpar id is changed. How will DLPAR work? A: From the HMC after live update you will see the same partition name, but new id. You would select same partition name, though it will have the new id. From the client lpar, no change Q: what is the minimum resources required? A: same cpu and memory as original. 2 extra disks at a minimum. Q: Is IBM providing temporary CoD for this type of upgrades A: Initial release there is no integration with CoD, so you would have to activate the CoD resources prior to the Live Update and then de-activate after. Q: Are the new Enterprise versions licensed separately? A: Yes
A: I'm not sure about this -- I don't remember exactly how the machine id is constructed (might contain the lpar_id?)
A: no zonng required because we keep the same WWPNs Q: Is this an upgrade from regular 7.1 to 7.1 V1.1? A: Yes. There is a no charge upgrade from the old AIX 7.1 Enterprise Edition to the new AIX 7.1 Enterprise editoin Q: Customer currently has AIX7.1 EE installed with SWMA. Then this customer will automatically entitled with SWMA of AIX 7.1.1 EE. Customer does not need to do anything. Am I right? A: No. Customer needs to do the no charge upgrade to the new AIX 7.1 EE. Different pid from the old AIX EE. Q: If we have AIX 7.1 Enterprise Edition V1.1, is the upgrade to AIX 7.2 Enterprise Edition V1.1 "free"? A: Yes as well as upgrade to the new AIX 7.1 Enterprise Edition Q: Can I upgrade AIX 6.1 standard to 7.1/7.2 standard without charge? A: Yes as long as you maintain SWMA Q: the pausing of the workload... for what applications is this tested and supported. like for WebSphere Java or Oracle or Tivoli.. or MQ A: tricky question ... from an AIX perspective I can't really comment on what support statements various applications will make, especially ISVs. We are driving all apps certifying on 7.2 to also include Live Update testing. Q: So can I do DLPAR to increase CPU, and memory on Surrogate LPAR during lively updating only to speed up update process? A: no, DLPAR would be blocked during the LIve Update itself. Q: NfS 3 and NFS4? A: yes, both NFSv3 and v4 Q: powersc no extra coast if we have enterprise version ? A: Yes. PowerSC is included in AIX EE Q: Please clarify, Big Fix WILL include profiles for PCI and HIPAA? A: No, that is a PowerSC feature (also included in AIX EE) Q: so director is no longer included with the enterprise edition? A: Yes. Director products have been withdrawn and end of service announced. Q: Does the live update network cutover use the NPIV LPM WWN for the new LPAR? And do you end up using the second WWN on the new LPAR afterward? A: We use the same WWPNs. This is different than LPM (which uses the secondary WWPN). Q: can we upgrade from 6100-07 directly to 7.2? A: Yes
Q: Are SR-IOV adapters supported for AIX live update? A: Yes as long as you are using them via the VIOS vNIC. Dedicated adapters are not supported Q: AIX 7.2 will not support FCoE?? A: Yes. It will support fCOE Q: How do you rollback a live update? Is it going to be an live rollback? A: Reboot from the original boot disk Q: Does the storage need to be reserve_policy=no_reserve? A: Not required. Live update will break the reservation and re-establish as necessary if there is one. Q: " tricky question ... from an AIX perspective I can't really comment on what support statements various applications will make, especially ISVs. We are driving all apps certifying on 7.2 to also include Live Update testing." Have you, or will you be testing this with EMR applications like EPIC? A: The ISV team is working with all relevant vendors as they do for any new AIX release.
A: The new mirror becomes old_rootvg. The original becomes the active rootvg on the surrogate because we start all the processes chrooted in to the original rootvg file system rather than the boot rootvg. Q: ok will those methods be published ? and if so whwre? A: sorry, I missed what methods you're referring to? Q: Can you please paste here the link again ? "directordead" link ? A: https://ibm.biz/directordead Q: Is that the flux capacitor ? A: No. The flux capacitor was integrated into the POWER5 cores in 2004 Q: does it suppoer EMC SAN disk - as EMC powermt is have lot of issue with alt_dsk A: EMC storage with AIX MPIO multipathing is certainly supported. We are pushing for PowerPath support as well, but depends on EMC also. Q: so application support LPM like SAP, Oracle, then they should support AIX7.2 live update naturally. No need certification, am I correct? A: From a technical perspective, that is the design point, but of course, I can't say what the ISVs will require. Q: Is big fix going to be a seperate licensed product or is it included in the current/new EE offerings? A: itsa both a sewparate3 product, and included in AIX EE. Q: does the zoning of new virtual adapters in surrogated lpars to SAN need any manual intervention ? A: no manual intervention required Q: Will Python being included in AIX 7.2 as e.g. Perl is for current Releases? A: Not at this time. Python has dependencies on GPL code that are difficult to include in base AIX Q: Live update , is this fully automated process? A: yes
A: No. it’s a no charge upgrade.
A: The intent is to support all ifixes. There may be exceptions, for example if we have to patch live update code itself. Of course, if there is no reboot required for an ifix, then no need to use live update. Q: does all that wiil be mentioned through coming roadshows as SVA Power Systems Update Roadshow 2015. ? A: Sorry but I don’t know what content is planned for SVA roadshows. Q: Can this live update be used for other activities which dont involve patching but things like "rebooting after changing the settings for time zone change" A: Probably not unless the changes are kernel based. Configuration information that is unique to the non-kernel processes would not change. Q: The withdrawl website says. Why is 7.1 being withdrawn next year? 5765-G99 AIX V7.1 Enterprise edition September 30, 2016 A: The old AIX 7.1 Enterprise Edition was withdrawn because it was replaced by a new AIX 7.1 Enterprise Edition. AIX 7.1 has not been withdrawn. Q: looking to job in ibm india ? A: No I’m happy in Austin right now. You should have asked me at the peak of Summer.
A: Although AIX has supported rollback of patches since AIX V3, we strongly advise customer to use the alternate disk method to boot back to the original disk. There are many environmental variables involved in rolling back a patch can cause problems when you try to uninstall patches. Q: for mirrored rootvg, should I remove mirror before live update ? A: You do not need to remove the mirror, Live Update will simply create an additional copy. The only restriction is there are only 3 copies allowed, so if you alredy have 3 copies, then Live Update will fail Q: will live update have a minimum VIO level requirement? A: Yes. 2.2.4 Q: What is Power VC please? A: An advanced virtualization manager for Power. Replaced VMControl. See https://ibm.biz/powervclink Q: Why are you killing AIX by not introducing it to llinux cloud environment and on the other hand waisting resources to compeet with good established Linux platforms? Power KVM is a joke and is lightning years from existing on the market solutions. A: Linux is where the new applications are going. Power is trying to get our share of that business. Q: live update still works if the rootvg already has 3 mirror copies? A: Probably not. Q: What city will IBM Edge 2016 be in? A: I have not heard an announcement about this. My guess would be Las Vegas. Q: Can this live update be used for other activities which dont involve patching but things like "rebooting after changing the settings for time zone change" A: Potentially, but that is not what we're trying to do with this first release. Q: Why was "alternative disk" removed from VIOS between 2.2.2 and version 2.2.3 ? Since this is the preferred backout method for AIX, isn't this also the preferred backout method for VIOS ? A: Alternate disk install is still available in VIOS Q: Will SR-IOV be supported? A: The I/O must be virtualized through the VIOS, so we will be able to support SRIOV only through the new "vNIC" model where it is virtualized through the VIOS. Q: These Minipacks for VIO servers require reboot ? A: Yes
A: It should –it’s just a package of fixes like a service pack. Q: VIOS can do live update? A: No – Live update requires virtualized I/O and all I/O on a VIOS is physical.
A: We'll support vFC and vNIC, but not SRIOV with the VF assigned directly to the client LPAR (no VIOS). Q: thanks to Jay annd all of you, looking forward to meet you in Wiesbaden ^^ A: I didn’t know I was going to Wiesbaden Q: Are there any plans in allowing LPM over the WAN? A: Nothing announced. Q: How the migration works A: magic! It is built on the WPAR "Live Application Mobility" technology. It does a minimal checkpoint of each process, maps the memory for asynchronous demand-paging over a private network between original and surrogate, and then restarts the process on the surrogate. That's the best answer I can give in a chat session! Q: do you have to have HMC? Or is IVM enough? A: HMC is required Q: will vios move to aix7.2 code base? A: When it becomes necessary. Q: i mean aix 6.1 and 7.2 how we can migrate A: Yes, same migration options as with previous AIX releases Q: Is Server based Flash Caching AIX support of CAPI Flash? A: no, it's really not a good fit. Key benefit of CAPI flash is direct user-space access to the flash (need application to change to take advantage of this). flash caching is designed to plug in to the kernel i/o path so it's completely transparent to the applications. Q: Does Nova Link replace the HMC? A: Yes, eventually it will for virtualization management. HMC hardware management functions like firmware updates, call-home will continue to require a HMC. Q: is there any schedule for talking about vios patching? A: if this question was in context of live update, there is no current plan to support vios. First, it breaks the rule about having fully virtualized i/o, and second, with multiple VIOSs, there is already a non-disruptive update capability (by taking down one VIOS and updating one at a time) Q: I saw for flash caching the pci-e should be configured as vscsi. Is that true? Can we directly assign it to client LPAR, bypassing VIO server? A: Yes flash caching can be done with dedicated connections but that would disable LPM. Q: did live update require +1 disks (alt_inst) or +2 (pics looked like an alt_inst for the src AND the surrogate..?) A: 2 disks Q: Is NovaLink going to be a partition? A: yes
A: Same as previous generations of AIX.
A: Yes
A: this could potentially be a problem. While live update is intended to be transparent to applications, that's not true with kernel extensions. We have interfaces for ISVs to plug in to our framework so they can support it. It's also possible (if the extension is stateless), that it would work with no changes. We maintain a list of "safe" kernel extensions and by default Live Update will fail if an extension is not on the safe list. As ISVs add support for Live Update, they can add themselves to the list.
A: Not currently announced. Q: 2. Does novalink works with Redhat, too? A: Intent is to support other distros in time but not today. Q: how would Server Storage Pools affect the Live update? A: We will support SSP for Live Update. Q: Is VIOS v3 going to be discussed? A: No.
A: Yes
A: I believe this should work. Certainly no VIOS is required. Q: Will 7.1 to 7.2 be a full upgrade or update_all? A: New release requires clean install or migration (no update) Q: How the Flash Cache works with Easy Tier capability on SCO server? A: This is completely independent Q: Is PowerSC a separately priced product? A: yes, but PowerSC Standard Edition comes with AIX Enterprise Edition Q: So with customer that have configuration in flight with Power 8 and have HMC included, should they now remove the HMC if using 7.2? A: They will still need an HMC for phone home and firmware updates. Novalink will be version 1.0 so I personally would not drop the HMC just yet. Q: how does this effect updates with bos.net ? A: assuming this is referring to repackaging for network apps in 7.2. The whole idea is that if you remove a fileset (ftp for example), then on an update, it will not re-install this fileset that was removed. In other words, remove it once, and you don't have to worry about it any more. Q: Specifically, I am refering to 7.1 --7.2 Q: re: bos.net Q: 7.1 --> 7.2 A: The new packages will be installed on a migration to 7.2. You can uninstall the old bos.net.tcp.client packages after the migration. Q: are there SSP updates in VIOS 2.2.4? A: yes
A: HMC.
A: In due time. That is a non-disclosure briefing topic. Q: Is ASO/DSO being enabled for Power8 in 7.2 or 7.1 TL4? A: 7.2 will include DSO in the base (no longer a separate charge), but does not (yet) include P8 enablement – stay tuned! Q: Only NIS+ is mentioned. What about the really old NIS A: NIS is still supported. Yes it's older, but still in use by some, whereas NIS+ never really had much adoption Q: when Aix 7 will be withdrawn? is it 7.1 when Aix 7 will be withdrawn? is it 7.1 A: In due time. That is a non-disclosure briefing topic.
A: since we are using a different set of CPUs and memory in creating the surrogate, it will necessarily be different Q: Can remote restart of virtual machine be done outside of PowerVC or is it specific to PowerVC A: Remote restart can be done from the HMC as well. Q: no updates to cifs client? A: cifs client is moving to the expansion pack "as is" only, and no, there will be no updates in AIX 7.2 or 7.1 TL4. Any future updates to the cifs client will be "as is" only. Q: No Hitachi Disk support in PowerVC but they could be used by using a Shared Storage Pool, Right? A: Yes, using shared storage pools or SVC in front of HDS disks will work for PowerVC Q: When PowerVC 1.3.0 is going to be available ? A: December 6 Q: Will PowerVC support future models of DS8K ? A: That is up to the DSxxx development team but I would expect the answer is yes. Q: does aix7.2 support vWPAR 5.2 still? A: yes, both 5.2 and 5.3 vwpars are supported on 7.2 Q: hi ! Can i assume that The live update will include The hacmp licence that is required to run or I need to buy one licence of hacmp? A: Live update does not affect the PowerHA licensing requirement. You don't need anything "extra" for Live Update Q: If you decide to run novalink instead of the HMC is it required to run PowerVC? A: Potentially you would not need PowerVC but a vanilla OpenStack is not going to be able to use Power specific functions like shared processor pools, capped/uncapped, etc. Q: weather it will work with emc san disk ? A: Not sure which feature you're asking? There was an earlier question answered about EMC support for Live Update Q: So for this DRO to work is Enterprise Pool required? A: No. If you have it we will use it. Otherwise we will just use LPM. Q: I dont know if you already answer this or not, no reboot is only limited to kernel hot patch not for the TL /SP upgrade right ? A: First release is ifixes only. Stay tuned for SP/TL support.
A: WPARs are not going away. What IS going away is WPAR Manager, the IBM Systems Director plug-in. This means WPAR management will need to be via command-line. Q: How long is this presentation? I thought the original communication was 90 minutes. Is this running over, or was it planned to be 2 hours? A: Sorry. I ran over. Q: Any replacement for the PowerHA plugin for PowerHA 7.1 or will PowerHA 7.2 have its own management GUI? A: Nothing announced. Q: so what replaces wpar manager for LAM A: At the moment, there is no replacement for wpar manager for LAM Q: AIX 7.2 will support versioned WPAR for AIX 5.3? A: yes
A: Will be on AIX VUG wiki
A: 5.2 vWPARs continue to be supported on AIX 7.2 Q: One of Jay's slides had VIOS 3.1.0 listed. Is that not announced? No. it was just included as examples of naming standards. Yüklə 158,49 Kb. Dostları ilə paylaş:
|