Basic Administrator Guide for EverRun MX

Table of Contents

1. Using everRun Availability Center (eAC)
1.1 everRun Availability Center 1.2 eAC Icons 1.3 eAC Componet Icons 1.4 Monitoring PVM Information 1.5 Event & Error Logs	Page 3 Page 4 Page 5 Page 6-14 Page 15
2. Proper way of Shutting down and Power Up of Servers
2.1 Shutting down of Server 2.2 Power on Server	Page 16 Page 18
3. Maintenance
3.1 Collecting everRun 2G Logs 3.2 For physical Server RAID5 degraded 3.3 For Network Card failure 3.4 In the event of a XenServer system failure 3.5 Change Root Password for XenServer 3.6 everRun Support	Page 19-21 Page 22 Page 22 Page 22 Page 22 Page 22
Appendix A
Network Diagram	Page 23

1.   Using everRun Availability Center (eAC)

1.1 everRun Availability Center

The everRun management environment is called everRun Availability Center (eAC).

eAC is used for everRun specific monitoring and management of redundant virtual I/O devices and everRun protected virtual machines.

Figure 1

Use an Internet browser (Internet Explorer 6 and above, FireFox 2.0 and above) to login to the pool master as shown Figure 1

IP Address to access the eAC (1 Pool of Servers consist of 1 Master Server and 1 Member Server)

Pool Master for Card Access Server: Either http://x.x.x.x:8080 or y.y.y.y:8080

Pool Master for CCTV Server: Either http://x.x.x.x:8080 or y.y.y.y:8080

Login Username: root

Password: dontaccess

1.2 eAC Icons

The everRun Availability Center contain a number of icons that make it easy to quickly review the status of the components and systems in your XenServer resource

pool(s).

Figure 2

Status Icons indicate the operating state of the resource.

Power Status Icons indicate the power state of the resource and the transition icons display when a resource is changing from one state to another.

1.3 eAC Componet Icons

Figure 3

Refer to Figure 3, the everRun Availability Center uses a number of icons that make it easy to quickly identify the status of each resource in your XenServer pool. In each case, the icon combines a component icon (host, VM, PVM, compute instance, or resource pool) with a status icon that identifies the condition of the component. For instance, in the host and machine icons shown above, the XenServer host displays a Warning icon, the virtual machines have Running icons, and the compute instance includes a Protected icon.

1.4 Monitoring PVM Information

Go to the Virtual Machines Status tabs and select the PVM to check system health.

Compute instance, Adapter and Disk should be green tick.

Refer to Figure 4 – 6, by hovering the mouse over an icon, you can obtain configuration information about the component(s) represented by the icon. You can hover over Compute Instances, Adapter and Disk.

Figure 4

Figure 5

Figure 6

Figure 7

Refer to Figure 7, you can monitor the status of the disk mirror copy by clicking the Mirror Copy Status tab. When the copy is complete, you can view details of device status, copy rates, and elapsed time by hovering the mouse over the disk icon to display the pop-up message.

This status show whether the data for both Master and Member Server has synchronized properly. It is important that the status shown Complete in order for redundancy to function.

Figure 8

Availability Links Tab (Figure 8)

Configuration details for each of your A-Link networks can be reviewed here. The details in the bubble text confirm which physical NIC is used and how the IP networking was setup.

Hover over A-Link and review the bubble text:

•         Observe the network details for this network

•         Physical Xenbr(s) comply with configuration rules

Figure 9

The Virtual Machine Status table presents information about all system resources. You can click the heading in each column to sort the data in that column.

Status contains an icon that visually indicates the overall status of the resource.

Name lists all the resources according to the name assigned when the XenServer host or virtual machine (VM) was initially set up.

Figure 9. Virtual Machines Status Tab

1 Status: indicates overall status of VM or PVM

2 Name: name assigned in XenServer

3 Protect Level: VMs protection level

4 Candidacy: type of protection available

5 Power: power status of VM or PVM

6 Hosts: name of host/s VM or PVM

7 Pool: resource pool where XenServer host is located

Figure 10

Refer to Figure 10, the everRun Log tab displays status/log information for running tasks such as PVM start, migration, or mirror copy.

The everRun log stores the first 50 events following eAC startup. When the log exceeds 50 events, the oldest events are discarded first.

The everRun log display incorporates data for each everRun task, including the task name, the start time, the task status, a task progress bar and detailed, step-by-step task status information as the task progresses.

Figure 11

To monitor your pool resources, open the Hosts tab as shown n Figure 11, in the eAC navigation tree, then highlight the line that contains the pool icon.

The Hosts tab shows the resource pool icon at the top of the list. When you highlight the pool name, the Detail tab at lower right shows resource information for the pool.

You see the pool name, pool members, hardware configured, everRun license and version number, and relevant informational messages.

Figure 12

Figure 12. Online Help

You can invoke online help from any page on the site via the help menu by then clicking “Contents”, “Index” or “Search”. Online help is available from any page (menu)

1.5 Event & Error Logs

Refer to Figure 13, each Windows PVM maintains its event log like any other Windows system. Marathon events are generated and logged in the system log along side other events.

Figure 13

2.   Proper way of Shutting down and Power Up of Server

2.1 Shutting down of Server

Right click and select Shutdown on the Windows 2003 VM. (Figure 14)

Figure 14

Always shutdown the member XenServer first then the master XenServer.

Refer to Pg13 on how to determine which XenServer host is Pool Master. (Important)

From the Hosts tab in the eAC right-click the XenServer and select shutdown.

(Figure 15)

Figure 15

2.2 Power on Server

After power on the pair of XenServer, login to eAC to start the Virtual Server. (Figure 16)

Right click and select Start on the Windows 2003 VM

Figure 16

3.   Maintenance

3.1 Collecting everRun 2G Logs

Use XenServer console or SSH to the server as shown below.

Do this for the master XenServer first then on the member XenServer.

Go to the directory :

type

“cd /var/everRun/everRun-5.1.1HF8/bin”

Run the script:

type

“./mtc_log_collector.sh”

Plug in a usb disk to the XenServer

Type “fdisk –l” to identify your usb disk

Type “mount -t vfat /dev/sda1 /mnt” (if usbdisk is /dev/sda1)

Type “cp /var/everRun/current_everRun/log/MtcLogs/MtcLogs.xenHost2A.20090124130145.tgz /mnt” to copy logs to your usb disk

Type “umount /mnt” to unplug your usb disk.

Then collect the log for the other XenServer

3.2 For physical Server RAID5 degraded

Shutdown affected XenServer.

Replace faulty HDD and power up XenServer to rebuilt RAID5 volume.

Monitor everRun mirror copy status from eAC. (Refer Pg 9)

3.3 For Network Card failure

Shutdown affected XenServer

Replace with same model Network Card. Power up XenServer.

Verify XenServer network configuration.

eth 0 : Management NIC

eth 1 : A-Link 1

eth 2 : A-Link 2

eth 3 : VM NIC

Monitor everRun network links and disk copy status from eAC. (Refer Pg7-10)

3.4 In the event of a XenServer system failure

Replace faulty hardware.

Install XenServer and everRun software of the correct versions.

Recommended to call RoyceMedia for assistance.

3.5 Change Root Password for a XenServer Host

SSH in to XenServer and use

passwd

(note to change both XenServer in the pool)