Troubleshooting LLT health check warning messages
Prev Troubleshooting SF Oracle RAC Next

Troubleshooting LLT health check warning messages

Table: Troubleshooting LLT warning messages lists the warning messages displayed during the health check and corresponding recommendations for resolving the issues.

Table: Troubleshooting LLT warning messages

Warning

Possible causes

Recommendation

Warning: OS timer is not called for num seconds

CPU and memory consumption on the node is high.

Check for applications that may be throttling the CPU and memory resources on the node.

Warning: Kernel failed to allocate memory num time(s)

The available memory on the node is insufficient.

Reduce memory consumption on the node and free up allocated memory.

Flow-control occurred num time(s)and back-enabled num time(s) on port port number for node node number

  • The network bandwidth between the local node and the peer node (node number) is insufficient.

  • The CPU and memory consumption on the peer node (node number) is very high.

  • Allocate more bandwidth for communication between the local node and the peer node.

  • Check for applications that may be throttling the CPU and memory resources on the node.

Warning: Connectivity with node node id on link link id is flaky num time(s).

The distribution is: (0-4 s) <num> (4-8 s) <num> (8-12 s) <num> (12-16 s) <num> (>=16 s)

The private interconnect between the local node and the peer node is unstable.

Check the connectivity between the local node and the peer node. Replace the link, if needed.

One or more link connectivity with peer node(s) node name is in trouble.

The private interconnects between the local node and peer node may not have sufficient bandwidth.

Check the private interconnects between the local node and the peer node.

Link connectivity with node id is on only one link. Symantec recommends configuring a minimum of 2 links.

  • One of the configured private interconnects is non-operational.

  • Only one private interconnect has been configured under LLT.

  • If the private interconnect is faulty, replace the link.

  • Configure a minimum of two private interconnects.

Only one link is configured under LLT. Symantec recommends configuring a minimum of 2 links.

  • One of the configured private interconnects is non-operational.

  • Only one private interconnect has been configured under LLT.

  • If the private interconnect is faulty, replace the link.

  • Configure a minimum of two private interconnects.

Retransmitted % percentage of total transmitted packets.

Sent % percentage of total transmitted packet when no link is up.

% percentage of total received packets are with bad checksum.

% percentage of total received packets are out of window.

% percentage of total received packets are misaligned.

  • The network interface card or the network links are faulty.

  • Verify the network connectivity between nodes.

    Check the network interface card for anomalies.

% percentage of total received packets are with DLPI error.

The DLPI driver or NIC may be faulty or corrupted.

Check the DLPI driver and NIC for anomalies.

% per of total transmitted packets are with large xmit latency (>16ms) for port port id

%per received packets are with large recv latency (>16ms) for port port id.

The CPU and memory consumption on the node may be high or the network bandwidth is insufficient.

  • Check for applications that may be throttling CPU and memory usage.

  • Make sure that the network bandwidth is adequate for facilitating low-latency data transmission.

LLT is not running.

SF Oracle RAC is not configured properly.

Reconfigure SF Oracle RAC.

For instructions, see the Veritas Storage Foundation for Oracle RAC Installation and Configuration Guide.
Prev Up Next
Troubleshooting pre-installation check failures Home Troubleshooting LMX health check warning messages