Sponsored Content
Full Discussion: p520 -- amber light
Operating Systems AIX p520 -- amber light Post 302580244 by zaxxon on Thursday 8th of December 2011 02:39:06 AM
Old 12-08-2011
For your code B159A070 Google shows:
IBM InfoCenter

Google also shows:
IBM InfoCenter
which points to:
Quote:
B159A070 Indicates that the Panel is being deactivated
and this leads to a check if a service action is needed:
IBM InfoCenter
 

10 More Discussions You Might Find Interesting

1. AIX

installing aix 5.2 on p520

hello everybody. Has anyone tried to install aix 5.2 on p520 machines. I've been trying but in the installation menu it says, "no disk found". I've used the same CD on a different 520 server and its working fine on it. Can anyone help, please? (5 Replies)
Discussion started by: soahel
5 Replies

2. SuSE

Amber Lights + Remote Servers

Ok, so we get reports from operations after they do walk throughs about servers with amber or red lights showing. They want us to resolve the issues. On Solaris I can run prtdiag to identify the amber lights and clear them (replace hardware or "reboot" the daemon). How do I remotely figure out... (1 Reply)
Discussion started by: BOFH
1 Replies

3. AIX

P520 AIX com port (tty0) settings

I have software running under AIX 5.3 that should communicate with a special device using standard communication protocol (Modbus) using serial RS-232 line The settings are correct in both sides, But I can't establish a connection. I suspect that there's something that I should do regarding the... (3 Replies)
Discussion started by: ayman metwally
3 Replies

4. Red Hat

AMBER md/g95/gfortran issue

Hi, i am trying to install AMBER10 which is a molecular dynamcis package onto two linux red hat pcs. I can successfully install the tools that comes with which uses gcc to compile, however AMBER10 requires either g95 or gfortran to compile. This is where the issue lies, i have installed both... (0 Replies)
Discussion started by: olifu02
0 Replies

5. Solaris

troubleshooting cause of amber light

hi all, we've got an amber maintenance light on the front of our Netra-t4. I can't find out what's causing this issue. I've logged into the lom, and found the following. There's nothing in messages or prtdiag. Disks appear to be ok. Are there any other lom commands that can help? ... (6 Replies)
Discussion started by: badoshi
6 Replies

6. AIX

VIO server on p520

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)
Discussion started by: ppchu99
2 Replies

7. AIX

p520 Service Processor's IP

picked up this old p520 , try many ways to connect to the SP.. a) null modem using a PC connecting to the lower S1 ...but see a bunch of garbages across the screen once the main machine is off b) try guessing the default IPs 192.168.3.147 and 192.168.2.147, for ports HMC1 and HMC2 no... (7 Replies)
Discussion started by: ppchu99
7 Replies

8. AIX

running LPAR on power5 p520 hardware

picked up an old p520..and also spend sometimes to manage software: a) AIX 7.1 b) VIOS Server 2.2 attempting to run a few LPARs without much more $$$$, as this is a home-made projects.. machine hdisk0, pre-installed with AIX 7.1 a few questions: a) In order to run LPARs, I will... (7 Replies)
Discussion started by: ppchu99
7 Replies

9. UNIX Benchmarks

power 5 p520 2-dual core CPU and 8 Gig

p520's prtconf ..two internal drives 10K RPMs 140G, 2 dual core 1.5 GHz processors, 8 Gig of RAM, running AIX 7.1, with the newest gcc compiler The numbers don't make sense, Can someone comment ?? BYTE UNIX Benchmarks (Version 3.11) System -- AIX p520 1 7 00CD5D0C4C00 Start... (2 Replies)
Discussion started by: ppchu99
2 Replies

10. AIX

Hard drive compatibility for POWER6 p520

Hi, I have recently inherited an old p520 from work running AIX 6.1, based on the POWER6 CPU. I'm planning to play around with it and use it to learn the system, so this is a purely personal project. The machine is not under a support contract any more. I am looking to replace one of the disks... (11 Replies)
Discussion started by: topcat
11 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:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy