5. Internet Enhanced Service

This chapter provides information about Internet Enhanced Services the process overview, and implementation notes.

5.1. IES Service Overview

Internet Enhanced Service (IES) is a routed connectivity service where the subscriber communicates with an IP router interface to send and receive Internet traffic. An IES has one or more logical IP routing interfaces each with a SAP which acts as the access point to the subscriber network.

IES allows IP interfaces to participate in the same routing instance used for service network core routing connectivity. IES services require that the IP addressing scheme used by the subscriber be unique between other provider addressing schemes and potentially the entire Internet. While IES is part of the routing domain, the usable IP address space may be limited. This allows a portion of the service provider address space to be reserved for service IP provisioning, and be administered by a separate, but subordinate address authority.

IP interfaces defined within the context of an IES service must have a SAP associated as the uplink access point to the subscriber network. Multiple IES services are created to segregate subscriber owned IP interfaces.

Figure 52 shows internet enhanced service.

Figure 52: Internet Enhanced Service

The IES service provides in-band management connectivity. Other features include:

Multiple IES services are created to separate IP interfaces.
More than one IES service can be created for a single customer ID.
More than one IP interface can be created within a single IES service ID. All IP interfaces created within an IES service ID belong to the same customer.

5.2. IES Features

This section describes various general service features and any special capabilities or considerations as they relate to IES services.

5.2.1. IP Interfaces

IES customer IP interfaces can be configured with most of the options found on the core IP interfaces. The advanced configuration options supported are:

VRRP - for IES services with more than one IP interface
Secondary IP addresses (available only on 7210 SAS-M (network mode), 7210 SAS-T (network mode), 7210 SAS-Mxp, and 7210 SAS-Sx RPS platforms)
ICMP Options

Configuration options found on core IP interfaces not supported on IES IP interfaces are:

NTP broadcast receipt.

5.2.2. IPv6 support for IES IP interfaces (in network mode)

IES IPv6 IP interfaces provide IPv6 connectivity in the routing base instance. It can be used to connect IPv6 networks over an IPv4 cloud using 6PE mechanisms. For more information about the 6PE, see the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Router Configuration Guide.

IPv4 and IPv6 route table lookup entries are shared. Before adding routes for IPv6 destinations, route entries in the routed lookup table needs to be allocated for IPv6 addresses. This can be done using the CLI command config> system>resource-profile>router max-ipv6-routes and config> system>global-res-profile>max-ipv6-routes for 7210 SAS-R6 and 7210 SAS-R12. This command allocates route entries for /64 IPv6 prefix route lookups. The system does not allocate any IPv6 route entries by default and user needs to allocate some resources before using IPv6. For the command to take effect the node must be rebooted after making the change. For more information, see the following example and the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System Configuration Guide.

A separate route table (or a block in the route table) is used for IPv6 /128-bit prefix route lookup. A limited amount of IPv6 /128 prefixes route lookup entries is supported. The software enables lookups in this table by default (that is, no user configuration is required to enable IPv6 /128-bit route lookup).

In addition, the number IP subnets can be configured by the user using the command configure> system>resource-profile>router>max-ip-subnets and config>system>global-res-profile> max-ip-subnet for 7210 SAS-R6 and 7210 SAS-R12. Suitable default are assigned to this parameter. Users can increase the number of subnets if they plan to more IPv6 addresses per IPv6 interface.

Following features and restrictions is applicable for IPv6 IES IP interfaces:

IPv6 interfaces supports static routing, OSPv3, and IS-IS.
A limited amount of IPv6 /128 prefixes route lookup entries is supported on 7210 SAS platforms.

5.3. SAPs

This section provides information about SAPs on IES services.

5.3.1. Encapsulations

The following SAP encapsulation is supported on IES services.

Ethernet null
Ethernet dot1q
Ethernet QinQ

5.3.1.1. CPE Connectivity Check

Static routes are used within many IES services. Unlike dynamic routing protocols, there is no way to change the state of routes based on availability information for the associated CPE. CPE connectivity check adds flexibility so that unavailable destinations will be removed from the service provider routing tables dynamically and minimize wasted bandwidth.

The availability of the far-end static route is monitored through periodic polling. The polling period is configured. If the poll fails a specified number of sequential polls, the static route is marked as inactive.

An ICMP ping mechanism is used to test the connectivity. If the connectivity check fails and the static route is de-activated, the router will continue to send polls and reactivate any routes that are restored.

5.3.2. QoS Policies

When applied to 7210 SAS IES services, service ingress QoS policies only create the unicast meters defined in the policy. The multipoint meters are not created on the service. With IES services, service egress QoS policies function as with other services where the class-based queues are created as defined in the policy.

On 7210 SAS ingress, only meters are supported on all the platforms.

Note:

QoS policies only create the unicast meters defined in the policy if PIM is not configured on the associated IP interface; if PIM is configured, the multipoint meters are applied as well.

Both MAC and IPv4 criteria can be used in the QoS policies for traffic classification in an IES.

5.3.2.1. CPU QoS for IES Access Interfaces in Network Mode

Traffic bound to CPU received on IES access interfaces are policed/rate-limited and queued into CPU queues. The software allocates a policer per IP application or a set of IP applications, for rate-limiting CPU bound IP traffic from all IES access SAPs. The policers CIR/PIR values are set to appropriate values based on feature scaling and these values are not user configurable. The software allocates a set of queues for CPU bound IP traffic from all IES access SAPs. The queues are either shared by a set of IP applications or in some cases allocated to an IP application. The queues are shaped to appropriate rate based on feature scaling. The shaper rate is not user-configurable.

Note:

The instance of queues and policers used for traffic received on network port IP interfaces is different for traffic received from access port IP interfaces. Additionally the network CPU queues receive higher priority than the access CPU queues. This is done to provide better security and mitigate the risk of access traffic affecting the network side.
On the 7210 SAS-R6, the user can configure the IP DSCP value for self-generated traffic.

5.3.3. Filter Policies

In network mode, only IP filter policies can be applied to IES services.

5.3.4. VRRP Support for IES IP Interfaces in Network Mode

Note:

VRRP for IPv4 is supported for IES IPv4 interfaces in network mode only.

The Virtual Router Redundancy Protocol (VRRP) for IPv4 is defined in the IETF RFC 3768, Virtual Router Redundancy Protocol. VRRP describes a method of implementing a redundant IP interface shared between two or more routers on a common LAN segment, allowing a group of routers to function as one virtual router. When this IP interface is specified as a default gateway on hosts directly attached to this LAN, the routers sharing the IP interface prevent a single point of failure by limiting access to this gateway address. For more information about use of VRRP, refer to the 7210 SAS-M, T, R6, R12, Mxp, Sx, S Router Configuration Guide.