Ibm Error Code 0581
(FAQ) Question Understanding LED 581 in AIX Version 4.x and 5.x Answer This document describes what happens during the time that LED 581 is shown during boot up and what may cause an indefinite hang on LED 581. This document applies to AIX Versions 4 and 5. What happens during LED 581 Problem determination for LED 581 hang What happens during LED 581 LED 581 is shown during the time that the Configuration Manager (/usr/sbin/cfgmgr -s) configures TCP/IP and runs /etc/rc.net to do specific adapter/interface/host name configuration. Much of what happens during this time depends on factors such as access to a DNS, network traffic, valid network addresses, network access, network hardware/microcode, and the number and type of adapter/interfaces being configured. TCP/IP, over some interfaces (token-ring, for example), will wait for replies. If there are no replies, it will eventually timeout on the attempt and mark the interface as down. Nevertheless, this will take some time, possibly between three to ten minutes, or may hang indefinitely. Problem determination for LED 581 hang Most of the time LED 581 is caused by the DNS client not being able to resolve loopback correctly. This is often caused by a misconfigured or unreachable DNS server. This can be easily solved by resolving loopback locally using the /etc/netsvc.conf file, which dictates the order of name resolution. In maintenance mode, enter the following: mv /etc/netsvc.conf /etc/netsvc.conf.saveme NOTE: This file might not exist. Enter: cat /etc/hosts Search for the loopback line and make sure its correct, it should look like the following: 127.0.0.1 loopback localhost Using your favorite editor, create a new file as follows: /etc/netsvc.conf Add the following according to your AIX level and save the file. At AIX level 4.2.1 and below add: hosts=local,bind At AIX level 4.3.x and above add: hosts=local,bind4 Enter: mv /etc/resolv.conf /etc/resolv.conf.saveme NOTE: This file should exist only if you are using DNS for name resolution. Enter the following: mv /etc/rc.net /etc/rc.net.saveme touch /etc/rc.net chmod 755 /etc/rc.net Using your favorite editor, edit the following file: /etc/inittab Comment out the following 3 lines in /etc/inittab: rctcpip:2:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons rcnfs:2:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons dt:2:wait:/etc/rc.dt Also comment out all other lines which depend on TCP/IP being started. NOTE: Commenting out in /etc/inittab is done with a colon (:) in front of
& MappingSocial Networking & CommunicationUtilitiesWeb BrowsersComputer & HardwareGadgetsGaming & LeisureSmartphonesMobile AppsWindows Mobile (Pocket PC / PPC)Networking IBM Server Stops or Hangs with 0581 on LCD Display Home»Computer & Hardware»IBM Server Stops or Hangs with 0581 on LCD Display IBM Server Stops or Hangs with 0581 on LCD Display When a IBM server, such as pSeries, RS/6000 and etc, boots up, the server may stops, or appears hanging for quite a while, with the LED on LCD panel on the server displaying 0581 panel code.
0581 is shown during the time that the Configuration Manager (/usr/sbin/cfgmgr -s) configures TCP/IP and runs /etc/rc.net to do specific adapter/interface/host name configuration. Much of what happens during this time depends on factors such as access to a DNS, network http://www-01.ibm.com/support/docview.wss?uid=isg3T1000207 traffic, valid network addresses, network access, network hardware/microcode, and the number and type of adapter/interfaces being configured. TCP/IP, over some interfaces (token-ring, for example), will wait for replies. If there are no replies, it will eventually timeout on the attempt and mark the interface as down. Nevertheless, this will take some time, possibly between three to ten minutes, or may hang indefinitely. Most usually, 0581 indicates that the machine https://techjourney.net/ibm-server-stops-or-hangs-with-0581-on-lcd-display/ has a problem contacting the DNS name server or contacted a misconfigured DNS server. If the server can eventually get past the stage of 0581 and boot up, try setting NSORDER to NSORDER=local,bind in /etc/rc.net and /etc/rc.tcpip. And set also hosts=local,bind in /etc/netsvr.conf. This setting instructs the server to try to resolve loopback or domain name locally first. Beside, check and ensure your server's hostname is configured properly in /etc/hosts, which it must contains the following line or something similar: 127.0.0.1 loopback localhost The loopback line in /etc/hosts ensures that loopback can be resolved properly by the server. Beside, rename /etc/resolv.conf or delete nameserver entry in the configuration file to stop using DNS server for name resolution. If your server machine hangs indefinitely at panel code 0581, try to boot up the server in maintenance mode and configure the TCP/IP settings properly. The server may also have a faulty network card. To check the status of network card, run "errpt -a | more", or run diag as root. You May Also Interested In: Installing and Configuring DHCP Server (DHCPd) on FreeBSDApache Status (whm-server-status) in cPanel WebHost Manager…Request URL /server-status or 404 Page Not Found Apache…cPanel WHM Failed to Receive Status Information From Apache… By LK| 2015-01-04T01:51:08+00från GoogleLogga inDolda fältSök efter grupper eller meddelanden