Solaris Zone Cloning

Procedure :-
1.Expert the configuration of the zone you want to clone.
  #zonecfg -z zone1 export  > zone2.cfg
2.Change details of new zone from diff from the existing zone(ipaddress,zonepath,nework interface )
 #vi zone2.cfg
3.Create new zone (empty zone) in the user manul based on this configuration file.
 #  zonecfg -z zone2 -f zone2.cfg
4.Ensure that the zone you intent to clone /copy is not running                                  
 #zoneadm -z zone1 halt
5.Clone the existing Zone
 #zoneadm -z zone2 clone zone1

VXVM Failures

Refer the below link :-
http://www.unixarena.com/2012/07/vxvm-failures.html

 Thanks to Unix arena @Lingeshwaran R

Solaris Some important Questions

1.NFS client is not able to access NFS server? Troubleshooting steps?
   @.Verify the connectivity between NFS server & NFS client
   @.Check the NFS ports are open in network side.
   @.Verify the shares are properly exported to NFS clients
2.If on jumpstart client, boot command "boot net install" doesn't work, what could be the possible reasons?
  @.Check the network connectivity using watch-net-all from OK prompt.
  @.Verify the MAC address in Jumpstart server.
3.What is /etc/system file gets corrupted? How will system bootup?
   If you modify your /etc/system file in Solaris and screw it up or it gets corrupt, when you try to reboot, the server will no longer startup.

To recover from this problem:

1) As the server starts booting, press Stop+A (at the same time)

2) At OK> prompt, type "boot -as"

3) Solaris will now go into an interactive boot and will ask you several things.

4) Answer using all the defaults until it asks for your system file. 

5) Either specify the name of a backup system file (if you have one) OR type "/dev/null"

6) It will allow the system to boot with a vanilla kernel so that you can fix the broken /etc/system

7) Fix the /etc/system file

  4.What is mean by paging & server average time.

If a disk shows consistently high reads/writes along with , the percentage busy (%b) of the disks is greater than 5 percent, and the average service time (svc_t) is greater than 30 milliseconds, then one of the following action needs to be taken

@.If the LUNS average service time is more than 30 ,then you need to check with SAN team .They will help you with issue. May be they will spread the LUNS to multiple physical disks in the back end.

Solaris 10 Interview questions

http://www.unixarena.com/2013/05/solaris-10-interview-questions.html#sthash.xNXihZSd.dpuf

Solaris Administrator Interview Questions

1 Tell Me the problem u have faced?

2 what is the veritas volume manager?

3 difference between solaris 10,9?

4 What is the zone,how to add memory without restart,is it possible?

5 How to replace the failed hdd in svm explain the procedure?

6 R u working Disaster Recovery Setup?

1 how to change boot order in ok promt

2 how to add the Kernal patch & precaution?

3 what is the at & crontab?how many felds?

4 what is the root mirror & how to configure step by step?

5 what is the metadb ?& algaritham?

1.How to do the Kernal Patch?& after installed patch system not booting or some problem how to resolve?

2 How to check ip address in OK Prompt

3 How to check mirror disk in OK Prompt

4

How to check Kernal version OK Prompt

5

How to check disk & boot disk in OK prompt?

6

How to revert the server in working status after install the patch had problem..

7

How to configure the Zones?

8

How to configure the Veritas mirror volume  with 2 disk?

9

How to manage the server remotly through console?

10

How to configure the T-series server?

11

how to perform Performance Tuning?

12

What are the Veritas daemons?

13

How to bring disk under Veritas control ?

14

What is the difference between init1 & init S?

15

How to boot system from OK Prompt?

16

How many run levels ?

17

How to go ok Prompt from init run level 3?

Solaris Sparc Server Consoles using ALOM Commands

            ALOM (Advanced Lights Out Manager System Controller) only on SUN Sparc system
                   
1.Alom System COntroller enables you to remotely manage and administrator a server
2.It comes preinstalled on the machine , so as soon you plug in power cable, it works
3.Yes,It uses server's standby power,which enables you to remotely power off & on server
4.ALOM Monitors hardware in the server like CPU,RAM,Power supply,etc,and much more like Voltage and status of alarms.
5.of course,all this exercise assumes you configured ALOM's network parameters.Try to have dedicated management subnet for this
6.If you access ALOM and stay idle for 1 min .it will switch the serial console
7.You can type "console" and reach serial console of remote system from your cube or home living room.

Some ALOM Shell Commands:-

cannot login to the ALOM?
Try default password which is the last 8 digits of the chassis serial no.Usernameis "admin"
So find about them by yourself and see what help offers you.
sc> help  ------> It shows available commands
Most used commands will be:-
sc>setsc set if_network true
sc>setsc netsc_dhcp false
sc>setsc netsc_ipaddr 192.168.2.4
sc>setsc netsc_ipnetmask 255.255.255.0
sc>setsc netsc_ipgateway 192.168.2.1
sc>resetsc 
Are you sure you want reset the sc[y.n] y

sc> shownetwork
sc configuration is:
IP address :192.168.2.4
Gateway address:192.168.2.1
Netmask:255.255.255.0
Ethernet address:00:14:4f:64:b2:6f

sc>showplatform
SUNW,SUN-Fre-v240
Domanin status
------- ------
hostname OS running


sc>showenvironment ------> all hardware details like Hdd,system temperature,Fans,powersupply,
sc>usershow            ------> It will show username,permissions password 
sc>password         ---->Use to change the ALOM password for the account Must be between 6 & 8 characters 

sc>poweroff        ---->Graceful shutdown of the Solaris OS after "SC Alert:Hostsystem has shut down" wait until                                  you see this message beforepoering the system back on 

sc>poweroff -y --->Instructs ALOM to proceed without prompting 

sc>poweroff -f --->Forces an immediate shutdown regardless of the state of the host 

sc>poweron -c ---> Instructs ALOM to connect to the system console after performing the option 

sc>removefru PS0 --->To prepare POWER SUPPLY 0 form removal "T1000 servers attempting to use the 

                                removefru command on "PS0" Generates message "Could not remove <PS0> system only                                has one power supply 

sc>reset         ---->To force the host server to rest immediately 

sc>reset -c     ---->Instructs ALOM to connect to the system console after performing the operation. 

sc>resetsc     ---> To perform a hard reset of ALOM. This terminates all current ALOM sessions.
 

Solaris Useful OK prompt commands

                                Some Useful OK prompt commands

OK show-disks  ------> To show the disks
OK probe-scsi  ------> To search the scsi devices attached to the primary scsi controller
OK probe-scsi-all ---> To search all the scsi devices
OK devalias   ----> to list device alias names
OK devalias <alias> <path> --->To temporarily create a device alias
OK printenv            ---->To view the current NVRAM settings
OK setenv <env> <value> -----> To set the envirement variables
OK set-defaults                 -----> To set the open boot prompt settings to the factory default
OK nvalias <alias> <path>  --->To set the device alias permanently to NVRAM
OK nvunalias cdrom1  ----> To remove the nvalias 'cdrom1' from NVRAMRC
OK .version   ------> To find out the Open boot prompt version
OK .ent_addr -----> To find out the ethernet MAC address
OK .speed    -----> To find out the CPU and PCI bus speeds
OK banner    -----> To display the Model,Architecture,processor,openboot version,ethernet address,hostid and etc
OK set-defaults ----> To reset variable values to the factory defaults
OK reset-all -----> To reboot the system from OK Prompt
OK show-devs  ----->To show the PCI devices
OK boot   ---> boot the system from the default boot devices
OK boot cdrom ----> to boot from cdrom
OK boot disk ----> boots the system from device as specified by the disk device alias
OK boot device-path ---->boot from the full device mentioned
OK boot net ----> network boot .boots from a TFTP boot server or Jumpstart server
OK boot net -install  -----> Jumpstart boot.
OK boot tape -----> Tape boot.boots off a SCSI tape if available
OK boot -h ----> boot halted .boot into a halted state(ok prompt) intersting for troubleshooting boot at the lowest level
OK boot -r ----> Reconfiguration boot.Boot and search for all attached device.useful when new device attached to the system
OK boot -s ----> Single user.boots the system to run level 1
OK boot -v ----> verbose boot.show good debugging information.
OK boot -F failsafe   ---> to boot the server to failsafe mode

------------------------------------------------------------------------------------------------------------
                                Displaying System Information
Commands to display additional system related information .Not all commands work on all Platforms
OK .idprom  --------> Display ID PROM contents
OK .traps  --------> Display a list of processor-dependent trap types
OK show-devs ----->display list of installed and probed devices
OK eject floppy ----> Eject the floppy
OK eject cdrom ------>eject the cdrom
OK sync -----> call the operating system to write information to hard disk

-----------------------------------------------------------------------------------------------                      
                        Emergency Keyboard Commands
These are key sequences recognized by the system to perform predetermined
actions at boot time or during normal operation.

Stop     ---> Bypass POST .(This command does not depend on security-mode)
Stop-A ---> Abort.(This will also stop a running system. You can
                    resume normal operations if you enter go at the prompt.
                    Enter anything else and you will stay halted)
Stop-D  ---> Enter diagnostic mode(set diag-switch?to true)
Stop-N  ---> Reset NVRAM contents to default values.