CYBER ZONE

C Kkompany (2008)

2008-08-04T11:46:00.000-07:00

	01 - Khokha - Mika Singh, Bappi Lahiri & Rema Lahiri (4.26 MB)
	02 - Speaker Baje - Anand Raaj Anand & Sunidhi Chauhan (3.57 MB)
	03 - C Kkompany - Sanjay Dutt (3.51 MB)
	04 - Jaane Kya - K.k. & Shreya Ghoshal (4.37 MB)
	05 - Speakar Baje (dhol Mix) - Anand Raaj Anand (3.07 MB)
	06 - C Kkompany (r-mix) - Sanjay Dutt (3.16 MB)
	07 - Khokha (remix By Dj Akhil Talreja) - Mika Singh, Bappi Lahiri & Rema Lahiri (3.68 MB)

Hijack-(2008)

2008-08-04T11:44:00.000-07:00

	01 - Aksar - K.k. (5.28 MB)
	02 - Dekh Dekh - Sunidhi Chauhan, Suraj Jagan & Rap By Joi (4.66 MB)
	03 - Koi Na Jaane - K.k. & Shilpa Rao (4.95 MB)
	04 - Theme Of Hijack - Suraj Jagan & Uday (4.89 MB)
	05 - Aksar (unplugged) - Shaan (6.28 MB)
	06 - Dekh Dekh (club Mix) - Sunidhi Chauhan & Joi (3.91 MB)
	07 - Aksar (remix) - K.k. & Joi (4.85 MB)
	08 - Aksar (sad Version) - Shaan (1.17 MB)

Leg workout routines:

2008-07-21T12:28:00.003-07:00

Choose a leg workout exercise that you wish to perform, and fully labeled directions shall be provided on the following page:


machine leg curl	machine leg extension	machine leg press


cable hamstring curl	cable leg extension	cable front squat


dumbbell/barbell lunge	back squat	dead lift


alternating seated calf raise	bulgarian split squat	single-leg standing calf raise


good morning	romanian deadlift	swiss-ball leg curl


beginner squat	sumo squat	decline leg curl


power clean	front squat

Chest workout routines:

2008-07-21T12:28:00.002-07:00

Choose a chest workout exercise that you wish to perform, and fully labeled directions shall be provided on the following page:


machine chest press	machine chest flye	cable crossover



cable chest press	cable chest flye	barbell bench press


dumbbell flye	dumbbell pullover	decline close-grip bench press


parallel-bar dip	single-arm external rotation	weighted pushup


unilateral high cable fly	unilateral low cable fly

Back workout routines:

2008-07-21T12:28:00.001-07:00

Choose a back workout exercise that you wish to perform, and fully labeled directions shall be provided on the following page:



assisted pull-up	machine lateral pull-down	cable seated low row


cable straight arm pull-down	cable seated high row	barbell bent-over row


bar upright row	lat pulldown	dead lift


seated reverse fly	neutral-grip pullup	t-bar bent-over row


one-arm row	back raise

Arm workout routines:

2008-07-21T12:26:00.000-07:00

Choose an arm workout exercise that you wish to perform, and fully labeled directions shall be provided on the following page:


preacher bench biceps curl	standing cable biceps curl	dumbbell biceps curl


ez bar standing biceps curl	machine triceps extension	triceps assisted dip


cable triceps push-down	cable triceps overhead extension	overhead bar press


triceps kickback	lat pulldown	decline close-grip bench press


standing concentration curl	swiss-ball preacher curl	french press


wrist curl	reverse wrist curl	hammer curl


angled prone curl	upright row	shrug

Shoulder workout routines

2008-07-21T12:25:00.000-07:00

Choose a shoulder workout exercise that you wish to perform, and fully labeled directions shall be provided on the following page:


machine shoulder press	machine lateral raise	cable side lateral raise


cable rear lateral raise	rotator cuff - internal	rotator cuff - external



bar military press	bar upright row	dumbbell lateral raise


single-arm pulldown	cable woodchopper	alternating shoulder press


shrug	standing scarecrow	lateral raise

Abdominal workout routines:

2008-07-21T12:23:00.000-07:00

Choose an abdominal workout exercise that you wish to perform, and fully labeled directions shall be provided on the following page:

illustrations

Ab Workout Routine

A routine which targets the abs effectively, and uses a select list of exercises shown on this page.

Altrnatively, customize your own routine by choosing from those illustrated on this page.

superman

prone cobra

abdominal crunch on a ball

inclined reverse crunch

v-up

standing oblique crunch

barbell cable rollout

jackknife


kneeling cable crunch	bicycle kick	oblique v-up


swiss-ball oblique crunch	high woodchopper	pulse-up


abdominal reverse curl	crunch twist

videos


abdominal hip thrust	medicine ball crunch	russian oblique twist


one leg reach	weighted side bend	plank

Weight Loss Basics

2008-07-21T12:16:00.000-07:00

How to Lose Weight

If you've ever tried to lose weight, you know it can be a difficult process. But, there are ways to make it easier. Understanding exactly what you need to do to lose weight is your first step and these resources will help you learn about the basic steps to lose weight, how to set realistic goals and simple tips for making healthy lifestyle changes.

Exercise for Weight Loss

Exercise is a key component in any weight loss program, but it can be confusing to figure out how much you need and where to start. Here you'll find in-depth information about every element of an exercise program including cardio, strength training, flexibility and how to put it all together. You'll also learn how to maximize your exercise program for great results.

Weight Loss Programs

An effective weight loss program includes both exercise and healthy eating to help you burn more calories than you take in. If you want specific guidance on starting a weight loss or exercise program, these free newsletter courses offer a variety of options for losing weight and creating a healthy lifestyle.

Top 7 Most Effective Ab Exercises

2008-07-21T12:07:00.000-07:00

Bicycle Exercise

The following exercises are part of the American Council on Exercise's study to determine the most effective ab exercises. Keep in mind that ab exercises won't reduce fat over the abs or create the coveted 'six-pack' abs. That comes with good genes and low body fat

although you should strengthen the abs along with the rest of the body to build muscle and raise your metabolism. For more about flat abs, visit my Abs Page for articles, workouts, FAQs and more.

The Bicycle exercise is the best move to target the rectus abdominis (i.e., the 'six pack') and the obliques (the waist), according to a study done by the American Council on Exercise. To do this exercise correctly:

1. Lie face up on the floor and lace your fingers behind your head.
2. Bring the knees in towards the chest and lift the shoulder blades off the ground without pulling on the neck.
3. Straight the left leg out to about a 45-degree angle while simultaneously turning the upper body to the right, bringing the left elbow towards the right knee.
4. Switch sides, bringing the right elbow towards the left knee.
5. Continue alternating sides in a 'pedaling' motion for 12-16 reps.

Exercise Ball Crunch

The exercise ball is an excellent tool to strengthen the abs and comes out number three for working the rectus abdominis. To do it right: 1. Lie face-up with the ball resting under your mid/lower back.
2. Cross your arms over the chest or place them behind your head.
3. Contract your abs to lift your torso off the ball, pulling the bottom of your ribcage down toward your hips.
4. As you curl up, keep the ball stable (i.e., you shouldn't roll).
5. Lower back down, getting a stretch in the abs, and repeat for 12-16 reps.

Vertical Leg Crunch

The vertical leg crunch is another effective move for the rectus abdominis and the obliques. To do it right: 1. Lie face up on the floor and extend the legs straight up with knees crossed.
2. Contract the abs to lift the shoulder blades off the floor, as though reaching your chest towards your feet.
3. Keep the legs in a fixed position and imagine bringing your belly button towards your spine at the top of the movement.
4. Lower and repeat for 12-16 reps.

Long Arm Crunch

This move, ranked 6th in the ACE study, emphasizes the upper part of the abs. To do it right: 1. Lie on a mat and extend the arms straight out behind the head with hands clasped, keeping the arms next to the ears.
2. Contract the abs and lift the shoulder blades off the floor.
3. Lower and repeat for 12-16 reps.

Reverse Crunch

It may seem like the reverse crunch is for the lower abs but, remember, the rectus abdominis is one long muscle, so you can't separate upper from lower. To do this move right: 1. Lie on the floor and place hands on the floor or behind the head.
2. Bring the knees in towards the chest until they're bent to 90 degrees, with feet together or crossed.
3. Contract the abs to curl the hips off the floor, reaching the legs up towards the ceiling.
4. Lower and repeat for 12-16 reps.
5. It's a very small movement, so try to use your abs to lift your hips rather than swinging your legs and creating momentum.

Full Vertical Crunch

In a full verticul crunch, you really work the abs by involving both the upper and lower body. To do it right: 1. Lie on your back and extend the legs up towards the ceiling.
2. Place hands behind your head (lightly cupping it) and contract the abs to lift the shoulder blades off the floor.
3. At the same time, press the heels towards the ceiling, creating a 'u' shape with the torso.
4. Lower down and repeat for 12-16 reps.

Plank on Elbows and Toes

The plank exercise ranked number 10 in the ACE study and is a great way to build endurance in both the abs and back, as well as stabilizer muscles. To do it right: 1. Lie face down on mat resting on the forearms, palms flat on the floor.
2. Push off the floor, raising up onto toes and resting on the elbows.
3. Keep your back flat, in a straight line from head to heels.
4. Tilt your pelvis and contract your abdominals to prevent your rear end from sticking up in the air.
5. Hold for 20 to 60 seconds, lower and repeat for 3-5 reps.

Rock On

2008-07-21T12:05:00.001-07:00

	01 - Socha Hai - Farhan Akhtar (3.84 MB)
	02 - Pichle Saat Dinon Mein - Farhan Akhtar (2.94 MB)
	03 - Rock On - Farhan Akhtar (3.59 MB)
	04 - Ye Tumhari Meri Baatein - Dominique Cerejo (5.02 MB)
	05 - Zehreelay - Suraj Jaggan (3.4 MB)
	06 - Tum Ho Toh - Farhan Akhtar (3.9 MB)
	07 - Sinbad The Sailor - Farhan Akhtar & Raman Mahadevan (5.99 MB)
	08 - Pichle Saat Dinon Mein (live Version) - Farhan Akhtar (6.04 MB)
	09 - Phir Dekhiye - Caralisa Monteiro (3.17 MB)

Mukhbiir

2008-07-21T12:01:00.000-07:00

	01 - Tu Salaamat - K.k. (5.77 MB)
	02 - Jeena - Sonu Kakkar (4.63 MB)
	03 - Dhoonde Dil - Hariharan (6.18 MB)
	04 - Tere Bina - Sadhna Sargam (4 MB)
	05 - Piya Mera Banjaara - Sonu Kakkar (4.81 MB)
	06 - In Dino (metro) - Soham Chakrabarthy (6.08 MB)
	07 - O Meri Jaan (metro) - K.k. (4.64 MB)
	08 - Alvida (metro) - K.k. (5.18 MB)
	09 - Dhaani (strings) - Bilal Maqsood, Faisal Kapadia (4.1 MB)
	10 - Albela Saajan (kailash Kher) - Kailash Kher (4.39 MB)
	11 - Yeh Tanhai (kk) - K.k. (4.01 MB)

God Tussi Great Ho (2008)

2008-07-21T12:00:00.001-07:00

	01 - Lets Party - Shaan & Sunidhi Chauhan (4.53 MB)
	02 - Tujhe Aksa Beach Ghuma Doon - Wajid & Amrita Kak (3.83 MB)
	03 - God Tussi Great Ho - Sonu Nigam & Shankar Mahadevan (4.15 MB)
	04 - Tumko Dekha - Neeraj Shridhar & Shreya Ghoshal (5.1 MB)
	05 - Lal Chunariya - Udit Narayan & Alka Yagnik (3.94 MB)
	06 - Tujhe Aksa Beach Ghuma Doon (remix) - Wajid & Amrita Kak (3.64 MB)
	07 - Lets Party (remix) - Shaan & Sunidhi Chauhan (4.19 MB)
	08 - God Tussi Great Ho (remix) - Sonu Nigam & Shankar Mahadevan (3.61 MB)

Hum Phirr Milein Na Milein

2008-07-21T11:58:00.000-07:00

	01 - Tere Dar Ke Siva - Udit Narayan & Sadna Sargam (4.32 MB)
	02 - Hum Phirr Milein Na Milein - Nishant Mudal (4.74 MB)
	03 - Sajan Mera - Sunidhi Chauhan (3.67 MB)
	04 - Sooni Sooni Rahein - Neeraj (bombay Viking) (3.92 MB)
	05 - Roz Yeh Mausam - Sonu Nigam & Sanjeevni (3.25 MB)
	06 - Main Ro Na Padun - Sunidhi Chauhan & Neeraj (bombay Viking) (4.44 MB)

what is web hosting ?

2008-07-17T13:20:00.000-07:00

A web hosting service is a type of Internet hosting service that allows individuals and organizations to provide their own website accessible via the World Wide Web. Web hosts are companies that provide space on a server they own for use by their clients as well as providing Internet connectivity, typically in a data center. Web hosts can also provide data center space and connectivity to the Internet for servers they do not own to be located in their data center, called colocation.

HOW DO I CHOOSE A GOOD SHARED WEB HOST?

2008-07-17T13:19:00.003-07:00

A good, shared Web host must provide reliable and reasonable quality of service. Many times, a consumer will sign up with the least expensive provider only to experience many technical difficulties and the inevitable and frustrating experience of changing Web hosts. To avoid this experience, it is best if the consumer chooses the right hosting company. Ensuring that a shared Web hosting firm has the following characteristics will increase the probability of consumer satisfaction.

Quality Server Technology The use of quality server technology is important. Since shared hosting services utilize multiplexed equipment, consumers must ensure that the server and server technology used can accommodate the number of users on your particular server.

System Administrators Make sure that knowledgeable system administrators are operating your hosting company’s technology.

Network Redundancy Your shared hosting package must have multiple connections to the Internet. Network redundancy ensures that if one Internet connection goes down, traffic can be re-routed through another connection.

Network Connectivity It is important to find the fastest Internet connection possible. Since you are competing with other users for resources in a shared hosting environment, you should ensure that you have at least T3 connection that is using less than 50 per cent of available bandwidth.

You should also consider the following factors before selecting any type of shared hosting solution for your Web site. By considering these factors, you will save money in the long run by selecting a solution that grows with your business.

Purchase only what you need Select a Web hosting solution that corresponds with your business needs. Only purchase services that your site will require to provide your specific content. Don't sign up for an all-inclusive account with a hosting firm if you won't use most of their services. This will unnecessarily increase your costs.

Select a scalable solution Make sure that your hosting solution can grow as your site grows in complexity. Ensure that you can upgrade your site to accommodate increased bandwidth and other demanding resource requirements such as server-side scripting, database support and multimedia streaming.

Find prompt tech support Only use a host that provides prompt and knowledgeable customer care. A dependable host should offer 24x7 toll-free technical support rendered by experienced and professionally trained technicians.

Check references Before you commit to a particular hosting firm, ask for references. Make sure to canvass other webmasters running sites with similar specifications. Browse their Web sites and measure response times at both peak and non-peak periods.

Watch your billing and keep your receipt Many hosting firms are notorious for their horrid billing practices. Check your credit card statements to ensure that you are not being overcharged or billed at an incorrect frequency. Most purchases occur online, so make sure to print out your receipt. Most companies will require you to remit that receipt by fax in order to cancel.

Back up all your data Do not depend on your host to recover any data you publish on the Web. Most hosting firms are only equipped to recover files in the event of a system failure. Ensure that you have a copy of any data that you post to the Web on your own hard drive.

Own your own domain Make sure that your Web host will not hold you hostage to their service by exercising administrative control over your domain name. Your host should only be listed as a technical contact. You should exercise administrative control over the domain name from the point of purchase.

Do extensive background research Find out whether a host is real or whether it resells hosting solutions. Also check what payment processor the host uses to run credit card transactions. Determine who owns the hosting company and whether they possess the technical expertise required to run it effectively. All of these factors impact upon the credibility and reliability of the host and the services you provide your customers.

Obtain assurances You should obtain assurances concerning service quality before you sign up for hosting services. A quality Web host should assure some form of service quality and compensation if you experience an interruption in service.

Understand your obligations Before you sign up with a Web host, you must understand what your obligations are concerning payment for service and permissible behavior. Certain hosting companies will not permit high traffic content, such as adult material. Other hosting companies will permit such content, but only if a special hosting service package is selected.

Establish an exit strategy Always have a backup plan in case your host goes belly-up or experiences an unrecoverable failure. Redundancy should always be a priority if you are running an Internet-based business. Remember that any service outage can completely compromise your source of income.

ENSURING YOUR HOST OFFERS DECENT TECHNICAL SUPPORT

2008-07-17T13:19:00.001-07:00

It's the role of any reliable hosting firm to take full responsibility for its hardware, software and operating environment so that webmasters can focus solely upon running their business.

If a hosting company is truly committed to this objective, their technical support must be stellar. Customer care therefore is always a major consideration before you chose a Web host.

Since it is a major loss leader, many hosting firms don't invest in the labor and equipment required to maintain their operation. It is thus the task of wise webmasters to size up the expertise of a hosting company's support staff before making the fateful decision concerning where to host their Web sites.

Determining whether technical support is dependable is important, because if anything goes wrong with your site, who are you going to call? In an ideal world, it would be your knowledgeable customer care representative. However, in the real world, we know that knowledgeable customer care is hard to find.

Hosting companies claim that they have technicians working 24 hours a day, seven days a week, 365 days a year in their operation centers maintaining mission-critical systems. While this in fact may be true, the most unqualified people in the hosting industry sometimes work in support call centers. Due to the unprecedented demand for IT professionals, many Web hosts can't find employees that are formally trained in Operating System and network technology. Other firms allot so much money to advertising and marketing that technical support becomes a secondary priority. In both instances, customers suffer because they cannot access immediate or useful assistance. So before you select a host, make sure that you put their support to the test.

First, call up technical support and ask them to walk you through the basic routines needed to maintain your site. Ask the technical support technician whether he or she is available at the office at regular intervals. Ask the technician whether he or she went through a corporate or professional training program in order to qualify for the job. If the technician is assisting you with a Windows NT-based request, make sure to ask whether he or she has a MCSC, or Microsoft certification. Ask the support technician how long he or she has been working with the company.

Determine whether technicians are knowledgeable by listening and assessing their tone of voice. Do technicians at a certain company put you on hold often? Then they may only be employed to answer telephones or e-mail and relay support requests to someone more qualified. Also ask support technicians basic questions about where the company is located, where they are located and the company's address. This might give you an indication if a hosting company's support services are outsourced, or whether support representatives are working out of the firm's server farm or head office. Ask the support representative outright whether he or she is employed on a contractual basis. Also determine how sophisticated customer tracking and billing is by asking the technician to pull information about your account.

This will give you an indication whether the company has automated systems to track technical inquiries. Further, ask the technician whether the firm provides an online "knowledge base" or "technical support center." If the company does, make sure to inspect its support documentation to determine whether it is specific to the service.

Many hosting companies now offer technical support documentation in hard copy format. You should attempt to determine whether the hosting firm will allow you to download a PDF file with all of its documentation enclosed.

A prospective Web hosting customer should also determine whether a hosting company offers true 24-hour support by e-mailing or calling the hosting provider after hours.

These tests will give you a strong indication whether the technical support is reliable or questionable. Remember that you'll have to trust any host you select to deliver timely and useful support on issues that can affect your income.

What operating system is best for your web site?

2008-07-17T13:18:00.004-07:00

One of the first things you will need to do in setting up your business on the Internet is to find a web host. The Web expands every day, and so do our choices. Just how do you find a web host to meet your business needs? There are literally tens of thousands, each one with a different focus and services designed for a specific segment of the market.

The operating system used by your hosting company may limit your flexibility as your company begins to grow. As you study your options, you might consider the following tips:

An operating system or "platform," such as Microsoft's Windows NT or DOS is the basic set of commands that tell your computer how to open applications and store files. In the early days of Internet activity, most servers operated on a UNIX platform, an extremely powerful and flexible system that requires considerable technical expertise to administrate. UNIX is still as popular as ever, but today you have a choice: Windows NT and UNIX variations such as Sun Microsystems Solaris, and Berkeley's BSD.

Experts offer significantly different opinions as to which platform works best for web sites, we will however give a brief description and analysis of the different systems. In the end, the choice depends largely on your budget and what you want to do with your site.

Linux

Linux, a version of UNIX, is a very versatile platform that serves a number of functions well. It is particularly suitable for meeting your Internet requirements, such as mailing, streaming, Web serving, and fileserving. Linux is a very cost-effective choice it uses hardware efficiently, and allows for more web sites per server, thereby lowering the cost of hosting per account. Linux servers are compatible with certain Microsoft extensions and applications, for example, MS SQL (a database program) or Microsoft Front Page (a web authoring tool). Many engineers prefer the flexibility, security, and control of Linux servers. Linux is Open Source (free) software and a host of free programs are available to users of Linux.

Microsoft Windows NT/2000

Window's 2000 graphical user interface makes it user-friendly and provides a familiar interface for most IT teams to work with. It integrates well with other Microsoft applications and there are a wealth of commercial applications available for this platform. Particularly attractive is the integration with Microsoft Application Server (ASP) which allows the creation of dynamic web pages linked to SQL databases, and other Legacy back office systems.

Sun Solaris

Sun Solaris servers offer the highest level of resources and power - these are the most robust servers! Sun has a proven track record and is deployed in many large Fortune 500 corporations. It is a mature platform and there are a large number of applications and development tools available. Because of Sun's capacity and stability it is ideal for high-traffic functions, such as database servers, high-traffic Web servers and mission-critical servers.

Cobalt RaQ

The RaQ was designed for virtual (shared) hosting of multiple Web sites. It's simple administration makes it a great first Web server. Its flexible administration interface also allows you to share administration responsibilities among your staff.

FreeBSD

FreeBSD is a version of BSD that was designed for the X86 processor. FreeBSD is a very stable open source operating system, and a good alternative to Linux. It is an extremely well-integrated and tested system, and is inexpensive. There are a large number of free applications available for use with it

How do I choose? As your site grows in size and complexity, in all likelihood your needs will change and the capability and scalability of a particular platform will come into question. It's best to anticipate this contingency and choose a web host that offers a variety of operating systems which are scalable and backs them up with technical expertise.

What is Bandwidth?

2008-07-17T13:18:00.003-07:00

What is bandwidth at all? Why does it matter when signing up for a web hosting account?

Definition:

Bandwidth = The amount of data passing through a connection over a given time. It is usually measured in bps (bits-per-second) or Mbps (Megabits per Second).

Many web hosts use this term (bandwidth) in place of (data) transfer allowance. The actual data transfer allowance is important to you as the hosting client. Transfer allowance is the amount of data that is actually allowed to be transferred between the server (your website in this case) and the client(s) who access your website when browsing the Internet.

How can you measure the amount of transfer allowance you will approx. need for your website? To find out what your transfer requirements are, you will need to look at the actual data transfer that your website will create.

For example, if you have a website with 5 pages each is about 50 kb in size. If a visitor of your website views one page, about 1 x 50 kb of data transfer is being used. If the person views all 5 pages then you get 5 x 50 kb or 250 kb of data transfer being used. Now imagine your website gets 100 visitors a day who all look at your 5 pages. 100 X 250 KB = 25,000 KB (approx. 24.41 Megs). Now put this into 30 days of a month and you get the approx. of data transfer allowance (for the matter: bandwidth) you will need to operate your website.

Keep in mind, that you should allow enough room to grow and that there is actually more data being transferred when you use email and/or FTP on the same account. Uploading your website uses part of your data transfer allowance.

Unlimited bandwidth or data transfer allowance - this is good, isn't it?! "I see this all the time when searching for the best deal in web hosting!"

No, it is not good. There is no such thing like unlimited bandwidth or data transfer. Bandwidth is limited by hardware. A 'pipe' only has a certain size (throughput). It can't just grow in size when required. Also - a web host as to pay for the data transfer being used. He will be charged by his upstream provider (AT&T, Sprint, Level3, etc.). Try to find an 'unlimited' offer for web hosts on their websites. You won't find it. There is always a price tag on data transfer and bandwidth. Stay away from an 'unlimited' offer. If you really start using more and more bandwidth, the web host will you cut you off at one point because you start eating up his revenue.

What is a Data Center?

2008-07-17T13:18:00.001-07:00

A data center is a facility used for housing a large amount of electronic equipment, typically computers and communications equipment. As the name implies, a data center is usually maintained by an organization for the purpose of handling the data necessary for its operations. A bank for example may have a data center, where all its customers' account information is maintained and transactions involving this data are carried out. Practically every company mid-sized and upwards has some kind of data center, and large companies often have dozens of data centers.

As data is a crucial aspect of most organizational operations, organizations tend to be very protective of their data. A data center must therefore keep high standards for assuring the integrity and functionality of its hosted computer environment. This is depicted in its physical and logical layout.

Prior to and during the dot com crash, thousands of square feet of general-purpose data centers were built in the hope of filling them with servers for web hosting and application service providers. This demand went largely unrealized.

A co-location centre is a type of data center.

Physical Layout

A data center can occupy one room of a building, one or more floors, or up to the whole building. Most of the equipment is often in the form of 1U servers (so-called "pizza boxes") racked up in 19 inch rack cabinets, which are usually placed in single rows forming corridors between them. This allows people access to the front and rear of each cabinet. Some equipment such as mainframe computers and storage devices is often as big as the racks themselves, and are placed alongside them.

The physical environment of the data center is usually under strict control:

Air conditioning is used to keep the room cool, generally around 17 degrees Celsius. This is crucial since electronic equipment in a confined space generates much excess heat, and tends to malfunction if cooling is not handled.

Backup power is often available. This can include one or more uninterruptible power supplies and diesel generators located close by.

Data centers typically have raised flooring made up of 2 foot (600mm) removable square tiles. These allow (in theory) all data and power cabling to be laid neatly and safely in cable trays below.

Data centers often have elaborate fire prevention and fire extinguishing systems. Using water on operational electrical equipment can do just as much damage as a fire so using it is not an option - also ordinary water and electricity don't mix well. Originally halon gas was used in the event of a fire to extinguish flames - an inert gas that pushes all the oxygen out of the room. However this has now been banned in some countries because of the danger it poses to people if they are trapped in the same room without emergency breathing oxygen supplies. More recent alternatives include Aragonite and FM200, and even systems based on ultra-pure water.

Physical security also plays a large role with data centers. Personal access to the site is usually restricted to a select few. Video camera surveillance and permanent security guards are almost always present if the data center is large or contains sensitive information on any of the systems within.

Network Infrastructure

Communications in data centers today are most often based on networks running the IP protocol suite. Data centers contain a set of routers and switches that transport traffic between the servers and to the outside world.

Some of the servers at the data center are used for running the basic Internet and intranet services needed by internal users in the organization: email servers, proxy servers, DNS servers, etc.

Network security elements are also usually deployed: firewalls, VPN gateways, Intrusion detection systems, etc. Also common are monitoring systems for the network and some of the applications.

MOVING TO A NEW WEB HOST

2008-07-17T13:17:00.004-07:00

So, you've decided that your current host doesn't suit your needs and you need to choose a new one. Well, don't worry - it happens all the time. Many webmasters upgrade their hosting services once their Web sites become popular, usually because their current hosting firm cannot provide an effective level of scalability or technical support.

Before you move, it's extremely important to make sure you have copies of everything related to your site. Double-check that all content, including Web pages, databases and scripts, are properly archived. But don't archive your Web sites just in case you switch hosts - always back up your data at regular intervals in case you experience unexpected data loss or hardware failure. This will also ensure that all your data is archived and compressed in its original directories, which is very important if you want to retain the full-working integrity of your Web site when you move.

Once you have archived your site, make arrangements to purchase your new hosting services. Make sure that any new solution you select includes basic services that approximate and surpass the service you where obtaining with your previous provider. Perform a search with our advanced search utility to make sure the companies you are considering offer exactly what you're looking for. It makes no sense to replace your present hosting service with another Web hosting solution that equally cannot fulfill your technical requirements.

When your new solution is activated, upload your archived Web pages, database and scripts to the new host. You will be allocated an IP number from the new hosting company. Take time to debug and test the new site from the individual IP number.

After your site is entirely debugged and you verify that all site functionality is operative, transfer your domain name service (DNS) servers over from your old host to your new host.

During this DNS transition period, which is referred to as the "propagation period," your Web site will be resolved by both your new and old host, as new DNS information about your Web site filters through the Internet worldwide. It typically takes about 1-2 weeks for the transfer to fully propagate around the Internet; so keep your old site running in case you get visitors whose ISP's name servers haven't updated fully.

It is imperative that you retain both your old and new hosting services during your hosting solution transition. You will need to check your e-mail from both hosting providers, since some regions of the Internet will direct e-mail to your original host, while other regions will start sending mail to your new server during the transition.

This same situation will occur with your site’s Web server during the period of propagation. For this reason, you must ensure that both hosting services are operating simultaneously during your solution transition.

Once a week or two have elapsed, cancel the account with your previous hosting company. Make sure to only pull the plug on your old account when e-mail stops arriving from your old server.

To ease the transition, you may want to select a hosting service that approximates the features of your previous hosting company. With a wide range of hosting control panel and automation software packages available, it is now easier to transition Web sites.

Transitioning from one new host to another can be a simpler task if you select the same operating system platform and control panel. Some hosting companies make transition from one control panel to another easier by employing a tool that actually automates the transition from a competitor.

Remember, when you're shopping for a new hosting company, make sure their services suit all of your needs. Use our enhanced search to find a host that meets your exact specifics. This will reduce your chances of having to search for another host later.

EVALUATING PERSONAL WEB SITE HOSTING SOLUTIONS

2008-07-17T13:17:00.003-07:00

Web hosting for personal sites differs tremendously from hosting for mission-critical e-commerce in that it is not as complex or demanding. For this reason, individuals and hobbyists can opt to select low-cost solutions that allow them to experiment with Internet technology without making a demanding or expensive commitment.

Personal Web sites that focus on publishing an individual's resumes and other personal content can be easily satisfied by free hosting solutions. Typically, if all you require is a small personal Web site, then there are a myriad of free sub-domain hosting solutions that are available.

Free sub-domain hosting allows individuals to host their Web site at a large portal or content aggregator. Usually your Web site is hosted in a Web community, and is sub-categorized by interest. The hosting is provided free-of-charge by way of pop-up or banner advertIsements and sponsorship automatically included by the host. The most popular of these sites include Yahoo! Geocities (www.geocities.com) and Tripod (www.tripod.com).

These services are only meant for personal use and because they are offered en masse, your site will be one of many sites shared on a server. Because free hosts don't charge you for their services, their fiduciary responsibility to you and your quality of service is limited. Free hosts have a tendency to offer no quality assurance or technical support because their business model is a loss leader meant to attract a large amount of users in order to generate advertising revenue.

While this business model might not amount to the most dependable service, it does allow individuals to set up free sites. Another solution that many individuals and hobbyists also select is the hosting associated with their ISP account. Many ISPs offer sub-domain hosting space along with their dial-up or broadband access to the Internet.

More complex hosting services provide highly individualized functionality that guarantees a sound level of quality service. Such services are fee-based, ensuring that revenues can be allotted to maintaining and improving service and providing superior technical support.

The most basic entry-level fee-based service is "virtual" or "shared" hosting. Shared servers offer clients the ability to host their Web site on a powerful, professionally managed server, at a low monthly cost.

Shared servers provide individual Web sites with redundant connectivity, guaranteed uptime. These services provide an excellent solution for entry-level hosting needs because they are designed to host small-scale e-commerce sites and static Web pages.

These sites are also popular amongst first-time webmasters because they can provide reliable Web presence without advanced technical skills. These servers are also very popular amongst webmasters because they allow you have your Web site hosted on your domain name such as http://www.yourname.com.

Such services vary widely in price and can cost anywhere between $2 to $50. As with any purchase, users can expect the quality of service to fluctuate based upon the amount paid for the service. "Caveat emptor" is thus the rule and not the exception when it comes to purchasing shared hosting services.

If an individual decides to purchase a relatively inexpensive package, then he or she can expect the quality to reflect the cost of the service. The lower the price one pays for hosting, the more network outages and service problems a consumer can expect.

This however might be acceptable if all an individual desires is non mission-critical hosting for a non-essential personal site.

WHAT IS VIRTUAL OR SHARED WEB HOSTING?

2008-07-17T13:17:00.001-07:00

Virtual or shared Web hosting is the business of housing and serving files for a Web site. Typically, an individual or small to mid-sized business cannot afford to independently obtain an extremely robust connection to the Internet for their Web presence. Virtual or shared Web hosting provides these consumers with the option to outsource their Internet requirements inexpensively.

Using a shared hosting service allows these companies to share the cost of a fast Internet connection for serving files. It is the most basic entry-level, fee-based hosting service a customer can select.

Shared hosting offers clients the ability to host their Web site on a powerful, professionally managed server at a low monthly cost. Shared servers provide individual Web sites with redundant connectivity and guaranteed uptime. These services provide an excellent solution for entry-level hosting needs because they are designed to host small-scale e-commerce sites and static Web pages.

Shared hosting is also popular among first-time webmasters because it can provide a reliable Web presence without advanced technical skills. Such a service is also advantageous to the smaller consumer because it assures them that they will obtain transparent services and that their Web site will have its own domain name and set of e-mail addresses.

Virtual hosting services are thus extremely popular because they offer the smaller consumer fast deployment, strong resources and most importantly, low cost. By paying an affordable and predictable monthly fee to a shared Web hosting service, consumers obtain reliability, expertise and faster connections than their dial-up service can provide.

Such a service is also advantageous to the smaller consumer because it allows them outsource a high-traffic, content-rich Web site for a small percentage of what it would cost to hire a single employee to develop it and run it in-house. For this reason, most individuals and small businesses opt to select a virtual hosting service because it is inexpensive and usually provides the basic services that they require.

Convenience is another factor that drives popular interest in shared Web hosting due to the service's fast setup time and bundled features. Typically, site activation can take minutes after you have purchased services with a credit card.

The most characteristic feature of virtual Web hosting is that services are usually bundled. For an inclusive monthly fee, consumers can obtain a variety of high-quality, multi-platform Web site solutions.

Usually the bundle of services includes a minimum amount of disk storage space for your Web pages. The bundle will normally also include a minimum amount of data transfer, or a capped amount of data that your can send to individuals that access your Web site. Most virtual accounts will also include e-mail forwarding services along with hardwired, physical e-mail boxes. Mail forwarding services allows you to create e-mail aliases at your domain name that will forward to an external e-mail address.

A decent shared hosting firm will also include free 24x7 technical support in all of its service bundles. It should also include unlimited file transfer protocol (FTP) services so that you can update your Web site at anytime.

For your own reference, a shared Web hosting service should also provide you access to Web statistics, so that you can gage how many Internet clients are visiting your site. For the sake of accuracy, a reliable Web host should also provide its customers with access to raw statistical logs, so that consumers can use their own statistical Web packages for site analysis.

Other services that are typically characteristic of a shared Web host include: daily tape backup of your Web site; anonymous FTP server access so you can provide public access to your files via file transfer protocol format; and full CGI-BIN access so that as you upload scripts that will add functionality to your Web site.

Most shared or virtual hosting services now also offer hosting automation software such as control panels. The control panel allows a consumer to control most aspects of their hosting service through an online graphical interface. The graphical interface allows users to control all the characteristics of a shared hosting service described above.

HOW DO I EVALUATE A SHARED WEB HOST?

2008-07-17T13:16:00.002-07:00

Finding a decent virtual or shared Web host can only be achieved by conducting in-depth consumer research and evaluation. Many tools exist online that can assist the individual and small business find an extremely reliable hosting service. With the myriad of choice available, it is necessary for the consumer to discriminate. Since shared Web hosting is conceived as only a low-end, low-margin commodity by the industry itself, it is necessary for the consumer to be very wary. There are literally thousands of hosts that offer shared and virtual Web hosting services. While many provide extremely good service, others provide service that is less than desirable. In order to find suitable Web hosts, consumers must conduct due diligence.

Prospective shared hosting clients must therefore ensure that they test the technical capacity of any host thoroughly before they procure their services. Advanced testing of a potential host will reveal whether the solutions they provide are reliable enough for your high-traffic site. Remember that your Web host must be trusted to provide solid network infrastructure. If you select a host that cannot provide robust connectivity, then your site's availability to the world will suffer. For this reason, informed consumers will evaluate potential hosting firms before they sign-up.

Testing ensures that consumers will not waste their good money on bad services. Reliable testing results can be obtained through the use of sophisticated network tools that monitor hosting performance. Such tools will determine how often a host's servers experience outages and will generate a list of probable reasons why hosting services are unreachable. It is advantageous for you to use such tools to ensure that the host you select will provide minimum downtime. Most hosting firms boast about their relentless commitment to excellent service and server responsiveness, and usually the crowning jewel of this commitment is 99 per cent uptime.

But while most hosting operations use this promise of incredible uptime as a hard sell, few consumers actually test whether these pledges are true. Smart consumers of hosting services, on the other hand, are the first to authenticate these service guarantees. They usually consult the services of an established server monitoring services such as NetMechanic, provided by Keynote Systems.

NetMechanic provides an integrated suite of tools that detect problems with your Web site. The company's "Server Check Pro" product is an excellent choice for ensuring that your server is up 24 hours a day. The tool will ping, traceroute and attempt to access your site via http on a regular basis to verify that your server is up. For a small fee, the service monitors your servers constantly, and contacts you by your choice of pager, cell phone or e-mail when your server goes down. The tool will also generate specialized performance statistics in real-time so that you can monitor outage patterns to ensure you're getting quality uptime from your host.

You should also routinely attempt to check server response from your own computer. If you are using a regular 56k dial-up connection, you should attempt to pull up sites located with your prospective host during peak and non-peak hours. A battery of low-cost tests is available on the network layer level of your operating system. You can test a potential hosts' network and server responsiveness from your MS-DOS or UNIX line prompt. In order to obtain a true representation of the host's services, you should select Web sites on your host's network that are typical of the services they render to their normal clients.

You should thus avoid testing the host's main Web site or premier customers. These sites are mission-critical to a hosting firm and thus are afforded an extremely high level of maintenance, which is not always representative of typical service.

In order to locate a typical client of your prospective host, execute a "whois" search. Whois is an application that looks up critical information about any Internet domain. This information includes ownership, location of the host, and most importantly, its block of network numbers. By executing the "whois -a yourhost.com" command at a UNIX line prompt, you can search your potential host's entire block of network numbers, and seek out a normal customer who is hosted on an individual network address. The customer that you use should have the approximate services that you seek. Use the ping and traceroute commands from either your UNIX or DOS prompt to test server responsiveness. You also can obtain many free or shareware WYSIWYG (what-you-see-is-what-you-get) network tools for the Windows platform that can test server responsiveness. An excellent suite of bundled network tools is provided free-of-charge by PCS Network Tools.

Using a line-prompt or WYSIWYG application, attempt to "ping" sites from the prospective host on your computer. Ping is the networking equivalent of sonar. The network tool is used to verify that a given server is actually reachable, and measures the delay that occurs when sending a data packet to it and back again.

Executing a "traceroute" from your computer is also an interesting and informative experiment to run on a hosting company. Traceroute applications allow you to map the direction that data travels over the Internet. By conducting a traceroute, you can determine whether the data you have requested from your prospective host will take a direct or indirect path to you. The most successful incident of a traceroute is therefore when data takes the shortest route to your computer.

These tests, conducted manually on a regular 56k connection will give you a rough indication of your client's response time if you were to choose the prospective host that your testing. In essence, these tests determine whether a host provides the lowest level of network latency, ensuring that data is passed to browsers and other Internet applications as quickly as possible. Your aim must be to ensure that the delay between request and response from a prospective hosting service is as short as possible. Making this determination is only possible if you conduct serious tests on prospective hosts before hosting your content there.

HOW DO I FIND A GOOD SHARED WEB HOSTING PROVIDER?

2008-07-17T13:16:00.001-07:00

Consumers can find an excellent shared hosting provider by using Web hosting directories or by directly soliciting hosts for comments on their service packages.

Using hosting directories is a highly recommended strategy, because such sites aggregate a tremendous amount of information about the hosting industry and its participants. By leveraging a host directory, regular consumers can contrast and compare the different features of several Web hosting firms.

The most credible hosting directories have catalogues that allow you to search for hosts that match specified criteria, whether it is based on cost, technology or geography. Most of the more sophisticated hosting directories also include an "advanced search" option that allows consumers to fine tune their hosting requirements.

Users of these resources must be cautious and exercise due diligence however. Some directories only allow paid advertisers in their catalogues, making the directory non-meritorious in composition. Consumers should be aware of how the list is compiled, updated and what criteria are used to add companies - especially if the site offers a top ten or twenty ranking.

Many hosting companies only conceive of hosting directories as marketing channels. For this reason, some disreputable hosting companies and executives have developed, purchased or even influenced certain hosting directories to boost their own revenues.

Too often, a directory will actually sell the most popular listings to various hosts who are willing to pay top-dollar for an award or recognition. Consumers should thus make no correlation between an award and quality.

Kudos, awards and recognition are indicators that a host has financial resources to advertising online, but does not indicate whether the host offers credible and reliable service.

Not all awards and recognition are purchased advertisements, however. When recognition is not purchased, you only need to inquire how the host was specifically selected for an award. This can usually be determined from an evaluation formula that is posted on the Web site.

Consumers should also note that many hosting directories not only offer a large list of hosts, but also detailed information about the host's features, price ranges and provide consumers with the ability to compare hosts again each other.

More sophisticated hosting directories will also include in-depth articles, message forums, evaluation tools and even promotional campaigns that will save you money with the most credible hosting firms. These features are also important because they allow consumers to obtain more in-depth and personalized information about a hosting firm.

Other resources that consumers may want to consult are online bulletin boards. Specialized bulletin boards contain and solicit postings from consumers who provide their opinion and experiences concerning their experiences with a hosting company. These resources provide users with a candid understanding of the inter-workings of hosting companies.

Savvy consumers should also consider searching for online comments concerning a specific host that they are seriously contemplating. Finding comments from dissatisfied consumers is as important as finding complements about the company. Consumers can find comments by conducting a search, using the candidate hosting company's name, in a search engine.

Another strategy that should be employed is direct correspondence. The concerned consumer should actually send potential hosting companies pre-sales e-mail to determine what features are available. Sending a pre-sales e-mail will also give the consumer an indication of how quickly the host responds to general inquiries. A credible Web host will respond in less than 24 hours. However, consumers must be aware that most hosting outfits will always respond to sales inquiries faster than technical support requests.

When composing a pre-sales e-mail, consumers should ask the following questions (consider simply copying this following list and sending it to a candidate Web host):

* Is there a discount if I pre-pay for a number of months in advance?
* What payment methods are available?
* How many months in advance am I required to pay?
* Is there a set-up fee?
* Is there a trial period or money-back guarantee?
* What is your bandwidth, transfer or hit limit?
* May I visit other sites hosted by you?
* Will I have my own IP number or is it shared?
* Do you offer an unlimited, 24/7 technical support service?
* How much space is available with your package?
* What is the OS and version of the server my site will be placed on?
* What are the hardware specs of the server?
* How many sites are currently running on the server?
* How many more sites do you think you will put on it before it is full?
* How do you decide what constitutes a full server?
* Is there any way for us to set up a mailing list for announcements?
* Will I have 24-hour FTP and telnet access?
* Will I have anonymous FTP?
* Will I have an automated control panel to access my site?
* Do you provide a full, free CGI directory?
* Can I run CGI scripts outside of the CGI directory?
* Is there a limit to how many scripts I can install?
* Do you provide full shell access?
* Can I debug a problematic CGI script on the server?
* What version of Perl do you use? Does it contain a full set of modules?
* Do you offer a Web statistics package?
* Will I also have access to the raw statistical log files?
* Does the space used by my logs count against my allotted disk space?
* What is your acceptable usage policy?
* How long have you been in business?

By employing a strategy of due diligence through the combined use of credible, hosting directories and direct correspondence with hosting firms, smart consumers can find an excellent shared hosting provider.

WHAT OPERATING SYSTEM SHOULD I CHOOSE?

2008-07-17T13:15:00.002-07:00

Shared or virtual hosting is usually available on a UNIX or Windows platform. What is the difference between hosting on these operating systems?

Windows Servers are designed to accommodate advanced Microsoft applications. Windows Servers therefore integrate back office offerings such as FrontPage, Access and MS SQL. Windows Servers also offer specific programming environments such as Active Server Pages (ASP), Visual Basic Scripts, and Cold Fusion, which mainly link database applications to the Web. Windows servers usually do not provide an interactive shell, but are accessible through GUI-based remote administration packages such as PCAnywhere or through a customized control panel. Such packages allow you to log into the server's desktop as chief administrator as long as you have full control over your server.

Windows hosting is now an excellent option for both shared and dedicated servers. Due to the latest technological developments, Windows Servers can be more easily multiplexed and managed due to .NET technology.

Windows is also an excellent operating system to use if you intend to run your own dedicated server.

Since Windows servers provide unparalleled levels of support, security and integration for the Microsoft family of products, we recommend that consumers select Windows hosting if they need to link a Microsoft-based service to their Internet hosting requirements. Windows hosting, however, is rather complex and labor-intensive and should only be selected if a webmaster has extensive experience in maintaining Windows systems remotely and requires product/Web integration.

If a webmaster does not have experience in deployment or development in the Windows environment, they might opt to host on the UNIX platform.

A large number of hosting solutions are provided on the UNIX platform. This is because the UNIX platform is specifically designed to accommodate heavy Web traffic and server loads. UNIX servers are robust and are recognized for their ability to host multiple sites and serve out gigabytes of traffic.

This platform is also preferred by most webmasters due to their technical requirements. UNIX servers provide a wider degree of flexibility due to their shell environment. Shell environments are interactive, text-based systems that allow webmasters to interact and customize their services in real-time from any computer system worldwide. Unlike Windows systems, UNIX is not limited to special remote administration programs. A typical UNIX system can be accessed from any computer connected to the Internet without special or expensive software.

But the most favored reason that most webmasters choose the UNIX platform is because of its uptime. Most UNIX systems with heavy traffic can provide 99 per cent uptime. Windows servers with heavy traffic usually cannot make this same claim, unless specially configured. For this reason, average webmasters should select UNIX as their OS.

If you are a novice, you most likely will not require Windows hosting and you should select one of many UNIX hosting plans. The only time you would need to use Windows hosting is when you are using the specific Windows applications noted above. Microsoft FrontPage may be used on both the UNIX and Windows platforms, since most hosting firms support Microsoft FrontPage server extensions on both.

EXPLAINING VIRTUAL PRIVATE SERVER (VPS) SOLUTIONS

2008-07-17T13:15:00.001-07:00

A virtual private server (VPS) solution uses a software platform that permits a hosting vendor to multiplex a single dedicated server into multiple "virtual" machines. In essence, a VPS solution is a private and protected Web services infrastructure that operates as an independent server.

A virtual private server allows multiple customers to share the expense of hardware and network connections without sacrificing privacy, performance or preference. For this reason, VPS is considered one of the most sophisticated modes of automation available for provisioning small to mid-sized enterprise Web hosting.

The use of such technology allows hosting providers to save money by simulating the features of a dedicated server multiple times upon a single physical hosting environment, while concurrently allowing them to deliver high-quality Web services to their end users. VPS solutions allow Web hosting resellers to provide a full range of services usually only afforded by dedicated hosting technology. Resellers can therefore offer their clientele full administrative or "root" access to their Web services.

The virtual private server was first implemented by hosting giant NTT/Verio to bridge the gap between shared hosting environments and customized dedicated servers. By using a virtual private server, Web hosting resellers and Web designers can provide small businesses the performance, security, and control of dedicated hosting services at a fraction of the cost.

A virtual private server eliminates the restrictions of virtual hosting by providing all of the administrative features of a dedicated server. Each VPS user therefore receives their own set of services that they can customize to their specific needs. Virtual hosting is limited in comparison because its users do not have root access and software configurations cannot be customized, despite the fact that physical resources are also multiplexed. A virtual private server on the other hand, contains its own unique file system and CGI-BIN, disk space, system resources, bandwidth and memory allotments, which allow for a high level of customization.

Due to the fact that a VPS solution truly simulates a dedicated server, some technical understanding of server administration is required. Any true VPS solution will provide users with: "root" or full administrative access; guarantee a specific allocation of server resources, including CPU, memory and bandwidth; and allow the user to manage multiple servers and file areas through a sophisticated control panel.

A virtual private server will ensure "performance isolation" so that heavy traffic or CPU loads will not affect other VPS solutions on the same infrastructure. Others major features that characterize VPS solutions include: "fault tolerance," which ensures that errors, which affect one specific private server, do not affect others; and "enhanced security," which ensures that e-business applications can be deployed with greater privacy.

The most popular feature that VPS customers use, however, is the virtual private server's capacity for "functional isolation." Because a VPS has its own contained services, it is possible for users to install and customize their own open-source and commercial software packages.

Many virtual private servers on the Unix platform have become so advanced that they even permit users to install Linux RPM packages. This allows users to take source code for new software and package it into source and binary form, such that binaries can be easily installed and tracked, and source can be easily rebuilt. The use of RPM packages also allows VPS users to maintain a database of all packages and their files that can be used for verifying packages and querying for information about files and/or packages.

Small businesses that run their own e-commerce Web sites also appreciate the functional isolation of their private server, because it allows them to obtain their own secure certificates and shopping cart software for their e-business operations. Many sophisticated VPS solutions will even offer third-party plug-ins or modules, allowing users to take advantage of control panel functionality in order to install everything from the simplest CGI scripts to the most advanced shopping carts.

Due to these advantages, virtual private servers are very popular and are a relatively inexpensive choice for small to mid-sized enterprises seeking to maintain their own Web presence. VPS solutions are the natural choice for SMEs and individuals wishing to upgrade a shared or virtual hosting package. The following are descriptions of popular VPS packages now available through an assortment of major Web host vendors:

Ensim
Ensim's award-winning product line includes control panels, virtual private servers, server management, as well as Microsoft Exchange hosting software.

H-Sphere
Hsphere is scalable multi-server, centralized hosting automation software with fully brandable resellers support, comprehensive recurrent billing, trouble ticket system as well as complete account provisioning automated signup. It supports Win2000, Linux & FreeBSD. It provides fully features, easy-to-use end user web based control panel, and powerful admin user interface.

SW-soft
SW-soft develops the Virtuozzo technology and the HSPcomplete hosting automation solution. SWsoft's products deliver powerful, comprehensive solutions that power data center management and provide excellent return on investment.

Sphera
Sphera is a leading developer of Web hosting automation and management software for Internet data centers, ISPs and hosting providers. Sphera's HostingDirector enables cost-cutting and revenue increases by automating Web hosting management, facilitating sales of value added applications, services and more.

These above hosting software firms develop popular and dependable VPS packages. Consider using a hosting firm that elects to use one of the above virtual private server systems.

An Introduction to Disk Space

2008-07-17T13:14:00.000-07:00

When you are looking for a Web hosting account, and even after you have signed up for an account, a lot of Web hosting jargon is thrown around. From bandwidth limits to server uptime, all of them are important.

When you buy a Web hosting account, you have to learn how to be a good Web hosting client. Once of the most important jargon keywords they will throw your way is disk space. So what is disk space?

Disk space is the space you actually rent on the Web hosting server. It is the place where you put all of your HTML files, images, scripts and anything else you might want to upload to your Web hosting account. You can also use disk space by creating email accounts on your Web hosting space. Each email account takes a little disk space so that you have room to store the messages on the Web hosting server.

Other customers rent space all around you on a shared server but most of the time you do not know who they are and they do not know who you are.

Web hosting accounts, and more importantly the disk space you are given in those accounts, can be any size at all, and some Web hosts offer more than others. It all depends on how much space is assigned to the Web hosting plan you purchased. As part of the plan, you are renting the space from the Web hosting provider.

For example, you might pay five dollars a month for Web hosting. You are renting the space for that amount of money. If you cannot pay for your rent, then you will be kicked out of the space you rent, and somebody else will take your lot.

Just a few years ago, Web hosting accounts were a lot more expensive than they are now, and you did not get close to what you are getting now. For a small Web hosting plan now, you might have payed four times as much, depending on the disk space and bandwidth, a few years ago.

These days though, things are a lot cheaper. With more data centers and bigger pipes on the Internet, we can get more bandwidth to and from our Web hosting accounts. Since the cost of hard drives has been going down, you are also able to get more disk space for less than you would have paid even five years ago.

Where is the world of disk space going in the future? Eventually prices will even out. With new technology though, hard drive space will grow and so will your Web hosting disk space. You will start getting even more bang for your buck in the future.

Once you decide to take that leap and purchase a Web hosting account, you do need to learn about every inch of the Web hosting world. Educating yourself about all the different parts of your Web hosting account will help you in the long run. And disk space is unmistakably one of those important parts. Without disk space, there could be no Web hosting at all.

Find Web Hosting for your Blog, Web Blog Hosting

2008-07-17T13:13:00.002-07:00

The following web hosting providers offer hosting for your web blog, personal web site, online photo gallery, family web site, email hosting, domain name hosting and more.

You want good and easy to use Blog, We provide technology and reliability. And one more thing! You pay less because you get Free .US or .CA Domain name. WordPress blog software we provide is the most popular blogging technology! Try it! Sign up for our Risk Free web hosting plans and enjoy good service and dedicated support!

Want to say whatever you want, however you want? WordPress blog is easy to setup, a cinch to manage, and a lot of fun to have! Pick a template, add your blog title, and you are ready to write your first post. Customize your blog to fit your personality now!

Open Source Vs Windows

2008-07-17T13:13:00.001-07:00

I know this subject is controversial, but here's what I have found in 25 years of experience. I use Windows, Linux, Unix, OpenVMS, FreeBSD and other operating systems all day long, and I am experienced with IIS and Apache. My conclusions are based upon actual testing and benchmarking, not rumor and articles by others.

Stick with the brand names for mission critical systems. Open source is fine for many things, but excluding the "big products" such as Mozilla, Apache and so forth, I am leery of it.

I would never even consider open source for the important things such as payroll, general ledger, accounting, warehouse operations and SCADA. These are the applications which companies actually use and need to stay in business.

I have never found anything that even approaches Office XP feature-for-feature. Office XP is rock solid, doesn't crash and is very secure. I cannot say the same for Staroffice, Wordperfect and the other competitors.

Windows 2000 and Windows XP are unmatched in quality as far as their market is concerned. Windows 2000 server is rock solid stable, has an incredible number of features and, most important of all, is supported and well documented.

Windows 2000 also has a security model which is unmatched in the industry. This model came from the VAX (Digital Equipment) and Novell, both of which were (and are) excellent. Linux and Unix don't really have a security model in comparison (I am referring, of course, to active directory and NTFS).

Of course, Windows has the well known issue of security exploits (a different issue than the security model). I currently manage quite an extensive farm of IIS servers, and I've found it's not that much work to keep these systems completely up-to-date. We just have to do our jobs as administrators.

IIS and Apache are equivalent in functionality.

IIS performs better than Apache (I've done the testing myself on the same machine) for straight HTML pages. IIS also has a better security model than Apache by far (based on NTFS as it is). IIS is also a heck of a lot easier to use than Apache, although you can certainly purchase GUI's for apache which make it usable for the average person. And the first major problems (including security) with Apache 2.0 have started appearing, and they are just as nasty as anything found in IIS.

To my way of thinking the main reason to prefer Apache over IIS is (a) initial cost, and (b) knowledge of your people. If you and your group already know apache, then that is the best choice for you. If you already know IIS, then that is probably the best choice.

Browsers? IE won the browser wars for a good reason (besides ruthlessness) - it's far superior to Netscape 6 and before. Now that Mozilla and Opera have had a couple of years, it looks like they might give IE a run for it's money. Even now, though, I've found IE is superior to the competition and I'm sure there is a new version in the works.

But all of this is not as relevant as the cost of modifications. I've found the initial cost of the software, regardless of what it is, is puny compared to the cost of modifications. I would never even consider hiring programmers, for example, to modify the OS, the browser, or the web server, so the availability of sources is not relevant. As far as an application system is concerned, I am interested in modifying the business rules, not the application itself. In fact, if my accounting system requires me to modify it's primary code just to change a business rule, I'll find something else.

There are many companies which provide good application systems, including SAP, Ultipro and hundreds of others. To date, not one open-source version of these (the really important things) has even made it to the initial RFP.

I find the "religious wars" about this subject fascinating. Ask Apache admins and they will tell you Apache is best and death to all unbelievers. Ask IIS admins and you will get the same story. same with Windows, Linux and OpenVMS and any other similar thing. I personally believe we all like what we like and are used to. What I personally like to do is ignore the hype and rumors and so forth and do my own analysis. And yes, I ignore Microsoft hype as well ... they have more PR skills than any hundred other organizations. But PR does not make for a good product.

The decision to use or not use a product should depend upon rational facts, not opinions and noise. Apache is in many ways better than IIS, and IIS is in many ways better than Apache. Which is better? Depends upon what you are using it for, the goals of your organization and many other things. Same with Windows Vs Linux, or any other argument.

Our experience, and keep in mind this is for corporate intranet web servers, is that the cost of Windows and IIS over a long term (5+ years) is far, far less than the cost of Linux and Apache. We performed our own internal study and factored in the cost of the software, maintenance costs, upgrades, time to support, training and so on. Windows 2000 server came out far ahead of Linux (even with all of the patching) and IIS came out ahead of Apache. I have only just installed Apache 2.0 on a windows platform and so have not formed any opinions on this product yet. In a few months, perhaps, I will have some solid data about what appears to be a great new release of Apache.

Cost, however, should never be the primary criteria of this kind of decision. Cost is the least important of many different factors which go into a decision. I have found over my career that when I chose something based upon cost as a primary factor I wound up with that sore behind feeling. Yet when I chose something based upon features and requirements and a good analysis, then picked the product which fit the best, then and only then was it comfortable sitting down.

I have found that Apache (with a good front-end GUI) is superior for a hosting solution. I like Apache in this environment because it gives the users (webmasters for small and medium sized shared hosting web sites) more flexibility without the server admin needing to get involved.

Linux is a great server platform, although we have found the cost to support, train and maintain is higher than windows 2000. As a desktop, though, Linux isn't even on the same planet as Windows XP. Linux has a long way (and I mean light years) to go before it is anywhere near Windows XP as a desktop solution for corporations.

How Much is 100 Percent?

2008-07-17T13:12:00.000-07:00

The Web hosting market has changed dramatically over the years, with consolidation and price cutting making the services more affordable, but also reducing the number of choices available to businesses. More hosting companies are also trying to bundle services in order to derive more revenue from the surviving business customers they have left.

In addition to providing rack space and managing servers and storage, many hosting service providers also look to manage the applications that run on their customers' Web sites. Reliability is critical in the Web hosting arena, and competitive pressures are even driving a few hosting providers to make unrealistic promises. In February, for example, Electronic Data Systems offered a service level agreement that promised 100 percent availability for Web sites and applications that EDS is hosting. This is raising the bar pretty high.

Other service providers have often promised 99.99 percent (commonly referred to as "four nines") uptime, which gives them a cushion of about 53 minutes of outage time a year when they can down the servers briefly for regularly scheduled maintenance. A few have even touted "five nines," or 99.999 percent availability, which narrows the margin for error considerably.

While these claims are suspect in their own right, promising 100 percent uptime seems to be over-reaching a little bit further. Even if you offer "nines to the nth degree" availability, you're still not going so far as guaranteeing 100 percent availability. One hundred percent availability doesn't leave much room for mistakes and disasters, especially these days when there's so much for Webmasters to worry about, from cyberterrorism threats to over-subscribed Webcasts that overload the server.

We all know that Internet connections go down, that Web sites become temporarily unavailable or fall prey to denial of service attacks. It's not uncommon for an errant Java script to crash a Web application. Indeed, EDS seems to be hedging the uninterrupted claim, backing the offer with a "time-to-repair commitment as short as 15 minutes for fully redundant systems" and providing service credits that accumulate from the first minute of downtime. That's certainly comforting if you're worried that the actual uptime might fall a little short of the 100 percent mark.

The "fully redundant" part also sounds a little fishy. Does that mean you have an extra hard drive mirroring your hard drive, and maybe a third drive just for grins? How about an extra server mirroring your server, and uninterruptible power supplies backing up the electricity for the servers, disk arrays, and air conditioner, and while you're at it, an extra system administrator so one of them can go to lunch.

The Web hosting market has grown more competitive with today's economic slowdown. With fewer companies launching Web sites and scaling back plans for multimedia Webcasts and similar brand-building and bandwidth-hogging activities, hosting providers have needed to focus on niche industries and promote unique capabilities to differentiate themselves.

The claim of perfect uptime is one such strategy. So 100 percent uptime doesn't necessarily mean availability around the clock 24/7/365. You can just see EDS founder Ross Perot snickering about that bit of slick salesmanship.

Old Ross moved on from EDS years ago to hang out with Larry King, but his spirit still lives on. And you can just hear the "giant sucking sound," as Perot put it, while this claim deflates on its own dubious merits.

Glossary of Web Hosting Terms

2008-07-17T13:10:00.000-07:00

Access Microsoft's advanced database creation and maintenance software. It is very popular among developers who maintain online databases with Windows NT.

Active Server Page (ASP) ASPs are HTML documents embedded with scripts (typically Microsoft's VB Script or Jscript). These scripts are processed by the server prior to being transferred to the user.

ActiveX A set of properties that define how applications are to share information with each other. These properties are known as controls.

Aliased Nameservers An aliased nameserver is a nameserver that has been labeled as yours (the reseller's) despite the fact it actually belongs to your Web hosting provider. This ensures that domains located on your server are listed as "ns.yourservername.com" instead of "ns.yourprovidersname.com". Also see NAMESERVER below.

Apache One of the world's most popular Web server programs, Apache was built by a group of open-source programmers and is often used because of its outstanding performance, strong security features and the fact that it is free.

Application Service Provider A third party that manages software applications for servers and networks.

Bandwidth The amount of data that can be transmitted at a given moment to a server. The higher your bandwidth, the larger amount of traffic your site can handle at one time.

CGI Short for Common Gateway Interface, a small script that processes data taken from the user (such as from a form application).

Cgi-bin The directory on a Web server where CGI scripts are stored.

Co-located hosting This hosting option gives webmasters complete control over their server. You are responsible for providing the physical hardware and network administration; the hosting company will provide you with the rack space and Internet connection.

Cookie A text file sent to a user's Web browser from a Web server. Cookies are typically exchanged back and forth between the two in order to prepare custom content for users, and to exchange data like registration information.

Dedicated hosting A hosting feature that allows a Web site to have its own server. This is more flexible than shared hosting (see below), as webmasters typically have full control over the back end of the server, including choice of OS. Administration, however, is still handled by the hosting company.

Diesel Generator A diesel-powered generator used by hosting companies as a back-up source to generate electricity in the event of a power outage.

Domain names Domain names are the word sequences users enter in their URL bar to visit your site. They are attached to a DNS, short for Domain Naming System, which is used to translate numeric addresses (known as IP, or Internet Protocol, addresses) into words. Each site you visit on the net has a numeric IP address behind its name.

Firewall A piece of security software designed to protect Web servers. They are typically used to protect sites from hacker attacks/unauthorized access.

Flash A popular piece of animation software developed by Macromedia. Flash is widely used on the Web because it requires little bandwidth, therefore making it friendly to users with low or high-speed connections.

FrontPage A popular site design and management tool developed by Microsoft.

FTP Short for File Transfer Protocol, a method of allowing remote users and Web servers to exchange files.

HTML Short for HyperText Markup Language, the language by which Web servers and client browsers communicate. All server-side functions (such as database processing), although they may be performed in another language, must eventually be output back to the user in HTML.

HTTP Stands for HyperText Transfer Protocol, the protocol by which HTML files move across the Internet. HTTP requires a client browser and an HTTP server (typically a Web server).

IIS Short for Internet Information Server, Microsoft's server software for Windows NT/2000.

Intranet A vast internal network structured in a fashion similar to the Internet. Intranets are usually established by large corporate organizations to improve communication. The main difference between the Internet and an intranet is that access to intranets are restricted to authorized members only.

IP Short for Internet Protocol, which designates the format of "data packets" that are used to exchange information over the Internet.

IRC Short for Internet Relay Chat, a popular text-base multi-user chat network.

ISDN Short for Integrated Services Digital Network, a high-speed solution to moving data over phone lines. It can transfer data at approximately 128,000 bits per second over a standard land line.

Load Balancing Distributing data across a network of servers in order to ensure that a single Web server does not get overloaded with work, thereby affecting performance.

Managed hosting A dedicated server that is accompanied by a full suite of technical support, maintenance and monitoring services. This differs from dedicated Web hosting, where customers are provided with their own servers but are still responsible for virtually all administrative and maintenance duties.

MIME Short for Multipurpose Internet Email Extensions, a protocol that allows users to transfer non-text messages like audio, video and images through e-mail.

Mirror sites A mirror site is an exact copy of another FTP or Web site. These are used to offset/spread traffic load on busy Web sites.

MS Index Server An add-on for Microsoft Internet Information server (see above) that indexes documents on Web or Intranet servers running IIS. The information is then presented to users in a searchable format.

Name server A server responsible for translating domain names and IP addresses.

Newsgroup A USENET discussion group (see below).

NOC Short for Network Operations Center, a hosting company's "home base," so to speak. The NOC is usually where most administration, technical support and physical server storage takes place. For more information, please refer to our article, Inside the NOC, here.

OC Short for Optical Carrier, representing the speed of fiber-optic networks. OC speeds can range anywhere between 1 and 48. Most hosting companies have OC3 connections, which allows for the transfer of data at a rate of up to 155.52 Mbps.

Packet switching The method by which most data is exchanged throughout the Internet. Most data is broken down in to smaller "packets" prior to transfer, and then reassembled at the destination.

Parking All domain names have to be stored on a server in order to be purchased. Most domain registration services will therefore temporarily place a newly purchased name on their servers until a hosting plan is purchased or the owner points the DNS to a different site. This is known as parking.

POP Short for Post Office Protocol. An e-mail protocol that mail software such as Eudora use to communicate with mail servers.

Propagation The process where name servers throughout the Internet add new domains and remove expired ones from their records. This can be a lengthy process, which is why connecting to a new domain name can often take three or four days.

RAID Short for Redundant Array of Independent Disks, a method of data protection/backup. Data is stored over a number of servers so that information will still be accessible if a piece of hardware/software crashes.

Reseller A reseller operates components of a Web hosting operation using services, infrastructure and equipment provided by another Web hosting service. Some resellers operate full-fledged businesses using the hardware, software, network and logistical support of another Web hosting firm, while others simply operate as sales agents for other Web hosting companies, offering discounts and providing low-level technical support.

Scalability The ability of a piece of software or hardware to expand/grow as necessary.

Shared hosting The most basic of Web hosting types. With shared hosting, numerous Web sites are shared on one server. While an economic solution, they typically cannot handle large amounts of storage or traffic.

Shopping cart A program designed to handle the e-commerce section of a Web site. Shopping cart software lets users browse for and purchase products online.

SMTP Short for Simple Mail Transfer Protocol, a protocol used by mail servers to exchange messages with each other.

SQL Short for Standard Query Language. A standard protocol used to request information from databases. Servers which can handle SQL are known as SQL servers.

SSL Short for Secure Sockets Layer, a protocol developed by Netscape to handle and protect confidential/sensitive information required for e-commerce transactions (like credit card numbers). SSL address usually begin with 'https'.

Subdomain Typically known as a "domain within a domain", subdomains are individual Web addresses built upon a pre-existing domain name (such as clientname.yourhostingcompany.com). As a reseller, you will have the option of assigning subdomains to clients if they do not choose to have a domain name.

T1 Connection A phone or data connection that can support the transfer of up to 1.544Mbits of data per second. T1 connections are popular among businesses and ISPs. Most T1s are connected to T3, which can handle up to 43Mbits per second and are actual Internet backbone connections.

Tape back-up A popular and inexpensive way to back up Web sites. Contents of a site are periodically stored that looks similar to a cassette. Some cassettes can store several gigabytes.

Telnet A command-line interface that allows remote users and Web servers to communicate.

TCP Short for Transmission Control Protocol, an important network protocol. TCP allows two hosts to connect and exchange data, and ensures that "data packets" are delivered exactly as sent.

TLD Shot for Top Level Domain, the suffix for major domain names like .com, .net and .org.

UNIX A text-based, multitasking Operating System suitable for Web and network administration. Unix has spawned numerous popular spinoffs, including Linux and FreeBSD. Most Unix-based Operating Systems are open source, meaning the source code to the Operating System has been made freely available to the public for modification. Most Web hosting companies and resellers offer Unix-based hosting in some capacity or other.

USENET A network of thousands of discussion groups (known as newsgroups; see above) on the Internet.

UUENCODE Short for Unix to Unix Encoding, a method of converting images to ASCII (see above) text in order to be transferred over the Internet.

Virtual host A shared hosting solution, the most basic of hosting types. Numerous Web sites are shared on one server.

Virtualization A process/software designed to reduce server management costs through automation, while providing more control over service levels.

Virtual Private Server (VPS) A virtual private server provides the features of a dedicated server on a machine that is shared by other Web hosting customers. Customers therefore get hosting services that are similar to that of dedicated Web hosting without sacrificing privacy or performance.

WHOIS A central database which tracks all domain name/IP registrations.

Windows NT/2000 These are graphic-based, multitasking Operating Systems developed over the past few years by Microsoft. Both can act as standalone OS for personal computers/workstations, or can serve as an OS for a Web site/network. Most Web hosting companies and resellers offer Windows-based hosting in some capacity or other.

XML Short for Extensible Markup Language. XML is a language allowing developers to create their own markup tags. All XML tags are defined by the programmer, and can be interpreted differently in different applications. For example, the "" tag in HTML means Italics, but could mean anything in XML, depending on the function the developer assigns to it.

Step 32 & 33 Check for cluster Stabilize & VG varied on

2008-07-12T11:36:00.000-07:00

Wait for the cluster to stabilize. You can check when the cluster is up by following
commands
a. netstat –i
b. ifconfig –a : look-out for service ip. It will show on each node if the cluster is up.

Check whether the VGs under cluster’s RGs are varied-ON and the filesystems in the
VGs are mounted after the cluster start.

Here test1vg and test2vg are VGs which are varied-ON when the cluster is started and
Filesystems /test2 and /test3 are mounted when the cluster starts.
/test2 and /test3 are in test2vg which is part of the RG which is owned by this node.
32. Perform all the tests such as resource take-over, node failure, n/w failure and verify
the cluster before releasing the system to the customer.

step 30 & 31 Synchronize & start Cluster

2008-07-12T11:34:00.001-07:00

Synchronize the cluster:
This will sync the info from one node to second node.
Smitty cl_sync

That’s it. Now you are ready to start the cluster.
Smitty clstart

You can start the cluster together on both nodes or start individually on each node.

You can start the cluster together on both nodes or start individually on each node.

step 29 Adding IP label & RG owned by Node

2008-07-12T11:34:00.000-07:00

Add the service IP label for the owner node and also the VGs owned by the owner node
Of this resource group.

step 28 Setting attributes of Resource group

2008-07-12T11:33:00.000-07:00

Set attributes of the resource groups already defined:
Here you have to actually assign the resources to the resource groups.
smitty hacmp -> Extended Configuration -> Extended Resource Configuration ->
HACMP extended resource group configuration

step 27 Adding Resource Group

2008-07-12T11:32:00.003-07:00

Add Resource Groups:
smitty hacmp -> Extended Configuration -> Extended Resource Configuration ->
HACMP extended resource group configuration

Continue similarly for all the resource groups.
The node selected first while defining the resource group will be the primary owner of
that resource group. The node after that is secondary node.
Make sure you set primary node correctly for each resource group. Also set the failover/fallback policies as per the requirement of the setup

step 26 Defining IP labels

2008-07-12T11:32:00.002-07:00

Define the service IP labels for both nodes.
smitty hacmp -> Extended Configuration -> Extended Resource Configuration ->
HACMP extended resource configuration -> Configure HACMP service IP label

step 25 Adding Persistent IP labels

2008-07-12T11:32:00.001-07:00

Add a persistent ip label for both nodes.

step 24 Adding persistent IP

2008-07-12T11:31:00.000-07:00

Add the persistent IPs:

smitty hacmp -> Extended Configuration -> Extended Topology Configuration ->
Configure HACMP persistent nodes IP label/Addresses

step23 Adding boot IP & Disk heart beat information

2008-07-12T11:30:00.001-07:00

Include all the four boot ips (2 for each nodes) in this ether interface already defined.Then include the disk for heartbeat on both the nodes in the diskhb already defined

step 22 Adding device for Disk Heart Beat

2008-07-12T11:30:00.000-07:00

Include the interfaces/devices in the ether n/w and diskhb already defined.
smitty hacmp -> Extended Configuration -> Extended Topology Configuration ->
Configure HACMP communication interfaces/devices -> Add communication
Interfaces/devices.

Step21 Adding Communication interface

2008-07-12T11:29:00.001-07:00

Add HACMP communication interfaces. (Ether interfaces.)
smitty hacmp -> Extended Configuration -> Extended Topology Configuration ->
Configure HACMP networks -> Add a network to the HACMP cluster.
Select ether and Press enter.
Then select diskhb and Press enter. Diskhb is your non-tcpip heartbeat.

Step20 Discover HACMP config for Network settings

2008-07-12T11:29:00.000-07:00

22. Discover HACMP config: This will import for both nodes all the node info, boot ips,
service ips from the /etc/hosts
smitty hacmp -> Extended configurations -> Discover hacmp related information

Step 19 Define Cluster Nodes

2008-07-12T11:27:00.003-07:00

19. Define the cluster nodes. #smitty hacmp -> Extended Configuration -> Extended topology configuration -> Configure an HACMP node - > Add a node to an HACMP cluster Define both the nodes on after the other.

Step 18 to configure HACMP

2008-07-12T11:27:00.002-07:00

18. Define cluster name.

Steps 1 to 17 to configure HACMP

2008-07-12T11:27:00.001-07:00

Steps to configure HACMP:

1. Install the nodes, make sure the redundancy is maintained for power supplies, n/w and
fiber n/ws. Then Install AIX on the nodes.
2. Install all the HACMP filesets except HAview and HATivoli.
Install all the RSCT filesets from the AIX base CD.
Make sure that the AIX, HACMP patches and server code are at the latest level (ideally
recommended).
4. Check for fileset bos.clvm to be present on both the nodes. This is required to make the
VGs enhanced concurrent capable.
5. V.IMP: Reboot both the nodes after installing the HACMP filesets.
6. Configure shared storage on both the nodes. Also in case of a disk heartbeat, assign a
1GB shared storage LUN on both nodes.
7. Create the required VGs only on the first node. The VGs can be either normal VGs or
Enhanced concurrent VGs. Assign particular major number to each VGs while creating
the VGs. Record the major no. information.
To check the Majar no. use the command:
ls –lrt /dev grep
Mount automatically at system restart should be set to NO.
8. Varyon the VGs that was just created.
9. V.IMP: Create log LV on each VG first before creating any new LV. Give a unique
name to logLV.
Destroy the content of logLV by: logform /dev/loglvname
Repeat this step for all VGs that were created.
10. Create all the necessary LVs on each VG.
11. Create all the necessary file systems on each LV created…..you can create mount pts
as per the requirement of the customer,
Mount automatically at system restart should be set to NO.
12. umount all the filesystems and varyoff all the VGs.

13. chvg –an ---All VGs will be set to do not mount automatically at
System restart.
14. Go to node 2 and run cfgmgr –v to import the shared volumes.
15. Import all the VGs on node 2
use smitty importvg -----import with the same major number as assigned on node
16. Run chvg –an for all VGs on node 2.
17. V.IMP: Identify the boot1, boot2, service ip and persistent ip for both the nodes
and make the entry in the /etc/hosts.

HACMP v5.x Disk Heartbeat device configuration

2008-07-12T11:26:00.001-07:00

Creating a Disk Heartbeat device in HACMP v5.x

Introduction
This document is intended to supplement existing documentation on how to configure, test, and monitor a disk heartbeat device and network in HACMP/ES V 5.x. This feature is new in V5.1, and it provides another alternative for non-ip based heartbeats. The intent of this document is to provide step-by-step directions as they are currently sketchy in the HACMP v5.1 pubs. This will hopefully clarify several misconceptions that have been brought to my attention.
This example consists of a two-node cluster (nodes GT40 & SL55) with shared ESS vpath devices. If more than two nodes exist in your cluster, you will need N number or non-ip heartbeat networks. Where N represents the number of nodes in the cluster. (i.e. three node cluster requires 3 non-ip heartbeat networks). This creates a heartbeat ring.
It’s worth noting that one should not confuse concurrent volume groups with concurrent resource groups. And note, there is a difference between concurrent volume groups and enhanced concurrent volume groups. A concurrent resource group is one which may be active on more than one node at a type. A concurrent volume group also shares the characteristic that it may be active on more than one node at a time. This is also true for an enhanced concurrent VG; however, in a non-concurrent resource group, the enhanced concurrent VG, while it may be active and not have a SCSI reserve residing on the disk, it’s data is only normally accessed by one system at a time.

Pre-Reqs

In this document, it is assumed that the shared storage devices are already made available and configured to AIX, and that the proper levels of RSCT and HACMP are already installed. Since utilizing enhanced-concurrent volume groups, it is also necessary to make sure that bos.clvm.enh is installed. This is not normally installed as part of a HACMP installation via the installp command.
Disk Heartbeat Details
This provides the ability to use existing shared disks, regardless of disk type, to provide a serial network like heartbeat path. A benefit of this is that one need not dedicate the integrated serial ports for HACMP heartbeats (if supported on the subject systems) or purchase an 8-port asynchronous adapter.
This feature utilizes a special area on the disk previously reserved for “Concurrent Capable” volume groups (traditionally only for SSA disks). Since AIX 5.2 dropped support for the SSA concurrent volume groups, this fit makes it available for use. This also means that the disk chosen for serial heartbeat can be part of a data volume group. (Note Performance Concerns below)

The disk heart beating code went into the 2.2.1.30 version of RSCT. Some recommended APARs bring that to 2.2.1.31. If you've got that level installed, and HACMP 5.1, you can use disk heart beating. The relevant file to look for is /usr/sbin/rsct/bin/hats_diskhb_nim. Though it is supported mainly through RSCT, we recommend AIX 5.2 when utilizing disk heartbeat.

To use disk heartbeats, no node can issue a SCSI reserve for the disk. This is because both nodes using it for heart beating must be able to read and write to that disk. It is sufficient that the disk be in an enhanced concurrent volume group to meet this requirement. (It should also be possible to use a disk that is in no volume group for disk heart beating. RSCT certainly won't care; but HACMP SMIT panels may not be particularly helpful in setting this up.)

Now, in HACMP 5.1 with AIX 5.1, enhanced concurrent mode volume groups can be used only in concurrent (or "online on all available nodes") resource groups. This means that disk heart beating is useful only to people running concurrent configurations, or who can allocate such a volume group/disk (which is certainly possible, though perhaps an expensive approach). In other words, at HACMP 5.1 and AIX 5.1, typical HACMP clusters (with a server and idle standby) will require an additional concurrent resource group with a disk in an enhanced concurrent VG dedicated for heartbeat use. At AIX 5.2, disk heartbeats can exist on an enhanced concurrent VG that resides in a non-concurrent resource group. At AIX 5.2, one may also use the fast disk takeover feature in non-concurrent resource groups with enhanced concurrent volume groups. With HACMP 5.1 and AIX 5.2, enhanced concurrent mode volume groups can be used in serial access configurations for fast disk takeover, along with disk heart beating. (AIX 5.2 requires RSCT 2.3.1.0 or later) That is, the facility becomes usable to the average customer, without committment of additional resource, since disk heart beating can occur on a volume group used for ordinary filesystem and logical volume activity.

Performance Concerns with Disk Heart Beating

Most modern disks take somewhere around 15 milliseconds to service an IO request, which means that they can't do much more than 60 seeks per second. The sectors used for disk heart beating are part of the VGDA, which is at the outer edge of the disk, and may not be near the application data. This means that every time a disk heart beat is done, a seek will have to be done. Disk heart beating will typically (with the default parameters) require four (4) seeks per second. That is each of two nodes will write to the disk and read from the disk once/second, for a total of 4 IOPS. So, if possible, a disk should be selected as a heart beat path that does not normally do more than about 50 seeks per second. The filemon tool can be used to monitor the seek activity on a disk.

In cases where a disk must be used for heart beating that already has a high seek rate, it may be necessary to change the heart beat timing parameters to prevent long write delays from being seen as a failure.

The above cautions as stated apply to JBOD configurations, and should be modified based on the technology of the disk subsystem:
• If the disk used for heart beating is in a controller that provides large amounts of cache - such as the ESS - the number of seeks per second can be much larger
• If the disk used for heart beating is part of a RAID set without a caching front end controller, the disk may be able to support fewer seeks, due to the extra activity required by RAID operations
Pros & Cons of using Disk Heart Beating
Pros:
1. No additional hardware needed.
2. Easier to span greater distances.
3. No loss in usable storage space and can use existing data volume groups.
4. Uses enhanced concurrent vgs which also allows for fast-disk takeover.

Cons:
1. Must be aware of the devices diskhb uses and administer devices properly*
2. Lose the forced down option of stopping cluster services because of enhanced concurrent vg usage.

*I have had a customer delete all their disk definitions and run cfgmgr again to clean up number holes in their device definition list. When they did, obviously , the device names did not come back in the same order as they were before. So the diskhb device assigned to HACMP, was no longer valid as a different device was configured using the old device name and it was not part of an enhanced concurrent vg. Hence diskhb no longer worked, and since the customer did not monitor their cluster either, they were unaware that the diskhb no longer worked.

Configuring Disk Heartbeat

As mentioned previously, disk heartbeat utilizes enhanced-concurrent volume groups. If starting with a new configuration of disks, you will want to create enhanced-concurrent volume groups, either manually, or by utilizing C-SPOC. My example shows using C-SPOC which is the best practice to use here.

If you plan to use an existing volume group for disk heartbeats that is not enhanced concurrent, then you will have to convert them to such using the chvg command. We recommend that the VG be active on only one node, and that the application not be running when making this change run chvg –C vgname to change the VG to enhanced concurrent mode. Vary it off, then run importvg –L vgname on the other node to make it aware that the vg is now enhanced concurrent capable. If using this method, you can skip to the “Creating Disk Heartbeat Devices and Network” section of this document.

Disk and VG Preparation

To be able to use C-SPOC successfully, it is required that some basic IP based topology already exists, and that the storage devices have their PVIDs in both system’s ODMs. This can be verified by running lspv on each system. If a PVID does not exist on each system, it is necessary to run chdev -l -a pv=yes on each system. This will allow C-SPOC to match up the device(s) as known shared storage devices.
In this example, vpath0 on GT40 is the same virtual disk as vpath3 on SL55.
Use C-SPOC to create an Enhanced Concurrent volume group. In the following example, since vpath devices are being used, the following smit screen paths were used.
smitty cl_adminGo to HACMP Concurrent Logical Volume Management Concurrent Volume Groups Create a Concurrent Volume Group with Data Path Devices and press Enter

Choose the appropriate nodes, and then choose the appropriate shared storage devices based on pvids (vpath0 and vpath3 in this example). Choose a name for the VG , desired PP size, make sure that Enhanced Concurrent Mode is set to true and press Enter. (enhconcvg in this example). This will create the shared enhanced-concurrent vg needed for our disk heartbeat. .

It’s a good idea to verify via lspv once this has completed to make sure the device and vg is show appropriately as follows:

GT40#/ lspv
vpath0 000a7f5af78e0cf4 enhconcvg

SL55#/lspv
vpath3 000a7f5af78e0cf4 enhconcvg

Creating Disk Heartbeat Devices and Network

There are two different ways to do this. Since we have already created the enhanced concurrent vg, we can use the discovery method (1) and let HA find it for us. Or we can do this manually via the Pre-defined devices method (2). Following is an example of each.

1) Creating via Discover Method: (See Note)
Enter smitty hacmpExtended ConfigurationDiscover HACMP-related Information from Configured NodesPress Enter

This will run automatically and create a clip_config file that contains the information it has discovered. Once completed, go back to the Extended Configuration menu and chose:

Extended Topology ConfigurationConfigure HACMP Communication Interfaces/DevicesAdd Communication Interfaces/DevicesAdd Discovered Communication Interface and DevicesCommunication Devices Choose appropriate devices (ex. vpath0 and vpath3)

Select Point-to-Point Pair of Discovered Communication Devices to Add
Move cursor to desired item and press F7. Use arrow keys to scroll.
ONE OR MORE items can be selected.
Press Enter AFTER making all selections.
# Node Device Device Path Pvid
> nodeGT40 vpath0 /dev/vpath0 000a7f5af78
> nodeSL55 vpath3 /dev/vpath3 000a7f5af78

Note: Base HA 5.1 appears to have a problem when using the Discovered Devices this method. If you get this error: "ERROR: Invalid node name 000a7f5af78e0cf4".
Then you will need apar IY51594. Otherwise you will have to create via the Pre-Defined Devices method. Once corrected, this section will be completed
2) Creating via Pre-Defined Devices Method

When using this method, it is necessary to create a diskhb network first, then assign the disk-node pair devices to the network. Create the diskhb network as follows:

smitty hacmp  Extended Configuration  Extended Topology Configuration Configure HACMP Networks Add a Network to the HACMP cluster  choose diskhb  Enter desired network name (ex. disknet1)--press Enter

smitty hacmp  Extended Configuration  Extended Topology Configuration  Configure HACMP Communication Interfaces/Devices  Add Communication Interfaces/Devices Add Pre-Defined Communication Interfaces and Devices 
Communication Devices  Choose your diskhb Network Name 

Add a Communication Device

Type or select values in entry fields.
Press Enter AFTER making all desired changes.

[Entry Fields]
* Device Name [GT40_hboverdisk]
* Network Type diskhb
* Network Name disknet1
* Device Path [/dev/vpath0]
* Node Name [GT40]

For Device Name, that is a unique name you can chose. It will show up in your topology under this name, much like serial heartbeat and ttys have in the past.

For the Device Path, you want to put in /dev/. Then choose the corresponding node for this device and device name (ex. GT40). Then press Enter.

You will repeat this process for the other node (ex. SL55) and the other device (vpath3). This will complete both devices for the diskhb network.

Testing Disk Heartbeat Connectivity

Once the device and network definitions have been created, it is a good idea to test it and make sure communications is working properly. If the volume group is varied on in normal mode on one of the nodes, the test will probably not work.

/usr/sbin/rsct/bin/dhb_read is used to test the validity of a diskhb connection. The usage of dhb_read is as follows:

dhb_read -p devicename //dump diskhb sector contents
dhb_read -p devicename -r //receive data over diskhb network
dhb_read -p devicename -t //transmit data over diskhb network

To test that disknet1, in the example configuration, can communicate from nodeB(ex. SL55) to nodeA (ex. GT40), you would run the following commands:

On nodeA, enter:

dhb_read -p rvpath0 -r

On nodeB, enter:

dhb_read -p rvpath3 -t

Note: That the device name is raw device as designated with the “r” proceeding the device name.

If the link from nodeB to nodeA is operational, both nodes will display:

Link operating normally.

You can run this again and swap which node transmits and which one receives. To make the network active, it is necessary to sync up the cluster. Since the volume group has not been added to the resource group, we will sync up once instead of twice.

Add Shared Disk as a Shared Resource

In most cases you would have your diskhb device on a shared data vg. It is necessary to add that vg into your resource group and synchronize the cluster.

smitty hacmp Extended Configuration Extended Resource Configuration > Extended Resource Group Configuration Change/Show Resources and Attributes for a Resource Group and press Enter.

Choose the appropriate resource group, enter the new vg (enhconcvg) into the volume group list and press Enter.

Return to the top of the Extended Configuration menu and synchronize the cluster.

Monitor Disk Heartbeat

Once the cluster is up and running, you can monitor the activity of the disk (actually all) heartbeats via lssrc -ls topsvcs. An example of the output follows:

Subsystem Group PID Status
topsvcs topsvcs 32108 active

Network Name Indx Defd Mbrs St Adapter ID Group ID
disknet1 [ 3] 2 2 S 255.255.10.0 255.255.10.1
disknet1 [ 3] rvpath3 0x86cd1b02 0x86cd1b4f
HB Interval = 2 secs. Sensitivity = 4 missed beats
Missed HBs: Total: 0 Current group: 0
Packets sent : 229 ICMP 0 Errors: 0 No mbuf: 0
Packets received: 217 ICMP 0 Dropped: 0
NIM's PID: 28724

Be aware that there is a grace period for heartbeats to start processing. This is normally around 60 seconds. So if you run this command quickly after starting the cluster, you may not see anything at all until heartbeat processing is started after the grace period time has elapsed.

HACMP failover scenario

2008-07-12T11:26:00.000-07:00

HA failover scenarios

1. Graceful
For graceful failover, you can run “smitty clstop” then select graceful option. This will not change anything except stopping the cluster on that node.
Note: If you stop the cluster, check the status using lssrc –g cluster, sometimes clstrmgrES daemon will take long time to stop, DO NOT KILL THIS DAEMON.It will stop automatically after a while.
You can do this on both the nodes

2. Takeover
For takeover, run “smitty clstop” with takeover option, this will stop the cluster on that node and the standby node will take over the pakage
You can do this on both the nodes

3. Soft Pakckage Failover
Run smitty cm_hacmp_resource_group_and_application_management_menu >>>Move a Resource Group to Another Node >>>>select the package name and node name >>>enter
This will move the package from that node to the node that you have selected in the above menu. This method will give lot of troubles in HA 4.5 whereas it runs good on HA 5.2 unless we have any apps startup issues.
You can do this on both the nodes
│
4. Failover Network Adapter(s):
For this type of testing , run “ifconfig enx down” , then package IP will failover to primary adapter. You can not even see any outage or anything.

We can manually (ifconfig enx up) bring it back to original adapter , but better to reboot the server to bring the package back to the original node

5. Hardware Failure (crash):
This is a standard type of testing; run the command “reboot –q” then the node will godown without stopping any apps and come up immediately. The package will failover to the standby node with in 2 min os downtime (Even tough HA failover is fast, some apps will take long time to start

Specifying the default gateway on a specific interface in HACMP

2008-07-12T11:25:00.002-07:00

Specifying the default gateway on a specific interface

When you're using HACMP, you usually have multiple network adapters installed and thus multiple network interface to handle with. If AIX configured the default gateway on a wrong interface (like on your management interface instead of the boot interface), you might want to change this, so network traffic isn't sent over the management interface. Here's how you can do this:

First, stop HACMP or do a take-over of the resource groups to another node; this will avoid any problems with applications when you start fiddling with the network configuration.

Then open up a virtual terminal window to the host on your HMC. Otherwise you would loose the connection, as soon as you drop the current default gateway.

Now you need to determine where your current default gateway is configured. You can do this by typing: lsattr -El inet0 and netstat -nr. The lsattr command will show you the current default gateway route and the netstat command will show you the interface it is configured on. You can also check the ODM: odmget -q"attribute=route" CuAt.

Now, delete the default gateway like this:
lsattr -El inet0 | awk '$2 ~ /hopcount/ { print $2 }' | read GW
chdev -l inet0 -a delroute=${GW}

If you would now use the route command to specifiy the default gateway on a specific interface, like this:
route add 0 [ip address of default gateway: xxx.xxx.xxx.254] -if enX
You will have a working entry for the default gateway. But... the route command does not change anything in the ODM. As soon as your system reboots; the default gateway is gone again. Not a good idea.

A better solution is to use the chdev command:
chdev -l inet0 -a addroute=net,-hopcount,0,,0,[ip address of default gateway]
This will set the default gateway to the first interface available.

To specify the interface use:
chdev -l inet0 -a addroute=net,-hopcount,0,if,enX,,0,[ip address of default gateway]
Substitute the correct interface for enX in the command above.

If you previously used the route add command, and after that you use chdev to enter the default gateway, then this will fail. You have to delete it first by using route delete 0, and then give the chdev command.

Afterwards, check with lsattr -El inet0 and odmget -q"attribute=route" CuAt if the new default gateway is properly configured. And ofcourse, try to ping the IP address of the default gateway and some outside address. Now reboot your system and check if the default gateway remains configured on the correct interface. And startup HACMP again!

HACMP topology & usefull commands

2008-07-12T11:25:00.001-07:00

Hacmp can be configured in 3 ways.

1. Rotating
2. Cascading
3. Mutual Failover

The cascading and rotating resource groups are the “classic”, pre-HA 5.1 types. The new “custom” type of resource group has been introduced in HA 5.1 onwards.

Cascading resource group:
Upon node failure, a cascading resource group falls over to the available node with the next priority in the node priority list.
Upon node reintegration into the cluster, a cascading resource group falls back to its home node by default.

Cascading without fallback
Thisoption, this means whenever a primary node fails, the package will failover to the next available node in the list and when the primary node comes online then the package will not fallback automatically. We need to move package to its home node at a convenient time.

Rotating resource group:
This is almost similar to Cascading without fallback, whenever package failover to the standby nodes it will never fallback to the primary node automatically, we need to move it manually at our convenience.

Mutual takeover:
Mutual takeover option, which means both the nodes in this type are active-active mode. Whenever fail over happens the package on the failed node will move to the other active node and will run with already existing package. Once the failed node comes online we can move the package manually to that node.

Useful HACMP commands

clstat - show cluster state and substate; needs clinfo.
cldump - SNMP-based tool to show cluster state
cldisp - similar to cldump, perl script to show cluster state.
cltopinfo - list the local view of the cluster topology.
clshowsrv -a - list the local view of the cluster subsystems.
clfindres (-s) - locate the resource groups and display status.
clRGinfo -v - locate the resource groups and display status.
clcycle - rotate some of the log files.
cl_ping - a cluster ping program with more arguments.
clrsh - cluster rsh program that take cluster node names as argument.
clgetactivenodes - which nodes are active?
get_local_nodename - what is the name of the local node?
clconfig - check the HACMP ODM.
clRGmove - online/offline or move resource groups.
cldare - sync/fix the cluster.
cllsgrp - list the resource groups.
clsnapshotinfo - create a large snapshot of the hacmp configuration.
cllscf - list the network configuration of an hacmp cluster.
clshowres - show the resource group configuration.
cllsif - show network interface information.
cllsres - show short resource group information.
lssrc -ls clstrmgrES - list the cluster manager state.
lssrc -ls topsvcs - show heartbeat information.
cllsnode - list a node centric overview of the hacmp configuration.

HACMP Basics

2008-07-12T11:24:00.001-07:00

History
IBM's HACMP exists for almost 15 years. It's not actually an IBM product, they bought it from CLAM, which was later renamed to Availant and is now called LakeViewTech. Until august 2006, all development of HACMP was done by CLAM. Nowadays IBM does it's own development of HACMP in Austin, Poughkeepsie and Bangalore

IBM's high availability solution for AIX, High Availability Cluster Multi Processing (HACMP), consists of two components:

•High Availability: The process of ensuring an application is available for use through the use of duplicated and/or shared resources (eliminating Single Points Of Failure – SPOF's)

.Cluster Multi-Processing: Multiple applications running on the same nodes with shared or concurrent access to the data.

A high availability solution based on HACMP provides automated failure detection, diagnosis, application recovery and node reintegration. With an appropriate application, HACMP can also provide concurrent access to the data for parallel processing applications, thus offering excellent horizontal scalability.

What needs to be protected? Ultimately, the goal of any IT solution in a critical environment is to provide continuous service and data protection.

The High Availability is just one building block in achieving the continuous operation goal. The High Availability is based on the availability hardware, software (OS and its components), application and network components.

The main objective of the HACMP is to eliminate Single Points of Failure (SPOF's)

“…A fundamental design goal of (successful) cluster design is the elimination of single points of failure (SPOFs)…”

Eliminate Single Point of Failure (SPOF)
Cluster Eliminated as a single point of failure

Node Using multiple nodes
Power Source Using Multiple circuits or uninterruptible
Network/adapter Using redundant network adapters
Network Using multiple networks to connect nodes.
TCP/IP Subsystem Using non-IP networks to connect adjoining nodes & clients
Disk adapter Using redundant disk adapter or multiple adapters
Disk Using multiple disks with mirroring or RAID
Application Add node for takeover; configure application monitor
Administrator Add backup or every very detailed operations guide
Site Add additional site.

Cluster Components

Here are the recommended practices for important cluster components.

Nodes

HACMP supports clusters of up to 32 nodes, with any combination of active and standby nodes. While it
is possible to have all nodes in the cluster running applications (a configuration referred to as "mutual
takeover"), the most reliable and available clusters have at least one standby node - one node that is normally
not running any applications, but is available to take them over in the event of a failure on an active
node.

Additionally, it is important to pay attention to environmental considerations. Nodes should not have a
common power supply - which may happen if they are placed in a single rack. Similarly, building a cluster
of nodes that are actually logical partitions (LPARs) with a single footprint is useful as a test cluster, but
should not be considered for availability of production applications.
Nodes should be chosen that have sufficient I/O slots to install redundant network and disk adapters.
That is, twice as many slots as would be required for single node operation. This naturally suggests that
processors with small numbers of slots should be avoided. Use of nodes without redundant adapters
should not be considered best practice. Blades are an outstanding example of this. And, just as every cluster
resource should have a backup, the root volume group in each node should be mirrored, or be on a

RAID device.
Nodes should also be chosen so that when the production applications are run at peak load, there are still
sufficient CPU cycles and I/O bandwidth to allow HACMP to operate. The production application
should be carefully benchmarked (preferable) or modeled (if benchmarking is not feasible) and nodes chosen
so that they will not exceed 85% busy, even under the heaviest expected load.
Note that the takeover node should be sized to accommodate all possible workloads: if there is a single
standby backing up multiple primaries, it must be capable of servicing multiple workloads. On hardware
that supports dynamic LPAR operations, HACMP can be configured to allocate processors and memory to
a takeover node before applications are started. However, these resources must actually be available, or
acquirable through Capacity Upgrade on Demand. The worst case situation – e.g., all the applications on
a single node – must be understood and planned for.

Networks

HACMP is a network centric application. HACMP networks not only provide client access to the applications
but are used to detect and diagnose node, network and adapter failures. To do this, HACMP uses
RSCT which sends heartbeats (UDP packets) over ALL defined networks. By gathering heartbeat information
on multiple nodes, HACMP can determine what type of failure has occurred and initiate the appropriate
recovery action. Being able to distinguish between certain failures, for example the failure of a network
and the failure of a node, requires a second network! Although this additional network can be “IP
based” it is possible that the entire IP subsystem could fail within a given node. Therefore, in addition
there should be at least one, ideally two, non-IP networks. Failure to implement a non-IP network can potentially
lead to a Partitioned cluster, sometimes referred to as 'Split Brain' Syndrome. This situation can
occur if the IP network(s) between nodes becomes severed or in some cases congested. Since each node is
in fact, still very alive, HACMP would conclude the other nodes are down and initiate a takeover. After
takeover has occurred the application(s) potentially could be running simultaneously on both nodes. If the
shared disks are also online to both nodes, then the result could lead to data divergence (massive data corruption).
This is a situation which must be avoided at all costs.

The most convenient way of configuring non-IP networks is to use Disk Heartbeating as it removes the
problems of distance with rs232 serial networks. Disk heartbeat networks only require a small disk or
LUN. Be careful not to put application data on these disks. Although, it is possible to do so, you don't want
any conflict with the disk heartbeat mechanism!

Adapters

As stated above, each network defined to HACMP should have at least two adapters per node. While it is
possible to build a cluster with fewer, the reaction to adapter failures is more severe: the resource group
must be moved to another node. AIX provides support for Etherchannel, a facility that can used to aggregate
adapters (increase bandwidth) and provide network resilience. Etherchannel is particularly useful for
fast responses to adapter / switch failures. This must be set up with some care in an HACMP cluster.
When done properly, this provides the highest level of availability against adapter failure. Refer to the IBM
techdocs website: http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD101785 for further
details.
Many System p TM servers contain built-in Ethernet adapters. If the nodes are physically close together, it
is possible to use the built-in Ethernet adapters on two nodes and a "cross-over" Ethernet cable (sometimes
referred to as a "data transfer" cable) to build an inexpensive Ethernet network between two nodes for
heart beating. Note that this is not a substitute for a non-IP network.
Some adapters provide multiple ports. One port on such an adapter should not be used to back up another
port on that adapter, since the adapter card itself is a common point of failure. The same thing is true
of the built-in Ethernet adapters in most System p servers and currently available blades: the ports have a
common adapter. When the built-in Ethernet adapter can be used, best practice is to provide an additional
adapter in the node, with the two backing up each other.
Be aware of network detection settings for the cluster and consider tuning these values. In HACMP terms,
these are referred to as NIM values. There are four settings per network type which can be used : slow,
normal, fast and custom. With the default setting of normal for a standard Ethernet network, the network
failure detection time would be approximately 20 seconds. With todays switched network technology this
is a large amount of time. By switching to a fast setting the detection time would be reduced by 50% (10
seconds) which in most cases would be more acceptable. Be careful however, when using custom settings,
as setting these values too low can cause false takeovers to occur. These settings can be viewed using a variety
of techniques including : lssrc –ls topsvcs command (from a node which is active) or odmget
HACMPnim |grep –p ether and smitty hacmp.

Applications
The most important part of making an application run well in an HACMP cluster is understanding the
application's requirements. This is particularly important when designing the Resource Group policy behavior
and dependencies. For high availability to be achieved, the application must have the ability to
stop and start cleanly and not explicitly prompt for interactive input. Some applications tend to bond to a
particular OS characteristic such as a uname, serial number or IP address. In most situations, these problems
can be overcome. The vast majority of commercial software products which run under AIX are well
suited to be clustered with HACMP.

Application Data Location
Where should application binaries and configuration data reside? There are many arguments to this discussion.
Generally, keep all the application binaries and data were possible on the shared disk, as it is easy
to forget to update it on all cluster nodes when it changes. This can prevent the application from starting or
working correctly, when it is run on a backup node. However, the correct answer is not fixed. Many application
vendors have suggestions on how to set up the applications in a cluster, but these are recommendations.
Just when it seems to be clear cut as to how to implement an application, someone thinks of a new
set of circumstances. Here are some rules of thumb:
If the application is packaged in LPP format, it is usually installed on the local file systems in rootvg. This
behavior can be overcome, by bffcreate’ing the packages to disk and restoring them with the preview option.
This action will show the install paths, then symbolic links can be created prior to install which point
to the shared storage area. If the application is to be used on multiple nodes with different data or configuration,
then the application and configuration data would probably be on local disks and the data sets on
shared disk with application scripts altering the configuration files during fallover. Also, remember the
HACMP File Collections facility can be used to keep the relevant configuration files in sync across the cluster.
This is particularly useful for applications which are installed locally.

Start/Stop Scripts
Application start scripts should not assume the status of the environment. Intelligent programming should
correct any irregular conditions that may occur. The cluster manager spawns theses scripts off in a separate
job in the background and carries on processing. Some things a start script should do are:
First, check that the application is not currently running! This is especially crucial for v5.4 users as
resource groups can be placed into an unmanaged state (forced down action, in previous versions).
Using the default startup options, HACMP will rerun the application start script which may cause
problems if the application is actually running. A simple and effective solution is to check the state
of the application on startup. If the application is found to be running just simply end the start script
with exit 0.
Verify the environment. Are all the disks, file systems, and IP labels available?
If different commands are to be run on different nodes, store the executing HOSTNAME to variable.
Check the state of the data. Does it require recovery? Always assume the data is in an unknown state
since the conditions that occurred to cause the takeover cannot be assumed.
Are there prerequisite services that must be running? Is it feasible to start all prerequisite services
from within the start script? Is there an inter-resource group dependency or resource group sequencing
that can guarantee the previous resource group has started correctly? HACMP v5.2 and later has
facilities to implement checks on resource group dependencies including collocation rules in
HACMP v5.3.
Finally, when the environment looks right, start the application. If the environment is not correct and
error recovery procedures cannot fix the problem, ensure there are adequate alerts (email, SMS,
SMTP traps etc) sent out via the network to the appropriate support administrators.
Stop scripts are different from start scripts in that most applications have a documented start-up routine
and not necessarily a stop routine. The assumption is once the application is started why stop it? Relying
on a failure of a node to stop an application will be effective, but to use some of the more advanced features
of HACMP the requirement exists to stop an application cleanly. Some of the issues to avoid are:

Be sure to terminate any child or spawned processes that may be using the disk resources. Consider
implementing child resource groups.
Verify that the application is stopped to the point that the file system is free to be unmounted. The
fuser command may be used to verify that the file system is free.
In some cases it may be necessary to double check that the application vendor’s stop script did actually
stop all the processes, and occasionally it may be necessary to forcibly terminate some processes.
Clearly the goal is to return the machine to the state it was in before the application start script was run.
Failure to exit the stop script with a zero return code as this will stop cluster processing. * Note: This is not the case with start scripts!
Remember, most vendor stop/starts scripts are not designed to be cluster proof! A useful tip is to have stop
and start script verbosely output using the same format to the /tmp/hacmp.out file. This can be achieved
by including the following line in the header of the script: set -x && PS4="${0##*/}"'[$LINENO]

AIX Security Checklist

2008-07-12T11:23:00.000-07:00

AIX Environment Procedures

The best way to approach this portion of the checklist is to do a comprehensive physical inventory of the servers. Serial numbers and physical location would be sufficient.

____Record server serial numbers
____Physical location of the servers

Next we want to gather a rather comprehensive list of both the AIX and pseries inventories. By running these next 4 scripts we can gather the information for analyze.

____Run these 4 scripts: sysinfo, tcpchk, nfsck and nethwchk. (See Appendix A for scripts)
____sysinfo:
____Determine active logical volume groups on the servers: lsvg -o
____List physical volumes in each volume group: lsvg –p "vgname"
____List logical volumes for each volume group: lsvg –l "vgname"
____List physical volumes information for each hard disk
____lspv hdiskx
____lspv –p hdiskx
____lspv –l hdiskx
____List server software inventory: lslpp -L
____List server software history: lslpp –h
____List all hardware attached to the server: lsdev –C | sort –d
____List system name, nodename, LAN network number, AIX release, AIX version and machine ID: uname –x
____List all system resources on the server: lssrc –a
____List inetd services: lssrc –t 'service name' –p 'process id'
____List all host entries on the servers: hostent -S
____Name all nameservers the servers have access to: namerslv –Is
____Show status of all configured interfaces on the server: netstat –i
____Show network addresses and routing tables: netstat –nr
____Show interface settings: ifconfig
____Check user and group system variables
____Check users: usrck –t ALL
____Check groups: grpck –t ALL
____Run tcbck to verify if it is enabled: tcbck
____Examine the AIX failed logins: who –s /etc/security/failedlogin
____Examine the AIX user log: who /var/adm/wtmp
____Examine the processes from users logged into the servers: who –p /var/adm/wtmp
____List all user attributes: lsuser ALL | sort –d
____List all group attributes: lsgroup ALL
____tcpchk:
____Confirm the tcp subsystem installed: lslpp –l | grep bos.net
____Determine if it is running: lssrc –g tcpip
____Search for .rhosts and .netrc files: find / -name .rhosts -print ; find / -name .netrc –print
____Checks for rsh functionality on host: cat /etc/hosts.equiv
____Checks for remote printing capability: cat /etc/hosts.lpd | grep v #
____nfschk:
____Verify NFS is installed: lslpp -L | bin/grep nfs
____Check NFS/NIS status: lssrc -g nfs | bin/grep active
____Checks to see if it is an NFS server and what directories are exported: cat /etc/xtab
____Show hosts that export NFS directories: showmount
____Show what directories are exported: showmount –e
____nethwchk
____Show network interfaces that are connected: lsdev –Cc if
____Display active connection on boot: odmget -q value=up CuAt | grep name|cut -c10-12
___Show all interface status: ifconfig ALL

Root level access

____Limit users who can su to another UID: lsuser –f ALL
____Audit the sulog: cat /var/adm/sulog
____Verify /etc/profile does not include current directory
____Lock down cron access
____To allow root only: rm –i /var/adm/cron/cron.deny and rm –I /var/adm/cron/cron.allow
____To allow all users: touch cron.allow (if file does not already exist)
____To allow a user access: touch /var/adm/cron/cron.allow then echo "UID">/var/adm/cron/cron.allow
____To deny a user access: touch /var/adm/cron/cron.deny then echo "UID">/var/adm/cron/cron.deny
____Disable direct herald root access: add rlogin=false to root in /etc/security/user file or through smit

____Limit the $PATH variable in /etc/environment. Use the users .profile instead.

Authorization/authentication administration

____Report all password inconsistencies and not fix them: pwdck –n ALL
____Report all password inconsistencies and fix them: pwdck –y ALL
____Report all group inconsistencies and not fix them: grpck –n ALL
____Report all group inconsistencies and fix them: grpck –y ALL
____Browse the /etc/shadow, etc/password and /etc/group file weekly

SUID/SGID

____Review all SUID/SGID programs owned by root, daemon, and bin.
____Review all SETUID programs: find / -perm -1000 –print
____Review all SETGID programs: find / -perm -2000 –print
____Review all sticky bit programs: find / -perm -3000 –print
____Set user .profile in /etc/security/.profile

Permissions structures

____System directories should have 755 permissions at a minimum
____Root system directories should be owned by root
____Use the sticky bit on the /tmp and /usr/tmp directories.
____Run checksum (md5) against all /bin, /usr/bin, /dev and /usr/sbin files.
____Check device file permissions:
____disk, storage, tape, network (should be 600) owned by root.
____tty devices (should be 622) owned by root.
____/dev/null should be 777.
____List all hidden files in there directories ( the .files).
____List all writable directories (use the find command).
____$HOME directories should be 710
____$HOME .profile or .login files should be 600 or 640.
____Look for un-owned files on the server: find / -nouser –print.
Note: Do not remove any /dev files.
____Do not use r-type commands: rsh, rlogin, rcp and tftp or .netrc or .rhosts files.
____Change /etc/host file permissions to 660 and review its contents weekly.

____Check for both tcp/udp failed connections to the servers: netstat –p tcp; netstat –p udp.
____Verify contents of /etc/exports (NFS export file).
____If using ftp, make this change to the /etc/inetd.conf file to enable logging.
ftp stream tcp6 nowait root /usr/sbin/ftpd ftpd –l
____Set NFS mounts to –ro (read only) and only to the hosts that they are needed.
____Consider using extended ACL's (please review the tcb man page).
____Before making network connection collect a full system file listing and store it off-line:
ls -Ra -la>/tmp/allfiles.system
____Make use of the strings command to check on files: strings /etc/hosts | grep Kashmir

Recommendations

Remove unnecessary services

By default the Unix operating system gives us 1024 services to connect to, we want to parse this down to a more manageable value. There are 2 files in particular that we want to parse. The first is the /etc/services file itself. A good starting point is to eliminate all unneeded services and add services as you need them. Below is a screenshot of an existing ntp server etc/services file on one of my lab servers.

#
# Network services, Internet style
#
ssh 22/udp
ssh 22/tcp mail
auth 113/tcp authentication
sftp 115/tcp
ntp 123/tcp # Network Time Protocol
ntp 123/udp # Network Time Protocol
#
# UNIX specific services
#
login 513/tcp
shell 514/tcp cmd # no passwords used

Parse /etc/rc.tcpip file

This file starts the daemons that we will be using for the tcp/ip stack on AIX servers. By default the file will start the sendmail, snmp and other daemons. We want to parse this to reflect what
functionality we need this server for. Here is the example for my ntp server.

# Start up the daemons
#
echo "Starting tcpip daemons:"
trap 'echo "Finished starting tcpip daemons."' 0
# Start up syslog daemon (for error and event logging)
start /usr/sbin/syslogd "$src_running"

# Start up Portmapper

start /usr/sbin/portmap "$src_running"

# Start up socket-based daemons
start /usr/sbin/inetd "$src_running"

# Start up Network Time Protocol (NTP) daemon
start /usr/sbin/xntpd "$src_running"

This helps also to better understand what processes are running on the server.

Remove unauthorized /etc/inittab entries

Be aware of what is in the /etc/inittab file on the AIX servers. This file works like the registry in a Microsoft environment. If an intruder wants to hide an automated script, he would want it launched here or in the cron file. Monitor this file closely.

Parse /etc/inetd.conf file

This is the AIX system file that starts system services, like telnet, ftp, etc. We also want to closely watch this file to see if there are any services that have been enabled without authorization. If you are using ssh for example this is what the inetd.con file should look like. Because we are using other internet connections, this file is not used in my environment and should not be of use to you. This is why ssh should be used for all administrative connections into the environment. It provides an encrypted tunnel so connection traffic is secure. In the case of telnet, it is very trivial to sniff the UID and password.

## protocol. "tcp" and "udp" are interpreted as IPv4.
##
## service socket protocol wait/ user server server program
## name type nowait program arguments
##

Edit /etc/rc.net

This is network configuration file used by AIX. This is the file you use to set your default network route along your no (for network options) attributes. Because the servers will not be used as routers to forward traffic and we do not want to use loose source routing at you, we will be making a few changes in this file. A lot of them are to protect from DOS and DDOS attacks from the internet. Also protects from ACK and SYN attacks on the internal network.

##################################################################
##################################################################
# Changes made on 06/07/02 to tighten up socket states on this

# server.

##################################################################
if [ -f /usr/sbin/no ] ; then
/usr/sbin/no -o udp_pmtu_discover=0 # stops autodiscovery of MTU
/usr/sbin/no -o tcp_pmtu_discover=0 # on the network interface
/usr/sbin/no -o clean_partial_conns=1 # clears incomplete 3-way conn.
/usr/sbin/no -o bcastping=0 # protects against smurf icmp attacks
/usr/sbin/no -o directed_broadcast=0 # stops packets to broadcast add.
/usr/sbin/no -o ipignoreredirects=1 # prevents loose
/usr/sbin/no -o ipsendredirects=0 # source routing
/usr/sbin/no -o ipsrcrouterecv=0 # attacks on
/usr/sbin/no -o ipsrcrouteforward=0 # our network
/usr/sbin/no -o ip6srcrouteforward=0 # from using indirect
/usr/sbin/no -o icmpaddressmask=0 # dynamic routes
/usr/sbin/no -o nonlocsrcroute=0 # to attack us from
/usr/sbin/no -o ipforwarding=0 # Stops server from acting like a router
fi

Securing root

Change the /etc/motd banner

This computer system is the private property of XYZ Insurance. It is for authorized use only. All users (authorized or non-authorized) have no explicit or implicit expectations of privacy.

Any or all users of this system and all the files on this system may be intercepted, monitored, recorded, copied, audited, inspected and disclosed to XYZ Insurance's management personnel.

By using this system, the end user consents to such interception, monitoring, recording, copying, auditing, inspection and disclosure at the discretion of such personnel. Unauthorized or improper use of this system may result in civil and/or criminal penalities and administrative or disciplinary action, as deemed appropriate by said actions. By continuing to use this system, the individual indicates his/her awareness of and consent to these terms and conditions of use.

LOG OFF IMMEDIATELY if you do not agree to the provisions stated in this warning banner.

Modify /etc/security/user

root:
loginretries = 5 – failed retries until account locks
rlogin = false – Disables remote herald access to a root shell. Need to su from another UID.
admgroups = system
minage = 0 – minimum aging is no time value
maxage = 4 – maximum aging is set to 30 days or 4 weeks
umask = 22

Tighten up /etc/security/limits

This is an attribute that should be changed due to a runaway resource hog. This orphaned process can grow to use
an exorbinate amount of disk space. To provent this we can set the ulimit value here.

default:
#fsize = 2097151
fsize = 8388604 – sets the soft file block size to a max of 8 Gig.

Variable changes in /etc/profile

Set the $TMOUT variable in /etc/profile. This will cause an open shell to close after 15 minutes of inactivity. It works in conjunction with the screensaver, to prevent an open session to be used to either delete the server or worse corrupt data on the server.

# Automatic logout, include in export line if uncommented
TMOUT=900

4.6.5 Sudo is your friend….

This is a nice piece of code that the system administrators can use in order to allow "root-like" functionality. It allows a non-root user to run system binaries or commands. The /etc/sudoers file is used to configure exactly what the user can do. The service is configured and running on ufxcpidev. The developers are running a script called changeperms in order to tag there .ear files with there own ownership attributes.

First we setup sudo to allow root-like or superuser doer access to sxnair.

# sudoers file.
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the sudoers man page for the details on how to write a sudoers file.
#
# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
root ALL=(ALL) ALL
sxnair,jblade,vnaidu ufxcpidev=/bin/chown * /usr/WebSphere/AppServer/installedApps/*
#
#
# Override the built in default settings
Defaults syslog=auth

Defaults logfile=/var/log/sudo.log

For more details, please see the XYZ Company Insurance Work Report that I compiled, or visit this
URL: http://www.courtesan.com/sudo/.

Tighten user/group attributes

Change /etc/security/user

These are some of the changes to the /etc/security/user file that will promote a more heightened
configuration of default user attributes at your company.

default:

umask = 077 – defines umask values – 22 is readable only for that UID
pwdwarntime = 7 – days of password expiration warnings
loginretries = 5 – failed login attempts before account is locked
histexpire = 52 – defines how long a password cannot be re-used
histsize = 20 – defines how many previous passwords the system remembers
minage = 2 – minimum number of weeks a password is valid
maxage = 8 – maximum number of weeks a password is valid
maxexpired = 4 – maximum time in weeks a password can be changed after it exp

HACMP log files

2008-07-12T11:21:00.000-07:00

/usr/sbin/cluster/etc/rhosts --- to accept incoming communication from clcomdES (cluster communucation enahanced security)
/usr/es/sbin/cluster/etc/rhosts

Note: If there is an unresolvable label in the /usr/es/sbin/cluster/etc/rhosts file,
then all clcomdES connections from remote nodes will be denied.

cluster manager clstrmgrES
cluster lock Daemon (clockdES)
cluster multi peer extension communication daemon (clsmuxpdES)

The clcomdES is used for cluster configuration operations such as cluster synchronisation
cluster management (C-SPoC) * Dynamic re-configuration DARE configuration. (DARE ) operation.

For clcomdES there should be atleast 20 MB free space in /var file system.
/var/hacmp/clcomd/clcomd.log --it requires 2 MB
/var/hacmp/clcomd/clcomdiag.log --it requires 18MB
Additional 1 MB required for
/var/hacmp/odmcache directory

clverfify.log also present in /var directory
/var/hacmp/clverify/current//* contains log for mcurrent execution of clverify
/var/hacmp/clverify/pass//* contains logs from the last passed verification
/var/hacmp/clverify/pass.prev//* contains log from the second last passed verification

AIX 6.1 WPAR Commands

2008-07-11T13:01:00.001-07:00

Most of these commands are only runable by root user for the Global LPAR (Global
Environment).

chwpar Modifies dynamically the configuration options of the WPAR even when it is
running.

clogin Provides a mechanism for the root user to log in or run a command within a
workload partition. The “clogin” command uses a pseudo-terminal allocated on
the Global Environment (see in the mobility part the impact of this) and creates
a login shell running which belongs to the workload partition.

lswpar Prints information about WPARs

mkwpar Specific for System WPAR - Builds the infrastructure and the configuration
file. Then it creates and populates the WPARs file systems. Allocate the
specified resources as well as the WLM information (if any) and eventually
starts it. Specifying whether the workload partitions should be automatically
started on system boot or when /etc/rc.wpars is executed.

startwpar Activates the System WPAR defined with mkwpar

wparexec Specific for Application WPAR – Builds, create specification file and
eventually starts the Application WPAR

rebootwpar Stops and resumes a System Workload Partition. It cannot be run within a
WPAR

rmwpar Deletes the specified Workload Partition from the system as well as its
configuration and its WLM profile

stopwpar Kills the WPAR and deallocate all resources belonging to it. It removes the
Application WPAR

syncwpar Specific to System WPAR - Synchronizes the software installed in the global
shared parts (usually /usr and /opt) with the workload partition's root part

Note: The mkwpar and chwpar can update the global file /etc/wpars:

Note: /etc/rc.wpars: Specific to System WPAR - this script is run at main system boot it
invokes the startwpar command on all workload partitions with the autostart option.
Some commands have different or enhanced behavior in a WPAR environment. The list
includes acctcom, acctctl, df, domainname, hosted, hostname, ifconfig, ioo, ipcrm, ipcs,
mkclass, mount, netstat, nfso, no, projctl, ps , schedo, uname, vmo, wlmstat, wlmtune,
wlmcntrl. This change is described in the AIX 6 documentation.

The simplest way to administrate WPARs using command lines (CLI) is to issue the
command smitty wpar which will provide the interface to these commands.

Server Snapshots: IBM p570 Power 6

2008-07-11T13:00:00.002-07:00

The IBM POWER6 processor-based System p570 is a midrange server that aims to deliver outstanding price/performance while providing mainframe-like reliability and availability. This 19-inch rack-mount system, which can handle up to 16 POWER6 cores, is best-suited to database and application serving, as well as server consolidation.
"The first server to use the new POWER6 processor is the System p570," said Jeff Howard, director of System p offering management for IBM (Armonk, N.Y.). "The p570 leverages the chip's many breakthroughs in energy conservation and virtualization technology."

POWER6 Packs a Punch
The modular p570 takes over from its predecessor, the IBM POWER5+ processor-based System p5 570 server. POWER6 processors can run 64-bit applications while concurrently supporting 32-bit applications. They feature simultaneous multithreading, allowing two application threads to be run at the same time.
"At 4.7 GHz, the dual-core POWER6 processor doubles the speed of the previous generation, POWER5, while using the same amount of electricity to run and cool it," said Howard. "This means customers can use the new processor to either increase their performance by 100 percent or cut their power consumption in half."
Dan Olds, principal of Oregon-based Gabriel Consulting Group, believes the p570/POWER6 combo is an impressive one. The new processors come in 3.5 GHz, 4.2 GHz and 4.7 GHz flavors. IBM has effectively doubled the frequency over its predecessor without increasing the number of cores on the chip.

p570 close up

The POWER6 [processor] has two cores, each of which can simultaneously execute two threads, an approach known as simultaneous multithreading (SMT)," said Gordon Haff, an analyst at Illuminata (Nashua, N.H.). "POWER6 processors also have integrated memory controllers in order to improve memory access times and thereby application performance."
He pointed out that changes in the way POWER6 processors connect to each other and to the rest of the system flatten latency differences. There are also new specialized execution units and reliability features. Compute power is able to double largely because POWER6 has more than 790 million transistors compared to 276 million in the POWER5+. The amount of Level 2 Cache has gone up to 8 MB from just under 2 MB.
More to Come
While POWER6 has been released and is functioning currently in data centers, it is not quite a finished article. IBM is introducing more features later this year, such as Live Partition Mobility and Live Partition Migration. Live Partition Mobility, for example, will move a running Logical Partition (LPAR) from one physical server to another. It functions below the level of the operating system, at the hypervisor level; works only with the upcoming AIX 6 (currently in beta), AIX 5.3, and Linux; and the servers must all be on the same network subnet.
Haff said AIX 6 contains several major new features, including role-based access controls, a Trusted installation option and new "Workload Partitions" (WPAR). WPAR are resource groups similar to Solaris Containers or virtual servers that can be migrated from one server to another.
"I think that enhancements to the overall system, particularly the Live Partition Mobility feature, are big news and will provide the most business value to customers," said Olds. "With Live Partition Mobility, IBM users can move active workloads from one physical server to another — with no application interruption, no loss of transactions, and no user impact."
Gaining Ground
With such functions added to the already impressive POWER6, Olds believes the IBM p570 will gain major ground in the marketplace.
"This arguably means the end of planned application downtime and can eliminate perhaps half of overall application downtime, which is a big deal," said Olds. "This is much more sophisticated than VMware's VMotion and is a feature that their competitors will need to address."
Howard of IBM boasted that the POWER6 chip is nearly three times faster than the latest HP Itanium processor that runs much of HP's midrange server line. Thus, it will likely reinforce IBM's lead in the Unix servers market. According to research firm IDC (Framingham, Mass.), the company has a 29.6 percent revenue share in Unix.
"The p570 is the first server to hold all four major benchmark speed records for business and technical performance," said Howard. "In fact, the System p 570 now holds more than 20 benchmark records."
The p570 currently supports AIX 5L (v5.2 or later), the upcoming AIX 6, as well as Linux distributions from Red Hat (RHEL 4 Update 5 or later) and SUSE Linux (v10 SP1 or later).
The starting price for a basic version of the server is $60,000. IBM was reluctant to give out more details of pricing and configurations. Per its Web site, the minimum is a 2-core version operating at 3.5 GHz, so presumably that is what is obtained for this price. Each p570 building block accommodates two processor cards, each of which provides two 64-bit POWER6 processor cores, 8 MB of Level 2 (L2) cache and 32 MB of Level 3 (L3) cache. Each processor card has 12 slots for DDR2 (double data rate 2) ECC memory DIMMs, providing memory capacity of up to 192 GB per building block.

p570 Close Up

Name p 570
Vendor IBM
Platform Power6
Dimensions 4U rackmount; 19" by 32.4" by 6.85"; Weight: 140 lb
Processor Details 2- to 16-core POWER6
Hard Drives Six hot-swappable SAS disk bays per building block provide up to 7.2 TB of internal disk storage, up to four building blocks
Operating Systems Supported by AIX 5L (V5.2 or later) and Linux distributions from Red Hat (RHEL 4 Update 5 or later) and SUSE Linux (V10 SP1 or later) operating systems; AIX6 is in beta
Configuration Options The base configuration starts at $60,000 for a 2-core processor, 3.5 GHz, 64MB L3 cache, 16 GB system memory, and 2 x 73.4GB SAS 15K rpm internal storage. A high-end, system begins at $2 million before IBM discounts. This is a 16-core version running at 4.7 GHz.
GA Now available
Warranty Three years

Changing WPAR properties & starting it in Verbose mode.

2008-07-11T13:00:00.001-07:00

1 To modify the host name of the workload partition called roy, enter the following command:

chwpar -h roy.com roy
2 To remove a network address from the workload partition called dale, enter the following command:

chwpar -K -N address=219.81.45.65 dale
3 To disable resource controls in the workload partition called wayne while retaining the settings for future use, enter the following command:

chwpar -R active=no wayne
4 To remove the device /dev/foo, exported by default through the devexportsFile, from a workload partition, enter the following command:

chwpar -D globaldev=/dev/foo export=no moore
5 To export the device /dev/bar, permitted by the devexportsFile but not exported, enter the following command:

chwpar -D globaldev=/dev/bar export=yes moore
6 To rename the workload partition from moore to hart, enter the following command:

chwpar -n hart moore
=========================================================

To start WPAR in verbose mode.

tarting workload partition MyTestWpar3.
Mounting all workload partition file systems.
Mounting /wpars/MyTestWpar3
Mounting /wpars/MyTestWpar3/home
Mounting /wpars/MyTestWpar3/opt
Mounting /wpars/MyTestWpar3/proc
Mounting /wpars/MyTestWpar3/tmp
Mounting /wpars/MyTestWpar3/usr
Mounting /wpars/MyTestWpar3/var
Loading workload partition.
$corral_t = {
'name' => 'MyTestWpar3',
'wlm_cpu' => [
undef,
undef,
undef,
undef
],
'path' => '/wpars/MyTestWpar3',
'hostname' => 'MyTestWpar3',
'wlm_procVirtMem' => [
-1,
undef
],
'wlm_mem' => [
undef,
undef,
undef,
undef
],
'key' => 5,
'vips' => [
[
'en0',
'172.29.138.24',
'255.255.192.0',
'172.29.191.255'
]
],
'wlm_rset' => undef,
'opts' => 4,
'id' => 0
};
Exporting workload partition devices.
Starting workload partition subsystem cor_MyTestWpar3.
0513-059 The cor_MyTestWpar3 Subsystem has been started. Subsystem PID is 536778.
Verifying workload partition startup.
Return Status = SUCCESS.
lpar47p682e_pub[/] >

Creating WPAR on command line.

2008-07-11T12:59:00.000-07:00

1 To create a workload partition called roy, enter the following command:

mkwpar -n roy -N address=192.168.0.51
All values that are not specified are generated or discovered from the global system's settings.
2 To create a workload partition based on an existing specification file, enter the following command:

mkwpar -f /tmp/wpar1.spec
3 To create a modified copy of a specification file with a new IP address, host name, and workload partition name (without creating a workload
partition), enter the following command:

mkwpar -f /tmp/wpar1.spec -N address=219.168.45.132 -h www.flowers.com -n wpar2
-o /tmp/wpar2.spec -w
4 To create a new specification file based on an existing workload partition, enter the following command:

mkwpar -e wpar1 -o /tmp/wpar2.spec -w
5 To recreate a workload partition that was previously removed with the rmwpar -p command, enter the following command:

mkwpar -p wparname

==========================================================
Actual WPAR creation screen shots.

par47p682e_pub[/] > mkwpar -n MyTestWpar2 -N ip= xyz
mkwpar: Creating file systems...
/
/home
/opt

/proc
/tmp
/usr
/var
Mounting all workload partition file systems.
x ./usr
x ./lib
x ./admin
x ./admin/tmp
x ./audit
x ./dev
x ./etc
x ./etc/check_config.files
x ./etc/consdef
x ./etc/cronlog.conf
x ./etc/csh.cshrc
x ./etc/csh.login
x ./etc/dlpi.conf
x ./etc/dumpdates
x ./etc/environment
x ./etc/ewlm
x ./etc/ewlm/limits
x ./etc/ewlm/trc
x ./etc/ewlm/trc/config_schema.xsd
x ./etc/ewlm/trc/output_schema.xsd
x ./etc/filesystems
x ./etc/group
x ./etc/inittab
x ./etc/magic
x ./etc/motd
x ./etc/nscontrol.conf
x ./etc/objrepos
x ./etc/objrepos/CDiagAtt
x ./etc/objrepos/CDiagAtt.vc
x ./etc/objrepos/CDiagDev
x ./etc/objrepos/Config_Rules
x ./etc/objrepos/CuAt
x ./etc/objrepos/CuAt.vc
x ./etc/objrepos/CuDep
x ./etc/objrepos/CuDv
x ./etc/objrepos/CuDvDr
x ./etc/objrepos/CuPath
x ./etc/objrepos/CuPath.vc
x ./etc/objrepos/CuPathAt
x ./etc/objrepos/CuPathAt.vc
x ./etc/objrepos/CuVPD
x ./etc/objrepos/CuData
x ./etc/objrepos/CuData.vc
x ./etc/objrepos/DAVars
x ./etc/objrepos/FRUB
x ./etc/objrepos/FRUB_SRC
x ./etc/objrepos/FRUs
x ./etc/objrepos/FRUs_src
x ./etc/objrepos/MenuGoal
x ./etc/objrepos/SRCextmeth
x ./etc/objrepos/SRCnotify
x ./etc/objrepos/SRCsubsvr
x ./etc/objrepos/SRCsubsys
x ./etc/objrepos/SWservAt
x ./etc/objrepos/SWservAt.vc
x ./etc/objrepos/TMInput
x ./etc/objrepos/errnotify
x ./etc/objrepos/history
x ./etc/objrepos/history.vc
x ./etc/objrepos/inventory
x ./etc/objrepos/inventory.vc
x ./etc/objrepos/lpp
x ./etc/objrepos/lpp.vc
x ./etc/objrepos/product
x ./etc/objrepos/product.vc
x ./etc/passwd
x ./etc/profile
x ./etc/project
x ./etc/project/projdef
x ./etc/pse.conf
x ./etc/pse_tune.conf
x ./etc/qconfig
x ./etc/rc
x ./etc/rc.C2
x ./etc/rc.CC
x ./etc/rc.dacinet
x ./etc/rc.d
x ./etc/rc.d/init.d
x ./etc/rc.d/rc
x ./etc/rc.d/rc2.d
x ./etc/rc.d/rc3.d
x ./etc/rc.d/rc4.d
x ./etc/rc.d/rc5.d
x ./etc/rc.d/rc6.d
x ./etc/rc.d/rc7.d
x ./etc/rc.d/rc8.d
x ./etc/rc.d/rc9.d
x ./etc/rc.ha_star
x ./etc/rc.powerfail
x ./etc/rc.security.boot
x ./etc/security
x ./etc/security/acl
x ./etc/security/audit
x ./etc/security/audit/bincmds
x ./etc/security/audit/config
x ./etc/security/audit/events
x ./etc/security/audit/objects
x ./etc/security/audit/streamcmds
x ./etc/security/authorizations
x ./etc/security/privcmds
x ./etc/security/privdevs
x ./etc/security/environ
x ./etc/security/group
x ./etc/security/lastlog
x ./etc/security/ldap
x ./etc/security/ldap/2307aixgroup.map
x ./etc/security/ldap/2307aixuser.map
x ./etc/security/ldap/2307group.map
x ./etc/security/ldap/2307user.map
x ./etc/security/ldap/aixgroup.map
x ./etc/security/ldap/aixid.map
x ./etc/security/ldap/aixuser.map
x ./etc/security/ldap/ldap.cfg
x ./etc/security/ldap/ldapid.ldif.template
x ./etc/security/ldap/nisSchema.ldif
x ./etc/security/ldap/proxy.ldif.template
x ./etc/security/ldap/sec.ldif
x ./etc/security/ldap/sectoldif.cfg
x ./etc/security/ldap/sfu20group.map
x ./etc/security/ldap/sfu20user.map
x ./etc/security/ldap/sfu30group.map
x ./etc/security/ldap/sfu30user.map
x ./etc/security/ldap/sfur2group.map
x ./etc/security/ldap/sfur2user.map
x ./etc/security/limits
x ./etc/security/login.cfg
x ./etc/security/passwd
x ./etc/security/portlog
x ./etc/security/priv
x ./etc/security/privfiles
x ./etc/security/.profile
x ./etc/security/pwdalg.cfg
x ./etc/security/roles
x ./etc/security/services
x ./etc/security/smitacl.group
x ./etc/security/smitacl.user
x ./etc/security/sysck.cfg
x ./etc/security/user
x ./etc/security/user.roles
x ./etc/shells
x ./etc/swapspaces
x ./etc/trcfmt.Z
x ./etc/tsh_profile
x ./etc/uucp
x ./etc/uucp/Devices
x ./etc/uucp/Dialers
x ./etc/vfs
x ./etc/vg
x ./etc/xtiso.conf
x ./etc/wlm
x ./etc/wlm/standard
x ./etc/wlm/current
x ./etc/wlm/standard/README
x ./etc/wlm/standard/classes
x ./etc/wlm/standard/limits
x ./etc/wlm/standard/shares
x ./etc/wlm/standard/rules
x ./etc/wlm/template
x ./etc/wlm/template/classes
x ./etc/wlm/template/limits
x ./etc/wlm/template/shares
x ./etc/wlm/template/rules
x ./etc/wlm/template/description
x ./u
x ./lost+found
x ./lpp
x ./mnt
x ./opt
x ./proc
x ./sbin
x ./sbin/comp.kext
x ./sbin/comp.uext
x ./sbin/comp.uext64
x ./sbin/rc.boot
x ./sbin/helpers
x ./sbin/helpers/v3fshelper
x ./sbin/helpers/udfmnthelp
x ./sbin/helpers/jfs2
x ./sbin/helpers/jfs2/backbyinode
x ./sbin/helpers/jfs2/chfs
x ./sbin/helpers/jfs2/chfs64
x ./sbin/helpers/jfs2/crfs
x ./sbin/helpers/jfs2/defragfs
x ./sbin/helpers/jfs2/diskusg
x ./sbin/helpers/jfs2/dumpfs
x ./sbin/helpers/jfs2/ff
x ./sbin/helpers/jfs2/fsck
x ./sbin/helpers/jfs2/fsck64
x ./sbin/helpers/jfs2/fscklog
x ./sbin/helpers/jfs2/fsdb
x ./sbin/helpers/jfs2/fstype
x ./sbin/helpers/jfs2/istat
x ./sbin/helpers/jfs2/logform
x ./sbin/helpers/jfs2/logredo
x ./sbin/helpers/jfs2/logredo64
x ./sbin/helpers/jfs2/lsfs
x ./sbin/helpers/jfs2/mkfs
x ./sbin/helpers/jfs2/mount
x ./sbin/helpers/jfs2/umount
x ./sbin/helpers/jfs2/ncheck
x ./sbin/helpers/jfs2/quotacheck
x ./sbin/helpers/jfs2/rdump
x ./sbin/helpers/jfs2/restbyinode
x ./sbin/helpers/jfs2/rollback
x ./sbin/helpers/jfs2/rrestore
x ./sbin/helpers/jfs2/snapshot
x ./sbin/helpers/jfs2/backsnap
x ./sbin/helpers/jfs2/statfs64
x ./tmp
x ./tmp/lost+found
x ./bin
x ./etc/drivers
x ./etc/methods
x ./etc/microcode
x ./etc/objrepos/DSMOptions
x ./etc/objrepos/DSMOptions.vc
x ./etc/objrepos/DSMenu
x ./etc/objrepos/PDiagRes
x ./etc/objrepos/PDiagRes.vc
x ./etc/objrepos/PDiagTask
x ./etc/objrepos/PDiagTask.vc
x ./etc/objrepos/PDiagAtt
x ./etc/objrepos/PDiagAtt.vc
x ./etc/objrepos/PDiagDev
x ./etc/objrepos/PDiagDev.vc
x ./etc/objrepos/PdAt
x ./etc/objrepos/PdAt.vc
x ./etc/objrepos/PdAtXtd
x ./etc/objrepos/PdAtXtd.vc
x ./etc/objrepos/PdCn
x ./etc/objrepos/PdDv
x ./etc/objrepos/PdDv.vc
x ./etc/objrepos/PdPathAt
x ./etc/objrepos/PdPathAt.vc
x ./etc/methods.cfg
x ./etc/security/mkuser.default
x ./etc/security/mkuser.sys
x ./etc/security/fpm
x ./etc/security/fpm/custom
x ./etc/security/fpm/custom/high
x ./etc/security/fpm/custom/med
x ./etc/security/fpm/custom/default
x ./etc/security/fpm/data
x ./etc/security/fpm/data/high_fpm_list
x ./etc/security/fpm/data/med_fpm_list
x ./etc/security/fpm/data/default_fpm_list.example
x ./etc/security/fpm/data/status_fpm
x ./etc/dtappintegrate
x ./etc/init
x ./var
x ./var/adm
x ./var/adm/cron
x ./var/adm/cron/at.deny
x ./var/adm/cron/cron.deny
x ./var/adm/cron/log
x ./var/adm/cron/queuedefs
x ./var/adm/ras
x ./var/adm/ras/raspertune
x ./var/adm/ras/codepoint.cat
x ./var/adm/ras/platform
x ./var/adm/streams
x ./var/adm/sw
x ./var/adm/sw/tmp
x ./var/adm/sw/tmp/bos.rte.ILS
x ./var/adm/sw/tmp/bos.rte.bind_cmds
x ./var/adm/sw/tmp/bos.rte.console
x ./var/adm/sw/tmp/bos.rte.date
x ./var/adm/sw/tmp/bos.rte.edit
x ./var/adm/sw/tmp/bos.rte.iconv
x ./var/adm/sw/tmp/bos.rte.install
x ./var/adm/sw/tmp/bos.rte.libc
x ./var/adm/sw/tmp/bos.rte.libcfg
x ./var/adm/sw/tmp/bos.rte.libcur
x ./var/adm/sw/tmp/bos.rte.libpthreads
x ./var/adm/sw/tmp/bos.rte.loc
x ./var/adm/sw/tmp/bos.rte.methods
x ./var/adm/sw/tmp/bos.rte.misc_cmds
x ./var/adm/sw/tmp/bos.rte.mlslib
x ./var/adm/sw/tmp/bos.rte.net
x ./var/adm/sw/tmp/bos.rte.odm
x ./var/adm/wtmp
x ./var/locks
x ./etc/locks
x ./var/lost+found
x ./var/msgs
x ./var/news
x ./var/preserve
x ./var/security/fpm
x ./var/security/fpm/log
x ./var/spool
x ./var/spool/cron
x ./var/spool/cron/atjobs
x ./var/spool/cron/crontabs
x ./var/spool/cron/crontabs/adm
x ./var/spool/cron/crontabs/root
x ./var/spool/cron/crontabs/sys
x ./var/spool/lpd
x ./var/spool/lpd/qdir
x ./var/spool/lpd/stat
x ./var/spool/mqueue
x ./var/spool/qdaemon
x ./var/spool/writesrv
x ./var/tmp
x ./etc/pam.conf
x ./etc/security/tsd
x ./etc/security/tsd/tsd.dat
x ./etc/security/certificates
x ./etc/security/certificates/certificate_610
x ./home
x ./home/guest
x ./home/lost+found
syncroot: Processing root part installation status.
syncroot: Synchronizing installp software.
+-----------------------------------------------------------------------------+
Pre-installation Verification...
+-----------------------------------------------------------------------------+
Verifying selections...done
Verifying requisites...done
Results...

SUCCESSES
---------
Filesets listed in this section passed pre-installation verification
and will be installed.

Selected Filesets
-----------------
Java5.sdk 5.0.0.130 # Java SDK 32-bit
Java5_64.sdk 5.0.0.150 # Java SDK 64-bit
Tivoli_Management_Agent.client.rte 3.7.1.0 # Management Framework Endpoin...
X11.Dt.ToolTalk 6.1.0.0 # AIX CDE ToolTalk Support
X11.Dt.bitmaps 6.1.0.0 # AIX CDE Bitmaps
X11.Dt.helpinfo 6.1.0.0 # AIX CDE Help Files and Volumes
X11.Dt.helpmin 6.1.0.0 # AIX CDE Minimum Help Files
X11.Dt.rte 6.1.0.0 # AIX Common Desktop Environme...
X11.apps.xdm 6.1.0.1 # AIXwindows xdm Application
X11.base.rte 6.1.0.1 # AIXwindows Runtime Environment
X11.base.smt 6.1.0.1 # AIXwindows Runtime Shared Me...
X11.help.EN_US.Dt.helpinfo 6.1.0.0 # AIX CDE Help Files and Volum...
X11.loc.DE_DE.Dt.rte 6.1.0.0 # CDE Locale Configuration - G...
X11.loc.ES_ES.Dt.rte 6.1.0.0 # CDE Locale Configuration - S...
X11.loc.FR_FR.Dt.rte 6.1.0.0 # CDE Locale Configuration - F...
X11.loc.IT_IT.Dt.rte 6.1.0.0 # CDE Locale Configuration - I...
X11.loc.JA_JP.Dt.rte 6.1.0.0 # CDE Locale Configuration - J...
X11.loc.Ja_JP.Dt.rte 6.1.0.0 # CDE Locale Configuration - J...
X11.loc.KO_KR.Dt.rte 6.1.0.0 # CDE Locale Configuration - K...
X11.loc.PT_PT.Dt.rte 6.1.0.0 # CDE Locale Configuration - P...
X11.loc.RU_RU.Dt.rte 6.1.0.0 # CDE Locale Configuration - R...
X11.loc.ZH_CN.Dt.rte 6.1.0.0 # CDE Locale Configuration - S...
X11.loc.ZH_HK.Dt.rte 6.1.0.0 # CDE Locale Config - Simplifi...
X11.loc.ZH_SG.Dt.rte 6.1.0.0 # CDE Locale Config - Simplifi...
X11.loc.ZH_TW.Dt.rte 6.1.0.0 # CDE Locale Configuration - T...
X11.loc.Zh_CN.Dt.rte 6.1.0.0 # CDE Locale Configuration - S...
X11.loc.Zh_TW.Dt.rte 6.1.0.0 # CDE Locale Configuration - T...
X11.loc.de_DE.Dt.rte 6.1.0.0 # CDE Locale Configuration - G...
X11.loc.en_US.Dt.rte 6.1.0.0 # CDE Locale Configuration - U...
X11.loc.fr_FR.Dt.rte 6.1.0.0 # CDE Locale Configuration - F...
X11.loc.it_IT.Dt.rte 6.1.0.0 # CDE Locale Configuration - I...
X11.loc.ja_JP.Dt.rte 6.1.0.0 # CDE Locale Configuration - J...
X11.loc.ko_KR.Dt.rte 6.1.0.0 # CDE Locale Configuration - K...
X11.loc.zh_CN.Dt.rte 6.1.0.0 # CDE Locale Configuration - S...
X11.loc.zh_TW.Dt.rte 6.1.0.0 # CDE Locale Configuration - T...
X11.samples.apps.clients 6.1.0.0 # AIXwindows Sample X Consorti...
bos.64bit 6.1.0.1 # Base Operating System 64 bit...
bos.acct 6.1.0.1 # Accounting Services
bos.adt.base 6.1.0.0 # Base Application Development...
bos.adt.insttools 6.1.0.0 # Tool to Create installp Pack...
bos.aixpert.cmds 6.1.0.1 # AIX Security Hardening
bos.cdmount 6.1.0.0 # CD/DVD Automount Facility
bos.compat.links 6.1.0.0 # AIX 3.2 to 4 Compatibility L...
bos.compat.net 6.1.0.0 # AIX 3.2 TCP/IP Compatability...
bos.compat.termcap 6.1.0.0 # AIX 3.2 Termcap Source and L...
bos.diag.com 6.1.0.0 # Common Hardware Diagnostics
bos.diag.rte 6.1.0.0 # Hardware Diagnostics
bos.diag.util 6.1.0.0 # Hardware Diagnostics Utilities
bos.ecc_client.rte 6.1.0.0 # Electronic Customer Care Run...
bos.mh 6.1.0.0 # Mail Handler
bos.mp64 6.1.0.1 # Base Operating System 64-bit...
bos.net.ipsec.keymgt 6.1.0.0 # IP Security Key Management
bos.net.ipsec.rte 6.1.0.0 # IP Security
bos.net.ncs 6.1.0.0 # Network Computing System 1.5.1
bos.net.nfs.client 6.1.0.1 # Network File System Client
bos.net.nis.client 6.1.0.0 # Network Information Service ...
bos.net.snapp 6.1.0.0 # System Networking Analysis a...
bos.net.tcp.client 6.1.0.1 # TCP/IP Client Support
bos.net.tcp.server 6.1.0.0 # TCP/IP Server
bos.net.tcp.smit 6.1.0.0 # TCP/IP SMIT Support
bos.net.uucp 6.1.0.0 # Unix to Unix Copy Program
bos.perf.diag_tool 6.1.0.0 # Performance Diagnostic Tool
bos.perf.libperfstat 6.1.0.0 # Performance Statistics Libra...
bos.perf.perfstat 6.1.0.0 # Performance Statistics Inter...
bos.perf.tools 6.1.0.1 # Base Performance Tools
bos.perf.tune 6.1.0.0 # Performance Tuning Support
bos.pmapi.pmsvcs 6.1.0.0 # Performance Monitor API Kern...
bos.pmapi.tools 6.1.0.0 # Performance Monitor API Tools
bos.rte.archive 6.1.0.1 # Archive Commands
bos.rte.boot 6.1.0.1 # Boot Commands
bos.rte.control 6.1.0.1 # System Control Commands
bos.rte.security 6.1.0.1 # Base Security Function
bos.rte.serv_aid 6.1.0.1 # Error Log Service Aids
bos.suma 6.1.0.0 # Service Update Management As...
bos.sysmgt.loginlic 6.1.0.0 # License Management
bos.sysmgt.nim.client 6.1.0.0 # Network Install Manager - Cl...
bos.sysmgt.quota 6.1.0.0 # Filesystem Quota Commands
bos.sysmgt.serv_aid 6.1.0.1 # Software Error Logging and D...
bos.sysmgt.smit 6.1.0.0 # System Management Interface ...
bos.sysmgt.sysbr 6.1.0.1 # System Backup and BOS Instal...
bos.sysmgt.trace 6.1.0.1 # Software Trace Service Aids
bos.wpars 6.1.0.1 # AIX Workload Partitions
csm.client 1.7.0.0 # Cluster Systems Management C...
csm.core 1.7.0.0 # Cluster Systems Management Core
csm.deploy 1.7.0.0 # Cluster Systems Management D...
csm.diagnostics 1.7.0.0 # Cluster Systems Management P...
csm.dsh 1.7.0.0 # Cluster Systems Management Dsh
devices.artic960.diag 6.1.0.0 # IBM ARTIC960 Adapter Diagnos...
devices.artic960.rte 6.1.0.0 # IBM ARTIC960 Runtime Support
devices.artic960.ucode 6.1.0.0 # IBM ARTIC960 Adapter Software
devices.chrp.IBM.lhca.rte 6.1.0.1 # Infiniband Logical HCA Runti...
devices.chrp.IBM.lhea.rte 6.1.0.0 # Host Ethernet Adapter (HEA) ...
devices.chrp.base.ServiceRM 1.4.0.0 # RSCT Service Resource Manager
devices.chrp.base.diag 6.1.0.1 # RISC CHRP Base System Device...
devices.chrp.base.rte 6.1.0.1 # RISC PC Base System Device S...
devices.chrp.pci.rte 6.1.0.0 # PCI Bus Software (CHRP)
devices.chrp.vdevice.rte 6.1.0.0 # Virtual I/O Bus Support
devices.common.IBM.atm.rte 6.1.0.0 # Common ATM Software
devices.common.IBM.crypt.rte 6.1.0.0 # Cryptographic Common Runtime...
devices.common.IBM.cx.rte 6.1.0.0 # CX Common Adapter Software
devices.common.IBM.ethernet.rte 6.1.0.0 # Common Ethernet Software
devices.common.IBM.fc.hba-api 6.1.0.0 # Common HBA API Library
devices.common.IBM.fc.rte 6.1.0.0 # Common IBM FC Software
devices.common.IBM.hdlc.sdlc 6.1.0.0 # SDLC COMIO Device Driver Emu...
devices.common.IBM.ib.rte 6.1.0.1 # Infiniband Common Runtime En...
devices.common.IBM.ide.rte 6.1.0.0 # Common IDE I/O Controller So...
devices.common.IBM.iscsi.rte 6.1.0.0 # Common iSCSI Files
devices.common.IBM.ktm_std.rte 6.1.0.0 # Common Keyboard, Tablet, and...
devices.common.IBM.mpio.rte 6.1.0.1 # MPIO Disk Path Control Module
devices.common.IBM.scsi.rte 6.1.0.0 # Common SCSI I/O Controller S...
devices.common.IBM.sissas.rte 6.1.0.0 # Common IBM SAS RAID Software
devices.common.IBM.usb.rte 6.1.0.0 # USB System Software
devices.fcp.disk.array.rte 6.1.0.0 # FC SCSI RAIDiant Array Devic...
devices.fcp.disk.rte 6.1.0.1 # FC SCSI CD-ROM, Disk, Read/W...
devices.fcp.tape.rte 6.1.0.0 # FC SCSI Tape Device Software
devices.graphics.com 6.1.0.0 # Graphics Adapter Common Soft...
devices.ide.cdrom.rte 6.1.0.0 # IDE CDROM Device Software
devices.ide.disk.rte 6.1.0.0 # IDE Disk Device Software
devices.isa_sio.chrp.ecp.rte 6.1.0.0 # CHRP IEEE1284 Parallel Port ...
devices.isa_sio.pnpPNP.501.rte 6.1.0.0 # CHRP Serial Adapter Software...
devices.iscsi_sw.rte 6.1.0.0 # iSCSI Software Device Driver
devices.pci.00105000.com 6.1.0.0 # Common SAS Expansion Card De...
devices.pci.02105e51.rte 6.1.0.1 # Native Display Adapter Softw...
devices.pci.13100560.rte 6.1.0.0 # PCI Audio Adapter (13100560)...
devices.pci.14100401.rte 6.1.0.0 # Gigabit Ethernet-SX PCI Adap...
devices.pci.14101403.rte 6.1.0.0 # Gigabit Ethernet-SX Adapter ...
devices.pci.14101b02.rte 6.1.0.0 # GXT6500P Graphics Adapter So...
devices.pci.14101c02.rte 6.1.0.0 # GXT4500P Graphics Adapter So...
devices.pci.14102e00.diag 6.1.0.0 # IBM PCI SCSI RAID Adapter Di...
devices.pci.14102e00.rte 6.1.0.0 # IBM PCI SCSI RAID Adapter De...
devices.pci.14103302.rte 6.1.0.0 # GXT135P Graphics Adapter Sof...
devices.pci.14103e00.rte 6.1.0.0 # IBM PCI Token-Ring Adapter S...
devices.pci.14104e00.rte 6.1.0.0 # PCI ATM Adapter (14104e00) S...
devices.pci.14104f00.rte 6.1.0.0 # PCI ATM Adapter (14104f00) S...
devices.pci.14105000.rte 6.1.0.0 # PCI ATM Adapter (14105000) S...
devices.pci.14105e01.rte 6.1.0.0 # 622Mbps ATM PCI Adapter Soft...
devices.pci.14106602.diag 6.1.0.0 # PCI-X Dual Channel SCSI Adap...
devices.pci.14106602.rte 6.1.0.0 # PCI-X Dual Channel SCSI Adap...
devices.pci.14106802.rte 6.1.0.0 # Gigabit Ethernet-SX PCI-X Ad...
devices.pci.14106902.rte 6.1.0.1 # 10/100/1000 Base-TX PCI-X Ad...
devices.pci.14106e01.rte 6.1.0.0 # GXT4000P Graphics Adapter So...
devices.pci.14107001.rte 6.1.0.0 # GXT6000P Graphics Adapter So...
devices.pci.14107802.diag 6.1.0.0 # PCI-X Dual Channel Ultra320 ...
devices.pci.14107802.rte 6.1.0.0 # PCI-X Dual Channel Ultra320 ...
devices.pci.14107c00.rte 6.1.0.0 # PCI ATM Adapter (14107c00) S...
devices.pci.14108802.rte 6.1.0.0 # 2-Port Gigabit Ethernet-SX P...
devices.pci.14108902.rte 6.1.0.0 # 2-Port 10/100/1000 Base-TX P...
devices.pci.14108c00.rte 6.1.0.0 # ARTIC960Hx 4-Port Selectable...
devices.pci.14109f00.rte 6.1.0.0 # IBM 4758 PCI Cryptographic C...
devices.pci.1410bb02.rte 6.1.0.0 # 10 Gigabit-LR Ethernet PCI-X...
devices.pci.1410d002.com 6.1.0.0 # Common PCI iSCSI TOE Adapter...
devices.pci.1410d002.rte 6.1.0.0 # 1000 Base-TX PCI-X iSCSI TOE...
devices.pci.1410e501.rte 6.1.0.0 # IBM PCI-X Cryptographic Copr...
devices.pci.1410e601.rte 6.1.0.0 # IBM Crypto Accelerator Adapt...
devices.pci.1410ec02.rte 6.1.0.0 # 10 Gigabit Ethernet-LR PCI-X...
devices.pci.1410ff01.rte 6.1.0.0 # 10/100 Mbps Ethernet PCI Ada...
devices.pci.22106474.rte 6.1.0.0 # USB Host Controller (2210647...
devices.pci.23100020.rte 6.1.0.0 # IBM PCI 10/100 Ethernet Adap...
devices.pci.2b102725.rte 6.1.0.0 # GXT145 Graphics Adapter Soft...
devices.pci.33103500.rte 6.1.0.0 # USB Host Controller (3310350...
devices.pci.331121b9.com 6.1.0.0 # IBM PCI 2-Port Multiprotocol...
devices.pci.331121b9.rte 6.1.0.0 # IBM PCI 2-Port Multiprotocol...
devices.pci.4f111100.rte 6.1.0.0 # PCI 8-Port Asynchronous Adap...
devices.pci.4f111b00.rte 6.1.0.0 # PCI 128-Port Asynchronous Ad...
devices.pci.4f11c800.rte 6.1.0.0 # 2-Port Asynchronous EIA-232 ...
devices.pci.77101223.com 6.1.0.0 # PCI FC Adapter (77101223) Co...
devices.pci.77102224.com 6.1.0.1 # PCI-X FC Adapter (77102224) ...
devices.pci.99172704.rte 6.1.0.0 # USB Host Controller (9917270...
devices.pci.ad100501.rte 6.1.0.0 # IDE Adapter Driver for Winbo...
devices.pci.b315445a.rte 6.1.0.0 # PCI 1x/4x Infiniband Device ...
devices.pci.c1110358.rte 6.1.0.0 # USB Host Controller (c111035...
devices.pci.df1000f7.com 6.1.0.1 # Common PCI FC Adapter Device...
devices.pci.df1000f7.diag 6.1.0.0 # PCI FC Adapter Device Diagno...
devices.pci.df1000f7.rte 6.1.0.0 # PCI FC Adapter Device Software
devices.pci.e414a816.rte 6.1.0.0 # Gigabit Ethernet-SX Adapter ...
devices.pciex.b3157862.rte 6.1.0.0 # PCIe-X 4x Infiniband Device ...
devices.sas.rte 6.1.0.0 # Serial Attached SCSI Device ...
devices.scsi.disk.rte 6.1.0.0 # SCSI CD-ROM, Disk, Read/Writ...
devices.scsi.safte.rte 6.1.0.0 # SCSI Accessed Fault-Tolerant...
devices.scsi.ses.rte 6.1.0.0 # SCSI Enclosure Device Software
devices.tty.rte 6.1.0.0 # TTY Device Driver Support So...
devices.usbif.010100.rte 6.1.0.0 # USB Audio Device Driver
devices.usbif.03000008.rte 6.1.0.0 # USB 3D Mouse Client Driver
devices.usbif.030101.rte 6.1.0.0 # USB Keyboard Client Driver
devices.usbif.030102.rte 6.1.0.0 # USB Mouse Client Driver
devices.vdevice.IBM.l-lan.rte 6.1.0.0 # Virtual I/O Ethernet Software
devices.vdevice.IBM.v-scsi.rte 6.1.0.1 # Virtual SCSI Client Support
devices.vdevice.hvterm1.rte 6.1.0.0 # Virtual Terminal Devices
devices.vdevice.vty-server.rte 6.1.0.0 # Virtual Terminal Devices
ibmdebugger 6.0.0.0 # IBM Debugger for AIX
ifor_ls.base.cli 6.1.0.0 # License Use Management Runti...
invscout.com 2.2.0.1 # Inventory Scout Microcode Ca...
invscout.ldb 2.2.0.2 # Inventory Scout Logic Database
invscout.rte 2.2.0.12 # Inventory Scout Runtime
lum.base.cli 5.1.2.0 # License Use Management Runti...
lwi.runtime 6.1.0.0 # Lightweight Infrastructure R...
openssh.base.client 4.3.0.5301 # Open Secure Shell Commands
openssh.base.server 4.3.0.5301 # Open Secure Shell Server
perfagent.tools 6.1.0.0 # Local Performance Analysis &...
printers.rte 6.1.0.0 # Printer Backend
rpm.rte 3.0.5.41 # RPM Package Manager
rsct.core.auditrm 2.5.0.0 # RSCT Audit Log Resource Manager
rsct.core.errm 2.5.0.0 # RSCT Event Response Resource...
rsct.core.fsrm 2.5.0.0 # RSCT File System Resource Ma...
rsct.core.hostrm 2.5.0.0 # RSCT Host Resource Manager
rsct.core.lprm 2.5.0.0 # RSCT Least Privilege Resourc...
rsct.core.rmc 2.5.0.0 # RSCT Resource Monitoring and...
rsct.core.sec 2.5.0.0 # RSCT Security
rsct.core.sensorrm 2.5.0.0 # RSCT Sensor Resource Manager
rsct.core.sr 2.5.0.0 # RSCT Registry
rsct.core.utils 2.5.0.0 # RSCT Utilities
sysmgt.websm.apps 6.1.0.1 # Web-based System Manager App...
sysmgt.websm.framework 6.1.0.0 # Web-based System Manager Cli...
sysmgt.websm.rte 6.1.0.0 # Web-based System Manager Run...
vac.C 9.0.0.0 # IBM XL C Compiler
vac.C 9.0.0.2 # IBM XL C Compiler
vacpp.cmp.core 9.0.0.0 # IBM XL C/C++ Compiler

<<>>

+-----------------------------------------------------------------------------+
BUILDDATE Verification ...
+-----------------------------------------------------------------------------+
Verifying build dates...done
FILESET STATISTICS
------------------
217 Selected to be installed, of which:
217 Passed pre-installation verification
----
217 Total to be installed

+-----------------------------------------------------------------------------+
Installing Software...
+-----------------------------------------------------------------------------+

installp: APPLYING software for:
Java5.sdk 5.0.0.130

Filesets processed: 1 of 217 (Total time: 1 secs).

installp: APPLYING software for:
Java5_64.sdk 5.0.0.150

Filesets processed: 2 of 217 (Total time: 1 secs).

installp: APPLYING software for:
Tivoli_Management_Agent.client.rte 3.7.1.0

Filesets processed: 3 of 217 (Total time: 1 secs).

installp: APPLYING software for:
X11.Dt.bitmaps 6.1.0.0
X11.Dt.helpinfo 6.1.0.0
X11.Dt.helpmin 6.1.0.0

Filesets processed: 6 of 217 (Total time: 1 secs).

installp: APPLYING software for:
X11.base.smt 6.1.0.1

Filesets processed: 7 of 217 (Total time: 1 secs).

installp: APPLYING software for:
X11.help.EN_US.Dt.helpinfo 6.1.0.0

Filesets processed: 8 of 217 (Total time: 1 secs).

installp: APPLYING software for:
bos.acct 6.1.0.1

Filesets processed: 9 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.adt.base 6.1.0.0
bos.adt.insttools 6.1.0.0

Filesets processed: 11 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.compat.links 6.1.0.0
bos.compat.net 6.1.0.0
bos.compat.termcap 6.1.0.0

/usr/sbin/inetimp: 0822-037 fopen failed on file /etc/services of access mode: r+, errno = 2.
Filesets processed: 14 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.diag.util 6.1.0.0

Filesets processed: 15 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.mh 6.1.0.0

Filesets processed: 16 of 217 (Total time: 2 secs).

installp: APPLYING software for:
bos.net.nis.client 6.1.0.0
bos.net.snapp 6.1.0.0
bos.net.tcp.smit 6.1.0.0
bos.net.uucp 6.1.0.0

rm: 0653-609 Cannot remove bos.net.snapp.unpre_i.
The file system has read permission only.
rm: 0653-609 Cannot remove bos.net.snapp.unpre_i.
The file system has read permission only.
Filesets processed: 20 of 217 (Total time: 3 secs).

installp: APPLYING software for:
bos.perf.diag_tool 6.1.0.0
bos.perf.libperfstat 6.1.0.0
bos.perf.perfstat 6.1.0.0
bos.perf.tools 6.1.0.1

Filesets processed: 24 of 217 (Total time: 3 secs).

installp: APPLYING software for:
bos.pmapi.pmsvcs 6.1.0.0
bos.pmapi.tools 6.1.0.0

Filesets processed: 26 of 217 (Total time: 4 secs).

installp: APPLYING software for:
bos.rte.archive 6.1.0.1

Filesets processed: 27 of 217 (Total time: 4 secs).

installp: APPLYING software for:
bos.rte.boot 6.1.0.1

Filesets processed: 28 of 217 (Total time: 4 secs).
Note :- Full output had not been showed here.....

+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+

Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
Java5.sdk 5.0.0.130 ROOT APPLY SUCCESS
Java5_64.sdk 5.0.0.150 ROOT APPLY SUCCESS
Tivoli_Management_Agent.cli 3.7.1.0 ROOT APPLY SUCCESS
X11.Dt.bitmaps 6.1.0.0 ROOT APPLY SUCCESS
X11.Dt.helpinfo 6.1.0.0 ROOT APPLY SUCCESS
X11.Dt.helpmin 6.1.0.0 ROOT APPLY SUCCESS
X11.base.smt 6.1.0.1 ROOT APPLY SUCCESS
X11.help.EN_US.Dt.helpinfo 6.1.0.0 ROOT APPLY SUCCESS
bos.acct 6.1.0.1 ROOT APPLY SUCCESS
bos.adt.base 6.1.0.0 ROOT APPLY SUCCESS
bos.adt.insttools 6.1.0.0 ROOT APPLY SUCCESS
bos.compat.links 6.1.0.0 ROOT APPLY SUCCESS
bos.compat.net 6.1.0.0 ROOT APPLY SUCCESS
bos.compat.termcap 6.1.0.0 ROOT APPLY SUCCESS
bos.diag.util 6.1.0.0 ROOT APPLY SUCCESS
bos.mh 6.1.0.0 ROOT APPLY SUCCESS
bos.net.nis.client 6.1.0.0 ROOT APPLY SUCCESS
bos.net.snapp 6.1.0.0 ROOT APPLY SUCCESS
bos.net.tcp.smit 6.1.0.0 ROOT APPLY SUCCESS
bos.net.uucp 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.diag_tool 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.libperfstat 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.perfstat 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.tools 6.1.0.1 ROOT APPLY SUCCESS
bos.pmapi.pmsvcs 6.1.0.0 ROOT APPLY SUCCESS
bos.pmapi.tools 6.1.0.0 ROOT APPLY SUCCESS
bos.rte.archive 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.boot 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.control 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.security 6.1.0.1 ROOT APPLY SUCCESS
bos.rte.serv_aid 6.1.0.1 ROOT APPLY SUCCESS
bos.sysmgt.loginlic 6.1.0.0 ROOT APPLY SUCCESS
bos.sysmgt.quota 6.1.0.0 ROOT APPLY SUCCESS
bos.sysmgt.serv_aid 6.1.0.1 ROOT APPLY SUCCESS
bos.sysmgt.smit 6.1.0.0 ROOT APPLY SUCCESS
bos.sysmgt.sysbr 6.1.0.1 ROOT APPLY SUCCESS
bos.sysmgt.trace 6.1.0.1 ROOT APPLY SUCCESS
bos.wpars 6.1.0.1 ROOT APPLY SUCCESS
csm.deploy 1.7.0.0 ROOT APPLY SUCCESS
csm.diagnostics 1.7.0.0 ROOT APPLY SUCCESS
csm.dsh 1.7.0.0 ROOT APPLY SUCCESS
devices.artic960.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.artic960.ucode 6.1.0.0 ROOT APPLY SUCCESS
devices.chrp.IBM.lhca.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.chrp.IBM.lhea.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.chrp.base.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.chrp.pci.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.chrp.vdevice.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.atm.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.crypt.rt 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.ethernet 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.fc.hba-a 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.fc.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.hdlc.sdl 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.ib.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.common.IBM.ide.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.iscsi.rt 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.ktm_std. 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.mpio.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.common.IBM.scsi.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.sissas.r 6.1.0.0 ROOT APPLY SUCCESS
devices.common.IBM.usb.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.fcp.disk.array.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.fcp.disk.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.fcp.tape.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.graphics.com 6.1.0.0 ROOT APPLY SUCCESS
devices.ide.cdrom.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.ide.disk.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.isa_sio.chrp.ecp.rt 6.1.0.0 ROOT APPLY SUCCESS
devices.isa_sio.pnpPNP.501. 6.1.0.0 ROOT APPLY SUCCESS
devices.iscsi_sw.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.00105000.com 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.02105e51.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.pci.13100560.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14100401.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14101403.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14101b02.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14101c02.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14102e00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14103302.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14103e00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14104e00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14104f00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14105000.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14105e01.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14106802.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14106902.rte 6.1.0.1 ROOT APPLY SUCCESS
devices.pci.14106e01.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14107001.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14107802.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14107c00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14108802.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14108902.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14108c00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14109f00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410bb02.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410d002.com 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410d002.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410e501.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410e601.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410ec02.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.1410ff01.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.22106474.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.23100020.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.2b102725.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.33103500.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.331121b9.com 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.331121b9.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.4f111100.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.4f111b00.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.4f11c800.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.77101223.com 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.77102224.com 6.1.0.1 ROOT APPLY SUCCESS
devices.pci.99172704.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.ad100501.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.b315445a.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.c1110358.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.df1000f7.com 6.1.0.1 ROOT APPLY SUCCESS
devices.pci.df1000f7.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.e414a816.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pciex.b3157862.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.sas.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.scsi.disk.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.scsi.safte.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.scsi.ses.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.tty.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.usbif.010100.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.usbif.03000008.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.usbif.030101.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.usbif.030102.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.vdevice.IBM.l-lan.r 6.1.0.0 ROOT APPLY SUCCESS
devices.vdevice.IBM.v-scsi. 6.1.0.1 ROOT APPLY SUCCESS
devices.vdevice.hvterm1.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.vdevice.vty-server. 6.1.0.0 ROOT APPLY SUCCESS
ibmdebugger 6.0.0.0 ROOT APPLY FAILED
ibmdebugger 6.0.0.0 ROOT CLEANUP SUCCESS
invscout.com 2.2.0.1 ROOT APPLY SUCCESS
invscout.ldb 2.2.0.2 ROOT APPLY SUCCESS
invscout.rte 2.2.0.12 ROOT APPLY SUCCESS
lwi.runtime 6.1.0.0 ROOT APPLY SUCCESS
openssh.base.client 4.3.0.5301 ROOT APPLY SUCCESS
openssh.base.server 4.3.0.5301 ROOT APPLY SUCCESS
printers.rte 6.1.0.0 ROOT APPLY SUCCESS
sysmgt.websm.apps 6.1.0.1 ROOT APPLY SUCCESS
sysmgt.websm.framework 6.1.0.0 ROOT APPLY SUCCESS
X11.base.rte 6.1.0.1 ROOT APPLY SUCCESS
bos.64bit 6.1.0.1 ROOT APPLY SUCCESS
bos.aixpert.cmds 6.1.0.1 ROOT APPLY SUCCESS
bos.cdmount 6.1.0.0 ROOT APPLY SUCCESS
bos.diag.com 6.1.0.0 ROOT APPLY SUCCESS
bos.diag.rte 6.1.0.0 ROOT APPLY SUCCESS
bos.mp64 6.1.0.1 ROOT APPLY SUCCESS
bos.net.ncs 6.1.0.0 ROOT APPLY SUCCESS
bos.net.tcp.client 6.1.0.1 ROOT APPLY SUCCESS
bos.net.tcp.server 6.1.0.0 ROOT APPLY SUCCESS
bos.perf.tune 6.1.0.0 ROOT APPLY SUCCESS
devices.artic960.diag 6.1.0.0 ROOT APPLY SUCCESS
devices.chrp.base.diag 6.1.0.1 ROOT APPLY SUCCESS
devices.common.IBM.cx.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14102e00.diag 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14106602.diag 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14106602.rte 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.14107802.diag 6.1.0.0 ROOT APPLY SUCCESS
devices.pci.df1000f7.diag 6.1.0.0 ROOT APPLY SUCCESS
perfagent.tools 6.1.0.0 ROOT APPLY SUCCESS
sysmgt.websm.rte 6.1.0.0 ROOT APPLY SUCCESS
vac.C 9.0.0.0 ROOT APPLY SUCCESS
vac.C 9.0.0.2 ROOT APPLY SUCCESS
X11.Dt.ToolTalk 6.1.0.0 ROOT APPLY SUCCESS
X11.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.apps.xdm 6.1.0.1 ROOT APPLY SUCCESS
X11.loc.DE_DE.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ES_ES.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.FR_FR.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.IT_IT.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.JA_JP.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.Ja_JP.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.KO_KR.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.PT_PT.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.RU_RU.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ZH_CN.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ZH_HK.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ZH_SG.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ZH_TW.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.Zh_CN.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.Zh_TW.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.de_DE.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.en_US.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.fr_FR.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.it_IT.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ja_JP.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.ko_KR.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.zh_CN.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.loc.zh_TW.Dt.rte 6.1.0.0 ROOT APPLY SUCCESS
X11.samples.apps.clients 6.1.0.0 ROOT APPLY SUCCESS
bos.net.ipsec.rte 6.1.0.0 ROOT APPLY SUCCESS
bos.net.nfs.client 6.1.0.1 ROOT APPLY SUCCESS
bos.sysmgt.nim.client 6.1.0.0 ROOT APPLY SUCCESS
bos.net.ipsec.keymgt 6.1.0.0 ROOT APPLY SUCCESS
ifor_ls.base.cli 6.1.0.0 ROOT APPLY SUCCESS
lum.base.cli 5.1.2.0 ROOT APPLY SUCCESS
rpm.rte 3.0.5.41 ROOT APPLY SUCCESS
rsct.core.utils 2.5.0.0 ROOT APPLY SUCCESS
bos.ecc_client.rte 6.1.0.0 ROOT APPLY SUCCESS
bos.suma 6.1.0.0 ROOT APPLY SUCCESS
csm.core 1.7.0.0 ROOT APPLY SUCCESS
rsct.core.sec 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.sr 2.5.0.0 ROOT APPLY SUCCESS
vacpp.cmp.core 9.0.0.0 ROOT APPLY SUCCESS
csm.client 1.7.0.0 ROOT APPLY SUCCESS
rsct.core.rmc 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.sensorrm 2.5.0.0 ROOT APPLY SUCCESS
devices.chrp.base.ServiceRM 1.4.0.0 ROOT APPLY SUCCESS
rsct.core.auditrm 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.errm 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.fsrm 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.hostrm 2.5.0.0 ROOT APPLY SUCCESS
rsct.core.lprm 2.5.0.0 ROOT APPLY SUCCESS
bos.rte.archive 6.1.0.1 ROOT COMMIT SUCCESS
bos.rte.boot 6.1.0.1 ROOT COMMIT SUCCESS
bos.rte.control 6.1.0.1 ROOT COMMIT SUCCESS
bos.rte.security 6.1.0.1 ROOT COMMIT SUCCESS
bos.rte.serv_aid 6.1.0.1 ROOT COMMIT SUCCESS
vac.C 9.0.0.2 ROOT COMMIT SUCCESS
syncroot: Error synchronizing installp software.
syncroot: Returns Status = FAILURE
Workload partition MyTestWpar4 created successfully.
mkwpar: 0960-390 To start the workload partition, execute the following as root: startwpar [-v] MyTestWpar4
lpar47p682e_pub[/] >

to start WPAR

lpar47p682e_pub[/] > startwpar -v MyTestWpar3
Starting workload partition MyTestWpar3.
Mounting all workload partition file systems.
Mounting /wpars/MyTestWpar3
Mounting /wpars/MyTestWpar3/home
Mounting /wpars/MyTestWpar3/opt
Mounting /wpars/MyTestWpar3/proc
Mounting /wpars/MyTestWpar3/tmp
Mounting /wpars/MyTestWpar3/usr
Mounting /wpars/MyTestWpar3/var
Loading workload partition.
$corral_t = {
'name' => 'MyTestWpar3',
'wlm_cpu' => [
undef,
undef,
undef,
undef
],
'path' => '/wpars/MyTestWpar3',
'hostname' => 'MyTestWpar3',
'wlm_procVirtMem' => [
-1,
undef
],
'wlm_mem' => [
undef,
undef,
undef,
undef
],
'key' => 5,
'vips' => [
[
'en0',
'172.29.138.24',
'255.255.192.0',
'172.29.191.255'
]
],
'wlm_rset' => undef,
'opts' => 4,
'id' => 0
};
Exporting workload partition devices.
Starting workload partition subsystem cor_MyTestWpar3.
0513-059 The cor_MyTestWpar3 Subsystem has been started. Subsystem PID is 536778.
Verifying workload partition startup.
Return Status = SUCCESS.
lpar47p682e_pub[/] >
-------------------------------------------------------
lpar47p682e_pub[/] > syncroot -i
syncroot: Processing root part installation status.
syncroot: Installp root packages are currently synchronized.
syncroot: Root part is currently synchronized.
syncroot: Returns Status = SUCCESS
------------------------------------------------------------

To synchronising all File set from global to WPAR syncroot command needs to executed.

To remove WPAR from command line.

2008-07-11T12:58:00.002-07:00

par47p682e_pub[/] > rmwpar TestWpar3
rmwpar: Removing file system /wpars/TestWpar3/var.
rmlv: Logical volume fslv15 is removed.
rmwpar: Removing file system /wpars/TestWpar3/usr.
rmwpar: Removing file system /wpars/TestWpar3/tmp.
rmlv: Logical volume fslv14 is removed.
rmwpar: Removing file system /wpars/TestWpar3/proc.
rmwpar: Removing file system /wpars/TestWpar3/opt.
rmwpar: Removing file system /wpars/TestWpar3/home.
rmlv: Logical volume fslv13 is removed.
rmwpar: Removing file system /wpars/TestWpar3.
rmlv: Logical volume fslv12 is removed.

To remove WPAR first we need to stop WPAR in order to remove it.
After removing WPAR all filesystem related to that WPAR gets deleted.

Console login to WPAR

2008-07-11T12:58:00.001-07:00

par47p682e_pub[/] > lswpar
Name State Type Hostname Directory
----------------------------------------------------------
MyTestWpar1 A S MyTestWpar1 /wpars/MyTestWpar1
MyTestWpar2 A S MyTestWpar2 /wpars/MyTestWpar2
TestWpar3 A S TestWpar3 /wpars/TestWpar4

lpar47p682e_pub[/] > clogin MyTestWpar4
*******************************************************************************
* *
* *
* Welcome to AIX Version 6.1! *
* *
* *
* Please see the README file in /usr/lpp/bos for information pertinent to *
* this release of the AIX Operating System. *
* *
* *
*******************************************************************************

#

You can also connect to WPAR via ssh. It will have its own user id for authentication.

lsvg, lspv commands wont work as all filesystem alocated to WPAR has been created in AIX 6. global environment.

# df -k
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/fslv12 131072 104404 21% 2109 9% /
/dev/fslv13 131072 128640 2% 7 1% /home
/opt 262144 119808 55% 3048 11% /opt
/proc - - - - - /proc
/dev/fslv14 131072 128424 3% 9 1% /tmp
/usr 3538944 158320 96% 91414 69% /usr
/dev/fslv15 131072 116816 11% 372 2% /var

To do changes in above mentioned file system . We need to do in global environment. Not frow WPAR. All system adminstartion task of increasing , decreasing, adding, deleting File system are to be done from AIX global environment.

Starting & Stopping WPAR command output

2008-07-11T12:56:00.001-07:00

NOTE :- All IP shown in the command has been altered as displaying IP on net is invitation to problem.

To reboot test wpar 2 command is

/usr/bin/stopwpar -r MyTestWpar2 Flag r stands for reboot.

output

Stopping workload partition MyTestWpar2
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Stopping workload partition MyTestWpar2.
Stopping workload partition subsystem cor_MyTestWpar2.
0513-044 The cor_MyTestWpar2 Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
Unmounting all workload partition file systems.
Starting workload partition MyTestWpar2.
Mounting all workload partition file systems.
Loading workload partition.
Exporting workload partition devices.
Starting workload partition subsystem cor_MyTestWpar2.
0513-059 The cor_MyTestWpar2 Subsystem has been started. Subsystem PID is 696392.
Verifying workload partition startup.

=============================================

To stop WPAR MyTestWpar2

/usr/sbin/stopwpar MyTestWpar2

output

Stopping workload partition MyTestWpar2.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Stopping workload partition MyTestWpar2.
Stopping workload partition subsystem cor_MyTestWpar2.
0513-044 The cor_MyTestWpar2 Subsystem was requested to stop.
stopwpar: 0960-261 Waiting up to 600 seconds for workload partition to halt.
Shutting down all workload partition processes.
Unmounting all workload partition file systems.

All file systems related to testwpar 2 will be unmounted.

lpar47p682e_pub[/] > df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 0.12 0.02 87% 8105 63% /
/dev/hd2 3.38 0.15 96% 91414 69% /usr
/dev/hd9var 0.25 0.24 6% 477 1% /var
/dev/hd3 0.25 0.25 1% 53 1% /tmp
/dev/hd1 0.12 0.12 1% 8 1% /home
/dev/hd11admin 0.12 0.12 1% 5 1% /admin
/proc - - - - - /proc
/dev/hd10opt 0.25 0.11 55% 3048 11% /opt
p650:/stage/middleware 73.94 13.38 82% 37383 2% /stage/middleware
192.168.1.12:/userdata/20005533 10.00 9.92 1% 19 1% /home/u0005533
/dev/fslv00 0.12 0.10 21% 2106 9% /wpars/MyTestWpar1
/dev/fslv01 0.12 0.12 2% 5 1% /wpars/MyTestWpar1/home
/dev/fslv02 0.25 0.11 56% 3048 11% /wpars/MyTestWpar1/opt
/proc - - - - - /wpars/MyTestWpar1/proc
/dev/fslv03 0.12 0.12 3% 13 1% /wpars/MyTestWpar1/tmp
/dev/fslv04 3.38 0.14 96% 91483 71% /wpars/MyTestWpar1/usr
/dev/fslv05 0.12 0.11 10% 371 2% /wpars/MyTestWpar1/var
lpar47p682e_pub[/] >

We will not able to ping that TestWpar 172.29.138.23

lpar47p682e_pub[/] > ping 172.29.138.23
PING 172.29.138.23: (172.29.138.23): 56 data bytes

Alias IP 172.29.138.23 will be removed from en0 network adapter....

lpar47p682e_pub[/] > ifconfig -a
en1: flags=1e080863,480
inet 10.153.3.101 netmask 0xffff0000 broadcast 10.153.255.255
tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1
en0: flags=1e080863,480
inet 172.29.138.149 netmask 0xffffc000 broadcast 172.29.191.255
inet 172.29.138.203 netmask 0xffffc000 broadcast 172.29.191.255
tcp_sendspace 262144 tcp_recvspace 262144 rfc1323 1
lo0: flags=e08084b
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
lpar47p682e_pub[/] >

lpar47p682e_pub[/] > lswpar
Name State Type Hostname Directory
----------------------------------------------------------
MyTestWpar1 A S MyTestWpar1 /wpars/MyTestWpar1
MyTestWpar2 D S MyTestWpar2 /wpars/MyTestWpar2 ---- >

D state stands for partition is not activated.
=======================================================================

To start WPAR
To start WPAR TestWpar2

lpar47p682e_pub[/] > startwpar MyTestWpar2
Starting workload partition MyTestWpar2.
Mounting all workload partition file systems.
Loading workload partition.
Exporting workload partition devices.
Starting workload partition subsystem cor_MyTestWpar2.
0513-059 The cor_MyTestWpar2 Subsystem has been started. Subsystem PID is 291026.
Verifying workload partition startup.

Filesystem for testwpar2 is now in mounted state.

lpar47p682e_pub[/] > df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 0.12 0.02 87% 8105 63% /
/dev/hd2 3.38 0.15 96% 91414 69% /usr
/dev/hd9var 0.25 0.24 6% 477 1% /var
/dev/hd3 0.25 0.25 1% 53 1% /tmp
/dev/hd1 0.12 0.12 1% 8 1% /home
/dev/hd11admin 0.12 0.12 1% 5 1% /admin
/proc - - - - - /proc
/dev/hd10opt 0.25 0.11 55% 3048 11% /opt
p650:/stage/middleware 73.94 13.38 82% 37383 2% /stage/middleware
192.168.1.12:/userdata/20005533 10.00 9.92 1% 19 1% /home/u0005533
/dev/fslv00 0.12 0.10 21% 2106 9% /wpars/MyTestWpar1
/dev/fslv01 0.12 0.12 2% 5 1% /wpars/MyTestWpar1/home
/dev/fslv02 0.25 0.11 56% 3048 11% /wpars/MyTestWpar1/opt
/proc - - - - - /wpars/MyTestWpar1/proc
/dev/fslv03 0.12 0.12 3% 13 1% /wpars/MyTestWpar1/tmp
/dev/fslv04 3.38 0.14 96% 91483 71% /wpars/MyTestWpar1/usr
/dev/fslv05 0.12 0.11 10% 371 2% /wpars/MyTestWpar1/var
/dev/fslv06 0.12 0.10 21% 2107 9% /wpars/MyTestWpar2
/dev/fslv07 0.12 0.12 2% 5 1% /wpars/MyTestWpar2/home
/dev/fslv08 0.25 0.11 56% 3048 11% /wpars/MyTestWpar2/opt
/proc - - - - - /wpars/MyTestWpar2/proc
/dev/fslv09 0.12 0.12 3% 10 1% /wpars/MyTestWpar2/tmp
/dev/fslv10 3.38 0.14 96% 91483 71% /wpars/MyTestWpar2/usr
/dev/fslv11 0.12 0.11 11% 373 2% /wpars/MyTestWpar2/var
lpar47p682e_pub[/] >
=============================================================================

To maintain software for sytem WPAR with Global AIX

syncwpar [ [-a] [-i] | [-F] [-r] ] [-p] [-v] [-X]
{ -A | -f wparNamesFile | wparName }

Flags:
-a = Perform additional installation only.
-i = Only update installp filesets.
-F = Force copy RPM files.
-r = Only update RPM files.
-p = Preview operation. Do not actually perform the synchronization.
-v = Verbose mode.
-X = Expand file system space if possible.
-A = Apply operation to all corrals.
-f = Specifies a file containing a list of workload partitions.

Note : - If system WPAR has /usr private file system for WPAR. Synchronisation will Fail ...

Starting & Stopping WPAR command output

2008-07-11T12:56:00.000-07:00

Listing WPAR Command outputs

2008-07-11T12:52:00.000-07:00

Server consist of three Test WPAR

To list All WPAR lswpar comamnd is used.

lpar47p682e_pub[/] > lswpar --help
Usage:
Tabular: lswpar [-D | -M | -N] [-a fieldname[,...]]
[-q] [-s state] [-t type] [wparname ...]

Paragraph: lswpar {-G | -L | -R | -S | -T}
[-s state] [-t type] [wparname ...]

Delimited: lswpar {-c | -d delim} [-a fieldname[,...] |
-G | {-D|-M|-N} [-a fieldName[,...]] | -R | -S | -T]
[-q] [-s state] [-t type] [wparname ...]

Flags:
-a = Comma-separated list of field names to print.
-c = Colon delimited output (equivalent to -d:).
-d = Output delimited by specified delimiter.
-D = Print device exports.
-G = Print general information (paragraph format).
-L = Long format.
-M = File systems or file system dependencies.
-N = Print network information.
-q = Suppress output header.
-R = Print resource information (paragraph format).
-S = Print security information (paragraph format).
-s = Only print information about workload partitions in a
given state. Valid states are D (Defined), L (Loaded),
A (Active), F (Frozen), P (Paused), T (Transitional)
and B (Broken).
-T = Print operation information.
-t = Only print information about workload partitions of a given type. Valid
types are S (System), A (Application) and C (Checkpointable).

To have detail inormation of WPAR Use -L flag.

=======================================================================

lpar47p682e_pub[/] > lswpar
Name State Type Hostname Directory
----------------------------------------------------------
MyTestWpar1 A S MyTestWpar1 /wpars/MyTestWpar1
MyTestWpar2 A S MyTestWpar2 /wpars/MyTestWpar2
TestWpar3 A S TestWpar3 /wpars/TestWpar3
lpar47p682e_pub[/] > lswpar TestWpar3

Name State Type Hostname Directory
----------------------------------------------------
TestWpar3 A S TestWpar3 /wpars/TestWpar3

========================================================================

THere are diffrent state of WPAR -- ref Man page

The lswpar command prints information about one or more specified workload partition (or all workload partitions if none are specified) to standard
output.

You can filter all listings according to the following workload partition states using the -s flag:
Defined
The workload partition has been defined by the mkwpar command and is ready for use, but is not active. Start workload partitions in this state
with the startwpar command.
Loaded
The workload partition has been configured in the kernel, but processes have not yet been started. Note: This state is visible only to
programmatic consumers that use the lswpar command to start a workload partition.
Active
The workload partition is running normally.
Frozen
A checkpoint operation is initiated, and the processes of the workload partition are quiesced, awaiting the storing phase. Note: The Frozen
state is only visible when you use the lswpar command to checkpoint a workload partition. The checkpoint or restart function requires additional
software package other than base WPAR.
Paused
A checkpoint or restart operation has been performed, and the workload partition's processes are ready to be resumed or killed. The checkpoint
or restart functionality requires additional software.
Transitional
An administrative operation is in progress. The workload partition is in the process of being created, started, stopped, configured, and so on.
Broken
An administrative operation failed, leaving this workload partition in an unusable state.

You can filter all listings according to the following workload partition types using the -t flag:
Application
This is an application workload partition, running a single process (or a group of processes invoked by that means) without isolated system
services. The process or group of processes inherits its operating environment (file systems, security, devices. and so on) from the environment
where the application workload partition was created.
System
This is a system workload partition, emulating an independent, fully-functional instance of the operating system.

If additional checkpoint or restart software is installed, you can also specify the following type:
Checkpointable

This workload partition is enabled for checkpoint or restart functions. Tip: This is not a mutually exclusive workload partition type.
Checkpointable workload partitions are still either System or Application workload partitions.

=======================================================================
To list detail of MyTestWpar1

====================================================================

lpar47p682e_pub[/] > lswpar -L MyTestWpar1
=================================================================
MyTestWpar1 - Active
=================================================================
GENERAL
Type: S
Owner: root
Hostname: MyTestWpar1
Directory: /wpars/MyTestWpar1
Start/Stop Script:
Auto: yes
Private /usr: yes
Checkpointable: no
Application:

NETWORK
Interface Address Mask/Prefix Broadcast
-----------------------------------------------------------------
en0 172.29.138.203 255.255.192.0 172.29.191.255

FILE SYSTEMS
MountPoint Device Vfs Nodename Options
-----------------------------------------------------------------
/wpars/MyTestWpar1 /dev/fslv00 jfs2
/wpars/MyTestWpar1/home /dev/fslv01 jfs2
/wpars/MyTestWpar1/opt /dev/fslv02 jfs2 rw
/wpars/MyTestWpar1/proc /proc namefs rw
/wpars/MyTestWpar1/tmp /dev/fslv03 jfs2
/wpars/MyTestWpar1/usr /dev/fslv04 jfs2 rw
/wpars/MyTestWpar1/var /dev/fslv05 jfs2

RESOURCE CONTROLS
Active: yes
Resource Set:
CPU Shares: 20
CPU Limits: 0%-100%,100%
Memory Shares: 20
Memory Limits: 0%-100%,100%
Per-Process Virtual Memory Limit: unlimited
Total Processes: unlimited
Total Threads: unlimited

OPERATION
Operation: none
Process ID:
Start Time:

SECURITY SETTINGS
Privileges: PV_AU_,PV_AU_ADD,PV_AU_ADMIN,PV_AU_PROC,PV_AU_READ,
PV_AU_WRITE,PV_AZ_ADMIN,PV_AZ_CHECK,PV_AZ_READ,PV_AZ_ROOT,
PV_DAC_,PV_DAC_GID,PV_DAC_O,PV_DAC_R,PV_DAC_RID,PV_DAC_UID,
PV_DAC_W,PV_DAC_X,PV_DEV_CONFIG,PV_DEV_QUERY,PV_FS_CHOWN,
PV_FS_CHROOT,PV_FS_CNTL,PV_FS_LINKDIR,PV_FS_MKNOD,
PV_FS_MOUNT,PV_FS_QUOTA,PV_KER_ACCT,PV_KER_CONF,PV_KER_DR,
PV_KER_EWLM,PV_KER_EXTCONF,PV_KER_IPC,PV_KER_IPC_O,
PV_KER_IPC_R,PV_KER_IPC_W,PV_KER_LVM,PV_KER_NFS,PV_KER_RAC,
PV_KER_RAS_ERR,PV_KER_REBOOT,PV_NET_PORT,PV_PROC_CKPT,
PV_PROC_CORE,PV_PROC_CRED,PV_PROC_ENV,PV_PROC_PRIO,
PV_PROC_RAC,PV_PROC_RTCLK,PV_PROC_SIG,PV_PROC_TIMER,
PV_PROC_VARS,PV_PROC_PRIV,PV_SU_UID,PV_TCB,PV_TP,PV_TP_SET,
PV_MIC,PV_MIC_CL,PV_LAB_,PV_LAB_CL,PV_LAB_CLTL,PV_LAB_LEF,
PV_LAB_SLDG,PV_LAB_SLDG_STR,PV_LAB_SL_FILE,PV_LAB_SL_PROC,
PV_LAB_SL_SELF,PV_LAB_SLUG,PV_LAB_SLUG_STR,PV_LAB_TL,
PV_MAC_,PV_MAC_CL,PV_MAC_R,PV_MAC_R_CL,PV_MAC_R_STR,
PV_MAC_R_PROC,PV_MAC_W,PV_MAC_W_CL,PV_MAC_W_DN,PV_MAC_W_UP,
PV_MAC_W_PROC,PV_MAC_OVRRD,PV_KER_SECCONFIG,
PV_PROBEVUE_TRC_USER,PV_PROBEVUE_TRC_USER_SELF

DEVICE EXPORTS
Name Type
-----------------------------------------------------------------
/dev/null pseudo
/dev/tty pseudo
/dev/console pseudo
/dev/zero pseudo
/dev/clone pseudo
/dev/sad clone
/dev/xti/tcp clone
/dev/xti/tcp6 clone
/dev/xti/udp clone
/dev/xti/udp6 clone
/dev/xti/unixdg clone
/dev/xti/unixst clone
/dev/error pseudo
/dev/errorctl pseudo
/dev/audit pseudo
/dev/nvram pseudo

=========================================================================

Listing file system of diffrent WPAR in server . THere are three WPAR.

lpar47p682e_pub[/] > df -g
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 0.12 0.01 91% 8120 68% /
/dev/hd2 3.38 0.15 96% 91414 69% /usr
/dev/hd9var 0.25 0.24 6% 488 1% /var
/dev/hd3 0.25 0.25 1% 55 1% /tmp
/dev/hd1 0.12 0.12 1% 8 1% /home
/dev/hd11admin 0.12 0.12 1% 5 1% /admin
/proc - - - - - /proc
/dev/hd10opt 0.25 0.11 55% 3048 11% /opt
p650:/stage/middleware 73.94 13.38 82% 37383 2% /stage/middleware
192.168.1.12:/userdata/20005533 10.00 9.92 1% 19 1% /home/u0005533
------------------------------------------------------------------------------
WPAR1 Filesystem
/dev/fslv00 0.12 0.10 21% 2107 9% /wpars/MyTestWpar1
/dev/fslv01 0.12 0.12 2% 5 1% /wpars/MyTestWpar1/home
/dev/fslv02 0.25 0.11 56% 3048 11% /wpars/MyTestWpar1/opt
/proc - - - - - /wpars/MyTestWpar1/proc
/dev/fslv03 0.12 0.12 3% 13 1% /wpars/MyTestWpar1/tmp
/dev/fslv04 3.38 0.14 96% 91483 71% /wpars/MyTestWpar1/usr
/dev/fslv05 0.12 0.11 10% 371 2% /wpars/MyTestWpar1/var
/proc - - - - - /wpars/MyTestWpar1/proc
------------------------------------------------------------------------------
WPAR 2 File system
/dev/fslv06 0.12 0.10 21% 2112 9% /wpars/MyTestWpar2
/dev/fslv07 0.12 0.12 2% 5 1% /wpars/MyTestWpar2/home
/dev/fslv08 0.25 0.11 56% 3048 11% /wpars/MyTestWpar2/opt
/proc - - - - - /wpars/MyTestWpar2/proc
/dev/fslv09 0.12 0.12 3% 10 1% /wpars/MyTestWpar2/tmp
/dev/fslv10 3.38 0.14 96% 91483 71% /wpars/MyTestWpar2/usr
/dev/fslv11 0.12 0.11 11% 374 2% /wpars/MyTestWpar2/var
------------------------------------------------------------------------------
WPAR 3 FIle System
/dev/fslv12 0.12 0.10 21% 2103 9% /wpars/MyTestWpar3
/dev/fslv13 0.12 0.12 2% 5 1% /wpars/MyTestWpar3/home
/opt 0.25 0.11 55% 3048 11% /wpars/MyTestWpar3/opt
/proc - - - - - /wpars/MyTestWpar3/proc WPAR 3
/dev/fslv14 0.12 0.12 3% 9 1% /wpars/MyTestWpar3/tmp
/usr 3.38 0.15 96% 91414 69% /wpars/MyTestWpar3/usr
/dev/fslv15 0.12 0.11 11% 370 2% /wpars/MyTestWpar3/var
lpar47p682e_pub[/] >