Monday, December 31, 2012

Disable T5120 RAID - Cause failure in booting/installing from HD

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started.  To stop, type #.

{0} ok show-disks
a) /pci@0/pci@0/pci@8/pci@0/pci@9/LSILogic,sas@0/disk
b) /pci@0/pci@0/pci@2/scsi@0/disk
c) /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/hub@4/device@4/storage@0/disk
Enter Selection, q to quit: c
/pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/hub@4/device@4/storage@0/disk has been selected.
Type ^Y ( Control-Y ) to insert it in the command line.
e.g. ok nvalias mydev ^Y
         for creating devalias mydev for /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/hub@4/device@4/storage@0/disk
{0} ok boot /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/hub@4/device@4/storage@0/disk -s
Boot device: /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/hub@4/device@4/storage@0/disk  File and args: -s

How To Reset The ALOM Password On A Sun Fire T2000

If an ALOM password reset is required on a Sun Fire T1000 or Sun Fire T2000 in case the password is lost or forgotten, the following steps can be taken to erase the ALOM NVRAM so that a user can gain access to it, set a new password and restore the NVRAM settings.
Note: Access to the server’s power cables and the ALOM serial port is required for this procedure.
Connect your computer or laptop to the ALOM serial management port.
Power cycle the system by unplugging the server’s power supplies, waiting several seconds and then plugging the power back in. You should see the ALOM booting on the serial management console. Hit “Esc” during the ALOM boot, before or at the point where the display says:
Return to Boot Monitor for Handshake
The system will return with this message:
Return to Boot Monitor for Handshake ESC keypress detected.
The ALOM enters the “ALOM boot escape menu”. The following choices will be displayed:
ALOM  Menu
e - Erase ALOM NVRAM.
m - Run POST Menu.
R - Reset ALOM.
r - Return to bootmon.
Your selection:

Saturday, December 22, 2012

Installing Net-SNMP on Solaris OS

Sun OS versions previous to Solaris10 come configured with the Sun SNMP agent. Solaris has started shipping Net-SNMP with Solaris10 as an alternative to the Sun SNMP agent, this guide is designed to offer a road-map for installing Net-SNMP on versions older than Solaris10 so that users can utilize both the inclusion of the HOST-MIB Tree (Disk and CPU monitoring) and the use of SNMPv3 (encryption of SNMP traffic over a network) within these previous OS's (capability unavailable in the Sun SNMP agent).

Check For Sun SNMP Agent:
Before we start we need to check for the existence of the Sun SNMP agent and turn it off if it is running.

To do so run the following command from the command line:

ps -ef | grep snmp

Wednesday, December 19, 2012

How to Upgrade to Perl 5.12.5 on Linux Machine

Upgrading Perl from source on Linux

This tutorial explains how to compile Perl 5.12 for a Linux machine. In this tutorial, CentOS 5 / Red Hat Enterprise Linux 5 will be used, however the procedure should be quite similar for other distributions of Linux as well.
Note: You may be tempted to do a `yum remove perl` to remove the 5.8 version that your distribution came with. Don't. I'll give an explanation why later on.

Does your vendor already have Perl 5.12?

If you can install Perl 5.12 via yum, apt, portage, or whatever your package manager is, I highly recommend you do it. It's always better to install things so that your package manager is aware of their existence rather than to go ahead and install something behind its back. If all you can get is Perl 5.8, though, you'll need to compile it yourself.

Download the Perl Source

Just link to and click the "Download" link at the top of the page. That should get you the source code to the most recent version of Perl, which is currently 5.12.5. (Stable Release) Download it, extract it somewhere, and open up a terminal.

Wednesday, December 12, 2012

Year 2038 problem

The year 2038 problem may cause some computer software to fail at some point near the year 2038. The problem affects all software and systems that both store system time as a signed 32-bit integer, and interpret this number as the number of seconds since 00:00:00 UTC on Thursday, 1 January 1970.[1] The furthest time that can be represented this way is 03:14:07 UTC on Tuesday, 19 January 2038.[2] Times beyond this moment will "wrap around" and be stored internally as a negative number, which these systems will interpret as a date in 1901 rather than 2038. This is caused by integer overflow. The counter "runs out" of usable digits, "increments" the sign bit instead, and reports a maximally negative number (continuing to count up, toward zero). This is likely to cause problems for users of these systems due to erroneous calculations.
Further, while most programs will only be affected in or very close to 2038, programs that work with future dates will begin to run into problems much sooner. For example, a program that works with dates 20 years in the future will have to be fixed no later than 2018.
Because most 32-bit Unix-like systems store and manipulate time in this format, it is usually called Unix time, and so the year 2038 problem is often referred to as the Unix Millennium Bug.

Example showing how the date would reset, represented as a signed 32bit integer (at 03:14:08 UTC on 19 January 2038).

See original Wikipedia article »

Search & Buy Amazon Products at discounted rate!!


Subscribe to AtoZ-networking Newsletter

Do you want to receive Linux FAQs, Microsoft FAQ, Solaris FAQ, detailed Networking tutorials and tips published at atoz-networking? Enter your email address below, and we will deliver our Linux posts straight to your email box, for free. Delivery powered by Google Feedburner.

Sign-up for the newsletter