Provisioning model

The main objective of this proposed provisioning model is to separate the definition of the QoS attributes from the definition of the membership of an encap-group. The user can apply the same SAP egress QoS policy to a large number of ISID members without having to configure the QoS attributes for each member.

The following are conditions of the provisioning model:

• A SAP egress policy ID must be assigned to an encap-group before any member can be added regardless of the setting of the qos-per-member option.

• When qos-per-member is specified in the encap-group creation, the user must add or remove ISID members one at a time. The command is failed if a range is entered.

• When qos-per-member is specified in the encap-group creation, the sap-egress QoS policy ID and the scheduler policy name cannot be changed unless the group membership is empty. However, the agg-rate-limit parameter value can be changed or the command removed (no agg-rate-limit).

• When qos-per-member is not specified in the encap-group creation, the user may add or remove ISID members as a singleton or as a range of contiguous values.

• When qos-per-member is not specified in the encap-group creation, the sap-egress QoS policy ID and the scheduler policy name or agg-rate-limit parameter value may be changed at any time. Note however that the user cannot still remove the SAP egress QoS policy (no qos) while there are members defined in the encap-group.

• The QoS policy or the scheduler policy itself may be edited and modified while members are associated with the policy.

• There is a maximum number of ISID members allowed in the lifetime of an encap-group.

Operationally, the provisioning consists of the following steps:

1. Create an encap-group.

2. Define and assign a SAP egress QoS policy to the encap-group. This step is mandatory; if it is not performed, the user is allowed to add members to the encap-group.

3. Manage memberships for the encap-group using the member command (or SNMP equivalent).

   Note: The member command supports both range and singleton ISIDs.

   The following restrictions apply to the member command:

   • An ISID cannot be added if it already exists on the SAP in another encap-group. If the member fails for this reason, the following applies:

     • The member command is all-or-nothing. No ISID in a range is added if one fails.

     • The first ISID that fails is the only one identified in the error message.

     • An ISID that already exists on the SAP in another encap-group must be removed from its encap-group using the no member command before it can be added to a new one.

   • Specifying an ISID in a group that already exists within the group is a no-op (no failure)

   • If insufficient queues or scheduler policies or FC-to-Queue lookup table space exists to support a new member or a modified membership range, the command is fails.

4. Optionally, define and assign a scheduling policy or agg-rate-limit for the encap-group.

Logically, the encap-group membership operation can be viewed as three distinct functions:

• Creation or deletion of new queue sets and optionally scheduler/agg-rate-limit at QoS policy association time.

• Mapping or un-mapping the member ISID to either the group queue set and scheduler (group QoS) or the ISID specific queue set and scheduler (qos-per-member).

• Modifying the groups objective membership based on newly created or expanded ranges or singletons based on the membership operation.