Sponsored Content
Full Discussion: Versioned WPAR's
Operating Systems AIX Versioned WPAR's Post 302915665 by firefox111 on Thursday 4th of September 2014 07:42:39 AM
Old 09-04-2014
Hi bakunin,

I totally agree.

The problem is, one of our customers needs to run old AIX5.2 and 5.3 Systems on P7 Hardware (applications do not run on AIX6 or AIX7). The only way to do this is to use the versioned WPAR's. And after all he wants these applications to be highly available Smilie
 

9 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

snmpget not working on AIX shared wpar

Hi, I have a shared AIX wpar configured. I have started snmpd process on shared AIX wpar. But when i tried to query a MIB id using the following command /opt/OV/bin/snmpget -d -v 1 -c public -p <hostname> .1.3.6.1.2.1.1.7.0 i get the following error message #... (0 Replies)
Discussion started by: avazeer
0 Replies

2. AIX

Unexpected Behaviour with WPAR

Hello, We have a system running AIX 6.1.7.1. We have created a Workload Partition(wpar) on this system with wpar specific routing enabled. On wpar, we are running DNS (UDP/53) and syslog (UDP/514). en0: 1.1.1.1/255.255.255.0 NOT assigned to any wpar en1:... (0 Replies)
Discussion started by: 03sep2011
0 Replies

3. AIX

Virtualization: WPAR vs LPAR

seems to be WPAR is quite easy to set up..without additional licenses.. If I don't need Linux and all my legacy and new apps are happy in AIX 7.1 (the latest OS), I could save all troubles and use WPAR. Can someone comment on this ?? One copy of OS to maintain, so to speak.. ... (4 Replies)
Discussion started by: ppchu99
4 Replies

4. Shell Programming and Scripting

WPAR monitoring shell script suggestions needed

Hi All, This is for WPAR monitoring shell script, earlier opened thread was closed, had to open a new thread, as suggested I have used script as below, But am trying to get the output in below format, need suggestions with it. Below is the lswpar output, required output format. ... (7 Replies)
Discussion started by: aix_admin_007
7 Replies

5. UNIX for Advanced & Expert Users

LPAR,DLPAR and WPAR

Can anyone please let know difference between LPAR/DLPAR/WPAR. and its purpose ??? (3 Replies)
Discussion started by: Pavithran
3 Replies

6. AIX

Wpar network,i'm confused

Hi. I've setup a wpar on aix mkwpar -h ibmunix2 -i -r -N interface=en0 address=10.6.0.1 netmask=255.255.255.0 -n ibmunix2 When i log into ibmunix2 it can't ping any external host,include the ibm host. How to set route for network please? I've set ibmunix2 with a different subnet. ... (7 Replies)
Discussion started by: Linusolaradm1
7 Replies

7. AIX

How to Load a CICS IPC Kernel Extension in a versioned "rootvg" WPAR ?

Anyone running CICS TX in a WPAR ? In my attempts to run CICS TX 5.1.0.1 in a WPAR..... CICS fails to start due to unable to load a CICS IPC Kernel Extension. The Kernel Extension is 64 bit (so not a 32 vs 64 bit issue). Base system/LPAR is Power8 and AIX 7.1 TL3 SP5. WPAR is versioned... (4 Replies)
Discussion started by: The Doctor
4 Replies

8. AIX

No iscsi available in newly created AIX wpar

AIX 7.1 New to WPAR, hopefully just missing something simple here. Creating the WPAR like this..... (The box where the WPAR is hosted does have an iscsi protocol device) mkwpar -h wpar08 -l -n wpar08 -N interface=en0 address=xxx.xx.xx.xxx netmask=255.255.255.0 -D devname=/dev/iscsi0 -D... (0 Replies)
Discussion started by: TomR
0 Replies

9. AIX

Error doing clogin into a wpar

I have this error when I'm trying to do clogin from AIX 7200-00-00-0000 into a wpar with AIX 5.2 abanksPaDesa2:/> clogin AbanksBDPA_wpar exec: A file or directory in the path name does not exist somebody can help me to fix this? I'm restoring the wpar from wpar mksysb not a mksysb from... (2 Replies)
Discussion started by: sandra25350
2 Replies
sys_attrs_cam(5)						File Formats Manual						  sys_attrs_cam(5)

NAME
sys_attrs_cam, sys_attrs_cam_disk, sys_attrs_cam_tape - SCSI CAM I/O subsystem attributes DESCRIPTION
This reference page lists and describes attributes for the following kernel subsystems associated with the SCSI CAM I/O system: cam cam_adapter-id cam_disk cam_tape An asterisk (*) precedes the name of an attribute that is modifiable at run time. However, the ability to modify the value at run-time may be a software requirement. Read the attribute description carefully to determine whether run-time configuration should ever be done manu- ally. Refer to the sys_attrs(5) reference page for an introduction to the topic of kernel subsystem attributes. cam and Adapter-Specific Cam Subsystem Attributes Values of attributes for the CAM (cam) subsystem and adapter-specific (cam_adapter-id) CAM subsystems should never be modified. cam_disk Subsystem Attributes Attributes for the cam_disk subsystem should be changed internally or under the direction of support personnel. Most of these attributes have a global effect across all disk devices. If the affected devices are of the same type, a global change may be appropriate. However, global changes applied to devices with different requirements is likely to adversely affect some of the devices. The Hardware Manager application allows you to apply device-specific adjustments and it is recommended that you use this interface. Number of seconds that the subsystem waits in the presence of repeated device busy signals before performing a bus device reset operation on the device. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. This attribute has effect only in a TruCluster environment. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. This attribute has effect only in a TruCluster environment. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. This attribute has effect only in a TruCluster environment. Do not modify the default setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. A value that indicates how long to wait after the start of constant "no connection" errors for the disk device before starting recovery procedure. The default value indicates that all bits are set to 1. This specifies that disk driver defaults for this wait interval are applied. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. A set- ting change is global; that is, it overrides the default wait interval for all disk drivers and is likely to cause unpredictable behavior in some devices. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. Disk drive initialization state, which is set by the subsystem. This attribute is query only. A query-only identifier that is set by the subsystem. A query-only identifier that is set by the subsystem. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. Default value: 2 (spinups) Number of seconds that device polling reveals a drive is inactive before spinning down the disk. Default value: 30 (seconds) Minimum value: 5 Maximum value: 65,535 cam_tape Subsystem Attributes Do not modify the default setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. Default value: 0 A value queried by the tape device driver to determine its initialization state. You cannot modify this variable. The driver changes the value from 0 (when the system starts to boot) to 1 (during the boot operation). A value that specifies the system behavior when a write-locked tape is opened with the O_RDWR or O_WRONLY flag. The default and rec- ommended behavior (1) is to return failure on the open operation. The alternate behavior (0) is to allow the open operation but return failure on an attempt to write to the tape. Default value: 1 It is recommended that you do not change the default. The 0 value is intended only for customers whose applications ran on DIGITAL UNIX versions earlier than Version 4.0B and depend on the open behavior in effect for those earlier versions. SEE ALSO
sys_attrs(5) sys_attrs_cam(5)
All times are GMT -4. The time now is 01:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy