List of M3 Command Line Tools: Difference between revisions

From Alteeve Wiki
Jump to navigation Jump to search
Line 18: Line 18:
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-boot-machine]]
!style="white-space:nowrap; text-align:left;"|[[striker-boot-machine]]
|
|Tool used to boot physical machines that have IPMI configuration information.
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-check-machines]]
!style="white-space:nowrap; text-align:left;"|[[striker-check-machines]]
|
|This program tests access and, when not reachable, checks the power state if out of band management is available.
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-collect-debug]]
!style="white-space:nowrap; text-align:left;"|[[striker-collect-debug]]
|
|This program collects data needed to help diagnose problems with an Anvil! system.
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-db-status]]
!style="white-space:nowrap; text-align:left;"|[[striker-db-status]]
|
|This shows the current status of striker dashboards
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-file-manager]]
!style="white-space:nowrap; text-align:left;"|[[striker-file-manager]]
|
|This manages the files available for use by servers
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-get-peer-data]]
!style="white-space:nowrap; text-align:left;"|[[striker-get-peer-data]]
|
|This manages peering two Striker dashboards
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-get-screenshots]]
!style="white-space:nowrap; text-align:left;"|[[striker-get-screenshots]]
|
|Tool used to collect screenshots from Anvil! subnodes and DR hosts
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-initialize-host]]
!style="white-space:nowrap; text-align:left;"|[[striker-initialize-host]]
|
|Tool used on Striker dashboards to initialize new Nodes and DR hosts.
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-manage-install-target]]
!style="white-space:nowrap; text-align:left;"|[[striker-manage-install-target]]
|
|This manages the "Install Target" feature on Striker dashboards
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-manage-peers]]
!style="white-space:nowrap; text-align:left;"|[[striker-manage-peers]]
|
|This manages peering two Striker dashboards
|-
!style="white-space:nowrap; text-align:left;"|[[striker-manage-peers]]
|
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-parse-oui]]
!style="white-space:nowrap; text-align:left;"|[[striker-parse-oui]]
|
|This parses the [[IEEE]] [[OUI]] file and parses it for storage in the Anvil database
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-purge-target]]
!style="white-space:nowrap; text-align:left;"|[[striker-purge-target]]
|
|This tool purges the target from all Anvil! databases.
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-scan-network]]
!style="white-space:nowrap; text-align:left;"|[[striker-scan-network]]
|
|This scans accessible networks to create a map of MAC addresses to IP addresses
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-show-db-counts]]
!style="white-space:nowrap; text-align:left;"|[[striker-show-db-counts]]
|
|This shows the number of records in accessible databases.
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-show-jobs]]
!style="white-space:nowrap; text-align:left;"|[[striker-show-jobs]]
|
|This shows the queued, running and (recently) completed jobs.
|-
|-
!style="white-space:nowrap; text-align:left;"|[[striker-update-cluster]]
!style="white-space:nowrap; text-align:left;"|[[striker-update-cluster]]
|
|This program updates all physical machines in an Anvil! cluster
|-
|-
|}
|}

Revision as of 23:47, 31 July 2024

 Alteeve Wiki :: How To :: List of M3 Command Line Tools

The Anvil! uses a fairly naming convention. That is;

  • Tools that start with striker-X are tools useful mainly to Striker dasboards.
  • Tools that start with anvil-X are tools that can be useful on any machine in the Anvil! cluster

Separately, Scancore has a collection of scan agents, programs designed to collect information on hardware, software or other sources of information that can prove useful to the Scancore decision engine. These agents are core to the Anvil! system's Intelligent Availability capabilities.

Striker-Specific Tools

Command Brief Description
striker-auto-initialize-all Tools to autonomously configure all machines in an Anvil! IA cluster
striker-boot-machine Tool used to boot physical machines that have IPMI configuration information.
striker-check-machines This program tests access and, when not reachable, checks the power state if out of band management is available.
striker-collect-debug This program collects data needed to help diagnose problems with an Anvil! system.
striker-db-status This shows the current status of striker dashboards
striker-file-manager This manages the files available for use by servers
striker-get-peer-data This manages peering two Striker dashboards
striker-get-screenshots Tool used to collect screenshots from Anvil! subnodes and DR hosts
striker-initialize-host Tool used on Striker dashboards to initialize new Nodes and DR hosts.
striker-manage-install-target This manages the "Install Target" feature on Striker dashboards
striker-manage-peers This manages peering two Striker dashboards
striker-parse-oui This parses the IEEE OUI file and parses it for storage in the Anvil database
striker-purge-target This tool purges the target from all Anvil! databases.
striker-scan-network This scans accessible networks to create a map of MAC addresses to IP addresses
striker-show-db-counts This shows the number of records in accessible databases.
striker-show-jobs This shows the queued, running and (recently) completed jobs.
striker-update-cluster This program updates all physical machines in an Anvil! cluster

General Tools

anvil-access-module anvil-boot-server anvil-change-password anvil-check-memory anvil-configure-host anvil-cycle-vm-nics anvil-delete-server anvil-download-file anvil-file-details anvil-get-server-screenshot anvil-join-anvil anvil-maintenance-mode anvil-manage-alerts anvil-manage-daemons anvil-manage-dr anvil-manage-files anvil-manage-firewall anvil-manage-host anvil-manage-keys anvil-manage-power anvil-manage-server anvil-manage-server-storage anvil-manage-server-system anvil-manage-storage-groups anvil-manage-vnc-pipe anvil-migrate-server anvil-network-profiler anvil-parse-fence-agents anvil-pcs-wrapper anvil-pcs-wrapper.bash anvil-pcs-wrapper.new anvil-provision-server anvil-rename-server anvil-report-usage anvil-safe-start anvil-safe-stop anvil-show-local-ips anvil-shutdown-server anvil-special-operations anvil-sync-shared anvil-update-issue anvil-update-system anvil-version-changes anvil-virsh-wrapper anvil-watch-bonds anvil-watch-drbd anvil-watch-power anvil-watch-servers

Command Brief Description
[[]]

Scan Agents

scan-apc-pdu scan-apc-ups scan-cluster scan-drbd scan-filesystems scan-hardware scan-hpacucli scan-ipmitool scan-lvm scan-network scan-server scan-storcli

Command Brief Description
[[]]

Specialized Tools

These tools are designed for use primarily by other tools, and are not meant to be used by administrators directly.

fence_pacemaker generate_pm_dispatch_table scancore unfence_pacemaker

Command Brief Description
anvil-daemon This is the main Anvil! daemon. It maintains the state of the various machines in the cluster, runs jobs as needed, etc.
anvil-monitor-network This is a daemon that watches for changes to network interfaces. When changes are detected, the 'scan-network' scan agent is called. This ensures that changes are quickly reflected in the Anvil! database, which is particularly useful when mapping network interfaces.
anvil-monitor-performance This is a daemon that collects performance data and records it in the anvil.log log file. This is designed to help diagnose performance issues by keeping track of CPU load, I/O wait times, and other metrics.
alteeve-repo-setup This tool configures the Alteeve repository. Primarily it is used to setup the repository needed to access Alteeve software, and to switch between the community and enterprise repositories.
fence_delay This is a pseudo fence agent that the Anvil! uses automatically when a subnode has an IPMI BMC. It's purpose is the slow down Pacemaker to give time for the IPMI BMC to boot after a power fence device, like a switched PDU, cut and restored power to a failed node.
fence_pacemaker This is a DRBD fence agent. It acts as a glue layer so that DRBD can request a resource (or node) be fenced, and passing that request on to Pacemaker.
scancore This is the Scancore daemon, which is the component of the Anvil! cluster that provides all of the Intelligent Availability / risk mitigation.
unfence_pacemaker This is the DRBD "unfence" agent. It acts as a glue layer so that DRBD can request a resource be unfenced, and passing that request on to Pacemaker.

 

Any questions, feedback, advice, complaints or meanderings are welcome.
Alteeve's Niche! Enterprise Support:
Alteeve Support
Community Support
© Alteeve's Niche! Inc. 1997-2024   Anvil! "Intelligent Availability®" Platform
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.