Adding Member Interfaces to an Interface Set

You can add interfaces as members of an interface set using the CLI or RADIUS.

Tasks to add members to an interface set include:

Adding Interfaces to an Interface Set with the CLI

To add subscriber interfaces to the interface set:

  1. Specify the VLAN or ATM-VC subinterface you want to add to the interface set.

    For VLAN subinterfaces:

    host1(config)#interface gigabitEthernet 4/0/0.1

    For ATM subinterfaces:

    host1(config)#interface atm 2/0/0.1host1(config-sub-if)#atm pvc 21 0 21 aal5snap
  2. Configure the interface set as the parent of this interface.
    host1(config-sub-if)#qos-interface-parent residential-customers

    The interface type must match the member-interface type specified in the interface set.

Adding Interfaces to an Interface Set with RADIUS

You can add interfaces to an interface set using the QoS-Interfaceset-Name RADIUS VSA attribute [26-130].

This VSA is useful when configuring local loop topologies of interface sets in the network. When the subscriber interface is created, the VSA supplies the interface name and the subscriber interface. The system matches the subscriber interface with the member-interface type that is specified in the interface set. Note that the VSA cannot specify an interface superset.

When multiple subscribers exist in one interface set, such as PPPoE subscribers over the same VLAN, they are joined with the first subscriber’s VSA. The system generates an error message if one of the subscribers attempts to join another interface set using another VSA.

Leaving an interface set is not supported from RADIUS. The interface leaves an interface set when it is deleted or manually removed from the interface set through the CLI.

Changing and Deleting Interface Members in an Interface Set

If you want to move interface members in an interface set, we recommend that you delete the interface member from the interface set before associating it with another interface.

To move an interface member from an interface set to another interface set:

  1. Specify the subinterface associated with the member interface.
    host1(config)#interface gigabitEthernet 4/0/0.1
  2. Delete the member interface from the subinterface using the no version of the command.
    host1(sub-if)#no qos-interface-parent vlan-business
  3. Configure the new interface set for the member interface.
    host1(sub-if)#qos-interface-parent vlan-residential

Changing Interface Members with Upper-Layer Protocols in an Interface Set

When upper-layer protocols such as IP are configured on an interface set, moving an interface member from one interface set to another interface set can cause problems with the interface column in munged QoS profiles.

For example, moving an interface set to an upper layer binding causes the interface set to appear below the subinterface level. If a QoS profile were attached to the VLAN subinterface in this example, the munged QoS profile for all IP interfaces stacked above the subinterface would change.

host1(config)#interface gigabitEthernet 4/0/0.1host1(config-sub-if)#svlan id 3 1host1(config-sub-if)#ip address vlan-business

Instead of moving the member interface, we recommend that you add an interface member to an interface set at the subinterface rather than at the upper-layer binding. For example:

host1(config)#interface gigabitEthernet 4/0/0.1host1(config-sub-if)#svlan id 3 1host1(config-sub-if)#qos-interface-parent vlan-businesshost1(config-sub-if)#ip address

Related Documentation