1. Skip to Menu
  2. Skip to Content
  3. Skip to Footer>
Thursday Dec 13th     7:18 AM PST                                  

The Plan

PDF Print E-mail

Written by Greg King Sunday, 16 November 2014 00:00

DISCLAIMER! This document is nothing more than the musings of the author as he attempts to perform the stated tasks.  Conclusions and approaches
may very well be incorrect, inefficient, or otherwise outside of professionally accepted best practices. Use this document at your own risk! In this
document, screen outputs will be presented in green. Where keyboard input is required, the prompt will be in bolded red. # means you should be at the
super user prompt, $ means you should be at an
unprivileged
user prompt. Do not include these prompts in your input! The command to be typed will be
shown in blue.
# ls -al
means you type ls -al at the super user prompt.

The Plan
is to build the network illustrated below,  using SPARC based hardware, the Solaris 10u11 operating system, Sun Ray 5.3.1 server/client software and Dsee7 LDAP services.  The  goal is that we have a functioning and patchable network that  utilizes alternate boot environments, ZFS snapshots and flar imaging for backups and upgrades.





The Oracle Solaris Systems Administrator (OSSA) exams place a strong emphasis on knowing how to configure and maintain Solaris on the x86 (Intel cpu) platform.  While our  network drawing  does not specifically include an x86 system, at least one will be deployed in a workstation function.

We will not be using NIS or DNS, rather relying instead on the use of host files.   The naming convention for workstations and servers is as follows:

[DOMAIN][TYPE][INCREMENT]

Where domain is the subnet

Tyoe is the type of configured system:

ADM = administrative system which is basically the same image as the workstation, but includes the LDAP server and will be the syslog server for the respective domain.  The 15ADM box will also have the SUNRAY server software installed.

SRA and SRB = Servers

WS= Workstation

and increment is simply a count of that domain and type in the network.

From a functional standpoint, there is no difference between a workstation and server in this environment. As is the case with the multiple IP addresses for  the A servers , the naming significance is simply to emulate a scripting challenge.

The host file will look like this

10.0.0.52             solnas
24.43.164.140 saturn-public
192.168.10.10    10SRA
192.168.10.11    10SRA
192.168.10.12    10SRB
192.168.10.15    10ADM
192.168.10.25 10WS01
192.168.10.26 10WS02

192.168.11.10    11SRA
192.168.11.11    11SRA
192.168.11.12    11SRB
192.168.11.15    11ADM

192.168.12.10    12SRA
192.168.12.11    12SRA
192.168.12.12    12SRB
192.168.12.15    12ADM

192.168.13.10    13SRA
192.168.13.11    13SRA
192.168.13.12    13SRB
192.168.13.15    13ADM
  Solaris Lab
eXTReMe Tracker
Content View Hits : 264665