Skip to main content
๐Ÿ““ Tibero Online Manual Click here ๐Ÿ““

Search

Welcome to Tibero GTS!

Explanation of CM RESOURCE Statuses

Document Type | Technical Information

Category | Administration

Applicable Product Version | 7FS02PS

Document Number | TADTI052

 

Overview

This explains the differences between CM RESOURCE statuses. 
 

Method

Difference between CM RESOURCE DOWN / DEACT

DOWN status: The resource is not in use because there is no operation on it.
DEACT status: It is the same as DOWN status, but it does not accept the START command either. 
A CM RESOURCE in DEACT status is outside CM control and does not perform any operations.

 

Cases when RESOURCE becomes DEACT

  1. When start could not be performed even after retrying retry cnt times
  2. When the user explicitly deactivated it
 
When a RESOURCE reaches DEACT status, the user must identify and resolve the boot failure cause and then change it to DOWN status with the act command.
Note
If a resource in DEACT status is a VIP, inbound/outbound communication is allowed but it means it is outside CM's control. Resources removed from cluster management need inspection.

 

When VIP is displayed in INTR (INTERRUPT) status

When a VIP fails over to another node due to a DB failure, the following procedure is followed.
  1. Pre-work (VIP release operation)
  2. VIP release (release)
  3. Post-work (post-processing such as flag cleanup)
  • If interrupt status is set to CM_INTR_NOTI at the start of Pre-work, the VIP status is displayed as INTR.
  • When a Post-work message is received, the interrupt status switches to CM_INTR_COMMIT and the VIP status is displayed as UP(R). In other words, the INTR status means the VIP is in an interrupt state during failover.


When VIP is displayed in UNKNOWN status

If the cluster is down due to an Interconnect Network down failure and a COMMIT for VIP failover is not received, it is unknown whether the VIP is operating normally on another node, so the VIP status is displayed as UNKNOWN. If the cluster is operating normally, a COMMIT message is received and the VIP status is displayed as UP(R).
Note
Logs related to VIP pre/post work 
Check the trace_cm.log file in the CM_LOG_DEST path specified in the cm tip file.
cm_act_s:0277(03) [cls] [VIP] Need failback VIP 'tac2_vip' from node 1 to 2
cm_act_s:0303(03) [cls] [VIP] New NOTI for vip 'tac2_vip'
cm_actio:6421(03) [cls] [VIP] Release VIP 'tac2_vip' for node 2
cm_actio:6011(03) [cls] [VIP] (tac2_vip) prework start! vip:192.168.56.21, port:8629 (svc: tac)
cm_actio:3525(03) [cls] [INST] VIP_LOST msg
cm_actio:3943(03) [cls] [VIP] (tac2_vip) prework done! vip:192.168.56.21, port:8629 (svc: tac)
cm_util.:0395(03) [cls] start exec ifconfig ens33:2 down
cm_util.:0415(03) [cls] exec ifconfig ens33:2 down success. exit status 0
cm_vip.c:0661(03) [cls] VIP 192.168.56.21 removed from ens33:2
cm_actio:5039(00) cmd execution rc: 0 (100 < rc < 106)
cm_actio:5154(00) Resource `tac2_vip` down SUCCESS
cm_act_s:0327(03) [cls] [VIP] COMMIT for vip 'tac2_vip'
cm_act_s:0394(03) [cls] [VIP] (tac2_vip) postwork for vip:192.168.56.21, port:8629 (svc: tac)

 

 

 

Related to