Production to DR switch


 
Thread Tools Search this Thread
Special Forums IP Networking Production to DR switch
Prev   Next
# 1  
Old 02-07-2013
Network Production to DR switch

Hi,

I have application server on IP 10.10.220.42 (Prod).

When the Production goes down I wish to switch over all my application server's configuration files onto IP 10.10.220.45 (DR).

The client is exposed to proxy apache http webserver running @ IP 10.10.220.30

Can you please suggest what configuration change needs to go in where inorder to achieve Prod -> DR switch ?
 
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. BSD

Copying OpenBSD Kernel from a non production to production machine

Hi All, There are few OpenBSD 4.8 servers without compiler installed at my working place. However, sometimes there are some patches released for patching the kernel. My question is: Can I setup a non production OpenBSD 4.8 server as a test machine with compiler installed and use it to... (1 Reply)
Discussion started by: lcxpics
1 Replies

2. UNIX for Dummies Questions & Answers

To know the server which the production is pointing to?

Hi, How to know which server(Application or webserver) the production link or url is pointing to? Is there any command to get the server IP address? Thanks in advance. (3 Replies)
Discussion started by: venkatesht
3 Replies

3. Shell Programming and Scripting

how to access console of a switch having rj45 on switch side to db 9 female on pc side console cable

hi, how to access console of a switch having rj45 on switch side to db 9 female on pc side console cable which needs to be connected to one console server having rj11 on its side and db 9 female on other end.i.e. on switch side,console cable has rj45 and db 9 pin female connector on other side of... (1 Reply)
Discussion started by: pankajd
1 Replies

4. UNIX for Dummies Questions & Answers

need help.. ! Production Env.

Hi ! I want to delete a softlink... with a name.. " -> ALCATEL " FYI:- lrwxrwxrwx 1 infomcm develop 32 Dec 3 2007 COX -> /wlsuite/om/cm/build/sandbox/COX lrwxrwxrwx 1 infomcm develop 33 Jul 21 05:52 WL10 -> /wlsuite/om-cm/build/sandbox/WL10 lrwxrwxrwx 1... (2 Replies)
Discussion started by: dashok.83
2 Replies
Login or Register to Ask a Question
dhcpparm(8)						      System Manager's Manual						       dhcpparm(8)

NAME
dhcpparm - Daemon for client configuration SYNOPSIS
/usr/sbin/dhcpparm [-i interface] tag | symbol | name OPTIONS
Use this option on hardware that has two or more interfaces configurable by the Dynamic Host Configuration Protocol (DHCP), and for a parameter that is interface specific. When no interface is specified, the client daemon returns the name of the first interface it finds on which DHCP has successfully completed: the value(s) displayed will be those of the configuration received on that interface. DESCRIPTION
The dhcpparm command displays the value(s) of the parameter requested on the command line as supplied by the DHCP protocol. If the DHCP parameter implies more than one value (for example, a list of gateways), the values are displayed separated by newline characters. The parameter may be identified either by its numeric value in the DHCP protocol, by its two character symbol, or by its long name. The dhcp- parm command is intended to be used in command substitutions in the shell scripts invoked by init at system boot. It first contacts the DHCP client daemon (joinc) to verify that DHCP has successfully completed. When the -i option specifies a particular interface, the daemon verifies successful DHCP configuration of that interface; otherwise, the client verifies that at least one interface is successfully con- figured, and supplies the name of that interface to dhcpparm. Parameter values echoed by dhcpparm should not be used without checking exit status. See the EXIT STATUS section below. RESTRICTIONS
A cluster member should never be a DHCP client; it should always use static addressing. If a cluster is to support a DHCP server, there can only be one DHCP server for all the cluster members using a common database with failover. If a cluster is to support a DHCP server, there can only be one DHCP server for all the cluster members using a common database with failover. DHCP client is not supported on dataless clients. SYMBOLS
See dhcptags(4) for the list of two letter symbol codes and names of all DHCP parameters. See RFC 1533 for more detail. EXIT STATUS
Exit codes are as follows: Success. DHCP was not successful. The DHCP client daemon may not be running, the interface might have failed to configure, or no satisfactory DHCP responses were received. Bad arguments. A timer was set and the interface had not configured before it expired. Can only be run as root. Some system error (should never occur). SEE ALSO
Commands: dhcpconf(8), joinc(8), showdhc(8), shleases(8) Files: client.pcy(4), dhcptags(4) RFC1533 dhcpparm(8)