Ethernet Switching
Ethernet Switching

ae configuration not able to be committed

‎08-12-2019 03:12 PM

We got a EX3400 and would need to incorporate the configurations in EX2200 where ae is concerned:

 

chassis {
aggregated-devices {
ethernet {
device-count 1;
}
}
alarm {
management-ethernet {
link-down ignore;
}
}
auto-image-upgrade;
}

...

ge-0/0/20 {
ether-options {
802.3ad ae0;
}
}
ge-0/0/21 {
ether-options {
802.3ad ae0;
}
}

......

ae0 {
description "LAG to Juniper Fw02.vlan20";
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members svr;
}
}
}
}

 

I was trying to configure ae in J-web, but I goth this error message:

The configuration could not be locked.

Error(s):
'interface'

1) XSTP : Interface ge-0/0/20 is not enabled for Ethernet Switching
2) configuration check-out failed

 

Can someone help me out?

 

Appreciated.

 

Wayne 

5 REPLIES 5
Ethernet Switching

Re: ae configuration not able to be committed

‎08-12-2019 05:24 PM

Hi Wayne,

 

Looks like you have spanning tree configured on ge-0/0/20, which is now a in a lagg. 

Delete the spanning tree configuration for both ge-0/0/20 and ge-0/0/21.

 

show configuration protocols

Not sure which version you are running but will be under rstp / vstp / mst. I do not use j-web but I assume there is a protocols section somwhere.

 

Tim

Ethernet Switching

Re: ae configuration not able to be committed

[ Edited ]
‎08-12-2019 06:23 PM

Hey all!

 

I am going to move this post to a better spot - the Switching Forum!

 

Thanks for contributing to the community!

- Jeremiah, Community Manager

 

Jeremiah
J-Net Community Manager
Ethernet Switching

Re: ae configuration not able to be committed

‎08-12-2019 06:40 PM
Hi Wayne,

Could you please provide the output of “ show configuration protocols” ? it might be that ge-0/0/20 is configured for spanning tree

Below command will show what all has been configured for ge-0/0/20

show configuration | match ge-0/0/20 | display set

Regards,
Jibu
Ethernet Switching

Re: ae configuration not able to be committed

‎08-12-2019 08:58 PM

Hello Wayne

 

Please compare the default configuration of interface ge-0/0/20 and ge-0/0/21 and make the configuration identical.

You are seeing the error message only for ge-0/0/20 and not ge-0/0/21. Most probably you might have to enable the ethernet switching on the interfacege-0/0/20.

 

Thanks

 

Ethernet Switching
Solution
Accepted by topic author Wayne L
‎08-13-2019 06:56 AM

Re: ae configuration not able to be committed

‎08-13-2019 05:22 AM

Interfaces ge-0/0/20 and ge-0/0/20 could be enabled for spanning-tree since by default rstp is enabled for all interfaces.

 

Remove the ports from spanning-tree and commit again.

 

https://www.juniper.net/documentation/en_US/junos/topics/example/layer-2-spanning-tree-security-conf...