This article explains how to resolve the commit error "xSTP configuration disallowed on interface <interface-name> as it is part of an aggregate bundle".

In this scenario, the switch needs to commit configuration, but it presents the error "xSTP configuration disallowed on interface ge-1/0/18 as it is part of an aggregate bundle" on every commit attempt, and the commit fails with error "error: configuration check-out failed".

This error appears because the physical interfaces ge-1/0/18, ge-1/0/20 and ge-1/0/22 are part of an interface range <MY-RANGE> which is configured under [edit protocols rstp] and the interface ae1 which is the bundle that consists of ge-1/0/18, ge-1/0/20 and ge-1/0/22 is configured under [edit protocols rstp] too. This is redundant and causes the commit failed error. It will appear even if the interfaces ge-1/0/18, ge-1/0/20 and ge-1/0/22 are not explicitly configured under [edit protocols rstp].

Note that the commit error may just illustrate one interface at once on every commit attempt but will show the next one affected on the next commit until you make the necessary corrections for all affected interfaces.

To resolve this, you will need to optimize your configuration. If the interface range <MY-RANGE> under [edit interfaces interfaces-range] is configured from ge-1/0/0 to ge-1/0/30, you will have making multiple member ranges ignoring only the ones that form ae1. After a commit check, we confirmed that it is successful.

Using member instead of member range with port numbers in ranges omitting the interfaces that should be excluded and adding the interfaces that are isolated and cannot fit in a range. See the below example:

set interfaces interface-range MY-RANGE member ge-1/0/[0-17]
set interfaces interface-range MY-RANGE member ge-1/0/[23-30]
set interfaces interface-range MY-RANGE member ge-1/0/19
set interfaces interface-range MY-RANGE member ge-1/0/21

{master:0}[edit]
user@switch# show interfaces
interface-range MY-RANGE {
  member "ge-1/0/[0-17]";
  member "ge-1/0/[23-30]";
  member ge-1/0/19;
  member ge-1/0/21;
}

Using multiple member-range and member set commands omitting the interfaces that should be excluded. See the below example:

set interfaces interface-range MY-RANGE member-range ge-1/0/0 to ge-1/0/17
set interfaces interface-range MY-RANGE member ge-1/0/19
set interfaces interface-range MY-RANGE member ge-1/0/21
set interfaces interface-range MY-RANGE member-range ge-1/0/23 to ge-1/0/30

{master:0}[edit]
user@switch# show interfaces
interface-range MY-RANGE {
  member ge-1/0/19;
  member ge-1/0/21;
  member-range ge-1/0/0 to ge-1/0/17;
  member-range ge-1/0/23 to ge-1/0/30;
}