Document Type | Troubleshooting
Category | Installation
Document Number | TINTS015
Issue
When starting Tibero Active Cluster Manager (TBCM) using VIP, the HP CM (Cluster Manager) Status
network_Parameters interface item changes to unknown.[cmviewcl -v : Check HP Cluster Status]
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
- If the network_Parameter section of HP CM is unknown, it is not possible to determine whether the interface is operational.
- This state occurs when the Cluster is stopped, and adding online disks to the Cluster is not possible.
Cause
This can occur when using Tibero VIP in an HP Cluster environment,
and the above situation can be observed in the following Tibero configuration using VIP.
[Tibero Configuration: $TB_SID.tip]
LOCAL_CLUSTER_VIP=192.168.41.170 LOCAL_CLUSTER_NIC=lan1 LOCAL_CLUSTER_VIP_NETMASK=255.255.255.0 LOCAL_CLUSTER_VIP_BROADCAST=192.168.0.1
[HP-UX Ethernet: ifconfig lan1]
lan1: flags=2000000000001843<UP,BROADCAST,RUNNING,MULTICAST,CKO,TSO> inet 128.1.1.1 netmask fffff800 broadcast 192.168.0.1
Solutions
When using Tibero VIP in an HP Cluster environment, it is recommended to use the netmask value of the OS NIC Interface.
[Tibero Configuration: $TB_SID.tip Modification]
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