12-01-2011
10 More Discussions You Might Find Interesting
1. AIX
I am trying to run the lscod command against an HMC that has managed system names with spaces.
Tried enclosing the managed system names in quotes; single and double.
How do I get the command to run?
ssh hmcname lscod -m 'managed system 1' -t cap -r proc -c cuod
Thanks,
~Donavon (0 Replies)
Discussion started by: djlerman
0 Replies
2. AIX
Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS )
This article or post covers upgrades for
- Hardware Management Console ( HMC )
- Firmware ( also known as microcode )
- VIO ( Virtual I/O Server = PowerVM )
- AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies
3. AIX
I started the AIX install with a fiber channel disk, and let it run:
restricted by GSA ADP Schedule Contract with IBM Corp.
. . . . . << End of copyright notice for perfagent.tools >>. . . .
... (2 Replies)
Discussion started by: Gideon1a
2 Replies
4. AIX
I have an HMC that I'm looking to upgrade from V7.3.4.0 SP2 to the latest version V7.7.6.0. I'm looking at the firmware levels of the systems attached to this HMC, and all of the systems have compatible firmware revisions but there are two that have been update recently and the platform IPL level... (10 Replies)
Discussion started by: acascianelli
10 Replies
5. AIX
Hi ,
I would like to access the cd drive of , i have power series server , and have lpars .
I try to install AIX in an lpar via HMC, but it can't access the cd drive.
how i can make installtion or make the the cd drive accessible in hmc or in power series server?
Thanks in advance (2 Replies)
Discussion started by: prpkrk
2 Replies
6. AIX
Hi,
For installing aix on power series , do i need to install hmc first?
or i can connect hmc after?
Rgs, (7 Replies)
Discussion started by: prpkrk
7 Replies
7. AIX
Trying to get the IP address of the HMC connected to some servers running AIX 6 and 7. I thought this would be as easy as running 'lsrsrc IBM.MCP IPAddresses', but when I run that command, the resource is empty. Is there some where else I should be looking, or is there a reason why this resource... (5 Replies)
Discussion started by: acascianelli
5 Replies
8. AIX
Hi Experts
So we have two data center .I upgraded the HMC in one datacenter, very easy no problem, but in the second datacenter we have dual HMC connection. I am looking at the document from the ibm documentation. I found something that I am not comfortable following. which is this : Physically... (2 Replies)
Discussion started by: JME2015
2 Replies
9. AIX
Hey All,
I have running dual VIOS on a P9 systems, and just created a new LPAR profile. My objective is to create LPAR Client VFC adapters, and then DLPAR VFC Server adapters on the VIOS.
In the HMC v9 Enhanced GUI, I have DLPAR a VFC adapter to both VIOS, however, you can't specify the... (1 Reply)
Discussion started by: aixkidbee
1 Replies
10. AIX
hello
P6 was managed by HMC, tried to install on it VIOS 2.2.6
and got this error message
Hosting requires a hosting partition -- boot not permitted
vios-4 - imgbb.com
then after creating an lpar in HMC got this message
B2001230
vios-3 - imgbb.com
anyone know how to solve this... (3 Replies)
Discussion started by: filosophizer
3 Replies
LEARN ABOUT SUSE
innupgrade
INNUPGRADE(8) InterNetNews Documentation INNUPGRADE(8)
NAME
innupgrade - Upgrade INN configuration files
SYNOPSIS
innupgrade directory
innupgrade [-t type] -f file
DESCRIPTION
innupgrade is intended to be run during a major upgrade of INN to fix the configuration files with any required changes. If given a
directory, it will scan that directory for any files that it has updates defined for, try to perform those updates, and replace the files
with updated versions if applying the updates resulted in any changes. The old versions of the files will be saved with a ".OLD"
extension.
If the -f flag is used, only that file will be updated. If the file name doesn't match the standard file name of an INN configuration
file, the optional -t flag may be given to specify the type. See "EXAMPLES" for an example of this.
Currently, innupgrade knows how to apply the following updates:
inn.conf
o Quote values with whitespace and comment out keys with no values, required for the change in configuration parsers introduced in
INN 2.4. The new format is not backward compatible with the previous parser, since the previous parser will include the double-quotes
in the value of the parameter.
o Add the hismethod parameter if not found (introduced in INN 2.4, with the default value "hisv6") and rename nntpactsync to
incominglogfrequency (since INN 2.5).
o If the overview.fmt file exists, its content is merged in the extraoverviewadvertised and extraoverviewhidden parameters introduced in
INN 2.5. The file is then renamed to overview.fmt.OLD.
o If the sasl.conf file exists, its content is merged in the tlscapath, tlscafile, tlscertfile and tlskeyfile parameters introduced in
INN 2.5. The file is then renamed to sasl.conf.OLD.
newsfeeds
o Replace the use of startinnfeed with the appropriate direct invocation of innfeed or imapfeed.
A few obsolete programs or configuration files are renamed with a ".OLD" extension by innupgrade. Obsolete man pages are directly removed.
Normally, innupgrade should be run at least on the pathetc directory after any upgrade of INN other than a patch release (any upgrade that
changes the first or second version numbers). This may occur automatically during the upgrade process.
OPTIONS
-f file
Only act on file rather than working on an entire directory.
-t type
For a file specified with -f, parse it and upgrade it as if it were named type. Used for upgrading files with the same syntax as
normal INN configuration files but with different names. Only makes sense in combination with -f.
EXAMPLES
Upgrade any configuration files found in pathetc and append a ".OLD" extension to obsolete files in pathetc:
innupgrade <pathetc in inn.conf>
Upgrade only /news/etc/inn.conf:
innupgrade -f /news/etc/inn.conf
Upgrade a file named inn-special.conf that should have the same syntax as inn.conf:
innupgrade -t inn.conf -f inn-special.conf
Any upgrade rules that apply to inn.conf will be applied to the alternate file.
HISTORY
Written by Russ Allbery <rra@stanford.edu> for InterNetNews.
$Id: innupgrade.pod 8415 2009-04-12 20:19:35Z iulius $
INN 2.5.2 2009-05-21 INNUPGRADE(8)