Timezone mismatch across cluster members-f5-all

Timezone mismatch across cluster members-f5-all
0

Timezone mismatch 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 timezone setting is different.

Remediation Steps:
Review the settings of each device in the cluster and ensure they are the same.

How does this work?
Indeni logs in over SSH and executes “tmsh -q list sys ntp”. The output is then parsed for the configured timezone.

Why is this important?
A correct time and time zone is very important for many reasons. An incorrectly configured time zone could mean that timestamps on logs are incorrect. Indeni will identify when two devices are part of a cluster and alert if the timezone setting is different.

Without Indeni how would you find this?
An administrator could login to the unit through SSH, enter TMSH and issue the command “list sys ntp” to see the configured timezone. This information is also availble through the Web Interface by navigating to “System” -> “Platform”.

f5-tmsh-list-sys-ntp

name: f5-tmsh-list-sys-ntp
description: Get the configured NTP servers and timezone
type: monitoring
monitoring_interval: 60 minutes
requires:
    vendor: f5
    product: load-balancer
    shell: bash
comments:
    ntp-servers:
        why: |
            Not having an NTP server configured could make the clock slowly drift, which makes log entries and other information harder to summarize between devices. If the clock drifts very far out, there could also be issues with validating certificates.
        how: |
            Indeni logs in over SSH and executes "tmsh -q list sys ntp". The output is then parsed for any ntp server configuration.
        can-with-snmp: false
        can-with-syslog: false
    timezone:
        why: |
            A correct time and time zone is very important for many reasons. An incorrectly configured time zone could mean that timestamps on logs are incorrect. Indeni will identify when two devices are part of a cluster and alert if the timezone setting is different.
        how: |
            Indeni logs in over SSH and executes "tmsh -q list sys ntp". The output is then parsed for the configured timezone.
        can-with-snmp: false
        can-with-syslog: false
steps:
-   run:
        type: SSH
        command: tmsh -q list sys ntp
    parse:
        type: AWK
        file: tmsh-list-sys-ntp.parser.1.awk

cross_vendor_compare_timezone

Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/templatebased/crossvendor/cross_vendor_compare_timezone.scala