Mark,
It was the native-vlan-id, actually.
Removing it made it all start working.
Thank you!
On 2/28/2014 午後 07:58, Mark Tinka wrote:
On Friday, February 28, 2014 12:31:00 PM Paul S. wrote:
However, if I move the unit 137 stanza from vlan.137
directly to ae0 (Removing its trunk status in the
process), and config it with vlan-tagging, and vlan-id
137 -- it becomes accessible just fine, and can route
traffic.
On my EX4550's (and EX3200/4200's), the below works:
ae0 {
description "SOMETHING";
aggregated-ether-options {
link-speed 10g;
lacp {
passive;
}
}
unit 0 {
description "SOMETHING";
bandwidth 20g;
family ethernet-switching {
port-mode trunk;
vlan {
members all;
}
}
}
}
vlan {
unit 999 {
description "SOMETHING - Management VLAN";
bandwidth 20g;
family inet {
filter {
input filter-incoming;
output filter-outgoing;
}
address a.b.c.d/30;
}
family iso;
family inet6 {
filter {
input filter-incoming6;
inactive: output filter-outgoing6;
}
address aaaa:bbbb:c:d::e/126;
}
}
}
vlans {
Edge-Network {
vlan-id 999;
l3-interface vlan.999;
}
}
Hope this helps.
Mark.
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
