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
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
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...
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...
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
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.