1) The RR will show a NoNeg state for normal IPV4 session. Assuming you have not activated the IPV4 address-family for the RR on PE1.
2) On PE1 side you will not see any neighbor when you want to see IPV4 neighbors.
3) For VPNV4 both sides agree upon and the peering happens, and they exchange VPNV4 updates.
Now, generally in a MPLS scenario, to avoid IPV4 peering, the default behaviour of BGP to form IPV4 peering is turned off on RR, and not on PE. So when ever a PE tries to peer on both IPV4 and VPNV4, all the PE's would see NoNeg state for IPV4 with the RR and VPNV4 will work as usual, and all the VPNS would be able to exchnage routes and other updates.
If you want to have IPV4 peering also, on a per neighbor basis, what you can do is where you have turned off default IPV4 peering, in that address-family you will have to specifically activate the neighbor for IPV4 as well. For Example: you have turned off IPV4 peering on PE1, so you will have to enter IPV4 address-family on PE1 and activate the RR neighbor IP. so they exahnge IPV4 and VPNV4.
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...