The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Access Node Control Protocol (ANCP) feature enhances communication between Digital Subscriber Line Access Multiplexers (DSLAMs) and a broadband remote access server (BRAS), enabling the exchange of events, actions, and information requests between the multiplexer end and the server end. As a result, either end can implement appropriate actions.
To run ANCP over Transmission Control Protocol (TCP), IP must be enabled on broadband remote access servers (BRAS). Interactions from RADIUS to the BRAS are not required for ANCP and are dependent on the RADIUS server.
For information about release and platform support, see the Feature Information for Access Node Control Protocol.
Cisco IOS XE Release 2.4 supports interactions with the RADIUS server from the broadband remote access server (BRAS). Interactions from RADIUS to the BRAS are not required for ANCP and are dependent on the RADIUS server.
ANCP is used to aggregate traffic from multiple subscribers and deliver information for any application, while remaining independent from the application. ANCP is currently used in the application between DSLAMs and the broadband remote access server in a digital subscriber line (DSL) broadband environment.
The ANCP feature enables close communication between DSL aggregation multiplexers (DSLAMs) and network edge devices. Using ANCP between DSLAMs and a BRAS enables exchange of events, actions, and information requests so that the appropriate actions occur at the DSLAM and BRAS.
The ANCP architecture supports the following uses of ANCP:
Rate adaptive mode helps to maximize the line bit rate for a given line, and the rate is dependent on the quality of the signal achieved on the line. Rate adaptive mode conveys DSL modem line rate from a DSLAM to a broadband remote access server.
A BRAS running ANCP listens for TCP requests from its ANCP neighbors (DSLAMs).
After a TCP session is established--ANCP begins exchanging messages to establish adjacency between the BRAS and its neighbors.
After adjacency is established--ANCP event messages can be sent from the DSLAM to the BRAS.
Rate adaptive DSL uses signal quality to adjust line speeds. A BRAS typically sets the subscriber interfaces to the maximum bandwidth agreed to in the service license agreement (SLA).
When customer premises equipment (CPE) is synchronized to a data rate that is lower than the line speed, cell or packet loss occurs on the DSLAM. To prevent this, the DSLAM can use ANCP to notify the BRAS of newly adjusted circuit rates.
When a customer-facing port:
Activates -- The DSLAM sends a Port Up message to the BRAS. The appropriate quality of service (QoS) takes effect in accordance with the ANCP-delivered information.
Deactivates -- The DSLAM sends a Port Down message to the BRAS. ANCP reports the DSL state sent by the DSLAM, which is typically Silent or Idle. If the broadband remote access server receives another Port Up message, the subscriber sessions either time out or are renewed with a new shaping rate. The shaping rate on the interface does not change until the router receives a new Port Up message.
Interactions between the broadband remote access server and the RADIUS server are from the router to RADIUS.
The BRAS sends the following attributes and attribute-value pairs (AVPs) to the RADIUS server:
|
ANCP Line Rates |
Upstream Data Rate |
Downstream Data Rate |
Output Policy Name |
|---|---|---|---|
|
VSA 39 |
Attribute 197, Ascend-Data-Rate |
Attribute 255, Ascend-Xmit-Rate |
Attribute 77, Connect-Speed-Info |
|
Attribute Type 38, Rx Connect Speed AVP |
Attribute Type 24, Tx Connect Speed AVP |
The BRAS uses Point-to-Point Protocol (PPPoE) to interact with the authentication, authorization, and accounting (AAA) module. RADIUS processes the information and then takes appropriate action.
Port mapping associates customer premises equipment (CPE) clients of a DSLAM with VLAN subinterfaces on the BRAS. The VLANs include 802.1Q or queue-in-queue (Q-in-Q) hierarchical VLANs. Port mapping is configured in global configuration mode on the BRAS by grouping CPE client IDs with a specific DSLAM neighbor.
There are two methods you can use to map ports: configure all VLAN subinterfaces first, and the ANCP neighbor mappings next. Or, you can configure the mappings directly under the interface.
For example, the following commands configure port mapping for Q-in-Q VLAN subinterfaces:
ancp neighbor name
dslam-name
id
dslam-id
dot1q
outer-vlanid
second-dot1q
inner-vlanid
[interface
type number
] client-id
"
client-id
"
or
ancp neighbor name
dslam-name
id
dslam-id
dot1q
outer-vlanid
client-id
"
client-id
"
The client-id is a unique access-loop-circuit-id that the DSLAM sends to the BRAS for each unique port. The DSLAM sends this ID in the ANCP Port Up event message. The access-loop-circuit-id uses a defined format consisting of an access node identifier and digital subscriber line (DSL) information as mentioned below:
" access-node-identifier atm slot/module/port . subinterface : vpi . vci "
" access-node-identifier ethernet slot / module / port . subinterface [: vlan-id ]"
The BRAS sets the default state as Down, on all ports of the router, until the DSLAM sends a Port Up message.
ANCP provides an out-of-band control channel for performing noninteractive operation, administration, and maintenance (OAM) operations from the broadband remote access server. This channel enables router operators to view the ANCP port state of specific DSLAM ports. ANCP port state information is stored in the ANCP dynamic database on the BRAS.
The Interactive OAM and Scaling Improvements feature adds on-demand ping capability to ANCP for operations and troubleshooting.
 Note |
This feature is enabled by default and requires no configuration. |
ANCP is an extension of the General Switch Management Protocol (GSMP). GSMP defines a primary-secondary neighbor relationship in which the primary neighbor initiates a connection to a secondary neighbor. In ANCP, this primary-secondary relationship is reversed: the BRAS (primary) listens and accepts incoming ANCP connections from the DSLAM (secondary). The DSLAM uses event messages to communicate asynchronous events to the BRAS, such as topology changes and Port Down or Port Up events.
GSMP connectivity between the BRAS and the DSLAM occurs over TCP/IP (RFC 3293). The DSLAM initiates the connection to the router and the router accepts the connection if the appropriate interface is ANCP enabled.
The GSMP Adjacency Protocol establishes GSMP neighbor relationships.
During the adjacency-building:
The DSLAM and router negotiate their capabilities and determine the synchronization state between the two ends.
GSMP detects whether the router and the DSLAM have retained a local information database state in case of a transport failure, or whether both devices require a state update.
If GSMP determines that it must resynchronize the adjacency, it restarts the adjacency synchronization process, which includes the capability negotiation defined in the ANCP extension draft available at:
http://tools.ietf.org/id/draft-wadhwa-gsmp-l2control-configuration-02.txt
In an ANCP, if a neighbor (neighbor1) contains capabilities that its neighbor (neighbor2) does not support, neighbor1 turns off the capabilities and recommunicates the packets to neighbor2 with the same set of capabilities as neighbor2.
After both the neighbors agree to the same set of capabilities, adjacency is established.
To configure ANCP, perform the following global or interface configuration tasks:
Perform this task to enable ANCP on an Ethernet interface.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ancp adjacency timer interval Example: |
Sets the ANCP adjacency timer interval, which specifies the amount of time to wait before sending an ANCP hello packet to the DSLAM. |
| Step 4 |
interface type number Example: |
Enters interface configuration mode to define an interface. |
| Step 5 |
ip address address mask Example: |
Assigns an IP address and subnet mask to the interface. |
| Step 6 |
ancp enable Example: |
Enables ANCP on the interface where IP is configured. |
| Step 7 |
interface type number . subinterface Example: |
Enters subinterface configuration mode to define a subinterface. |
| Step 8 |
encapsulation dot1q vlanid [second-dot1q second-vlanid ] Example: |
Enables dot1q VLAN encapsulation on the subinterface for a single-queue 802.1Q VLAN or for Q-in-Q hierarchical VLANs. |
| Step 9 |
exit Example: |
Exits subinterface configuration mode. |
The ancp enable command should be configured only for the control VCs on which the ANCP message is sent from the DSLAM. Perform this task to enable ANCP on ATM interfaces.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ancp adjacency timer interval Example: |
Sets the ANCP adjacency timer interval, which specifies the amount of time to wait before sending an ANCP hello packet to the DSLAM. |
| Step 4 |
interface atm slot / subslot / port . subinterface Example: |
Enters subinterface configuration mode to define a subinterface. |
| Step 5 |
ip address ip-address mask Example: |
Assigns an IP address and subnet mask to the subinterface. |
| Step 6 |
pvc vpi / vci Example: |
Enters ATM virtual circuit configuration mode to enable an ANCP connection over ATM PVC. |
| Step 7 |
ancp enable Example: |
Enables ANCP on the interface where IP is configured. |
| Step 8 |
exit Example: |
Exits ATM virtual circuit configuration mode. |
Perform this task to map DSLAM ports to VLAN interfaces on the BRAS.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ancp atm shaper percent-factor factor Example: |
Enables ANCP cell tax accounting for ATM U-interface connections |
| Step 4 |
interface type number.subinterface Example: |
Enters interface configuration mode for the specified subinterface. |
| Step 5 |
encapsulation dot1q vlan-id Example: |
Enables IEEE 802.1Q encapsulation of traffic on a specified VLAN. |
| Step 6 |
ancp neighbor name dslam-name [id dslam-id ] client-id client-id Example: |
Specifies the ANCP access DSLAM to which VLAN subinterfaces are mapped. |
| Step 7 |
exit Example: |
Exits subinterface configuration mode. |
The ancp neighbor name command is available under pvc and pvc-in-range command modes. This command creates a one-to-one mapping between a PVC and a DSLAM port. Perform this task to map DSLAM ports to PVC interfaces on the BRAS.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
ancp atm shaper percent-factor factor Example: |
Enables ANCP cell tax accounting for ATM U-interface connections. |
| Step 4 |
interface atm slot / subslot / port . subinterface Example: |
Enters interface configuration mode for the specified ATM subinterface. |
| Step 5 |
Do one of the following:
Example:Example:Example: |
Creates a one-to-one mapping between a PVC and DSLAM port and enters ATM virtual circuit configuration mode. or Defines a range of ATM PVCs and enters PVC range configuration mode.
|
| Step 6 |
pvc-in-range vpi / vci Example: |
(Optional) Configures an individual PVC within a range in PVC range configuration mode. |
| Step 7 |
ancp neighbor name dslam-name [id dslam-id ] client-id client-id Example: |
Specifies the ANCP access DSLAM to which PVC subinterfaces are mapped.
|
| Step 8 |
end Example: |
Exits PVC range configuration mode. |
The following example shows how to enable ANCP on Ethernet subinterface 2/0/1.
interface GigabitEthernet 2/0/1
ip address 192.168.64.16 255.255.255.0
ancp enable
!
interface GigabitEthernet 2/0/1.1
encapsulation dot1q 100 second-dot1q 200
!
ancp adjacency timer 100The following example shows how to enable ANCP on ATM subinterface 2/0/1.1.
interface ATM2/0/0.1 point-to-point
description ANCP Link to one DSLAM
no ip mroute-cache
ip address 192.168.0.2 255.255.255.252
pvc 254/32
protocol ip 192.168.0.1
ancp enable
no snmp trap link-statusThe following example shows how to map the CPE client ports of a DSLAM to Q-in-Q VLAN subinterfaces on the BRAS. In the example, the DSLAM neighbor named dslam1 with an IP address of 192.68.10.5 has a CPE client port mapped to Q-in-Q VLANs 100 and 200 configured on Ethernet interface 1/0/0.2. Another CPE client port is mapped to Q-in-Q VLANs 100 and 100 configured on Ethernet interface 1/0/0.1.
interface GigabitEthernet1/0/0.1
encapsulation dot1q 100 second-dot1q 100
ancp neighbor name dslam1 id 192.168.10.5 client-id "192.168.10.5 ethernet1/0/0.2"
!
interface GigabitEthernet1/0/0.2
encapsulation dot1q 100 second-dot1q 200
ancp neighbor name dslam1 id 192.168.10.5 client-id "192.168.10.5 ethernet1/0/0.1"
!
ancp atm shaper percent-factor 95
!The example shown above maps the ports directly at the subinterface level. You can also configure all VLAN subinterfaces first, and perform the mappings under ANCP neighbor next, as shown in the following example:
interface GigabitEthernet1/0/0.1
encapsulation dot1q 100 second-dot1q 100
!
interface GigabitEthernet1/0/0.2
encapsulation dot1q 100 second-dot1q 200
!
ancp atm shaper percent-factor 95
!
ancp neighbor name dslam1 id 192.168.10.5
dot1q 100 second-dot1q 100 interface GigabitEthernet1/0/0.1 client-id "192.168.10.5 ethernet1/0/0.2"
!
ancp neighbor name dslam1 id 192.168.10.5
dot1q 100 second-dot1q 200 interface GigabitEthernet1/0/0.2 client-id "192.168.10.5 ethernet1/0/0.2"The ancp neighbor name command maps the CPE client ports of a DSLAM to PVC interfaces on the BRAS. This command can be configured either globally or under PVC/PVC-in-Range mode.
In this example, the router interfaces with one DSLAM which has two ports or clients.
interface ATM2/0/0.1 point-to-point
description ANCP Link to one DSLAM
no ip mroute-cache
ip address 192.168.0.2 255.255.255.252
pvc 254/32
protocol ip 192.168.0.1 255.255.255.252
ancp neighbor name dslam1 id 192.168.10.5 client-id "dslam-port-x-identifier"
no snmp trap link-status
!
interface ATM1/0/0.1 multipoint
description TDSL clients - default TDSL 1024
class-int speed:ubr:1184:160:10
range pvc 10/41 10/160
service-policy input SET-PRECEDENCE-0
service-policy output premium-plus:l2c:25088
pvc-in-range 10/103
description TDSL client 16 Mbps with ANCP
class-vc speed:ubr:17696:1184:05
ancp neighbor name dslam1 id 192.168.10.5 client-id "dslam-port-x-identifier"
!
range pvc 11/41 11/160
service-policy input SET-PRECEDENCE-0
service-policy output premium-plus:l2c:25088
pvc-in-range 11/108
description TDSL client 16 Mbps with ANCP
class-vc speed:ubr:17696:1184:05
ancp neighbor name dslam1 id 192.168.10.5 client-id "dslam-port-y-identifier"
!When the ancp neighbor command is configured globally, the PVC information for the ATM interface must also be specified, as shown in the following example:
interface ATM1/0/0.1 multipoint
description TDSL clients - default TDSL 1024
class-int speed:ubr:1184:160:10
range pvc 10/41 10/160
service-policy input SET-PRECEDENCE-0
service-policy output premium-plus:l2c:25088
pvc-in-range 10/103
description TDSL client 16 Mbps with ANCP
class-vc speed:ubr:17696:1184:05
!
range pvc 11/41 11/160
service-policy input SET-PRECEDENCE-0
service-policy output premium-plus:l2c:25088
pvc-in-range 11/108
description TDSL client 16 Mbps with ANCP
class-vc speed:ubr:17696:1184:05
!
ancp neighbor name dslam1 id 192.168.10.5
atm 10/103 interface ATM1/0/0.1 client-id "dslam-port-x-identifier"
atm 11/108 interface ATM1/0/0.1 client-id "dslam-port-y-identifier"|
Related Topic |
Document Title |
|---|---|
|
Cisco IOS commands |
|
|
ANCP Commands |
Cisco IOS Access Node Control Protocol Command Reference |
|
IEEE 802.1Q VLAN |
Configuring Routing Between VLANs with IEEE 802.1Q Encapsulation |
|
Queue-in-Queue VLAN Tags |
IEEE 802.1Q-in-Q VLAN Tag Termination |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
Access Node Control Protocol |
Cisco IOS XE Release 2.4 |
In Cisco IOS XE Release 2.4, this feature was introduced on the Cisco ASR 1000. The following command was introduced: ancp vdsl ethernet shaper . |
|
Interactive OAM and Scaling Improvements |
Cisco IOS XE Release 2.4 |
The Interactive OAM and Scaling Improvements feature adds on demand ping capability to ANCP for operations and troubleshooting. In Cisco IOS XE Release 2.4, this feature was introduced on the Cisco ASR 1000. The following commands were introduced or modified: ping ancp , show ancp neighbor port , show ancp port , show ancp session , show ancp session adjacency , show ancp session event , and show ancp statistics . |
Feedback