- About PTK
- Quick Start
- Guidance
- Preparing Configuration File
- Checking the System
- Deploy Database Cluster
- Manage Clusters
- Show Cluster List
- Show Cluster Status
- Start Database
- Stop Database
- Restart Database
- Rebuild Database
- Switchover
- Failover
- Show Plugin Information
- Install Plugins
- Upgrade Database
- Scale-out Cluster
- Scale-in Cluster
- Show Database HBA
- Set Database HBA
- Show Database Parameters
- Set Database Parameters
- Show Cluster Topology Configuration
- Show Cluster Meta Information
- Update Cluster Comment
- Update Database IP
- Role Management
- Install CM
- Uninstall CM
- Manage Cluster VIP
- Install MogHA Service
- Uninstall MogHA Service
- Rename Cluster
- Create Empty Cluster
- Throw Out A Node
- Takeover A Node
- Manage Cluster
- Uninstall Database Cluster
- Collect OS Information
- Download MogDB Installer
- Encrypt Sensitive Information
- Upgrade PTK
- PTKC
- Compatible With Higher Versions of MogDB
- Reference
- Samples of Configuration Files
- Commands
- ptk
- ptk completion
- ptk view-static-config
- ptk init-cluster
- ptk collect
- ptk rec-guc
- ptk cache
- ptk gen-ptkc
- ptk manage
- ptk demo
- ptk meta
- ptk version
- ptk self
- ptk gen-om-xml
- ptk env
- ptk gen-static-config
- ptk cluster
- ptk cluster createdb
- ptk cluster uninstall-compat-tools
- ptk cluster install-compat-tools
- ptk cluster install-mogila
- ptk cluster rename
- ptk cluster throwout
- ptk cluster takeover
- ptk cluster uninstall-cm
- ptk cluster install-cm
- ptk cluster gen-cert-files
- ptk cluster load-cm-vip
- ptk cluster del-kerberos-auth
- ptk cluster add-kerberos-auth
- ptk cluster uninstall-kerberos-server
- ptk cluster install-kerberos-server
- ptk cluster is-in-upgrade
- ptk cluster upgrade-rollback
- ptk cluster upgrade-commit
- ptk cluster upgrade
- ptk cluster demote
- ptk cluster promote
- ptk cluster refresh
- ptk cluster shell
- ptk cluster modify-comment
- ptk cluster show-config
- ptk cluster set-guc
- ptk cluster show-guc
- ptk cluster set-hba
- ptk cluster show-hba
- ptk cluster scale-out
- ptk cluster scale-in
- ptk cluster uninstall-mogha
- ptk cluster install-mogha
- ptk cluster list-plugins
- ptk cluster install-plugin
- ptk cluster inspect
- ptk cluster failover
- ptk cluster switchover
- ptk cluster build
- ptk cluster status
- ptk cluster restart
- ptk cluster stop
- ptk cluster start
- ptk uninstall
- ptk ls
- ptk install
- ptk exec
- ptk template
- ptk encrypt
- ptk checkos
- ptk download
- ptk candidate
- Troubleshooting
- FAQ
- Release Notes
- Community
- Appendix: YAML Syntax
Manage Cluster VIP
This document only describes how to manage VIPs for clusters with CM. For MogHA VIP configuration, please refer to this document.
What is a VIP
VIP stands for virtual IP, which does not correspond to a specific server or NIC, and can be bound to any server in the same network segment. Therefore, using a virtual IP to connect to the database service ensures that when the database is switched and the VIP is bound to a new primary node, there is no need to change the configuration of the service, which ensures the continuity of the service.
Prerequisites
When using load-cm-vip to operate on a cluster, the cluster must have CM installed.
Operation of VIP
PTK provides the functions of installing, uninstalling, and refreshing VIPs.
Operation command:
ptk cluster -n <CLUSTER_NAME> load-cm-vip --action ACTION --vip VIPOptions:
| option name | option type | description |
|---|---|---|
| --action | String | Action type for cm-vip, currently only support [install, uninstall, refresh] |
| --vip | String | The value of VIP, only required for install. |
QA
How to check if the installation is successful after installing VIP?
- Check to see if the install command reported any errors.
- Run
ptk cluster -n <CLUSTER_NAME> statusand see if the value ofactive_vipcolumn is as expected.
Does load-cm-vip have version requirements for MogDB?
There is a limitation that this command can only be executed on VIPs if the MogDB version >= 5.0.4.
How can I manage VIP with CM commands?
You can refer to this document to use CM commands to manage VIP.
Does cluster scale-in and scale-out affect VIPs?
No. If you use PTK to scale in or out a cluster, if VIP has been configured, PTK will refresh the cluster VIP configuration once to ensure that CM is configured correctly and available.
What is the maximum number of VIPs that can be configured?
The number of VIPs that can be configured depends on the number of network segments currently used by the cluster.