Enhanced Layer 2 Software (ELS) provides a uniform command-line interface (CLI) for configuring and monitoring Layer 2 features on EX Series switches that support ELS, such as EX4300 and EX9200 switches, and on MX Series routers in LAN mode (MX-ELM).
Link to MX-ELM for more details below:
Enhanced Layer 2 Software (ELS) provides a uniform CLI for configuring and monitoring Layer 2 features on QFX Series switches, EX Series switches, and other Juniper Networks devices, such as MX Series routers. With ELS, you configure Layer 2 features in the same way on all these Juniper Networks devices.
Yes, there will be some features that work on Non-ELS that are not flexible for ELS device and vise versa.
List of products and applications that support ELS:
The below link will give you details about configuration on ELS devices and what is the difference in configuration statements:
If I am getting your last question correctly, you would want to introduce ELS on a Non-ELS device. Correct me if I am wrong. As far as I understand, that is not possible.
Hope this helps 🙂
Please mark this as an "Accepted Solution" if this helps you solve your queries.
Kudos would be always appreciated!
This is to unify the syntax with new devices, but the configuration syntax is not that difference from els to non-els ,other than CoS for QFXs...
You can check the difference here too
Hope this help!
If this solves your problem, please mark this post as "Accepted Solution".
If you think that my answer was helpful, please spend some Kudos.
Enhanced Layer 2 Software (ELS) provides a uniform command-line interface (CLI) for configuring and monitoring Layer 2 features on EX Series switches that support ELS, such as EX4300 and EX9200 switches, and on MX Series routers in LAN mode (MX-ELM).The web-based ELS Translator tool is available for registered customers to help them become familiar with the ELS CLI and to quickly translate existing EX Series switch–based CLI configurations into ELS CLI configurations.
To check which all devices support the feature:
To know more and the exact device:
The above directly downloads a PDF and you can view the difference between ELS and a normal Juniper device.
I hope this helps. Please mark this post "Accept as solution" if this answers your query.
Kudos are always appreciated!
Couple of clarifications below. #1, ELS was a way to get more CLI syntax consistency across all Juniper products, that run Junos. Namely EX/QFX, MX/PTX/ACX, and SRX. For SRX branch follows like EX, while HE/Mid SRX is like MX.
ELS/non-ELS for EX is model dependant, not SW dependant. You can not change SW and get a different format of the CLI syntax. ELS is support by all newer [Broadcom] based models, while non-ELS is used with older legacy [Marvel] based models.
Both EX9200 and all [current] QFX 5K/10K based models only support ELS, from day 1.
The ELS Translator tool has been decommisioned, so no longer available.
MX is the one product that moved to ELS in SW, but MX was basically ELS-like always. MX L3 is the same as ELS L3, and MX (and EX9200) still only support "bridge-domains" for L2, while EX/QFX ELS supports "vlans".
MX LAN Mode (https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/configuring-mx-enhanced-lan-mode.html) which is now an obsolete concept (has not really applied for last 5+ years), has nothing to do with ELS Syntax on MX. MX-ELM has basically been replaced by newer Flex Licensing model.
I believe the above is correct. Just to repeat, for EX 4K series and QFX 5K/10K, you can not change from ELS to non-ELS or vice-a-versus via any SW change. Branch SRX are similar, in the older 2xx Series is non-ELS, while new 3xx series in ELS based.
As everyone has said, it unifies syntax across platforms.
If you want to see it in action, try configuring DHCP on an older non-ELS device. Now, try it on a new one.
You'll see that there are two ways that this can be done, the legacy way, and the extended way. This is one example of changing the configuration syntax to be consistent across devices.