Supported Platforms
Associating an Access Node with Subscribers for ANCP Operations
The ANCP agent on the router uses the access loop circuit identifier (ACI) to distinguish individual ANCP subscribers. Because the agent uses the ACI to associate (map) each subscriber to an interface or interface set, each ACI must be unique across all ANCP neighbors connected to the router.
 | Note: In earlier Junos OS releases, we recommend that the ACIs be unique across all neighbors, but this is not required. When the ACIs are not unique in the earlier releases, you can configure the subscribers to be uniquely identified by associating the IP address of the neighbor with the subscriber’s interface or interface-set. This configuration is no longer supported and the ACIs must be unique across your ANCP network. |
The ACIs can be statically or dynamically configured. When the subscriber’s DHCP or PPPoE discovery packets contain the ACI, then the agent can dynamically map it to the interface or interface set. Otherwise, the ACI must be statically configured. A static configuration overrides dynamic mapping of ACIs—and therefore subscribers—to interfaces or sets.
To associate an ACI with a set of VLAN interfaces for subscribers:
- Specify the name of the interface set and the unique ACI
for the access node.[edit protocols ancp interfaces]user@host# set interface-set vlan5 access-identifier “dslam port 2/3”
To associate an ACI with a single VLAN:
- Specify the logical interface and the unique ACI for the
access node.[edit protocols ancp interfaces]user@host# set ge-1/0/4.12 access-identifier “dslam port-2-10”
To associate an ACI with a static VLAN demux interface:
- Specify the logical interface and the unique ACI for the
access node.[edit protocols ancp interfaces]user@host# set demux0.100 access-identifier aci_100_1_0
