Service Groups

This module explains the Service Group feature and tell you how to use it.The Service Group feature allows network administrators to create service groups, add members (such as service instances) to those service groups, and apply service policies (also known an policy maps) to those newly created groups. The service policies (policy maps) contain the aggregate features (such as traffic policing and queueing) to be applied to the groups in compliance with the Service-Level Agreement (SLA) negotiated between the service provider and the subscribers.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Service Groups" section.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Restrictions for Service Groups

•Information About Service Groups

•How to Configure Service Groups

•Configuration Examples for Service Groups

•Additional References

•Feature Information for Service Groups

Restrictions for Service Groups

For Cisco IOS Release12.2(33)SRE, the following restrictions apply:

•This feature is supported only on the Cisco IOS 7600 series router.

•Layer 3 subinterfaces are not supported.

Note For additional restrictions for the Cisco 7600 series routers and the line cards used on the router, see both the Cisco 7600-ES20 Ethernet Line Card Configuration Guide and the Cisco 7600 Series Ethernet Services + Line Card Configuration Guide.

•From Cisco IOS Release 15.1(1)S onwards, subinterfaces and access subinterfaces are supported on Ethernet service + line cards. A service group can have service instance members, subinterface members, or a mix of the two under the same main interface on these line cards.

Information About Service Groups

To configure the Service Groups feature, you should understand the following concepts.

•Service Instance Definition

•Benefits of Service Groups

•Service Groups, QoS Policy Maps, and Automatic load balancing

Service Instance Definition

A service instance is a configuration object (container) that holds all management and control plane attributes and parameters that apply to that service instance on a per-port basis. Different service instances that correspond to the same Ethernet Virtual Connection (EVC) must share the same name. Service instances are associated with a global EVC object through their shared name.

Benefits of Service Groups

Th Service Groups feature allows you to create service groups and apply aggregate features to those service groups. For Cisco IOS Release 12.2(33)SRE on a Cisco 7600 series router, a Quality of Service (QoS) policy map is the only feature that can be applied to service groups.

Service Groups, QoS Policy Maps, and Automatic load balancing

For Cisco IOS Release 12.2(33)SRE on Cisco 7600 series router, only QoS service policies (policy maps) on service groups or group members are supported. A QoS policy map may be configured on service groups (or on individual service group members) on an interface or a port channel. On a port channel, the service group feature enables you to implement load balancing by distributing the multiple service instances among the different member links.

When a member link goes down, automatic load balancing is triggered on the port channel. Load balancing redistributes the EVCs to the remaining member links on the port channel, while maintaining the original QoS policy maps. For example, consider that two QoS policy maps, QoS1 and QoS2, implemented on two service groups, SG1 and SG2, respectively:

•Service group SG1 is connected to the network through link M1.

•Service group SG2 is connected to the network through link M2.

If the M2 link goes down, automatic load balancing is initiated and all the EVCs of service group SG2 are redistributed to the M1 link. Even though the service group SG2 is now moved under the link M1, service group SG2 maintains its original QoS policy map, QoS2; when service groups are redistributed, the QoS policy maps are not affected.

Note You can manually load balance service groups and service instances across member links of a port channel using a feature called "User-Network Interface (UNI) Link Aggregation Group (LAG) Advanced load balancing". For more information, see the "Configuring Layer 2 Features" chapter in the Cisco 7600 Series Ethernet Services + Line Card Configuration Guide.

How to Configure Service Groups

This section contains the following tasks:

•Creating a Service Group (required)

•Adding or Deleting Service Instance Members (deleting members is optional; adding members is required)

•Deleting a Service Group (optional)

•Verifying the Service Instance Group Configuration (optional)

•Adding or Deleting a Subinterface from a Service Group (optional)

•Verifying the Subinterface Configuration (optional)

Creating a Service Group

Prerequisites

In this procedure, you need to specify the name of a QoS policy to be attached to the service group. The QoS policy must already exist.

SUMMARY STEPS

1. enable

2. configure terminal

3. service-group service-group-identifier

4. description descriptive-text

5. service-policy {input | output} policy-map-name

6. end

DETAILED STEPS

Adding or Deleting Service Instance Members

Restrictions

The following restrictions apply to service group members:

•In Cisco IOS Release 12.2(33)SRE on the Cisco 7600 series router, a member can join only one service group at a time.

•On the Cisco 7600 series router, all members of a service group must reside on the same physical or port channel interface.

•A member of a service group cannot be individually assigned to a load balance link of a port channel. The entire service group must be assigned to the load balance link.

•A service group cannot have members that are assigned to multiple load balance links on a port channel.

•The Cisco 7600 series router does not allow service instances to join the same group from multiple interfaces. On the Cisco 7600 series router, group members must come from the same interface, as shown in the the sample configuration below:

interface GigabitEthernet 2/0/0

service instance 1 ethernet

group 32

Service-policy output policy3

service instance 2 ethernet

group 32

service instance 3 ethernet

group 37

interface GigabitEthernet 2/0/1

service instance 1 ethernet

group 32  |<--Disallowed because this group has members in g2/0/0 already |

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

or

interface port-channel port-channel-number

4. service instance service-instance-number ethernet

5. group service-group-identifier

6. no group service-group-identifier

7. exit

8. end

DETAILED STEPS

Deleting a Service Group

SUMMARY STEPS

1. enable

2. configure terminal

3. no service-group service-group-identifier

4. end

DETAILED STEPS

Verifying the Service Instance Group Configuration

SUMMARY STEPS

1. enable

2. show running-config service-group

3. show service-group {service-group-identifier | all}

4. show service-group interface type number

5. show service-group stats

6. show service-group state

7. show service-group traffic-stats

8. show policy-map interface type number service group {service-group-identifier}

9. show policy-map target service-group {service-group-identifier}

10. show ethernet service instance [detail]

11. clear service-group traffic-stats

12. debug service-group {all | error | feature | group | interface | ipc | member | qos | stats}

DETAILED STEPS

Adding or Deleting a Subinterface from a Service Group

Restrictions

If a subinterface is already a member of a group, you cannot add it to another group. To move a subinterface, first delete it from the current group, then add it to the new group.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number
or
interface range {type number [- interface-number] [,] . . .type number | macro word}

or

interface port-channel port-channel-number

4. group service-group-identifier
or
no group service-group-identifier

5. exit

6. end

DETAILED STEPS

Verifying the Subinterface Configuration

SUMMARY STEPS

1. enable

2. show running-config service-group

3. show service-group {service-group-identifier | all}

4. show service-group interface type number

5. show policy-map target service-group service-group-identifier

6. show service-group stats

7. show service-group state

8. show service-group traffic-stats

9. clear service-group traffic-stats

10. debug service-group {all | error | feature | group | interface | ipc | member | qos | stats}

DETAILED STEPS

Configuration Examples for Service Groups

This section provides the following configuration examples:

•Example: Creating a Service Group

•Example: Adding Service Instance Members to a Service Group

•Example: Adding Subinterfaces to a Service Group

•Example: Deleting Service Instance Members from a Service Group

•Example: Deleting Subinterfaces from a Service Group

•Example: Deleting a Service Group

•Example: Verifying the Service Group Configuration

Example: Creating a Service Group

In the following example, service group 20 has been created:

Router> enable

Router# configure terminal

Router(config)# service-group 20

Router(config-service-group)# description account number 105AB1

Router(config-service-group)# service-policy input policy1

Router(config-service-group)# end

Example: Adding Service Instance Members to a Service Group

In the following example, service instance 200 will be added to service group 20:

Router> enable

Router# configure terminal

Router(config)# interface GigabitEthernet 1/0

Router(config-if)# service instance 200 ethernet

Router(config-if-srv)# group 20

Router(config-if-srv)# end

Example: Adding Subinterfaces to a Service Group

In the following example, subinterface g3/7.12 will be added to service group 10:

Router> enable

Router# configure terminal

Router(config)# interface GigabitEthernet 3/7.12

Router(config-subif)# group 10

Router(config-subif)# end

Example: Deleting Service Instance Members from a Service Group

In the following example, service instance 300 will be deleted from service group 30 on a port channel:

Router> enable

Router# configure terminal

Router(config)# interface port-channel 50

Router(config-if)# service instance 300 ethernet

Router(config-if-srv)# no group 30

Router(config-if-srv)# end

Example: Deleting Subinterfaces from a Service Group

In the following example, subinterface g3/7.12 will be deleted from service group 10:

Router> enable

Router# configure terminal

router(config)# interface g3/7.12

router(config-subif)# no group 10

router(config-subif)# end

Example: Deleting a Service Group

In the following example, service group 20 will be deleted:

Router> enable

Router# configure terminal

Router(config)# no service-group 20

Router(config)# end

Example: Verifying the Service Group Configuration

This section contains sample output from the show policy-map target service-group command. The show policy-map target service-group command displays policy-map information for service groups.

Note This command is one of several that you can use to verify the service-group configuration. For additional commands that can be used, see the "Verifying the Service Instance Group Configuration" section.

In the following example, service group 1 is specified. Service group 1 contains two policy maps (service policies), policy1 and policy2. Traffic policing is enabled in the evc policy map. Traffic queueing is enabled in the isg policy map.

Router# show policy-map target service-group 1

 GigabitEthernet9/5: Service Group 1

  Service-policy input: policy1

    Class-map: class-default (match-any)

      0 packets, 0 bytes

      5 minute offered rate 0000 bps, drop rate 0000 bps

      Match: any 

      police:

          cir 200000 bps, bc 6250 bytes

        conformed 0 packets, 0 bytes; actions:

          transmit

        exceeded 0 packets, 0 bytes; actions:

          drop

        conformed 0000 bps, exceed 0000 bps

  Service-policy output: policy2

  Counters last updated 00:00:34 ago

    Class-map: class-default (match-any)

      0 packets, 0 bytes

      5 minute offered rate 0000 bps, drop rate 0000 bps

      Match: any 

      Queueing

      queue limit 131072 packets

      (queue depth/total drops/no-buffer drops) 0/0/0

      (pkts output/bytes output) 0/0

      bandwidth remaining ratio 2 

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Feature Information for Service Groups

Table 1 lists the release history for this feature.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2011 Cisco Systems, Inc. All rights reserved.