menu:nccm:nccm_selection
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
menu:nccm:nccm_selection [2022/05/16 08:24] – yspeerte | menu:nccm:nccm_selection [2024/07/03 12:31] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{indexmenu_n> | ||
+ | ====== Polling status ====== | ||
+ | |||
+ | {{: | ||
+ | |||
+ | The polling status screen provides an overview of all nodes present in the polling group(s), allowing you to filter on nodes that are being //polled// or //polling// has been //halted// as a result of reaching the max retries defined in polling group in question, another option is //not polling// when the node(s) are not part of a polling group but the configuration got stored in the NCCM because of the backup feature within command jobs. Entries here are color-coded: | ||
+ | |||
+ | In case your netYCE setup consists of multiple backend servers you will see more than one of these servers listed in the // | ||
+ | |||
+ | // | ||
+ | |||
+ | At the bottom of the grid are a number of buttons: | ||
+ | * **Schedule now:** Takes the node or nodes that are selected, and puts their Schedule_time at the current time. This will cause them to be picked up by the next cycle (if load permitted) of the nccmd daemon for an nccm poll. | ||
+ | * **Delete:** Deletes this node from the NCCM. It will not be polled again for nccm, nor for compliance. Note however that when this entry was created through a polling group it will be automatically re-created (history will not be re-installed), | ||
+ | * **Re-enable: | ||
+ | * **Force daemon:** Forces a cycle of the nccmd daemon. Normally it wakes up every 5 minutes, but with this you can force it to wake up right now and carry out its tasks. | ||
+ | * **Search:** Allows you to search through the nodes | ||
+ | |||
+ | For more information on nccm selections, see [[guides: | ||