Transcript
KVM.net Manager Slave Quick Installation Guide
w w w . m i n i c o m . c o m
International HQ
North American HQ
European HQ
Jerusalem, Israel
Linden, NJ, USA
Dübendorf, Switzerland
Tel: + 972 2 535 9666
[email protected]
Tel: + 1 908 4862100
[email protected]
Tel: + 41 44 823 8000
[email protected]
Customer support -
[email protected] 5UM70164 V1 1/06
QUICK GUIDE
Introduction The KVM.net Manager Slave (Slave) replicates all data from the KVM.net Manager Master (Master). In the event of a failure in the Master, the Slave can take over, and operate with the most up to date database. The Master is designed to fully operate and serve KVM.net users, while the Slave detects any changes and replicates all data. Running a script from the command line promotes a Slave to a primary operational Manager.
Connecting the Slave to the network The Slave must reside on the same network segment as the Master. 1.
Connect the KVM.net Slave to a power supply outlet.
2.
Connect the KVM.net Slave to the network as follows: On the rear panel connect an Ethernet cable to LAN 1
3.
Connect a local keyboard and monitor to the KVM interface on the KVM.net Slave rear panel.
4.
Power up KVM.net Slave – after about 2 minutes the login prompt appears
5.
Login with the default user credentials root / access.
Setting the Slave IP address There are 2 possible ways of obtaining an IP address for the KVM.net Slave: (1) Obtaining an IP address via DHCP
If a DHCP (Dynamic Host Configuration Protocol) server exists on the network where KVM.net Slave is installed, the unit boots with an automatically assigned IP address. To view the IP address obtained from a DHCP server: Type ifconfig eth0 and press Enter. The IP address appears. (2) Configuring a Static IP Address
To avoid a network conflict the Master and Slave must have different IP Addresses. To configure a static IP address: 1. Type “netconfig” and press Enter. A confirmation dialog appears. 2. Click Yes. A network configuration screen appears. 3. Enter the IP address, Default Gateway, and Netmask, obtained from your System Administrator. 1
KVM.NET SLAVE
4. Press OK. The command prompt appears. 5. Type Service network restart for the IP changes to take affect. Or, type reboot for the unit to restart with its new IP parameters. When first connecting a Slave to the system you must configure both the KVM.net Manager units to determine the Master/Slave relationship. This is now explained.
Configuring the Slave unit Configure the Slave as follows: At the Slave, command prompt: ·
type: cd /replicom/scripts [Enter]
·
type: ./be_slaver.sh [Enter] The following appears:
·
Stopping slapd:
[OK]
Stopping slurpd:
[OK]
Stopping httpd:
[OK]
Stopping tomcat5:
[OK]
Please enter Master server IP: “x.x.x.x” [Enter] <= Enter the IP Address of the KVM.net Master unit here
Configuring the Master unit When you connect a Slave to the system you must configure the Master as follows: At the KVM.net Master local console command prompt: ·
type: cd /replicom/scripts [Enter]
·
type: ./be_master.sh [Enter] The following appears:
·
Stopping slapd:
[OK]
Stopping httpd:
[OK]
Stopping tomcat5:
[OK]
Please enter slave IP: “x.x.x.x” [Enter] <= Enter the IP Address of the KVM.net Slave unit here 2
QUICK GUIDE
Promoting a Slave to a primary operational Manager When a Master unit is down, you can promote the Slave to be a primary operational Manager by running the following script from the local console of the Slave. ·
type: cd /replicom/scripts [Enter]
·
type: ./be_stand_alone.sh [Enter] The following appears: Stopping slapd:
[OK]
Stopping httpd:
[OK]
Stopping tomcat5:
[OK]
Starting slapd:
[OK]
Starting httpd:
[OK]
Starting tomcat5:
[OK]
Important IP Access configuration information Check the KVM.net section of the IP Access Network Configuration window (HTTPS://IP address/config/), see below.
If the system’s IP Access units have a static IP address entered for the KVM.net Manager and are not set to Manager Auto Discovery, you must change the IP address of the new KVM.net Manager unit to the address of the unit you replaced. To do so, use the “Netconfig” command (see above). The new KVM.net Manager is now operational. Reconfiguring the Master and Slave
Once the original Master unit is functioning again, you can set it up as a replicating unit to the current primary Manager. Before you begin, you must align the database contents. To do so, repeat the steps set out in this guide to reconfigure the Master and Slave units.
3
