<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>virtualisation &#8211; Strava LTD</title>
	<atom:link href="https://strava.ltd/category/virtualisation/feed/" rel="self" type="application/rss+xml" />
	<link>https://strava.ltd</link>
	<description>Services of IT infrastructure, AIX Operating System and IBM pSeries, IBM Power, PureStorage PureArrays and DevOps Ansible, Terraform, Infrastructure as a Code</description>
	<lastBuildDate>Tue, 03 Mar 2026 20:25:58 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>

<image>
	<url>https://strava.ltd/wp-content/uploads/2024/02/cropped-logo_strava-140_transparent-32x32.png</url>
	<title>virtualisation &#8211; Strava LTD</title>
	<link>https://strava.ltd</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>So you want an AIX versioned WPAR?</title>
		<link>https://strava.ltd/2025/09/05/so-you-want-an-aix-versioned-wpar/</link>
		
		<dc:creator><![CDATA[nicolas]]></dc:creator>
		<pubDate>Fri, 05 Sep 2025 15:41:54 +0000</pubDate>
				<category><![CDATA[virtualisation]]></category>
		<guid isPermaLink="false">https://strava.ltd/?p=232</guid>

					<description><![CDATA[You cannot get rid of your oldies but goodies AIX 5.x? No problemo, create an AIX versioned WPAR. In our example, we create an AIX5.3 on a AIX 7.2 host lpar: Once created, you can then wait for the migration day with confidence. Once the source lpar has been shutdowned, configure the IP addresses into the wpar: You can do so for multiple addresses, including IP aliases into the wpar on the same physical interface/ To map new or migrated disks (by SAN for example), you can use this same chwpar command: Once the disks are added, login into the]]></description>
										<content:encoded><![CDATA[<p>You cannot get rid of your oldies but goodies AIX 5.x? No problemo, create an AIX versioned WPAR. In our example, we create an AIX5.3 on a AIX 7.2 host lpar:</p>
<pre class="brush: plain; title: ; notranslate">
rendev -l hdisk1 -n aix53_rootvg
mkwpar -D devname=aix53_rootvg rootvg=yes -C -B /mksysb/mksysb0139 -t -n aix53 -l -O
&#x5B;...]
</pre>
<p>Once created, you can then wait for the migration day with confidence. Once the source lpar has been shutdowned, configure the IP addresses into the wpar:</p>
<pre class="brush: plain; title: ; notranslate">
chwpar -N interface=en0 address=10.30.191.130 netmask=255.255.255.0 aix53
chwpar -N interface=en0 address=10.30.191.131 netmask=255.255.255.0 aix53
chwpar -N interface=en0 address=10.30.191.132 netmask=255.255.255.0 aix53

chwpar -N interface=en1 address=10.30.194.130 netmask=255.255.255.0 aix53
chwpar -N interface=en1 address=10.30.194.131 netmask=255.255.255.0 aix53
chwpar -N interface=en1 address=10.30.194.132 netmask=255.255.255.0 aix53
</pre>
<p>You can do so for multiple addresses, including IP aliases into the wpar on the same physical interface/</p>
<p>To map new or migrated disks (by SAN for example), you can use this same chwpar command:</p>
<pre class="brush: plain; title: ; notranslate">
chwpar -D devname=hdisk2 devtype=disk aix53
chwpar -D devname=hdisk3 devtype=disk aix53
chwpar -D devname=hdisk4 devtype=disk aix53
</pre>
<p>Once the disks are added, login into the wpar using clogin, and pass a cfgmgr in order to load the newly mapped disks. You should then be able to import your Volume Group and or create a new one.</p>
<p>Have fun :/</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
