Home > Articles

This chapter is from the book

25.6 Testing Critical Hardware before Setting Up a Cluster

Let's start by looking at some "tips and tricks" of setting up our key hardware components. We'll begin with disk drives:

  • Disk Drives: There are two scenarios I want to consider here:

    - Using VxVM disks: When using VxVM disks, we should give each disk an easily identifiable Disk Media name. In this way, when we deport/import disk groups, we can identify disks easily; remember, it is possible that device file names will not be consistent across machines in the cluster, so Disk Media Names will be the identifier in this case.

    - Using LVM disks: Using LVM disks poses its own problems. The identifier for an LVM disk is the device file. We need to know the device file name to be able to import the volume group into all nodes in the cluster. Here's what I do:

    1. - Set up the volume group on one node in the cluster. This includes all logical volumes and filesystems. Create all the mount points necessary.

    2. - Load all data/files into the appropriate filesystems and logical volumes.

    3. - Do not update the file /etc/fstab.

    4. - Test that you can see and access all data/files appropriately.

    5. - Create a map file (in preview mode) from the active volume group. Here is an example of the error message you will see:

      root@hpeos001[] # vgexport –p –m /tmp/vg01.map /dev/vg01
                           vgexport: Volume group "/dev/vg01" is still active.
                           root@hpeos001[] # cat /tmp/vg01.map
                           1 db
                           2 progs
                           root@hpeos001[] #
                           

      This is not really an error; it's LVM just telling you that the volume group is still active. You will notice from the output above that the important part of this step is that the map file is created.

      Something else to notice is that I haven't used the "-s" option to vgexport; this would write the concatenated "CPU-ID+VG-ID" into the map file. This seems like a good idea, but in my experience using this in a large configuration just causes you slight problems later on as we see.

    6. - You can now distribute the map file to all nodes in the cluster in preparation for using vgimport to import the relevant disks into the volume group.

    7. - The next problem is the fact that device files may be different on different nodes. The biggest problem is the Instance number of the interface the disk is connected to. Some administrators spend lots of time and effort to make the Instance numbers of all corresponding devices on a machine the same. That's fine by me if you want to take that route; see how we do it in Chapter 4, "Advanced Peripheral Configuration" (Rebuilding the ioinit File to Suit Your Needs). If you aren't going to spend all your time doing that, then you need to identify which disks are connected to which interfaces. You will need to work this out for all nodes in the cluster. See the example in Figure 25-2.

      25fig02.jpgFigure 25-2 Identifying shared disks.

      What we have is a single disk, dual-pathed from two hosts. In systems with lots of disks and multiple paths, e.g., through a SAN, you may have four paths per disk and possibly hundreds of disks. This example goes to show how you would identify which paths are "related" to a particular disk. Just looking at the device files will not show you much. Using a command like diskinfo won't yield much information either. We need to go back to our understanding of the layout of an LVM disk. At the beginning of a disk, we have the 8KB header used to point to the boot area. We then have the PVRA. The first element of the PVRA is an LVM Record, which identifies this disk as an LVM disk. The LVM Record is 8 bytes in size. So take 8KB + 8 bytes = 8200 (2008 in hex) bytes. If we read from that location, we find four interesting numbers in the PVRA; the CPU-ID, the PV-ID, the CPU-ID (again) and the VG-ID. If we were to read this information from any of the device files, we should see exactly the same information. I would use the following command to do this:

      # echo "0x2008?4X" | adb /dev/dsk/cXtYdZ
      

      adb moves to the prescribed address and prints four integers; in my case, I display them in hex (the reason for using hex will become apparent). In fact, if you look at the output below, I have run just that command on my first node, hpeos001:

      root@hpeos001[] # echo "0x2008?4X" | adb /dev/dsk/c12t0d1
                           2008: 77A22A2C 3C9DFCD9   77A22A2C   3C9DFCD6
                           root@hpeos001[] # echo "0x2008?4X" | adb /dev/dsk/c13t0d1
                           2008: 77A22A2C 3C9DFCD9   77A22A2C   3C9DFCD6
                           

      If we look at the output from the commands run from the other node, hpeos002, the output should be the same.

      root@hpeos001[] # echo "0x2008?4X" | adb /dev/dsk/c9t0d1
                           2008: 77A22A2C 3C9DFCD9   77A22A2C  3C9DFCD6
                           root@hpeos001[] # echo "0x2008?4X" | adb /dev/dsk/c10t0d1
                           2008: 77A22A2C 3C9DFCD9   77A22A2C  3C9DFCD6
                           

      Theses are the two nodes as shown in Figure 25-2. As you can see, the relevant fields match up regardless of which device file we look at. In a large, complex environment, this can help you visualize which device files are "related" to which disks.

    8. - We can use vgimport to get the relevant disks into the relevant volume groups using the map file we distributed earlier.

      # mkdir /dev/vg01
      # mknod /dev/vg01/group c 64 0x010000
      # vgimport /dev/vg01 /dev/dsk/c9t0d1 /dev/dsk/c10t0d1
      # vgchange –a y /dev/vg01
      # vgcfgbackup /dev/vg01
      # vgchange –a n /dev/vg01
      

      I want to say just a word regarding the "-s" option to vgexport/vgimport. I mentioned earlier that in my experience using this option would cause you slight problems. Here are the reasons why:

      1. - You are going to have to document the layout of your disks anyway, so why not do it now?

      2. - When we use the "-s" option with vgimport, vgimport must scan every disk on the system looking for matching CPU-ID+VG-ID values for corresponding disks. When you have lots of disks, this can take many seconds. In fact, on some systems I have seen it take many minutes. While it is inquiring of all those disks, you are interrupting other important data related IO.

      3. - Conclusion: Get to know your hardware; it makes sense in the long run.

    9. - It might be advisable to start to draw some form of diagram so that you know how your disks map to the device files. Documentation will certainly help later, as well as in any Disaster Recovery scenario.

  • LAN cards

    The important thing to remember here is the importance of having a bridged network between your "active" LAN cards and your "standby" LAN cards. Before embarking on creating a cluster, you must ensure that you can linkloop from and to each LAN card in your bridged network. If not, Serviceguard will not allow you to proceed. It's a relatively simple process as long as you are confident in how your network has been physically constructed. Let's look at a simple example shown in Figure 25-3.

    25fig03.jpgFigure 25-3 A bridged network.

    We can see from Figure 25-3 that we have eliminated all the SPOFs for the Cluster Network. Now we need to check that our switch/hub/bridge has no filtering or blocking configured on the ports that we are using. If we are using two links between the switches, as shown, it may be a good idea to disconnect one link, perform the tests, swap the links over, and perform the tests again. It is not important which node you perform the test from because if one component is not working, it will show up. Some administrators perform the tests from both nodes "just to be sure." I don't mind that as a philosophy. I perform the tests on one node, and let you perform the tests on both of your nodes. Note that I am sending packets out of both interfaces and to both interfaces; so in our example, that means four linkloop tests. Below, I am performing the tests on two nodes configured similarly to the nodes in Figure 25-3.

    root@hpeos001[] # lanscan
             Hardware Station        Crd Hdw   Net-Interface  NM  MAC     HP-DLPI DLPI
             Path     Address        In# State NamePPA        ID  Type    Support Mgr#
             8/16/6   0x080009BA841B 0   UP    lan0 snap0     1   ETHER   Yes     119
             8/20/5/2 0x0800093D4C50 1   UP    lan1 snap1     2   ETHER   Yes     119
             root@hpeos001[] # linkloop –i 0 0x080009C269C6
             Link connectivity to LAN station: 0x080009C269C6
             -- OK
             root@hpeos001[] # linkloop –i 0 0x080009E419BF
             Link connectivity to LAN station: 0x080009E419BF
             -- OK
             root@hpeos001[] # linkloop –i 1 0x080009C269C6
             Link connectivity to LAN station: 0x080009C269C6
             -- OK
             root@hpeos001[] # linkloop –i 1 0x080009E419BF
             Link connectivity to LAN station: 0x080009E419BF
             -- OK
             

I am going to assume that you have worked out all the SPOFs we talked about earlier and that you are happy with your current IT processes, system performance, user access, and security issues. I am also going to assume that all nodes in the cluster are listed in your host lookup database.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020