Routes defined in clish/webUI are missing-checkpoint-gaia

Routes defined in clish/webUI are missing-checkpoint-gaia
0

Routes defined in clish/webUI are missing-checkpoint-gaia

Vendor: checkpoint

OS: gaia

Description:
Sometimes the routes that are defined in the Check Point Web UI or through clish may not be fully applied to the operating system layer. If this happens, Indeni will alert.

Remediation Steps:
A workaround to get it to work can be to restart the routeD daemon by running “cpstop;cpstart” or restarting the device. However since this should not happen a case can also be opened with your technical support provider. In the case of devices in a cluster it is possible that the issue happens only for one of the nodes and a failover to the other node could lessen the impact of the issue.

How does this work?
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.

Why is this important?
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.

Without Indeni how would you find this?
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.

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.
        can-with-snmp: true
        can-with-syslog: false
    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.
        can-with-snmp: true
        can-with-syslog: false
    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.
        can-with-snmp: false
        can-with-syslog: false
steps:
-   run:
        type: SSH
        file: gaia-routes-vsx.remote.1.bash
    parse:
        type: AWK
        file: gaia-routes-vsx.parser.1.awk

chkp_firewall_routes_missing_novsx

Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/templatebased/checkpoint/chkp_firewall_routes_missing_novsx.scala