|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
vns:LDevInst The local state in the object that reuses encaps across graphs with the same subnet. This is an internal object. |
|
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
vns:LDevInst The local state in the object that reuses encaps across graphs with the same subnet. This is an internal object. |
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
vns:LDevInst The local state in the object that reuses encaps across graphs with the same subnet. This is an internal object. |
|
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
vns:LDevInst The local state in the object that reuses encaps across graphs with the same subnet. This is an internal object. |
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
vns:LDevInst The local state in the object that reuses encaps across graphs with the same subnet. This is an internal object. |
|
|
|
|
|
|
|
|
├
|
|
vns:EPpInfo Internal object to store encap info (vlan ID) for an endpoint. |
|
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
vns:LDevInst The local state in the object that reuses encaps across graphs with the same subnet. This is an internal object. |
|
|
|
├
|
|
vns:EPpInfo Internal object to store encap info (vlan ID) for an endpoint. |
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
vns:VDev A collection of groups that can share parts of their configuration. This object is implicit. |
|
|
|
|
|
|
|
├
|
|
vns:RndrInfo An internal object that stores rendered graph information. |
|
|
|
|
|
|
|
|
├
|
|
vns:EPpContr A container to hold endpoint profile objects. |
|
|
|
|
|
|
|
|
|
├
|
|
vns:EPpInfo Internal object to store encap info (vlan ID) for an endpoint. |
|
|
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
vns:VDev A collection of groups that can share parts of their configuration. This object is implicit. |
|
|
├
|
|
vns:RndrInfo An internal object that stores rendered graph information. |
|
|
|
├
|
|
vns:EPpContr A container to hold endpoint profile objects. |
|
|
|
|
├
|
|
vns:EPpInfo Internal object to store encap info (vlan ID) for an endpoint. |
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
vns:LDevCtx A device cluster context points to the device cluster used to pick a specific device based on contract, subject, and function label or names. To specify a wild card, set the name to Any. |
|
|
|
|
|
|
|
|
├
|
|
vns:LIfCtx The logical interface context points to the logical interface used to pick a specific logical interface based on the connector name. To specify a wild card, set the name to Any. |
|
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
vns:LDevCtx A device cluster context points to the device cluster used to pick a specific device based on contract, subject, and function label or names. To specify a wild card, set the name to Any. |
|
|
|
├
|
|
vns:LIfCtx The logical interface context points to the logical interface used to pick a specific logical interface based on the connector name. To specify a wild card, set the name to Any. |
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
mgmt:MgmtP The in-band and out-of-band management endpoint groups consists of switches (leaves/spines) and APICs.
Each node in the group is assigned an IP address that is dynamically allocated from the address pool associated with the corresponding
in-band or out-of-band management zone. |
|
|
|
|
|
|
|
|
├
|
|
mgmt:InB The in-band management endpoint group consists of switches (leaves/spines) and APICs.
Each node in the group is assigned an IP address that is dynamically allocated from the address pool associated with the corresponding
in-band management zone. The allocated IP address is then configured as the in-band management access IP address on the corresponding node.
Any host that is part of another endpoint group can communicate with the nodes in the... |
|
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
mgmt:MgmtP The in-band and out-of-band management endpoint groups consists of switches (leaves/spines) and APICs.
Each node in the group is assigned an IP address that is dynamically allocated from the address pool associated with the corresponding
in-band or out-of-band management zone. |
|
|
|
├
|
|
mgmt:InB The in-band management endpoint group consists of switches (leaves/spines) and APICs.
Each node in the group is assigned an IP address that is dynamically allocated from the address pool associated with the corresponding
in-band management zone. The allocated IP address is then configured as the in-band management access IP address on the corresponding node.
Any host that is part of another endpoint group can communicate with the nodes in the... |
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
fv:Ap The application profile is a set of requirements that an application instance has on the virtualizable fabric. The policy regulates connectivity and visibility among endpoints within the scope of the policy. |
|
|
|
|
|
|
|
|
├
|
|
fv:AEPg A set of requirements for the application-level EPG instance. The policy regulates connectivity and visibility among the end points within the scope of the policy. |
|
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
fv:Ap The application profile is a set of requirements that an application instance has on the virtualizable fabric. The policy regulates connectivity and visibility among endpoints within the scope of the policy. |
|
|
|
├
|
|
fv:AEPg A set of requirements for the application-level EPG instance. The policy regulates connectivity and visibility among the end points within the scope of the policy. |
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
fv:BD A bridge domain is a unique layer 2 forwarding domain that contains one or more subnets. Each bridge domain must be linked to a context. |
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
fv:BD A bridge domain is a unique layer 2 forwarding domain that contains one or more subnets. Each bridge domain must be linked to a context. |
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
fv:ABDPol Abstract representation of a bridge domain policy. |
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
fv:ABDPol Abstract representation of a bridge domain policy. |
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
|
|
|
|
|
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
|
|
|
|
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
|
|
|
|
|
├
|
|
l2ext:Out The L2 outside policy controls connectivity to the outside. |
|
|
|
|
|
|
|
|
├
|
|
l2ext:InstP The external network instance profile represents a group of external
subnets that have the same security behavior. These subnets inherit contract profiles
applied to the parent instance profile. Each subnet can also associate to route
control profiles, which defines the routing behavior for that subnet. |
|
|
|
|
|
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|
top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
|
pol:Uni Represents policy definition/resolution universe. |
|
├
|
|
fv:Tenant A policy owner in the virtual fabric. A tenant can be either a private or a shared entity. For example, you can create a tenant with contexts and bridge domains shared by other tenants. A shared type of tenant is typically named common, default, or infra. |
|
|
├
|
|
l2ext:Out The L2 outside policy controls connectivity to the outside. |
|
|
|
├
|
|
l2ext:InstP The external network instance profile represents a group of external
subnets that have the same security behavior. These subnets inherit contract profiles
applied to the parent instance profile. Each subnet can also associate to route
control profiles, which defines the routing behavior for that subnet. |
|
|
|
|
├
|
|
fv:Subnet A subnet defines the IP address range that can be used within the bridge domain. While a context defines a unique layer 3 space, that space can consist of multiple subnets. These subnets are defined per bridge domain. A bridge domain can contain multiple subnets, but a subnet is contained within a single bridge domain. |
|
|
|
|
|
├
|
|
fv:RsNdPfxPol The neighbor discovery prefix policy. |
|