Monday, December 22, 2014

      How to reset password on Solaris’ ALOM


Connect to the serial management port.
Unplug power to the server, then connect power.
=====================================================

ALOM POST 1.0


Dual Port Memory Test, PASSED.

TTY External - Internal Loopback Test
         
TTY External - Internal Loopback Test, PASSED.

TTYC - Internal Loopback Test
         
TTYC - Internal Loopback Test, PASSED.

TTYD - Internal Loopback Test
         
TTYD - Internal Loopback Test, PASSED.

Memory Data Lines Test
Memory Data Lines Test, PASSED.

Memory Address Lines Test
  Slide address bits to test open address lines
  Test for shorted address lines
Memory Address Lines Test, PASSED.

============================================================
Press the Escape key during ALOM boot right after connecting power.
============================================================

The ALOM boot escape menu is shown
Boot Sector FLASH CRC Test
Boot Sector FLASH CRC Test, PASSED.



Return to Boot Monitor for Handshake  ESC keypress detected.

ALOM <ESC> Menu

e - Erase ALOM NVRAM.
m - Run POST Menu.
R - Reset ALOM.
r - Return to bootmon.
Your selection: e {Choose e to erase NVRAM}
ALOM NVRAM erased.

ALOM <ESC> Menu

e - Erase ALOM NVRAM.
m - Run POST Menu.
R - Reset ALOM.
r - Return to bootmon.
Your selection: r {Choose r to reset ALOM}

ALOM POST 1.0
   Status = 00007fff

Returned from Boot Monitor and Handshake



Instruction CACHE Test
  DISABLE the I-CACHE
  ENABLE the I-CACHE
  Verify I-CACHE Performance Increase
Instruction CACHE Test, PASSED.

Memory Cells Test
  Counting UP:    Write data:  00000000
  Counting DOWN:  Read - Verify - Write data:  ffffffff
  Counting UP:    Read - Verify - Write data:  55aa33cc
Memory Cells Test, PASSED.

Data CACHE Test
  Verify D-CACHE Performance Increase
    D-CACHE Performance Increase I-CACHE Disabled
    D-CACHE Performance Increase I-CACHE Enabled
  Verify D-CACHE Memory
Data CACHE Test, PASSED.

Main Sectors FLASH CRC Test
Main Sectors FLASH CRC Test, PASSED.

Loading the runtime image... VxWorks running.  Starting Advanced Lights Out Manager CMT v1.3.8  Copyright 2007 Sun Microsystems, Inc.  All rights reserved. Use is subject to license terms.  Current mode: NORMAL
Attaching network interface lo0... done.
Attaching network interface motfec0.... done. Booting from Segment 1

Sun(tm) Advanced Lights Out Manager CMT v1.3.8


SC Alert: SC System booted.


Full VxDiag Tests

BASIC TOD TEST
  Read the TOD Clock:      
SC Alert: Preceding SC reset due to watchdog
SAT JAN 01 00:02:15 2000
  Wait, 1 - 3 seconds      
  Read the TOD Clock:        SAT JAN 01 00:02:17 2000
BASIC TOD TEST, PASSED

ETHERNET CPU LOOPBACK TEST
  50 BYTE PACKET   - a 0 in field of 1's.
  50 BYTE PACKET   - a 1 in field of 0's.
  900 BYTE PACKET  - pseudo-random data.
ETHERNET CPU LOOPBACK TEST, PASSED

Full VxDiag Tests - PASSED



    Status summary  -  Status = 7FFF

       VxDiag    -          -  PASSED
       POST      -          -  PASSED
       LOOPBACK  -          -  PASSED

       I2C       -          -  PASSED
       EPROM     -          -  PASSED
       FRU PROM  -          -  PASSED

       ETHERNET  -          -  PASSED
       MAIN CRC  -          -  PASSED
       BOOT CRC  -          -  PASSED

       TTYD      -          -  PASSED
       TTYC      -          -  PASSED
       MEMORY    -          -  PASSED
       MPC885    -          -  PASSED



sc> shownetwork
SC network configuration is:
IP Address: 10.0.14.189
Gateway address: 0.0.0.0
Netmask: 255.0.0.0
Ethernet address: 00:21:28:4f:a3:1d
=====================================================
sc> setupsc {Set ALOM parameters by running the command setupsc}
Warning: the setupsc command is being ignored because the password for admin is not set.
Setting password for admin.
New password: *********

Re-enter new password: *********

Setup New IP:
=======================================================

sc> setsc netsc_ipnetmask 255.255.255.0
sc> setsc netsc_ipaddr 169.144.193.198
sc> setsc netsc_ipgateway 169.144.193.1
sc> setsc if_network true
sc> showsc
Advanced Lights Out Manager CMT v1.3.8

parameter                value
---------                -----
if_network               true
if_connection            ssh
if_emailalerts           false
netsc_dhcp               true
netsc_ipaddr             169.144.193.198
netsc_ipnetmask          255.255.255.0
netsc_ipgateway          169.144.193.1
mgt_mailhost            
mgt_mailalert          
sc_customerinfo        
sc_escapechars           #.
sc_powerondelay          false
sc_powerstatememory      false
sc_clipasswdecho         true
sc_cliprompt             sc
sc_clitimeout            0
sc_clieventlevel         2
--pause--  Press 'q' to quit, any other key to continue
                                                     
sc_backupuserdata        true
diag_trigger             power-on-reset error-reset
diag_verbosity           normal
diag_level               min
diag_mode                normal
sys_autorunonerror       false
sys_autorestart          reset
sys_eventlevel           2
ser_baudrate             9600
ser_parity               none
ser_stopbits             1
ser_data                 8
netsc_enetaddr           00:21:28:4f:a3:1d
sys_enetaddr             00:21:28:4f:a3:14
                                                     
sc> console

Tuesday, August 12, 2014

Display Default LDOM services

PurposeCommand
Check ldom manager (ldmd)# svcs ldmd
Check vntsd is running# svcs vntsd
Check Default Services are running# ldm list-services primary
Check ldm software# ldm -V
check ldoms manager package in Solaris 11# pkg info ldomsmanager

Creating Default LDOM services

PurposeCommand
add virtual console concentrator (vcc)# ldm add-vcc port-range=5000-5100 primary-vcc0 primary
add virtual network switch (vsw)# ldm add-vsw net-dev=net0 primary-vsw0 primary
add virtual disk server (vds)#ldm  add-vds primary-vds0 primary
add virtual storage device to virtual disk service (Add zfs filesystem to existing Guest domain)# zfs   create -V   5G   rpool/ldom01_disk01
# ldm add-vdsdev  /dev/zvol/dsk/rpool/ldom01_disk01 ldom01_disk01@primary-vds0″

Removing Default LDOM services

PurposeCommand
remove virtual console concentrator (vcc)# ldm remove-vcc  primary-vcc0
remove virtual network switch (vsw)# ldm remove-vsw  primary-vsw0
remove virtual disk server (vds)# ldm remove-vds primary-vds0
remove virtual storage device to virtual disk  service# ldm remove-vdsdev dvd-iso@primary-vds0

Start Default Services

PurposeCommand
start ldom manager# svcadm [enable|restart] ldmd
start vntsd# svcadm [enable|restrat] vntsd

Basic Guest LDOM Administration

PurposeCommand
list resources binded to a Guest Domain   #ldm list-bindings ldom01
how to identify if the current domain role ? [Control,Guest,Service or Root]# virtinfo -a
how to check status of I/O device# ldm list-io
how to check logical domain (ldom) status# ldm  list-domain -o domain ldom01
list the status of all the guest domains on the system# ldm list
how to manually list the LDOM config on a  system# ldm list-bindings [ldom_name]
list current LDOM configuration in Solaris# ldm list-spconfig
Check CPU activation# ldm list-permits
Check Autoreplacement policy for CPU# svccfg -s ldmd listprop ldmd/autoreplacement_policy_cpu

stop/start/break/unbind/bind

PurposeCommand
issue send break# telnet localhost 5000
telnet> send brk
stop Guest Domain# ldm stop ldom01
start Guest Domain# ldm start ldom01
unbind Guest Domain # ldm unbind ldom01
bind Guest Domain # ldm bind ldom01

Add/Create/Assign

PurposeCommand
Add Guest Domain# ldm add-domain ldom01 
assign cpu threads to Guest Domain# ldm add-vcpu 6 ldom01
assign vcpu units of cores# ldm add-core, ldm set-core  [number] [ldom]
assign memory to Guest Domain# ldm add-memory 4G ldom01
add vnet device to Guest Domain# ldm add-vnet vnet1 primary-vsw0 ldom01
assign disk resource to Guest Domain# ldm add-vdisk ldom01-disk01  ldom01-disk01@primary-vds0 ldom01

Remove/Delete

PurposeCommand
Remove a Guest Domain# ldm remove-domain ldom01
Remove disk resource from Guest Domain# ldm remove-vdisk vdisk01 ldom01
Remove virtual network device from a Guest Domain# ldm remove-vnet vnet1 ldom01
Remove CPU threads from a Guest Domain# ldm remove-vcpu 8 ldom01
Remove virtual cpu units in cores from a  Guest Domain# ldm remove-core 2 ldom01
Remove memory from a Guest Domain# ldm remove-memory 8G ldom01

Save LDOM Config

PurposeCommand
save ldom configuration to the SP# ldm add-spconfig newconfig
backup of existing configuration from the control domain# ldm list-constraints -x >  /var/tmp/guest-domain-name.xml
# ldm list-bindings > /var/tmp/full-bindings
# ldm ls -l > /var/tmp/guest-domain-list.xml”

Miscellaneous Commands

PurposeCommand
identify physical resources bindings# ldm list-constraints
login to the console of a Guest Domain# telnet localhost 5001
Enable/Disable console loggging function for  a Guest Domain# ldm set-vcons log=[off|on]  [dom-name]
Display current console settings of a Guest  Domain# ldm list -o console ldom01
list all LDOM config from SP with timestamp-> show /HOST/domain/configs date_created -t
list current LDOM config from SP-> show /HOST/bootmode config -t
Generate crashdump from SP-> set  /HOST/send_break_action=dumpcore
Crash a guest domain from the control domain# ldm panic-domain ldom01
to check failed cpu or memory components from Control Domain# ldm list-domain -l -S

Monday, June 16, 2014

The Brocade DCX 8510-8 requires three IP addresses, which are configured using the ipAddrSet command. IP addresses are required for both CP blades (CP0 and CP1) and for the chassis management IP (shown as SWITCH under the ipAddrShowcommand) in the Brocade DCX 8510-8.
NOTE: The default IP addresses and host names for the Brocade DCX 8510-8 are:
– 10.77.77.75 / CP0 (the CP blade in slot 6 at the time of configuration)
– 10.77.77.74 / CP1 (the CP blade in slot 7 at the time of configuration)
ATTENTION! Resetting an IP address while the Brocade DCX 8510-8 has active IP traffic or has management and monitoring tools running, such as DCFM, Fabric Watch, and SNMP, can cause traffic to be interrupted or stopped.
swDir:admin> ipAddrSet -chassis
Enter the information at the prompts. Specify the -chassis IP address. The -sw 0 IP address is not valid on this chassis.
3.
swDir:admin> ipAddrSet -cp 0
4.
swDir:admin> ipAddrSet -cp 1
swDir:admin> ipaddrset -chassis
Ethernet IP Address [0.0.0.0]: 192.168.1.1
Ethernet Subnetmask [0.0.0.0]: 255.255.255.0
Fibre Channel IP Address [0.0.0.0]:
Fibre Channel Subnetmask [0.0.0.0]:
Issuing gratuitous ARP...Done.
Committing configuration...Done.
swDir:admin> ipaddrset -cp 0
Ethernet Subnetmask [0.0.0.0]: 255.255.255.0
Gateway IP Address [0.0.0.0]: 192.168.1.254
swDir:admin> ipaddrset -cp 1
Ethernet Subnetmask [0.0.0.0]: 255.255.255.0
Gateway IP Address [0.0.0.0]: 192.168.1.254
IP address of remote CP is being changed...Done.
Committing configuration...Done.

Wednesday, June 11, 2014

Linux Kickstart POST Script to Bond Two NICs

       =========================================

for i in $(ifconfig -a | sed 's/[ \t].*//;/^\(lo\|\)$/d' | grep eth)
do
STATUS=$(ethtool $i | grep 'Link detected' | awk -F: '{print $2}')

if [ $STATUS == 'yes' ]; then
                COUNTER=$((COUNTER+1))

                NIC[$COUNTER]="$i"
fi
done

cat << EOF1 >/etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
IPADDR=$IPADDRESS
NETMASK=$NETMASK
USERCTL=no
BONDING_OPTS="mode=1 miimon=100 primary=${NIC[1]}"
EOF1

cat << EOF2 >>/etc/sysconfig/network-scripts/ifcfg-${NIC[1]}
MASTER=bond0
SLAVE=yes
EOF2

cat << EOF3 >>/etc/sysconfig/network-scripts/ifcfg-${NIC[2]}
MASTER=bond0
SLAVE=yes
EOF3

echo 'alias bond0 bonding' >> /etc/modprobe.conf

Wednesday, January 8, 2014

Red Hat Enterprise Solaris vs Linux Run Levels
It's the little things... Why does trying to power off a Linux box using "init 5" fail? Ahhh, RHEL uses different run levels! Gotta keep 'em straight!

Solaris Run Levels:
Run level 0 orderly shut down to "OBP" (OK) prompt
Run level 1 single-user/Administrative mode - user logins disabled
Run level s single-user/Administrative mode - user logins disabled
Run Level S single-user/Administrative mode - user logins disabled
Run level 2 multi-user mode with no NFS
Run level 3 multi-user mode with networking (default)
Run level 4 not used
Run level 5 shut down & power off
Run level 6 full shutdown and reboot (graceful shutdown & reboot)


Linux Run Levels:
Run level 0 orderly shut down and power down
Run level 1 single-user mode
Run level s single-user mode
Run level S single-user mode
Run level 2 multi-user mode with networking support, but no network services(i.e., X-Windows support, NFS/NIS, at, or xinetd support)
Run level 3 multi-user mode with networking support, plus network services
Run level 4 not defined
Run level 5 multi-user mode with X-Windows support (default run level)
Run level 6 full shutdown and reboot (graceful shutdown & reboot)
Run level 7,8,9 not defined

RHEL also has a "poweroff" command that performs the same function as "init 5" on Solaris, or "init 0" on RHEL. However, just remember to put the word "man" in front of that "poweroff" command if you're doing research on it, since the RHEL "poweroff" command works A LOT faster than the Solaris "init 5" command - there's no "quick, kill the process" option to keep the system from going down immediately when you enter "poweroff" in error!!! :-)