6. Internet Enhanced Service on 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T

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

6.1. IES Service Overview

Note:

  1. IES is used for in-band management of the node on the 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T.
  2. IES service (standalone, without being associated with a routed VPLS) is not supported on the 7210 SAS-K 2F1C2T.

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’s 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 78 shows the internet enhanced service.

Figure 78:  Internet Enhanced Service 

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

  1. Multiple IES services are created to separate IP interfaces.
  2. More than one IES service can be created for a single customer ID.
  3. 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.

On 7210 SAS-D and 7210 SAS-Dxp, the IES services provide IP connectivity to the node for in-band management of the node. Most of the management tasks supported with the out-of-band management port are supported with in-band management.

6.2. IES Features

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

6.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:

  1. ICMP Options

6.2.2. IPv6 Support for IES IP Interfaces Associated with Access-Uplink SAPs (on 7210 SAS-D and 7210 SAS-Dxp)

In access-uplink mode, IES IP interfaces associated with access-uplink SAPs support IPv6 addressing. IPv6 can be used for in-band management of the node using the IES IP interface.

Note:

IPv6 IES IP interfaces on access-uplink SAPs are only supported on 7210 SAS-D and 7210 SAS-Dxp.

On 7210 SAS-D and 7210 SAS-Dxp, 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 config> system> resource-profile> router> max-ipv6-routes command. 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, refer to the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide. A separate route table is used for IPv6 /128-bit prefix route lookup. A limited number of IPv6 /128 prefixes route lookup entries is supported on 7210 SAS-D. The software enables lookups in this table by default (that is, no user configuration is required to enable IPv6 /128-bit route lookup).

Note:

On the 7210 SAS-D and 7210 SAS-Dxp, IPv6 interfaces are created without allocating IPv6 route entries.

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

  1. IPv6 interfaces supports only static routing.
  2. Only port-based ingress QoS policies are supported.
  3. IPv6 filter policies can be used on SAP ingress and egress.
  4. Routing protocols, such as OSPFv3, and others are not supported.
  5. A limited number of IPv6 /128 prefixes route lookup entries is supported.

6.3. SAPs

6.3.1. Encapsulations

For 7210 SAS-D and 7210 SAS-Dxp, the following Access SAP encapsulation is supported on IES services in both network mode and access-uplink mode:

  1. Ethernet null
  2. Ethernet dot1q
  3. Ethernet QinQ

For 7210 SAS-D and 7210 SAS-Dxp, Ethernet QinQ (access-uplink QinQ SAP) encapsulation is supported.

6.3.2. CPE Connectivity Check

Note:

This capability is only supported on the 7210 SAS-D and 7210 SAS-Dxp.

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’s 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 deactivated, the router will continue to send polls and re-activate any restored routes.

6.3.3. QoS Policies

When applied to 7210 SAS IES services, service ingress QoS policies only create the unicast meters defined in the policy. The multi-point 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:

  1. 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.
  2. On the 7210 SAS-K 2F1C2T, both unicast and multicast queues are configured.

In access-uplink mode, IES IP interface associated with an access SAP supports use of service ingress QoS policies. IES IP interface associated with an access-uplink SAP does not support use of service ingress QoS policies. IES IP interfaces associated with an access-uplink SAP share the port based ingress and egress QoS policies.

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

6.3.4. CPU QoS for IES interfaces in access-uplink mode

In access-uplink mode, IES IP interface bound to routed VPLS services, IES IP interface on access SAPs and IES IP interface on Access-Uplink SAPs are designed for use with inband management of the node. Consequently, they share a common set of queues for CPU bound management traffic. All CPU bound traffic is policed to predefined rates before being queued into CPU queues for application processing. The system uses meters per application or a set of applications. It does not allocate meters per IP interface. The possibility of CPU overloading has been reduced by use of these mechanisms. Users must use appropriate security policies either on the node or in the network to ensure that this does not happen.

6.3.5. Filter Policies

In access-uplink mode, only IP filter policies can be applied to IES service when either access SAP or access-uplink SAP is associated with the service.