OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: IT Resource Center (support_feedbackus-support.external.hp.com)
Date: Wed Feb 21 2001 - 08:02:50 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

                            HP Support Information Digests

    ===============================================================================
    o IT Resource Center World Wide Web Service
       ---------------------------------------------------

       If you subscribed through the IT Resource Center and would
       like to be REMOVED from this mailing list, access the
       IT Resource Center on the World Wide Web at:

         http://www.itresourcecenter.hp.com/

       Login using your IT Resource Center User ID and Password.
       Then select Support Information Digests (located under
       Maintenance and Support). You may then unsubscribe from the
       appropriate digest.
    ===============================================================================


    Digest Name: monthly HP-UX technical tips digest
        Created: Wed Feb 21 3:10:03 PST 2001

    Table of Contents:

    Document ID Title
    --------------- -----------
    3100521365 SYS ADM: swacl(1M) indicates a different realm and host than t
    1100399055 SYS ADM: receiving srvrflash error message at boot time

    The documents are listed below.
    -------------------------------------------------------------------------------


    Document ID: 3100521365
    Date Loaded: 20010215
          Title: SYS ADM: swacl(1M) indicates a different realm and host than the true hostname

    PROBLEM

    Attempts to install patches on an HPUX 10.20 computer failed. Upon
    reboot, the following error occurred during "swconfig \*":

         "you do not have the right permissions to install on this target"

    This computer is a member of an MC/ServiceGuard cluster, but it did
    not rejoin the cluster.

    The swacl(1M) command indicates that the realm and root user hostname
    is not the name of this host. Here is an example:

         # swacl -l root
         #
         # swacl Installed Software Access Control List
         #
         # For host: luke:/
         #
         # Date: Wed Jan 17 14:31:39 2001
         #
         # Object Ownership: User= root
         # Group=sys
         # Realm=luke.test.hp.com
         #
         # default_realm=luke.test.hp.com
         object_owner:crwit
         group:swadm:crwit
         any_other:-r--t

    The "swacl -l host" command returns the same information as follows:

         # swacl -l host
         #
         # swacl Host Access Control List
         #
         # For host: luke
         #
         # Date: Wed Jan 17 14:32:18 2001
         #
         # Object Ownership: User= root
         # Group=sys
         # Realm=luke.test.hp.com
         #
         # default_realm=luke.test.hp.com
         group:swadm:crwit
         any_other:-r--t

    However, the true hostname is "han".

         # uname -n
         han

         NOTE: The name services files confirm the result from uname(1)
                and nslookup(1).

    How can this situation be corrected?

    CONFIGURATION

    Operating System - HP-UX
    Version - 10.20
    Hardware System - 9000
    Series - K370
    Subsystem - Software Distributor (SD-UX)

    RESOLUTION

    The acl files have the wrong host listed in them:

         # grep luke /var/adm/sw/security/*
         /var/adm/sw/security/_ACL:# default_realm=luke
         /var/adm/sw/security/_OWNER:# default_realm=luke
         /var/adm/sw/security/_PROD_DFLT_ACL:# default_realm=luke
         /var/adm/sw/security/_SOC_DFLT_ACL:# default_realm=luke

    To correct this situation, do the following steps:

         1. Edit the contents of each _<file> to match the desired hostname.

         2. Restart swagentd after fixing the _ACL file for hosts.

                  # swagentd -r

         3. Use the swacl(1M) command to modify the host entries.
             For example:

                  # swacl -l host -M user:rootluke.test.hp.com:crwit
                  entry_type:[ key ]:permissions

             NOTE: To remove an entry, use the -D option as follows:

                  # swacl -l host -D user:roothan.test.hp.com

             NOTE: Log out and log back in, or reboot the system, prior
                    to running the "swacl -l root" command.

    <!-- ALT KEYWORDS -->
    -----End of Document ID: 3100521365------------------------------------------


    Document ID: 1100399055
    Date Loaded: 20010215
          Title: SYS ADM: receiving srvrflash error message at boot time

    PROBLEM

    The following error message occurs at boot time:

          ISL booting hpux srvrflash

          Boot
          : disk(0/4/0/0.2.25.0.7.0.0;0)srvrflash
          disk(0/4/0/0.2.25.0.7.0.0;0)srvrflash: cannot open, or not executable
          Exec failed: No such file or directory

    However, the system does boot up.

    How can this message be removed?

    CONFIGURATION

    Operating System - HP-UX
    Version - 11.0
    Hardware System - N4000-55

    RESOLUTION

    This problem is known to occur after installing the PDC reflash patch,
    PHSS_21679. Typically, it occurs on mirrored disk systems.

    The firmware patches assume that the first disk entry of the
    /stand/bootconf file is the primary boot disk. The patches modify the
    autoboot file in the lif area on this disk such that the firmware flash
    utility is executed upon the next reboot.

    In some instances, the first disk entry in the /stand/bootconf file is
    not the primary boot disk but is the secondary mirror boot disk instead.
    So, the patch installation modifies the autoboot file on the mirror disk,
    not the primary disk. As a result, the system firmware was never updated.

    To verify this, please inspect a copy of the /stand/bootconf file from
    the system in question. The output of setboot(1M) and 'ioscan -fun' is
    also helpful. With these pieces of information, the device file for the
    primary boot disk can be determined.

    Also, it may be helpful to obtain the current version of the firmware via
    cstm (Command-Line Support Tool Manager). If it is not 40.26, it further
    verifies that the srvrflash utility was never executed. If it is 40.26,
    that does not mean that the srvrflash did execute, because this firmware
    could already have been present.

    To recover from this situation, the following steps can be used:

         1. Modify the /stand/bootconf file so that the first
             disk entry points to the primary boot disk. Here is
             one way to accomplish this task:

             A. Obtain the current autoboot file from the boot disk.
                 For example, given c6t0d0, enter the following command:

                      # lifcp /dev/rdsk/c6t0d0:AUTO /tmp/auto

             B. Examine the file /tmp/auto; it should contain two lines
                 similar to:

                      srvrflash ...
                      hpux

             C. Restore the original autoboot file based on the second line
                 shown in the file /tmp/auto above. Example:

                      # mkboot -a "hpux" /dev/rdsk/c6t0d0

                 If the second line in the file /tmp/auto is different from
                 "hpux", then copy the second line to the string included in the
                 mkboot(1M) command. For example:

                      # mkboot -a "blabla" /dev/rdsk/c6t0d0

         2. Reinstall [PHSS_21696/PACHRDME/English] with the
             'reinstall=true' option, for example:

             # swinstall -s /tmp/PHSS_21696.depot -x autoreboot=true \
                         -x reinstall=true -x patch_match_target=true

             Note: It is not necessary to remove PHSS_21696
                    prior to reinstalling it.

    <!-- ALT KEYWORDS -->
    -----End of Document ID: 1100399055------------------------------------------