OID reference

vpwsConfigLocalSiteID

1.3.6.1.4.1.629.10.19.1.1.1.16

Description

The local VPWS site ID, or zero if not specified. This is only used if BGP auto-discovery is enabled (vpwsConfigADType = bgp). It can be used with BGP or LDP signaling. If auto-discovery is enabled then the VPWS service establishes a pseudowire (PW) between each pair of VPWS sites within a VPWS. The valid range for VP…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.629.10.19.1.1.1 (vpwsConfigEntry)
Node code
16
Node name
vpwsConfigLocalSiteID
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.629.10.19.1.1.1.16
URN notation
urn:oid:1.3.6.1.4.1.629.10.19.1.1.1.16
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 629 10 19 1 1 1 16}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbase(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nbs(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbase(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nbs(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbase(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nbs(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbase(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nbs(629) opx(10) vpwsMib(19) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/629/10/19/1/1/1/16
  • /ISO/Identified-Organization/6/1/4/1/629/10/19/1/1/1/16
  • /ISO/3/6/1/4/1/629/10/19/1/1/1/16
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/nbase/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/identified-organization/dod/internet/private/enterprise/nbs/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/identified-organization/dod/internet/private/enterprises/nbase/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/identified-organization/dod/internet/private/enterprises/nbs/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbase/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nbs/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbase/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/identified-organization/dod/internet/private/vendor-objects/nbs/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/org/dod/internet/private/enterprise/nbase/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/org/dod/internet/private/enterprise/nbs/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/org/dod/internet/private/enterprises/nbase/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/org/dod/internet/private/enterprises/nbs/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/org/dod/internet/private/ldap-enterprise/nbase/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/org/dod/internet/private/ldap-enterprise/nbs/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/org/dod/internet/private/vendor-objects/nbase/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/org/dod/internet/private/vendor-objects/nbs/opx/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • Additional combinations skipped.

SNMP properties

Value type
L2vpnVeIdOrZero
Maximum access defined by MIB
read-create
Status in MIB
current
Default value
0

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

vpwsConfigLocalSiteID OBJECT-TYPE
    SYNTAX      L2vpnVeIdOrZero
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION "The local VPWS site ID, or zero if not specified.

                 This is only used if BGP auto-discovery is enabled
                 (vpwsConfigADType = bgp).  It can be used with BGP or LDP
                 signaling.

                 If auto-discovery is enabled then the VPWS service
                 establishes a pseudowire (PW) between each pair of VPWS
                 sites within a VPWS.

                 The valid range for VPWS site IDs depends on whether
                 LDP or BGP signaling is used.
                 -  For LDP signaling (vpwsConfigSigType = ldp) the valid
                 range is 1-4294967295 (4 bytes).
                 -  For BGP signaling (vpwsConfigSigType = bgp) the valid
                 range is 1-65535 (2 bytes).

                 The use of the VPWS site ID in auto-discovery and
                 signaling also depends on whether LDP or BGP signaling
                 is used.
                 -  For BGP auto-discovery with LDP signaling the VPWS site
                 ID is advertised in the 4-byte 'PE_addr' field in the
                 BGP NLRI specified in [RFC 6074].  It is also used as
                 the local SAII/TAII value in LDP messages.
                 -  For BGP auto-discovery with BGP signaling the VPWS site
                 ID is advertised in the 2-byte 'VE ID' field in the
                 BGP NLRI specified in [RFC 4761].

                 Changing this value will cause an interruption to data
                 flow for this VPWS."
    DEFVAL      { 0 }
    ::= { vpwsConfigEntry 16 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The local VPWS site ID, or zero if not specified. This is only used if BGP auto-discovery is enabled (vpwsConfigADType = bgp). It can be used with BGP or LDP signaling. If auto-discovery is enabled then the VPWS service establishes a pseudowire (PW) between each pair of VPWS sites within a VPWS. The valid range for VPWS site IDs depends on whether LDP or BGP signaling is used. - For LDP signaling (vpwsConfigSigType = ldp) the valid range is 1-4294967295 (4 bytes). - For BGP signaling (vpwsConfigSigType = bgp) the valid range is 1-65535 (2 bytes). The use of the VPWS site ID in auto-discovery and signaling also depends on whether LDP or BGP signaling is used. - For BGP auto-discovery with LDP signaling the VPWS site ID is advertised in the 4-byte 'PE_addr' field in the BGP NLRI specified in [RFC 6074]. It is also used as the local SAII/TAII value in LDP messages. - For BGP auto-discovery with BGP signaling the VPWS site ID is advertised in the 2-byte 'VE ID' field in the BGP NLRI specified in [RFC 4761]. Changing this value will cause an interruption to data flow for this VPWS.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

vpwsConfigLocalSiteID · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: vpwsConfigLocalSiteID

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "vpwsConfigLocalSiteID",
    "OBJECT-TYPE",
    "SYNTAX",
    "L2vpnVeIdOrZero",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The local VPWS site ID, or zero if not specified. This is only used if BGP auto-discovery is enabled (vpwsConfigADType = bgp). It can be used with BGP or LDP signaling. If auto-discovery is enabled then the VPWS service establishes a pseudowire (PW) between each pair of VPWS sites within a VPWS. The valid range for VPWS site IDs depends on whether LDP or BGP signaling is used. - For LDP signaling (vpwsConfigSigType = ldp) the valid range is 1-4294967295 (4 bytes). - For BGP signaling (vpwsConfigSigType = bgp) the valid range is 1-65535 (2 bytes). The use of the VPWS site ID in auto-discovery and signaling also depends on whether LDP or BGP signaling is used. - For BGP auto-discovery with LDP signaling the VPWS site ID is advertised in the 4-byte 'PE_addr' field in the BGP NLRI specified in [RFC 6074]. It is also used as the local SAII/TAII value in LDP messages. - For BGP auto-discovery with BGP signaling the VPWS site ID is advertised in the 2-byte 'VE ID' field in the BGP NLRI specified in [RFC 4761]. Changing this value will cause an interruption to data flow for this VPWS.\"",
    "DEFVAL",
    "{",
    "0",
    "}",
    "::=",
    "{",
    "vpwsConfigEntry",
    "16",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "L2vpnVeIdOrZero"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The local VPWS site ID, or zero if not specified. This is only used if BGP auto-discovery is enabled (vpwsConfigADType = bgp). It can be used with BGP or LDP signaling. If auto-discovery is enabled then the VPWS service establishes a pseudowire (PW) between each pair of VPWS sites within a VPWS. The valid range for VPWS site IDs depends on whether LDP or BGP signaling is used. - For LDP signaling (vpwsConfigSigType = ldp) the valid range is 1-4294967295 (4 bytes). - For BGP signaling (vpwsConfigSigType = bgp) the valid range is 1-65535 (2 bytes). The use of the VPWS site ID in auto-discovery and signaling also depends on whether LDP or BGP signaling is used. - For BGP auto-discovery with LDP signaling the VPWS site ID is advertised in the 4-byte 'PE_addr' field in the BGP NLRI specified in [RFC 6074]. It is also used as the local SAII/TAII value in LDP messages. - For BGP auto-discovery with BGP signaling the VPWS site ID is advertised in the 2-byte 'VE ID' field in the BGP NLRI specified in [RFC 4761]. Changing this value will cause an interruption to data flow for this VPWS."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      0
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.629)

Rotenstein Sergiu

Siblings (19)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.629.10.19.1.1.1.2 vpwsIndex00
1.3.6.1.4.1.629.10.19.1.1.1.3 vpwsConfigRowStatus00
1.3.6.1.4.1.629.10.19.1.1.1.4 vpwsConfigAdminStatus00
1.3.6.1.4.1.629.10.19.1.1.1.5 vpwsConfigOperStatus00
1.3.6.1.4.1.629.10.19.1.1.1.6 vpwsConfigName00
1.3.6.1.4.1.629.10.19.1.1.1.7 vpwsConfigDescr00
1.3.6.1.4.1.629.10.19.1.1.1.8 vpwsConfigADType00
1.3.6.1.4.1.629.10.19.1.1.1.9 vpwsConfigSigType00
1.3.6.1.4.1.629.10.19.1.1.1.10 vpwsConfigPwEncapType00
1.3.6.1.4.1.629.10.19.1.1.1.11 vpwsConfigMtu00
1.3.6.1.4.1.629.10.19.1.1.1.12 vpwsConfigControlWord00
1.3.6.1.4.1.629.10.19.1.1.1.13 vpwsConfigSeqDelivery00
1.3.6.1.4.1.629.10.19.1.1.1.14 vpwsConfigRouteDistinguisher00
1.3.6.1.4.1.629.10.19.1.1.1.15 vpwsConfigVpnId00
1.3.6.1.4.1.629.10.19.1.1.1.17 vpwsConfigLocalPreference00
1.3.6.1.4.1.629.10.19.1.1.1.18 vpwsConfigLabelBlockSize00
1.3.6.1.4.1.629.10.19.1.1.1.19 vpwsConfigIncludeCSV00
1.3.6.1.4.1.629.10.19.1.1.1.20 vpwsConfigIgnoreMtuMismatch00
1.3.6.1.4.1.629.10.19.1.1.1.21 vpwsConfigIgnoreEncapsMismatch00