I think the following link can answer it for you: http://www.juniper.net/techpubs/en_US/junos13.2/topics/task/configuration/getting-started-els.html
Enhanced Layer 2 Software EX4300 switches 13.2X50-D10 EX9200 switches 12.3R2 QFX3500 switches 13.2X50-D15 QFX3600 switches 13.2X50-D15 QFX5100 switches 13.2X51-D10 Giuliano Cardozo Medalha Systems Engineer +55 (17) 3011-3811 +55 (17) 8112-5394 JUNIPER J-PARTNER ELITE [email protected] http://www.wztech.com.br/ WZTECH is registered trademark of WZTECH NETWORKS. Copyright © 2013 WZTECH NETWORKS. All Rights Reserved. The information transmitted in this email message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any review, transmission, dissemination or other use of this information is prohibited. If you have received this communication in error, please notify the sender immediately and delete the material from any computer, including any copies. On Wed, Feb 19, 2014 at 3:15 PM, Bill Blackford <[email protected]>wrote: > Next Gen CLI for layer2. This is the same format as the Layer2 Functions > on the MX. Is this a trend for all EX products or just the NG hardware? > > > On Wed, Feb 19, 2014 at 2:25 AM, Giuliano Cardozo Medalha < > [email protected]> wrote: > >> ex4300 uses next generation cli for L2 >> >> instead of use interface vlan you need to use interface irb >> >> set vlan TEST vlan-id 20 l3-interface irb.20 >> >> set interface irb unit 20 family inet address 192.168.20.100/24 >> >> and now for port mode ( access x trunk ) you need to use >> >> interface-mode ... >> >> dhcp-relay and rstp changed too ... >> >> set forwarding-options dhcp-relay ... and not helpers anymore >> >> set protocols rstp interface ge-0/0/0 >> >> you need to declare every interface under rstp ... >> >> wildcard range set protocols ... helps >> >> wildcard range set interfaces ... too >> >> to see trunk ports >> >> > show ethernet-switching interface | except untagged | match tagged >> >> >> >> Sent from my iPhone >> >> > On 19/02/2014, at 00:44, Janusz Wełna <[email protected]> wrote: >> > >> > Hi, >> > >> > >> > Why when I have below config: >> > >> > ge-0/0/44 { >> > description test; >> > unit 0 { >> > family ethernet-switching { >> > vlan { >> > members vlan103; >> > } >> > storm-control default; >> > >> > unit 103 { >> > description test; >> > family inet { >> > address 10.46.163.1/29; >> > >> > >> > vlan103 { >> > description test; >> > vlan-id 103; >> > l3-interface vlan.103; >> > >> > >> > >> > >> > I cannot ping from EX4300 10.46.163.1 and I cannot ping 10.46.163.1 from >> > server connected to ge-0/0/44 >> > >> > >> > >> > >> > But when I add below: >> > >> > >> > irb { >> > unit 103 { >> > family inet { >> > address 10.46.163.1/29; >> > >> > >> > and delete : >> > >> > >> > vlan103 { >> > description SGI; >> > vlan-id 103; >> > l3-interface vlan.103 >> > >> > >> > >> > >> > ping works correctly. >> > >> > >> > On EX3300, EX4200 and EX2200 I not need setup irb interface, why I need >> on >> > EX4300 ? >> > >> > >> > >> > Br, >> > >> > >> > Janusz >> > _______________________________________________ >> > juniper-nsp mailing list [email protected] >> > https://puck.nether.net/mailman/listinfo/juniper-nsp >> >> _______________________________________________ >> juniper-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > > > > -- > Bill Blackford > > Logged into reality and abusing my sudo privileges..... > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
