Skip to main content

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-(

I'm struggling to recognize a reason that a default should even be present on the array.

Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-)

My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly.

I was curious as to what version of SunOS it was running.

Notice the following progression:


uss01:> shell
Executing shell commands may invalidate your service contract. Continue? (Y/N)
Executing raw shell; "exit" to return to appliance shell ...


uss01# uname
+-----------------------------------------------------------------------------+
|  You are entering the operating system shell.  By confirming this action in |
|  the appliance shell you have agreed that THIS ACTION MAY VOID ANY SUPPORT  |
|  AGREEMENT.  If you do not agree to this -- or do not otherwise understand  |
|  what you are doing -- you should type "exit" at the shell prompt.  EVERY   |
|  COMMAND THAT YOU EXECUTE HERE IS AUDITED, and support personnel may use    |
|  this audit trail to substantiate invalidating your support contract.  The  |
|  operating system shell is NOT a supported mechanism for managing this      |
|  appliance, and COMMANDS EXECUTED HERE MAY DO IRREPARABLE HARM.             |
|                                                                             |
|  NOTHING SHOULD BE ATTEMPTED HERE BY UNTRAINED SUPPORT PERSONNEL UNDER ANY  |
|  CIRCUMSTANCES.  This appliance is a non-traditional operating system       |
|  environment, and expertise in a traditional operating system environment   |
|  in NO WAY constitutes training for supporting this appliance.  THOSE WITH  |
|  EXPERTISE IN OTHER SYSTEMS -- HOWEVER SUPERFICIALLY SIMILAR -- ARE MORE    |
|  LIKELY TO MISTAKENLY EXECUTE OPERATIONS HERE THAT WILL DO IRREPARABLE      |
|  HARM.  Unless you have been explicitly trained on supporting this          |
|  appliance via the operating system shell, you should immediately return    |
|  to the appliance shell.                                                    |
|                                                                             |
|  Type "exit" now to return to the appliance shell.                          |
+-----------------------------------------------------------------------------+
uss01# which uname
/usr/bin/uname
uss01# file /usr/bin/uname
/usr/bin/uname: ELF 32-bit LSB executable 80386 Version 1 [FPU], dynamically linked, not stripped, no debugging information available
uss01# /usr/bin/uname
SunOS
uss01# /usr/bin/uname -a
SunOS uss01 5.11 ak/generic@2010.08.17.4.2,1-1.37 i86pc i386 i86pc

First.. somehow the uname command dumps out the banner, or /etc/motd.  Nice.






Updating the IP address on a USS 7110 (7x10) Array from command line

[jradtke@neo ~]$ ssh root@10.10.21.10
Password:

Sun(TM) Integrated Lights Out Manager

Version 2.0.2.5

Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

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

Serial console started.  To stop, type ESC (



uss01:> configuration
uss01:configuration> net
uss01:configuration net> interfaces
uss01:configuration net interfaces> select nge1
uss01:configuration net interfaces nge1> set v4addrs=10.10.21.42/24
                       v4addrs = 10.10.21.42/24 (uncommitted)
uss01:configuration net interfaces nge1> commit

uss01:configuration net interfaces nge1> cd ..
uss01:configuration net interfaces> select nge2
uss01:configuration net interfaces nge2> set v4addrs=10.10.21.43/24
                       v4addrs = 10.10.21.43/24 (uncommitted)
uss01:configuration net interfaces nge2> commit
uss01:configuration net interfaces nge2> cd ..
uss01:configuration net interfaces> select nge3
uss01:configuration net interfaces nge3> set v4addrs=10.10.21.44/24
                       v4addrs = 10.10.21.44/24 (uncommitted)
uss01:configuration net interfaces nge3> commit

uss01:configuration net interfaces nge3> cd ..
uss01:configuration net interfaces> select ipmp1

uss01:configuration net interfaces ipmp1> set v4addrs=10.10.21.40/24
                       v4addrs = 10.10.21.40/24 (uncommitted)
uss01:configuration net interfaces ipmp1> commit

uss01:configuration net interfaces ipmp1> cd ..
uss01:configuration net interfaces> show
Interfaces:

INTERFACE   STATE    CLASS LINKS       ADDRS                  LABEL
ipmp1       up       ipmp  nge3        10.10.21.40/24         IPMP-01
                           nge2                              
                           nge1                              
                           nge0                              
nge0        up       ip    nge0        10.10.21.41/24         interface 0
nge1        up       ip    nge1        10.10.21.42/24         interface 1
nge2        up       ip    nge2        10.10.21.43/24         interface 2
nge3        up       ip    nge3        10.10.21.44/24         interface 3

uss01:configuration net interfaces> cd /

uss01:>  shell
Executing shell commands may invalidate your service contract. Continue? (Y/N)
Executing raw shell; "exit" to return to appliance shell ...

+-----------------------------------------------------------------------------+
|  You are entering the operating system shell.  By confirming this action in |
|  the appliance shell you have agreed that THIS ACTION MAY VOID ANY SUPPORT  |
|  AGREEMENT.  If you do not agree to this -- or do not otherwise understand  |
|  what you are doing -- you should type "exit" at the shell prompt.  EVERY   |
|  COMMAND THAT YOU EXECUTE HERE IS AUDITED, and support personnel may use    |
|  this audit trail to substantiate invalidating your support contract.  The  |
|  operating system shell is NOT a supported mechanism for managing this      |
|  appliance, and COMMANDS EXECUTED HERE MAY DO IRREPARABLE HARM.             |
|                                                                             |
|  NOTHING SHOULD BE ATTEMPTED HERE BY UNTRAINED SUPPORT PERSONNEL UNDER ANY  |
|  CIRCUMSTANCES.  This appliance is a non-traditional operating system       |
|  environment, and expertise in a traditional operating system environment   |
|  in NO WAY constitutes training for supporting this appliance.  THOSE WITH  |
|  EXPERTISE IN OTHER SYSTEMS -- HOWEVER SUPERFICIALLY SIMILAR -- ARE MORE    |
|  LIKELY TO MISTAKENLY EXECUTE OPERATIONS HERE THAT WILL DO IRREPARABLE      |
|  HARM.  Unless you have been explicitly trained on supporting this          |
|  appliance via the operating system shell, you should immediately return    |
|  to the appliance shell.                                                    |
|                                                                             |
|  Type "exit" now to return to the appliance shell.                          |
+-----------------------------------------------------------------------------+
uss01#












Comments

  1. Sun Uss 7100 Foo >>>>> Download Now

    >>>>> Download Full

    Sun Uss 7100 Foo >>>>> Download LINK

    >>>>> Download Now

    Sun Uss 7100 Foo >>>>> Download Full

    >>>>> Download LINK lV

    ReplyDelete

Post a Comment

Popular posts from this blog

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up.  After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa.   -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un