Hi guys,
In a bit of a bind here, what's the recommended way to configure in-band
strictly management interface over a trunk port on the EX2200?
I've been trying various formations of the following -- but it doesn't
even register an arp entry on the l3 router.
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.
At its current state, the RVI virtual interface refuses to even go
online, presumably because of the lack of a member interface in
vlan-137. However, I don't want to route anything over this -- so I
don't have anything to assign as an 'interface' here.
Any pointers would be appreciated.
## Last commit: 2013-10-29 19:59:12 UTC by root
version 11.4R5.5;
chassis {
aggregated-devices {
ethernet {
device-count 1;
}
}
}
interfaces {
ge-0/0/0 {
ether-options {
802.3ad ae0;
}
}
ge-0/0/1 {
ether-options {
802.3ad ae0;
}
}
ge-0/0/3 {
unit 0 {
family ethernet-switching;
}
}
ae0 {
aggregated-ether-options {
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members all;
}
native-vlan-id vlan-137;
}
}
}
vlan {
unit 137 {
family inet {
address 10.1.12.46/29;
}
}
}
}
routing-options {
static {
route 0.0.0.0/0 next-hop 10.1.12.41;
}
}
vlans {
vlan-137 {
vlan-id 137;
l3-interface vlan.137;
}
}
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
