Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Is a requirement that the devices collected from the poller are the same than the mirror. 

Discoveries

What happen when we discover a poller?

  • The first time we discover a poller, all the nodes are copied into the master. But once they have being copied, in the synchronisations the node configuration will be send from the master to the poller. 
  • The server will be set up as a poller, so we are not gonna be able to edit the nodes from the poller. 

What happen when we discover a mirror?

  • The first time we discover a mirror, it needs to be empty (Except for localhost). This is because, all nodes needs to be copied from the poller that is being mirroring. 
  • The nodes will be sent to the mirror, the mirror will start polling those devices, at the same time that the poller. 
  • But the data it won't be synchronised, unless the poller is disabled/down. 
  • The server will be set up as a mirror, so we are not gonna be able to edit the nodes from the mirror. 
  • Every time we made a change into the poller nodes from the master, they will be replicated into the mirror. 

Deletes

What happen when we remove a poller?

We can update the role before remove the poller. If not, we are not going to be able to manage the nodes. We can do this manually by setting opha_role in conf/opCommon.json and restarting the server. 

The mirror will became the poller. 

What happen when we discover a mirror?

We can update the role before remove the poller. If not, we are not going to be able to manage the nodes. We can do this manually by setting opha_role in conf/opCommon.json and restarting the server. 

Pull Data

What happen pull from a poller?

If the poller is active and responsive, we will bring the data from the poller, except for the nodes. This is made in the Sync all Nodes operation. 

What happen pull from a mirror?

If the poller is active, we will only bring the registry and the selftest data. 

Data Verification

We can use the following command to review the data and where it is coming from:

Code Block
/usr/local/omk/bin/opha-cli.pl act=data_verify debug=9 

As an output example:

Code Block
ACTIVE ENABLED STATUS NODES INVENTORY EVENTS LATEST_DATA STATUS 
=============================================================== 
Poller: poller-nine 0d28dcf0-8fe2-49d9-a26f-6ccf3f2875c0 
	1	ok	[ 519 ] 	[ 20442 ] 	[ 694 ] 	[ 3956 ] 	[ 2059 ] 

Poller: fulla a515c63a-0d11-4bcb-a402-39a4600aebb9 
	1	ok	[ 99 ] 	[ 2827 ] 	[ 2827 ] 	[  ] 	[  ] 

Poller: uburnto 8bf31ddc-8f32-4fdf-8173-8ce989e2e210 
1	1	ok	[ 7 ] 	[ 230 ] 	[ 10 ] 	[ 40 ] 	[ 101 ] 
[Tue May 11 19:40:09 2021] [info] Returning: se7en
Mirror: se7en 1487b8fb-f1f9-41e9-995b-29e925724ff3 
0	1	ok	[  ] 	[  ] 	[  ] 	[  ] 	[  ]