We are looking at creating a new VR to segregate the routing of traffic. I've setup a lab for this and have it working conceptually.
A couple of issues/questions:
1) it seems that it is very difficult to identify virtual router-specific config.
For example - if I go to the vr context ("vr newvr") and do a "show config ospf" it shows me the config of the root/default virtual router, not the newvr virtual router. This seems pretty odd given I am in the context of the VR.
To see the ospf config (and presumably other config done in the vr context), I need to run "show config detail" and trawl through hundreds and hundreds of lines of config to find the virtual router-specific config.
This is pretty terrible from a management and troubleshooting perspective.
Is there a simple way to see all config done within the context of a particular VR?
2) I've found the whole process of adding a new VR incredibly painful. By default each port, AND each VLAN is assigned to the default vr and you cannot simply change this within the config. You have to delete the port from the VR (requiring you to delete all VLANs and L2 protocols from the port and re-add them), and delete the entire VLAN, then re-add it to every single port...ridiculous when you have a lot of VLANs and ports.
It would be absolutely fine if you were creating a new switch, or adding new VLANs into a new VR, but environments and requirements change and, as is the case for us, trying to re-architect an existing switch with existing networks on EXOS is a daunting task. It seems to requiring an unnecessary level of planning, pre-prepared scripts and lots of room for human error and mistakes, potentially causing a much greater business impact.
To do the same on a more mature product such as Cisco or Juniper would be relatively simple.
Keen to hear peoples thoughts and experiences and if I am missing a trick here or not.