HP-UX GUID Manager V1.0 Administrator Guide HP Part Number: 5900-2008a Published: March 2012 Edition: 1.
© Copyright 2012 Hewlett-Packard Development Company, L.P Legal Notices Confidential computer software. license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction...............................................................................................5 1.1 About GUIDMgr..................................................................................................................5 1.2 Using the GUID Manager documentation...............................................................................6 1.2.1 GUIDMgr manpages....................................................................................................6 1.2.
Tables 1 2 Chapters in this Manual......................................................................................................6 Documentation and its location..........................................................................................
1 Introduction The HP-UX GUID (globally unique identifier) Manager (GUIDMgr) is a client-server based product that allocates and manages unique World-Wide Names (WWNs) for N_Port ID Virtualization (NPIV) Host Bus Adapters (HBAs), so you do not have to perform these tasks manually.
1.2 Using the GUID Manager documentation The GUID Manager product includes information provided in this manual as well as manpages that provide a reference to the syntax. This manual also provides information about integrating the GUIDmgr with HP Integrity Virtual Machines V4.3 (January 2012 patch release), HP-UX Virtual Partitions V6.0, and vPars and Integrity VM V6.1. For more information about these products, see the following manuals at http://www.hp.
1.3 WWN States A WWN managed by the GUIDMgr can be in one of five states in the database: • FREE — The WWN is available for assignment to a vPar, either by manually specifying the WWNs or by requesting them from the GUID server. • EXTERNAL – The WWN has not been assigned to a vPar yet. While in this state, the WWNs are not automatically handed out to another requestor. NOTE: This is usually a transitory state to INUSE. The WWNs may be held by a third party like Virtual Server Manager.
2 Installing the GUIDMgr This chapter describes how to install the GUIDMgr software and includes the following topics: • Installation requirements • Installation procedure • Verifying the installation • Removing the GUIDMgr software • Reporting problems 2.1 Installation requirements To install the GUIDMgr, you need the following: • HP-UX Secured Shell installed and working • An HP Integrity server with HP-UX B.11.31 installed • root privilege is required 2.
the database for the first time, if not already created, and start the postgresql daemons needed to access the database. 2.2.2 Installing on the client To install the GUID client, enter the following command on all the VSP hosts: # swinstall -s ${DEPOT_PATH}/GUIDMGR_A.01.00.579_HP-UX_B.11.31_IA.depot GUIDMGR NOTE: After installing and verifying the client installation, you must set up authentication on GUID client. Otherwise, any GUID request to remote server will fail.
3 Setting up the GUIDMgr This chapter discusses how to set up the server and the client, how to create the GUIDMgr database and how to configure and manage the WWNs. 3.1 Setting up the server and the client This section provides the steps for setting up the server and the client. After installing, initializing, and configuring the GUID manager on the server (see “Installing on the server” (page 9)), follow these steps to set up the server: 1.
:cd /sbin/init.d ./guidd stop ./guidkeyd stop ./guidsshd stop ./guidd start ./guidkeyd start .
4 Using GUIDMgr commands This chapter lists the GUIDMgr commands used to manage WWNs. • Managing the database • Configuring a range • Managing a WWN 4.1 Managing the database The following GUIDMgr commands manage the GUIDMgr database: • guiddbutil –c wwn Creates the WWN database, with the range_wwn table, addr_wwn table, and db_vers_wwn. • guiddbutil –d wwn Deletes the WWN database. • guiddbutil –s range_wwn wwn Displays the contents of the range_wwn table.
For more information about setting WWN ranges and listing WWNs, see “Setting WWN ranges” (page 15) and “Listing WWN ranges” (page 15) • guidmgmt –L wwn Displays the port World- Wide name (pWWN) range and the node World-Wide name (nWWN) range, where the limit is 0x8000, from 0 to 7fff. • guidmgmt -U wwn old_start old_end new_start new_end Updates a GUID range, where new must be a superset of the old. • guidmgmt –F wwn start end Deletes a GUID range.
4.4.1 Setting WWN ranges The following command sets the GUID range (50014c20000114bb~50014c20000114cc) in the server database The range type is HP-DEFINED-PWWN and the owner is HPVM: # guidmgmt -S -t HP-DEFINED-PWWN -o HPVM wwn 50014c20000114bb 50014c20000114cc NOTE: If the pWWN range is set successfully, the related nWWN range is set by the GUID server in the background. See “Listing WWN ranges” (page 15) for an example of listing all the ranges that have been set. 4.4.
50014c20000114bd wwn 50014c20000114be wwn FREE FREE 4.4.5 Freeing a range of WWNs This command allows you to free ranges from the GUID server database at the end of a range's lifecycle: # guidmgmt -F -o HPVM wwn 50014c20000114bb 50014c20000114cc 4.4.6 Stopping and starting the GUID daemons To stop and start the GUID daemons, first change to the directory /sbin/init.d, then run each script, one by one in the following order to first stop them all then start them all: :cd /sbin/init.d ./guidd stop .
guidmgr 20173 20167 0 15:33:55 ? guidmgr 20176 20167 0 15:33:55 ? guidmgr 20167 1 0 15:33:54 pts/0 /opt/guid/db/ guidmgr 20174 20167 0 15:33:55 ? guidmgr 20175 20167 0 15:33:55 ? 0:00 postgres: writer process 0:00 postgres: stats collector process 0:00 /opt/guid/tools/postgresql/bin/postgres -p 49220 -D 0:00 postgres: wal writer process 0:00 postgres: autovacuum launcher process # check for key daemon, daemon to allow SSH tunneling from GUID Client to GUID Server :ps -ef | grep guidkeyd | grep -v grep roo
This command starts the daemons and uses the existing database that you have already configured. If you receive the two Warnings, you have already created a wwn_db database, and it will be reused. If you do not receive Warnings, you are setting up a GUID server for the first time. NOTE: There is no harm in running the guid_server_prepare.sh command while the GUID server daemons are running. The script checks that all the daemons needed by the GUID server are running. 2.
NOTE: In this scenario, GUID client is not set up to communicate with the GUID server. You must perform a manual configuration, so that the GUID client can communicate with the GUID server. 3.
5 Integrating GUIDMgr GUID Manager is integrated with HP Integrity VM V4.3 (January 2012 patch release), HP-UX Virtual Partitions V6.0 (vPars V6.0), and vPars and Integrity VM V6.1. NPIV allows you to create multiple virtual fiber channel ports (VFCs) over one physical port (PFC) on a host. Each of these virtual ports should be created with a unique World Wide Node name (WWN) and World Wide Port name (pWWN). Several commands can be used with the GUIDMgr: • • • HP Integrity Virtual Machines V4.
The following commands update the WWNs data field (which is an optional task): # /opt/guid/bin/guidmgmt -d wwn 50014C20000000 atcuxvm5 # /opt/guid/bin/guidmgmt -d wwn 50014C2000000001 atcuxvm5 # /opt/guid/bin/guidmgmt -q Address ================ 50014C2000000000 Address ================ 50014C2000000001 wwn | head -l 0 Type Owner Status Data ========== ========== ========== ========== wwn HPVM INUSE atcuxvm5 Type Owner Status Data ========== ========== ========== ========== wwn HPVM INUSE atcuxvm5 The d
6 Support and other resources 6.1 Contacting HP 6.1.1 Before you contact HP Be sure to have the following information available before you call contact HP: • Technical support registration number (if applicable) • Product serial number • Product model name and number • Product identification number • Applicable error message • Add-on boards or hardware • Third-party hardware or software • Operating system type and revision level 6.1.
Table 2 Documentation and its location Documents Website HP Integrity Virtual Machines documentation HP Integrity Virtual Machines and Online VM Migration HP Superdome 2 Onboard Administrator User Guide HP Business Support Center Manuals HP Superdome 2 Onboard Administrator Command Line Interface User Guide Virtual Partition documentation www.hp.com/go/hpux-vpars-docs HP-UX System documentation http://www.hp.com/go/hpux-core-docs Partition commands http://www.hp.com/go/hpux-clickable-manpages 6.
Index C Client and server setup, 11 D document related documentation, 23 documentation, 6 G GUID Manager installing, 9 GUIDMgr installation requirements, 9 removing, 10 verifying installation, 10 GUIDMgr commands, 13 GUIDMgr installation procedure, 9 I installing the GUIDMgr, 9 Integrating with vPars and Integrity VM vPars integration, 21 Integrity VM V4.
