Replication
Main menu option: Replication
It retrieves status information about the operation of the Replication(Info), performs management actions such as manually adding and removing nodes(Nodes), connection tests(Cross Check) andNotify Node Down.
For more details on how the HSM Replication mechanism works, see the topic Replication.
Dinamo - Remote Management Console v. 4.7.12.3 2018 (c) Dinamo Networks
HSM 127.0.0.1 e - Engine 5.0.22.0 (DXP) - TCA0000000 - ID master
HSM - Replication
1 - Info
2 - Nodes
3 - Refresh
4 - Cross Check
5 - Notify Node Down
0 - Main Menu
Option:
Information
Option 1 displays general information about the configuration and status of Replication on the node to which the console is connected.
If the HSM to which the Remote Console is connected does not belong to a Replication Domain, only the Sync Point information is displayed.
Dinamo - Remote Management Console v. 4.7.12.3 2018 (c) Dinamo Networks
HSM 127.0.0.1 e - Engine 5.0.22.0 (DXP) - TCA0000000 - ID master
HSM - Replication - Info
Joined Repl Dmn : -
Sync Point : BCC787FD954B8979 3737
Press ENTER key to continue...
If the HSM belongs to a Replication Domain, the information will be displayed:
- Domain name: name as defined by the operator to group the nodes.
- Sync Point Value: value of the current Sync Point in the HSM, and also the SPVV value (Sync Point Verification Value).
- Interface Binding: the node's interfaces are listed with their IP addresses, and if there is Binding configured on any of them, it is indicated with an '*'.
- Policy: values of the replication policy timers;
- Node list: this is the list of nodes with which this HSM will replicate transactions whenever it takes on a coordinator role, i.e. initiates a replicated transaction.
Dinamo - Remote Management Console v. 4.7.12.3 2018 (c) Dinamo Networks
HSM 127.0.0.1 e - Engine 5.0.22.0 (DXP) - TCA0000000 - ID master
HSM - Replication - Info
Joined Repl Dmn : production
Sync Point : 65615963B06064EB 3173
Interface Binding : [1] - 10.0.62.44
[2] - 172.16.1.2
Policy : Manager Pulsing - 93 secs
Recovery Pulsing - 93 secs
Node List : 10.0.62.18
Press ENTER key to continue...
If the HSM has a pending replication transaction(PTL), the details of the pending transaction are displayed in addition to the information shown above:
- Date and time: time when the pending transaction took place;
- GUID: unique identifier of the transaction;
- Status: phase of the communication protocol in which the transaction is stopped;
- Type: type of transaction being carried out;
- Nodes: the nodes with which the transaction coordinator node is trying to replicate, the first IP is always the current transaction coordinator, and the node marked with a P is the node that is pending confirmation.
Dinamo - Remote Management Console v. 4.7.12.3 2018 (c) Dinamo Networks
HSM 127.0.0.1 e - Engine 5.0.22.0 (DXP) - TCA0000000 - ID master
HSM - Replication - Info
PTL : Date/Time - 2013-12-18 20:56:24
GUID - 0807060504030201
State - Phase 2 - Coordinator
Type - Undefined
Nodes - 10.0.62.44
- 10.0.62.18 P
Joined Repl Dmn : production
Sync Point : 65615963B06064EB 3173
Interface Binding : [1] - 10.0.62.44
[2] - 172.16.1.2
Policy : Manager Pulsing - 93 secs
Recovery Pulsing - 93 secs
Node List : 10.0.62.18
Press ENTER key to continue...
Nodes
In option 2 the operator can perform administrative actions with the nodes in the Replication Domain, such as listing, adding, removing and testing.
Danger
See the Node List topic on the impacts of manually adding and removing nodes from a Replication Domain.
In the add, remove and test actions, the operator must enter the node's IP address. These actions are available in the Remote Console as an administrative facility, and should be used with discretion and understanding by the operator.
Dinamo - Remote Management Console v. 4.7.12.3 2018 (c) Dinamo Networks
HSM 127.0.0.1 e - Engine 5.0.22.0 (DXP) - TCA0000000 - ID master
HSM - Replication - Nodes
1 - List
2 - Add
3 - Delete
4 - Test
0 - Main Menu
Option:
Refresh
In option 3, the operator can restart the replication service timers on the node to which it is connected. For more details on the replication policy timers, see the Policy topic.
Dinamo - Remote Management Console v. 4.7.12.3 2018 (c) Dinamo Networks
HSM 127.0.0.1 e - Engine 5.0.22.0 (DXP) - TCA0000000 - ID master
HSM - Replication - Refresh
Update Replication Service (y/[n]):y
Replication service updated successfully.
Press ENTER key to continue...
Cross Check
It sends a cross-test request to the connected HSM. From there, each HSM in the pool will report which nodes it has configured in its list and the current state of communication with each node. The reports are consolidated and an overview is presented to the user
On HSMs with an older firmware version, this test is carried out from the user's station and not from the connected HSM, and will be a much more limited test.
Dinamo - Remote Management Console v. 4.7.12.3 2018 (c) Dinamo Networks
HSM 127.0.0.1 e - Engine 5.0.22.0 (DXP) - TCA0000000 - ID master
HSM - Replication - Cross Check
this 01 node(s)
version : 5.0.22.0
node list :
10.61.53.118
10.61.53.118 01 node(s)
version : 5.0.22.0
node list :
10.61.53.116
Press ENTER key to continue...
Node Down
In option 5 it is possible to notify the pool of a node with a problem, which should be removed from the replication list of all nodes in the Domain. The operator notifies the node to which it is connected and the latter takes care of transmitting the information to the other nodes. Before broadcasting the notification to the other nodes. The Console only returns to the operator after receiving confirmation from all the nodes on the list.
Dinamo - Remote Management Console v. 4.7.12.3 2018 (c) Dinamo Networks
HSM 127.0.0.1 e - Engine 5.0.22.0 (DXP) - TCA0000000 - ID master
HSM - Replication - Notify Node Down
Node Down IP Address : 10.0.62.18
Node Down notification of 10.0.62.18 successfully sent.
Press ENTER key to continue...
The HSM performs some connection tests with the reported address of the problem node, to ensure that the node really is out of communication. Therefore, if the operator accidentally enters the address of an active and operational node, the notification is ignored and the node remains in the pool's replication list.
Dinamo - Remote Management Console v. 4.7.12.3 2018 (c) Dinamo Networks
HSM 127.0.0.1 e - Engine 5.0.22.0 (DXP) - TCA0000000 - ID master
HSM - Replication - Notify Node Down
Node Down IP Address : 10.0.62.18
Error notifying node down IP. Invalid event. Tried to send node down message but the node is not down. (37018)
Press ENTER key to continue...