[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring VPN Aggregation

VPN aggregation configurations have the following requirements.

All interfaces in a pool must belong to the same service PIC.
Logical interfaces cannot be in more than one pool.
All interfaces must have either family inet or family inet6 configured.
Logical unit 0 cannot be configured in a service interface pool.
The maximum number of service interfaces in a pool is 1000.
The service set must have a next-hop service that is set to the service interface pool; it cannot have inside and outside services.
The service set must have a PGCP rule.
In the virtual interface configuration, the service and physical interfaces must match interfaces configured in the VRF routing instance.
The virtual interface configuration must include all media services in the PGCP rule that is configured in the service set.

Step-by-Step Procedure

See Figure 23 for an illustration of this configuration.

To configure VPN Aggregation:

Configure a policy statement to be used for the vrf-import and vrf-export policies that you plan to configure in the routing instances.[edit] user@host#edit policy-options policy-statement policy-1[edit policy-options policy-statement policy-1] user@host#set term t1 then reject
Configure a VRF routing instance for each VPN.[edit] user@host#edit routing-instances vrf1[edit routing-instances vrf1] user@host#set instance-type vrf user@host#set interface fe-1/3/0.10 user@host#set interface sp-1/0/0.10 user@host#set route-distinguisher 10.10.10.11:0 user@host#set vrf-import policy-1 user@host#set vrf-export policy-1[edit] user@host#edit routing-instances vrf2[edit routing-instances vrf2] user@host#set instance-type vrf user@host#set interface ge-1/0/0.10 user@host#set interface sp-2/0/0.10 user@host#set route-distinguisher 10.10.10.22:0 user@host#set vrf-import policy-1 user@host#set vrf-export policy-1[edit] user@host#edit routing-instances vrf3[edit routing-instances vrf1] user@host#set instance-type vrf user@host#set interface fe-1/2/0.10 user@host#set interface sp-3/0/0.10 user@host#set route-distinguisher 10.10.10.33:0 user@host#set vrf-import policy-1 user@host#set vrf-export policy-1
Configure a pool of logical PGCP service interfaces that are configured in the VRF routing instances. [edit] user@host#edit services service-interface-pools pool pgcp-pool[edit services service-interface-pools pool pgcp-pool] user@host#set interface sp-1/0/0.10 user@host#set interface sp-2/0/0.10 user@host#set interface sp-3/0/0.10
Create a service set that links the VRF and the PGCP services. Specify the service interface pool as the next-hop service. The service set must contain a PGCP rule. It cannot contain any other type of rule. [edit] user@host#edit services service-set pgcp[edit services service-set pgcp] user@host#set next-hop-service service-interface-pool pgcp-pool user@host#set pgcp-rules pgcp-rule
Configure a virtual interface in the PGCP configuration for each VRF routing instance.[edit] user@host#edit services pgcp virtual-interface vif-1[edit services pgcp virtual-interface 1] user@host#set routing-instance vrf1 service-interface sp-1/0/0.10 user@host#set interface fe-1/3/0.10 user@host#set media-service access_ms[edit] user@host#edit services pgcp virtual-interface vif-2[edit services pgcp virtual-interface 2] user@host#set routing-instance vrf1 service-interface sp-2/0/0.10 user@host#set interface ge-1/0/0.10 user@host#set media-service core_ms[edit] user@host#edit services pgcp virtual-interface vif-3[edit services pgcp virtual-interface 1] user@host#set routing-instance vrf3 service-interface sp-3/0/0.10 user@host#set interface fe-1/2/0.10 user@host#set media-service access_ms

Configuring VPN Aggregation

Related Topics