From your VRF configuration, NMS will import RT of xxxx:162 (note that you have two xxxx:162, I wonder if that is a typo). Test10 will import xxxx:10 and xxxx:161. Since 10.161.1.0/24 route is in the NMS and not in Test10, I will assume that it is tagged with xxxx:162, and not with either xxxx:10 or xxxx:161.
The key thing to note is that your export map configuration in the vrf does not affect routes that have been recieved from another PE. It has effect for the routes locally originated on the PE. Hence, the 10.161.0.0/24 route will be affected by export maps.
You can try show ip bgp vpnv4 all 10.161.1.0 to see the RTs associated with the route.
Ok - So if I have the monitoring servers (VRF NMS 10.161.1.0/24) directly connected to a different PE to the VRF TEST10 connections, is there anyway to monitor TEST10 CE's from the 10.161.1.0/24 range?(i.e. Inject the 10.161.1.0/24 range into vrf TEST10, and the CE's Loop addresses into vrf NMS)?
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...