Category: Solaris Troubleshooting


Solaris Troubleshooting Jumpstart – Common Problems

How Jumpstart Works:     First Level Boot Process 1) When the “boot net – install” command is issued at the ok prompt, the JumpStart client looks for a Jumpstart boot server. 2) The boot server responds to the rarp request via the “rarpd” daemon (in.rarpd)....


Solaris Troubleshooting : Identifying the network address and port number for a running process

For Solaris System Administrators It is often necessary to find out all the related processes that are using a specific network port.  There are several ways to accomplish this (lsof, pfiles, crash): Method 1: lsof examples: Ex: netstat -a shows a connection between hodware.port 36169 to...


Solaris Troubleshooting Jumpstart : Identification of right network interface for network boot

During the jumpstart installation of a client below error is most command error that we encounter: Error: “Timeout waiting for ARP/RARP packet” This error cause might be network connectivity and most of the times it is the wrong network interface that is configured to boot from...


Solaris Networking Troubleshooting

The one problem that is vrey common in every system administrator’s life is network  issue, and most of the times it will kill  entire day if the root cause/symptoms were    misunderstood . Below information will help you to understand some of the basic  network issues...


Solaris Troubleshooting : Determine cause of a system fault at ok> prompt

The following is useful information on how to determine the cause of a system crash at the ok prompt, using the open boot commands. The Synchronous Fault Status Register (SFSR) provides information on exceptions (faults) issued by the Memory Management Unit (MMU).


Solaris Troubleshooting : Restore SDS Root mirror from the backup

NOTE: In order to restore the machine exactly the way it was, it is necessary to have a record of the locations of the state databases, and also the configuration of the metadevices. These are *not* held in user-readable form on the root filesystem, so it...


VXVM : Unable to recognise newly-added disks

VERITAS Volume Manager 3.x/4.x: Unable to Recognize Newly-Added Disks. A few reasons why this occurs: The command vxdctl enable should be run, to rescan the host for any newly-added disks.

  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us