|
|
You will want to synchronize the clocks on all of the hosts in the uOne system. The recommended method for doing so is to use the Network Time Protocol (NTP). You should use multiple redundant NTP servers to achieve high accuracy and reliability.
Your organization may operate private servers. If no public or private NTP server is available, a local server can act as a Stratum 1 server by using the IP address of 127.127.1.1. Other machines can then point to this machine.
The following table illustrates the recommended file system configuration for the gateserver.
| File System | Description | File System Type | File System Minimum (MB) | Suggested size (MB) for 9 GB hard disk and 512 MB RAM |
|---|---|---|---|---|
/ | Root file system | UFS | 800 | 2097 |
Swap Slice | swap | 2.5 x RAM + /tmp size | 2330 | |
Variables file system | UFS | 100 | 482 | |
File system for uOne | UFS | 2000 | 2616 | |
Temporary file system | TMPFS | 50 | 100 | |
Temporary file system | UFS | 300 | 448 |
The actual amount of hard disk space can vary slightly from one disk to another. Be sure that you use all of the available space on the drive taking care not to go below the levels specified in the File System Minimum column.
The /home2 file system should have a capacity of at least 800 MB. In addition, the /tmp file system should be created as a tmpfs file system with 100 MB capacity minimum. Larger /tmp capacity may be necessary if any of your Classes of Service (COS) permit many subscribers to receive large (> 3 minutes) voice messages.
You may have to borrow from the /home2 file system to accommodate the other minimums, but place as much available space as possible in the /home2 file system.
 |
Note Depending on the size of the hard disk, increase the file system sizes in the following order of priority: - /home2 - / - /var/tmp |
Be sure to apply the appropriate patches to Solaris 2.6. The web site is available in the Release Notes.
|
Note Use showrev -p to determine which Solaris patches are currently installed. |
The following settings should be present in the /etc/system file.
|
Note Prior to making the following changes, ensure that a copy of the original /etc/system file is preserved. |
We recommend that you use names instead of IP addresses when referring to hosts on the gateserver. It is best to use /etc/hosts as your primary means of name resolution and DNS (Domain Name Server) as your secondary means of name resolution. The use of NIS is discouraged. Take care to keep /etc/hosts consistent on all hosts. If you use DNS, be sure to:
|
Note The machine name cannot be longer than 15 characters. |
|
Note You cannot perform this procedure until the ACB has produced a $PARMLIB/parms/BASE/ObjectInfo.APP.<hostname> file. Thus you may have to return to this step later. Such a file is created by running the ACB on a host. This can be any host because the output in this file has to be consistent for all hosts. |
You can add one line to the /etc/rpc file for the ACB. This configures the ACB name so that it will be visible in the output of the rpcinfo command.
Note the following requirements when editing the /etc/rpc file. This assumes /etc/nsswitch.conf contains files for rpc.
DAP_ACB <RPC-number>
|
Note It is important that the RPC number correspondence be consistent on each host. Files that configure or display RPC numbers are /etc/rpc and $PARMLIB/parms/BASE/ObjectInfo.<object>.<hostname>. Be sure not to create inconsistencies between these files. |
The sendmail Daemon is on by default. This is used as a secondary SMTP MTA if the primary fails.
Posted: Mon Sep 25 20:24:00 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.