Blade(s) down-checkpoint-all

Blade(s) down-checkpoint-all
0

Blade(s) down-checkpoint-all

Vendor: checkpoint

OS: all

Description:
Indeni will alert one or more blades in a chassis is down.

Remediation Steps:
Review the cause for the blades being down.
If the blade was not stopped intentionally (admin down), check to see it wasn’t disconnected physically.",

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 down blade in the security group can mean loss of redundancy and performance.

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

chassis_blade_down

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

/**
  *
  */
case class chassis_blade_down() extends StateDownTemplateRule(
  ruleName = "chassis_blade_down",
  ruleFriendlyName = "Chassis Devices: Blade(s) down",
  ruleDescription = "Indeni will alert one or more blades in a chassis is down.",
  metricName = "blade-state",
  applicableMetricTag = "name",
  alertItemsHeader = "Blades Affected",
  alertDescription = "One or more blades in this chassis are down.",
  baseRemediationText = "Review the cause for the blades being down.")(
  RemediationStepCondition.VENDOR_CP -> "If the blade was not stopped intentionally (admin down), check to see it wasn't disconnected physically.",
  RemediationStepCondition.VENDOR_CISCO ->
    """|
      |Most of the module related failures (such as the module not coming up, the module getting reloaded, and so on) can be analyzed by looking at the logs stored on the switch. Use the following CLI commands to identify the problem:
      |•show system reset-reason module
      |•show version
      |•show logging
      |•show module internal exception-log
      |•show module internal event-history module
      |•show module internal event-history errors
      |•show platform internal event-history errors
      |•show platform internal event-history module
      |Further details can be found to the next CISCO troubleshooting guide:
      |https://www.cisco.com/en/US/products/ps5989/prod_troubleshooting_guide_chapter09186a008067a0ef.html""".stripMargin
)