System Make and Model
* Make : Sun Microsystems, Inc. * Model : Ultra 24 Workstation
System Configuration
* Processor : Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz CPU 1 * Memory : 6-Gbytes * Disk : 250-Gbytes * Networking : 10/100/1000 Ethernet
Operating System
- Solaris Nevada (build 95). The use of Solaris Nevada is necessary as it provides many of the up to date software packages used by services in our Phase 1.0 demonstration environment. OpenSolaris was considered but was not chosen due to its lack of support for sparse-root non-global zones.
Disk Partition Table
Current partition table (original): Total disk cylinders available: 30391 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 1278 - 3827 19.53GB (2550/0/0) 40965750 1 swap wu 3 - 1277 9.77GB (1275/0/0) 20482875 2 backup wm 0 - 30390 232.81GB (30391/0/0) 488231415 3 unassigned wm 3828 - 6438 20.00GB (2611/0/0) 41945715 4 unassigned wm 6439 - 9049 20.00GB (2611/0/0) 41945715 5 unassigned wm 9050 - 19493 80.01GB (10444/0/0) 167782860 6 unassigned wm 19494 - 30390 83.48GB (10897/0/0) 175060305 7 unassigned wm 0 0 (0/0/0) 0 8 boot wu 0 - 0 7.84MB (1/0/0) 16065 9 alternates wu 1 - 2 15.69MB (2/0/0) 32130
The following is a description of the partitions:
- 0. Global Zone Root File System (UFS)
- 1. Global Zone Swap
- 2. Entire Disk
- 3. Alternate Root 1 (Allowing for Booting Multiple Versions of Solaris)
- 4. Alternate Root 1 (Allowing for Booting Multiple Versions of Solaris)
- 5. ZFS Pool 1 (test) - used for deployment testing
- 6. ZFS Pool 2 (pool) - used for development
ZFS Configuration
Ensure you have a ZFS pool called pool mounted as /pool.
# zpool list pool NAME SIZE USED AVAIL CAP HEALTH ALTROOT pool 83G 2.55G 80.5G 3% ONLINE - # zfs list pool NAME USED AVAIL REFER MOUNTPOINT pool 2.61G 79.1G 31K /pool
Network Configuration
- DHCP
e1000g0: flags=201104843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,ROUTER,IPv4,CoS> mtu 1500 index 2 inet 192.168.2.2 netmask ffffff00 broadcast 192.168.2.255 ether 0:14:4f:4a:9c:6b
There may be cases when the primary IP address needs to associated with some other network. If this is the case, then a virtual network (e1000g0:1) should be created and assigned the IP address of gateway. This address is used by the Global Zone Proxy Server to access the environment.
e1000g0:1: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
inet 192.168.2.2 netmask ffffff00 broadcast 192.168.2.255
Naming Services Configuration
- DNS - initially automatic from DHCP then modified to use non-global zone DNS servers. The modified version is:
domain isc-testbed.sun nameserver 192.168.2.211 nameserver 192.168.2.1
Software Configuration
- SUNWCall (Entire Software Distribution)
Netmasks Table
192.168.2.0 255.255.255.0
Hosts Table
# # Gateway # 192.168.2.2 gateway isc-gateway # # Zones # 192.168.2.101 web1 192.168.2.102 web2 192.168.2.103 web3 192.168.2.104 web4 192.168.2.105 web5 # 192.168.2.111 web-proxy1 192.168.2.112 web-proxy2 # 192.168.2.121 cache1 192.168.2.122 cache2 # 192.168.2.151 db1 192.168.2.152 db2 # 192.168.2.201 lb1 192.168.2.202 lb2 # 192.168.2.211 dns1 192.168.2.212 dns2 # 192.168.2.221 time1 192.168.2.222 time2 # 192.168.2.224 log1 192.168.2.225 log2 # 192.168.2.250 template 192.168.2.251 test # 192.168.2.254 mgt
Proxy Server Configuration
Since the IP addresses used in the demonstration environment are all RFC 1918 private addresses, it is necessary to deploy a proxy server in the Global Zone of the demonstration system. The Proxy Server Configuration allows for both a forward proxy (allowing the ISC testbed to access the Internet and other external content) as well as a reverse proxy (allowing external clients to access the ISC testbed). If the ISC testbed were to use public or otherwise reachable IP addresses, this proxy server would not be required.
(Optional) Implement the CoolStack workarounds.
cd / mkdir -p -m 755 /opt/coolstack chown root:root /opt/coolstack cd /usr/sfw/lib ln -s /usr/sfw/lib/libcrypto.so.0.9.8 libcrypto.so.0.9.7 ln -s /usr/sfw/lib/libssl.so.0.9.8 libssl.so.0.9.7