Bienvenue sur le site admin-sys

Si probleme(s) avec NIS : (HPUX)

Jerome ROBERT — 2009-04-17T16:53:00Z

Si probleme(s) avec NIS :

If You Receive an NIS "Server Not
Responding" Message

Issue the /usr/sbin/ping(1M) command on
the NIS client to make sure the NIS server is up and is reachable on
the network. If the ping command fails, either the server is down, or
the network has a problem. If the server is down, reboot it, or wait
for it to come back up. For information on troubleshooting network
problems, see Installing and Administering LAN/9000 Software .

To boot your NIS client without waiting
for the server to come up, boot the client in single user mode, set
NIS_CLIENT=0 in the /etc/rc.config.d/namsvrs file, then boot your
client the rest of the way up.

Issue the domainname command (with no
arguments) on both the NIS server and the NIS client to check whether
their domain names are the same. If they are different, log in as
root to the NIS client and issue the following command to change its
domain name :

domainname domainname

Issue the ps -ef command on the NIS
server to check whether ypserv is running. If it is not, follow these
steps :

1.In the /etc/rc.config.d/namesvrs file
on the NIS server, make sure the following variables are set :

NIS_MASTER_SERVER=1

2.Issue the following command to start
up the NIS server :

/sbin/init.d/nis.server start

Make sure an NIS server exists on the
same subnet as the NIS client. The client broadcasts its bind
request, and it binds to the first server that responds to the
request. Broadcasts do not cross gateways or routers, so the server
must be on the same subnet as the client in order to receive the bind
request. If you cannot configure an NIS server on the same subnet as
your NIS clients, see To Bind an NIS Client to a Server on a
Different Subnet.

If a User Cannot Log In

If the user has recently changed
passwords, ask the user to try logging in with the old password. If
the user can log in using the old password, follow these steps :

1.Issue the ps -ef command on the NIS
master server to make sure the yppasswdd daemon is running. If it is
not, issue the

following command to start all the NIS
server processes :

/sbin/init.d/nis.server start

2.Check the cron scripts on the slave
servers to make sure transfers of the passwd map from the master
server are frequent enough. Once per hour is usually frequent enough,
but frequent map transfers may cause too much network traffic. You
might want to schedule map transfers for late at night, and advise
users to make their password changes just before they go home.

Issue the following command on the NIS
client to determine which master server supplies the passwd map to
the client :

/usr/bin/ypwhich -m passwd

If the server does not respond, see If
You Receive an NIS 'Server Not Responding' Message.

If the ypwhich command returns the name
of the NIS master server, log in as root to the master server and
make sure the user has an entry in its /etc/passwd file. Then, issue
the following commands on the master server to generate the NIS
passwd database from the /etc/passwd file and push it to the NIS
slave servers :

cd /var/yp

/usr/ccs/bin/make passwd

Issue the domainname command (with no
arguments) to make sure the client's default domain is the domain
served by the NIS master server. If it is not, log in as root to the
NIS client, and issue the following command to change its domain
name :

domainname domainname

Issue the following command to check
whether the NIS client has an entry in the passwd database on the NIS
server to which it is bound :

/usr/bin/ypmatch username passwd

If the client has no entry in the
passwd database, issue the following command on the NIS server to
which the client is bound :

/usr/sbin/ypxfr passwd

This command transfers the passwd
database from the NIS master server to the server where you issue the
command.

If the user's NIS client is bound to a
slave server, make sure the slave server is listed in the NIS master
server's ypservers database. Follow these steps :

1.Issue the following command on the
NIS client to determine which server the client is bound to :

/usr/bin/ypwhich

2.Log into the NIS master server, and
issue the following command :

cd /var/yp/domainname

3.Issue the following command on the
NIS master server to write the contents of the ypservers database to
a temporary file :

/usr/sbin/makedbm -u ypservers >
tempfile

4.If the NIS slave server is not listed
in tempfile, use a text editor to add it, and then issue the
following command to rebuild the ypservers database :

/usr/sbin/makedbm tempfile ypservers

If you are using NIS compat mode, make
sure the NIS escape entry in the /etc/passwd file on the client does
not have an asterisk in the password field. On HP systems, the NIS
escape entry in the /etc/passwd file should be

+: :-2:60001:: :

If You Receive an "Unknown Host"
Message

Issue the following command to trace a
lookup of the unknown host :

/usr/contrib/bin/nsquery hosts hostname

The trace will indicate which name
services (BIND, NIS, NIS+, or /etc/hosts) were queried and in what
order. If your host is not performing lookups the way you want, see
Configuring the Name Service Switch for instructions on configuring
the Name Service Switch.

Issue the following command on the NIS
client to determine which master server supplies the hosts map :

/usr/bin/ypwhich -m hosts

If the server does not respond, see If
You Receive an NIS 'Server Not Responding' Message.

If the ypwhich command returns the name
of the NIS master server, log in as root to the master server and
make sure the unknown host is listed in its /etc/hosts file. Then,
issue the following commands on the master server to generate the NIS
hosts database from the /etc/hosts file and push it to the NIS slave
servers :

cd /var/yp

/usr/ccs/bin/make hosts

Issue the domainname command (with no
arguments) to make sure the client's default domain is the domain
served by the NIS master server. If it is not, log in as root to the
NIS client and issue the following command to change its domain name :

domainname domainname

Issue the following command to check
whether the unknown host is listed in the hosts database on the NIS
server to which the client is

bound :

/usr/bin/ypmatch hostname hosts

If the host is not listed in the hosts
database, issue the following command on the NIS server to which the
client is bound :

/usr/sbin/ypxfr hosts

This command transfers the hosts
database from the NIS master server to the server where you issue the
command.

If the NIS client is bound to a slave
server, make sure the slave server is listed in the NIS master
server's ypservers database. Follow these steps :

1.Issue the following command on the
NIS client to determine which server the client is bound to :

/usr/bin/ypwhich

2.Log in as root to the NIS master
server and issue the following command to change to the directory
where the domain databases reside :

cd /var/yp/domainname

3.On the NIS master server, issue the
following command to write the contents of the ypservers database to
a temporary file :

/usr/sbin/makedbm -u ypservers >
tempfile

4.If the NIS slave server is not listed
in tempfile, use a text editor to add it, and then issue the
following command to rebuild the ypservers database :

/usr/sbin/makedbm tempfile ypservers

If an NIS Client Cannot Bind to a
Server

If NIS commands return any of the
following messages,

ypcat : can't bind to an NIS server for
domain domainname

ypmatch : can't match key.

reason : can't communicate with ypbind

ypwhich : clntudp_create error
RPC_PROG_NOT_REGISTERED

then ypbind is not running on the
client. Issue the following command to start all the NIS client
processes :

/sbin/init.d/nis.client start

If NIS Returns Incorrect Information

Issue the following command on the NIS
client to determine which master server supplies the appropriate NIS
map :

/usr/bin/ypwhich -m mapname

If the server does not respond, see If
You Receive an NIS 'Server Not Responding' Message.

Log in as root to the NIS master
server, and issue the following command to check the contents of the
appropriate NIS map :

/usr/bin/ypcat -k mapname

If the map contents are not correct,
edit the ASCII file from which the map is generated. Then issue the
following commands to regenerate the map and push it to the slave
servers :

cd /var/yp

/usr/ccs/bin/make mapname

domainname domainname

Issue the following command on the NIS
client to check the contents of the map on the NIS server to which
the client is bound :

/usr/bin/ypcat -k mapname

If the contents are not correct, log in
as root to the server that serves the NIS client, and issue the
following command :

/usr/sbin/ypxfr mapname

This command transfers the map from the
NIS master server to the server where you issue the command.

If the NIS client is bound to a slave
server, make sure the slave server is listed in the NIS master
server's ypservers database. Follow these steps :

1.Issue the following command on the
NIS client to determine which server the client is bound to :

/usr/bin/ypwhich

2.Log in as root to the NIS master
server and issue the following command to change to the directory
where the domain databases reside :

cd /var/yp/domainname

3.On the NIS master server, issue the
following command to write the contents of the ypservers database to
a temporary file :

/usr/sbin/makedbm -u ypservers >
tempfile

4.If the NIS slave server is not listed
in tempfile, use a text editor to add it, and then issue the
following command to rebuild the ypservers database :

/usr/sbin/makedbm tempfile ypservers

Make sure the slave servers have cron
scripts that schedule regular updates of the map.

Configuration de Netbackup 5.0

Jerome ROBERT — 2009-04-17T16:03:36Z

— >

Installation de NetBackup 5.0 sous HP-UX

Jerome ROBERT — 2009-04-17T16:02:05Z

Exemple d installation de NetBackup 5.0 sous HP-UX

Monter le Cd-rom sous HP-UX

 # mkdir /a # nohup pfs_mountd & # nohup pfsd & # pfs_mount -o xlat=unix /dev/dsk/c#t#d# /a

Executer le script

# cd /a

#./install

VERITAS Installation Script Copyright 1993 - 2003 VERITAS Software Corporation, All Rights Reserved. Installation Options 1 NetBackup 2 NetBackup Client Software 3 NetBackup Client Java Software q To quit from this script Choose an option [default: q]: 1 The NetBackup and Media Manager software is built for use on HP9000-800 hardware. Do you want to install NetBackup and Media Manager files? [y,n] (y) y NetBackup and Media Manager are normally installed in /usr/openv. The existing /usr/openv directory will be used for NetBackup and Media Manager. The HP9000-800 clients will be loaded. Do you want to load any other NetBackup clients onto the server? [y,n] (y) y Choose the Platform Client Options you wish to install. HP9000-800 must be installed Platform Client Options ----------------------- 1. ALPHA 2. HP9000 3. INTEL 4. Linux 5. MACINTOSH 6. RS6000 7. SCO 8. SGI 9. Solaris 10. All UNIX client platforms q. quit selecting HP9000-800 Enter Choice(s) [1 - 10] 2 HP9000-800 HP9000-800 Enter Choice(s) [1 - 10] 3 HP9000-800 HP9000-800 INTEL Enter Choice(s) [1 - 10] q You have chosen to install: HP9000 INTEL Is this the list you wish to use? [y,n] (y) y Reading client binaries for /usr/openv/netbackup/client/HP9000-800 x HP9000-800/HP-UX11.00/bp, 290816 bytes, 568 tape blocks x HP9000-800/HP-UX11.00/bparchive symbolic link to bpbackup x HP9000-800/HP-UX11.00/bpjava-msvc, 610304 bytes, 1192 tape blocks ... x HP9000-800/HP-UX11.11/libvopie.sl, 233472 bytes, 456 tape blocks x HP9000-800/HP-UX11.11/libvopie64.sl, 244912 bytes, 479 tape blocks x HP9000-800/HP-UX11.11/XKeysymDB, 773 bytes, 2 tape blocks Reading client binaries for /usr/openv/netbackup/client/INTEL x INTEL/FreeBSD4.5/bp, 255797 bytes, 500 tape blocks x INTEL/FreeBSD4.5/bparchive symbolic link to bpbackup x INTEL/FreeBSD4.5/bpbackup, 332085 bytes, 649 tape blocks ... x INTEL/FreeBSD4.5/vxss_db_paths, 1623 bytes, 4 tape blocks x INTEL/FreeBSD4.5/xbp, 582 bytes, 2 tape blocks x INTEL/FreeBSD4.5/XKeysymDB, 773 bytes, 2 tape blocks Reading NetBackup files from /cdrom/hp-ux/anb x usr/openv/db/bin/nbdbd, 3182592 bytes, 6216 tape blocks x usr/openv/db/etc/mysql/english/errmsg.sys, 11159 bytes, 22 tape blocks x usr/openv/db/etc/mysql/english/errmsg.txt, 11634 bytes, 23 tape blocks .. x usr/openv/man/man1m/vltrun.1m, 12321 bytes, 25 tape blocks x usr/openv/man/man1m/vopie_util.1m, 11573 bytes, 23 tape blocks x usr/openv/man/man1m/vopied.1m, 8863 bytes, 18 tape blocks Reading NetBackup-Java GUI applications from /cdrom/NB-Java/ The Java packages for installed client types will be loaded. cp NB-Java.install /usr/openv/NB-Java.install cp NB-Java.tar.Z /usr/openv/NB-Java.tar.Z cp HPUX_JRE.tar.Z /usr/openv/java/HPUX_JRE.tar.Z cp libSigScheduleJNI.sl /usr/openv/lib/server/hp_ux/libSigScheduleJNI.sl Reading Media Manager files from /cdrom/hp-ux/anb x usr/openv/volmgr/bin/drive_mount_notify, 2860 bytes, 6 tape blocks x usr/openv/volmgr/bin/drive_unmount_notify, 2822 bytes, 6 tape blocks x usr/openv/volmgr/bin/mmcrawl, 344064 bytes, 672 tape blocks ... x openv/db/var/mysql/tables_priv.frm, 8877 bytes, 18 tape blocks x openv/db/var/mysql/user.frm, 9148 bytes, 18 tape blocks x openv/db/etc/nbdb.cnf, 199 bytes, 1 tape blocks Copying HP-UX11.11 Client Binaries + /bin/cp ./bp /usr/openv/netbackup/bin/bp + /bin/cp ./bpcd /usr/openv/netbackup/bin/bpcd + /bin/cp ./bpdynamicclient /usr/openv/netbackup/bin/bpdynamicclient ... + /bin/cp ./template.names_allow.txt /usr/openv/var/auth/template.names_allow.txt + /bin/cp ./template.names_deny.txt /usr/openv/var/auth/template.names_deny.txt + /bin/cp ./fsanalyze /usr/openv/netbackup/bin/fsanalyze A NetBackup Server or Enterprise Server license key is needed for installation to continue. Enter license key: Evaluation NetBackup Enterprise Server with Apr 30, 2004 expiration date will be registered. Is this OK? [y,n] (y) ....-DR62-6PCP-R6TP-....-4ITP-6YNM-....-P: Evaluation NetBackup Enterprise Server Base product with the following features enabled: Open File Backup Remote Client Support Robotic Library Sharing Support Remote Media Server Support Microsoft RSM Robotic Libraries ADIC DAS/SDLC Robotic Libraries IBM ATL Robotic Libraries Fujitsu LMF Robotic Libraries StorageTek ACS Robotic Libraries Advanced Client MS SharePoint Agent Inline Tape Copy Vault GDM Managed Server Library Based Tape Drives Additional Drives/Robotics DataStore Intelligent Disaster Recovery Teradata Encryption DES 56-bit Encryption DES 40-bit SAP extension SQL-Backtrack extension Sybase extension Informix extension Oracle extension Lotus Notes extension DB2 extension MS SQL Server extension MS Exchange extension Advanced Reporting Option Shared Storage Option Global Data Manager NDMP EMC Additional clients has been registered. All additional keys should be added at this time. Do you want to add additional license keys now? [y,n] (y) n Use /usr/openv/netbackup/bin/admincmd/get_license_key to add, delete or list license keys at a later time. Installing NetBackup Enterprise Server version: 5.0GA If this machine will be using a different network interface than the default (server12), the name of the preferred interface should be used as the configured server name. If this machine will be part of a cluster, the virtual name should be used as the configured server name. Would you like to use "server12" as the configured name of the NetBackup server? [y,n] (y) y Is server12 the master server? [y,n] (y) y Do you have any media servers? [y,n] (n) n Linking /usr/lib/X11/app-defaults/XNB --> /usr/openv/netbackup/bin/XNB.dt Checking for a bpcd entry in /etc/inetd.conf: Adding bpcd entry. Original /etc/inetd.conf saved as /etc/inetd.conf.NBU_041604.11:47:01. Checking for a vnetd entry in /etc/inetd.conf: Adding vnetd entry. Checking for a vopied entry in /etc/inetd.conf: Adding vopied entry. Checking for a bpjava-msvc entry in /etc/inetd.conf: Adding bpjava-msvc entry. Checking /etc/services for the needed NetBackup and Media Manager services. Copying original /etc/services file to /etc/services.NBU_041604.11:53:12 Editing /etc/services to update NetBackup and Media Manager services. /etc/services will be updated to add the following entries for NetBackup/Media Manager. bprd 13720/tcp bprd bpcd 13782/tcp bpcd bpdbm 13721/tcp bpdbm vnetd 13724/tcp vnetd vopied 13783/tcp vopied bpjobd 13723/tcp bpjobd nbdbd 13784/tcp nbdbd visd 9284/tcp visd bpjava-msvc 13722/tcp bpjava-msvc vmd 13701/tcp vmd acsd 13702/tcp acsd tl8cd 13705/tcp tl8cd tldcd 13711/tcp tldcd ts8d 13709/tcp ts8d odld 13706/tcp odld tl4d 13713/tcp tl4d tsdd 13714/tcp tsdd tshd 13715/tcp tshd tlmd 13716/tcp tlmd tlhcd 13717/tcp tlhcd lmfcd 13718/tcp lmfcd rsmd 13719/tcp rsmd To change these entries modify the file /tmp/services.ov_edited.6908 and enter when ready to continue: /etc/services has been updated to contain NetBackup and Media Manager services. WARNING: ypwhich: the NIS domain name hasn't been set on this machine WARNING: ypcat: the NIS domain name hasn't been set on this machine Sending SIGHUP to inetd process. To make NetBackup start up automatically when the system is restarted, the netbackup script found in /usr/openv/netbackup/bin/goodies has been placed in /sbin/init.d, with links to it placed in the /sbin/rc2.d directory. To make NetBackup shut down automatically when the system is restarted, the netbackup script found in /usr/openv/netbackup/bin/goodies has been placed in /sbin/init.d, with links to it placed in the /sbin/rc0.d directory. Extracting NetBackup-Java product files. Installing NetBackup-Java, and the Java runtime environment for HP-UX B.11.11. Configuring NetBackup-Java runtime environment. The installation of the NetBackup-Java product on server12 is complete. In order for device discovery and auto-configuration to work properly in a NetBackup Enterprise environment, particularly where peripherals are connected to multiple servers, one host must serve as the repository for global device database information. Enter which host will store the global device database. (default: server12): server12 To be able to install the client software the NetBackup processes need to be started. Do you want to start the NetBackup processes so client software can be installed? [y,n] (y) y Starting the NetBackup database manager process (bpdbm). Do you want to create policy and schedule examples that you can view or use when you are configuring your own policies and schedules? [y,n] (y) y ... creating policy template_normal ... creating schedules for policy template_normal ... creating policy template_weekend ... creating schedules for policy template_weekend Done creating example policies and schedules. Creating Directive Set for LotusNotes Creating Directive Set for MS_Exchange_5.x Creating Directive Set for MS_Exchange_Mailbox Creating Directive Set for MS_Exchange_2000 Creating Directive Set for MS_Exchange_SRS Creating Directive Set for MS_Exchange_Public_Folders Creating Directive Set for MS_Exchange_KMS Creating Directive Set for MS_SharePoint_Server Creating Directive Set for MS_SharePoint_Workspaces Creating Template Set for Oracle_RMAN Creating Template Set for Oracle_XML_Export Creating Template Set for DB2 Creating Directive Set for Windows2000 Policy conversion summary: Number of original policies: 2 Number of non-snapshot policies skipped: 2 Number of policies not needing conversion: 0 Number of policies converted to 'auto' snapshot method: 0 Number of policies converted: 0 Number of new policies created due to multiple clients in a policy that had different snapshot method configurations: 0 Do you want to start the Media Manager device daemon processes? [y,n] (y) y Starting the Media Manager device daemon processes. Do you want to start the NetBackup bprd process so backups and restores can be initiated? [y,n] (y) y Starting the NetBackup request daemon process (bprd). Done executing NB.inst VERITAS Installation Script Copyright 1993 - 2003 VERITAS Software Corporation, All Rights Reserved. Installation Options 1 NetBackup 2 NetBackup Client Software 3 NetBackup Client Java Software q To quit from this script Choose an option [default: q]: 1 The NetBackup and Media Manager software is built for use on HP9000-800 hardware. Do you want to install NetBackup and Media Manager files? [y,n] (y) y NetBackup and Media Manager are normally installed in /usr/openv. Is it OK to install in /usr/openv? [y,n] (y) y The HP9000-800 clients will be loaded. Do you want to load any other NetBackup clients onto the server? [y,n] (y) y Choose the Platform Client Options you wish to install. HP9000-800 must be installed Platform Client Options ----------------------- 1. ALPHA 2. HP9000 3. INTEL 4. Linux 5. MACINTOSH 6. RS6000 7. SCO 8. SGI 9. Solaris 10. All UNIX client platforms q. quit selecting HP9000-800 Enter Choice(s) [1 - 10] 2,3 Choose values in the range 1 - 10, try again or enter q to quit: 2 3 HP9000-800 HP9000-800 INTEL Enter Choice(s) [1 - 10] q You have chosen to install: HP9000 INTEL Is this the list you wish to use? [y,n] (y) y Reading client binaries for /usr/openv/netbackup/client/HP9000-800 x HP9000-800/HP-UX11.00/bp, 290816 bytes, 568 tape blocks x HP9000-800/HP-UX11.00/bparchive symbolic link to bpbackup .. x HP9000-800/HP-UX11.00/bpbkar, 966656 bytes, 1888 tape blocks x HP9000-800/HP-UX11.00/bpcd, 659456 bytes, 1288 tape blocks x HP9000-800/HP-UX11.00/bpclimagelist, 425984 bytes, 832 tape blocks VERITAS Installation Script Copyright 1993 - 2003 VERITAS Software Corporation, All Rights Reserved. Installation Options 1 NetBackup 2 NetBackup Client Software 3 NetBackup Client Java Software q To quit from this script Choose an option [default: q]: 3 Choose the Java Platform Options you wish to install. Java Platform Options --------------------- 1. AIX 2. HPUX 3. Linux 4. Solaris_Sparc 5. Solaris_x86 6. Tru64 7. All Java platforms q. quit selecting Enter Choice(s) [1 - 7] 2 HPUX Enter Choice(s) [1 - 7] q You have chosen to install: HPUX Is this the list you wish to use? [y,n] (y) y cp HPUX_JRE.tar.Z /usr/openv/java/HPUX_JRE.tar.Z VERITAS Installation Script Copyright 1993 - 2003 VERITAS Software Corporation, All Rights Reserved. Installation Options 1 NetBackup 2 NetBackup Client Software 3 NetBackup Client Java Software q To quit from this script Choose an option [default: q]: q A trace of the install can be found in /tmp/install_trace.7435 That file can be deleted after you are sure the install was successful.

LDAP-UX

Jerome ROBERT — 2009-04-17T15:58:38Z

LDAP-UX

1. Installation LDAP-UX

Installation du produit : J4269AA ( LDAP-UX Integration )

swinstall -s /depot

2. Configuration de LDAP-UX

#
cd /opt/ldapux/config

#
ls

create_profile_cache
display_profile_cache setup

create_profile_entry
get_profile_entry

create_profile_schema
ldap_proxy_config

# Commande qui va modifier le schÃ©ma du serveur LDAP, Ã faire d'une
seul fois.

#
./create_profile_schema

Hewlett-Packard
Company LDAP-UX Client Services Schema Extension Program

--------------This
LDAP-UX Client Profile Schema Extension Program will guide you through

to
add/update the LDAP-UX Client Profile schema to the standard schema in

Directory
Server.

This
supports Netscape/iPlanet Directory Servers and

Windows
2000 Active Directory Servers.

During
the configuration :

- Press "Return" to choose the default and go to the next
screen

- Type "Control-B" to go back to the previous screen

- Type "Control-C" to cancel the Schema Extension program

Would
you like to continue with configuration ? [Yes] :

Hewlett-Packard
Company LDAP-UX Client Services Schema Extension Program

----------Enter
the host name of the directory where you want to store the profile.

BEnter
either the fully qualified host name (for example : sys001.hp.com)

or
IP address (for example : 15.13.118.130).

To
accept the default shown in brackets, press the Return key.

Directory
server host [server14 = 155.208.176.244] :
155.208.176.245

Hewlett-Packard Company LDAP-UX Client Services Schema Extension Program

>--------------Enter the port number of the previously
specified directory server.

>To accept the default shown in brackets, press the
Return key.

>Directory Server port number [389] :

Hewlett-Packard Company LDAP-UX Client Services
Schema Extension Program

-------------Select which Directory Server you want
to connect to :

1. Netscape/iPlanet Directory

2. Windows 2000 Active Directory

>NOTE : LDAP-UX defaults with the SFU 3.0 schema when
using Windows 2000 Active Directory.
Refer to /opt/ldapux/README-LdapUxClient to use other versions of
SFU.

To accept the default shown in brackets, press the
Return key.

Directory Server : [1] :

PFMERR 39 : The LDAP-UX Profile schema extension
exists !

#
ls

create_profile_cache
display_profile_cache setup

create_profile_entry
get_profile_entry

create_profile_schema
ldap_proxy_config

# Commande qui va crÃ©er une fichier du serveur LDAP, Ã faire d'une
seul fois.

#
./create_profile_entry

Hewlett-Packard
Company HP-UX LDAP Profile Entry Creation

----------------Welcome
to the HP-UX LDAP Integration profile creation program

This
program will prompt you for information required to create

the
configuration profile entry and add to LDAP Directory Server.

You
must have "root" privilege to run this Program.

During
the configuration :

- Press "Return" to choose the default and go to the next
screen

- Type "Control-B" to go back to the previous screen

- Type "Control-C" to cancel the program

Would
you like to continue ? [Yes] :

Hewlett-Packard Company HP-UX LDAP Profile Entry Creation

>-----------------Select which Directory Server you
want to connect to :

>1. Netscape/iPlanet Directory

>2. Windows 2000 Active Directory

>NOTE : LDAP-UX defaults with the SFU 3.0 schema when
using Windows 2000 Active Directory.
Refer to /opt/ldapux/README-LdapUxClient to use other versions of SFU.

>To accept the default shown in brackets, press the
Return key.

>Directory Server : [1] :

Hewlett-Packard Company HP-UX LDAP Profile Entry Creation

>---------------Enter the host name of the directory
where you want to store the profile.

>Enter either the fully qualified host name (for
example : sys001.hp.com)

>or IP address (for example : 15.13.118.130).

>To accept the default shown in brackets, press the
Return key.

>Directory server host [server14 = 155.208.176.244] :
155.208.176.245

Hewlett-Packard Company HP-UX LDAP Profile Entry Creation

>------------------Enter the port number of the
previously specified directory server.

>To accept the default shown in brackets, press the
Return key.

>Directory Server port number [389] :

Hewlett-Packard Company HP-UX LDAP Profile Entry Creation

>---------------Enter the distinguished name (DN) of
an existing LDAP-UX profile entry

>you want to use or the DN where you want to store a
new LDAP-UX profile

>entry. For a new entry, all parent entries of the DN
must already exist in

>the directory or this step will fail,

>(for example : cn=ldapuxprofile, ou=ldapuxprofile, o=hp.com)

>Profile Entry DN : [] : cn=ldapuxprofile,dc=hp,dc=com

Hewlett-Packard Company HP-UX LDAP Profile Entry Creation

>----------------Enter the distinguished name (DN) of
the directory user allowed to

>create a new LDAP-UX profile entry or to check an
existing profile entry.

>To accept the default shown in brackets, press the
Return key.

>User DN [cn=Directory Manager] :

>Password : directory

Hewlett-Packard Company HP-UX LDAP Profile Entry Creation

>----------------For high-availability, each LDAP-UX
client can look for user and group

>information in up to three different directory
servers. Please enter either

>the fully qualified host name and optional port
number

>(for example : sys001.hp.com:389) or IP address and
optional port number

>(for example : 15.13.118.130:400) where your directory
is running.

>The following hosts are currently specified :

>Default search host 2 : [ ]

>Default search host 3 : [ ]

>Enter 0 to accept these hosts and continue with the
setup program or

>Enter the number of the hosts you want to specify
[0] :

Hewlett-Packard Company HP-UX LDAP Profile Entry Creation

>----------Enter the default base DN where LDAP-UX
clients should look for user and

>Group information, (for example : ou=nis,o=hp.com)

>Default base DN [dc=hp,dc=com] :

Hewlett-Packard Company HP-UX LDAP Profile Entry Creation

>------------The setup program has all the information
needed to configure a default

>profile and client. You can accept default values for
the remaining

>parameters or configure the remaining parameters.

>Accept remaining defaults ? (y/n)
[y] :

Hewlett-Packard Company HP-UX LDAP Profile Entry Creation

>------------Are you ready to create the Profile Entry ?
[Yes] :

>modifying entry cn=ldapuxprofile,dc=hp,dc=com

#
cd /opt/ldapux/config

#
ls

create_profile_cache
display_profile_cache setup

create_profile_entry
get_profile_entry

create_profile_schema
ldap_proxy_config

# Commande Ã faire sur chaque client !

#
./setup

Hewlett-Packard
Company LDAP-UX Client Services Setup Program

------------------------------Welcome
to the LDAP-UX Client Services Setup Program !

You
must have "root" privilege to run this Setup Program.

If
this is the first client you are setting up, this program will :

-
Extend your directory schema with the LDAP-UX configuration profile schema.

-
Create a new LDAP-UX configuration profile entry in your directory.

-
Configure the local client system to use the directory.

If
your directory already has one or more LDAP-UX configuration profile

entries,
this program will :

-
Optionally create another new LDAP-UX configuration profile entry in your

directory and configure the local client system to use the
directory ;

-
or configure your client system with an existing profile entry.

During
the configuration :

- Press "Return" to choose the default and go to the next
screen

- Type "Control-B" to go back to the previous screen

- Type "Control-C" to cancel the setup program

Would
you like to continue with the setup ? [Yes] : Y

Hewlett-Packard Company LDAP-UX Client Services Setup Program

>-----------------Select which Directory Server you
want to connect to :

>1. Netscape/iPlanet Directory

>2. Windows 2000 Active Directory

>NOTE : LDAP-UX defaults with the SFU 3.0 schema when
using Windows 2000 Active Directory.

>Refer to /opt/ldapux/README-LdapUxClient to use other
versions of SFU.

>To accept the default shown in brackets, press the
Return key.

>Directory Server : [1] :

HEwlett-Packard Company LDAP-UX Client Services Setup Program

>------------Your
local client configuration file /etc/opt/ldapux/ldapux_client.conf

>shows the following profile entry information for the

>Name Service Switch (NSS) :

> LDAP_HOSTPORT="155.208.176.240:389
155.208.176.245:389"

> PROFILE_ENTRY_DN="cn=ldapuxprofile,dc=hp,dc=com"

>You can change this configuration to :

> o
specify a different directory

> o
specify a different existing profile in the directory

> o create
a new profile

>(You cannot change an existing profile with this
setup program. Use

>your directory administration tools to change
existing profiles.)

>Would you like to change this configuration (Yes/No/Quit)
? [Yes] :

Hewlett-Packard Company LDAP-UX Client Services Setup Program

>----------------Enter the host name of the directory
where you want to store the profile.

>Enter either the fully qualified host name (for
example : sys001.hp.com)

>or IP address (for example : 15.13.118.130).

>To accept the default shown in brackets, press the
Return key.

>Directory server host [server14 = 155.208.176.244] :
155.208.176.245

Hewlett-Packard Company LDAP-UX Client Services Setup Program

>-------------Enter the port number of the previously
specified directory server.

>To accept the default shown in brackets, press the
Return key.

>Directory Server port number [389] :

Hewlett-Packard
Company LDAP-UX Client Services Setup Program

-------------Enter
the distinguished name (DN) of an existing LDAP-UX profile entry

you
want to use or the DN where you want to store a new LDAP-UX profile

entry.
For a new entry, all parent entries of the DN must already exist in

the
directory or this step will fail,

for
example : cn=ldapuxprofile, ou=ldapuxprofile, o=hp.com)

Profile
Entry DN : [] : cn=ldapuxprofile,dc=hp,dc=com

Hewlett-Packard Company LDAP-UX Client Services Setup Program

>-----------Updated directory server at
155.208.176.245:389

>with a profile entry at

> [cn=ldapuxprofile,dc=hp,dc=com]

>Updated the local client configuration file

>
/etc/opt/ldapux/ldapux_client.conf

>Updated the local client profile entry LDIF file

>
/etc/opt/ldapux/ldapux_profile.ldif

>Updated the local client profile entry cache file

>
/etc/opt/ldapux/ldapux_profile.bin

>Press any key to continue :

Hewlett-Packard Company LDAP-UX Client Services Setup Program

>----------No proxy user is configured at this client

You
have changed configuration profile. To make it take effect,

>you need to start/restart the LDAP-UX daemon

>Would you like to start/restart the LDAP-UX daemon
(y/n) ? [y] :

>Updated the LDAP-UX daemon configuration file

>
/etc/opt/ldapux/ldapclientd.conf

>Restarted the LDAP-UX daemon !

>To enable the LDAP Pluggable Authentication Module,
save a copy of the

>file /etc/pam.conf then add ldap to it. See /etc/pam.ldap
for an example.

>To enable the LDAP Name Service Switch, save a copy
of the file

>/etc/nsswitch.conf then add ldap to it. See /etc/nsswitch.ldap
for an example.

>LDAP-UX Client
Services setup complete.

# Commande Ã faire sur chaque client !

#
cd /etc

#
cp pam.ldap pam.conf

#
cp nsswitch.ldap nsswitch.conf

# Les fichiers de configuration :

#
cd /etc/opt/ldapux

#
ls

daemon_auth
ldapentry.intl

default_profile_attr_ads.ldif
ldapentry.templates

default_profile_attr_ads_sfu2.ldif
ldapux_client.conf

default_profile_attr_ads_sfu3.ldif
ldapux_client.old

default_profile_attr_rfc2307.ldif
ldapux_profile.bin

ldapclientd.conf
ldapux_profile.bin.old

ldapclientd.old
ldapux_profile.ldif

ldapclientd.pid
ldapux_profile.ldif.old

Configuration de clients DNS (HPUX)

Jerome ROBERT — 2009-04-17T15:40:02Z

Configuration de clients DNS
Modifier ou créer /etc/resolv.conf
domain admin-sys.org
nameserver 192.168.3.120 # serveur primaire
nameserver 192.168.3.121 # serveur secondaire
Modifier ou créer /etc/nsswitch.conf
hosts : dns nis files
pour ma part je préfere cette l'ordre suivant :
hosts : files dns
Modifier les fichiers /.rhosts, /etc/hosts.equiv, si ces
derniers existent

- DNS

nslookup (HPUX)

Jerome ROBERT — 2009-04-17T15:35:47Z

nslookup(1)

Description
Diagnostics
Files

Arguments
Author
See
Also

NAME

nslookup - query name servers
interactively

SYNOPSIS

nslookup
[-option ...] host-to-find [server]

nslookup [-option
...] [- [server]]

DESCRIPTION

nslookup is a
program to query Internet domain name servers. nslookup

has been extended to follow the configured name resolution algorithm
of the host and to query NIS, as well as, DNS and host tables.

Both an interactive and non-interactive mode are available with
nslookup.
Interactive mode allows the user to query a name server for
information about various hosts and domains, or print a list of hosts
in the domain. Non-interactive mode is used to query a name server
for information about one host or domain.

By default, nslookup
accesses name services for name and address resolution based on the
policy information obtained from the switch configuration file
/etc/nsswitch.conf. When the policy is set to use NIS or
/etc/hosts first, or when DNS is first but unavailable,
then nslookup will
only provide a limited command set (a help command while
in this situation will show what actions are possible when querying
NIS or /etc/hosts). To override the switch policy and
query DNS servers directly, the server command can be
used to specify a nameserver. This same overriding of the switch
policy can also be done by providing a nameserver as the second
argument on the command line. In this case, nslookup

will ignore the switch policy and directly query nameservers, until a
reset command is issued. Whenever an action is taken that
causes the switch policy to be overridden, a warning message is
displayed.

Note, NIS+ is not supported by nslookup.
If the hosts source nisplus is found in the
/etc/nsswitch.conf file. It will be ignored.

ARGUMENTS

Interactive mode is entered in the following cases :

No arguments are given.
The first argument is a hyphen (-). The optional
second argument is a host name or Internet (IP) address of a name
server.

Non-interactive mode is used when the name of the host to be
looked up is given as the first argument. The optional second
argument is a host name or Internet address of a name server.

Options listed under the set command below can be
specified one per line in the .nslookuprc file in the
user's home directory. Alternatively, these options may be specified
on the command line by prefixing them with a hyphen and they must
precede other command line arguments. For example, to change the
default query type to host information, and the initial timeout to 10
seconds, type :

nslookup -query=hinfo -timeout=10

The command line option -swdebug may be used to debug
syntactic errors in the switch configuration file. This option turns
on tracing during initialization, causing the switch module to print
out a trace of the scan and parse actions on the "hosts"
entry (see nsswitch.conf(4)
) in the /etc/nsswitch.conf file.

Interactive
Commands

Commands
can be interrupted at any time by using the interrupt character. To
exit, type a Ctrl-D (EOF) or type exit. To treat a
built-in command as a host name, precede it with an escape character
(\). When using NIS or the host table, only host names
and Internet addresses are allowed as commands. An unrecognized
command is interpreted as a host name.

host [server]

Look up information for host using the current default
server or using server if specified. If host is an
Internet address and the query type is A or PTR,
the name of the host is returned. If host is a name and
does not have a trailing period, one or more domains are appended
to the name (this behavior depends on the state of the set

options domain, srchlist, defname,
and search). Answers from a name server's cache are
labeled ``non-authoritative.''

server domain

lserver domain

Change the default server to domain. lserver
uses the initial server to look up information about domain
while server uses the current default server. When
server is used while the current name service being
pointed to is either NIS or /etc/hosts, then the
switch policy will be overridden until a reset is
issued.

root

Changes the default server to the server for the root of the
domain name space. Currently, the host ns.nic.ddn.mil
is used (this command is a synonym for lserverns.nic.ddn.mil).
The name of the root server can be changed with the set
root command.

policy

Prints out the policy read from the switch configuration file.
The number of name services specified in the file are shown, as
well as the order and criteria on how the name services are to be
used. The four statuses of the criteria are represented by the
four positions within the square brackets. The order of the
statuses are : SUCCESS, NOTFOUND, UNAVAIL and TRYAGAIN. The two
actions of the criteria are represented by the two possible
letters used in the four status positions : R for
return and C for continue. However, if no criteria is
specified between two sources, then the default actions are
assigned to the statuses :

SUCCESS= return NOTFOUND= continue UNAVAIL= continue TRYAGAIN= continue

finger [name] [>
filename]

finger [name] [>>
filename]

Connects with the finger server on the current host. The
current host is defined when a previous lookup for a host was
successful and returned address information (see the set
querytype=A command). name is optional. >
and >> can be used to redirect output in the
usual manner.

ls [option] domain [>

filename]

ls [option] domain [>>

filename]

List the information available for domain, optionally
creating or appending to filename. The default output
contains host names and their Internet addresses. option
can be one of the following :

-t querytype

lists all records of the specified type (see querytype
below).

-a

lists aliases of hosts in the domain (synonym for

-t CNAME

-d

lists all records for the domain (synonym for -t ANY).

-h

lists CPU and operating system information for the domain
(synonym for -t HINFO).

-s

lists well-known services of hosts in the domain (synonym for
-t WKS).

When
output is directed to a file, # characters are
printed for every 50 records received from the server.

view filename

Sorts and lists the output of previous ls
command(s) using more (see more(1)
).

help

?

Prints a brief summary of commands.

exit

Exits the program.

reset

Returns to the use of the configured name service switch policy
and resets to use the original nameservers.

set keyword[=value]

This command is used to change state information that affects
the lookups. Valid keywords are :

all

Prints the current values of the various options to set.
Information about the current default server and host is also
printed.

cl[ass]=value

Change the query class to one of :
	`IN`	the Internet class.
	`CHAOS`	the Chaos class.
	`HESIOD`	the MIT Athena Hesiod class.
	`ANY`	wildcard (any of the above).
The class specifies the protocol group of the information. (Default = `IN`)

[no]deb[ug]

Turn debugging mode on. More information is printed about the
packet sent to the server and the resulting answer. (Default =
nodebug)

[no]d2

Turn exhaustive debugging mode on. Essentially all fields of
every packet are printed. (Default = nod2)

[no]def[name]

If set, append the default domain name to a single-component
lookup request (i.e., one that does not contain a period
character). (Default = defname)

do[main]=name

Change the default domain name to name. The default
domain name is appended to a lookup request, depending on the
state of the defname and search options.
The domain search list contains the parents of the default domain
if it has at least two components in its name. For example, if the
default domain is CC.Berkeley.EDU, the search list is
CC.Berkeley.EDU and Berkeley.EDU. Use
the set srchlist command to specify a
different list. Use the set all command
to display the list. (Default = value from hostname,
/etc/resolv.conf or LOCALDOMAIN)

[no]ig[nore]

Ignore truncation errors. (Default = noignore)

q[uerytype]=value

ty[pe]=value

Change the type of information returned from a query to one of :
	`A`	Host's Internet address
	`ANY`	All types of data
	`CNAME`	Canonical name for an alias
	`GID`	Group ID
	`HINFO`	Host CPU and operating system type
	`MB`	Mailbox domain name
	`MG`	Mail group member
	`MINFO`	Mailbox or mail list information
	`MR`	Mail rename domain name
	`MX`	Mail exchanger
	`NS`	Name server for the named zone
	`PTR`	Host name if the query is an Internet address, otherwise the pointer to other information.
	`SOA`	Start of authority record
	`TXT`	Text information
	`UID`	User ID
	`UINFO`	User information
	`WKS`	Well-known service description

po[rt]=value

Change the default TCP/UDP name server port to value.
(Default = 53)

[no]rec[urse]

Tell the name server to query other servers if it does not have
the information. (Default = recurse)

ret[ry]=number

Set the number of retries to number. When a reply to a
request is not received within a certain amount of time (changed
with set timeout), the timeout period is doubled and
the request is resent. The retry value controls how many times a
request is resent before giving up. (Default = 4)

ro[ot]=host

Change the name of the root server to host. This affects
the root command. (Default = ns.nic.ddn.mil)

[no]sea[rch]

If the lookup request contains at least one period but doesn't
end with a trailing period, append the domain names in the domain
search list to the request until an answer is received. See
hostname(5)
. (Default = search)

srchl[ist]=name1/name2/...

Change the default domain name to name1 and the domain
search list to name1, name2, etc. A maximum of 6
names separated by slashes (/) can be specified. For
example,

set srchlist=lcs.MIT.EDU/ai.MIT.EDU/MIT.EDU

sets
the domain to lcs.MIT.EDU and the search list to the
three names. This command overrides the default domain name and
search list of the set domain command.
Use the set all command to display the
list. (Default = value based on hostname, /etc/resolv.conf

or LOCALDOMAIN)

[no]swtr[ace]

When set, this flag causes nslookup
to print out information about the sources used for resolving a
name or an address lookup. This flag traces the behavior generated
by the switch policy. (Default = noswtrace)

t[imeout]=number

Change the initial timeout interval for waiting for a reply to
number seconds. Each retry doubles the timeout period.
(Default = 5 seconds)

[no]v[c]

Always use a virtual circuit when sending requests to the
server. (Default = novc)

DIAGNOSTICS

If the lookup request was not
successful, an error message is printed. Possible errors are :

`Time-out`		The server did not respond to a request after a certain amount of time (changed with `set` `timeout=` value) and a certain number of retries (changed with `set` `retry=` value).
`No` `response` `from` `server`
		No name server is running on the server machine.
`No` `records`		The server does not have resource records of the current query type for the host, although the host name is valid. The query type is specified with the `set` `querytype` command.
`Non-existent` `domain`
		The host or domain name does not exist.
`Connection` `refused`

`Network` `is` `unreachable`
		The connection to the name server could not be made at the present time.
`Server` `failure`
		The name server found an internal inconsistency in its database and could not return a valid answer.
`Refused`		The name server refused to service the request.
`Format` `error`
		The name server found that the request packet was not in the proper format.

AUTHOR

nslookup was
developed by the University of California, Berkeley.

FILES

`/etc/resolv.conf`
		Initial domain name and name server addresses
`$HOME/.nslookuprc`
		User's initial options

hosts_to_named (HPUX)

Jerome ROBERT — 2009-04-17T15:22:10Z

hosts_to_named(1M)

Description
Author
See Also

Examples
Files

NAME

hosts_to_named - translate host table to name server file format

SYNOPSIS

hosts_to_named -d domain -n network-number [options]

DESCRIPTION

hosts_to_named translates the host table, /etc/hosts, into files that are usable by the name server named(1M) . The format of these files is defined in RFC1035. The files are created in the current directory. Once the host table is translated, the name server files can be maintained directly, or the translation can be repeated after each change to the host table.

If a line in the host table contains no domain names, all names on the line are assumed to be in the default domain. The first domain listed is the "default domain". If data is being created for more than 1 domain or if certain options are used, there must be domain names in the host table to determine which names belong in which domain.

The name server data is referred to as "resource records".

Options are :

`-a network-number`
		Add the information about hosts in the local domain from network network-number. This is the same as the `-n` option except that no pointer (PTR) data is created. This is useful when there are multiple domains on a network and a different server is handling the address-to-name mapping for network-number.
`-b bootfile`		Name the boot file bootfile. The default is `named.boot` in the current directory.
`-c subdomain`		Create alias (CNAME) records for hosts in subdomain of the default domain. When a subdomain is delegated, it is useful to create aliases for the old names in the default domain that point to the new names in the subdomain. After creating the alias (CNAME) records, ignore lines in the host table that contain names in the subdomain. This option can be used more than once on the command line. This option requires domain names in the host table. When the old names in this domain are no longer used, they can be ignored with the `-e` option. If the subdomain name does not have dots, the default domain is appended to subdomain.
`-d domain`		Create data for domain. This option can be used more than once on the command line if data is being created for more than 1 domain. The first domain listed is the "default domain". This option requires domain names in the host table for all hosts in domains except the default domain.
`-e subdomain`		Eliminate lines from the host table that contain names in the subdomain before translating. If the subdomain name does not have dots, the default domain is appended. This option may be used more than once on the command line. This option requires domain names in the host table.
`-f file`		Read command line options from file. The `-f` option is not allowed within a file.
`-h host`		Declare host to be the host in the start of authority (SOA) record that the name server data was created on. Also use host for the electronic mail address of the responsible user in the SOA record. The default is the host this command is run on.
`-m weight:mailhub`
		For each canonical hostname from the host table, create mail exchanger (MX) records with the specified weight and mail hub. The weight is a positive integer. The mail hub is a hostname. If the mail hub name has no dots, the default domain is appended. This option can be used more than once on the command line.
`-n network-number[:mask]`
		Create data for network-number. See below for description of network-number. If only one domain is listed with `-d`, all data for network-number is assumed to be in domain. The optional subnet mask mask can be used instead of supplying each network-number for a subnet using multiple `-n` options. mask must be in dot notation.
`-o refresh:retry:expire:min`
		Set the values in the start-of-authority (SOA) record to those specified. See below for description of the start-of-authority (SOA) record.
`-p domain`		Create only pointer (PTR) data for hosts in domain. This is useful when there are multiple domains on a network and a different server is responsible for domain, but this server is responsible for the address-to-name mapping. This option can be used more than once on the command line. This option requires domain names in the host table.
`-q`		Run quietly. No messages are printed.
`-r`		Create name server data indicating that the name server is authoritative for `.` (the root of the domain tree). The file created is `db.root`. Use this only when your network is isolated from the Internet. If other root servers exist for the isolated network, they must be added manually.
`-s server`		Create name server (NS) records that declare server is an authoritative name server for all of the domains created. If more than 1 server is authoritative, each needs to be declared. If the server name does not have any dots in it, the default domain is appended. The default server is the host this script is run on. This option can be used more than once on the command line.
`-t`		Create text (TXT) records from the comments that appear with host data. The comments will all be in lower case because the host table is translated to lower case. If `[no smtp]` appears in a comment, it is omitted. The `[no smtp]` is used to control mail exchanger (MX) data.
`-u user`		Declare user to be the electronic mail address of the person responsible for this domain. This is used in the start of authority (SOA) record. The format required in the name server data is `user.host` (host must be a domain name). If given as user, the host on which this script is run is appended. If given as user @host, the @ is replaced with a dot (`.`). The default user is `root`.
`-w`		Create well known services (WKS) data declaring that the host provides the SMTP service. This is done only when mail exchanger (MX) data is also being created and only for hosts without `[no smtp]` in a comment.
`-z internet-address`
		Create a secondary boot file, `boot.sec.save`, from the primary boot file listing internet-address as the server to load the data from. The boot file has the server back up the data on disk. The internet-address defaults to the value used with `-Z`. This option can be used more than once.
`-A`		Do not create name server data for aliases in the host table.
`-C file`		Create resource records from strings in the comment field of the host table. Each string in the comment field (except `[no smtp]` ) is searched for in file. The format of file is a string, a colon, and a resource record. If the string in the comment field matches the string before the colon in file, a resource record is added consisting of the name of the host followed by everything after the colon from the matching line in file. For example, host information (HINFO) records can be created by adding `360:IN HINFO hp9000s360 hp-ux` to file and adding 360 to comments in the host table.
`-D`		Do not create name server data for domain names in the host table.
`-F`		By default, the serial number is incremented for a domain only if the data has changed (pointer (PTR) data only). This option forces the serial number to be incremented, even if the data has not changed.
`-H host-file`		Use host-file instead of `/etc/hosts`.
`-M`		Do not create mail exchanger (MX) records for hosts in the host table.
`-N mask`		Apply the default subnet mask mask to each network-number specified with `-n` except for ones with their subnet masks already provided. mask must be in dot notation. This is the same as supplying each network-number for a subnet using multiple `-n` options.
`-S server`		This option is the same as the `-s` option, but it only applies to the last domain specified with `-d` or the last network-number specified with `-n`. This option is for when server is backing up some, but not all, of the domains.
`-Z internet-address`
		Create a secondary boot file, `boot.sec`, from the primary boot file listing internet-address as the server to load the data from. The boot file does not have the server back up the data on disk. The internet-address defaults to value used with `-z`. This option can be used more than once.
`-1`		This option is obsolete.

hosts_to_named translates the host table to lower case to help eliminate duplicate data. Since the name server treats uppercase and lowercase as equivalent, names that differ only in case are considered the same.

Alias (CNAME) records are created for subdomains delegated with -c. Lines from the host table that contain names in subdomains from -c and -e are removed from the lowercase copy of the host table.

The host table is then used to create the name server data for each network-number declared on the command line. Do not include the trailing 0's in the network number. No distinction is made between class A, B, or C addresses nor is there any understanding of subnets unless a subnet mask is supplied. Example network numbers are : 10 (for all addresses of the form 10.*.*.*), 10.1 (for addresses of the form 10.1.*.*), or 10.2.2 (for addresses of the form 10.2.2.*).

Address (A) records are created for mapping hostnames to IP addresses. Alias (CNAME) records are created for aliases of hosts that are not multi-homed. The data are placed in a file named db. DOMAIN where DOMAIN is the first part of the domain from the command line. For the domain div.inc.com, the file is named db.div. All other name server data goes in this file except the pointer (PTR) records described below.

Pointer (PTR) records are created for mapping IP addresses to host names. PTR records are placed in a file named db. NET where NET is the network number from the command line. Network 10 data is placed in db.10. Network 10.1 data are placed in "db.10.1".

Mail exchanger (MX) records are created unless the -M option is used. The default MX record has a weight of 10 with the host itself as its mail exchanger. No default MX record is created for a host if [no smtp] is in the comment section of that line in the host table. MX records for each mail hub declared with the -m option are added for each host even if [no smtp] is in the comment section.

Well known services (WKS) records are created for each host that handles SMTP mail (does not have [no smtp]) if -w is used. The only service listed is SMTP.

Text (TXT) records are created for comments associated with hosts in the host table if -t is used. The comments do not include [no smtp].

For each domain, a start of authority (SOA) record is created. The SOA record requires 2 domain names : the host that the data is created on and the electronic mail address of the person responsible. The -h and -u options influence the names. In addition, the SOA record requires 5 values : a serial number, a refresh time, a retry time, an expire time, and a minimum ttl (time to live). The first time the data is created, the serial number is set to 1, the refresh time is set to 3 hours, the retry time is set to 1 hour, the expire time is set to 1 week, and the minimum ttl is set to 1 day. The -o option changes these values except for the serial number. Each subsequent time hosts_to_named is run, the serial number is incremented. If any of the other fields in the SOA record are modified, the changed values are retained.

If there are files named spcl. DOMAIN or spcl. NET in the current directory, $INCLUDE directives are added to the corresponding db. DOMAIN or db. NET file for the spcl file. In this way, special data can be added to the data generated by hosts_to_named.

The first time hosts_to_named is run, it creates a default boot file for a primary name server. Each subsequent time hosts_to_named is run, the boot file is updated if necessary. New entries are made in the boot file for any additional networks or domains not already in the boot file. No entries are deleted from the boot file.

The boot file for a caching-only server, boot.cacheonly, is created if it does not exist. The boot files for secondary servers, boot.sec.save and boot.sec, are created if the -z or -Z options are used. The boot files for secondary servers are created new each time from the primary server boot file so that they are equivalent.

EXAMPLES

Create name server data for networks 15.19.8 and 15.19.9 in div.inc.com.

hosts_to_named -d div.inc.com -n 15.19.8 -n 15.19.9

Create name server data for networks 15.19.8 and 15.19.9 in div.inc.com. Ignore aliases in the host table and include 2 mail hubs - aaa.div.inc.com and bbb.mkt.inc.comk. Put all of the options in a file.

hosts_to_named -f option_file

Option_file contains the following lines :

-d div.inc.com -n 15.19.8 -n 15.19.9 -m 20:aaa -m 30:bbb.mkt.inc.com -A

Network 15.19.15 has hosts in the xx.inc.com domain and the div.inc.com domain. Create name server data for xx.inc.com. Create only pointer (PTR) data for hosts in div.inc.com on network 15.19.15 (this requires the hosts in div.inc.com to have the canonical name or an alias of the form x.div.inc.com).

hosts_to_named -d xx.inc.com -n 15.19.15 -p div.inc.com

Create name server data for network 15.19.8 in div.inc.com. Include div.inc.com data from network 15.19.15 but do not create pointer (PTR) data for 15.19.15 since that is being handled by the xx.inc.com server.

hosts_to_named -d div.inc.com -n 15.19.8 -a 15.19.15

AUTHOR

hosts_to_named was developed by HP.

FILES

`/etc/hosts`		The host table
`named.boot`		Primary server boot file
`boot.cacheonly`
		Caching only server boot file
`boot.sec.save`
		Secondary server boot file
`boot.sec`		Secondary server boot file
`db.127.0.0`		Pointer information for 127.0.0.1
`db.cache`		Stub cache file for root server addresses
`db.root`		Data for servers for the root domain
`db.DOMAIN`		Address and other data for a domain
`db.DOMAIN.in-addr`
		Pointer data for all network-numbers
`db.NET`		Pointer data for a network-number

nsswitch.conf (HPUX)

Jerome ROBERT — 2009-04-17T15:18:08Z

Syntax of the nsswitch.conf File

Each line in the /etc/nsswitch.conf file has the following syntax :

lookup_type name_service [status=action status=action ...] name_service ...

If you include any status=action pairs after a name service, the square brackets are required.

lookup_type The type of information to be looked up. The supported keywords and the information types they represent are listed in Types of Lookups Controlled by the Name Service Switch. These keywords are case-sensitive.

name_service

One of the following name services to use for the type of information in the lookup_type field. These keywords must be in lowercase.

`files`		Files in the `/etc` directory on the local host (`/etc/hosts`, `/etc/services`, and so on).
`nis`		Network Information Service (NIS).
`dns`		Domain Name System (DNS), which is implemented by Berkeley Internet Name Domain (BIND) on HP-UX. See the Installing and Administering Internet Services manual for more information. The `dns` keyword may be used only on the line beginning with `hosts`.

status

One of the following statuses returned by a name service query. These values may be entered in uppercase or lowercase.

`SUCCESS`		The lookup was successful, and the requested information was found.
`NOTFOUND`		The name service returned a response, but the requested data was not in its database.
`UNAVAIL`		The name service is not configured.
`TRYAGAIN`		The name service was busy and the request timed out. This value is returned only by DNS.

action

The action to take based on the status of the name service query. The following values may be entered in uppercase or lowercase.

`continue`		Try the next name service in the list.
`return`		End the lookup and return control to the calling process without consulting the next name service in the list.

If a line beginning with one of the lookup_types does not exist in the /etc/nsswitch.conf file, the default Name Service Switch configuration for that type of information is used. If the /etc/nsswitch.conf file does not exist, the default configuration is used for every type of information. The default Name Service Switch configuration is described in Default Configuration.

**Table 1** **Types of Lookups Controlled by the Name Service Switch**
Keyword	Type of Information Represented by Keyword
`automount`	NFS automounter maps stored in files like `/etc/auto_master` and `/etc/auto_home` or in NIS maps like `auto.master` and `auto.home`.
`hosts`	Host names and IP addresses stored in the `/etc/hosts` file or the NIS `hosts.byaddr` and `hosts.byname` maps.
`netgroup`	NFS netgroups stored in the `/etc/netgroup` file or the NIS `netgroup`, `netgroup.byhost` and `netgroup.byuser` maps.
`networks`	Network names and IP addresses stored in the `/etc/networks` file or the NIS `networks.byaddr` and `networks.byname` maps.
`protocols`	Networking protocol names and numbers stored in the `/etc/protocols` file or the NIS `protocols.byname` and `protocols.bynumber` maps.
`rpc`	RPC program names and numbers stored in the `/etc/rpc` file or the NIS `rpc.byname` and `rpc.bynumber` maps.
`services`	Mapping of networking services to port numbers and protocols, stored in the `/etc/services` file or the NIS `services.byname` and `services.bynp` maps.

nsswitch.conf (HPUX)

Jerome ROBERT — 2009-04-17T15:16:24Z

Syntax
of the nsswitch.conf File

Each
line in the /etc/nsswitch.conf file has the following
syntax :

lookup_type name_service [status=action status=action ...] name_service ...

If you include any status=action pairs
after a name service, the square brackets are required.

lookup_type	The type of information to be looked up. The supported keywords and the information types they represent are listed in Types of Lookups Controlled by the Name Service Switch. These keywords are case-sensitive.
name_service	One of the following name services to use for the type of information in the lookup_type field. These keywords must be in lowercase.
		`files`	Files in the `/etc` directory on the local host (`/etc/hosts`, `/etc/services`, and so on).
		`nis`	Network Information Service (NIS).
		`dns`	Domain Name System (DNS), which is implemented by Berkeley Internet Name Domain (BIND) on HP-UX. See the Installing and Administering Internet Services manual for more information. The `dns` keyword may be used only on the line beginning with `hosts`.

status	One of the following statuses returned by a name service query. These values may be entered in uppercase or lowercase.
		`SUCCESS`		The lookup was successful, and the requested information was found.
		`NOTFOUND`		The name service returned a response, but the requested data was not in its database.
		`UNAVAIL`		The name service is not configured.
		`TRYAGAIN`		The name service was busy and the request timed out. This value is returned only by DNS.

action	The action to take based on the status of the name service query. The following values may be entered in uppercase or lowercase.
		`continue`		Try the next name service in the list.
		`return`		End the lookup and return control to the calling process without consulting the next name service in the list.

If a line beginning with one of the
lookup_types does not exist in the /etc/nsswitch.conf

file, the default Name Service Switch configuration for that type of
information is used. If the /etc/nsswitch.conf file does
not exist, the default configuration is used for every type of
information. The default Name Service Switch configuration is
described in Default Configuration.

Table
1 Types of Lookups Controlled by the Name
Service Switch

Keyword	Type of Information Represented by Keyword
`automount`	NFS automounter maps stored in files like `/etc/auto_master` and `/etc/auto_home` or in NIS maps like `auto.master` and `auto.home`.
`hosts`	Host names and IP addresses stored in the `/etc/hosts` file or the NIS `hosts.byaddr` and `hosts.byname` maps.
`netgroup`	NFS netgroups stored in the `/etc/netgroup` file or the NIS `netgroup`, `netgroup.byhost` and `netgroup.byuser` maps.
`networks`	Network names and IP addresses stored in the `/etc/networks` file or the NIS `networks.byaddr` and `networks.byname` maps.
`protocols`	Networking protocol names and numbers stored in the `/etc/protocols` file or the NIS `protocols.byname` and `protocols.bynumber` maps.
`rpc`	RPC program names and numbers stored in the `/etc/rpc` file or the NIS `rpc.byname` and `rpc.bynumber` maps.
`services`	Mapping of networking services to port numbers and protocols, stored in the `/etc/services` file or the NIS `services.byname` and `services.bynp` maps.

Configuration d'un DNS secondaire (HPUX)

Jerome ROBERT — 2009-04-17T15:14:04Z

Configuration d'un DNS secondaire

1° Préparation

Modifier le fichier /etc/rc.config.d/namesvrs

NAMED=1

NAMED_ARGS=""

Modifier ou créer /etc/resolv.conf

domain admin-sys.org

nameserver 192.168.3.120 # serveur primaire

nameserver 192.168.3.121 # serveur secondaire

Création du répertoire de configuration

mkdir /etc/named.data

cd /etc/named.data

2° Récupération des fichiers

grace à l'option z ou Z dans le fichier de configuration de
hosts_to_named. Ce dernier a créé le fichier de
configuration des DNS secondaire

fichier de configuration de named

ftp DNS_primaine

get /etc/named.data/boot.sec.save /etc/named.boot

quit

fichiers de data

ftp DNS_primaine

get /etc/named.data/db.127.0.0

get /etc/named.data/db.cache

quit

Attention : Le fichier db.cache n'est nécessaire que
si votre DNS est connecté sur le réseau public

3° Relancer le service

/sbin/init.d/named stop

/sbin/init.d/named start

4° Divers

Pour forcer la mise à jour, des serveurs secondaire :
sig_named restart