This requirement is not applicable for the DODIN Backbone. Review the network topology diagram to determine connectivity between the managed network and the NOC. Review the OOBM gateway router configuration to validate the path and interface that the management traffic traverses. MPLS-based VPN (L2 or L3) must have a working provider MPLS network including routing (for reachability) and Label Switched Paths (LSP). Additionally, the PE router will maintain separation for each CE router in individual routing instances. If using a dedicated circuit, verify the interface transporting NOC traffic is properly connected. CE routers will not peer with PE routers when using L2 VPN. Verify the CE router peers with the appropriate CE router, generally with an IGP (e.g., OSPF), and not the PE router. [edit interfaces] <exterior interface> { unit <number> { family inet { address <IPv4 address>/<mask>; } } } lo0 { unit 0 { family inet { address <IPv4 address>/32; } } } [edit protocols ospf] area <number> { interface lo0.0; interface <exterior interface>.<number>; } CE routers will peer with PE routers, generally with eBGP, when using L3 VPN. Verify the CE router advertises the appropriate interior networks to the PE. [edit interfaces] <exterior interface>:0 { unit <number> { family inet { address <IPv4 address>/<mask>; } } } lo0 { family inet { address <IPv4 address>/<mask>; } } [edit routing-options] router-id <ID>; autonomous-system <AS #>; [edit protocols bgp] group PE1 { type external; export <policy name>; peer-as <peer AS #>; neighbor <neighbor address>; << Reachable from the exterior interface } [edit policy-options policy-statement <statement name>] term 1 { from { protocol <protocol>; << Include the appropriate protocol (e.g., 'direct' for directly connected routes) route-filter <subnet>/<mask> <match condition>; << Include only interior routes that must be advertised to the L3 VPN } then accept; } Note: The policy-statement is applied as an export filter, using a route-filter to limit the exported routes. For example, assume 192.0.2.0/24 is the advertised route, and that it is directly connected. Using "protocol direct" will export all directly-connected routes, but no routes learned via an IGP (e.g., OSPF). Using "route-filter 192.0.2.0/24 orlonger then accept" will accept that /24 (or longer mask) and deny all others. Verify the match condition is appropriate for the desired advertisement. If management traffic is not transported between the managed network and the NOC via dedicated circuit, MPLS/VPN service, or IPsec tunnel, this is a finding.