More than one sync interface defined-checkpoint-all

More than one sync interface defined-checkpoint-all
0

More than one sync interface defined-checkpoint-all

Vendor: checkpoint

OS: all

Description:
ClusterXL works best with just one sync interface. To achieve redundancy, interface bonding is recommended. indeni will alert when more than one sync interface is used.

Remediation Steps:
Read Valeri Loukine’s post on the subject: http://checkpoint-master-architect.blogspot.com/2014/05/notes-about-sync-redundancy.html.

How does this work?
By using the Check Point built-in “cphaprob” command, the information is retrieved.

Why is this important?
ClusterXL defines a certain number of secured (sync) interfaces which are required to be up for the cluster to be considered healthy. If there are less than these actually up, the cluster is not in a healthy state and traffic flow may be affected.

Without Indeni how would you find this?
An administrator could login and manually run the command.

cphaprob_a_if_novsx

name: cphaprob_a_if_novsx
description: run "cphaprob -a if" on non-vsx
type: monitoring
monitoring_interval: 1 minute
requires:
    vendor: checkpoint
    high-availability: 'true'
    vsx:
        neq: true
    clusterxl: 'true'
    role-firewall: true
    or:
        - os.version.num:
            compare-type: version-compare
            op: "<"
            value: "80.40"
        - and:
            - os.version: R80.30
            - hotfix-jumbo-take:
                compare-type: version-compare
                op: "<"
                value: "215"
comments:
    cphaprob-required-interfaces:
        why: |
            ClusterXL defines a certain number of interfaces which are required to be up for the cluster to be considered
            healthy. If there are less than these actually up, the cluster is not in a healthy state and traffic flow may be affected.
        how: |
            By using the Check Point built-in "cphaprob" command, the information is retrieved.
        can-with-snmp: false
        can-with-syslog: false

    cphaprob-required-secured-interfaces:
        why: |
            ClusterXL defines a certain number of secured (sync) interfaces which are required to be up for the cluster
            to be considered healthy. If there are less than these actually up, the cluster is not in a healthy state
            and traffic flow may be affected.
        how: |
            By using the Check Point built-in "cphaprob" command, the information is retrieved.
        can-with-snmp: false
        can-with-syslog: false

    cphaprob-up-interfaces:
        why: |
            To check the healthy state of the cluster interfaces important factor for Cluster stability and redundancy
        how: |
            By Checking the input of Check Point clusterXL command "cphaprob -a if"
        can-with-snmp: false
        can-with-syslog: false

    cluster-vip:
        why: |
            This is the list of cluster virtual IP addresses also called floating IP adddresses for the cluster interfaces.
        how: |
            By using the Check Point built-in "cphaprob" command, the information is retrieved.
        can-with-snmp: false
        can-with-syslog: false

    clusterxl-ccp-mode:
        why: |
            ClusterXL can operate in different modes, multicast or broadcast. All members of the same clusters should have the same setting to ensure redundancy works correctly.
        how: |
            By using the Check Point built-in "cphaprob" command, the information is retrieved.
        can-with-snmp: false
        can-with-syslog: false

    cphaprob-up-secured-interfaces:
        why: |
            To check the status of the "Sync" interface is up
        how: |
            By running the command "cphaprob -a if"
        can-with-snmp: false
        can-with-syslog: false
steps:
-   run:
        type: SSH
        command: ${nice-path} -n 15 cphaprob -a if
    parse:
        type: AWK
        file: cphaprob-a-if-novsx.parser.1.awk

clusterxl_too_many_sync_nics_novsx

package com.indeni.server.rules.library.checkpoint

import com.indeni.ruleengine.expressions.conditions.GreaterThan
import com.indeni.ruleengine.expressions.core._
import com.indeni.ruleengine.expressions.data.{SelectTagsExpression, SelectTimeSeriesExpression, TimeSeriesExpression}
import com.indeni.server.common.data.conditions.Equals
import com.indeni.server.rules._
import com.indeni.server.rules.library.{ConditionalRemediationSteps, PerDeviceRule, RuleHelper}
import com.indeni.server.sensor.models.managementprocess.alerts.dto.AlertSeverity

case class ClusterXLTooManySyncNicsNoVsxRule() extends PerDeviceRule with RuleHelper {

  override val metadata: RuleMetadata = RuleMetadata.builder("clusterxl_too_many_sync_nics_novsx", "Firewall more than one sync interface defined",
    "ClusterXL works best with just one sync interface. To achieve redundancy, interface bonding is recommended. indeni will alert when more than one sync interface is used.", AlertSeverity.ERROR, categories = Set(RuleCategory.VendorBestPractices),deviceCategory = DeviceCategory.CheckPointClusterXLNonVSX).build()

  override def expressionTree(context: RuleContext): StatusTreeExpression = {
    val inUseValue = TimeSeriesExpression[Double]("cphaprob-required-secured-interfaces").last

    StatusTreeExpression(
      // Which objects to pull (normally, devices)
      SelectTagsExpression(context.metaDao, Set(DeviceKey), !Equals("vsx", "true")),

      // What constitutes an issue
        StatusTreeExpression(
          // The time-series we check the test condition against:
          SelectTimeSeriesExpression[Double](context.tsDao, Set("cphaprob-required-secured-interfaces"), denseOnly = false),

          // The condition which, if true, we have an issue. Checked against the time-series we've collected
          GreaterThan(
            inUseValue,
            ConstantExpression(Some(1.0)))
        ).withoutInfo().asCondition()

      // Details of the alert itself
    ).withRootInfo(
        getHeadline(),
        ConstantExpression("SK92804 and Check Point's best practices recommend you only have one sync interface. To achieve redundancy, a bond interface should be used."),
        ConditionalRemediationSteps("Read Valeri Loukine's post on the subject: http://checkpoint-master-architect.blogspot.com/2014/05/notes-about-sync-redundancy.html.")
    )
  }
}