View source for Striker-manage-peers

{{man_header}}

= NAME =

striker-manage-peers - This manages peering two Striker dashboards

= SYNOPSIS =

'''striker-manage-peers''' ''&lt;command&gt; ''[''options'']

= DESCRIPTION =

This handles peering Striker dashboards. Peered Strikers means that they act as replaceable alternative dashboards, should another fail.

; '''Note'''
: The list that is downloaded is - https://standards-oui.ieee.org/oui/oui.txt 
: The oui.txt file is cached locally once downloaded to minimizing loading the IEEE server. It will be redownloaded every few days.

= OPTIONS =

-?, -h, '''--help''' Show this man page.

; '''--log-secure'''
: When logging, record sensitive data, like passwords.
; -v, -vv, -vvv
: Set the log level to 1, 2 or 3 respectively. Be aware that level 3 generates a significant amount of log data.

== Commands: ==

'''--check''' This reports 'status=[1,0]' to indicate if the install target feature is currently running or not. Specifically, it checks to see if the DHCP server is running or not.

; '''--disable'''
: This disables the install target feature.
; '''--enable'''
: This enables the install target feature.
; '''--force'''
: This is the same as '--refresh', forcing the update of the RPM repo.
; '''--job-uuid''' &lt;uuid&gt;
: This is the job UUID used to run this job.
; '''--no-refresh'''
: If a refresh of the RPM repository would have been called, this switch will prevent it from happening.
; '''--refresh-file'''
: This tells this run to refresh the RPM repository, regardless of whether it would have run otherwise.
; '''--status'''
: This checks to see if dhcpd is running or not, then exits (effectively checking if the install target feature is running).

= AUTHOR =

Written by Madison Kelly, Alteeve staff and the Anvil! project contributors.

= REPORTING BUGS =

Report bugs to users@clusterlabs.org

{{footer}}