The following is a deployment example scenario.
CLI syntax:
config
subscriber-mgmt
auto-sub-id-key
ppp-sub-id-key sap-id
ipoe-sub-id-key mac circuit-id
CLI syntax:
config
service vprn 10
subscriber-interface <ip-int-name>
authentication-policy <auth-pol-name>
group-interface <ip-int-name>
sap 1
sub-sla-mgmt
def-sub-id use-sap-id
sub-ident-policy <ident-pol-name>
sap 2
sub-sla-mgmt
def-sub-id auto-id
sub-ident-policy <ident-pol-name>
sap 3
sub-sla-mgmt
def-sub-id ‟sub3”
sub-ident-policy <ident-pol-name>
sap 4
sub-sla-mgmt
sub-ident-policy <ident-pol-name>
Assume the following cases:
RADIUS returns the sub-id on all four SAPs.
RADIUS does not return the sub-id string on any of the SAPs.
In the first case where RADIUS returns the sub-id string, on all four SAPs, the sub-id string is assigned by the RADIUS server. Defaults have no effect, and neither do identifiers specified under the auto-sub-id-key node.
In the second case, the effects are the following:
On SAP1 the sub-id name is the sap-id (1/1/1:3)
On SAP 2 the sub-id name is the sap-id for PPPoE hosts and <mac>-<circuit-id> concatenation for IPoE type hosts.
On SAP3 the sub-id name is the literal ‛sub3’ for PPPoE and IPoE hosts.
On SAP4 the sub-id name is a semi-random value based on the sap-id for PPPoE hosts and the <mac, circuit-id> combination for IPoE hosts.