Sponsored Content
Full Discussion: AIX 7.1 Upgrade problem
Operating Systems AIX AIX 7.1 Upgrade problem Post 302882087 by h@foorsa.biz on Saturday 4th of January 2014 07:53:28 AM
Old 01-04-2014
Quote:
Originally Posted by rbatte1
If your server was pre-installed, then I would revert to the mksysb that you took in advance of the upgrade. This will preserve volume groups you have made/used if you overwrite the original boot disk.

Discuss the issue with the supplier and/or IBM if you still are under warranty.

It is possible that there is a firmware requirement for the upgrade, although I think that unlikely. Normally IBM are good with upgrades.




Robin
Alas no mksysb were taken prior to the upgrade.
I'm no longer under the support/warranty umbrella.
I have done firmware upgrades prior to the upgrade, I don't think the issue lies with firmware.
 

10 More Discussions You Might Find Interesting

1. AIX

HELP for AIX 4.3 upgrade to 5.3

Hi guys I have joined a new department and one of my tasks is to investigate the feasibility of upgrading our current AIX v 4.3 to V5.3. I do not know anything about AIX and any actual work will be done by an outside consultant until such time as I have built up my own knowledge. The system we... (3 Replies)
Discussion started by: JDM
3 Replies

2. UNIX for Dummies Questions & Answers

AIX ML upgrade

Hello everyone, I have to do a ML upgrade on AIX 5.2 from 01 to 09 this is the first time iam going to do it. are there any command i have to keep in mind?? thanks! (1 Reply)
Discussion started by: karthikosu
1 Replies

3. UNIX for Dummies Questions & Answers

AIX Upgrade

Does anyone know any gotcha's on upgrading AIX from 5.1 to 5.3? Any interim steps on needs to do or ??? (3 Replies)
Discussion started by: capeme
3 Replies

4. AIX

AIX Upgrade 5.2 to 5.3

I have an IBM P520 that I need to upgrade from 5.2 to 5.3. My background in Unix is from 15 years ago so I don't remember much. IBM documentation is hard to find. Any help would be appreciated. (1 Reply)
Discussion started by: bashtonmcse
1 Replies

5. AIX

AIX OS upgrade gone wrong

I have an AIX LPAR that is one half of a Oracle RAC cluster running over a GPFS filesystem. The OS version in the LPAR was 5300-05-01 I ran an upgrade to 5300-07-05 (Apply only, Commit=NO and preserve old files). The preview passed with no failures detected. The actual upgrade failed... (5 Replies)
Discussion started by: morgan_g
5 Replies

6. AIX

Upgrade from AIX 5.3 to 6.1

Hello Folks, i am facing some weired issues. case is like this :- initially i was on AIX 5.3 i have installed filesets related to my application and those were in APPLY state.(COMMIT is set as NO) Then i have taken lslpp -l| grep -i <apps name> in that i confirmed whether the filesets are... (1 Reply)
Discussion started by: harsh_mulay
1 Replies

7. AIX

How to upgrade AIX Firmware & TL Maintenance Level in 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

8. AIX

AIX upgrade

i upgrade aix ml 5.3.2.1 to 5.3.2.2 but when running commnd #oslevel -r shows out put, again 5.3.2.1-- where should i chek??? 2-can any one tell me when mknfs command run which files get updated?? (2 Replies)
Discussion started by: nayyer
2 Replies

9. AIX

Upgrade AIX without HMC

Hi all, i would like to know if it's possible upgrade AIX 5.3 to 6.1 on a LPAR without use the HMC. so i would like to know if i must use the console to do it or i can do all from the up&running system on LPAR. Thanks in advance. Mario (4 Replies)
Discussion started by: Zio Bill
4 Replies

10. AIX

Upgrade AIX 5.3 to AIX6.1

Dear Guys .. I'm going to Upgrade one of the servers AIX 6.1 I want to stop rootvg mirror to save the mirror then upgrade to AIX 6.1 this is to help me in rollback if something goes wrong but .. can anyone help me how to make sure that system is relay mirrored and how to know that second... (10 Replies)
Discussion started by: top.level
10 Replies
UPSLUG2(8)						      System Manager's Manual							UPSLUG2(8)

NAME
upslug2 - utility to upgrade the firmware of a NSLU2 via the network SYNOPSIS
upslug2 [options] DESCRIPTION
upslug2 is a command line program intended to allow the upgrade the firmware of a Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) to new or different versions. When a NSLU2 in the local network is put in upgrade mode, upslug2 can connect to it and upload a new firmware. upslug2 will accept a full firmware image but it can also upgrade the flash from individual files holding the kernel, ramdisk and root filesystem. upslug2 provides status information during the upgrade process and verifies the written image after the upgrade. OPTIONS
-C, --Complete-reprogram Reprogram the complete flash, including the RedBoot boot loader and the SysConf partition holding configuration information. Using this option may result in the NSLU2 becoming permanently unusable! By default, upslug2 will not touch these two partitions since this allows flashing a new firmware if an uploaded firmware does not work. This is not possible if RedBoot itself is damaged. Use with caution. -d, --device The network device on the host machine connected to the network on which the NSLU2 is located. (Default: eth0). -e, --endian The endianness of the files to be uploaded. upslug2 will usually detected the endianness automatically but this option can be used to force byte swapping to occur. This option accepts three values, separated by comma: endianness of kernel, data and RedBoot FIS directory. Valid values are l (little endian), p (pdp endian) and b (big endian). (Default: ,b,b) -f, --from The MAC address of the host system. -h, --help Show summary of options. -i, --image The complete flash image to use. -j, --rootfs A root filesystem, usually of type jffs. -k, --kernel A compressed kernel zImage image. -n, --no-reboot Do not reboot after upgrade -p, --payload FIS directory payload. There are about 140 Kb in the last block (between the FIS dir and the trailer at the end) which can be used for data. -r, --ramdisk A compressed ramdisk image. -R, --ram-payload A ram paylod (replaced ramdisk). (FIXME: if it replaced the ramdisk, why cannot you just use the -r option? What's the difference) -t, --target The MAC address of the NSLU2 to upgrade. Without this option, upslug2 will only perform an upgrade if there is just one NSLU2 in upgrade mode. -U, --no-verify Do not verify the image, only upgrade. -v, --verify Do not write to flash, only verify the image. Options to specify firmware information The following options should be used when individual kernel, ramdisk and root filesystem files are specified rather than a complete firmware image. -E, --extra-version Extra version information, a 2 byte value. (Default: 0x90f7) -F, --firmware-version The firmware version, a 2 byte value. (Default: 0x2329) -P, --product-id The product ID, a 2 byte value. (Default: 1) -T, --protocol-id The protocol ID, a 2 byte value. (Default: 0) USING UPSLUG2 In order to use upslug2 the NSLU2 which is to be upgraded has to be put in upgrade mode: 1. Disconnect any disks and/or devices from the USB ports. 2. Power off the NSLU2 3. Press and hold the reset button (accessible through the small hole on the back just above the power input). 4. Press and release the power button to power on the NSLU2. 5. Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset but- ton. 6. The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in upgrade mode. If you decide not to flash the image the NSLU2 can be rebooted by disconnecting the power. If the ready/status LED does not turn green after step four it will remain red for several seconds then flash amber. This happens if you do not release the reset button in time - pull the power, reconnect it and repeat from the second step. Once the NSLU2 is in upgrade mode it will remain in this state until either the power is connected or a new image has been flashed. If the flash fails the NSLU2 will (eventually) return to upgrade mode EXAMPLES
The most common use of upslug2 is the following: upslug2 --image NSLU2_V23R63.bin This specifies a complete firmware image which will be written to flash. Alternatively, kernel, ramdisk and root filesystem can be specified individually: upslug2 -k nslu2-zImage -r ramdisk -j root.jffs In this case, the options -E, -F, -P and -T should typically be specified as well. By default, upslug2 will search for the NSLU2 on the network on your eth0 network interface. If the network is on a different interface, you can easily specify it: upslug2 -d eth1 --image NSLU2_V23R63.bin If there are potentially more than one NSLU2 in your network which may be in upgrade mode, you can specify its MAC address: upslug2 -t 00:11:85:12:34:56 --image NSLU2_V23R63.bin SEE ALSO
slugimage(1) AUTHOR
John Bowler <jbowler@acm.org> January 2006 UPSLUG2(8)
All times are GMT -4. The time now is 09:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy