cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
280
Views
5
Helpful
2
Replies
Highlighted
Beginner

Contract - vzAny Error - F0467

Hello, 

a customer has the following problem: 

 

After configuring some contracts, he partially bound them to various EPGs as a provider and consumer. Often a contract is tied to an EPG as a provider and consumer.


The customer then found that the TCAM was almost over 90%. By using vzAny, the load could be brought back below 20%.
Now a minor error appears: F0467 - vzAny share service provider is not supported.


I'm not sure what the message means exactly. Does it mean that vzAny can only be defined as a consumer? But why is it then also possible to define a provider?
Or can vzAny not be defined as both at the same time? But only as a provider or consumer?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Collaborator

Hi @udo.konstantin 

Generally speaking, the vzAny can be both provider and consumer, however the error is referring to shared services (cross VRF). In this case:

 

  • vzAny is supported as a consumer of a shared service but is not supported as a provider of a shared service.

  • In the case of shared services, you must define the provider EPG shared subnet under the EPG in order to properly derive the pcTag (classification) of the destination from the consumer (vzAny) side. If you are migrating from a BD-to-BD shared services configuration, where both the consumer and provider subnets are defined under bridge domains, to vzAny acting as a shared service consumer, you must take an extra configuration step where you add the provider subnet to the EPG with the shared flags at minimum.

 

More details about vzAny: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/kb/b_KB_Use_vzAny_to_AutomaticallyApplyCommunicationRules_toEPGs.html 

 

Stay safe,

Sergiu

View solution in original post

2 REPLIES 2
Highlighted
Collaborator

Hi @udo.konstantin 

Generally speaking, the vzAny can be both provider and consumer, however the error is referring to shared services (cross VRF). In this case:

 

  • vzAny is supported as a consumer of a shared service but is not supported as a provider of a shared service.

  • In the case of shared services, you must define the provider EPG shared subnet under the EPG in order to properly derive the pcTag (classification) of the destination from the consumer (vzAny) side. If you are migrating from a BD-to-BD shared services configuration, where both the consumer and provider subnets are defined under bridge domains, to vzAny acting as a shared service consumer, you must take an extra configuration step where you add the provider subnet to the EPG with the shared flags at minimum.

 

More details about vzAny: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/kb/b_KB_Use_vzAny_to_AutomaticallyApplyCommunicationRules_toEPGs.html 

 

Stay safe,

Sergiu

View solution in original post

Highlighted

Hi @msdaniluk 

 

you are absolutely right. The problem is solved when we configure the contract scope as VRF. 

 

Thanks again 

Udo