Switching

We had a lag in the past on a pair of interfaces, but we updated the the config to use faster SFPs on a different pair of ports. I'm trying to remove the older ae0.  Here is the config from the CLI on the switch. I need to remove these by the Org template and not directly on the CLI. 

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.10/29

I suspect there may be a proper order of operations about removing these commands.  When I try to complete a removal on a few switches, I am getting a commit error.

" error commit-confirm: [edit interfaces ae1 unit 0 family] ethernet-switching: Family ethernet-switching and rest of the families are mutually exclusive "

I am not trying to remove ae1 in the CLI pane in the template.  All edits have to do with ae0. 

The switch that is currently not happy already has the inet address line removed via the template. I tried adding it back, thinking I should take another step first, but I get the same error when I try to do that. 

What is the proper order to remove this ae?

John, 

As you already notice, the error is specific to ae1, yet your config only show ae0 and therefore I can not judge or provide correct answer . But....
Mist like to use groups and interface-ranges to configure specific interfaces via inheritance method. To only way to see the entire configuration on device managed by mist, you MUST use display inheritance. Example

We had a lag in the past on a pair of interfaces, but we updated the the config to use faster SFPs on a different pair of ports. I'm trying to remove the older ae0.  Here is the config from the CLI on the switch. I need to remove these by the Org template and not directly on the CLI. 

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.10/29

I suspect there may be a proper order of operations about removing these commands.  When I try to complete a removal on a few switches, I am getting a commit error.

" error commit-confirm: [edit interfaces ae1 unit 0 family] ethernet-switching: Family ethernet-switching and rest of the families are mutually exclusive "

I am not trying to remove ae1 in the CLI pane in the template.  All edits have to do with ae0. 

The switch that is currently not happy already has the inet address line removed via the template. I tried adding it back, thinking I should take another step first, but I get the same error when I try to do that. 

What is the proper order to remove this ae?

Thanks for your reply Patrik. 

I'll look at what info I can get for you.  It's been about 7 months since I was working on this task and since no users were effected by the config, I have let it remain until I had time to revisit it.   Thanks for this reminder!

John

John, 

As you already notice, the error is specific to ae1, yet your config only show ae0 and therefore I can not judge or provide correct answer . But....
Mist like to use groups and interface-ranges to configure specific interfaces via inheritance method. To only way to see the entire configuration on device managed by mist, you MUST use display inheritance. Example

We had a lag in the past on a pair of interfaces, but we updated the the config to use faster SFPs on a different pair of ports. I'm trying to remove the older ae0.  Here is the config from the CLI on the switch. I need to remove these by the Org template and not directly on the CLI. 

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.10/29

I suspect there may be a proper order of operations about removing these commands.  When I try to complete a removal on a few switches, I am getting a commit error.

" error commit-confirm: [edit interfaces ae1 unit 0 family] ethernet-switching: Family ethernet-switching and rest of the families are mutually exclusive "

I am not trying to remove ae1 in the CLI pane in the template.  All edits have to do with ae0. 

The switch that is currently not happy already has the inet address line removed via the template. I tried adding it back, thinking I should take another step first, but I get the same error when I try to do that. 

What is the proper order to remove this ae?

mist@VPNL-MDFS01> show configuration interfaces ae1 | display inheritance terse    
aggregated-ether-options {
    lacp {
        active;
    }
}
unit 0 {
    family inet {
        address 10.254.253.102/29;
    }
}

Thanks for your reply Patrik. 

I'll look at what info I can get for you.  It's been about 7 months since I was working on this task and since no users were effected by the config, I have let it remain until I had time to revisit it.   Thanks for this reminder!

John

John, 

As you already notice, the error is specific to ae1, yet your config only show ae0 and therefore I can not judge or provide correct answer . But....
Mist like to use groups and interface-ranges to configure specific interfaces via inheritance method. To only way to see the entire configuration on device managed by mist, you MUST use display inheritance. Example

We had a lag in the past on a pair of interfaces, but we updated the the config to use faster SFPs on a different pair of ports. I'm trying to remove the older ae0.  Here is the config from the CLI on the switch. I need to remove these by the Org template and not directly on the CLI. 

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.10/29

I suspect there may be a proper order of operations about removing these commands.  When I try to complete a removal on a few switches, I am getting a commit error.

" error commit-confirm: [edit interfaces ae1 unit 0 family] ethernet-switching: Family ethernet-switching and rest of the families are mutually exclusive "

I am not trying to remove ae1 in the CLI pane in the template.  All edits have to do with ae0. 

The switch that is currently not happy already has the inet address line removed via the template. I tried adding it back, thinking I should take another step first, but I get the same error when I try to do that. 

What is the proper order to remove this ae?

mist@VPNL-MDFS01> show configuration interfaces ae0 | display inheritance terse 
aggregated-ether-options {
    lacp {
        active;
    }
}
unit 0 {
    family inet {
        address 10.254.254.58/30;
    }
}

mist@VPNL-MDFS01> show configuration interfaces ae1 | display inheritance terse    
aggregated-ether-options {
    lacp {
        active;
    }
}
unit 0 {
    family inet {
        address 10.254.253.102/29;
    }
}

Thanks for your reply Patrik. 

I'll look at what info I can get for you.  It's been about 7 months since I was working on this task and since no users were effected by the config, I have let it remain until I had time to revisit it.   Thanks for this reminder!

John

John, 

As you already notice, the error is specific to ae1, yet your config only show ae0 and therefore I can not judge or provide correct answer . But....
Mist like to use groups and interface-ranges to configure specific interfaces via inheritance method. To only way to see the entire configuration on device managed by mist, you MUST use display inheritance. Example

We had a lag in the past on a pair of interfaces, but we updated the the config to use faster SFPs on a different pair of ports. I'm trying to remove the older ae0.  Here is the config from the CLI on the switch. I need to remove these by the Org template and not directly on the CLI. 

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.10/29

I suspect there may be a proper order of operations about removing these commands.  When I try to complete a removal on a few switches, I am getting a commit error.

" error commit-confirm: [edit interfaces ae1 unit 0 family] ethernet-switching: Family ethernet-switching and rest of the families are mutually exclusive "

I am not trying to remove ae1 in the CLI pane in the template.  All edits have to do with ae0. 

The switch that is currently not happy already has the inet address line removed via the template. I tried adding it back, thinking I should take another step first, but I get the same error when I try to do that. 

What is the proper order to remove this ae?