OS version mismatch across cluster members-juniper-junos

OS version mismatch across cluster members-juniper-junos
0

OS version mismatch across cluster members-juniper-junos

Vendor: juniper

OS: junos

Description:
Indeni will identify when two devices are part of a cluster and alert if the OS installed is different.

Remediation Steps:
Install the correct versions of software on each device.

How does this work?
This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the “show version” command. The output includes the device’s hardware and software related details.

Why is this important?
Capture the device operating system version. The version should be the same across all members of a cluster.

Without Indeni how would you find this?
An administrator would have to log into the device and manually issue commands to retrieve this information.

junos-show-version

name: junos-show-version
description: Fetch the information for the end of support for hardware and software
type: monitoring
monitoring_interval: 5 minute
requires:
    vendor: juniper
    os.name: junos
    product: firewall
comments:
    model:
        why: |
            Capture the device model.
        how: |
            This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show version"
            command. The output includes the device's hardware and software related details.
        can-with-snmp: true
        can-with-syslog: false
    vendor:
        why: |
            Capture the device vendor name.
        how: |
            This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show version"
            command. The output includes the device's hardware and software related details.
        can-with-snmp: true
        can-with-syslog: false
    hostname:
        why: |
            Capture the host name of the device. This is used for inventory purposes.
        how: |
            This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show version"
            command. The output includes the device's hardware and software related details.
        can-with-snmp: true
        can-with-syslog: false
    os-name:
        why: |
            Capture the device operating system name.
        how: |
            This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show version"
            command. The output includes the device's hardware and software related details.
        can-with-snmp: true
        can-with-syslog: false
    os-version:
        why: |
            Capture the device operating system version. The version should be the same across all members of a cluster.
        how: |
            This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show version"
            command. The output includes the device's hardware and software related details.
        can-with-snmp: true
        can-with-syslog: false
    software-eos-date:
        why: "Ensuring the software being used is always within the vendor's list\
            \ of supported versions is critical.\nOtherwise, during a critical issue,\
            \ the vendor may decline to provide technical support. Juniper posts the\
            \ list\nof supported software on their website: \nhttp://www.juniper.net/support/eol/junos.html\n"
        how: |
            This script logs into the Juniper JUNOS-based device using SSH to retrieve the current software version and
            based on the software version and the Juniper provided information at:
            http://www.juniper.net/support/eol/junos.html the correct end of support date is used.
        can-with-snmp: false
        can-with-syslog: false
    hardware-eos-date:
        why: "Ensuring the hardware being used is always within the vendor's list\
            \ of supported models is critical. Otherwise,\nduring a critical issue,\
            \ the vendor may decline to provide technical support. Juniper posts the\
            \ list of\nsupported hardware on their website: \nhttp://www.juniper.net/support/eol/srxseries_hw.html\n"
        how: |
            This script logs into the Juniper JUNOS-based device using SSH to retrieve the current model used and based on
            it and the Juniper provided information at http://www.juniper.net/support/eol/srxseries_hw.html the correct end
            of support date is used.
        can-with-snmp: false
        can-with-syslog: false
steps:
-   run:
        type: SSH
        file: show-version.remote.1.bash
    parse:
        type: AWK
        file: show-version.parser.1.awk

cross_vendor_compare_osversion

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

/**
  *
  */
case class cross_vendor_compare_osversion() extends SnapshotComparisonTemplateRule(
  ruleName = "cross_vendor_compare_osversion",
  ruleFriendlyName = "Clustered Devices: OS version mismatch across cluster members",
  ruleDescription = "Indeni will identify when two devices are part of a cluster and alert if the OS installed is different.",
  metricName = "os-version",
  isArray = false,
  alertDescription = "The members of a cluster of devices must have the same OS's installed (including the same version).\n\nThis alert was added per the request of <a target=\"_blank\" href=\"http://il.linkedin.com/pub/gal-vitenberg/83/484/103\">Gal Vitenberg</a>.",
  baseRemediationText = """Install the correct versions of software on each device.""")(
  RemediationStepCondition.VENDOR_CISCO ->
    """|
      |1. Check that the vPC peers have the same NX-OS version except during the non-disruptive upgrade, that is, In-Service Software Upgrade (ISSU).
      |2. Execute the "show version" NX-OS command and check the installed NX-OS version across the vPC peer switches.
      |3. Login to the Cisco Software Download center (a CCO account is required) and check the available NX-OS releases for your devices. Further information can be found to the next link: https://software.cisco.com/download/navigator.html?mdfid=268437593&flowid=4466
      |4. Select the NX-OS release highlighted with a star icon and download it. This is the currently recommended NX-OS version by Cisco.
      |5. Review the Release Notes for this release for any bug and unsupported feature. If this NX-OS release does not support features which are already deployed at the current configuration a more recent NX-OS release should be used.
      |6. Schedule a Maintenance Window for NX-OS upgrade in order the vPC peer switches have exact the same NX-OS version.
      |NOTE: The vPC could be established between the vPC peers with not exact the same NX-OS release but several problems will be faced when new features are configured. For instance FEX-mismatch SW log message will be generated if you try to connect a FEX via vPC to a pair of vPC switches with different SW version. In this case the FEX will be operational only from one of the vPC peer switches.""".stripMargin
)