cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
311
Views
0
Helpful
1
Replies

ExtraNet Policy and SD-Access Transit Issue

Hello everyone.

 

We have deployed an 8000v as a transit control plane node.

We, therefore, created an SDA-Transit (named IV-Transit) and successfully assigned this SDA-Transit to one of the Fabric Site without any problems.

Subsequently, we created an extranet policy (in which Infra is the Publisher VN and CORP is the Subscriber VN) and always associated it with the Fabric site.

During deployment, we received the following error: "Failed to add Extranet Policy Ext-Pol_INFRA-Pub_CORP-Sub on Fabric Site IV-Transit, as one or more devices in Fabric Site are found to be Routing platforms. Extranet Policy is not supported when Fabric Site has Routing platform."

In essence, it seems that DNAC tries to associate the Extranet Policy with the IV-Transit Fabric Site, in which, however, the 8000v resides as TCP, which DNAC recognizes as "Device Family Routers."

We don't understand why DNAC are trying to associate the extranet policy with IV-Transit, which, for us, is precisely an SD-Access (LISP Pub/sub) transit and not a Fabric Site.

 

Thanks a lot.

 

Americo

1 Reply 1

jalejand
Cisco Employee
Cisco Employee

Hi Americo

For Multi-site extranet sites connected with a transit control plane, the extranet policies are propagated using LISP extranet policies with the TCP. The TCP must be able to support this extranet capability. Only Catalyst 9000 switches currently can.

Regards

Review Cisco Networking for a $25 gift card