Before going to the basic understanding of the disksets let us first know the necessity for disksets in solaris there are many prime reasons people prefer for going into disksets

1. Availability
2. Redundancy
3. Efficiency

Availability: Disksets are more reliable under sun cluster environment but not limited to HA they are even highly available out of the HA concept as well (Fail over Configuration)

Redundancy: Always a first and foremost term when it comes to disk management .this can be achieved via disksets with RAID being built over the disks from the disksets

Efficiency:  This can be spoken in two terms  on the aspect of system administration ,with help of disksets we can efficiently organize the metadevices under diskgroups   ,reuse the same metadevices on the different host(metaimport) , same diskset could be reused on another node via metaimport ,provided if the disk are externally connected (storage).This sometimes happens in cases like if the RAIDs are needed to be maintained and used on a diifernt system in other words if we want to use the same LUNS on other system . So far, I have not tried but will be doing this very soon, we will share the same as soon as possible  on gurkulindia

Requirement:

If availability comes as a first choice as a sys admin then the prime requirement for an disksets to be created under solaris volume manager is this ,The disk used should be visible on two hosts with the same device number and the shared disk should always use the same device driver by this is not applicable when the disksets are not multiowned by the hosts Full Story

The idea behind running BIND in a chroot jail is to limit the amount of access any malicious individual could gain by exploiting vulnerabilities in BIND. It is for the same reason that we run BIND as a non-root user. This should be considered as a supplement to the normal security precautions (running the latest version, using access control, etc.), certainly not as a replacement for them. Full Story

The non-global zones (or zones) facility in Solaris[TM] provides an isolated environment for running applications. The zones FAQ can be found at OpenSolaris.org.

Symptoms:

Full Story

• Solaris 10 Troubleshooting : Check the Integrity of libraries and critical files                11078 Reads
• VxVM : Resolving the Intermittent Disk errors by clearing the failing flag on a disk         5643 Reads
• Cloud Computing – What does it mean to System Administrators                                  3924 Reads
• Beginners Lesson – Veritas Cluster Services for System Admin                                     3473 Reads
• The one thing you must understand for better System Administration – SCSI                 2835 Reads
• Beginner’s Lesson – VERITAS Volume Manager for Solaris                                           2751 Reads
• Configuring Solaris 10 host with SAN storage ( EMC Clariion )                                      2134 Reads
• ORACLE-SUN Hardware Reference                                                                            2060 Reads
• Solaris Troubleshooting: CDE login problems                                                             2014 Reads
• EMC Power Path commands for system administrators                                               1954 Reads
  

When we trying to use a particular RPC  program, below may indicate that rpcbind is not running or the program is not registered with rpcbind.

Error “RPC: Program not registered”

Full Story

You might have already read my old post, 7 social engineering tips that new system admins should know in new team ,where I have discussed the social engineering points that helps you to quickly sync with the new team. And this post is the continuation post for the same topic, and I will be discussing the technical aspects that every system admin should know during his initial phase in his new job. And these rules are same for every one, irrespective of experience that he/she has in the old organization.

Before going to actual topic I would like to highlight one important point: whenever we work for any organization for long time we feel that we are comfortable with the job, and most of the times we will assume that it is our technical skill that is making us comfortable in our existing job but the actual fact is ” it is not our technical skill alone that makes us comfortable, it is our historical knowledge about the current environment added to our technical skill which makes us more comfortable with the current job”.

In simple terms, if you assume your technical skill as “1″ then every piece of information that you know about the history of the environment will add a “0 ( zero)” next to the “1″ and having more ’0′s next ’1′ will improve your value in the job. Whenever you join to a new job, you will be carrying only the “1″ with you from old job to new job and the rest of the “0″s you have to re-gain from the new job. So, during initial stage of new job keep your focus to understand the historical information about current environment , from the existing team, whenever you get a chance to discuss about it.

Full Story