Issue

When starting Tibero Active Cluster Manager (TBCM) using VIP, the status field among HP CM (Cluster Manager) network_Parameters changes to unknown.

network_Parameters

interface    status    path   name
primary   unknown   0/0/1/0   lan0
primary   unknown   0/0/2/0   lan1
primary   unknown   0/0/4/0   lan2

Caution

If the status part of HP CM's network_Parameter is unknown, it is not possible to determine whether the interface is operating or stopped.

This occurs when the Cluster is in a stopped state and online disk addition to the Cluster is not possible.

This document explains how to identify abnormal cluster phenomena on HP servers and how to resolve them.

Solutions

1. Check Ethernet netmask

When using Tibero VIP in an HP Cluster environment, the netmask value of the OS NIC Interface is used. (This can be checked using the ifconfig command.)

ifconfig lan1

lan1: flags=2000000000001843<UP,BROADCAST,RUNNING,MULTICAST,CKO,TSO>
      inet 128.1.1.1 netmask fffff800 broadcast 192.168.0.1

Note

ffffff800 is a hexadecimal representation of 255.255.248.0.

2. Set appropriate parameters in $TB_SID.tip

Enter the LOCAL_CLUSTER_VIP_NETMASK parameter correctly in the $TB_SID.tip file.

LOCAL_CLUSTER_VIP=192.168.41.170
LOCAL_CLUSTER_NIC=lan1
LOCAL_CLUSTER_VIP_NETMASK=255.255.248.0 
LOCAL_CLUSTER_VIP_BROADCAST=192.168.0.1