Reference record for OID 1.2.826.0.1.1578918.5.35.1.1.2.1.24

Parent
1.2.826.0.1.1578918.5.35.1.1.2.1 (dccrldpPmEntry)
Node code
24
Node name
dccrldpPmPolicySupportFlags
Numeric OID
1.2.826.0.1.1578918.5.35.1.1.2.1.24
URN notation
urn:oid:1.2.826.0.1.1578918.5.35.1.1.2.1.24
ASN.1 notation

{1 2 826 0 1 1578918 5 35 1 1 2 1 24}

  • {iso(1) member-body(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 35 dccrldp(1) dccrldpObjects(1) dccrldpPmTable(2) dccrldpPmEntry(1) dccrldpPmPolicySupportFlags(24)}
  • {iso(1) member-body(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 35 dccrldp(1) dccrldpObjects(1) dccrldpPmTable(2) dccrldpPmEntry(1) dccrldpPmPolicySupportFlags(24)}
  • {iso(1) member-body(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 35 dccrldp(1) dccrldpObjects(1) dccrldpPmTable(2) dccrldpPmEntry(1) dccrldpPmPolicySupportFlags(24)}
  • {iso(1) member-body(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 35 dccrldp(1) dccrldpObjects(1) dccrldpPmTable(2) dccrldpPmEntry(1) dccrldpPmPolicySupportFlags(24)}
  • {iso(1) memberBody(2) gb(826) national(0) eng-ltd(1) dataConnection(1578918) 5 35 dccrldp(1) dccrldpObjects(1) dccrldpPmTable(2) dccrldpPmEntry(1) dccrldpPmPolicySupportFlags(24)}
  • {iso(1) memberBody(2) gb(826) national(0) gbNatCompany(1) dataConnection(1578918) 5 35 dccrldp(1) dccrldpObjects(1) dccrldpPmTable(2) dccrldpPmEntry(1) dccrldpPmPolicySupportFlags(24)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) eng-ltd(1) dataConnection(1578918) 5 35 dccrldp(1) dccrldpObjects(1) dccrldpPmTable(2) dccrldpPmEntry(1) dccrldpPmPolicySupportFlags(24)}
  • {iso(1) memberBody(2) gb(826) gbNational(0) gbNatCompany(1) dataConnection(1578918) 5 35 dccrldp(1) dccrldpObjects(1) dccrldpPmTable(2) dccrldpPmEntry(1) dccrldpPmPolicySupportFlags(24)}
OID-IRI notation
  • /1/2/826/0/1/1578918/5/35/1/1/2/1/24
  • /ISO/Member-Body/GB/0/1/1578918/5/35/1/1/2/1/24
  • /ISO/Member-Body/826/0/1/1578918/5/35/1/1/2/1/24
  • /ISO/2/826/0/1/1578918/5/35/1/1/2/1/24
Named path variants
  • /iso/member-body/gb/national/eng-ltd/1578918/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/member-body/gb/national/eng-ltd/dataConnection/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/member-body/gb/national/gbNatCompany/1578918/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/member-body/gb/national/gbNatCompany/dataConnection/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/member-body/gb/gbNational/eng-ltd/1578918/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/member-body/gb/gbNational/eng-ltd/dataConnection/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/member-body/gb/gbNational/gbNatCompany/1578918/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/member-body/gb/gbNational/gbNatCompany/dataConnection/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/memberBody/gb/national/eng-ltd/1578918/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/memberBody/gb/national/eng-ltd/dataConnection/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/memberBody/gb/national/gbNatCompany/1578918/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/memberBody/gb/national/gbNatCompany/dataConnection/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/memberBody/gb/gbNational/eng-ltd/1578918/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/memberBody/gb/gbNational/eng-ltd/dataConnection/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/memberBody/gb/gbNational/gbNatCompany/1578918/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags
  • /iso/memberBody/gb/gbNational/gbNatCompany/dataConnection/5/35/dccrldp/dccrldpObjects/dccrldpPmTable/dccrldpPmEntry/dccrldpPmPolicySupportFlags

Descriptions

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

This field contains bit flags which indicate whether DC-LDP supports LDP Policy and if per FEC policy optimization is to be used. The supported bit flags are - policySupported - perFecOptimizationSupported - suppressAddressPolicy - policyForVCFECs. The policySupported flag indicates that DC-LDP will enforce policy decisions made by the user through a number of user exits. If this flag is not set DC-LDP will not call policy user exits. The perFecOptimizationSupported flag indicates that DC-LDP provides policy on a per FEC basis as opposed to a per FEC per session basis. This results in policy user exits only being called once per FEC. This field is only significant if the policySupported flag is set. This feature is used to reduce the number of calls to the Policy User Exits particularly when a change in Policy is being implemented. If the perFecOptimizationSupported flag is not set then DC-LDP Path Manager enforces policy on a per FEC per peer basis. If this flag is set policy is enforced on a per FEC basis and the same policy decision is assumed to apply for all peers. The suppressAddressPolicy flag if set prevents DC-LDP from performing any Policy processing on receipt of a Address or Address Withdraw message from a peer. If this field is not set then its default value is determined by the RCP_USER_DO_POLICY compile time flag. The policyForVCFECs flag indicates that DC-LDP should call the policy user exits for VC-FECs. The default behavior is not to call the policy user exits for VC-FECs. The value of this field should be decided during integration. The field is not expected to change during the lifetime of the DC-LDP PM entity. As such, this object follows the replaceOnlyWhileDisabled behavior. It may not be changed when the row is active.

Source records

dccrldpPmPolicySupportFlags

Status in source: current.

Names: dccrldpPmPolicySupportFlags

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dccrldpPmPolicySupportFlags",
    "OBJECT-TYPE",
    "SYNTAX",
    "BITS",
    "{",
    "policySupported",
    "(",
    "0",
    ")",
    ",",
    "perFecOptimizationSupported",
    "(",
    "1",
    ")",
    ",",
    "suppressAddressPolicy",
    "(",
    "2",
    ")",
    ",",
    "policyForVCFECs",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This field contains bit flags which indicate whether DC-LDP supports LDP Policy and if per FEC policy optimization is to be used. The supported bit flags are - policySupported - perFecOptimizationSupported - suppressAddressPolicy - policyForVCFECs. The policySupported flag indicates that DC-LDP will enforce policy decisions made by the user through a number of user exits. If this flag is not set DC-LDP will not call policy user exits. The perFecOptimizationSupported flag indicates that DC-LDP provides policy on a per FEC basis as opposed to a per FEC per session basis. This results in policy user exits only being called once per FEC. This field is only significant if the policySupported flag is set. This feature is used to reduce the number of calls to the Policy User Exits particularly when a change in Policy is being implemented. If the perFecOptimizationSupported flag is not set then DC-LDP Path Manager enforces policy on a per FEC per peer basis. If this flag is set policy is enforced on a per FEC basis and the same policy decision is assumed to apply for all peers. The suppressAddressPolicy flag if set prevents DC-LDP from performing any Policy processing on receipt of a Address or Address Withdraw message from a peer. If this field is not set then its default value is determined by the RCP_USER_DO_POLICY compile time flag. The policyForVCFECs flag indicates that DC-LDP should call the policy user exits for VC-FECs. The default behavior is not to call the policy user exits for VC-FECs. The value of this field should be decided during integration. The field is not expected to change during the lifetime of the DC-LDP PM entity. As such, this object follows the replaceOnlyWhileDisabled behavior. It may not be changed when the row is active.\"",
    "::=",
    "{",
    "dccrldpPmEntry",
    "24",
    "}"
  ],
  "syntax_tree": [
    [
      "BITS",
      [
        [
          "policySupported",
          0
        ],
        [
          "perFecOptimizationSupported",
          1
        ],
        [
          "suppressAddressPolicy",
          2
        ],
        [
          "policyForVCFECs",
          3
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This field contains bit flags which indicate whether DC-LDP supports LDP Policy and if per FEC policy optimization is to be used. The supported bit flags are - policySupported - perFecOptimizationSupported - suppressAddressPolicy - policyForVCFECs. The policySupported flag indicates that DC-LDP will enforce policy decisions made by the user through a number of user exits. If this flag is not set DC-LDP will not call policy user exits. The perFecOptimizationSupported flag indicates that DC-LDP provides policy on a per FEC basis as opposed to a per FEC per session basis. This results in policy user exits only being called once per FEC. This field is only significant if the policySupported flag is set. This feature is used to reduce the number of calls to the Policy User Exits particularly when a change in Policy is being implemented. If the perFecOptimizationSupported flag is not set then DC-LDP Path Manager enforces policy on a per FEC per peer basis. If this flag is set policy is enforced on a per FEC basis and the same policy decision is assumed to apply for all peers. The suppressAddressPolicy flag if set prevents DC-LDP from performing any Policy processing on receipt of a Address or Address Withdraw message from a peer. If this field is not set then its default value is determined by the RCP_USER_DO_POLICY compile time flag. The policyForVCFECs flag indicates that DC-LDP should call the policy user exits for VC-FECs. The default behavior is not to call the policy user exits for VC-FECs. The value of this field should be decided during integration. The field is not expected to change during the lifetime of the DC-LDP PM entity. As such, this object follows the replaceOnlyWhileDisabled behavior. It may not be changed when the row is active."
    ],
    null,
    null,
    null,
    null
  ]
}
  • 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-CR-LDP-MIB

    Published definition
    dccrldpPmPolicySupportFlags OBJECT-TYPE
            SYNTAX       BITS {
                              policySupported(0),
                              perFecOptimizationSupported(1),
                              suppressAddressPolicy(2),
                              policyForVCFECs(3)
            }
            MAX-ACCESS   read-create
            STATUS       current
            DESCRIPTION
             "This field contains bit flags which indicate whether
             DC-LDP supports LDP Policy and if per FEC policy
             optimization is to be used.
    
             The supported bit flags are
                - policySupported
                - perFecOptimizationSupported
                - suppressAddressPolicy
                - policyForVCFECs.
    
             The policySupported flag indicates that DC-LDP will
             enforce policy decisions made by the user through a number
             of user exits.  If this flag is not set DC-LDP will not
             call policy user exits.
    
             The perFecOptimizationSupported flag indicates that DC-LDP
             provides policy on a per FEC basis as opposed to a per FEC
             per session basis.  This results in policy user exits only
             being called once per FEC.  This field is only significant
             if the policySupported flag is set.  This feature is used
             to reduce the number of calls to the Policy User Exits
             particularly when a change in Policy is being implemented.
    
             If the perFecOptimizationSupported flag is not set then
             DC-LDP Path Manager enforces policy on a per FEC per peer
             basis.
    
             If this flag is set policy is enforced on a per FEC basis
             and the same policy decision is assumed to apply for all
             peers.
    
             The suppressAddressPolicy flag if set prevents DC-LDP from
             performing any Policy processing on receipt of a Address
             or Address Withdraw message from a peer.
    
             If this field is not set then its default value is
             determined by the RCP_USER_DO_POLICY compile time flag.
    
             The policyForVCFECs flag indicates that DC-LDP should call
             the policy user exits for VC-FECs.  The default behavior
             is not to call the policy user exits for VC-FECs.
    
             The value of this field should be decided during
             integration.  The field is not expected to change during the
             lifetime of the DC-LDP PM entity.  As such, this object
             follows the replaceOnlyWhileDisabled behavior.  It may not
             be changed when the row is active."
    
           ::= {dccrldpPmEntry 24 }
    Module imports
    {'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Integer32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}
    · Download DC-CR-LDP-MIB

    Related source files and packages:


    Source location: DC-CR-LDP-MIB::dccrldpPmPolicySupportFlags.
    Source version and references

    Downloaded: 2026-10-24T02:14:21.043228+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 (41)

OIDNameDirect childrenDescendantsDescription
1.2.826.0.1.1578918.5.35.1.1.2.1.1 dccrldpPmIndex00
1.2.826.0.1.1578918.5.35.1.1.2.1.2 dccrldpPmLsrIndex00
1.2.826.0.1.1578918.5.35.1.1.2.1.3 dccrldpPmLdpEntityAutoCreate00
1.2.826.0.1.1578918.5.35.1.1.2.1.4 dccrldpPmLdpEntityAutoStart00
1.2.826.0.1.1578918.5.35.1.1.2.1.5 dccrldpPmLdpEntityReuse00
1.2.826.0.1.1578918.5.35.1.1.2.1.6 dccrldpPmLdpVersion00
1.2.826.0.1.1578918.5.35.1.1.2.1.7 dccrldpPmUseLdpFt00
1.2.826.0.1.1578918.5.35.1.1.2.1.8 dccrldpPmAsNumber00
1.2.826.0.1.1578918.5.35.1.1.2.1.9 dccrldpPmIprBufPoolSize00
1.2.826.0.1.1578918.5.35.1.1.2.1.10 dccrldpPmLdpSupported00
1.2.826.0.1.1578918.5.35.1.1.2.1.11 dccrldpPmCrLdpSupported00
1.2.826.0.1.1578918.5.35.1.1.2.1.12 dccrldpPmQueryFECSupported00
1.2.826.0.1.1578918.5.35.1.1.2.1.13 dccrldpPmAdminStatus00
1.2.826.0.1.1578918.5.35.1.1.2.1.14 dccrldpPmOperStatus00
1.2.826.0.1.1578918.5.35.1.1.2.1.15 dccrldpPmRowStatus00
1.2.826.0.1.1578918.5.35.1.1.2.1.16 dccrldpPmRestartCapable00
1.2.826.0.1.1578918.5.35.1.1.2.1.17 dccrldpPmReconnectTime00
1.2.826.0.1.1578918.5.35.1.1.2.1.18 dccrldpPmRecoveryTime00
1.2.826.0.1.1578918.5.35.1.1.2.1.19 dccrldpPmMaxPeerReconnect00
1.2.826.0.1.1578918.5.35.1.1.2.1.20 dccrldpPmMaxPeerRecovery00
1.2.826.0.1.1578918.5.35.1.1.2.1.21 dccrldpPmAdjDwnHoldTime00
1.2.826.0.1.1578918.5.35.1.1.2.1.22 dccrldpPmOutSegProgOrder00
1.2.826.0.1.1578918.5.35.1.1.2.1.23 dccrldpPmSupportIpv600
1.2.826.0.1.1578918.5.35.1.1.2.1.25 dccrldpPmCheckOutSegIntfaceStat00
1.2.826.0.1.1578918.5.35.1.1.2.1.26 dccrldpPmLdpEntityCreateNhrLdb00
1.2.826.0.1.1578918.5.35.1.1.2.1.27 dccrldpPmLdpEntityCreatePsiJoin00
1.2.826.0.1.1578918.5.35.1.1.2.1.28 dccrldpPmRedundancySwitchIntvl00
1.2.826.0.1.1578918.5.35.1.1.2.1.29 dccrldpPmLabelWithdrawDelay00
1.2.826.0.1.1578918.5.35.1.1.2.1.30 dccrldpPmImplicitXcVcFecs00
1.2.826.0.1.1578918.5.35.1.1.2.1.31 dccrldpPmWthdrwDownstreamLbl00
1.2.826.0.1.1578918.5.35.1.1.2.1.32 dccrldpPmIngressReleaseDelay00
1.2.826.0.1.1578918.5.35.1.1.2.1.33 dccrldpPmPwFastUpstreamRelease00
1.2.826.0.1.1578918.5.35.1.1.2.1.34 dccrldpPmDistPrefixTargetSess00
1.2.826.0.1.1578918.5.35.1.1.2.1.35 dccrldpPmLdpEntityCreateLdbJoin00
1.2.826.0.1.1578918.5.35.1.1.2.1.36 dccrldpPmLdpEntityRpi4PartnerIx00
1.2.826.0.1.1578918.5.35.1.1.2.1.37 dccrldpPmLdpEntityI3ProviderIx00
1.2.826.0.1.1578918.5.35.1.1.2.1.38 dccrldpPmLdpEntityRecalcPlcy00
1.2.826.0.1.1578918.5.35.1.1.2.1.39 dccrldpPmTargetLdiProviderIx00
1.2.826.0.1.1578918.5.35.1.1.2.1.40 dccrldpPmLdpEntityRpi6PartnerIx00
1.2.826.0.1.1578918.5.35.1.1.2.1.41 dccrldpPmNextHopUpdateMode00
1.2.826.0.1.1578918.5.35.1.1.2.1.42 dccrldpPmCheckOutSegAdjState00