When using the new-style MX L2 commands, the bridge-domains do not require you to add the interface.
However you need to use the bridge-domains knob "routing-interface" to point to the irb interface. Also on the MX you need to create interface "irb.601" and not "vlan.601" Thank you, -- Doug Hanks - JNCIE-ENT #213, JNCIE-SP #875 Sr. Systems Engineer Juniper Networks On 11/11/11 5:01 AM, "Humair Ali" <[email protected]> wrote: >arent you missing the interface in your bridge-domain ? > >On 11 November 2011 11:46, saurabh sood <[email protected]> wrote: > >> Hello Experts, >> >> During the configuration for vlan and vlan l3-interfaces we observed >> "error: device vlan not found". >> >> Following is configuration which i did on MX80 (11.2R3): >> >> interfaces { >> ge-0/0/0 { >> unit 0 { >> family bridge { >> interface-mode access; >> vlan-id 601; >> } >> } >> vlan { >> unit 601 { >> family inet { >> no-redirects; >> address 10.20.21.22/24 { >> } >> } >> } >> } >> } >> >> bridge-domains { >> default { >> description default; >> domain-type bridge; >> vlan-id 1; >> } >> vlan-601 { >> domain-type bridge; >> vlan-id 601; >> } >> } >> >> we are getting: >> > show interfaces vlan >> error: device vlan not found >> >> Please let me know if this is not supported or there is any other >>reason. >> >> Aside, during a test with irb interfaces everything is working fine. >> >> Thanks in advance!!! >> >> Regards, >> >> Sunny >> _______________________________________________ >> juniper-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > > > >-- >Humair >_______________________________________________ >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
