Author Topic: vme.0 on dedicated routing instance  (Read 4666 times)


  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
vme.0 on dedicated routing instance
« on: November 24, 2009, 01:20:20 am »
I fear this may not be possible, but I have to ask anyway: on an EX4200 virtual chassis, is it possible to assign the vme.0 interface to a separate routing-instance so that it can be configured with a routing table of its own? This is what I get when I try it:

Code: [Select]
theuser@theswitch# show routing-instances
test {
    interface vme.0;

theuser@theswitch# commit check
[edit routing-instances test]
  'interface vme.0'
    RT Instance: Interface vme.0 not supported under routing-instances.
error: configuration check-out failed

My EX4200 virtual chassis is doing routing decisions inside a datacentre, and it gets a bunch of WAN routes pointing in all directions via OSPF. I would line to force my management interface to have only a default route, and any suggestions will be appreciated.


  • Newbie
  • *
  • Posts: 47
  • Karma: +0/-0
    • View Profile
Re: vme.0 on dedicated routing instance
« Reply #1 on: December 20, 2009, 07:23:48 pm »
No this is not supported in Junos. You need a completely separate routing infrastructure to make it completely autonomous.