Reference record for OID 1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.16

Parent
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1 (vpwsConfigEntry)
Node code
16
Node name
vpwsConfigLocalSiteID
Numeric OID
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.16
URN notation
urn:oid:1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.16
ASN.1 notation

{1 2 826 0 1 1578918 5 94 114 4 1 1 1 1 16}

  • {iso(1) member-body(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 94 114 4 vpwsMib(1) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) member-body(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 94 114 4 vpwsMib(1) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) member-body(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 94 114 4 vpwsMib(1) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) member-body(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 94 114 4 vpwsMib(1) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) memberBody(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 94 114 4 vpwsMib(1) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) memberBody(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 94 114 4 vpwsMib(1) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 94 114 4 vpwsMib(1) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 94 114 4 vpwsMib(1) vpwsObjects(1) vpwsConfigTable(1) vpwsConfigEntry(1) vpwsConfigLocalSiteID(16)}
OID-IRI notation
  • /1/2/826/0/1/1578918/5/94/114/4/1/1/1/1/16
  • /ISO/Member-Body/GB/0/1/1578918/5/94/114/4/1/1/1/1/16
  • /ISO/Member-Body/826/0/1/1578918/5/94/114/4/1/1/1/1/16
  • /ISO/2/826/0/1/1578918/5/94/114/4/1/1/1/1/16
Named path variants
  • /iso/member-body/gb/national/eng-ltd/1578918/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/member-body/gb/national/eng-ltd/dataConnection/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/member-body/gb/national/gbNatCompany/1578918/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/member-body/gb/national/gbNatCompany/dataConnection/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/member-body/gb/gbNational/eng-ltd/1578918/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/member-body/gb/gbNational/eng-ltd/dataConnection/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/member-body/gb/gbNational/gbNatCompany/1578918/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/member-body/gb/gbNational/gbNatCompany/dataConnection/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/memberBody/gb/national/eng-ltd/1578918/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/memberBody/gb/national/eng-ltd/dataConnection/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/memberBody/gb/national/gbNatCompany/1578918/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/memberBody/gb/national/gbNatCompany/dataConnection/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/memberBody/gb/gbNational/eng-ltd/1578918/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/memberBody/gb/gbNational/eng-ltd/dataConnection/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/memberBody/gb/gbNational/gbNatCompany/1578918/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID
  • /iso/memberBody/gb/gbNational/gbNatCompany/dataConnection/5/94/114/4/vpwsMib/vpwsObjects/vpwsConfigTable/vpwsConfigEntry/vpwsConfigLocalSiteID

Descriptions

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

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.

Source records

vpwsConfigLocalSiteID

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
    ]
  ]
}
  • Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive.

    Module: DC-VPWS-MIB

    Published 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 }
    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero', 'ifIndex'], 'SNMPv2-TC': ['TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Gauge32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'DC-L2VPN-MIB': ['L2vpnPwBindType', 'L2vpnADType', 'L2vpnSigType', 'L2vpnVeIdOrZero', 'BgpRouteDistinguisher', 'BgpExtendedCommunity', 'l2vmEntityIndex'], 'DC-MASTER-TC': ['AdminStatus', 'NpgOperStatus', 'NumericIndex', 'NumericIndexOrZero'], 'IANA-PWE3-MIB': ['IANAPwTypeTC'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download DC-VPWS-MIB

    Related source files and packages:


    Source location: DC-VPWS-MIB::vpwsConfigLocalSiteID.
    Source version and references

    Downloaded: 2026-10-24T02:14:21.058227+00:00.

First Registration Authority (inferred from ancestor 1.2.826.0.1)

None (see information above)

Current Registration Authority (inferred from ancestor 1.2.826.0)

Telecoms CSC

Siblings (22)

OIDNameDirect childrenDescendantsDescription
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.2 vpwsIndex00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.3 vpwsConfigRowStatus00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.4 vpwsConfigAdminStatus00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.5 vpwsConfigOperStatus00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.6 vpwsConfigName00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.7 vpwsConfigDescr00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.8 vpwsConfigADType00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.9 vpwsConfigSigType00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.10 vpwsConfigPwEncapType00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.11 vpwsConfigMtu00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.12 vpwsConfigControlWord00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.13 vpwsConfigSeqDelivery00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.14 vpwsConfigRouteDistinguisher00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.15 vpwsConfigVpnId00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.17 vpwsConfigLocalPreference00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.18 vpwsConfigLabelBlockSize00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.19 vpwsConfigIncludeCSV00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.20 vpwsConfigIgnoreMtuMismatch00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.21 vpwsConfigIgnoreEncapsMismatch00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.22 vpwsConfigPwLocalIfParmsList00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.23 vpwsConfigPwDescr00
1.2.826.0.1.1578918.5.94.114.4.1.1.1.1.24 vpwsConfigAutoMtu00