10 More Discussions You Might Find Interesting
1. AIX
any ideas ??????? (2 Replies)
Discussion started by: livehho
2 Replies
2. AIX
Hi. I just migrated a 5.3 box to 6.1 (standalone, no HMC). This is a System p5 520 Power 5 box
The migration process went smooth but at the end when the server rebooted it never came up. So the bootup process never completes. It gets stuck at the screen with the big AIX logo saying it's loading... (6 Replies)
Discussion started by: livehho
6 Replies
3. HP-UX
Hi gurus,
I was more on the Sun side and now am getting exposure to the HP-UX side of the world. I have to upgrade firmware on BL870c blade.
Can some one point to a url or give procedure to follow as I couldn't find much on the web.
Thanks
Momin (1 Reply)
Discussion started by: momin
1 Replies
4. Solaris
Hi All,
I am planning to do the Solaris level upgrade from "Solaris 10 1/06 s10s_u1wos_19a" to "Solaris 10 10/09 s10s_u8wos_08a" with 7 Non-global zones on it.....
I have done Level upgrade for Solaris 10 boxes without Non-global zones.....
Can any one let me know, whether it is possible... (8 Replies)
Discussion started by: indradev
8 Replies
5. Shell Programming and Scripting
Friends, I am really stuck on this one. In solaris i can get the number of disks using this command -->
pfexec format | egrep -v "Searching|AVAILABLE|Specify|^$|@" | wc -l
But when applying this command inside a solaris zone ,the format command doesnt work. any ideas on how i can go about it (1 Reply)
Discussion started by: achak01
1 Replies
6. 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
7. AIX
When I try to download firmware for pseries (power5 cpu), I found it seems the firmware upgrade code are same for 9117-570 and 9110-510. If they are the same current firmware level and want to upgrade to same firmware.
Am I right?
Because it descript:
This package provides new firmware for... (3 Replies)
Discussion started by: rainbow_bean
3 Replies
8. Solaris
Hi,
I going to upgrade the firmware for sunfire v490 server, current fw level is 4.15.6 and to be upgraded to 4.30.
can anyone share the pre and post firmware upgrade activity procedure and backout plan
Thanks
rjs (2 Replies)
Discussion started by: rajasekg
2 Replies
9. AIX
I need upgrade firmware for the device of p570, when I go to IBM FIX download website, there are a lot of device of p570 listed. How can I know what device I have on my p570? (4 Replies)
Discussion started by: rainbow_bean
4 Replies
10. AIX
Hi Guys,
It's me again with this unending support of AIX43 ML 9.
I finally able to test a migration from SSA to SAN, no problem. One problem, I bought some expansion of DS4300, two arrays. The IBM tech told me that before I can connect to the existing DS4300, I need to upgrade the firmware... (1 Reply)
Discussion started by: itik
1 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)