Switching

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

OK, that clears a few things up.  Let me return to the first post where I show the config lines I wish to remove. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

I should then have a port profile for those two interfaces, like I showed with ports 26 and 27.  Yet, here is my port profile section screenshot:

and the additional CLI section:

Finally, my port list on the 4600:

I still have a LAG10 in the template for the 4600s in general, so I can see where the line below comes from.

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

I just don't see how  port 22 and 23 are still in ae0 or how "set interfaces ae0 aggregated-ether-options lacp active" is still in the CLI on the switch without a port config that creates the ae0 with a checkbox saying to have LACP active. 

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

Interesting. 

• Do you have a port configuration at the switch level, if not at the ORG template?
• Are there any additional CLIs at the switch level?
• Is there a higher rule than the one for which the port configuration screenshot was shared, associating ports xe-0/0/22-23 with ae0? If a rule above this one in the template matches the switch, its settings will take precedence.
• On a side note, if you want to create a L3 lag interface, please configure the port-profile as shown below at the switch level. L3 interface option is not available at the ORG template level. This will not require configuring IP addresses and deleting the group assigned to the ae interface from additional CLI.

Regards

OK, that clears a few things up.  Let me return to the first post where I show the config lines I wish to remove. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

I should then have a port profile for those two interfaces, like I showed with ports 26 and 27.  Yet, here is my port profile section screenshot:

and the additional CLI section:

Finally, my port list on the 4600:

I still have a LAG10 in the template for the 4600s in general, so I can see where the line below comes from.

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

I just don't see how  port 22 and 23 are still in ae0 or how "set interfaces ae0 aggregated-ether-options lacp active" is still in the CLI on the switch without a port config that creates the ae0 with a checkbox saying to have LACP active. 

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

At the org level in the template, there is still a lag10 profile under the "Shared Elements" section, but nothing with ports 22 and 23. At the switch screen, the only additional port profile is to set a single xe-0/0/8 port to "Uplink" which is a trunked configuration.  All other port profiles are inherited from the Org template.  I already shared the specific named switch under the org template port profile . 

This sort of thing is why I'm reaching out.   I can't match everything on the switch's CLI with the configurations in the Dashboard.  Is there a chance the template has not been " pushed" to the switch and the switch and templates are not in synch? 

Interesting. 

• Do you have a port configuration at the switch level, if not at the ORG template?
• Are there any additional CLIs at the switch level?
• Is there a higher rule than the one for which the port configuration screenshot was shared, associating ports xe-0/0/22-23 with ae0? If a rule above this one in the template matches the switch, its settings will take precedence.
• On a side note, if you want to create a L3 lag interface, please configure the port-profile as shown below at the switch level. L3 interface option is not available at the ORG template level. This will not require configuring IP addresses and deleting the group assigned to the ae interface from additional CLI.

Regards

OK, that clears a few things up.  Let me return to the first post where I show the config lines I wish to remove. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

I should then have a port profile for those two interfaces, like I showed with ports 26 and 27.  Yet, here is my port profile section screenshot:

and the additional CLI section:

Finally, my port list on the 4600:

I still have a LAG10 in the template for the 4600s in general, so I can see where the line below comes from.

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

I just don't see how  port 22 and 23 are still in ae0 or how "set interfaces ae0 aggregated-ether-options lacp active" is still in the CLI on the switch without a port config that creates the ae0 with a checkbox saying to have LACP active. 

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

Craig,

I thought that was the case in the past, but I found out the hard way that large sections of code can be removed by Mist.  We have a 4600 doing a specific job and it has LAG and VPN settings and next hops for our internet access to two ISPs.  It was not managed by Mist because it never needed to be changed.  When it was changed to be managed all of that code was removed and the Template  settings, which where pretty generic replaced what we had.   

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

Ive compared the template config to the switch CLI config, and they appear to match as far as ports 0/0/22 and 0/0/23 and ae0 and LAG10 are concerned. 

I decided to to remove commands in the template that were no longer needed. When I removed the these to commands..

delete interfaces xe-0/0/22 unit 0

delete interfaces xe-0/0/23 unit 0

I no longer see the commands on the switch, but I see this error in the switch insights:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

The setting for AR devices is:

set groups top chassis aggregated-devices ethernet device-count 2

In my video watching on this topic, it looked like you could set the count higher than the current AE count for future use. So, why is it complaining that I have less AEs than the count specifies? 

I decided to change the device-count to 1 in the template to make the error go away, and I got this config failure error:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

So. with the count set at 2 I get an error that I have too many AEs ( Only 1 )  and with the count at 1 the error is that I don't have enough AEs ( Now with 2 )  

How am I supposed to fix this?! 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 10:17
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Craig,

I thought that was the case in the past, but I found out the hard way that large sections of code can be removed by Mist.  We have a 4600 doing a specific job and it has LAG and VPN settings and next hops for our internet access to two ISPs.  It was not managed by Mist because it never needed to be changed.  When it was changed to be managed all of that code was removed and the Template  settings, which where pretty generic replaced what we had.   

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 09:39
From: CRAIG DALRYMPLE
Subject: Steps to remove a lag setting on EX switch?

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

------------------------------
CRAIG DALRYMPLE

Original Message:
Sent: 04-02-2025 09:26
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

• The commit-confirm error occurs due to two AE interfaces in the configuration, but the device-count in "aggregated-devices" in the "set chassis" command is set to 1. It complains that you have more AEs than the configured device count, not the other way around.
• Verify if the device has only one AE interface, as stated, or two. As IPs were assigned to both ae0 and ae1 interfaces in the earlier additional CLI section screenshot to configure IPs on those interfaces.
• Mist will adjust the device count in the "set groups top chassis aggregated-devices" command based on the configured AE interfaces in the template
• On the device, is there a "set chassis aggregated-devices ethernet device-count 1" outside the "groups top" configuration? If yes, that will take precedence.
• On the device CLI itself (not from the template) can you please check the following: -
• a) show interfaces terse | match ae <<<<<<<---------- this will show how many ae interfaces are actually on the device.
• b) show configuration | match device-count | display set <<<<<<------ this will show if there is any other CLI command on the switch apart from the groups top, that Mist pushes)

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-07-2025 11:22
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Ive compared the template config to the switch CLI config, and they appear to match as far as ports 0/0/22 and 0/0/23 and ae0 and LAG10 are concerned. 

I decided to to remove commands in the template that were no longer needed. When I removed the these to commands..

delete interfaces xe-0/0/22 unit 0

delete interfaces xe-0/0/23 unit 0

I no longer see the commands on the switch, but I see this error in the switch insights:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

The setting for AR devices is:

set groups top chassis aggregated-devices ethernet device-count 2

In my video watching on this topic, it looked like you could set the count higher than the current AE count for future use. So, why is it complaining that I have less AEs than the count specifies? 

I decided to change the device-count to 1 in the template to make the error go away, and I got this config failure error:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

So. with the count set at 2 I get an error that I have too many AEs ( Only 1 )  and with the count at 1 the error is that I don't have enough AEs ( Now with 2 )  

How am I supposed to fix this?! 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 10:17
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Craig,

I thought that was the case in the past, but I found out the hard way that large sections of code can be removed by Mist.  We have a 4600 doing a specific job and it has LAG and VPN settings and next hops for our internet access to two ISPs.  It was not managed by Mist because it never needed to be changed.  When it was changed to be managed all of that code was removed and the Template  settings, which where pretty generic replaced what we had.   

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 09:39
From: CRAIG DALRYMPLE
Subject: Steps to remove a lag setting on EX switch?

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

------------------------------
CRAIG DALRYMPLE

Original Message:
Sent: 04-02-2025 09:26
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

Sheetqnshu,

The config on this swich is as follows:

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set interfaces ae1 unit 0 family inet address 10.254.253.86/29

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

set interfaces ae1 apply-groups lag40g

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae1 aggregated-ether-options lacp active

set groups top chassis aggregated-devices ethernet device-count 2

As you can see I have to AE and the device count is a set to 2. 

When I tried to remove the ports from ae0 I got an error that implied my device count was 1.

"error commit-confirm: number of AE devices configured 2 is more than device-count 1."

• The commit-confirm error occurs due to two AE interfaces in the configuration, but the device-count in "aggregated-devices" in the "set chassis" command is set to 1. It complains that you have more AEs than the configured device count, not the other way around.
• Verify if the device has only one AE interface, as stated, or two. As IPs were assigned to both ae0 and ae1 interfaces in the earlier additional CLI section screenshot to configure IPs on those interfaces.
• Mist will adjust the device count in the "set groups top chassis aggregated-devices" command based on the configured AE interfaces in the template
• On the device, is there a "set chassis aggregated-devices ethernet device-count 1" outside the "groups top" configuration? If yes, that will take precedence.
• On the device CLI itself (not from the template) can you please check the following: -
• a) show interfaces terse | match ae <<<<<<<---------- this will show how many ae interfaces are actually on the device.
• b) show configuration | match device-count | display set <<<<<<------ this will show if there is any other CLI command on the switch apart from the groups top, that Mist pushes)

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-07-2025 11:22
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Ive compared the template config to the switch CLI config, and they appear to match as far as ports 0/0/22 and 0/0/23 and ae0 and LAG10 are concerned. 

I decided to to remove commands in the template that were no longer needed. When I removed the these to commands..

delete interfaces xe-0/0/22 unit 0

delete interfaces xe-0/0/23 unit 0

I no longer see the commands on the switch, but I see this error in the switch insights:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

The setting for AR devices is:

set groups top chassis aggregated-devices ethernet device-count 2

In my video watching on this topic, it looked like you could set the count higher than the current AE count for future use. So, why is it complaining that I have less AEs than the count specifies? 

I decided to change the device-count to 1 in the template to make the error go away, and I got this config failure error:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

So. with the count set at 2 I get an error that I have too many AEs ( Only 1 )  and with the count at 1 the error is that I don't have enough AEs ( Now with 2 )  

How am I supposed to fix this?! 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 10:17
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Craig,

I thought that was the case in the past, but I found out the hard way that large sections of code can be removed by Mist.  We have a 4600 doing a specific job and it has LAG and VPN settings and next hops for our internet access to two ISPs.  It was not managed by Mist because it never needed to be changed.  When it was changed to be managed all of that code was removed and the Template  settings, which where pretty generic replaced what we had.   

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 09:39
From: CRAIG DALRYMPLE
Subject: Steps to remove a lag setting on EX switch?

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

------------------------------
CRAIG DALRYMPLE

Original Message:
Sent: 04-02-2025 09:26
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

Thanks.

"When I tried to remove the ports from ae0" -----> I believe you tried removing this from the template port-config? If yes, did you also delete the additional CLI where you had IP address configured for ae0 interface?

If the highlighted additional CLI is not deleted and only the port-configuration is removed, the device retains ae0 and ae1 configurations. Mist will set the device-count to 1 in the new config, causing the error.

Regards

Sheetqnshu,

The config on this swich is as follows:

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set interfaces ae1 unit 0 family inet address 10.254.253.86/29

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

set interfaces ae1 apply-groups lag40g

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae1 aggregated-ether-options lacp active

set groups top chassis aggregated-devices ethernet device-count 2

As you can see I have to AE and the device count is a set to 2. 

When I tried to remove the ports from ae0 I got an error that implied my device count was 1.

"error commit-confirm: number of AE devices configured 2 is more than device-count 1."

• The commit-confirm error occurs due to two AE interfaces in the configuration, but the device-count in "aggregated-devices" in the "set chassis" command is set to 1. It complains that you have more AEs than the configured device count, not the other way around.
• Verify if the device has only one AE interface, as stated, or two. As IPs were assigned to both ae0 and ae1 interfaces in the earlier additional CLI section screenshot to configure IPs on those interfaces.
• Mist will adjust the device count in the "set groups top chassis aggregated-devices" command based on the configured AE interfaces in the template
• On the device, is there a "set chassis aggregated-devices ethernet device-count 1" outside the "groups top" configuration? If yes, that will take precedence.
• On the device CLI itself (not from the template) can you please check the following: -
• a) show interfaces terse | match ae <<<<<<<---------- this will show how many ae interfaces are actually on the device.
• b) show configuration | match device-count | display set <<<<<<------ this will show if there is any other CLI command on the switch apart from the groups top, that Mist pushes)

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-07-2025 11:22
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Ive compared the template config to the switch CLI config, and they appear to match as far as ports 0/0/22 and 0/0/23 and ae0 and LAG10 are concerned. 

I decided to to remove commands in the template that were no longer needed. When I removed the these to commands..

delete interfaces xe-0/0/22 unit 0

delete interfaces xe-0/0/23 unit 0

I no longer see the commands on the switch, but I see this error in the switch insights:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

The setting for AR devices is:

set groups top chassis aggregated-devices ethernet device-count 2

In my video watching on this topic, it looked like you could set the count higher than the current AE count for future use. So, why is it complaining that I have less AEs than the count specifies? 

I decided to change the device-count to 1 in the template to make the error go away, and I got this config failure error:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

So. with the count set at 2 I get an error that I have too many AEs ( Only 1 )  and with the count at 1 the error is that I don't have enough AEs ( Now with 2 )  

How am I supposed to fix this?! 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 10:17
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Craig,

I thought that was the case in the past, but I found out the hard way that large sections of code can be removed by Mist.  We have a 4600 doing a specific job and it has LAG and VPN settings and next hops for our internet access to two ISPs.  It was not managed by Mist because it never needed to be changed.  When it was changed to be managed all of that code was removed and the Template  settings, which where pretty generic replaced what we had.   

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 09:39
From: CRAIG DALRYMPLE
Subject: Steps to remove a lag setting on EX switch?

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

------------------------------
CRAIG DALRYMPLE

Original Message:
Sent: 04-02-2025 09:26
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

Which is why I started this thread to see if there was an order that I need to remove things. 

Thanks.

"When I tried to remove the ports from ae0" -----> I believe you tried removing this from the template port-config? If yes, did you also delete the additional CLI where you had IP address configured for ae0 interface?

If the highlighted additional CLI is not deleted and only the port-configuration is removed, the device retains ae0 and ae1 configurations. Mist will set the device-count to 1 in the new config, causing the error.

Regards

Sheetqnshu,

The config on this swich is as follows:

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set interfaces ae1 unit 0 family inet address 10.254.253.86/29

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

set interfaces ae1 apply-groups lag40g

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae1 aggregated-ether-options lacp active

set groups top chassis aggregated-devices ethernet device-count 2

As you can see I have to AE and the device count is a set to 2. 

When I tried to remove the ports from ae0 I got an error that implied my device count was 1.

"error commit-confirm: number of AE devices configured 2 is more than device-count 1."

• The commit-confirm error occurs due to two AE interfaces in the configuration, but the device-count in "aggregated-devices" in the "set chassis" command is set to 1. It complains that you have more AEs than the configured device count, not the other way around.
• Verify if the device has only one AE interface, as stated, or two. As IPs were assigned to both ae0 and ae1 interfaces in the earlier additional CLI section screenshot to configure IPs on those interfaces.
• Mist will adjust the device count in the "set groups top chassis aggregated-devices" command based on the configured AE interfaces in the template
• On the device, is there a "set chassis aggregated-devices ethernet device-count 1" outside the "groups top" configuration? If yes, that will take precedence.
• On the device CLI itself (not from the template) can you please check the following: -
• a) show interfaces terse | match ae <<<<<<<---------- this will show how many ae interfaces are actually on the device.
• b) show configuration | match device-count | display set <<<<<<------ this will show if there is any other CLI command on the switch apart from the groups top, that Mist pushes)

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-07-2025 11:22
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Ive compared the template config to the switch CLI config, and they appear to match as far as ports 0/0/22 and 0/0/23 and ae0 and LAG10 are concerned. 

I decided to to remove commands in the template that were no longer needed. When I removed the these to commands..

delete interfaces xe-0/0/22 unit 0

delete interfaces xe-0/0/23 unit 0

I no longer see the commands on the switch, but I see this error in the switch insights:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

The setting for AR devices is:

set groups top chassis aggregated-devices ethernet device-count 2

In my video watching on this topic, it looked like you could set the count higher than the current AE count for future use. So, why is it complaining that I have less AEs than the count specifies? 

I decided to change the device-count to 1 in the template to make the error go away, and I got this config failure error:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

So. with the count set at 2 I get an error that I have too many AEs ( Only 1 )  and with the count at 1 the error is that I don't have enough AEs ( Now with 2 )  

How am I supposed to fix this?! 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 10:17
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Craig,

I thought that was the case in the past, but I found out the hard way that large sections of code can be removed by Mist.  We have a 4600 doing a specific job and it has LAG and VPN settings and next hops for our internet access to two ISPs.  It was not managed by Mist because it never needed to be changed.  When it was changed to be managed all of that code was removed and the Template  settings, which where pretty generic replaced what we had.   

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 09:39
From: CRAIG DALRYMPLE
Subject: Steps to remove a lag setting on EX switch?

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

------------------------------
CRAIG DALRYMPLE

Original Message:
Sent: 04-02-2025 09:26
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

The matter isn't with the order. The configuration of ae0 and ae1 lag interfaces in your template, including creating an L2 port-profile, deleting the group with additional CLI, and assigning IPs, isn't the correct way to set up an L3 lag interface. This approach uses unnecessary workarounds, when the configuration can be achieved in a much simpler way. As explained earlier and shown in the screenshot, the L3 AE port configuration should be done directly on the switch, making deletion a simple one-click task by removing the port configuration.

Regards

Which is why I started this thread to see if there was an order that I need to remove things. 

Thanks.

"When I tried to remove the ports from ae0" -----> I believe you tried removing this from the template port-config? If yes, did you also delete the additional CLI where you had IP address configured for ae0 interface?

If the highlighted additional CLI is not deleted and only the port-configuration is removed, the device retains ae0 and ae1 configurations. Mist will set the device-count to 1 in the new config, causing the error.

Regards

Sheetqnshu,

The config on this swich is as follows:

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set interfaces ae1 unit 0 family inet address 10.254.253.86/29

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

set interfaces ae1 apply-groups lag40g

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae1 aggregated-ether-options lacp active

set groups top chassis aggregated-devices ethernet device-count 2

As you can see I have to AE and the device count is a set to 2. 

When I tried to remove the ports from ae0 I got an error that implied my device count was 1.

"error commit-confirm: number of AE devices configured 2 is more than device-count 1."

• The commit-confirm error occurs due to two AE interfaces in the configuration, but the device-count in "aggregated-devices" in the "set chassis" command is set to 1. It complains that you have more AEs than the configured device count, not the other way around.
• Verify if the device has only one AE interface, as stated, or two. As IPs were assigned to both ae0 and ae1 interfaces in the earlier additional CLI section screenshot to configure IPs on those interfaces.
• Mist will adjust the device count in the "set groups top chassis aggregated-devices" command based on the configured AE interfaces in the template
• On the device, is there a "set chassis aggregated-devices ethernet device-count 1" outside the "groups top" configuration? If yes, that will take precedence.
• On the device CLI itself (not from the template) can you please check the following: -
• a) show interfaces terse | match ae <<<<<<<---------- this will show how many ae interfaces are actually on the device.
• b) show configuration | match device-count | display set <<<<<<------ this will show if there is any other CLI command on the switch apart from the groups top, that Mist pushes)

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-07-2025 11:22
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Ive compared the template config to the switch CLI config, and they appear to match as far as ports 0/0/22 and 0/0/23 and ae0 and LAG10 are concerned. 

I decided to to remove commands in the template that were no longer needed. When I removed the these to commands..

delete interfaces xe-0/0/22 unit 0

delete interfaces xe-0/0/23 unit 0

I no longer see the commands on the switch, but I see this error in the switch insights:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

The setting for AR devices is:

set groups top chassis aggregated-devices ethernet device-count 2

In my video watching on this topic, it looked like you could set the count higher than the current AE count for future use. So, why is it complaining that I have less AEs than the count specifies? 

I decided to change the device-count to 1 in the template to make the error go away, and I got this config failure error:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

So. with the count set at 2 I get an error that I have too many AEs ( Only 1 )  and with the count at 1 the error is that I don't have enough AEs ( Now with 2 )  

How am I supposed to fix this?! 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 10:17
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Craig,

I thought that was the case in the past, but I found out the hard way that large sections of code can be removed by Mist.  We have a 4600 doing a specific job and it has LAG and VPN settings and next hops for our internet access to two ISPs.  It was not managed by Mist because it never needed to be changed.  When it was changed to be managed all of that code was removed and the Template  settings, which where pretty generic replaced what we had.   

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 09:39
From: CRAIG DALRYMPLE
Subject: Steps to remove a lag setting on EX switch?

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

------------------------------
CRAIG DALRYMPLE

Original Message:
Sent: 04-02-2025 09:26
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

"the L3 AE port configuration should be done directly on the switch"

If not added to the additional CLI in the template, wouldn't it be removed? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-08-2025 13:12
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

The matter isn't with the order. The configuration of ae0 and ae1 lag interfaces in your template, including creating an L2 port-profile, deleting the group with additional CLI, and assigning IPs, isn't the correct way to set up an L3 lag interface. This approach uses unnecessary workarounds, when the configuration can be achieved in a much simpler way. As explained earlier and shown in the screenshot, the L3 AE port configuration should be done directly on the switch, making deletion a simple one-click task by removing the port configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-08-2025 12:44
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Which is why I started this thread to see if there was an order that I need to remove things. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-08-2025 00:09
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Thanks.

"When I tried to remove the ports from ae0" -----> I believe you tried removing this from the template port-config? If yes, did you also delete the additional CLI where you had IP address configured for ae0 interface?

If the highlighted additional CLI is not deleted and only the port-configuration is removed, the device retains ae0 and ae1 configurations. Mist will set the device-count to 1 in the new config, causing the error.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-07-2025 16:12
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetqnshu,

The config on this swich is as follows:

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set interfaces ae1 unit 0 family inet address 10.254.253.86/29

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

set interfaces ae1 apply-groups lag40g

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae1 aggregated-ether-options lacp active

set groups top chassis aggregated-devices ethernet device-count 2

As you can see I have to AE and the device count is a set to 2. 

When I tried to remove the ports from ae0 I got an error that implied my device count was 1.

"error commit-confirm: number of AE devices configured 2 is more than device-count 1."

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-07-2025 11:53
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

• The commit-confirm error occurs due to two AE interfaces in the configuration, but the device-count in "aggregated-devices" in the "set chassis" command is set to 1. It complains that you have more AEs than the configured device count, not the other way around.
• Verify if the device has only one AE interface, as stated, or two. As IPs were assigned to both ae0 and ae1 interfaces in the earlier additional CLI section screenshot to configure IPs on those interfaces.
• Mist will adjust the device count in the "set groups top chassis aggregated-devices" command based on the configured AE interfaces in the template
• On the device, is there a "set chassis aggregated-devices ethernet device-count 1" outside the "groups top" configuration? If yes, that will take precedence.
• On the device CLI itself (not from the template) can you please check the following: -
• a) show interfaces terse | match ae <<<<<<<---------- this will show how many ae interfaces are actually on the device.
• b) show configuration | match device-count | display set <<<<<<------ this will show if there is any other CLI command on the switch apart from the groups top, that Mist pushes)

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-07-2025 11:22
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Ive compared the template config to the switch CLI config, and they appear to match as far as ports 0/0/22 and 0/0/23 and ae0 and LAG10 are concerned. 

I decided to to remove commands in the template that were no longer needed. When I removed the these to commands..

delete interfaces xe-0/0/22 unit 0

delete interfaces xe-0/0/23 unit 0

I no longer see the commands on the switch, but I see this error in the switch insights:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

The setting for AR devices is:

set groups top chassis aggregated-devices ethernet device-count 2

In my video watching on this topic, it looked like you could set the count higher than the current AE count for future use. So, why is it complaining that I have less AEs than the count specifies? 

I decided to change the device-count to 1 in the template to make the error go away, and I got this config failure error:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

So. with the count set at 2 I get an error that I have too many AEs ( Only 1 )  and with the count at 1 the error is that I don't have enough AEs ( Now with 2 )  

How am I supposed to fix this?! 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 10:17
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Craig,

I thought that was the case in the past, but I found out the hard way that large sections of code can be removed by Mist.  We have a 4600 doing a specific job and it has LAG and VPN settings and next hops for our internet access to two ISPs.  It was not managed by Mist because it never needed to be changed.  When it was changed to be managed all of that code was removed and the Template  settings, which where pretty generic replaced what we had.   

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-03-2025 09:39
From: CRAIG DALRYMPLE
Subject: Steps to remove a lag setting on EX switch?

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

------------------------------
CRAIG DALRYMPLE

Original Message:
Sent: 04-02-2025 09:26
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------

Ive compared the template config to the switch CLI config, and they appear to match as far as ports 0/0/22 and 0/0/23 and ae0 and LAG10 are concerned. 

I decided to to remove commands in the template that were no longer needed. When I removed the these to commands..

delete interfaces xe-0/0/22 unit 0

delete interfaces xe-0/0/23 unit 0

I no longer see the commands on the switch, but I see this error in the switch insights:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

The setting for AR devices is:

set groups top chassis aggregated-devices ethernet device-count 2

In my video watching on this topic, it looked like you could set the count higher than the current AE count for future use. So, why is it complaining that I have less AEs than the count specifies? 

I decided to change the device-count to 1 in the template to make the error go away, and I got this config failure error:

error commit-confirm: number of AE devices configured 2 is more than device-count 1.

So. with the count set at 2 I get an error that I have too many AEs ( Only 1 )  and with the count at 1 the error is that I don't have enough AEs ( Now with 2 )  

How am I supposed to fix this?! 

Craig,

I thought that was the case in the past, but I found out the hard way that large sections of code can be removed by Mist.  We have a 4600 doing a specific job and it has LAG and VPN settings and next hops for our internet access to two ISPs.  It was not managed by Mist because it never needed to be changed.  When it was changed to be managed all of that code was removed and the Template  settings, which where pretty generic replaced what we had.   

Ok, I am probably going to catch a lot of grief for this, but, I dislike the use of the terms "overwrite" and "override" and the way these are used/interpreted, especially when relating to MWA (Mist Wired Assurance) and configuration commands. Realize that all my MWA knowledge is from having to jump into the deep end with concrete sneakers, so I may be misunderstanding something.
It is my experience, and observation, that Mist doesn't overwrite anything, at least as someone who grew up on the CLI would understand it.  Every experience I have had to date, it appears that whatever MWA is setting/modifying is actually MERGED with the existing candidate configuration.  For example, if right out of the box you enter configuration mode and set 1.2.2.1 as a name server, then commit and-quit, when the device finally connects to and is managed by MWA and the appropriate configuration is pushed, that name-server command is still there and will be until you remove it via the CLI or the Additional CLI Commands section of the device configuration page.

There are some commands where this doesn't apply, typically commands that cannot retain multiple values, but even in those cases you can't be 100% sure that the MWA config is the one that is RUNNING on the device.  This is the pitfall when using apply groups only. If the apply groups were done with a mechanism similar to using the junos "load" command, you would get around this by using the "override" option.

Tracking down the lines that are held over before the device has been joined to MWA has become an art form....

John,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

Yes, Mist will overwrite it. I mentioned that it is either locally configured (temporary for the moment) or via additional CLI section of Mist (permanent). The point was that deactivate commands are not required if the AE interface is configured correctly via the Mist template.

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

If configured correctly, the AE index should be set on the port configuration, as shown below. Port-aggregation option should be enabled to show the AE index field.If index 1 is not defined as shown below, then only the additional CLI to set the ether options either at the ORG template level (highlighted in the image below) OR at the site level OR at the switch level can populate the command.

Please share a screenshot of your port configuration from the ORG template and CLI Config (from the ORG template, site, and switch levels) to check further.

Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

No, keeping the SFPs in place is not required. Even if the interfaces will no longer be listed, there will be no commit errors for the switch configuration.

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 04-01-2025 16:13
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Sheetanshu,

"The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI."

If it was configured locally, wouldn't the config in the Mist dashboard overwrite it? 

I see in the "port config" of the section of our ORG template where this switch assigned the 26 and 27 ports to a LAG named 40, but nowhere in the profile does it say AE1 or anything that just says index 1.  The only mention of AE1 in the template, that I have found, is a multicast setting, "set protocols pim interface ae1 mode sparse".  So, I still don't see where " ether-options 802.3ad ae1 " is defined. 

Refering back to my original post...Do I need to keep the SFPs in place until after removing the configuration for the ports 0/0/22 and 0/0/23? 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 04-01-2025 14:05
From: Sheetanshu
Subject: Steps to remove a lag setting on EX switch?

Hi John,

• In the port assignments on the Mist switch, the configuration-profile or port-profile assigned to ports et-0/0/26 and et-0/0/27 (e.g., in the second case with group lag40) is named lag40g. This group, lag40g, is created as a result.
• The lag40g port-profile is configured as an access-port profile, with the port network set to data2. The VLAN members assigned to this group are therefore data42.
• The AE Index for these ports is set to 1, so the 802.3ad ether-options for these ports are configured as ae1.
• The deactivate commands for unit 0 are unnecessary, as they must have been configured either locally on the switch or via additional CLI. Mist will automatically remove the unit 0 configurations on ports that are part of the AE interface.

Regarding the error you encounter when attempting to delete the port configurations for xe-0/0/22 and xe-0/0/23, could you please share the error message and a screenshot of what you are attempting to delete?

Regards

------------------------------
Sheetanshu Shekhar

Original Message:
Sent: 03-28-2025 14:59
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

Adding some info 

I've pulled the config that Mist has for one of the switches in question and matched up where each line of the config ,that relates to AEs and Lags, in the templates and any " additional CLI " on the switch page.  

I can not find the location of these sets of commands.  Clearly, the ae0 ones are not ones I wish to remove, but I do want to know where to find the source of the setting

set interfaces et-0/0/26 ether-options 802.3ad ae1

set interfaces et-0/0/27 ether-options 802.3ad ae1

deactivate interfaces et-0/0/26 unit 0

deactivate interfaces et-0/0/27 unit 0

set groups lag40g interfaces <*> unit 0 family ethernet-switching vlan members [ data2 ]

I want to make sure I fully understand the flow of the config from the dashboard to the switch, so I can apply changes with more confidence. 

------------------------------
JOHN WILLIAMSON

Original Message:
Sent: 03-27-2025 16:41
From: JOHN WILLIAMSON
Subject: Steps to remove a lag setting on EX switch?

I thought I had asked this question before, but I didn't find it in the My Elevate list. I apologize if it is in the community somewhere. 

I have the following config on our site EX4600s with different IPs of course, and this LAG is no longer needed. The settings are applied via a template for each switch. WHen I try to remove them from the templates I end up with an error. I suspect there is an order of operation I need to take these steps. 

set interfaces xe-0/0/22 ether-options 802.3ad ae0

set interfaces xe-0/0/23 ether-options 802.3ad ae0

set interfaces ae0 aggregated-ether-options lacp active

set interfaces ae0 unit 0 family inet address 10.254.254.34/30

set groups lag10g interfaces <*> unit 0 family ethernet-switching vlan members data2

Secondly, should I leave the SFPs in the switch until these are removed? The interfaces will no longer be listed, if I pull them out, as this is only a fiber switch. 

John

------------------------------
JOHN WILLIAMSON
------------------------------