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 SUNOS
asupgrade
asupgrade(1m) Application Server Utility asupgrade(1m)NAME
asupgrade - migrates the configuration of a previously installed Sun Java System Application Server
SYNOPSIS
asupgrade [-c | --console] [-V--version] [-h | --help]-s | -source applicationserver7.x_installation -t--target application-
server8.x_installation [-d | --domain domain_name -n | --nsspwdfile NSS_password_filepath -j | --jkspwdfile JKS_password_filepath -p |
--capwdfile CA_password_filepath]
Use the asupgrade utility to migrate the server configration and its persisted state, J2EE services, and deployed J2EE applications. The
configuration of an installed Sun Java System Application Server 7 is migrated to the Sun Java System Application Server 8 Application
Server installation. If the domain contains information about a deployed application and the installed application components do not agree
with the configuration information, the configuration is migrated as is without any attempt to reconfigure the incorrect configurations.
asupgrade migrates the configuration and deployed applications of a previous version of the Application Server; however, the runtime bina-
ries of the server are not updated. Database migrations or conversions are beyond the scope of the asupgrade command.
Only those instances that do not use the Sun Java System Web Server specific features will be upgraded seamlessly. Configration files
related to HTTP path, CGI bin, SHTML, and NSAPI plugins will not be upgraded.
The upgrade process can also be initiated automatically at installation time using the Upgrade checkbox in the Application Server install-
er. After completion of the upgrade, use the Application Server 7 Uninstaller to remove the previous version of the Application Server.
Application archives (.ear) and component archives (.jar, .war, .rar) that are deployed in the Application Server 7 environment do not
require any modification to run on Application Server 8. However applications and components deployed in the source server are repackaged
into new J2EE archives in the target server's autodeploy directory and are deployed upon server startup. Applications that do not deploy
successfully, must use Migrationtool (asmigrate) on the application and then manually redeploy the application.
You must specify the source and target directories for the upgrade. If the upgrade includes certificates, you must also provide the pass-
words for the source PKCS12 file and the target JKS keyfile for each domain that contains certificates to be migrated. Since Application
Server 7 uses a different certificate store format (NSS) than Application Server 8 (JSSE), the migration keys and certificates are con-
verted to the new format. Upon successful upgrade, an upgrate report is generated listing successfully migrated items along with a list of
the items that could not be migrated.
OPTIONS -c --console launches the upgrade command line utility.
-V--version displays the version of the UpgradeTool.
-h--help displays the arguments for launching the UpgradeTool.
-s--source identifies the installation directory for Sun Java System Application Server 7.
-t--target identifies the installation directory for Sun Java System Application Server 8.
-d--domain identifies the destination domain name for the migrated certificates.
-n--nsspwdfile identifies the path to the NSS password file.
-j--jkspwdfile identifies the path to the JKS password file.
-p--capwdfile identifies the path to the CA certificate password file.
EXAMPLES
Example 1: Using asupgrade
example% upgrade -s /home/sunas7 -t /home/sunas8
SEE ALSO asmigrate(1M)Sun Java System Application Server March 2004 asupgrade(1m)