OID reference

dPoeIfPdAliveCfgTable

1.3.6.1.4.1.171.14.24.1.3.3

Description

This table consists of a list of configuration for the PD alive check function for ports. The PD alive check feature provides the solution for PD device that has the stop working or no response problem via Ping mechanism. Detailed Process: The detailed processes are described as follows: 1. The system needs to periodi…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.171.14.24.1.3 (dPoeIfObjects)
Node code
3
Node name
dPoeIfPdAliveCfgTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.171.14.24.1.3.3
URN notation
urn:oid:1.3.6.1.4.1.171.14.24.1.3.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 171 14 24 1 3 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) dlinkIndustrialCommon(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) dlink-experiment(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) dlinkIndustrialCommon(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) dlink-experiment(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) dlinkIndustrialCommon(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) dlink-experiment(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) dlinkIndustrialCommon(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) dlink-experiment(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) dlinkIndustrialCommon(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) dlink-experiment(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dlink(171) dlinkIndustrialCommon(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dlink(171) dlink-experiment(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) d-link(171) dlinkIndustrialCommon(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) d-link(171) dlink-experiment(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) company(171) dlinkIndustrialCommon(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) company(171) dlink-experiment(14) dlinkSwPoeExtMIB(24) dPoeMIBObjects(1) dPoeIfObjects(3) dPoeIfPdAliveCfgTable(3)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/171/14/24/1/3/3
  • /ISO/Identified-Organization/6/1/4/1/171/14/24/1/3/3
  • /ISO/3/6/1/4/1/171/14/24/1/3/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/dlink/dlinkIndustrialCommon/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprise/dlink/dlink-experiment/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprise/d-link/dlinkIndustrialCommon/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprise/d-link/dlink-experiment/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprise/company/dlinkIndustrialCommon/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprise/company/dlink-experiment/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprise/my/dlinkIndustrialCommon/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprise/my/dlink-experiment/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprise/nms/dlinkIndustrialCommon/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprise/nms/dlink-experiment/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprises/dlink/dlinkIndustrialCommon/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprises/dlink/dlink-experiment/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprises/d-link/dlinkIndustrialCommon/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprises/d-link/dlink-experiment/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprises/company/dlinkIndustrialCommon/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • /iso/identified-organization/dod/internet/private/enterprises/company/dlink-experiment/dlinkSwPoeExtMIB/dPoeMIBObjects/dPoeIfObjects/dPoeIfPdAliveCfgTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF DPoeIfPdAliveCfgEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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.

dPoeIfPdAliveCfgTable OBJECT-TYPE
        SYNTAX        SEQUENCE OF DPoeIfPdAliveCfgEntry
        MAX-ACCESS    not-accessible
        STATUS        current
        DESCRIPTION
             "This table consists of a list of configuration for the PD
             alive check function for ports.
             The PD alive check feature provides the solution for 
             PD device that has the stop working or no response 
             problem via Ping mechanism.
             Detailed Process:
             The detailed processes are described as follows:
             1. The system  needs to  periodically monitor the 
              specific PD by using Ping function. If there is no 
              response, system takes one of the following actions:
              (1) Reset: Switch resets (disable then enable) PoE 
                  power on the port which connects to a PD under monitoring.
              (2) Notify: Switch sends logs and traps to notify the administrator.
              (3) Both: Switch sends logs and traps, and resets the PoE port power.
             2. The system should implement the retry  mechanism to check 
              PD aliveness, hence the system will reset the PoE port power 
              feeding after the retry by using Ping without any response from a PD.
             3. If the action is Reset or  Both, the system needs 
              to wait for PD recovery from rebooting and then executes 
              the Ping function again. Besides, the waiting time can 
              be configured by users.
             4. If PoE schedule (time range) function is configured 
              on the port which enables the PD Alive Check  function, 
              the time range function has the top priority, and 
              therefore PD Alive Check function will not work 
              while PoE time range function is still active.
             5. This function only takes effect on PoE enabled 
              port with power feeding.
             
             Note: It is required to setup IP settings properly that 
              the PD can be reachable for Ping, otherwise this function 
              cannot work as expected.
             
              Limitation
             1. Support Ping Function: If the PD does not support ICMP, 
              this function cannot work normally.
             2. Direct-Connected PD: The Reset Action can only work on 
              the direct-connected PD. If the PD is not connected directly, 
              the Reset Action may not work as expected.
             3. PD Also Acts as PSE: If the direct-connected PD is also a PSE, 
              all the next level PDs connect to this PSE will be power cycling 
              whenever PD Alive Check function takes effect on 'Reset' or 'Both' Action." 
        ::= { dPoeIfObjects 3 }

Meaning

Descriptions

1 unique

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

This table consists of a list of configuration for the PD alive check function for ports. The PD alive check feature provides the solution for PD device that has the stop working or no response problem via Ping mechanism. Detailed Process: The detailed processes are described as follows: 1. The system needs to periodically monitor the specific PD by using Ping function. If there is no response, system takes one of the following actions: (1) Reset: Switch resets (disable then enable) PoE power on the port which connects to a PD under monitoring. (2) Notify: Switch sends logs and traps to notify the administrator. (3) Both: Switch sends logs and traps, and resets the PoE port power. 2. The system should implement the retry mechanism to check PD aliveness, hence the system will reset the PoE port power feeding after the retry by using Ping without any response from a PD. 3. If the action is Reset or Both, the system needs to wait for PD recovery from rebooting and then executes the Ping function again. Besides, the waiting time can be configured by users. 4. If PoE schedule (time range) function is configured on the port which enables the PD Alive Check function, the time range function has the top priority, and therefore PD Alive Check function will not work while PoE time range function is still active. 5. This function only takes effect on PoE enabled port with power feeding. Note: It is required to setup IP settings properly that the PD can be reachable for Ping, otherwise this function cannot work as expected. Limitation 1. Support Ping Function: If the PD does not support ICMP, this function cannot work normally. 2. Direct-Connected PD: The Reset Action can only work on the direct-connected PD. If the PD is not connected directly, the Reset Action may not work as expected. 3. PD Also Acts as PSE: If the direct-connected PD is also a PSE, all the next level PDs connect to this PSE will be power cycling whenever PD Alive Check function takes effect on 'Reset' or 'Both' Action.

Sources for this description

D-Link official switch MIBsD-Link 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 1D-Link official switch MIBs, D-Link MIB copies (LibreNMS/Observium Community)1 record · 2 sources

Description 1

dPoeIfPdAliveCfgTable · currentD-Link official switch MIBs, D-Link MIB copies (LibreNMS/Observium Community)2 sources

Status in source: current.

Names: dPoeIfPdAliveCfgTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dPoeIfPdAliveCfgTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "DPoeIfPdAliveCfgEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table consists of a list of configuration for the PD alive check function for ports. The PD alive check feature provides the solution for PD device that has the stop working or no response problem via Ping mechanism. Detailed Process: The detailed processes are described as follows: 1. The system needs to periodically monitor the specific PD by using Ping function. If there is no response, system takes one of the following actions: (1) Reset: Switch resets (disable then enable) PoE power on the port which connects to a PD under monitoring. (2) Notify: Switch sends logs and traps to notify the administrator. (3) Both: Switch sends logs and traps, and resets the PoE port power. 2. The system should implement the retry mechanism to check PD aliveness, hence the system will reset the PoE port power feeding after the retry by using Ping without any response from a PD. 3. If the action is Reset or Both, the system needs to wait for PD recovery from rebooting and then executes the Ping function again. Besides, the waiting time can be configured by users. 4. If PoE schedule (time range) function is configured on the port which enables the PD Alive Check function, the time range function has the top priority, and therefore PD Alive Check function will not work while PoE time range function is still active. 5. This function only takes effect on PoE enabled port with power feeding. Note: It is required to setup IP settings properly that the PD can be reachable for Ping, otherwise this function cannot work as expected. Limitation 1. Support Ping Function: If the PD does not support ICMP, this function cannot work normally. 2. Direct-Connected PD: The Reset Action can only work on the direct-connected PD. If the PD is not connected directly, the Reset Action may not work as expected. 3. PD Also Acts as PSE: If the direct-connected PD is also a PSE, all the next level PDs connect to this PSE will be power cycling whenever PD Alive Check function takes effect on 'Reset' or 'Both' Action.\"",
    "::=",
    "{",
    "dPoeIfObjects",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "DPoeIfPdAliveCfgEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table consists of a list of configuration for the PD alive check function for ports. The PD alive check feature provides the solution for PD device that has the stop working or no response problem via Ping mechanism. Detailed Process: The detailed processes are described as follows: 1. The system needs to periodically monitor the specific PD by using Ping function. If there is no response, system takes one of the following actions: (1) Reset: Switch resets (disable then enable) PoE power on the port which connects to a PD under monitoring. (2) Notify: Switch sends logs and traps to notify the administrator. (3) Both: Switch sends logs and traps, and resets the PoE port power. 2. The system should implement the retry mechanism to check PD aliveness, hence the system will reset the PoE port power feeding after the retry by using Ping without any response from a PD. 3. If the action is Reset or Both, the system needs to wait for PD recovery from rebooting and then executes the Ping function again. Besides, the waiting time can be configured by users. 4. If PoE schedule (time range) function is configured on the port which enables the PD Alive Check function, the time range function has the top priority, and therefore PD Alive Check function will not work while PoE time range function is still active. 5. This function only takes effect on PoE enabled port with power feeding. Note: It is required to setup IP settings properly that the PD can be reachable for Ping, otherwise this function cannot work as expected. Limitation 1. Support Ping Function: If the PD does not support ICMP, this function cannot work normally. 2. Direct-Connected PD: The Reset Action can only work on the direct-connected PD. If the PD is not connected directly, the Reset Action may not work as expected. 3. PD Also Acts as PSE: If the direct-connected PD is also a PSE, all the next level PDs connect to this PSE will be power cycling whenever PD Alive Check function takes effect on 'Reset' or 'Both' Action."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.171)

Henry P. Nagai

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.171.14.24.1.3.3.1 dPoeIfPdAliveCfgEntry77

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.171.14.24.1.3.1 dPoeIfCfgTable15
1.3.6.1.4.1.171.14.24.1.3.2 dPoeIfInfoObjects210