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

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...