Static routing table does not match across cluster members-checkpoint-gaia

Static routing table does not match across cluster members-checkpoint-gaia
0

Static routing table does not match across cluster members-checkpoint-gaia

Vendor: checkpoint

OS: gaia

Description:
Indeni will identify when two devices are part of a cluster and alert if their static routing tables are different.

Remediation Steps:
Ensure the static routing table matches across devices in a cluster.
Use the “show configuration” command in clish to compare the calls to "set static-route\

How does this work?
By parsing the gaia configuration database, /config/active, the static routes are retrieved. It can also be retrieved via Clish, but that creates a lot of log entries in /var/log/messages.

Why is this important?
It is important that the routing is configured the same for all cluster members of the same cluster. Otherwise there can be downtime in the event of a failover.

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

chkp-gaia-routes-vsx

name: chkp-gaia-routes-vsx
description: Report configured static and direct routes, and compare configured static
    routes with Linux routes.
type: monitoring
monitoring_interval: 10 minutes
requires:
    vendor: checkpoint
    os.name: gaia
    vsx: 'true'
    role-firewall: 'true'
    asg:
        neq: 'true'
comments:
    static-routing-table:
        why: |
            It is important that the routing is configured the same for all cluster members of the same cluster. Otherwise there can be downtime in the event of a failover.
        how: |
            By parsing the gaia configuration database, /config/active, the static routes are retrieved. It can also be retrieved via Clish, but that creates a lot of log entries in /var/log/messages.
        without-indeni: |
            An administrator could login and manually run the command.
        can-with-snmp: true
        can-with-syslog: false
        vendor-provided-management: |
            Listing static routes is only available from the command line interface or via SNMP. In VSX it is also visible in SmartDashboard.
    connected-networks-table:
        why: |
            It is important that the connected interfaces is configured the same, for all cluster members of the same cluster. Otherwise there can be downtime in the event of a failure.
        how: |
            By parsing the gaia configuration database, /config/active, the routes for directly connected interfaces are retrieved. It can also be retrieved via Clish, but that creates a lot of log entries in /var/log/messages.
        without-indeni: |
            An administrator could login and manually run the command.
        can-with-snmp: true
        can-with-syslog: false
        vendor-provided-management: |
            Listing routes for directly connected interfaces is only available from the command line interface, or SNMP.
    routes-missing-kernel:
        why: |
            If a static route is configured via Clish or WebUI, sometimes the system does not write the route into the Linux kernel routing table. To make sure all routes have been written, we compare the actual kernel routes with those configured in Check Point.
        how: |
            Retrieve Linux kernel routes using the Linux "netstat" command, and then the Check Point configured routes from Gaia's /config/active file. Then compare two route sets to make sure they are the same.
        without-indeni: |
            An administrator could login and manually list routes from both commands, and then compare it. However, often there are a many routes configured; combine this with the difference in output format (for example subnet), and it can be a very cumbersome task.
        can-with-snmp: false
        can-with-syslog: false
        vendor-provided-management: Listing routes from kernel is only available from
            the command line interface. Listing configured routes is also available
            from the WebUI.
steps:
-   run:
        type: SSH
        file: gaia-routes-vsx.remote.1.bash
    parse:
        type: AWK
        file: gaia-routes-vsx.parser.1.awk

static_routing_table_comparison_non_vsx

// Deprecation warning : Scala template-based rules are deprecated. Please use YAML format rules instead.

package com.indeni.server.rules.library.templatebased.crossvendor

import com.indeni.server.common.data.conditions.{Equals => DataEquals}
import com.indeni.server.rules.RuleContext
import com.indeni.server.rules.library.templates.SnapshotComparisonTemplateRule
import com.indeni.server.rules.RemediationStepCondition

/**
  *
  */
case class static_routing_table_comparison_non_vsx() extends SnapshotComparisonTemplateRule(
  ruleName = "static_routing_table_comparison_non_vsx",
  ruleFriendlyName = "Clustered Devices (Non-VS): Static routing table does not match across cluster members",
  ruleDescription = "Indeni will identify when two devices are part of a cluster and alert if their static routing tables are different.",
  metricName = "static-routing-table",
  isArray = true,
  metaCondition = !DataEquals("vsx", "true"),
  baseRemediationText = "Ensure the static routing table matches across devices in a cluster.",
  alertDescription = "Devices that are part of a cluster must have the same static routing tables. Review the differences below.\n\nThis alert was added per the request of <a target=\"_blank\" href=\"http://il.linkedin.com/pub/itzik-assaraf/2/870/1b5\">Itzik Assaraf</a> (Leumi Card)."
  )(
  RemediationStepCondition.VENDOR_CP -> "Use the \"show configuration\" command in clish to compare the calls to \"set static-route\".",
  RemediationStepCondition.VENDOR_CISCO ->
    """|
      |1. Execute the "show ip route static" command to display the current contents of the  static routes installed to the routing table.
      |2. Compare the static route config between the peer switches with the show run | i "ip route" command
      |NOTE: The static routes configured between the peer switches may be different in case of orphan devices without need of redundancy between the vPC peer switches
      |3. For more information please review the next Cisco configuration guide:
      |https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_cli_nxos/l3_route.html
    """.stripMargin
)
{override def deviceCondition(context: RuleContext) = generateDevicePassiveAndPassiveLinkStateCondition(context.tsDao)}