Solaris 10
Solaris 10 system was not starting up after abnormal system shutdown. It was always asking for root password for system maintainance. This is because, the boot archive may become out of sync with the root filesystem.
Sol: run "svcadm clear system/boot-archive". This will clear the boot archive service state and bring up the system.
Service Management Facility (SMF)
svcs – detailed state information about all service instances
svcadm – common service management tasks (enable, disable, ...)
svccfg – manipulate the SMF repository
svcprop – view SMF repository data
inetadm – view and configure inetd managed services
inetconv – convert an inetd.conf(4) to an SMF manifest
svcs -l ssh fmri svc:/network/ssh:default name SSH server enabled true state online next_state none state_time Wed Aug 08 00:04:31 2007 logfile /var/svc/log/network-ssh:default.log restarter svc:/system/svc/restarter:default contract_id 58 dependency require_all/none svc:/system/filesystem/local (online) dependency optional_all/none svc:/system/filesystem/autofs (online) dependency require_all/none svc:/network/loopback (online) dependency require_all/none svc:/network/physical (online) dependency require_all/none svc:/system/cryptosvc (online) dependency require_all/none svc:/system/utmp (online) dependency require_all/restart file://localhost/etc/ssh/sshd_config (online)
To enable a service
# svcadm enable network/login:rlogin # svcs -l network/login:rlogin fmri svc:/network/login:rlogin name The remote login service. enabled true state online next_state none restarter svc:/network/inetd:default
- Use svcadm enable -r to enable a service plus all of its dependents
To restart a service
# svcadm restart nfs/server
To re-read the configuration file
# svcadm refresh nfs/server
To disable telnet
# svcadm disable telnet
To display the service which are enables but not runnig or preventing another enabled service from running
# svcs -xv
ZFS (Zettabyte File System)
ZFS can be administered using Java Web console by using
https://hostname:6789/zfs
If you type the appropriate URLand are unable to reach the ZFS Administration console, the server might not be started. To start the server, run the following command:
# /usr/sbin/smcwebserver start
If you want the server to run automatically when the system boots, run the following command:
# /usr/sbin/smcwebserver enable
zpool --> To manage ZFS pool
zfs --> To mamage the ZFS file systems
Create a ZFS pool called mypoo1-1 consisting of two mirrored drives
# zpool create mypool-1 mirror c1t1d0s1 c1t1d0s0 df -h -F zfs Filesystem size used avail capacity Mounted on mypool-1 3.5G 24K 3.5G 1% /mypool-1
To destroy a ZFS File system
# zfs list NAME USED AVAIL REFER MOUNTPOINT tank 1.15T 395G 24.5K /tank tank/JRP 1.15T 395G 1.15T /oracle/JRP_SAN # zfs destroy tank/JRP
To destroy the pool tank
# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT tank 1.56T 7.12M 1.56T 0% ONLINE - # zpool list no pools available
Change a mount point
# zfs set mountpoint=/jeeva mypool-1
Zones
The Solaris Zones partitioning technology is used to virtualize operating system services and provide an isolated and secure environment for running applications. A zone is a virtualized operating system environment created within a single instance of the Solaris Operating System. When you create a zone, you produce an application execution environment in which processes are isolated from the rest of the system. This isolation prevents processes that are running in one zone from monitoring or affecting processes that are running in other zones. Even a process running with superuser credentials cannot view or affect activity in other zones.
Each zone that requires network connectivity has one or more dedicated IP addresses. A process assigned to a zone can manipulate, monitor, and directly communicate with other processes that are assigned to the same zone. The process cannot perform these functions with processes that are assigned to other zones in the system or with processes that are not assigned to a zone.
Each zone also has a node name that is completely independent of the zone name. The node name is assigned by the administrator of the zone. Each zone has a path to its root directory that is relative to the global zone's root directory.
Every Solaris system contains a global zone.
Global Zone
- The global zone always has the name global and assigned ID 0 by the system
- Provides the single instance of the Solaris kernel that is bootable and running on the system
- Contains a complete installation of the Solaris system software packages
- Can contain additional software packages or additional software, directories, files, and other data not installed through packages
- Provides a complete and consistent product database that contains information about all software components installed in the global zone
- Holds configuration information specific to the global zone only, such as the global zone host name and file system table
- Is the only zone that is aware of all devices and all file systems
- Is the only zone with knowledge of non-global zone existence and configuration
- Is the only zone from which a non-global zone can be configured, installed, managed, or uninstalled
Non-Global Zone
- Is assigned a zone ID by the system when the zone is booted
- Shares operation under the Solaris kernel booted from the global zone
- Contains an installed subset of the complete Solaris Operating System software packages
- Contains Solaris software packages shared from the global zone
- Can contain additional installed software packages not shared from the global zone
- Can contain additional software, directories, files, and other data created on the non-global zone that are not installed through packages or shared from the global zone
- Has a complete and consistent product database that contains information about all software components installed on the zone, whether present on the non-global zone or shared read-only from the global zone
- Is not aware of the existence of any other zones
- Cannot install, manage, or uninstall other zones, including itself
- Has configuration information specific to that non-global zone only, such as the non-global zone host name and file system table
To identify the multipathing support
# mpathadm list mpath-support mpath-support: libmpscsi_vhci.so