Features enabled do not match across cluster members-f5-all

Features enabled do not match across cluster members-f5-all
0

Features enabled do not match across cluster members-f5-all

Vendor: f5

OS: all

Description:
Indeni will identify when two devices are part of a cluster and alert if the features they have enabled are different.

Remediation Steps:
Review the licensing and enabled features or modules on each device to ensure they match.

How does this work?
This script uses the F5 iControl REST API to retrieve the provisioned modules of vCMP guests.

Why is this important?
This metric gives an administrator an easy way to get an overview of the vCMP guest configuration by listing the provisioned modules.

Without Indeni how would you find this?
This metric is available by logging into the device with SSH, entering TMSH and executing the command “show vcmp health module-provision”.

f5-rest-mgmt-tm-vcmp-health-modules-provision

name: f5-rest-mgmt-tm-vcmp-health-modules-provision
description: Extracts the vCMP guests provisioned modules
type: monitoring
monitoring_interval: 60 minutes
requires:
    vendor: f5
    product: load-balancer
    rest-api: 'true'
    vsx: 'true'
comments:
    features-enabled:
        why: |
            This metric gives an administrator an easy way to get an overview of the vCMP guest configuration by listing the provisioned modules.
        how: |
            This script uses the F5 iControl REST API to retrieve the provisioned modules of vCMP guests.
        can-with-snmp: false
        can-with-syslog: false
steps:
-   run:
        type: HTTP
        command: /mgmt/tm/vcmp/health/module-provision
    parse:
        type: JSON
        file: rest-mgmt-tm-vcmp-health-modules-provision.parser.1.json.yaml

cross_vendor_features_enabled_comparison_vsx

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

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

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

/**
  *
  */
case class cross_vendor_features_enabled_comparison_vsx() extends SnapshotComparisonTemplateRule(
  ruleName = "cross_vendor_features_enabled_comparison_vsx",
  ruleFriendlyName = "Clustered Devices: Features enabled do not match across cluster members",
  ruleDescription = "Indeni will identify when two devices are part of a cluster and alert if the features they have enabled are different.",
  metricName = "features-enabled",
  applicableMetricTag = "vs.name",
  metaCondition = DataEquals("vsx", "true"),
  isArray = true,
  alertDescription = "Devices that are part of a cluster must have the same features enabled. Review the differences below.",
  baseRemediationText = "Review the licensing and enabled features or modules on each device to ensure they match.")(
  RemediationStepCondition.VENDOR_CISCO ->
    """|
      |1. Execute the "show feature" and "show license-usage" NX-OS commands to review the enabled features and licenses per vPC peer switch.
      |2. Both vPC peer switches should have the same licenses installed and features activated.
      |3. For more information please review  the following CISCO  NX-OS guides:
      |https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/best_practices/cli_mgmt_guide/cli_mgmt_bp/features.html
      |https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/nx-os/licensing/guide/b_Cisco_NX-OS_Licensing_Guide/b_Cisco_NX-OS_Licensing_Guide_chapter_01.html""".stripMargin
)