I'm not sure if you're sanitising your config, but I don't think you'll be able
to commit with a network address applied to an interface (eg: 10.0.1.0/24) -
it'll have to be a host address.
On 20/04/2011, at 3:19 PM, Jesus Alvarez wrote:
> Hi,
>
> Has anyone used multiple VLANs on a FastE port in the M series routers (like
> the PE-4FE-TX on the M7i)? I tried a configuration similar to the one below
> and connected it to a trunk port on an EX switch. Unfortunately, the
> subinterfaces can not communicate with other devices on that switch with the
> same vlan-ids.
>
> If I configure each subnet on a separate FastE port without using
> vlan-tagging and then connect them to access ports on the switch for each
> vlan-id, it does work. Yet that limits the number of VLANs to the number of
> ports available.
>
> I consulted with the JTAC but they seem to be confusing the issue with a
> default-vlan problem. Any suggestions would be appreciated.
>
> Note that the FastE ports on the M series router do not support
> flexible-vlan-tagging. There is also no ethernet-switching fuctionality like
> in the MX series.
>
> Thanks!
> ----------
> fe-0/0/3 {
> description "VLAN Aggregation";
> vlan-tagging;
> speed 100m;
> link-mode full-duplex;
> unit 300 {
> vlan-id 300;
> family inet {
> address 10.0.0.0/24;
> }
> }
> unit 301 {
> vlan-id 301;
> family inet {
> address 10.0.1.0/24;
> }
> }
> unit 302 {
> vlan-id 302;
> family inet {
> address 10.0.2.0/24;
> }
> }
> }
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
