ipa02.phas.ubc.ca
142.103.236.38 (PUBLIC) - 192.168.1.38 (server)
System Information   xxxxxx xxx

Config Info

13-05-23
Configuring ipa server
[root@ipa02 ~]# history
    1  yum update
    2  ifconfig
    3  shutdown n\-h now
    4  shutdown -h now
    5  exit
    6  ifconfig -a
    7  cd /etc/sysconfig/
    8  cat network
    9  cd network-scripts/
   10  ls
   11  cp ifcfg-eth0 ifcfg-eth1
   12  vim ifcfg-eth1
   13  vi ifcfg-eth1
   14  service network restart
   15  ifconfig -a
   16  ping 142.103.243.254
   17  vi ifcfg-eth1
   18  service network restart
   19  ping 142.103.243.254
   20  ifconfig -a
   21  netstat -nr
   22  vi ifcfg-eth1
   23  ifconfig
   24  ifconfig -a
   25  ifconfig -a | grep eth1
   26  ifconfig -a | grep eth1 >> ifcfg-eth1
   27  vi ifcfg-eth1
   28  service network restart
   29  ping 142.103.243.254
   30  ping www.phas.ubc.ca
   31  cat /etc/resolv.conf 
   32  vim /etc/resolv.conf 
   33  vi /etc/resolv.conf 
   34  pwd
   35  cat /etc/redhat-release 
   36  pwd
   37  yum update
   38  ifconfig -a
   39  ping 142.103.243.254
   40  host dns.phas.ubc.ca
   41  yum install network-utils
   42  host mirrorlist.centos.org
   43  nslookup mirrorlist.centos.org
   44  ping google.com
   45  cat /etc/resolv.conf 
   46  cd /etc/sysconfig/
   47  vim network
   48  vi network
   49  service network restart
   50  ifconfig -a
   51  netstat -nr
   52  host dns.phas.ubc.ca
   53  cat /etc/resolv.conf 
   54  vi /etc/resolv.conf
   55  host dns.phas.ubc.ca
   56  yum update
   57  yum list | grep -i ipa
   58  yum update
   59  vim /etc/sysconfig/network-scripts/ifcfg-eth0
   60  vi /etc/sysconfig/network-scripts/ifcfg-eth0
   61  vi /etc/sysconfig/network-scripts/ifcfg-eth1
   62  service network restart
   63  ping 142.103.236.254
   64  ifconfig -a
   65  vi /etc/sysconfig/network-scripts/ifcfg-eth1
   66  service network restart
   67  ping 142.103.236.254
   68  ping 142.103.236.1
   69  ssh veyron
   70  cat /etc/hosts
   71  vim /etc/hosts
   72  yum install vim
   73  vim /etc/hosts
   74  host veyron
   75  yum list | grep -i netw
   76  ls /etc/init.d/*anag*
   77  ls /etc/init.d/*net*
   78  yum list | grep -i util
   79  yum list | grep -i util | more
   80  yum install iputils
   81  rpm -ql iputils
   82  yum list | grep -i util | more
   83  yum install bind-utils
   84  rpm -ql bind-utils | grep bin
   85  host veyron
   86  iptables -L
   87  iptables -Ln
   88  vim /etc/hosts
   89  vim /etc/sysconfig/network
   90  vim /etc/sysconfig/network-scripts/ifcfg-eth1
   91  hostname ipatest.phas.ubc.ca
   92  hostname
   93  cat /etc/hosts
   94  service network restart
   95  ping dns.phas.ubc.ca
   96  yum update
   97  reboot
   98  yum list | grep ipa
   99  yum install ipa-server
  100  iptables -L -n
  101  iptables -L
  102  sestatus
  103  iptables -L -n --line-numbers
  104  iptables -I INPUT 5 -j IPA
  105  iptables -L -n --line-numbers
  106  iptables -I INPUT 5 -j IPA
  107  iptables -N IPA
  108  iptables -L -n --line-numbers
  109  iptables -I INPUT 5 -j IPA
  110  iptables -I IPA -s 142.103.236.0/24 -p tcp --dport 88 -j ACCEPT
  111  iptables -I IPA -s 142.103.236.0/24 -p udp --dport 88 -j ACCEPT
  112  iptables -I IPA -s 142.103.236.0/24 -p udp --dport 53 -j ACCEPT
  113  iptables -I IPA -s 142.103.236.0/24 -p udp --dport 123 -j ACCEPT
  114  iptables -I IPA -s 142.103.236.0/24 -p tcp --dport 389 -j ACCEPT
  115  iptables -I IPA -s 142.103.236.0/24 -p tcp --dport 636 -j ACCEPT
  116  iptables -I IPA -s 142.103.236.0/24 -p tcp --dport 80 -j ACCEPT
  117  iptables -I IPA -s 142.103.236.0/24 -p tcp --dport 443 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p tcp --dport 88 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p udp --dport 88 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p udp --dport 53 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p udp --dport 123 -j ACCEPT 
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p tcp --dport 389 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p tcp --dport 636 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p tcp --dport 80 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p tcp --dport 443 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.236.0/24 -p tcp --dport 464 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.236.0/24 -p udp --dport 464 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p udp --dport 464 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p tcp --dport 464 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.235.0/24 -p tcp --dport 53 -j ACCEPT
[root@ipa02 ~]# iptables -I IPA -s 142.103.236.0/24 -p tcp --dport 53 -j ACCEPT
[root@ipa02 ~]# iptables -L IPA -n
Chain IPA (1 references)
target     prot opt source               destination         
ACCEPT     tcp  --  142.103.236.0/24     0.0.0.0/0           tcp dpt:53 
ACCEPT     tcp  --  142.103.235.0/24     0.0.0.0/0           tcp dpt:53 
ACCEPT     tcp  --  142.103.235.0/24     0.0.0.0/0           tcp dpt:464 
ACCEPT     udp  --  142.103.235.0/24     0.0.0.0/0           udp dpt:464 
ACCEPT     udp  --  142.103.236.0/24     0.0.0.0/0           udp dpt:464 
ACCEPT     tcp  --  142.103.236.0/24     0.0.0.0/0           tcp dpt:464 
ACCEPT     tcp  --  142.103.235.0/24     0.0.0.0/0           tcp dpt:443 
ACCEPT     tcp  --  142.103.235.0/24     0.0.0.0/0           tcp dpt:80 
ACCEPT     tcp  --  142.103.235.0/24     0.0.0.0/0           tcp dpt:636 
ACCEPT     tcp  --  142.103.235.0/24     0.0.0.0/0           tcp dpt:389 
ACCEPT     udp  --  142.103.235.0/24     0.0.0.0/0           udp dpt:123 
ACCEPT     udp  --  142.103.235.0/24     0.0.0.0/0           udp dpt:53 
ACCEPT     udp  --  142.103.235.0/24     0.0.0.0/0           udp dpt:88 
ACCEPT     tcp  --  142.103.235.0/24     0.0.0.0/0           tcp dpt:88 
ACCEPT     tcp  --  142.103.236.0/24     0.0.0.0/0           tcp dpt:443 
ACCEPT     tcp  --  142.103.236.0/24     0.0.0.0/0           tcp dpt:80 
ACCEPT     tcp  --  142.103.236.0/24     0.0.0.0/0           tcp dpt:636 
ACCEPT     tcp  --  142.103.236.0/24     0.0.0.0/0           tcp dpt:389 
ACCEPT     udp  --  142.103.236.0/24     0.0.0.0/0           udp dpt:123 
ACCEPT     udp  --  142.103.236.0/24     0.0.0.0/0           udp dpt:53 
ACCEPT     udp  --  142.103.236.0/24     0.0.0.0/0           udp dpt:88 
ACCEPT     tcp  --  142.103.236.0/24     0.0.0.0/0           tcp dpt:88 
[root@ipa02 ~]# service iptables save

  118  service iptables save
  119  iptables -L -n --line-numbers
  121  yum install bind
  122  yum install bind-dyndb-ldap
  124  ipa-server-install --help
  127  ipa-server-install --setup-dns
  128  vim /etc/sysconfig/network
  129  vim /etc/sysconfig/network-scripts/ifcfg-eth1
  130  pwd
  131  reboot
  132  ipa-server-install --setup-dns
  133  reboot
  134  vim /etc/hosts
[root@ipa02 ~]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
142.103.236.38 ipa02.phas.ubc.ca ipa02

[root@ipa02 ~]# ipa-server-install --setup-dns

The log file for this installation can be found in /var/log/ipaserver-install.log
==============================================================================
This program will set up the IPA Server.

This includes:
  * Configure a stand-alone CA (dogtag) for certificate management
  * Configure the Network Time Daemon (ntpd)
  * Create and configure an instance of Directory Server
  * Create and configure a Kerberos Key Distribution Center (KDC)
  * Configure Apache (httpd)
  * Configure DNS (bind)

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

Existing BIND configuration detected, overwrite? [no]: yes
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
.
Example: master.example.com.


Server host name [ipa02.phas.ubc.ca]: 

Warning: skipping DNS resolution of host ipa02.phas.ubc.ca
The domain name has been determined based on the host name.

Please confirm the domain name [phas.ubc.ca]: 

The kerberos protocol requires a Realm name to be defined.
This is typically the domain name converted to uppercase.

Please provide a realm name [PHAS.UBC.CA]: 
Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and has full access
to the Directory for system management tasks and will be added to the
instance of directory server created for IPA.
The password must be at least 8 characters long.

Directory Manager password: 
Password (confirm): 

The IPA server requires an administrative user, named 'admin'.
This user is a regular system account used for IPA server administration.

IPA admin password: 
Password (confirm): 

Do you want to configure DNS forwarders? [yes]: 
Enter the IP address of DNS forwarder to use, or press Enter to finish.
Enter IP address for a DNS forwarder: 142.103.236.1
DNS forwarder 142.103.236.1 added
Enter IP address for a DNS forwarder: 142.103.236.14
DNS forwarder 142.103.236.14 added
Enter IP address for a DNS forwarder: 
Do you want to configure the reverse zone? [yes]: 
Please specify the reverse zone name [236.103.142.in-addr.arpa.]: 
Using reverse zone 236.103.142.in-addr.arpa.

The IPA Master Server will be configured with:
Hostname:      ipa02.phas.ubc.ca
IP address:    142.103.236.38
Domain name:   phas.ubc.ca
Realm name:    PHAS.UBC.CA

BIND DNS server will be configured to serve IPA domain with:
Forwarders:    142.103.236.1, 142.103.236.14
Reverse zone:  236.103.142.in-addr.arpa.

Continue to configure the system with these values? [no]: yes

The following operations may take some minutes to complete.
Please wait until the prompt is returned.

Configuring NTP daemon (ntpd)
  [1/4]: stopping ntpd
  [2/4]: writing configuration
  [3/4]: configuring ntpd to start on boot
  [4/4]: starting ntpd
Done configuring NTP daemon (ntpd).
Configuring directory server for the CA (pkids): Estimated time 30 seconds
  [1/3]: creating directory server user
  [2/3]: creating directory server instance
  [3/3]: restarting directory server
Done configuring directory server for the CA (pkids).
Configuring certificate server (pki-cad): Estimated time 3 minutes 30 seconds
  [1/21]: creating certificate server user
  [2/21]: creating pki-ca instance
  [3/21]: configuring certificate server instance
  [4/21]: disabling nonces
  [5/21]: creating CA agent PKCS#12 file in /root
  [6/21]: creating RA agent certificate database
  [7/21]: importing CA chain to RA certificate database
  [8/21]: fixing RA database permissions
  [9/21]: setting up signing cert profile
  [10/21]: set up CRL publishing
  [11/21]: set certificate subject base
  [12/21]: enabling Subject Key Identifier
  [13/21]: setting audit signing renewal to 2 years
  [14/21]: configuring certificate server to start on boot
  [15/21]: restarting certificate server
  [16/21]: requesting RA certificate from CA
  [17/21]: issuing RA agent certificate
  [18/21]: adding RA agent as a trusted user
  [19/21]: configure certificate renewals
  [20/21]: configure Server-Cert certificate renewal
  [21/21]: Configure HTTP to proxy connections
Done configuring certificate server (pki-cad).
Configuring directory server (dirsrv): Estimated time 1 minute
  [1/38]: creating directory server user
  [2/38]: creating directory server instance
  [3/38]: adding default schema
  [4/38]: enabling memberof plugin
  [5/38]: enabling winsync plugin
  [6/38]: configuring replication version plugin
  [7/38]: enabling IPA enrollment plugin
  [8/38]: enabling ldapi
  [9/38]: disabling betxn plugins
  [10/38]: configuring uniqueness plugin
  [11/38]: configuring uuid plugin
  [12/38]: configuring modrdn plugin
  [13/38]: enabling entryUSN plugin
  [14/38]: configuring lockout plugin
  [15/38]: creating indices
  [16/38]: enabling referential integrity plugin
  [17/38]: configuring ssl for ds instance
  [18/38]: configuring certmap.conf
  [19/38]: configure autobind for root
  [20/38]: configure new location for managed entries
  [21/38]: restarting directory server
  [22/38]: adding default layout
  [23/38]: adding delegation layout
  [24/38]: adding replication acis
  [25/38]: creating container for managed entries
  [26/38]: configuring user private groups
  [27/38]: configuring netgroups from hostgroups
  [28/38]: creating default Sudo bind user
  [29/38]: creating default Auto Member layout
  [30/38]: adding range check plugin
  [31/38]: creating default HBAC rule allow_all
  [32/38]: Upload CA cert to the directory
  [33/38]: initializing group membership
  [34/38]: adding master entry
  [35/38]: configuring Posix uid/gid generation
  [36/38]: enabling compatibility plugin
  [37/38]: tuning directory server
  [38/38]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring Kerberos KDC (krb5kdc): Estimated time 30 seconds
  [1/10]: adding sasl mappings to the directory
  [2/10]: adding kerberos container to the directory
  [3/10]: configuring KDC
  [4/10]: initialize kerberos container
  [5/10]: adding default ACIs
  [6/10]: creating a keytab for the directory
  [7/10]: creating a keytab for the machine
  [8/10]: adding the password extension to the directory
  [9/10]: starting the KDC
  [10/10]: configuring KDC to start on boot
Done configuring Kerberos KDC (krb5kdc).
Configuring kadmin
  [1/2]: starting kadmin 
  [2/2]: configuring kadmin to start on boot
Done configuring kadmin.
Configuring ipa_memcached
  [1/2]: starting ipa_memcached 
  [2/2]: configuring ipa_memcached to start on boot
Done configuring ipa_memcached.
Configuring the web interface (httpd): Estimated time 1 minute
  [1/13]: setting mod_nss port to 443
  [2/13]: setting mod_nss password file
  [3/13]: enabling mod_nss renegotiate
  [4/13]: adding URL rewriting rules
  [5/13]: configuring httpd
  [6/13]: setting up ssl
  [7/13]: setting up browser autoconfig
  [8/13]: publish CA cert
  [9/13]: creating a keytab for httpd
  [10/13]: clean up any existing httpd ccache
  [11/13]: configuring SELinux for httpd
  [12/13]: restarting httpd
  [13/13]: configuring httpd to start on boot
Done configuring the web interface (httpd).
Applying LDAP updates
Restarting the directory server
Restarting the KDC
Configuring DNS (named)
  [1/9]: adding DNS container
  [2/9]: setting up our zone
  [3/9]: setting up reverse zone
  [4/9]: setting up our own record
  [5/9]: setting up kerberos principal
  [6/9]: setting up named.conf
  [7/9]: restarting named
  [8/9]: configuring named to start on boot
  [9/9]: changing resolv.conf to point to ourselves
Done configuring DNS (named).

Global DNS configuration in LDAP server is empty
You can use 'dnsconfig-mod' command to set global DNS options that
would override settings in local named.conf files

Restarting the web server
==============================================================================
Setup complete

Next steps:
	1. You must make sure these network ports are open:
		TCP Ports:
		  * 80, 443: HTTP/HTTPS
		  * 389, 636: LDAP/LDAPS
		  * 88, 464: kerberos
		  * 53: bind
		UDP Ports:
		  * 88, 464: kerberos
		  * 53: bind
		  * 123: ntp

	2. You can now obtain a kerberos ticket using the command: 'kinit admin'
	   This ticket will allow you to use the IPA tools (e.g., ipa user-add)
	   and the web user interface.

Be sure to back up the CA certificate stored in /root/cacert.p12
This file is required to create replicas. The password for this
file is the Directory Manager password

[root@ipa02 ~]# chkconfig --list | grep ipa
ipa            	0:off	1:off	2:on	3:on	4:on	5:on	6:off
ipa_memcached  	0:off	1:off	2:off	3:off	4:off	5:off	6:off

[root@ipa02 ~]# reboot
[root@ipa02 ~]# Connection to ipa02 closed by remote host.
rap@spyder:/tmp/ipa/freeipa-3.2.0$ ssh root@ipa02
root@ipa02's password: 
Last login: Thu May 23 14:05:19 2013 from spyder.phas.ubc.ca
[root@ipa02 ~]# service ipa status
Directory Service: RUNNING
KDC Service: RUNNING
KPASSWD Service: RUNNING
DNS Service: RUNNING
MEMCACHE Service: RUNNING
HTTP Service: RUNNING
CA Service: RUNNING
[root@ipa02 ~]# ipactl status
Directory Service: RUNNING
KDC Service: RUNNING
KPASSWD Service: RUNNING
DNS Service: RUNNING
MEMCACHE Service: RUNNING
HTTP Service: RUNNING
CA Service: RUNNING

    
Run udevadm trigger

Disaster Recovery xxx

Crashplan Purchase Details
Please make sure you're purchasing through this link.
Registration Key (for license purchases): 7727-S7TR-TMWH-JTRT


XXXX
xxxxxx

12-08-27

NFS sharing

OLD STUFF


12-05-25