Monitoring Your DMR Cluster
If there are problems with your event mesh, for example if DMR is configured incorrectly or if there are operational problems in the network, one or more brokers may report topology errors or DMR being operationally down.
Topology Errors and Troubleshooting
Topology errors are caused by problems in the configured or operational network topology.
Topology problems are expected while adding and removing nodes in a network, because configuration changes need time to propagate through the event mesh. However, if you following the procedures in this documentation, no message loss is expected, and the topology problem should be temporary and clear by itself.
Some examples of topology errors are:
- missing links—every node in a cluster must be connected by an internal link. Links must be bi-directional; that is, each link must be configured correctly on both nodes.
- mismatched link span—a link is either internal (connecting two nodes within a cluster) or external (connecting gateway nodes in two different clusters). The configuration at both ends of the link must match.
- missing channels—each link must have a control channel plus one data channel per message VPN.
- node name mismatch—each node must correctly specify the name of the remote node connected by the link.
- DMR is not correctly enabled—each participating VPN must opt in to DMR. In addition, for nodes connected by an internal link, the list of Message VPNs participating in DMR on each node must be the same.
DMR can be operationally down for other reasons, such as:
- misconfiguration in other areas, such as replication or redundancy
- problems with Guaranteed Messaging (e.g., the message spool is down)
- issues with cluster authentication
If there is a topology error, or DMR is down for some other reason, subscription propagation and data forwarding throughout the network may not be working properly.
To troubleshoot issues with your event mesh, use the commands in the sections that follow to view the configuration and operational status of the objects in the mesh. Start by looking at the cluster information, then the links, then the channels. That is, start at the widest level of detail (the cluster) and narrow down your focus (first link, then channel) as needed.
Displaying Cluster Information
To display cluster information, enter the following command:
show cluster <cluster-name-pattern> [detail]
Where:
<cluster-name-pattern> displays clusters matching the pattern. The cluster pattern can be the cluster's full name, or part of its name with the wildcard character ? used to represent one character of the name, or the wildcard character * used to represent zero or more characters of the name. Entering only the wildcard character * for the name displays all clusters.
detail displays detailed information for the specified cluster.
Displaying Cluster Link Information
To display cluster link information, enter the following command:
show cluster <cluster-name-pattern> link <link-name-pattern> [detail | client-profile | queue | ssl]
Where:
<cluster-name-pattern> displays clusters matching the pattern.
<link-name-pattern> displays cluster links matching the pattern. The link pattern can be the link's full name, or part of its name with the wildcard character ? used to represent one character of the name, or the wildcard character * used to represent zero or more characters of the name. Entering only the wildcard character * for the name displays all cluster links.
detail displays detailed information for the specified link.
client-profile displays cluster link client profile information for the specified link.
queue displays cluster link queue information for the specified link.
ssl displays cluster link TLS/SSL information for the specified link.
Displaying Cluster Channel Information
To display cluster link channel information, enter the following command:
show cluster <cluster-pattern> link <link-pattern> channel message-vpn <vpn-name> [detail]
Where:
<cluster-name-pattern> displays clusters matching the pattern.
<link-name-pattern> displays cluster links matching the pattern.
<vpn-name> displays channel information for the specified Message VPN.
detail displays detailed channel information for the specified link.
Displaying Message VPN Information
To display DMR information for a particular Message VPN, enter the following command:
show message-vpn <vpn-name> dynamic-message-routing [dmr-bridge <remote-node-name-pattern>]
Where:
<vpn-name> displays DMR information for the specified Message VPN.
<remote-node-name-pattern> displays information for DMR bridges that connect to the specified remote node.