1. Have the person needing the server submit a change listing you as the person responsible for server setup. Determine if you have necessary hardware, power, and computer rack location before beginning the work.
2. Submit a change ticket to obtain the IP address with new Server name. Request the cabling and Ethernet hardware necessary to accomplish the task.
3. Create a change ticket requesting the storage necessary from the originating disks, fibers, and cables based on the originating ticket.
4. Place hardware in cabinets, power up and determine if the hardware is seen by hardware management console. Note this may take getting Ethernet cables from the server to the HMC if not already present.
5. Create the LPAR from the Hardware Management Console where the server will be located. Use the spec’s submitted in the originating ticket.
6. Setup the Ethernet adapter (Shared or dedicated). Add adapter thru the HMC from available slot. Add IP address and default route. Check the connection with ping, nfs, or telnet.
7. Load the operating system if you do not already have it loaded. A NIM (Network Install Manager) environment has been setup on NAD0019aixd10 which should have the necessary file sets. Note make certain that the necessary patches are also applied to be certain the environment is up to date with current IBM supported patch sets.
8. Logon the server setting the root password to the standard used by the system administration staff.
9. Load SSL and SSH software assuring your connections is protected.
Change /etc/ssh_config – Setup value # MaxStartup 10 to MaxStartup 500.
10. Setup necessary disk storage space. If EMC be certain the fiber adapters are up to date on microcode levels in order to avoid future problems with access errors.
11. Loaded standard software as required by user requesting the system.
a. SUDOER
b. foglight
c. Setup BUXS directory with all home grown software.
12. Create user base that will use the necessary initially for DBA’s or other personnel to start their software loads.
13. Create user file systems from orginating ticket with required software.
14. Assist with any other software necessary for DBA load.
15. Have users test the application.
16. Reboot server to test everything comes back as required. Add custom scripts to root cron or inittab for rebooting to fix any reboot issues.
17: Secure server:
chuser rlogin=false root
18. In AIX 5.3 for Oracle:
chdev -l aio0 -P -a maxreqs=8192 (requires reboot)
vmo -p -o lru_file_repage=0
vi /etc/rc.tcpip:
Change:
start /usr/sbin/hostmibd “$src_running” “-c buxs”
start /usr/sbin/snmpmibd “$src_running” “-c buxs”
start /usr/sbin/aixmibd “$src_running” “-c buxs”
vi /etc/snmpdv3.conf:
Change all instances of ‘public’ to ‘buxs’
Comment out :
#start /usr/sbin/muxatmd …
vi /etc/inetd.conf:
Comment out:
# ftp ……..
# telnet ……….
vi /etc/inittab:
Comment out fbcheck ( with ‘:’ not, ‘#’ )
18: Set up buxs user with ssh key and initial scripts
19. for oracle:
touch /etc/oratab
chown oracle.dba /etc/oratab
copy from running system (if a client install only): /usr/local/bin files below:
-rwxr-xr-x 207 0 2413 Apr 12 15:17:10 2007 ./dbhome
-rwxr-xr-x 207 0 2545 Apr 12 15:17:14 2007 ./oraenv
-rwxr-xr-x 207 0 2316 Apr 12 15:17:17 2007 ./coraenv
20: Change the smtp server
21. Add to foglight,veritas,nessus
22. Create an entry for error reports to be sent to email.
chdev -l aio0 -P -a autoconfig=’available’
23. Set the maximum # of processes to be really big ( chdev -l sys0 -a maxuproc=90000 )
24. Set /etc/security/limits to be unlimited for oracle