1. Architecture and configuration of sunfire v440 Features SunFire V240 SunFire V440 Sun Fire V880 Rack or tower Rack Rack Tower (rack optional) Number of processors 1–2 2–4 2, 4, 6, or 8 CPU type UltraSPARC IIIi UltraSPARC IIIi UltraSPARC III CPU speed 1.06/1.28 GHz 1.06/1.28 GHz 900 MHz/1.05 GHz Level 2 cache 1 MB internal cache 1 MB internal cache 8 MB external cache Minimum/maximum 512 MB/8 GB 4 GB/16 GB 1024 MB/64 GB memory O/S Solaris 8/9 Solaris 8 Solaris 8/9 PCI slots 3 (1 x 66 MHz/64 bits, 6 (3 x 66 MHz/64 bits, 8 (1 x 66 MHz/64 bits, 2 x 33 MHz/64 bits) 3 x 33/66 MHz/64 bits) 7 x 33 MHz/64 bits) Network connections 4 x built-in 2 x built-in 1 x built-in 10/100/1000 BaseT 10/100/1000 BaseT 10/100/1000 Fiber Ethernet ports Ethernet ports Ethernet port I/O connections 1 x serial, 2 x USB, 2 x serial, 4 x USB, 2 x serial, 2 x USB, 1 x LVD 160 SCSI 1 x Ultra320 SCSI 1 x 10/100MB/s, 1 x GbE, 1 x FC-AL Number of disks and type 4 x Ultra160 SCSI 4 x Ultra320 SCSI 12 x FC-AL 36 GB/73 GB 36 GB/73 GB 36 GB/73 GB Remote management ALOM (standard) ALOM (standard) RSC, 1 x 10 Mb/s Ethernet, 1 x 10 Mb/s Ethernet, 1 x 10 Mb/s Ethernet, 1 x RJ45 Serial, 1 x RJ45 Serial 1 x RJ45 Serial 1 xRJ45 Modem System Configuration Card Yes Yes N/A 2. Special features in Sunfire T-series server Oracle VM Server for SPARC (previously called Sun Logical Domains) provides highly efficient, enterprise-class virtualization capabilities for Oracle's SPARC T-Series servers. Oracle VM Server for SPARC allows you to create up to 128 virtual servers on one system to take advantage of the massive thread scale offered by SPARC T-Series servers and the Oracle Solaris operating system. And all this capability is available at no additional cost. 3. steps to replace the hard disk in SVM. Check the error with the help of following commands # iostat -En
Transcript
1. Architecture and configuration of sunfire v440
Features SunFire V240 SunFire V440 Sun Fire V880Rack or tower Rack Rack Tower (rack optional)Number of processors 1–2 2–4 2, 4, 6, or 8CPU type UltraSPARC IIIi UltraSPARC IIIi UltraSPARC IIICPU speed 1.06/1.28 GHz 1.06/1.28 GHz 900 MHz/1.05 GHzLevel 2 cache 1 MB internal cache 1 MB internal cache 8 MB external cacheMinimum/maximum 512 MB/8 GB 4 GB/16 GB 1024 MB/64 GBmemoryO/S Solaris 8/9 Solaris 8 Solaris 8/9PCI slots 3 (1 x 66 MHz/64 bits, 6 (3 x 66 MHz/64 bits, 8 (1 x 66 MHz/64 bits,
2 x 33 MHz/64 bits) 3 x 33/66 MHz/64 bits) 7 x 33 MHz/64 bits)Network connections 4 x built-in 2 x built-in 1 x built-in
1 x 10 Mb/s Ethernet, 1 x 10 Mb/s Ethernet, 1 x RJ45 Serial,1 x RJ45 Serial 1 x RJ45 Serial 1 xRJ45 Modem
System Configuration Card Yes Yes N/A
2. Special features in Sunfire T-series server
Oracle VM Server for SPARC (previously called Sun Logical Domains) provides highly efficient, enterprise-class virtualization capabilities for Oracle's SPARC T-Series servers. Oracle VM Server for SPARC allows you to create up to 128 virtual servers on one system to take advantage of the massive thread scale offered by SPARC T-Series servers and the Oracle Solaris operating system. And all this capability is available at no additional cost.
3. steps to replace the hard disk in SVM.
Check the error with the help of following commands # iostat -En
...
c1t0d0 Soft Errors: 607 Hard Errors: 122 Transport Errors: 130 Vendor: SEAGATE Product: ST373207LSUN72G Revision: 065A Serial No: 054432ZX97 Size: 73.40GB Media Error: 99 Device Not Ready: 0 No Device: 11 Recoverable: 607 Illegal Request: 0 Predictive Failure Analysis: 9 c1t1d0 Soft Errors: 0 Hard Errors: 2 Transport Errors: 5 Vendor: FUJITSU Product: MAT3073N SUN72G Revision: 0602 Serial No: 0517B04DKE Size: 73.40GB Media Error: 0 Device Not Ready: 0 No Device: 1 Recoverable: 0 Illegal Request: 0 Predictive Failure Analysis: 0 c1t2d0 Soft Errors: 60 Hard Errors: 119 Transport Errors: 78 Vendor: SEAGATE Product: ST373207LSUN72G Revision: 065A Serial No: 064135KFJE Size: 73.40GB ...
Well, what are this "errors" stuff is about?
Device Not Ready: The drive returned the sense key 0x2 (Not ready).
Media Error: The drive returned the sense key 0x3(Medium Error).
No Device: The drive returned the sense key 0x6 (Unit Attention) or in the case of a removable device it must have happened multiple times.
Hard Errors: All the above conditions are counted as Hard errors with the addition of the SCSI sense key 0x4 (Hardware Error).
Illegal Request: The drive returned the sense key 0x5 (Illegal Request). This also treats as a Soft Error and that kstat is also incremented.
Recoverable: The drive returned the sense key 0x1 (Recovered Error) to indicate that the last command completed successfully but some recovery action had to be taken by the drive. This also treats as a Soft Error and that kstat is also incremented.
Predictive Failure Analysis: The drive returned sense key 0x6 (Unit Attention) with and ASC (Additional Sense Code) of 0x5D indicating that the drive has exceeded it's predictive failure threshold. This is treated as a soft error.
Transport Error: This error occurs for a number of reasons all related to being unable to transport the command. The command could have been timed out or reset or the host bus adapter unable to put the command onto the SCSI bus. This is neither as soft nor a hard error.
Device Not Ready: The drive returned the sense key 0x2 (Not ready).
Media Error: The drive returned the sense key 0x3(Medium Error).
No Device: The drive returned the sense key 0x6 (Unit Attention) or in the case of a removable device it must have happened multiple times.
Hard Errors: All the above conditions are counted as Hard errors with the addition of the SCSI sense key 0x4 (Hardware Error).
Illegal Request: The drive returned the sense key 0x5 (Illegal Request). This also treats as a Soft Error and that kstat is also incremented.
Recoverable: The drive returned the sense key 0x1 (Recovered Error) to indicate that the last command completed successfully but some recovery action had to be taken by the drive. This also treats as a Soft Error and that kstat is also incremented.
Predictive Failure Analysis: The drive returned sense key 0x6 (Unit Attention) with and ASC (Additional Sense Code) of 0x5D indicating that the drive has exceeded it's predictive failure threshold. This is treated as a soft error.
Transport Error: This error occurs for a number of reasons all related to being unable to transport the command. The command could have been timed out or reset or the host bus adapter unable to put the command onto the SCSI bus. This is neither as soft nor a hard error.
This is my steps to change the faulted hdd in SVM for RAID-O (mirroring) (in this example, faulting hdd is c1t1d0, and submirror living on it is d100, mirror using this submirror is d1):
1. Identify the submirrors which reside on faulting disk drives
# metastat
<look for the slices that are being used on faulting drives, note them>
2. Detatch this submirrors from the mirrors
# metadetatch d1 d100
<example, detatching from mirror d1 submirror d100, that lives on faulty hdd>
3. Clear the info used by SVM on detatched submirror
# metaclear d100
4. Check that you get rid of that submirror:
# metastat -p | grep d100
5. Remove SVM database replicas on that disk, that will be replaced
# metadb | grep c1t1d0
6. If you`ll find any replicas on this disk - delete them - and check, that they were deleted
# metadb -d /dev/c1t1d0s7 && metadb | grep c1t1d0
7. If there is open filesystem, that is not being controlled by SVM - unmount them
8. Find & unconfigure the faulty hdd, replace the hdd - checking the dmesg - and configure the new one
# cfgadm -al
# cfgadm -c unconfigure c1::dsk/c1t1d0
# dmesg
# cfgadm -c configure c1::dsk/c1t1d0
# cfgadm -al
<assumed, that you replaced hdd in the same slot that was occupied by the faulty one>
9. Format & place VTOC on this hdd, as it was used by the another in other submirror (or you can save the VTOC output previously to replace the HDD)
Here is the command to increase the soft partition
root@solaris:~ # metattach d51 10gd51: Soft Partition has been grown
After you increase the soft partition, you need to increase the filesystem with growfs
root@solaris:~ # growfs -M /bkp /dev/md/rdsk/d51/dev/md/rdsk/d51: Unable to find Media type. Proceeding with system determined parameters.Warning: 5376 sector(s) in last cylinder unallocated/dev/md/rdsk/d51: 116367360 sectors in 11436 cylinders of 24 tracks, 424 sectors
56820,0MB in 1144 cyl groups (10 c/g, 49,69MB/g, 6016 i/g)super-block backups (for fsck -F ufs -o b=#) at:32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 919760,Initializing cylinder groups:………………….super-block backups for last 10 cylinder groups at:115401920, 115504112, 115606304, 115708496, 115810688, 115912880, 116015072,116117264, 116219456, 116321648
5. what is the different b/w need maintenance and last error in svm
When a slice in a mirror or RAID5 metadevice device experiences errors,DiskSuite puts the slice in the “Maintenance” state. No further reads orwrites are performed to a slice in the “Maintenance” state. Subsequenterrors on other slices in the same metadevice are handled differently,depending on the type of the metadevice.
A mirror may be able to tolerate many slices in the “Maintenance” state and still be read from and written to. A RAID5 metadevice, by definition, can only tolerate a single slice in the “Maintenance” state. When either a mirror or RAID5 metadevice has a slice in the “Last Erred” state, I/O is still attempted to the slice marked “Last Erred”. This is because a “Last Erred” slice contains the last good copy of data from DiskSuite’s point of view.
With a slice in the “Last Erred” state, metadevice behaves like a normaldevice (disk) and returns I/O errors to an application. Usually, at thispoint some data has been lost.Always replace slices in the “Maintenance” state, followed by those in the“Last Erred” state. After a slice is replaced and resynched, use the metastatcommand to verify its state, then validate data to make sure it is good.Here are the specifics for Mirrors and RAID5 devices:1. MirrorsIf slices are in the “Maintenance” state, no data has been lost. You cansafely replace or enable the slices in any order. If a slice is in the “LastErred” state, you cannot replace it until you first replace all the othermirrored slices in the “Maintenance” state. Replacing or enabling a slice inthe “Last Erred” state usually means that some data has been lost. Be sureto validate the data on the mirror after repairing it.2. RAID5 metadevicesA RAID5 metadevice can tolerate a single slice failure. You can safelyreplace a single slice in the “Maintenance” state without losing data. Ifan error on another slice occurs, it is put into the “Last Erred” state. Atthis point, the RAID5 metadevice is a read-only device; you need to performsome type of error recovery so that the state of the RAID5 metadevice isnon-errored and the possibility of data loss is reduced. If a RAID5metadevice reaches a “Last Erred” state, there is a good chance it haslost data. Be sure to validate the data on the RAID5 metadevice afterrepairing it.
AN EXAMPLE
How to remove “maintenance” and “last erred” example, In this point maybe pay attentionin some case The “lost Erred” sub-mirror side have contained “maintenance” and “Okey” state
metareplace d0 c1t0d0s0Size: 8395200 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t0d0s0 0 No Last Erredd20: Submirror of d0State: Needs maintenanceInvoke: metareplace d0 c1t1d0s0Size: 8395200 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t1d0s0 0 No Maintenanced1: MirrorSubmirror 0: d11State: OkaySubmirror 1: d21State: OkayPass: 1Read option: roundrobin (default)Write option: parallel (default)Size: 8395200 blocksd11: Submirror of d1State: OkaySize: 8395200 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t0d0s1 0 No Okayd21: Submirror of d1State: OkaySize: 8395200 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t1d0s1 0 No Okayd4: MirrorSubmirror 0: d14State: Needs maintenanceSubmirror 1: d24State: Needs maintenancePass: 1Read option: roundrobin (default)Write option: parallel (default)Size: 4202688 blocksd14: Submirror of d4State: Needs maintenanceInvoke: after replacing “Maintenance” components:metareplace d4 c1t0d0s4Size: 4202688 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t0d0s4 0 No Last Erredd24: Submirror of d4State: Needs maintenanceInvoke: metareplace d4 c1t1d0s4Size: 4202688 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t1d0s4 0 No Maintenanced5: MirrorSubmirror 0: d15State: OkaySubmirror 1: d25State: OkayPass: 1Read option: roundrobin (default)Write option: parallel (default)Size: 62918208 blocksd15: Submirror of d5State: OkaySize: 62918208 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t0d0s5 0 No Okayd25: Submirror of d5
State: OkaySize: 62918208 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t1d0s5 0 No Okayd6: MirrorSubmirror 0: d16State: Needs maintenanceSubmirror 1: d26State: OkayPass: 1Read option: roundrobin (default)Write option: parallel (default)Size: 52436928 blocksd16: Submirror of d6State: Needs maintenanceInvoke: metareplace d6 c1t0d0s6Size: 52436928 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t0d0s6 0 No Maintenanced26: Submirror of d6State: OkaySize: 52436928 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t1d0s6 0 No Okayd7: MirrorSubmirror 0: d17State: OkaySubmirror 1: d27State: Needs maintenancePass: 1Read option: roundrobin (default)Write option: parallel (default)Size: 6970560 blocksd17: Submirror of d7State: OkaySize: 6970560 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t0d0s7 0 No Okayd27: Submirror of d7State: Needs maintenanceInvoke: metareplace d7 c1t1d0s7Size: 6970560 blocksStripe 0:Device Start Block Dbase State Hot Sparec1t1d0s7 0 No Maintenance-First dettach,delete master slice6 and resync with mirror side slice6,Because in this way the intact data only in mirror side:# metadetach d6 d16# metaclear d16# metainit d16 1 1 c1t0d0s6# metattach d6 d16- Wait for “Okay” status for the master slice6,- Then replace “Last erred” state disk before.Run “metadetach” to detach all the sub-mirrors on the mirror disk fromtheir respective mirrors (see the following):[b]# metadetach -f [/b]NOTE: The “-f” option is not required if the metadevice is in an “okay”state.Then run metaclear to remove the configuration from the disk:[b]# metaclear [/b]# metadb -d c1t1d0s3# luxadm remove_device /dev/rdsk/c1t1d0s2 (physical remove disk when prompt to pull out disk)# devfsadm -C -c disk -v# luxadm insert_device /dev/rdsk/c1t1d0s2 (physical insert disk when prompt to pull in disk)# prtvtoc /dev/rdsk/c1t0d0s2 |fmthard -s – /dev/rdsk/c1t1d0s2# metadb -afc 3 c1t1d0s3Use “metainit” and “metattach” to re-create and attach those submirrors tothe mirrors to start the resync:[b]# metainit 1 1 c#t#d#s#[/b]
[b]# metattach [/b]When all slice resync are finished,Begin replace “Last Erred” master diskRun “metadetach” to detach all the sub-mirrors on the master disk fromtheir respective mirrors (see the following):[b]# metadetach -f [/b]NOTE: The “-f” option is not required if the metadevice is in an “okay”state.Then run metaclear to remove the configuration from the disk:[b]# metaclear [/b]# metadb -d c1t1d0s3# luxadm remove_device /dev/rdsk/c1t0d0s2 (physical remove disk when prompt to pull out disk)# devfsadm -C -c disk -v# luxadm insert_device /dev/rdsk/c1t0d0s2 (physical insert disk when prompt to pull in disk)# prtvtoc /dev/rdsk/c1t1d0s2 |fmthard -s – /dev/rdsk/c1t0d0s2# metadb -afc 3 c1t0d0s3Use “metainit” and “metattach” to re-create and attach those submirrors tothe mirrors to start the resync:[b]# metainit 1 1 c#t#d#s#[/b][b]# metattach [/b]When all slice resync finished,the two sub-mirror is normal.
6. Diff between zones and Ldoms
Solaris Containers, aka zones, are a form of "OS virtualization" which sets up private virtual environments within a single instance of Solaris running on any computer capable of running Solaris 10, including PCs, laptops, and of course, Sun's SPARC, AMD, and Intel-based servers. - Logical Domains are a virtualization technology that lets you have multiple complete Solaris instances on the same T1 SPARC-based "coolthreads" chip multithreading servers, each of which lives in its own virtual machine and can be at different kernel versions. (Each of these Solaris instances can also host multiple containers too)
7. Basic steps to configure Zones.
Step 1 to Solaris Containers - Creating Containers
Doing a demo for Solaris Zone
1. login to a terminal as root
#
2. check the current status of the zones using zoneadm command
# zoneadm list -v
ID NAME STATUS PATH BRAND IP
0 global running / native shared
In the case above, we've a clean system without any non-global zones installed.
3. create a basic zone with IP address 192.168.88.1, using Class C netmask (255.255.255.0)
zonecfg -z tz
tz: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:tz> createzonecfg:tz> set autoboot=true
zonecfg:tz> add net
zonecfg:tz:net> set address=192.168.88.1/24
zonecfg:tz:net> set physical=wpi0
zonecfg:tz:net> end
zonecfg:tz> verify
zonecfg:tz> commit
zonecfg:tz> exit
* Note that in order for autoboot to function, the zone service needs to be enabled. 'svcs' can be used to check the status.
# svcs | grep zones
online 11:33:06 svc:/system/zones:default
The result above shows that the zone service is enabled. If the result is otherwise (disabled), it can be enabled using the 'svcadm' command as below
# svcadm enable svc:/system/zones:default
4. After the 'exit' step, the tz zone is now in 'configured' state.
# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- tz configured /zones/tz native shared
5. The next step is to install the zone. Below is a list of steps:
# zoneadm -z tz install
Preparing to install zone <tz>.
Creating list of files to copy from the global zone.
Copying <7665> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1142> packages on the zone.
Initializing package <143> of <1142>: percent complete: 12%
6. At this state, the state of 'tz' zone is incomplete as can be shown through 'zoneadm' command
# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- tz incomplete /zones/tz native shared
7. Wait till initialize package is done, the status will change to 'installed' as shown below
# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
- tz installed /zones/tz native shared
8. next change the status to 'ready' using (This is like powering the server without booting up)
# zoneadm -z tz ready
9. The command below will connect the 'serial cable' to console
# zlogin -C tz
[Connected to zone 'tz' console]
10. Using another terminal, issue the boot command to the zone (just like powering up the server)
# zoneadm -z tz boot
[NOTICE: Zone booting up]
SunOS Release 5.11 Version snv_75 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: tz
Loading smf(5) service descriptions: 141/141
Reading ZFS config: done.
11. Since this is the first time that this zone is being booted up, some initial configurations needs to be performed.
------------------------START OF SCREEN SHOT-----------------------------
What type of terminal are you using?
1) ANSI Standard CRT
2) DEC VT52
3) DEC VT100
4) Heathkit 19
5) Lear Siegler ADM31
6) PC Console
7) Sun Command Tool
8) Sun Workstation
9) Televideo 910
10) Televideo 925
11) Wyse Model 50
12) X Terminal Emulator (xterms)
13) CDE Terminal Emulator (dtterm)
14) Other
Type the number of your choice and press Return:12
Creating new rsa public/private host key pair
Creating new dsa public/private host key pair
Configuring network interface addresses: wpi0.
─ Host Name for wpi0:1 ─
Enter the host name which identifies this system on the network. The name
must be unique within your domain; creating a duplicate host name will cause
problems on the network after you install Solaris.
A host name must have at least one character; it can contain letters,
digits, and minus signs (-).
Host name for wpi0:1 tz-zone
> Press F2 to go to the next screen.
─ Confirm Information for wpi0:1 ─
> Confirm the following information. If it is correct, press F2;
to change any information, press F4.
Host name: tz-zone
─ Configure Security Policy: ─
Specify Yes if the system will use the Kerberos security mechanism.
Specify No if this system will use standard UNIX security.
Configure Kerberos Security
─────────────────
[ ] Yes
[X] No
─ Confirm Information ─
> Confirm the following information. If it is correct, press F2;
to change any information, press F4.
Configure Kerberos Security: No
─ Name Service ─
On this screen you must provide name service information. Select the name
service that will be used by this system, or None if your system will either
not use a name service at all, or if it will use a name service not listed
here.
> To make a selection, use the arrow keys to highlight the option
and press Return to mark it [X].
Name service
────────────
[X] NIS+
[ ] NIS
[ ] DNS
[ ] LDAP
[ ] None
─ Confirm Information ─
> Confirm the following information. If it is correct, press F2;
to change any information, press F4.
Name service: DNS
─ NFSv4 Domain Name ─
NFS version 4 uses a domain name that is automatically derived from the
system's naming services. The derived domain name is sufficient for most
configurations. In a few cases, mounts that cross domain boundaries might
cause files to appear to be owned by "nobody" due to the lack of a common
domain name.
The current NFSv4 default domain is: ""
NFSv4 Domain Configuration
─────────────────
[X] Use the NFSv4 domain derived by the system
[ ] Specify a different NFSv4 domain
─ Confirm Information for NFSv4 Domain ─
> Confirm the following information. If it is correct, press F2;
to change any information, press F4.
NFSv4 Domain Name: << Value to be derived dynamically >>
─ Time Zone ─
On this screen you must specify your default time zone. You can specify a
time zone in three ways: select one of the continents or oceans from the
list, select other - offset from GMT, or other - specify time zone file.
> To make a selection, use the arrow keys to highlight the option and
press Return to mark it [X].
Continents and Oceans
─────────────
- [ ] Africa
│ [ ] Americas
│ [ ] Antarctica
│ [ ] Arctic Ocean
│ [X] Asia
│ [ ] Atlantic Ocean
│ [ ] Australia
│ [ ] Europe
v [ ] Indian Ocean
─ Country or Region ─
> To make a selection, use the arrow keys to highlight the option and
press Return to mark it [X].
Countries and Regions
─────────────
^ [ ] Macao
│ [ ] Malaysia
│ [ ] Mongolia
│ [ ] Myanmar (Burma)
│ [ ] Nepal
│ [ ] Oman
│ [ ] Pakistan
│ [ ] Palestine
│ [ ] Philippines
│ [ ] Qatar
│ [ ] Russia
│ [ ] Saudi Arabia
v [X] Singapore
─ Confirm Information ─
> Confirm the following information. If it is correct, press F2;
to change any information, press F4.
Time zone: Singapore
─ Root Password ─
Please enter the root password for this system.
The root password may contain alphanumeric and special characters. For
security, the password will not be displayed on the screen as you type it.
> If you do not want a root password, leave both entries blank.
Root password: *******
Root password: *******
System identification is completed.
rebooting system due to change(s) in /etc/default/init
------------------------END OF SCREEN SHOT-----------------------------
12. After the reboot, the root prompt will appear and ready for login
tz-zone console login: root
Password:
Oct 23 13:51:57 tz-zone login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.11 snv_75 October 2007
#
13. Close the session using 'tilde' then 'dot'
tz-zone console login: ~.
[Connection to zone 'tz' console closed]
14. Back to the global zone, use zoneadm to check the current status of the zone
# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
2 tz running /zones/tz native shared
15. use the 'ps' command with zone option to list the running services in the tz zone
17. To shutdown the zone, issue the command (assuming from global zone):
# zlogin tz shutdown -y -i0 -g0
(remember the console terminal you've? Look at that and you'll see the interesting following)
# zlogin -C tz
[Connected to zone 'tz' console]
svc.startd: The system is coming down. Please wait.
svc.startd: 58 system services are now being stopped.
Oct 23 14:13:58 tz-zone syslogd: going down on signal 15
svc.startd: The system is down.
[NOTICE: Zone halted]
That's all for now!
By the way, tz is a shorthand for testzone. =P
8. how to simultaneously updated the patches on all zones.
If a non-global zone is not running when patchadd is run, patchadd will boot the non-global zone into single user mode so that the patchadd will work, and then return the zone to it's original state. The end result is that all zones are patched.
9. what is quorumThe quorum component of Solaris Cluster (SC) is used to guarantee that a cluster does not suffer from partitions, namely split brain and amnesia. Both these types of partitions can lead to data corruption in a cluster,and the quorum component prevents this from happening in an SC config. Split brain is partition in space, where subclusters are up, but not able to talk to each other. Amnesia is partition in time, where a given cluster incarnation is not aware of the previous incarnation.
Quorum uses a voting mechanism in SC to prevent partitions. Each node is assigned a vote, and a cluster needs to have the majority of votes in order to stay up. For a greater-than-two node cluster, it is straightforward to deduce why, with such a voting scheme, one can not encounter either split brain or amnesia in the cluster. See Solaris Cluster Concepts Guide for a detailed discussion of this concept.
For a two node cluster, the voting mechanism requires an external tie-breaking mechanism, which is provided by a quorum device (QD). This is not required for greater-than-two node clusters. However, configuring a QD results in greater availability for the cluster in the event of failures of multiple nodes in a cluster. In fact, if you configure a fully connected (ie. connected to all nodes) QD in an N node cluster, the cluster can survive the failure of (N-1) nodes in the cluster. The lone survivor node will stay up and running, and assuming that the capacity planning for it had ensured that it be able to handle all the load in the system, this node will be able to
service all client requests.
10. how to add the quorum.Quorum devices are nodes and disk devices, so the total quorum will be all nodes and devices added together.You can use the scsetup/ clsetup(3.2) GUI interface to add/remove quorum devices or use the below commands.
Adding a device to the quorum
scconf –a –q globaldev=d11
Note: if you get the error message "uable to scrub device" use scgdevs to add device to the global device namespace.
Removing a device to the quorum scconf –r –q globaldev=d11
Remove the last quorum device
Evacuate all nodes
put cluster into maint mode #scconf –c –q installmode
remove the quorum device#scconf –r –q globaldev=d11
check the quorum devices#scstat –q
Resetting quorum infoscconf –c –q reset
Note: this will bring all offline quorum devices online
Bring a quorum device into maintenance mode
obtain the device number#scdidadm –L #scconf –c –q globaldev=<device>,maintstate
Bring a quorum device out of maintenance mode
scconf –c –q globaldev=<device><device>,reset
11. diff b/w UFS and ZFS
ZFS vs. UFS
ZFS is a combined file system and logical volume manager. It includes support for high storage capacities, integration of concepts of file systems and volume management, snapshots and copy on write clones (that is, an optimization strategy that allows callers who ask for resources that are indistinguishable to be given pointers to the same resource), continuous integrity checking and automatic repair, RAID -Z, and native NFSv4 ACLs. It is an open source software that is licensed under the Common Development and Distribution License (or CDDL).
. The storage pool of ZFS is known as a zpool. It is constructed of virtual devices (or vdevs) which are constructed of block devices – files, hard drive partitions or entire drives (recommended). As such, vdevs are often times considered to be a group of hard drives. A ZFS capacity is rather large in comparison to standard file systems. It is a 128 bit file system, enabling it to address 18 quintillion times more data than 64 bit systems. The limitations found in ZFS are designed specifically to be large enough to never be encountered
The Unix File System (also known as UFS) is a file system used exclusively with Unix, and all Unix-like operation systems. It has been known as the Berkeley Fast File System, and is a removed descendant of the original file system used in Version 7 Unix.
12. how many partition can be created in UFS13. how many partitin can be created in ZFS14. what is smf and advantage of smf.In the most general sense, SMF services provide capabilities to applications and other services, both localand remote. In the Solaris 10 OS, most system services — such as network services (ftp, telnet, rlogin,etc.), file system services, security services, device services, print services, cron services, and so forth —are implemented as SMF services. Besides typical UNIX® system services, the SMF managementframework is designed to support third-party software application services, including web services anddatabase services (such as starting an Oracle® database daemon)SMF offers many advantages, including:• Simplified service administration. Services are objects that can be viewed and easily managed with afew simple administrative commands.• Automated restart of failed services. SMF monitors service processes, and can proactively restart aservice when it detects an administrative error, hardware fault, or service death.• Persistent service configuration. Service definitions and configurations persist across reboots, even afterinstalling OS upgrades or patches.• Explicit dependencies. Relationships are defined between services to reflect that some services rely on
the availability of other services.• Easier debugging. Individual service log files make it easier to determine why a service isn't running.• Faster boot/shutdown processes. SMF parallelizes the start/stop of services when possible.• Delegated service administration. Administrators can securely delegate service-related tasks to non-rootusers, including the ability to configure, start, stop, or restart services.
15. how to assign user password expiry
There are two ways to force a user to change passwords the next time the user logs in:Force change keeping password aging rules in effect passwd -f username * Force change and turn off password aging rules passwd -x 0 username Setting a Password Age Limit The *-max* argument to the passwd command sets an age limit for the current password. In other words, it specifies the number of days that a password remains valid. After that number of days, a new password must be chosen by the user. Once the maximum number of days have passed, the next time the user tries to login with the old password a Your password has been expired for too long message is displayed and the user is forced to choose a new password in order to finish logging in to the system. The max argument uses the following format: passwd -x max username Where: - **username is the login ID of the user - **max is one of the following values: - ***Greater than zero*. Any number greater than zero sets that number of days before the password must be changed. - ***Zero (0)*. A value of zero (0) forces the user to change passwords the next time the user logs in, and it then turns off password aging. - ***Minus one (-1*). A value of minus one (-1) turns off password aging. In other words, entering *passwd -x -1* username cancels any previous password aging applied to that user. Setting Minimum Password Life The min argument to the passwd command specifies the number of days that must pass before a user can change passwords. If a user tries to change passwords before the minimum number of days has passed, a Sorry less than N days since the last change message is displayed. The min argument uses the following format: passwd -x max -n min username
Where: - **username is the login ID of the user - **max is the maximum number of days a password is valid as described in the section above - **min is the minimum number of days that must pass before the password can be changed. The following rules apply to the min argument: - **You do not have to use a min argument or specify a minimum number of days before a password can be changed. - **If you do use the min argument, it must always be used in conjunction with the *-max* argument. In other words, in order to set a minimum value you must also set a maximum value. - **If you set min to be greater than max, the user is unable to change passwords at all. For example, the command passwd -x 7 -n 8 prevents the user from changing passwords. If the user tries to change passwords, the You may not change this password message is displayed. Setting the min value greater than the max value has two effects:
- **The user is unable to change password. In this case, only someone with administer privileges could change the password. For example, in situations where multiple users share a common group password, setting the min value for that password greater than the max value would prevent any individual user from changing the group password. - **The password is only valid for the length of time set by the maxvalue, but the user cannot change it because the min value is greater than the max value. Thus, there is no way for the user to prevent the password from becoming invalid at the expiration of the max time period. In effect, this prevents the user from logging in after the max time period unless an administrator intervenes. Establishing a Warning Period The warn argument to the passwd command specifies the number of days before a password reaches its age limit that users will start to seeing a Your password will expire in N days message (where N is the number of days) when they log in. For example, if a user's password has a maximum life of 30 days (set with the *-max* argument) and the warn value is set to 7 days, when the user logs in on the 24th day (one day past the warn value) the warning message Your password will expire in 7 days is displayed. When the user logs in on the 25th day the warning message Your password will expire in 6 days is displayed. Keep in mind that the warning message is not sent by Email or displayed in a user's console window. It is displayed only when the user logs in. If the user does not log in during this period, no warning message is given. Keep in mind that the warn value is *relative* to the max value. In other words, it is figured backwards from the deadline set by the max value. Thus, if the warn value is set to 14 days, the Your password will expire in N daysmessage will begin to be displayed two weeks before the password reaches its age limit and must be changed. Because the warn value is figured relative to the max value, it only works if a max value is in place. If there is no max value, warn values are meaningless and are ignored by the system. The warn argument uses the following format: passwd -x max -w warn username
Where: - **username is the login ID of the user. - ***max* is the maximum number of days a password is valid as described on Setting a Password Age . - **warn is the number of days before the password reaches its age limit that the warning message will begin to be displayed. The following rules apply to the warn argument: - **You do not have to use the warn argument or specify a warning message. If no warn value is set, no warning message is displayed prior to a password reaching its age limit. - **If you do use the warn argument, it must always be used in conjunction with the max argument. In other words, in order to set a warning value you must also set a maximum value. Turning Off Password Aging There are two ways to turn off password aging for a given user: Turn off aging while allowing user to retain current password passwd -x -1 username
Force user to change password at next login, and then turn off aging
16. what is ipmp? how many interface need to configure ipmp, is their need for same
IP Multipathing (IPMP) in Sun Solaris enables the load balancing capabilities and resilience for Network connections with multple Network Interface Cards (NIC).
I discussed here about providing resilience for network connections with multiple NICs on the system. Now, we take it to the next step and make the network connections not only resilient but also load balance the network connections such that both the NICs participating in IPMP are active and forwards traffic. This improves the network throughput and thereby efficiency of the server especially if it is a critical system serving multiple connections.To configure IPMP for load balancing we need to have
1. Two Virtual IP Addresses. These IPs are used by the Applications for data.
2. Test IP Address for each NIC. These IPs are not used by applications and are only used to prode a remote target device to check connectivity.
3. Each Interface has unique MAC-Address. By default in SPARC platforms, all NICs have a System-wide MAC-Address assigned and so they share a single MAC-Address. To change this behaviour click here
The NICs doesn’t have to be of the same kind but have to be of the same speed (10/100/1000Mbps).
In our configuration,
192.168.1.99 – Virtual IP1
192.168.1.100 – Virtual IP2
192.168.1.101 – Test IP for ce0 (NIC1)
192.168.1.102 – Test IP for ce1 (NIC2)
appserver – Actual hostname
appserver-1 – Hostname for Data IP2
appserver-2 – Hostname for Data IP2
appserver-ce0 – Hostname for test IP on ce0 interface
appserver-ce1 – Hostname for test IP on ce1 interface
Add Host Entries in /etc/hosts
Let’s start with adding the hosts entries for the IP addresses in the /etc/hosts file.
We have configured a hostname for each of the Virtual IPs and the Test IPs. However, the Test IPs should not be used by applications for any network connections.
Create hostname.ce* files
For every interface on the system create a hostname.ce* file. For us, create the files
hostname.ce0 & hostname.ce1
Edit hostname.ce0
Add the following on the hostname.ce0 file. This is the primary or master interface of the IPMP Pair
appserver-ce0 netmask + broadcast + group appserver-ipmp deprecated -failover up \addif appserver netmask + broadcast + failover up
Edit hostname.ce1
Add the following on the hostname.ce1 file. This is the secondary or slave interface of the IPMP Pair
appserver-ce1 netmask + broadcast + group appserver-ipmp deprecated -failover up \addif appserver netmask + broadcast + failover up
wherenetmask – assigns the default netmask
broadcast – assigns the default broadcast value
group – specifies the IPMP group
deprecated – indicate test Interface not be used for data transfer
-failover – makes the test interface not to failover
Now, the configuration is complete and an ifconfig output should look like as follows:
root@ appserver:/$lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1inet 127.0.0.1 netmask ff000000ce0: flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 2inet 192.168.1.99 netmask ffffff00 broadcast 192.168.1.255groupname appserver-ipmpether 0:xx:xx:xx:xx:xce0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2inet 192.168.1.101 netmask ffffff00 broadcast 192.168.1.255ce1: flags=69040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4,NOFAILOVER> mtu 1500 index 3inet 192.168.1.100 netmask ffffff00 broadcast 192.168.1.255groupname appserver-ipmpether 0:xx:xx:xx:xx:xce1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
Now, both the NICs will forward traffic and when one of the inerface fails, it transparently failover the virtual IP address onto the other active interface and you can see an interface “ce1:2″ would be created for the failed over IP. When the link is restored, this will be failed back to the ce0 interface. There should be no disruption to the network connections.interface name or diff
17. features of XSCF and which model can support xscf.18How to check cpu utilization. 19.How to initialize a new disk in veritas. 20.How to start/stop a volume in veritas. 22How to add kernal patch in system if svm is running. 23.How to create metadevice on second disk and attach them with main mirror device in svm. 24.How to detach metadevices. 25.What are daemon of jumpstart. 26How to assign root previlieg to a perticular user other than RBAC. 27.What is the diff b/w ufs and vxfs. 28.How to check multipathing in solaris 10. 29.How to check o/s fatal error or reason of system crash. 30.How to take system console without ALOM , ELOM.
31.What are main files of RBAC. 32.How to assign RBAC to a user. 33.How to make a perticular availabei Fs from one node to another node in cluster
34,Full syntax for increase volume
35.What is the procedure for creating volumes in vxvm 36,How to manage cluster SG in vcs 37, What are the different type of backup
![1 $SU VW (G +LWDFKL +HDOWKFDUH %XVLQHVV 8QLW 1 X ñ 1 … · 2020. 5. 26. · 1 1 1 1 1 x 1 1 , x _ y ] 1 1 1 1 1 1 ¢ 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1](https://static.documents.pub/doc/80x56/5fbfc0fcc822f24c4706936b/1-su-vw-g-lwdfkl-hdowkfduh-xvlqhvv-8qlw-1-x-1-2020-5-26-1-1-1-1-1-x.jpg)
![1 1 1 1 1 1 1 ¢ 1 , ¢ 1 1 1 , 1 1 1 1 ¡ 1 1 1 1 · 1 1 1 1 1 ] ð 1 1 w ï 1 x v w ^ 1 1 x w [ ^ \ w _ [ 1. 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 ð 1 ] û w ü](https://static.documents.pub/doc/80x56/5f40ff1754b8c6159c151d05/1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-w-1-x-v.jpg)
![[XLS] · Web view1 1 1 2 3 1 1 2 2 1 1 1 1 1 1 2 1 1 1 1 1 1 2 1 1 1 1 2 2 3 5 1 1 1 1 34 1 1 1 1 1 1 1 1 1 1 240 2 1 1 1 1 1 2 1 3 1 1 2 1 2 5 1 1 1 1 8 1 1 2 1 1 1 1 2 2 1 1 1 1](https://static.documents.pub/doc/80x56/5ad1d2817f8b9a05208bfb6d/xls-view1-1-1-2-3-1-1-2-2-1-1-1-1-1-1-2-1-1-1-1-1-1-2-1-1-1-1-2-2-3-5-1-1-1-1.jpg)
![1 1 1 1 1 1 1 ¢ 1 1 1 - pdfs.semanticscholar.org€¦ · 1 1 1 [ v . ] v 1 1 ¢ 1 1 1 1 ý y þ ï 1 1 1 ð 1 1 1 1 1 x ...](https://static.documents.pub/doc/80x56/5f7bc722cb31ab243d422a20/1-1-1-1-1-1-1-1-1-1-pdfs-1-1-1-v-v-1-1-1-1-1-1-y-1-1-1-.jpg)
