Search results for query: *

I've resolved the issue by updating the APPLHEAPSZ (doubling from 256 to 512) and then re-running the upgrade database command

I've installed DB2 v10.1 on our AIX server in parallel to our current v9.5 install. After upgrading the DAS from v9.5 to v10.1 and the tools db to v10.1, when I attempted the db2 upgrade database on our large WAREHOUS database, the process coredumps and db2 stops. the db2diag.log reports "Out of...

has anyone upgraded to networker 7.6.3 and encountered times being off through the GUI as well as mminfo ? In terms of using time to have networker kick off a backup, it seems fine. But the monitoring tab would show that a group started an hour after the actual time it started. Also, when you...

thanks Blueslave that's what I figured. I didn't want to have to ask our network guys to disable LCAP on one of the ports and then later re-enable, when I had the option of just reimaging from a mksysb dvd

yes, everything I was setup. I gave up and created a mksysb dvd from a previous image to reimage the vio server thanks

yes I did

the vio lpar boots up just fine, but I need to re-image it from a mksysb because something got screwed up in the vio configuration. that's why I'd like to boot up to a nim server to reimage it with the last mksysb I made of the vio server

still no good

I've disconnected 2x of the 3x cables just now. within sms->remote ipl->adapter configuration I set it use 802.3, do I set spanning tree to yes or no ? it still fails on the ping

on our p7, our vio servers have 3x ethernet ports configured w/ etherchannel. I have fsck errors on one of the vio servers, so I'd like to boot up off a nim server to run maintenance, but when I go into the SMS menu of the lpar and setup remote ipl, the ping fails using one of the 3x adapters...

We are running networker v7.6.1. Using versions 7.6.0 and lower, our Windows Sys Admins were able to access the Software Distribution Wizard in Networker to push out client updates to Windows hosts. About 3 months ago, we changed NMC to use Windows Active Directory for login to NMC/Networker...

thanks guys

We have our nim server on a P5 server, running aix 6.1 tl3. I have NIM setup to host mksysb images of hosts running different oslevels - 5.3tl5, 5.3tl7, 5.3 tl12, 6.1 tl3 When I set nim to host out a mksysb image using any one of these mksysb images to a new lpar on our P5, the lpar boots up...

thanks again!

first, apply the TL04 to the NIM master (NIM master always needs to be a same or higher level as clients) next, create the LPP package in nim for TL04 then this should work on the client (TARGET=client): nim -o cust -a lpp_source=LPP -a accept_licenses=yes \ -a fixes=update_all TARGET

my stupid question: do you have the openssh packages installed on the aix 4.3.3 server? if so, is the sshd daemon running ? do you have port 22 blocked at/before the host ?

it did turn out to be a permissions issue, on the .ssh folder. When I changed it to 755 and verified authorized_keys was 600 then ssh went through w/o the password thanks for the info on debugging!

I see this in debug mode when trying that: debug1: userauth-request for user srvcusr1 service ssh-connection method none debug1: attempt 0 failures 0 debug3: mm_getpwnamallow entering debug3: mm_request_send entering: type 6 debug3: mm_getpwnamallow: waiting for MONITOR_ANS_PWNAM debug3...

I'm trying to setup ssh into a user account (not padmin) on 2x of our VIO servers running ioslevel 2.1 which is also aix 6.1 tl2. After switching to root from padmin, for the user I want to ssh to, I've setup the .ssh directory in the user's home folder, and within the folder created the file...

We are working with EMC on upgrading from DMX 3000's in each of our data centers to VMAX. We are receiving conflicting information from EMC on how to setup the dual pathing for hosts on the VMAX. Some EMC people say to continue to use rule of 17 for dual pathed hosts, but other EMC people are...