Run this command on both the peers and make sure that each device shows up on the other correctly.

Use the show device-id command to check the device ID, as follows:

WAE#show device-id
System Device ID is: 00:21:5e:57:e9:d4

Verifying that a Serial Inline Cluster is Operational

Given the following topology example:

BR-WAE -----------WAN----------- DC-WAE2 -- DC-WAE1

or

BR-WAE1 -- BR-WAE2 -----------WAN----------- DC-WAE2 -- DC-WAE1

Normally, optimization should take place between the outermost WAEs, that is, BR-WAE and DC-WAE1, or BR-WAE1 and DC-WAE1. To ensure this, verify the device IDs on the connections by using the show statistics connection command. The PeerID on BR-WAE should indicate that it is optimizing with DC-WAE1 and the PeerID on DC-WAE1 should indicate that it is optimizing with BR-WAE.

If DC-WAE1 fails or goes into overload, new connections should be optimized between BR-WAE1 and DC-WAE2. You can verify this by using the show statistics connection optimized command on DC-WAE2. Optimized connections should be seen on DC-WAE2, with the peer ID of BR-WAE1 as the peer device.

If BR-WAE1 fails or goes into overload, there should not be optimization between DC-WAE2 and DC-WAE1. All connections should be in the "PT Non-optimizing Peer" state on DC-WAE1 and "PT No Peer" on DC-WAE2. An example of the expected show statistics connection command output follows:

You can also use the Central Manager Connection Statistics report (Device > Monitor > Optimization > Connections Statistics) to display device connection statistics in a table, as shown in Figure 1. The Peer IDs are indicated by device name.

Figure 1. Central Manager Device Connection Statistics Report

Detecting Serial Peer Configuration Mismatch

Serial peers must be configured so that each is designated as a non-optimizing peer with the other. If device A is configured as a peer of B, but B is not configured as a peer of A, that is a mismatch. To discover a mismatch, you can use the Central Manager My WAN > Configure > Peer Settings page, which reports on the status of all serial peers, as shown in Figure 2. All correctly configured serial peers have a green check mark in the Mutual Pair column. Any devices without a green check mark are incorrectly configured with a serial peer that is not also configured with the device as its serial peer.

Figure 2. Central Manager Peer Settings

To detect a serial peer configuration mismatch, you can also look for syslog messages such as the following:

Enabling Debug Logging

If looking at the dynamic policies and the filtering and auto-discovery statistics does not help, then enable debug logging so that a technical support engineer can troubleshoot what is happening with MAPI accelerated connections in a serial inline cluster.