Critical process(es) down (per VS)-f5-all

Critical process(es) down (per VS)-f5-all
0

Critical process(es) down (per VS)-f5-all

Vendor: f5

OS: all

Description:
Many devices have critical processes, usually daemons, that must be up for certain functions to work. indeni will alert if any of these goes down.

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

How does this work?
This script logs into the device through SSH and extracts the guest process states via TMSH.

Why is this important?
Each device has certain executable processes which are critical to the stable operation of it. Within F5 units, these processes are responsible for the management layer. An example is the watchdog service which ensures that the system will reboot in the event of a lockup. A process being down may indicate a critical failure.

Without Indeni how would you find this?
An administrator could track this manually by logging into the device via SSH, entering TMSH and executing the command “show vcmp health”.

f5-tmsh-show-vcmp-health

name: f5-tmsh-show-vcmp-health
description: Extract the process-state and provisioned modules from guests
type: monitoring
monitoring_interval: 10 minutes
requires:
    vendor: f5
    product: load-balancer
    linux-based: 'true'
    vsx: 'true'
    shell: bash
comments:
    process-state:
        why: |
            Each device has certain executable processes which are critical to the stable operation of it. Within F5 units, these processes are responsible for the management layer. An example is the watchdog service which ensures that the system will reboot in the event of a lockup. A process being down may indicate a critical failure.
        how: |
            This script logs into the device through SSH and extracts the guest process states via TMSH.
        without-indeni: |
            An administrator could track this manually by logging into the device via SSH, entering TMSH and executing the command "show vcmp health".
        can-with-snmp: false
        can-with-syslog: false
    features-enabled:
        why: |
            This information could be useful for troubleshooting purposes could be used to correlate high usage of resources with the enabled modules.
        how: |
            This script logs into the device through SSH and extracts the enabled modules via TMSH.
        without-indeni: |
            An administrator could track this manually by logging into the device via SSH, entering TMSH and executing the command "show vcmp health".
        can-with-snmp: false
        can-with-syslog: false
steps:
-   run:
        type: SSH
        command: tmsh -q -c "show vcmp health"
    parse:
        type: AWK
        file: tmsh-show-vcmp-health.parser.1.awk

cross_vendor_critical_process_down_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.rules.RuleContext
import com.indeni.apidata.time.TimeSpan
import com.indeni.server.rules.library.templates.StateDownTemplateRule
import com.indeni.server.rules.RemediationStepCondition

/**
  *
  */
case class cross_vendor_critical_process_down_vsx() extends StateDownTemplateRule(
  ruleName = "cross_vendor_critical_process_down_vsx",
  ruleFriendlyName = "All Devices: Critical process(es) down (per VS)",
  ruleDescription = "Many devices have critical processes, usually daemons, that must be up for certain functions to work. indeni will alert if any of these goes down.",
  metricName = "process-state",
  applicableMetricTag = "process-name",
  descriptionMetricTag = "vs.name",
  alertItemsHeader = "Processes Affected",
  alertDescription = "One or more processes which are critical to the operation of this device, are down.",
  baseRemediationText = "Review the cause for the processes being down.")(
  RemediationStepCondition.VENDOR_CP -> "Check if \"cpstop\" was run.If MDS check if \"mdsstop\" was run",
  RemediationStepCondition.VENDOR_CISCO ->
    """|
      |1. Use the "show processes cpu" NX-OS command in order to show the CPU usage at the process level.
      |2. Use the "show process cpu detail <pid>" NX-OS command to find out the CPU usage for all threads that belong to a specific process ID (PID).
      |3. Use the "show system internal sysmgr service pid <pid>" NX-OS command in order to display additional details, such as restart time, crash status, and current state, on the process/service by PID.
      |4. Run the "show system internal processes cpu" NX-OS command which is equivalent to the top command in Linux and provides an ongoing look at processor activity in real time.""".stripMargin
)