Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"l2vmBgpRTCfgTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"L2vmBgpRTCfgEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"L2VPN BGP Route Target Config Table. This table specifies the Route Targets that are imported and exported during BGP auto-discovery. In BGP auto-discovery each L2VPN instance advertises itself by originating a BGP L2VPN route and discovers other L2VPN instances by importing their BGP L2VPN routes. The Route Target configuration controls which L2VPN instances import which BGP L2VPN routes, and so determines which L2VPN instances discover each other and establish pseudowires. - When an L2VPN instance originates a BGP L2VPN route it includes its export Route Targets as extended community attributes in the BGP L2VPN route. - When an L2VPN instance receives a BGP L2VPN route it only imports the route if one of its import Route Targets matches the received route. - The result is that two L2VPN instances only discover each other if each exports a Route Target that the other imports. Each L2VPN instance that uses BGP auto-discovery must be configured with at least one Route Target, otherwise it will never discover other L2VPN instances (no import Route Target) and never be discovered by other L2VPN instances (no export Route Target). The simplest configuration is for each L2VPN instance to import and export a single Route Target that is unique to the L2VPN that it belongs to. This MIB table corresponds to vplsBgpRteTargetTable in draft-ietf-l2vpn-vpls-mib-10, and is also used for configuration of BGP Route Targets for VPWS instances that are provisioned using the colored-pools method.\"",
"::=",
"{",
"l2vpnObjects",
"4",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"L2vmBgpRTCfgEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"L2VPN BGP Route Target Config Table. This table specifies the Route Targets that are imported and exported during BGP auto-discovery. In BGP auto-discovery each L2VPN instance advertises itself by originating a BGP L2VPN route and discovers other L2VPN instances by importing their BGP L2VPN routes. The Route Target configuration controls which L2VPN instances import which BGP L2VPN routes, and so determines which L2VPN instances discover each other and establish pseudowires. - When an L2VPN instance originates a BGP L2VPN route it includes its export Route Targets as extended community attributes in the BGP L2VPN route. - When an L2VPN instance receives a BGP L2VPN route it only imports the route if one of its import Route Targets matches the received route. - The result is that two L2VPN instances only discover each other if each exports a Route Target that the other imports. Each L2VPN instance that uses BGP auto-discovery must be configured with at least one Route Target, otherwise it will never discover other L2VPN instances (no import Route Target) and never be discovered by other L2VPN instances (no export Route Target). The simplest configuration is for each L2VPN instance to import and export a single Route Target that is unique to the L2VPN that it belongs to. This MIB table corresponds to vplsBgpRteTargetTable in draft-ietf-l2vpn-vpls-mib-10, and is also used for configuration of BGP Route Targets for VPWS instances that are provisioned using the colored-pools method."
],
null,
null,
null,
null
]
}