`tenant.l3out.node_profile.node_attachment`¶

A static association with each leaf node that is part of the node profile. The corresponding set of policies will be resolved into the specified node. This object must contain a router ID that will be used as the OSPF/BGP router ID.


ACI class	`l3extRsNodeL3OutAtt`
RN	`rsnodeL3OutAtt-[{target_dn}]`
Cursor	`NodeAttachmentCursor`
Parent	tenant.l3out.node_profile
Atomic	—

Attributes¶

Accepted as keyword arguments of .node_attachment(target_dn) and of .set(**attrs) on this cursor. Enum parameters also accept the plain string.

parameter	wire	type	values	default	description
`target_dn` (positional)	`tDn`	`str`	—	—	The distinguished name for the node attached to the layer 3 outside profile. The maximum supported string length is 255 ASCII characters.
`config_issues`	`configIssues`	L3extConfigIssues	`none`, `node-path-misconfig`, `routerid-not-changable-with-mcast`, `loopback-ip-missing`, `subnet-mismatch`, `node-vlif-misconfig`, `anchor-node-mismatch`, `missing-rs-export-route-profile`, `missing-mpls-infra-l3out`, `bd-profile-mismatch`, `mtu-mac-mismatch`, `anchor-encap-mismatch`, `access-encap-node-overlap`, `access-encap-bd-map-conflict`, `rtsumsubnet-l3extsubnet-conflict`	`none`	Bitmask representation of the configuration issues found during the endpoint group deployment.
`rtr_id`	`rtrId`	`str`	—	—	The router identifier used as the OSPF/BGP router ID.
`rtr_id_loop_back`	`rtrIdLoopBack`	`bool`	—	`True`	—

Children¶

maker	creates	position
`.static_route(match_ip_address, **attrs)`	`ipRouteP`	tenant.l3out.node_profile.node_attachment.static_route
`.infra_node(**attrs)`	`l3extInfraNodeP`	tenant.l3out.node_profile.node_attachment.infra_node
`.loopback(loop_back_interface_address, **attrs)`	`l3extLoopBackIfP`	tenant.l3out.node_profile.node_attachment.loopback
`.node_sid_profile(srgb_index, **attrs)`	`mplsNodeSidP`	tenant.l3out.node_profile.node_attachment.node_sid_profile

APIC diagnostics¶

States the APIC can flag on this class — it accepts the configuration and reports the inconsistency afterwards.

Config issues

code	meaning
`access-encap-bd-map-conflict`	Conflicting access-encap to BD mapping
`access-encap-node-overlap`	Access encap node overlap
`anchor-encap-mismatch`	Anchor node encap mismatch
`anchor-node-mismatch`	v4 and v4 anchor node sets are not matching
`bd-profile-mismatch`	External bridge profile mismatch
`loopback-ip-missing`	CP-TEP configuration validations
`missing-mpls-infra-l3out`	MPLS infra l3out validation for the consumer Lbl
`missing-rs-export-route-profile`	MPLS ConsLbl configuration validations
`mtu-mac-mismatch`	Fault added via CSCvv00759 for identical l3extRsPathL3OutAtt
`node-path-misconfig`	LNodeP node/path configuration validations
`node-vlif-misconfig`	LNodeP node/vlif configuration validations
`routerid-not-changable-with-mcast`	LNodeP router id multicast configuration validations
`rtsumsubnet-l3extsubnet-conflict`	fvRtSummSubnet and l3extSubnet has same prefix
`subnet-mismatch`	Primary IP and floating ip are not in same subnet