The issue we have is that there is no working equivalent of the IOS/JunOS commands:I still cannot se exactly why CE Devices want to know about all vrf's and routing's in MPLS cloud. It should know about it own routes, and Gateways. If running a bgp outside the MPLS, but inside the vrf, CE should still have the full Routing table that is usful to Customer, and would update the vrf With internal "own" subnets/routes. I just let CE know about the default (Routing table) via ospf (if CE should have l2VPN) and just running a bgp, without internal confederation and l3VPN at last point (PE-CE) (without default Routing table). This also make the problem about what vrf to run services to to dissappere. Its a bit annoing to not have managment to Devices, but its possible to have a link net to just have mgmt, and not run full ospf/bgp/MPLS to just do managment. Usualy my vrf's is Public IP's from different ISP's and my default via ospf, is rfc1918 for ospf/MPLS/loopback. Bgp via vpn4, l2vpn-cisco and confederation inside different AS set. All MPLS routers would have its own internal AS in the confederation and produce the non agregated table for AS set that peer With global transits.
show ip bgp vpnv4 vrf vrf-nzr-wan neighbors 172.16.95.1 advertised-routes
show ip bgp vpnv4 vrf vrf-nzr-wan neighbors 172.16.95.1 received-routes
show ip bgp vpnv4 vrf vrf-nzr-wan neighbors 172.16.95.1 routes
in RouterOS. This prevents us from seeing what prefixes we are advertising/receiving/using to/from CE routers with BGP. Most of the time we are just advertising everything in the customers VRF, but occasionally we want to block leaked management ranges from being advertised to the customers CE device, at the moment we cannot easily confirm that our filters are working correctly, or what ranges we are receiving from a peer inside a routing instance.
Yes this problem is extremely annoying, we too are still experiencing this issue. Connect a CCR to a Cisco device and set the port at 100mbit FDX, after a random period of time (from within hours, to 6 weeks) connectivity will drop completely, you check the port config on the CCR and notice it somehow now has a speed of 1gbps listed, the only fix at the moment is to reboot the CCR We had to dig a bunch of HP1800's out of retirement to sit between CCR's and Cisco devices and convert from 1gbps/AUTO to 100/FDX just so our client networks stopped dropping out.And there is other more annoing problems, like 100mb/s to Cisco, that make the CCR's freeze etc. (We had 1500 CPE Down today, couse of this problem a technican put wrong GE on a cisco to 100mb/s) (No its not fixed in 6.10, like it supposed to)