NSO 5.7 M4 FRR enable resulting error: Hi Sahiti, Van,We have NSO 5.X + M4 CFP on one set upAfter service with RSVP TE tunnel was created, we wanted to enable FRR stateIt have following errorXR team had mentioned in past that PCE delegation should be removed from tunnelSo we did that and did Device->NSO sync as well.But still the Flex UI giving following errorCan someone help? Here is testbed details and tunnel between AA-NCS5501-1 and AA-NCS5501-2I have opened JIRA as wellThx,Vaishali 
Hi Vaisali, Sorry I don't get your issue. Can you provide your service payload? Is FRR option available from CFP? Is this feature working in previous release?What is error message that you saw in NSO?Thanks,Linh1) yes FRR support is added in CFP M2 itself2) Service payload is like this which created similar tunnel 221<data xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf">  <te xmlns="urn:ietf:params:xml:ns:yang:ietf-te"xmlns:y="http://tail-f.com/ns/rest"xmlns:te="urn:ietf:params:xml:ns:yang:ietf-te" xmlns:te-types="urn:ietf:params:xml:ns:yang:ietf-te-types">    <tunnels xmlns="urn:ietf:params:xml:ns:yang:ietf-te" xmlns:te="urn:ietf:params:xml:ns:yang:ietf-te">      <tunnel>        <name>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-1-221</name>        <identifier>221</identifier>        <description>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-1-221</description>        <head-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">AA-NCS5501-1</head-end>        <tail-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">AA-NCS5501-3</tail-end>        <source>100.100.100.2</source>        <destination>100.100.100.6</destination>        <signaling-type>te-types:path-setup-rsvp</signaling-type>        <primary-paths>          <primary-path>            <name>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-1-221</name>            <path-computation-method xmlns:te-types="urn:ietf:params:xml:ns:yang:ietf-te-types">te-types:path-externally-queried</path-computation-method>            <optimizations>              <optimization-metric>                <metric-type>te-types:path-metric-igp</metric-type>              </optimization-metric>            </optimizations>            <preference>1</preference>          </primary-path>        </primary-paths>      </tunnel>      <tunnel>        <name>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221</name>        <identifier>221</identifier>        <description>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221</description>        <head-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">AA-NCS5501-3</head-end>        <tail-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">AA-NCS5501-1</tail-end>        <source>100.100.100.6</source>        <destination>100.100.100.2</destination>        <signaling-type>te-types:path-setup-rsvp</signaling-type>        <primary-paths>          <primary-path>            <name>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221</name>            <path-computation-method xmlns:te-types="urn:ietf:params:xml:ns:yang:ietf-te-types">te-types:path-externally-queried</path-computation-method>            <optimizations>              <optimization-metric>                <metric-type>te-types:path-metric-igp</metric-type>              </optimization-metric>            </optimizations>            <preference>1</preference>          </primary-path>        </primary-paths>      </tunnel>    </tunnels>  </te>  <l2vpn-ntw xmlns="urn:ietf:params:xml:ns:yang:ietf-l2vpn-ntw">    <vpn-services>      <vpn-service>        <vpn-id>L2VPN_NM_P2P_RSVPTE-221</vpn-id>        <vpn-type>vpn-common:vpws</vpn-type>        <vpn-nodes>          <vpn-node>            <vpn-node-id>AA-NCS5501-3</vpn-node-id>            <te-service-mapping xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">              <te-mapping>                <te-tunnel-list>                  <ietf-te-service>L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221</ietf-te-service>                  <fallback>disable</fallback>                </te-tunnel-list>              </te-mapping>            </te-service-mapping>            <signaling-option>              <ldp-or-l2tp>                <pw-peer-list>                  <peer-addr>100.100.100.2</peer-addr>                  <vc-id>221</vc-id>                  <mpls-label xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">221</mpls-label>                </pw-peer-list>              </ldp-or-l2tp>            </signaling-option>            <vpn-network-accesses>              <vpn-network-access>                <id>221</id>                <interface-id>GigabitEthernet0/0/0/0</interface-id>                <connection>                  <encapsulation>                    <encap-type>vpn-common:dot1q</encap-type>                    <dot1q>                      <cvlan-id>221</cvlan-id>                    </dot1q>                  </encapsulation>                </connection>              </vpn-network-access>            </vpn-network-accesses>          </vpn-node>          <vpn-node>            <vpn-node-id>AA-NCS5501-1</vpn-node-id>            <te-service-mapping xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">              <te-mapping>                <te-tunnel-list>                  <te-tunnel-id>221</te-tunnel-id>                </te-tunnel-list>              </te-mapping>            </te-service-mapping>            <signaling-option>              <ldp-or-l2tp>                <pw-peer-list>                  <peer-addr>100.100.100.6</peer-addr>                  <vc-id>221</vc-id>                  <mpls-label xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">221</mpls-label>                </pw-peer-list>              </ldp-or-l2tp>            </signaling-option>            <vpn-network-accesses>              <vpn-network-access>                <id>1</id>                <interface-id>GigabitEthernet0/0/0/0</interface-id>                <connection>                  <encapsulation>                    <encap-type>vpn-common:dot1q</encap-type>                    <dot1q>                      <cvlan-id>221</cvlan-id>                    </dot1q>                  </encapsulation>                </connection>              </vpn-network-access>            </vpn-network-accesses>          </vpn-node>        </vpn-nodes>      </vpn-service>    </vpn-services>  </l2vpn-ntw></data> Hi Vaisali,I applied your payloads to my setup. They are working fine l2vpn xconnect and te-tunnel 221 are up.RP/0/RSP0/CPU0:PE3#show l2vpn xconnect group L2VPN_NM_P2P_RSVPTE-221Thu Dec 8 18:43:17.189 UTCLegend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,    SB = Standby, SR = Standby Ready, (PP) = Partially Programmed,    LU = Local Up, RU = Remote Up, CO = Connected, (SI) = Seamless InactiveXConnect          Segment 1            Segment 2        Group   Name    ST  Description      ST    Description      ST  ------------------------  -----------------------------  -----------------------------L2VPN_NM_P2P_RSVPTE-221      L2VPN_NM_P2P_RSVPTE-221           UP  Hu0/0/0/4.221     UP    100.100.100.6  221  UP  ----------------------------------------------------------------------------------------RP/0/RSP0/CPU0:PE3#show mpls traffic-eng tunnels name L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221Thu Dec 8 18:38:44.494 UTCLSP Tunnel 100.100.100.6 221 is signalled, Signaling State: up Tunnel Name: L2VPN_NM-P2P-RSVPTE-AA-NCS5501-3-221 Tunnel Role: Tail InLabel: HundredGigE0/0/0/0, implicit-null Signalling Info:  Src 100.100.100.6 Dst 100.100.100.5, Tun ID 221, Tun Inst 3, Ext ID 100.100.100.6  Router-IDs: upstream  100.100.100.1        local   100.100.100.5  Bandwidth: 0 kbps (CT0) Priority: 7 7 DSTE-class: 0  Soft Preemption: None  SRLGs: not collected  Path Info:   Incoming Address: 10.10.10.10   Incoming:   Explicit Route:    Strict, 10.10.10.10    Strict, 100.100.100.5   Record Route: Disabled   Tspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbits   Session Attributes: Local Prot: Not Set, Node Prot: Not Set, BW Prot: Not Set             Soft Preemption Desired: Not Set  Resv Info: None   Record Route: Disabled   Fspec: avg rate=0 kbits, burst=1000 bytes, peak rate=0 kbitsDisplayed 0 (of 2) heads, 0 (of 0) midpoints, 1 (of 1) tailsDisplayed 0 up, 0 down, 0 recovering, 0 recovered headsI am not sure these are operation status that you looked at. Please let me knowRegards,LinhThere is no update from subimitter. I am going to close the ticketRegards,Linh