For feedback and comments:
documentation.feedback@alcatel-lucent.com

Table of Contents Previous Next PDF


Configuring Triple Play Services with CLI
This section provides information to configure Residential Broadband Aggregation services using the command line interface. It is assumed that the reader is familiar with basic configuration of VPLS, IES and VPRN services.
Topics in this section include:
 
Configuring VPLS Residential Split Horizon Groups
To configure a group of SAPs in a VPLS service as a Residential Split Horizon Group (RSHG), add the residential-group parameter when creating the split horizon group. Traffic arriving on a SAP within an RSHG will not be copied to other SAPs in the same split horizon group. Note that the split horizon group must be created before it can be applied.
The following example displays a VPLS configuration with split horizon enabled:
*A:ALA-48>config>service>vpls# info
----------------------------------------------
            split-horizon-group "DSL-group2" residential-group create
                description "split horizon group for DSL - no broadcast supported"
            exit
            stp
                shutdown
            exit
            sap 2/1/4:100 split-horizon-group "DSL-group2" create
                description "SAP in RSHG"
            exit
            sap 2/1/4:200 split-horizon-group "DSL-group2" create
                description "another SAP in the RSHG"
            exit
            no shutdown
----------------------------------------------
*A:ALA-48>config>service>vpls#
 
Configuring Static Hosts
In order for the static host to be operational, forwarding traffic bi-directional, the mac address of the host must be learned or configured. Learning the MAC of the static host is different for IPv4 or IPv6.
If an IPv4 static host MAC is not specified
If an IPv6 static host MAC is not specified
The learned MAC address will be handled as a MAC address of static host with explicitly defined mac-address. Meaning:
Every time the given static-host uses different MAC address in its ARP request, the dynamic MAC learning process will be performed. The old MAC address will be overwritten by a new MAC address.
The learned MAC address will not be made persistent (a static host is not a part of the persistency file). A service discontinuity of such a host could be proportional to its arp-cache timeout.
The following interactions are described:
 
BNG Learning IP-Only Static Host’s MAC Address
Before an IP-only static host can forward or receive traffic, the MAC of the host must be learned by the BNG. The learned MAC is used to fill in the anti-spoof entry for the static host. Table 6 summarizes the different methods that the BNG could use to learn the IP only static host MAC address.
 
 
IP-only static hosts without a MAC address are put into a “non-forwarding” state and are not be able to send or receive traffic. The BNG must populate the MAC address using the methods described in the table above to put the host into a “forwarding” state. If the IPv4 static host sends an ARP, then the IPv4 address along with Ethernet header source MAC can populate the IP-only host MAC address. For IPv6, the subscriber must send in a NS using the GUA to allow the BNG to resolve the MAC address. If the IP-only host is an IPv6 prefix, NS using the GUA can also resolve the static host MAC address, provided that the GUA is within the subnet of the prefix. n IPv6 prefix host can only have one MAC association, multiple bridged hosts using a single IPv6 prefix is not supported. To support multiple bridge hosts on a SAP, individual /128 host must be configured along with enabling ipoe-bridge-mode.
 
Static Host Learning the IPv6 Default Gateway Address
Static hosts also need to resolve the default gateway and MAC in order to forward traffic. Static hosts can learn the BNG MAC using the following methods.
1.
2.
3.
A host’s RS/NS messages might use link-local as the source address. The host’s link-local addresses are unknown to the BNG, since the BNG only knows static hosts by their GUA. By default, unknown host’s RS/NS messages are dropped. Therefore, static hosts cannot resolve their default gateway/MAC address. There are two different methods to enable the BNG to respond to static host’s RS/NS messages. The first solution is to declare the SAP as a single-mac. When a SAP is configured as a “single-mac”, it is declaring that only a single host is expected on the SAP and any RS/NS sent by the host will automatically populate the MAC table. The BNG in return will also respond to the static host’s RS/NS. The second solution is for cases where multiple hosts are on the SAP. RS/NS might not provide enough information to populate the subscriber host’s MAC because the source IP are link-local addresses. The BNG anti-spoof will only reply to known hosts RS/NS; therefore, these static hosts’ RS/NS are dropped. The group interface has a configuration option to auto-reply to any RS/NS, which will allow the static host to resolve their default gateway/route. Afterwards, the static host can send traffic to the BNG, which the BNG can use for MAC learning. To use data packets for MAC learning, the BNG has a “data-trigger” learning option for static hosts.
 
 
 
 
Configuring Static Hosts on an VPLS SAP
The following example displays a static host on a VPLS SAP configuration:
*A:ALA-48>config>service# info
----------------------------------------------
vpls 800 customer 6001 create
	description "VPLS with residential split horizon for DSL"
	stp
		shutdown
	exit
	sap 1/2/7:100 split-horizon-group "DSL-group2" create
		description "SAP for RSHG"
		static-host ip 10.1.1.1
	exit
	no shutdown
----------------------------------------------
*A:ALA-48>config>service#
 
Configuring Static Hosts on an IES SAP
The following displays a static host on an IES SAP:
*A:ALA-49>config>service>ies>sub-if>grp-if# info
----------------------------------------------
	sap 7/1/5 create
	description "IES with static host"
		static-host ip 10.1.1.1 create
		static-host ip 2001::1/128 create
		static-host ip 2001:1::/64 create
	exit
----------------------------------------------
*A:ALA-49>config>service>ies#
 
Configuring Static Hosts on an VPRN SAP
The following displays a static host on a VPRN SAP:
*A:ALA-49>config>service>vprn>sub-if>grp-if# info
----------------------------------------------
	description "VPRN service with static host"
	sap 7/1/5 create
		description "IES with static host"
		static-host ip 10.1.1.1 create
		static-host ip 2001::1/128 create
		static-host ip 2001:1::/64 create
	exit
----------------------------------------------
*A:ALA-49>config>service>vprn#