Hi, I’m Julie Craft from AIX development in Austin, TX. We wanted to start a conversation with our customers about some of the function that we ship with AIX, interesting things that are going on and even get feedback.
I’ve been working on install (Image Management), NIM, serviceability and Systems Management since AIX was a young operating system.
One of the functions that I know many customers don’t know about is the ability to run inventory comparisons against NIM resources. You can do this thru smit (smitty invcon) or with the niminv command.
Also, many customers have asked about using NIM to install the VIOS, and while there are separate menus for this (smitty nim_node_tasks), you can also use regular mksysb installation and backup. Just remember to also backup the VIOS clients themselves, as well.
And, don’t forget to use lppmgr on your lpp_sources. This command will remove superseded updates or any language packages you are not using and keep your lpp_sources clean and tidy. More function is coming that will help with management of Service Pack downloads, so stay tuned for that!
Next time I’d like to talk about service & Fix Central a bit.
Other developers are waiting in the wings with their blogs, so I’ll close for now.
AIX Developers will discuss the latest in AIX technologies.
Hi there. My name is Thierry , and I provide support for AIX WPAR mobility. And before talking about mobility I wanted to add some comments on system WPARs.
WPAR file system considerations :----------------------------------------------Creating a simple system WPAR with a command like "mkwpar -sn mywpar" will result in creation of file systemsand associated messages : mkwpar: Creating file systems... / /home /opt /proc /tmp /usr /var......
When the file system population is complete, I can review the file system definition with the WPAR characteristics list command root> lswpar -M mywpar
Name Mount Point Device Vfs Nodename Options-------------------------------------------------------------------mywpar /wpars/mywpar /dev/fslv04 jfs2 mywpar /wpars/mywpar/home /dev/fslv05 jfs2 mywpar /wpars/mywpar/opt /opt namefs ro mywpar /wpars/mywpar/proc /proc namefs rw mywpar /wpars/mywpar/tmp /dev/fslv06 jfs2 mywpar /wpars/mywpar/usr /usr namefs ro mywpar /wpars/mywpar/var /dev/fslv07 jfs2
That's it for now - ThanksThierry[Read More]
Hello, it is me again, Thierry.I realized after my first blog that we talked about system and application WPAR but I didn’t come with a why use one or the other.So here are some hints.
All commands should get a man page (for example man mkwpar or man wparexec on your AIX system) which will provide detail of syntax and parameters of them and I recommend to read these pages before using the commands.
One way to choose between a System or an Application WPAR is to answers questions like • Do I need to run multiples processes and daemons ?• Do I need file system isolation (writing to global file systems not an issue) ?• Do I need devices ?• Do I need to log on using telnet/rsh ?• Do I need user management ?
If I answer “yes” to any of these questions, then I want to run System WPAR (see the man page for the mkwpar command) – Otherwise an Application WPAR may be sufficient (see the man page for the wparexec command).
Let think about this, and I will come back soon. Bye for now :-)[Read More]
I wanted to touch on a couple of things today: • Changes to Fix Central • IBM Systems Director and Update Manager
Back in 2007, Fix Central (http://www-933.ibm.com/support/fixcentral/main/System+p/AIX) was moved to a new infrastructure. While this gave us some nice new features like Download Director, we had to remove individual PTF / APAR download capability.
The net result is now customers must download the entire TL (which is required because we don’t support partial install/upgrade of a TL anyway) or Service Pack. Once a Service Pack is downloaded, you can select individual PTFs or install by APAR.
Also, the same thing happened with SUMA. If you request an APAR or PTF, the entire Service Pack (or TL) that contains the update will be downloaded.
I’m bringing this up not because I want to get beat up, but because we are working on some code that would allow customers to create a directory/repository with just the updates they want. I know many customers use ‘smitty update_all’ or ‘install_all_updates’ and they only want the updates in the directory or lpp_source that they want applied to their systems, nothing else. This will help create that directory. You can select just the fileset update or APAR and it will copy the required updates and requisites into a separate directory. Stay tuned to another blog and I’ll let you know when the code ships.
Also, if you haven’t already seen it, you can still do searches by fileset or APAR using the ‘Fix Search’ capability.
IBM Systems Director 6.1
Some of you may have seen the announcements for the new IBM Systems Director (http://www-03.ibm.com/systems/management/director/). There is a nice whitepaper out on http://www-03.ibm.com/systems/power/software/management/resources.html on Managing IBM® Power Servers with IBM Systems Director 6.1.
The paper will continue to be updated and in the next round should include more information about the Update Manager capability for AIX, System Firmware and HMC. One thing I will mention here about Update Manager is that it uses NIM to update the AIX systems.
Update Manager gives you the ability to set policies for your systems and flag them if they are out-of-policy. For instance, if you want to keep your systems at the recommended level for a particular Technology Level, you can set that and Update Manager will check the IBM database and let you know if there is a new recommended Service Pack available. Recommended Service Packs have been out in the field for at least 30 days and have no severe problems found.
We will continue to support SUMA for AIX update acquisition, but Update Manager will also download and install HMC and System Firmware updates and we’ll continue adding to that capability, so take a look and let us know what you think.
Until next time,Julie[Read More]
Hi there! My name is Veena. I work in the VIOS development area at IBM. VIOS is an acronym for Virtual I/O Server.
Virtualization is one of the latest buzz words in the industry today. So I wanted to talk a little bit about it in my first blog.
Virtualization was developed when mainframes predominated. But, it is now emerging as an important technology to provide scalability, greater flexibility and increased availability at all levels of computing. It is also being used to improve resource utilization and lower management cost.
Virtualization is a technique of abstracting physical resources and presenting a logical view of these resources to its end user. The physical resource could be a CPU, memory or an I/O device. By abstracting the physical resources and its boundaries, the virtualization techniques enable operating systems and applications to run independently of the actual physical hardware.
Virtualization allows aggregation, sharing and emulation of hardware resources. For example, a set of hard disks can be aggregated and presented as a single large virtual storage device. This virtual storage device may be later divided up on a different boundary to fit the applications. Virtualization facilitates sharing of physical resources. For example, a single I/O adapter may be shared by abstracting it to the multiple operating systems and applications as separate devices. Virtualization permits emulation of a hardware resource such that the applications may not know the difference between a physical piece of hardware and the emulated piece of virtual hardware. Pretty cool, eh?
I’ll talk about the VIOS and provide important tidbits in my next blog. Bye for now :-)[Read More]