06-10-2009
It depends what way you implement it.
You can do the simplest method which it to multi-home the server on all subnets, use dhcp jumpstart with DHCP relaying enabled in your network or use WAN boot.
In general the hardware is not that important. You just need to have enough network interfaces / bandwidth, processing power and storage space to handle your requirements. Anything you can install Solaris on will work as the server.
10 More Discussions You Might Find Interesting
1. Solaris
Hi everybody,
I am trying to clone Solaris 10 with applications to another server.
The total amount of data of jumpstart image is larger than a single dvd disk.
Any ideas if it is possible to split image to several dvds and then use them to install cloned os on another server?
I want to avoid... (2 Replies)
Discussion started by: jarek
2 Replies
2. Solaris
Hi Guys,
I want to configure Jumpstart server in x86, but i am not able to see my cd drive. and i am not able to mount also, my partition looks like this. and i cannot see this file ./setup_install_server -b, but i can see in windows when i open the cd in windows i can see the... (2 Replies)
Discussion started by: kurva
2 Replies
3. Solaris
Could someone assist me with the following issue. Recently I downloaded a document that walked me through creating a Solaris 10 Sparc jumpserver. It was only when I tried to use the server to push an OS to a client box when I realized that the document was a step by step intrcutions for a Solaris... (3 Replies)
Discussion started by: kass_k
3 Replies
4. IP Networking
Hello all,
I have configured Freebsd 8.1 Bind DNS as DNS server for intrenal domain and clients on one subnet 192.168.10.0/24 . What do I have to change in zone file and in in-addr.arpa zone file if I have two additional subsets 192.168.20.0/24 and 192.168.30.0/24? Do I have to create another... (0 Replies)
Discussion started by: kreno
0 Replies
5. Solaris
We have a WAN boot jumpstart server which works fine .. we have a requirement wherein we would require to jumpstart multiple sparc servers simultaneously, Whats the way .. so that we do not have to wait for a cleint to complete the installation before starting with another server.
Any help would... (1 Reply)
Discussion started by: fugitive
1 Replies
6. Solaris
Hello,
I 've a jumpstart configured, its working fine .. i can build servers from this jumpstart server but i want to build 2-3 servers from the same jumpstart server simultaneously, and since i have only one sysidcfg i can only build 1 server at a time. My question is which file i shuld use for... (4 Replies)
Discussion started by: fugitive
4 Replies
7. IP Networking
We have two subnets, say 'domA' (192.168.0.0/24) and 'domB' (10.10.0.0/16). These subnets are connected through the router 'router01'. One server 'base01' has two network cards, configured to domA and domB subnets respectively.
Now let's consider a host host01.domA (192.168.0.5) trying to... (0 Replies)
Discussion started by: amriksk
0 Replies
8. UNIX for Advanced & Expert Users
Hello,
I have a rsyslog server configured on a server with two IP's on different Class C subnets. By default, it receives all logs from servers on these two subnets. The problem I have is that I want the Rsyslog server to monitor other subnets as well. Is there anyway to do this? I have searched... (0 Replies)
Discussion started by: mojoman
0 Replies
9. Solaris
Hello,
Can anyone share a good online article/tutorial on how to properly set up JumpStart server for Solaris 10?
Thanks,
Regards. (3 Replies)
Discussion started by: NewSolarisSquad
3 Replies
10. AIX
Hi Guys,
I'm building a new NIM environment with clients on 3 different subnets. I want to get some advise on what is the best approach for this kind of setup.
This is the sample network for my new NIM.
Master IP: 10.20.1.20
Client IP subnet_1: 10.20.1.21
Client IP subnet_1: 10.30.1.21... (5 Replies)
Discussion started by: kaelu26
5 Replies
dhcp(5) Standards, Environments, and Macros dhcp(5)
NAME
dhcp - Dynamic Host Configuration Protocol
DESCRIPTION
Dynamic Host Configuration Protocol (DHCP) enables host systems in a TCP/IP network to be configured automatically for the network as they
boot. DHCP uses a client/server mechanism: servers store configuration information for clients, and provide that information upon a
client's request. The information can include the client's IP address and information about network services available to the client.
This manual page provides a brief summary of the Solaris DHCP implementation.
Solaris DHCP Client
The Solaris DHCP client is implemented as background daemon, dhcpagent(1M). This daemon is started automatically during bootup if there
exists at least one dhcp.interface file in /etc. Only interfaces with a corresponding /etc/dhcp.interface file are automatically configured
during boot. Network parameters needed for system configuration during bootup are extracted from the information recieved by the daemon
through the use of the dhcpinfo(1) command. The daemon's default behavior can be altered by changing the tunables in the /etc/default/dhc-
pagent file. The daemon is controlled by the ifconfig(1M) utility. Check the status of the daemon using the netstat(1M) and ifconfig(1M)
commands.
Solaris DHCP Server
The Solaris DHCP server is implemented as a background daemon, in.dhcpd(1M). This daemon can deliver network configuration information to
either BOOTP or DHCP clients. The Solaris DHCP service can be managed using the dhcpmgr(1M) GUI or the command line utilities dhcpcon-
fig(1M), dhtadm(1M), and pntadm(1M).
DHCP Configuration Tables
The Solaris DHCP server stores client configuration information in the following two types of tables:
dhcptab tables Contain macros and options (also known as symbols), used to construct a package of configuration information to
send to each DHCP client. There exists only one dhcptab for the DHCP service. The dhcptab(4) can be viewed and mod-
ified using the dhtadm(1M) command or dhcpmgr(1M) graphical utility. See dhcptab(4) for more information about the
syntax of dhcptab records. See dhcp_inittab(4) for more information about the DHCP options and symbols.
DHCP network tables DHCP network tables, which contain mappings of client IDs to IP addresses and parameters associated with those
addresses. Network tables are named with the IP address of the network, and can be created, viewed, and modified
using the pntadm command or dhcpmgr graphical utility. See dhcp_network(4) for more information about network
tables.
SEE ALSO
dhcpinfo(1), dhcpagent(1M), dhcpconfig(1M), dhcpmgr(1M), dhtadm(1M), ifconfig(1M), in.dhcpd(1M), netstat(1M), pntadm(1M), syslog(3C),
dhcp_network(4), dhcptab(4), dhcpsvc.conf(4), dhcp_inittab(4), dhcp_modules(5)
Solaris DHCP Service Developer's Guide
Alexander, S., and R. Droms. RFC 2132, DHCP Options and BOOTP Vendor Extensions. Silicon Graphics, Inc. Bucknell University. March 1997.
Droms, R. RFC 1534, Interoperation Between DHCP and BOOTP. Bucknell University. October 1993.
Droms, R. RFC 2131, Dynamic Host Configuration Protocol. Bucknell University. March 1997.
Wimer, W. RFC 1542, Clarifications and Extensions for the Bootstrap Protocol. Carnegie Mellon University. October 1993.
SunOS 5.10 13 Mar 2001 dhcp(5)