Static Subscribers Over Statically Configured Soft-GRE Tunnels
Service Providers using Wireless LAN (WLAN) to provide network access to subscribers can provision static subscribers over statically configured soft-GRE tunnels, including support for Authentication, Authorization and Accounting (AAA) services.
Provision Static Subscribers over Statically Configured Soft-GRE Tunnels
Service Providers are increasingly looking into Fixed Wireless for home users to take advantage of the 4G and 5G proliferation. While the local loop is wireless, these fixed wireless subscribers are managed by the wireline Broadband Network Gateway (BNG), thereby reducing the backend subscriber management requirements such as provisioning, billing, and more. Broadband edge subscriber services over soft-GRE tunnel are developed to support such Wifi Offload Gateway deployments, allowing L2 traffic between the customer premises equipment (CPE) and the broadband network gateway (BNG). Service Providers can now provision static IPv4 subscribers wherein IP address of the Customer Premises Equipment (CPE) router is statically configured on both the CPE and the BNG and the data is transmitted over statically configured soft-GRE tunnels. Control plane protocols such as PPPoE or DHCP do not run on the CPE to provision the CPE IP address.
Service providers can provision static subscribers over statically configured soft-GRE tunnels, including support for Authentication, Authorization and Accounting (AAA) services. Both the soft-GRE tunnel and the static subscriber must be configured using the router CLI. The soft-GRE tunnel is brought up by configuration on the router and will stay up as long as the configuration is present. The static subscriber is also brought up based on the configuration on the router but requires the underlying soft-GRE tunnel to be present before it comes up.
The static soft-GRE tunnel configuration must be defined under the set services
soft-gre gre-group hierarchy with a tunnel name and a
remote address, along with the source address, destination networks and service
interface. The remote address is the GRE tunnel endpoint associated with the subscriber,
typically the Multi-Dwelling Unit (MDU), and must be known and should not change. It
should also be one of the networks defined as the destination-networks
for the soft-GRE group. Note that the destination-networks configured
in the soft-GRE groups must be non-overlapping within the same or different soft-GRE
groups. You can define multiple tunnels, each with a unique tunnel name and a unique
remote address. The BNG software automatically initiates ARP resolution to the tunnel
remote address upon configuration commit.
An example for soft-GRE tunnel configuration is provided below. The configuration snippet
defines two tunnels, each with a unique tunnel name and its remote
address—mdu-21 with remote address 10.10.0.21 and
mdu-31 with remote address 10.10.0.31. Both remote
addresses belong to the configured destination-networks subnet
10.10.0.0/16.
user@host# show services soft-gre
gre-1 {
source-address 172.16.0.1;
destination-networks {
10.10.0.0/16;
}
tunnel {
mdu-21 {
remote-address 10.10.0.21;
}
mdu-31 {
remote-address 10.10.0.31;
}
}
service-interface ps1;
tunnel-idle-timeout 240;
dynamic-profile tunnel-profile;
}
The service interface ps1 can be anchored to a logical tunnel (LT) interface
for forwarding plane processing. To provide redundancy for the underlying forwarding
path, you can also anchor the Pseudowire Subscriber (PS) interface to a redundant
logical tunnel (RLT) interface by grouping multiple LT interfaces. PS over RLT supports
both active-active and active-backup modes.
The tunnel logical interfaces are created using the dynamic profile
tunnel-profile defined for the soft-GRE group. The same dynamic
profile can be used for both static and dynamic GRE tunnels.
The correlation between the static soft-GRE tunnel configuration and static subscriber is
provided by the keyword underlying-interface-tag, which must be the
tunnel name defined for the soft-GRE group tunnel configuration. The
static-subscriber configuration must define the
demux1 interface with an underlying-interface-tag.
The demux-source address should be set to an IP prefix that must match
the IP address configured on the CPE . The demux1 interface is mapped
to the tunnel for the matching tunnel name, remote address and demux source IP prefix.
Note that the demux1 interface is reserved for static subscribers over
statically configured soft-GRE tunnels. You must therefore configure a static subscriber
group for demux1 interfaces separate from the traditional static
subscriber group for demux0 interfaces.
user@host# show system services static-subscribers
group gre-group {
dynamic-profile {
demux1-profile;
}
interface demux1 {
unit 21 {
demux-options {
underlying-interface-tag mdu-21;
}
family inet {
demux-source {
192.168.1.21/32;
}
}
}
}
}demux1.unit interface must map to one
tunnel and is limited to a single source address.underlying-interface-tag value set to the
tunnel name. Configuration commit will not succeed if this order is not
maintained.The demux1 interfaces are created using the dynamic profile
demux1-profile configured in the
static-subscribers configuration. When configuring the dynamic
profile, you must define demux1 under the interfaces
hierarchy.
user@host# show dynamic-profiles demux1-profile
routing-instances {
"$junos-routing-instance" {
interface "$junos-interface-name";
}
}
interfaces {
demux1 {
unit "$junos-interface-unit" {
demux-options {
underlying-interface "$junos-interface-ifd-name";
}
family inet {
demux-source {
$junos-subscriber-ip-address;
}
unnumbered-address lo0.0;
}
}
}
}When a static subscriber is logged out using the CLI commands request services
static-subscribers logout interface or request services
static-subscribers logout group, the demux1 logical
interface is deleted but the static soft-GRE tunnel persists. There is uplink traffic
but no downlink traffic when the subscriber is logged out. The demux1
logical interface is recreated when the subscriber logs back in using request
services static-subscribers login interface or request services
static-subscribers login group CLI commands.
clear services
soft-gre tunnel will not be automatically recreated. This command therefore
should not be used to clear statically configured soft-GRE tunnels.Configuring Static Subscribers over Statically Configured Soft-GRE Tunnels
In this example we will configure provisioning static IPv4 subscribers over statically configured soft-GRE tunnels. Please take note of the following IP address:
- Wifi Access Gateway (WAG) IP address:
172.16.0.1 -
Destination networks:
10.10.0.0/16 -
Subscriber IP addresses:
192.168.0.21/32and192.168.0.31/32
See Also
Verify Static Subscriber Over Statically Configured Soft-GRE Tunnel
Purpose
Verify the static subscriber provisioning over statically configured soft-GRE tunnels.
Action
-
Verify the subscriber summary using the
show subscriber summarycommand. The The demux1.unitsubscribers will show as client-typestatic, and the statically-configured GRE tunnels will show as client typegre.user@router> show subscribers summary Subscribers by State Active: 4 Total: 4 Subscribers by Client Type Static: 2 GRE: 2 Total: 4 {master} user@router> -
Verify the subscribers using the
show subscriberscommand:user@router> show subscribers Interface IP Address/VLAN ID User Name LS:RI demux1.21 192.168.0.21 demux1.21 default:default demux1.31 192.168.0.31 demux1.31 default:default ps1.3221225476 10.10.0.21 :default ps1.3221225477 10.10.0.31 :default
Verify the tunnel summary using the
show services soft-gre tunnel summarycommand:user@router> show services soft-gre tunnel summary GRE tunnels by Type: Static: 2 Dynamic: 0 Total: 2Verify the tunnel details using the
show services soft-gre tunnel tunnel-name tunnel name command:user@router> show services soft-gre tunnel tunnel-name mdu-21 Interface Remote IP Local IP Subscribers ps1.3221225476 10.10.0.21 172.16.0.1 1
user@router> show services soft-gre tunnel tunnel-name mdu-21 brief Interface Remote IP Local IP Subscribers ps1.3221225476 10.10.0.21 172.16.0.1 1
user@router> show services soft-gre tunnel tunnel-name mdu-21 detail Interface Name: ps1.3221225476, Group Name: gre-1, Tunnel-name: mdu-21 Local IP: 172.16.0.1 Remote IP: 10.10.0.21 Subscribers: 1 Routing Instance: default Create time: 2024-10-23 12:48:22 PDTuser@router> show services soft-gre tunnel tunnel-name mdu-21 extensive Interface Name: ps1.3221225476, Group Name: gre-1, Tunnel-name: mdu-21 Local IP: 172.16.0.1 Remote IP: 10.10.0.21 Subscribers: 1 Routing Instance: default Create time: 2024-10-23 12:48:22 PDT Statistics since: Wed Oct 23 12:48:22 2024 Statistic Packets Bytes Data Rx 5138 51440 Data Tx 5137 41178user@router> show services soft-gre tunnel tunnel-name mdu-21 statistics Interface Name: ps1.3221225476, Group Name: gre-1, Tunnel-name: mdu-21 Local IP: 172.16.0.1 Remote IP: 10.10.0.21 Subscribers: 1 Routing Instance: default Create time: 2024-10-23 12:48:22 PDT Statistics since: Wed Oct 23 12:48:22 2024 Statistic Packets Bytes Data Rx 5138 51440 Data Tx 5137 41178
See Also
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.