I am doing this through the hmc console so unless I can post pictures here and I'm not sure how if I can then I'm out of luck on the screen shots as I am not versed in the hmc command line enough to perform the steps there. If one of you know the cmd line well maybe you get close on a cmd I could try.
I also monitored the cimserver.log file while trying to peform the DLPAR function and there are lots of data being written to that log file. Even though the date cmd returns the correct date the time being logged in the cimserver.log file is way off so I am unable to look based upon time.
So I think I found how to upload pictures. I ended up just uploading a word doc with the screen shots in there.
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)
Hi
My vio client is getting its virtual Ethernet services from dual vio servers. What command if I execute on the vio
client will get me the names of the vio servers ? (2 Replies)
trying to put VIO server software into this p520, firmware upgraded to the latest and greatest..SF240_415_318 , I think
a few questions, on this practice AIX machine on AIX 7.1
VIO can only be installed if ASMI or HMC is running ???
if so, perhaps ASMI is much simpler, since I will need to... (2 Replies)
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 would like to know installing vio server on local disk and mirroring rootvg,
if I am creating AIX VIO CLIENT(lpar),
and any of single local hard disk failuare.
will it affect lpars? will lpars able to boot.
what needs to be done? (1 Reply)
Hi
One of our server is showing the uptime 0hr 5mints
there is no log in /var/log/messages
there is no log in command "last"
kernel version is 2.4.9 (RH2.1 AS)
What could be the reason for this. is this issue is related to uptime counter reached max
how to verify this.
Best Regards
KVK (4 Replies)
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 want to grab all the luns in vscsi disks from vio that are assigned to client lpars. They are not powerpath disks. Now when I do lspv as root in vio server I see 956 disks..the problem right now is that each disks lun are in hex so when I do lscfg vpl from vio..the FRU number is on hex.
Can... (3 Replies)
Hi Experts, Kind of embarrassed to ask this , it's been a while I've done this . Can anyone verify below procedure to replace HBA in the VIO server. Many client LPARs are using this HBA for NPIV . Please correct me if I am wrong . Thanks in Advanced
Identify the HBA (did that)
Unconfigure the... (2 Replies)
Discussion started by: JME2015
2 Replies
LEARN ABOUT CENTOS
backup_listdumps
BACKUP_LISTDUMPS(8) AFS Command Reference BACKUP_LISTDUMPS(8)NAME
backup_listdumps - Displays the dump hierarchy from the Backup Database
SYNOPSIS
backup listdumps [-localauth] [-cell <cell name>] [-help]
backup listd [-l] [-c <cell name>] [-h]
DESCRIPTION
The backup listdumps command displays the dump hierarchy from the Backup Database.
OPTIONS -localauth
Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to
the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more
details, see backup(8).
-cell <cell name>
Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8).
-help
Prints the online help for this command. All other valid options are ignored.
OUTPUT
The output displays the complete dump hierarchy and indicates the relationship between full and incremental dump levels. Full dump levels
appear at the left margin. The hierarchy can include more than one full dump level; each one defines a subhierarchy of dump levels that can
be used for dumping different volume sets.
Incremental dump levels appear below and indented to the right of their parent dump levels, which can be either full or incremental. Since
multiple incremental dump levels can share the same parent, an incremental dump level is not always directly below its parent; the amount
of indentation indicates the parent/child relationship.
If a dump level has an associated expiration date, it appears along with the level name. Absolute expiration dates appear in the format
<dump_level> expires at <day month date time year>
and relative expiration dates in the format
<dump_level> expires in {<years>y | <months>m | <days>d}
to indicate the number of years, months, days, or combination of the three after creation a dump expires when created at this level.
EXAMPLES
The following example depicts six dump hierarchies. The expiration date for all incremental dump levels is 13 days so that the
corresponding tapes can be recycled two weeks after their creation. The expiration dates for all full dump levels is 27 days so that the
corresponding tapes can be recycled four weeks after their creation.
% backup listdumps
/week1 expires in 27d
/tuesday expires in 13d
/thursday expires in 13d
/sunday expires in 13d
/tuesday expires in 13d
/thursday expires in 13d
/week3 expires in 27d
/tuesday expires in 13d
/thursday expires in 13d
/sunday expires in 13d
/tuesday expires in 13d
/thursday expires in 13d
/sunday1 expires in 27d
/monday1 expires in 13d
/tuesday1 expires in 13d
/wednesday1 expires in 13d
/thursday1 expires in 13d
/friday1 expires in 13d
/sunday2 expires in 27d
/monday2 expires in 13d
/tuesday2 expires in 13d
/wednesday2 expires in 13d
/thursday2 expires in 13d
/friday2 expires in 13d
/sunday3 expires in 27d
/monday1 expires in 13d
/tuesday1 expires in 13d
/wednesday1 expires in 13d
/thursday1 expires in 13d
/friday1 expires in 13d
/sunday4 expires in 27d
/monday2 expires in 13d
/tuesday2 expires in 13d
/wednesday2 expires in 13d
/thursday2 expires in 13d
/friday2 expires in 13d
PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged
onto a server machine as the local superuser "root" if the -localauth flag is included.
SEE ALSO backup(8), backup_adddump(8), backup_deldump(8)COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas
Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
OpenAFS 2012-03-26 BACKUP_LISTDUMPS(8)