Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Hello all,
I have been trying to run commands that collect basic info from the VIO's
The issue I am having is setting the env with the "oem_setup_env" after I login as "padmin".
I usually do the following:
ssh server command
ssh root@server date , but I need to login set the env and... (0 Replies)
Hi Guys,
I'm working on building a new 595 machine.. I'm try to achieve high availability for the VIO clients using 2 VIO servers, The ethernet part is satisfied using SEA failover, Now how do I achieve redundancy for the disks, its the servers internal disk attached to the scsi cards...
... (2 Replies)
I am planning carving out dual VIO servers on a P750 based and would like to know how to allocate internal disks to the VIOS. This has 4 internal disks and I would to assign 2 disks to each VIO.
This is what I was thinking of assigning . Any advise?
vio1
U5802.001.9K8H757-P1-C1 PCI-E x8... (17 Replies)
I have same lun (hdisk3) assigned to 2 vios server (dual vio server) and this is mapped to the client lpar. I have sddpcm on the VIO.
On the VIOA, the attributes for fscsi1 and fscsi3 are set to fast_fail and dyntrk is set to yes
Now, if I do a lqueryvg -Atp on the hdisk3, I get a "DISK... (4 Replies)
I am working in AIX. In a P series machine both aix and linux os can install.. specific command is there for aix to list out the vio servers details mapped in a frame(ie. lssrc "IBM.ManagementServer", like that..) is there any command is der to list out vio servers details in linux or how to find... (1 Reply)
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Hi,
I am facing an issue in vio server. When I run
bosboot -ad /dev/hdisk0
I am getting an error
trustchk: Verification of attributes failed: /usr/sbin/bootinfo
: accessauths
regards,
vjm
Please use code tags next time for your code and data. (8 Replies)
I hope someone has experienced this problem before and can help. I have a P730 (8231-E2D) which is fitted with 8 IBM SAS disks on 2 separate SISSAS controllers. The disk type is ST9146853SS (Seagate SAS 146Gb).
The problem occurs when I try to install the VIO server software at 2.2.3. It... (3 Replies)
We've got two datacenters and in every datacenter 2 VIOs.
The VIO manages the I/O of the LPARs. So: Is it possible to reboot the VIO without shuting down an LPAR:wall: (4 Replies)
Discussion started by: DiViN3
4 Replies
LEARN ABOUT DEBIAN
env::ps1
Env::PS1(3pm) User Contributed Perl Documentation Env::PS1(3pm)NAME
Env::PS1 - prompt string formatter
SYNOPSIS
# use the import function
use Env::PS1 qw/$PS1/;
$ENV{PS1} = 'u@h $ ';
print $PS1;
$readline = <STDIN>;
# or tie it yourself
tie $prompt, 'Env::PS1', 'PS1';
# you can also tie a scalar ref
$format = 'u@h$ ';
tie $prompt, 'Env::PS1', $format;
DESCRIPTION
This package supplies variables that are "tied" to environment variables like 'PS1' and 'PS2', if read it takes the contents of the
variable as a format string like the ones bash(1) uses to format the prompt.
It is intended to be used in combination with the various ReadLine packages.
EXPORT
You can request for arbitrary variables to be exported, they will be tied to the environment variables of the same name.
TIE
When you "tie" a variable you can supply one argument which can either be the name of an environement variable or a SCALAR reference. This
argument defaults to 'PS1'.
METHODS
"sprintf($format)"
Returns the formatted string.
Using this method all the time is a lot less efficient then using the tied variable, because the tied variable caches parts of the
format that remain the same anyway.
FORMAT
The format is copied mostly from bash(1) because that's what it is supposed to be compatible with. We made some private extensions which
obviously are not portable.
Note that this is not the prompt format as specified by the posix specification, that would only know "!" for the history number and "!!"
for a literal "!".
Apart from the escape sequences you can also use environment variables in the format string; use $VAR or "${VAR}".
The following escape sequences are recognized:
a The bell character, identical to "