Search Type:
Search for:

Language:

Product:
Category:
No categories for selected product

How does PIM identify offline slave nodes?

Article ID: 6599 
Last Review: Sep,25 2009
Author: Kichigin Aleksey
Last updated by: Kichigin Aleksey APPLIES TO:
  • Parallels Virtuozzo Containers Tools
  • Virtuozzo Containers for Windows 4.0
  • Virtuozzo Containers for Linux 4.0

Resolution

PIMU400013 update introduces two values which allow to customize time how often Parallels Infrastructure Manager (PIM) checks slave nodes availability:

   1. The slave_ping_update_timeout option defines timeout of pings between from master to slave;
   2. The slave_ping_wait_timeout option defines how long master node waits response for ping request. Status of pinged slave node is set to offline If no answer  gained.

The default value of  slave_ping_update_timeout is 120 sec, slave_ping_wait_timeout is 20. Guarantied time of detection of a slave server disconnection is slave_ping_update_timeout + slave_ping_wait_timeout seconds, by default it is 140 sec.

1. How to change the timeouts parameters by using PMC:

    By default slave_ping_update_timeout and slave_ping_wait_timeout parameters do not exist. To add them open PMC, right click on the node and choose Tasks, Manage Parallels Agent Configuration, select server_group, configuration, in the right pane add both parameters, Click Apply.

   Note: vzagent service restart is not required.

2. How to change the timeouts parameters in vzagent.conf file:

    2.1 Open vzagent.conf file

        on Windows node  - x:\vz\VZAgent\etc\vzagent.conf, where x:\ is drive where VZ folder is located,
        on Linux node - /var/vzagent/etc/vzagent.conf
 
    2.2 Add slave_ping_update_timeout and slave_ping_wait_timeout parameters:
 
        <data>
        <server_group>
        <configuration >
            <slave_ping_update_timeout>120</slave_ping_update_timeout>
            <slave_ping_update_timeout>20</slave_ping_update_timeout>

        < /configuration >
        </server_group>
        </data>

    2.3 Save vzagent.conf file;

    2.4 Restart VZAgent service by means service snap-in or this command on Windows: sc stop vzaop &sc start vzaop and that one on Linux: vzagent_ctl restart


Subscription for changes to this article Subscription for changes to this article

Please provide feedback on this article

Did this article help you solve your issue?
Yes
No
Partially
I do not know yet
 
Strongly Agree   Strongly Disagree
  9 8 7 6 5 4 3 2 1
The article is easy to understand
The article is accurate
Additional Comments:
*Please provide us with your email address in case we need to contact you.
* - required fields
 
 
 
 
 
 
For Home
For Business
For Hosters
For SaaS
For Developers
 
Desktop Virtualization
- Parallels Desktop Switch to Mac Edition
- Parallels Desktop for Mac
- Parallels Desktop 4 for Windows & Linux
- Parallels Workstation Extreme
- Parallels Solution for Windows 7
Server Virtualization
- Parallels Server for Mac
- Parallels Server 4 Bare Metal
- Parallels Virtuozzo Containers
Automation
- Parallels Operations Automation
- Parallels Business Automation
- Parallels Virtual Automation
- Parallels Plesk Panel Suite
More Products