Chassis down-checkpoint-all

Chassis down-checkpoint-all
0

Chassis down-checkpoint-all

Vendor: checkpoint

OS: all

Description:
Indeni will generate an issue when one or more chassis are down.

Remediation Steps:
Review the cause for the chassis being down.

How does this work?
Indeni uses the built-in Check Point “asg stat -v” command to retrieve the current blade state.

Why is this important?
A chassis failure can be detrimental if high-availability is not configured. Even if it is, proactively identifying a chassis failure will provide the time necessary to bring it back on.

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

chkp-asg-stat-v

name: chkp-asg-stat-v
description: Retrieve status data
type: monitoring
monitoring_interval: 5 minute
requires:
    vendor: checkpoint
    asg: true
    os.version:
        neq: R80.20SP
comments:
    chassis-state:
        why: |
            A chassis failure can be detrimental if high-availability is not configured. Even if it is, proactively identifying a chassis failure will provide the time necessary to bring it back on.
        how: |
            Indeni uses the built-in Check Point "asg stat -v" command to retrieve the current blade state.
        without-indeni: |
            An administrator could login and manually run the command.
        can-with-snmp: true
        can-with-syslog: false
        vendor-provided-management: |
            Listing the chassis state is only available from the command line interface.
    blade-state:
        why: |
            A down blade in the security group can mean loss of redundancy and performance.
        how: |
            Indeni uses the built-in Check Point "asg stat -v" command to retrieve the current blade state.
        without-indeni: |
            An administrator could login and manually run the command.
        can-with-snmp: false
        can-with-syslog: false
        vendor-provided-management: |
            Listing the blade state is only available from the command line interface.
    blade-state-live-config:
        skip-documentation: true
    cluster-member-active:
        skip-documentation: true
    chkp-cluster-member-active-live-config:
        skip-documentation: true
steps:
-   run:
        type: SSH
        command: ${nice-path} -n 15 asg stat -i local_id && ${nice-path} -n 15 asg stat -v
    parse:
        type: AWK
        file: asg-stat-v.parser.1.awk

CrossVendorChassisDown

// 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.rules.library.templates.StateDownTemplateRule
import com.indeni.server.rules.RemediationStepCondition


/**
  *
  */
case class CrossVendorChassisDown() extends StateDownTemplateRule(
  ruleName = "CrossVendorChassisDown",
  ruleFriendlyName = "Chassis Devices: Chassis down",
  ruleDescription = "Indeni will generate an issue when one or more chassis are down.",
  metricName = "chassis-state",
  applicableMetricTag = "name",
  alertItemsHeader = "Chassis Affected",
  alertDescription = "One or more chassis are down.",
  baseRemediationText = "Review the cause for the chassis being down.")(
  RemediationStepCondition.VENDOR_CP -> "A chassis fails usually if all the SGM blades have gone down. Indeni will have identified in a separate issue for all blades that have gone down. Additionally, you can run the command asg stat. This will provide information on hardware elements required to have the chassis operational.")