show ancp neighbor

Version

Version of the ANCP implementation:

• 0x31—General Switch Management Protocol (GSMP) version 3, sub-version 1; ANCP version before RFC 6320, Protocol for Access Node Control Mechanism in Broadband Networks.

• 0x32—ANCP version 1, defined in RFC 6320, Protocol for Access Node Control Mechanism in Broadband Networks.

IP Address

IP address of the ANCP neighbor.

PartId

Number that associates the ANCP message with a specific partition.

State

Operational state of the ANCP adjacency:

• Configured—The neighbor has been configured, but has never been in the Established state. An asterisk (*) is prefixed to the neighbor entry for this state.

• Establishing—Adjacency negotiations are in progress for the neighbor. An asterisk (*) is prefixed to the neighbor entry for this state. This state is rarely seen because the adjacency is established so quickly.

• Established—Adjacency negotiations have succeeded for the neighbor and an ANCP session has been established.

• Not Estblshed—Not Established; adjacency negotiations are ready to begin. Indicates that this neighbor previously had been in the Established state; that is, it has lost a previously established adjacency. An asterisk (*) is prefixed to the neighbor entry for this state.

Time

How long the adjacency has been up in one of the following formats:

• nwndnh—number of weeks, days, and hours

• nd hh:mm:ss—number of days, hours, minutes, and seconds

Subscriber Count

Number of subscribers associated with the ANCP neighbor (access local loop).

Capabilities

Negotiated ANCP capability:

• Topo—Topology discovery.

• OAM—Performance of local Operations Administration Maintenance (OAM) procedures on an access loop controlled by the router.

System Name

MAC address of the ANCP neighbor.

TCP Port

TCP port on which ANCP messages are exchanged.

System Instance

Number identifying the ANCP link instance from the edge device’s perspective.

Peer Instance

Number identifying the ANCP instance from the access node’s perspective. This number is unique and changes when the node or link comes back up after going down.

Timer

Adjacency timer value advertised by the ANCP peer in 100 ms increments; the interval between ANCP ACK messages. This value remains constant for the duration of an ANCP session.

Partition Type

Number that identifies whether partitions are used and how the ID is negotiated:

• 0—No partition.

• 1—Fixed partition requested.

• 2—Fixed partition assigned.

Partition Flag

Number that specifies the type of partition requested: 1 (new adjacency) or 2 (recovered adjacency).

Partition Identifier

Number that identifies a logical partition of an access node with which the ANCP agent has formed an adjacency.

A value of zero indicates that the agent supports each neighbor on an IP address over a single TCP session with a partition ID of zero. This is the default support case.

A nonzero value indicates that the agent supports each neighbor on an IP address over a single TCP session with a nonzero partition ID.

Partition Adjacencies

Number of adjacencies that share the partition.

Dead Timer

Remaining period that the edge device waits for adjacency packets from a neighbor before declaring the neighbor to be down. The maximum dead time value is three times the configured adjacency timer value. This field displays the current value based on the time that the last adjacency packet was received.

Received Syn Count

Number of synchronization messages received from neighbors to maintain adjacencies.

Received Synack Count

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

Received Rstack Count

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

Received Ack Count

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

Received Port Up Count

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

Received Port Down Count

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

Received Generic Resp Count

Number of generic response messages received from neighbors.

Received Adjacency Update Count

Number of adjacency update messages received from neighbors.

Received OAM Count

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

Received Other Count

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

Sent Syn Count

Number of synchronization messages sent to neighbors to maintain adjacencies.

Sent Synack Count

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

Sent Rstack Count

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

Sent Ack Count

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

Sent Generic Resp Count

Number of generic response messages sent to neighbors.

Sent OAM Count

Number of OAM request commands sent to neighbors.

Max Discovery Limit Exceed Count

Number of times that the maximum number of discovery table entries accepted from the neighbor has been exceeded.

Result Codes

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

• Invalid Request Message Count—A properly formed request message 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—ANCP 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.