Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vpwsConfigVpnId",
"OBJECT-TYPE",
"SYNTAX",
"BgpExtendedCommunity",
"MAX-ACCESS",
"read-create",
"STATUS",
"current",
"DESCRIPTION",
"\"The VPN ID to advertise as a BGP extended community, or zero if none. If the VPWS uses BGP auto-discovery and LDP signaling (vpwsConfigADType = bgp and vpwsConfigSigType = ldp) then this must be set to a valid VPN ID, otherwise it is unused and can be set to zero. If the VPWS uses BGP auto-discovery and LDP signaling then the VPN ID is used as follows. - The VPWS advertises the VPN ID as a BGP extended community attribute on all BGP L2VPN routes that it exports. - The VPWS uses the VPN ID as an import filter on all BGP L2VPN routes that it imports (in addition to Route Target import filtering). - The VPWS uses the VPN ID as the AGI value in LDP messages. Changing this value will cause an interruption to data flow for this VPWS.\"",
"DEFVAL",
"{",
"'",
"0000000000000000",
"'",
"H",
"}",
"::=",
"{",
"vpwsConfigEntry",
"15",
"}"
],
"syntax_tree": [
[
"row",
"BgpExtendedCommunity"
],
null,
[
"MaxAccessPart",
"read-create"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The VPN ID to advertise as a BGP extended community, or zero if none. If the VPWS uses BGP auto-discovery and LDP signaling (vpwsConfigADType = bgp and vpwsConfigSigType = ldp) then this must be set to a valid VPN ID, otherwise it is unused and can be set to zero. If the VPWS uses BGP auto-discovery and LDP signaling then the VPN ID is used as follows. - The VPWS advertises the VPN ID as a BGP extended community attribute on all BGP L2VPN routes that it exports. - The VPWS uses the VPN ID as an import filter on all BGP L2VPN routes that it imports (in addition to Route Target import filtering). - The VPWS uses the VPN ID as the AGI value in LDP messages. Changing this value will cause an interruption to data flow for this VPWS."
],
null,
null,
null,
[
"DEFVAL",
"'0000000000000000'H"
]
]
}