Home > Error Code > Aix Error Code 613

Aix Error Code 613

Contents

Rebuilding the RAID with fewer disks can be done on some controllers, but you never want to do that on a system in stress anyway. IV58106 Support for future TL/SP IV58111 EEH state machine, TX descriptor fixes and code cleanup IV58465 some adapters : Software Error pop up is coming IV58466 ifconfig enX fails on 1Gports Because that document should be creates by every company on their own I will focus on only creating the so-called golden image… or as you could say… One image to rule Is that like five 2-disk mirrors? have a peek at this web-site

NONE New security APARs Security updates are initially released as interim fixes to expedite availability. If you enjoy reading the LazySystemAdmin blog, please help spread the word by sharing this site with your friends. c44 Initializing install data base with target disk information. Thanks! 0 LVL 46 Overall: Level 46 Server Hardware 28 Linux 10 Unix OS 8 Message Active today Expert Comment by:dlethe2014-07-14 You could do that, but doing so profoundly increases https://www-304.ibm.com/support/docview.wss?uid=isg3T1012561

0552 Aix Error Code

LED 613 – NIM routing This LED indicates your nim routing is setup incorrectly and typically is easy to diagnose. Either way redundancy is fully removed and a rebuild must take place. This may seem like an amateur check to make, however this check is the number one check to make for a reason.

If this was a 3-disk RAID5 and you lost another disk, you still would have data loss. I would suggest to go to diag, find RAID and leave bad disk permanently lit up and try to convince IBM to send tech to do replacement (it may fail) Remember IV51941 Not able to install root part of bos.sysmgt.serv_aid fileset IV51945 SNMPMIBD OCASSIONALY CORE DUMPS ROUGHLY ONCE IN 10 SCANS. You will use your own appropriate hostnames. # host shadoe # host shadoe.austin.ibm.com # host 9.3.58.215 Your output should read similar to the following for all 3 commands.

We do nightly full backups to tape. Aix Error Codes List To do so, create the file /etc/tftpaccess.ctl and define the correct directories: bash-3.2# vi /etc/tftpaccess.ctl bash-3.2# cat /etc/tftpaccess.ctl # NIM access for network boot allow:/tftpboot allow:/nim/tftpboot Test TFTP bash-3.2# cat /tftpboot/test That way, I'll always keep one filesystem and volumegroup for booting, and one of each for the NIM data. You will use your own appropriate hostnames. # host shadoe # host shadoe.austin.ibm.com # host 9.3.58.215 Your output should read similar to the following for all 3 commands.

IV55189 system crashes while freeing sctp association twice IV55191 SMIT CHTZ_USER MAY FAIL TO PRE-LOAD FROM THE TZ VARIABLE IV55197 Page Fault regenerates many times IV55204 IN WPAR: SYSTEM CRASH IN Heck, you might already have unrecoverable write errors on other disks. Make sure all 3 commands output the exact same output (verbatim) : shadoe is 9.3.58.215, Aliases: shadoe.austin.ibm.com # host kintaro # host kintaro.austin.ibm.com # host 192.168.50.25 kintaro is 192.168.50.25, Aliases: kintaro.austin.ibm.com This is one of the most common errors that are made with bootp/tftp requests.

Aix Error Codes List

Next you'll check your client. # lsnim -l client_name kintaro : class = machines type = standalone connect = shell platform = chrp netboot_kernel = mp if1 = master_net kintaro 0 http://docs.gz.ro/nim-crash-0613.html Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! 0552 Aix Error Code When you initate the bootp request you normally see a “Sent” and “Received” indicator that may look like this : S=1 R=0 S=2 R=0 S=3 R=0 ....etc This at least indicates 0554 Error Code In Aix You will actually use the word 'master' in this case – not the hostname of the NIM master. # lsnim -l master |grep if1 if1 = master_net shadoebso.austin.ibm.com 00145EB7F3F5 The master's

You also will want to verify the master's hostname is correct in the output of that command as well. http://lanprolab.net/error-code/and-error-code-0x5.php Next you'll check your client. # lsnim -l client_name kintaro : class = machines type = standalone connect = shell platform = chrp netboot_kernel = mp if1 = 192.168_network kintaro 0 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. . . . . . << End of copyright notice for bos.adt Home | Invite Peers | More UNIX Groups Your account is ready. 0518 Error Code Aix

Lose a pair and you are screwed. IV58494 FILEMON COLLATED REPORTS WRONG BCOUNT VALUES. Your NIM routing entry represents the gateway system connecting your master and client. Source I'm Experienced in Linux/Unix System Administration and Scripting.

Use it. Before running any check it is always good to run a reset/deallocate operation so we know that we're starting fresh. # nim -Fo reset client_name # nim -o deallocate -a subclass=all Many times you will have to use your NIM client names in these commands, so I've placed that indication in italics.

This indicates : o The device driver level installed into the SPOT is too low o The target adapter is not supported o The target adapter is bad Often times there

You will actually use the word 'master' in this case – not the hostname of the NIM master. # lsnim -l master |grep if1 if1 = master_net shadoebso.austin.ibm.com 00145EB7F3F5 The master's You can monitor the installation through the console and through the nim commandline: bash-3.2# lsnim -l ms-lpar01 ms-lpar01: class = machines type = standalone connect = nimsh platform = chrp netboot_kernel This incorrect NIM network definition will cause an LED 608 hang. You can probably run a manual parity (or sometimes called data consistency check).

Already a member? IV54986 topas -P -U not working for non-root user IV54987 Possible System Hang when Global Profiling tools are used IV54988 topasrec -L shows NaNQ values for cpu metrics when smt In the first case I would think if another disk fails I have a 1 in 9 chance of it being the wrong disk. http://lanprolab.net/error-code/and-the-error-code-was-8.php IV56457 aixpert undo fails to restore suid bits IV56458 Additional improvements to compression accelerator system calls IV56459 SCB_SYSBR SERIALIZATION ISSUE IN VM_MAKEADSP64 IV56460 possible crash in getutinfo IV56461 SMIT HELP SCREEN

and if so how can I check which kind of RAID it is? The NIM master's network information may be wrong also, so make sure you check both machine definitions and both NIM network definitions for errors. You can use the NIM "showlog" operation to view the installation log file for the SPOT. +-----------------------------------------------------------------------------+ Pre-installation Verification... +-----------------------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results...