show ancp statistics

Total count of ANCP neighbors.

Total count of ANCP subscribers.

Number of neighbor TCP/IP sessions accepted on listener socket.

Number of neighbor TCP/IP sessions that failed due to one of the following causes: session already exists, maximum number of ANCP connections exceeded, creation of session or neighbor failed, or protocol start failed.

Number of neighbor TCP/IP sessions that failed because the neighbor was not configured.

Number of synchronization messages received from neighbors to maintain adjacencies.

Number of synchronization acknowledgment messages received from neighbors in response to the node’s synchronization messages.

Number of messages received from neighbors indicating that the link to the neighbor needs to be reset.

Number of acknowledgment messages periodically received from neighbors after an adjacency has been established.

Number of status messages received from neighbors indicating that a port has transitioned to the up state.

Number of status messages received from neighbors indicating that a port has transitioned to the down state.

Number of generic response messages received from neighbors.

Number of adjacency update messages received from neighbors.

Number of OAM responses received from neighbors in reply to request commands.

Number of all other ANCP message packets received from neighbors that do not fit into one of the other categories.

Number of synchronization messages sent to neighbors to maintain adjacencies.

Number of synchronization acknowledgment messages sent to neighbors in response to the their synchronization messages.

Number of messages sent to neighbors indicating that the link to the neighbor needs to be reset.

Number of acknowledgment messages periodically sent to neighbors after an adjacency has been established.

Number of generic response messages sent to neighbors.

Number of OAM request commands sent to neighbors.

Number of generic response messages sent to neighbors that include each of the following result codes:

• Invalid Request Message Count—A properly formed request messages violated the protocol because of timing (such as a race condition) or direction of transmission.

• Specified Port(s) Down Count—One or more of the specified ports are down because of a state mismatch between the router and an ANCP control application.

• Out of Resources Count—the ANCP agent is out of resources, probably not related to the access lines. This result code is sent only by an access node.

• Request Msg Not Implemented Count—

• Malformed Msg Count—Message is malformed because it was corrupted in transit or there was an implementation error at either end of the connection.

• TLV Missing Count—One or more mandatory TLVs was missing from a request.

• Invalid TLV Contents Count—The contents of one or more TLVs in the request do not match its required specification.

• Non-Existent Port(s) Count—One or more of the ports specified in a request do not exist, possibly because of a configuration mismatch between the access node and the router or AAA.