Practices Overview
Practice 3-2: Configuring the AI Server
Overview
After you have verified that the server meets the AI requirements, you are ready to configure the AI server. After the configuration is complete, you will be able to install the Oracle Solaris 11 OS on one or more client hosts. This practice will set up a DHCP server as part of the configuration. This DHCP server allocates an IP address to the client host.
Tasks
Note: Because you are not using the default IPS service, you will need to adjust the default AI service accordingly.
1. On the Sol11-Server1 virtual machine, check whether the
svc:/network/dns/multicast service is online. If the service is not online, enable it. root@s11-serv1:~# svcs network/dns/multicast
STATE STIME FMRI
disabled 1:08:14 svc:/network/dns/multicast:default root@s11-serv1:~# svcadm enable network/dns/multicast root@s11-serv1:~# svcs network/dns/multicast
STATE STIME FMRI
online 1:32:27 svc:/network/dns/multicast:default
2. Verify that the netmasks file is configured appropriately for the DHCP service. root@s11-serv1:~# getent netmasks 192.168.0.0
Note that DHCP requires that the network mask for the local subnet should be
configured in the /etc/netmasks file. If an entry does not exist, update the netmasks file now.
# vi /etc/netmasks …
192.168.0.0 255.255.255.0
root@s11-serv1:~# getent netmasks 192.168.0.0 192.168.0.0 255.255.255.0
3. Use the installadm create-service command to create an AI service based on the
following information:
- Service name: basic_ai
- DHCP base IP address: 192.168.0.130 - DHCP IP address range: 5
- AI ISO image location: /opt/ora/course_files/sol-11-dev-173-ai-x86.iso
- Target directory: /export/ai/basic_ai
root@s11-serv1:~# installadm create-service -n basic_ai \
-s /opt/ora/course_files/sol-11-dev-173-ai-x86.iso \
Oracle Internal & Or
-i 192.168.0.130 -c 5 -d /export/ai/basic_ai
Creating service from: /opt/ora/course_files/sol-11-dev-173-ai- x86.iso
Setting up the image ...
Creating service: basic_ai
Image path: /export/ai/basic_ai
Starting DHCP server...
Adding IP range to local DHCP configuration
Unable to determine a route for network 192.168.0.0. Setting the route
temporarily to 0.0.0.0; this should be changed to an appropriate value
in the DHCP configuration file. Please see dhcpd(8) for further information.
Refreshing install services
Creating default-i386 alias.
Setting the default PXE bootfile in the local DHCP configuration to
'default-i386/boot/grub/pxegrub'
Refreshing install services
Note: If a warning message “Unable to determine a route…” appears, ignore it because it is caused by the virtual machine network configuration. The same is true for any other warnings. However, these messages have no impact on this practice.
Note: If you need to, you can remove an AI service and its associated clients by using the command installadm delete-service -r svcname.
4. Use the installadm list command to verify that your AI service is installed.
root@s11-serv1:~# installadm list
Service Name Alias Of Status Arch Image Path --- --- --- ---- ---
default-i386 basic_ai on x86 /export/ai/basic_ai basic_ai - on x86 /export/ai/basic_ai
Oracle Internal & Or
5. Use the installadm create-client command to add the client MAC address for the Sol11-Client1 virtual machines to the basic_ai service.
root@s11-serv1:~# installadm create-client -e \
08:00:27:85:C7:D6 -n basic_ai
Adding host entry for 08:00:27:85:C7:D6 to local DHCP configuration.
Note that, on the job, you will not encounter duplicate MAC addresses on your network. You should verify carefully what your actual network client systems' MAC addresses are in order to properly install Oracle Solaris 11 on them.
6. Use the installadm list –c command to verify that the client was added to the AI
server basic_ai.
root@s11-serv1:~# installadm list -c
Service Name Client Address Arch Image Path --- --- ---- ---
basic_ai 08:00:27:85:C7:D6 i386 /export/ai/basic_ai
7. Create the directory /var/tmp/manifests to store the AI manifest files.
root@s11-serv1:~# mkdir -p /var/tmp/manifests
8. Copy the default manifest file to the /var/tmp/manifests/basic_ai.xml file so that you can modify it for your configuration.
root@s11-serv1:~# cp \
/export/ai/basic_ai/auto_install/manifest/default.xml \
/var/tmp/manifests/basic_ai.xml
9. Using the vi editor, modify the auto_install section of the
/var/tmp/manifests/basic_ai.xml file and use the following data. auto_install manifest:
- AI instance name (ai_instance name): basic_ai
- Auto-reboot (auto_reboot): true
- IPS origin URI: http://s11-serv1.mydomain.com
- IPS package: entire (confirm it uses the entire package)
- IPS package: solaris-large-server (confirm it uses the solaris-large-
server package)
10. Use the diff command to view the differences between the basic_ai.xml file and the default.xml file.
root@s11-serv1:~# diff /var/tmp/manifests/basic_ai.xml \ /export/ai/basic_ai/auto_install/manifest/default.xml 27c27
< <ai_instance name="basic_ai" auto_reboot="true" > ---
> <ai_instance name="default">
Oracle Internal & Or
40c40
< <origin name="http://s11-serv1.mydomain.com"/> ---
> <origin name="http://pkg.oracle.com/solaris/release"/>
This output shows you the modifications that you made to the basic_ai.xml file. 11. Create a MAC address–based criteria file named criteria_ai.xml in the
/var/tmp/manifests directory. Use the MAC address of the network client Sol11- Client1. root@s11-serv1:~# vi /var/tmp/manifests/criteria_ai.xml <ai_criteria_manifest> <ai_criteria name="mac"> <value>08:00:27:85:C7:D6</value> </ai_criteria> </ai_criteria_manifest>
Note: If the AI client does not match the criteria for a service (in this case, a specific MAC address), the AI service will use the default manifest when installing the OS. 12. Add the basic_ai manifest and criteria file to the basic_ai service.
root@s11-serv1:~# installadm create-manifest –n basic_ai \ -f /var/tmp/manifests/basic_ai.xml \
-C /var/tmp/manifests/criteria_ai.xml
When a custom AI manifest (basic_ai.xml, in this example) is defined for this install service and the client matches the criteria specified (in the criteria_ai.xml file) for the custom AI manifest, the client will use that manifest. In cases where client
characteristics match multiple AI manifests, the client characteristics are evaluated in the order: mac, ipv4, platform, arch, cpu, and mem.
If the client does not match the criteria for any custom AI manifest, the client uses the default AI manifest.
13. Use the installadm list –m command to verify that your manifest and the criteria have been added to the basic_ai service.
root@s11-serv1:~# installadm list -m
Service Name Manifest Status
--- --- ---
default-i386 orig_default Default
basic_ai basic_ai
orig_default Default
root@s11-serv1:~# installadm list -m -n basic_ai Manifest Status Criteria
--- --- ---
basic_ai mac = 08:00:27:85:C7:D6 orig_default Default None