XSCF sun solaris command

In order to login into console from XSCF you must know in which domain you want to login into.

1. To show all the domains on a server.

XSCF> showdomainstatus -a

DID         Domain Status

00          Running

01          Running

02          -

03          -

2. To check the status of server.

XSCF> showstatus

No failures found in System Initialization.

Note: Currently on the server no hardware fault. this command clearly show the current status.

3. To login in domain-

XSCF> console -d 00

Console contents may be logged.

Connect to DomainID 0?[y|n] :y

if the console is not appear then you can run the below command to take a console forcefully.

XSCF> console -d 00 -f

Console contents may be logged.

Connect to DomainID 0?[y|n] :y

4. To check the complete hardware status from XSCF.

XSCF> showhardconf

5. To return to XSCF from domain , type

#.

6. To power-on & power-off the domain

XSCF> poweroff -d 00

XSCF>poweron -d 00

Note: if domain 00 is not power off , you can use "-f" with command to shutdown forcefully.

7. To check the error & power logs from SXCF

XSCF> showlogs error

Date: Nov 02 11:15:03 UTC 2016     Code: 40000200-cfffd701-0300003200000000

    Status: Information            Occurred: Nov 02 11:15:02.536 UTC 2016

    FRU: /HDD#0,/IOU#0

    Msg: Boot process failed

XSCF> showlogs power

Date                          Event            Cause          DID  Switch

Jan 01 00:29:36 UTC 2001      SCF Reset        Power On       --   Locked

Jan 01 01:43:31 UTC 2001      SCF Reset        Self Reset     --   Locked

8. To check the hostname of XSCF server

XSCF> showhostname -a

9. To view the fault management logs

XSCF> fmdump -v

TIME                 UUID                                 MSG-ID

Nov 02 11:15:03.3078 b121fe1b-a418-4b9e-8a23-474dda80891f SCF-8001-KC

   66%  upset.chassis.SPARC-Enterprise.io.disk.boot

10. To reboot the XSCF

XSCF>rebootsxcf

11. To display complete network information

XSCF> shownetwork  -a

xscf#0-lan#0

          Link encap:Ethernet  HWaddr 00:21:28:6E:C4:AA

          inet addr:192.168.0.1  Bcast:192.168.255.255  Mask:255.255.0.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:240177064 errors:419 dropped:0 overruns:0 frame:0

          TX packets:75330 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3346969538 (3.1 GiB)  TX bytes:12900961 (12.3 MiB)

          Base address:0xe000

xscf#0-lan#1

          Link encap:Ethernet  HWaddr 00:21:28:6E:C4:AB

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

          Base address:0xc000

Sun Solaris useful commands

1. to check the storage size useful

dipso

2. to check the product model

prtconf -b

3.Display system information

cat /etc/release

4.How to display a system phycial processor type

psrinfo -pv

5. to check the SUN powerpath

/etc/powermt version

or

pkginfo -l EMCpower


6. To check the sun server system configuration

#prtdiag

Solaris local zone not booting "zoneadm: zone 'zone_name': call to zoneadmd failed"

Hello Friends,

In this post, I will explain you the one important issue which we generally facing while we boot the local Solaris zone on the Sun Solaris operating system.

When you are trying to boot the local zone from your Global zone, you encounter the below error message as mentioned below.

Error: zoneadm: zone 'sunz1': "/usr/lib/fs/zfs/mount das/sunz1/export /zones/sunz1/root/export" failed with exit code 1
zoneadm: zone 'sunz1': call to zoneadmd failed.

Solution: For such type of issue is normally related to NFS. When you boot the server, it will start NFS service before start zones. so, as NFS is started, FS /zones/sunz1/root/export  is already in use so global zone doesn't want to start a zone with a FS already in use by a process. You can check which file system is mounted on your global zone as describe below.

sun:/> cat /etc/dfs/dfstab

#       Place share(1M) commands here for automatic execution
#       on entering init state 3.
#
#       Issue the command 'svcadm enable network/nfs/server' to
#       run the NFS daemon processes and the share commands, after adding
#       the very first entry to this file.
#
#       share [-F fstype] [ -o options] [-d "<text>"] <pathname> [resource]
#       .e.g,
#       share  -F nfs  -o rw=engineering  -d "home dirs"  /export/home
share -F nfs -o rw=sun.vibhor.com:sunz1.vibhor.com /zones/sunz2/root/export

In above output you can see one folder is NFS mounted on the two local zone.

2. Now for resolving the issue , please stop the NFS service, boot the zone and restart the service.

sun:/> svcs status nfs/server
STATE          STIME    FMRI
online          5:13:30 svc:/network/nfs/status:default
online          5:13:36 svc:/network/nfs/server:default

Currently NFS server service is online on the Global zone, so using below command we will disable the service.

sun:/> svcadm disable nfs/server

sun:/> svcs status nfs/server
STATE          STIME    FMRI
disabled        5:21:57 svc:/network/nfs/server:default
online          5:13:30 svc:/network/nfs/status:default

3. Now we will boot the local zone again and see the existing error occur or not.

sun:/> zoneadm -z sunz1 boot

Note: Now your local zone is boot without any error. So normally this problem occur when NFS is mounted on the server.

4. Once the issue has been resolved you may enable the NFS server services.

sun:/> svcadm enable nfs/server

sun:/> svcadm restart nfs/server

If you see the my screen output images the whole method is describe step by step. If you facing still issue please comment on this post.