OID reference

esPoeIfPdAliveCfgTable

1.3.6.1.4.1.171.17.24.1.3.3

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.171.17.24.1.3 (esPoeIfObjects)
Node code: 3
Node name: esPoeIfPdAliveCfgTable
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.171.17.24.1.3.3
URN notation: urn:oid:1.3.6.1.4.1.171.17.24.1.3.3

ASN.1, OID-IRI and named path variants

ASN.1 notation

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

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dlink(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) d-link(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) company(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) my(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nms(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dlink(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) d-link(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) company(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) my(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nms(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dlink(171) dlinkCommon(17) dlinkEsPoeExtMIB(24) esPoeMIBObjects(1) esPoeIfObjects(3) esPoeIfPdAliveCfgTable(3)}
Additional combinations skipped.

OID-IRI notation

/1/3/6/1/4/1/171/17/24/1/3/3
/ISO/Identified-Organization/6/1/4/1/171/17/24/1/3/3
/ISO/3/6/1/4/1/171/17/24/1/3/3

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/dlink/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/enterprise/d-link/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/enterprise/company/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/enterprise/my/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/enterprise/nms/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/enterprises/dlink/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/enterprises/d-link/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/enterprises/company/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/enterprises/my/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/enterprises/nms/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/ldap-enterprise/dlink/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/ldap-enterprise/d-link/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/ldap-enterprise/company/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/ldap-enterprise/my/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/ldap-enterprise/nms/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
/iso/identified-organization/dod/internet/private/vendor-objects/dlink/dlinkCommon/dlinkEsPoeExtMIB/esPoeMIBObjects/esPoeIfObjects/esPoeIfPdAliveCfgTable
Additional combinations skipped.

SNMP properties

Value type: SEQUENCE OF EsPoeIfPdAliveCfgEntry
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.

Published definition

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

esPoeIfPdAliveCfgTable OBJECT-TYPE
        SYNTAX        SEQUENCE OF EsPoeIfPdAliveCfgEntry
        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."
        ::= { esPoeIfObjects 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 MIBs

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 MIBs1 record · 3 sources

Description 1

esPoeIfPdAliveCfgTable · currentD-Link official switch MIBs3 sources

Status in source: current.

Names: esPoeIfPdAliveCfgTable

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "esPoeIfPdAliveCfgTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "EsPoeIfPdAliveCfgEntry",
    "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.\"",
    "::=",
    "{",
    "esPoeIfObjects",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "EsPoeIfPdAliveCfgEntry"
      ]
    ],
    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
  ]
}

D-Link official switch MIBs · Publisher's source file: Source package: DGS3130_RUN_1.12.B002_mibs.tar.bz2
Module: DLINKES-POE-MIB

See published definition above
Module imports
```
{'SNMPv2-TC': ['DisplayString', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['PortList', 'VlanId'], 'DLINK-ID-REC-MIB': ['dlinkCommon'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'POWER-ETHERNET-MIB': ['pethMainPseGroupIndex', 'pethPsePortIndex', 'pethPsePortShortCounter', 'pethPsePortOverLoadCounter', 'pethPsePortPowerDeniedCounter']}
```
· Download DLINKES-POE-MIB.my
Related source files and packages:
Show all 6 related files and packages
Same file in DGS3130_RUN_1.12.B002_mibs.tar.bz2.
Same file in DGS3130_RUN_1.12.B002_mibs.tar.bz2.
Same file in DGS3130_RUN_1.12.B002_mibs.tar.bz2.
Same file in DGS3130_RUN_1.12.B002_mibs.tar.bz2.
D-Link official switch MIBs · Publisher's source file: Source package: DGS3130_RUN_2.04.001_mibs.tar.bz2
Module: DLINKES-POE-MIB

Same published definition
Module imports
```
{'SNMPv2-TC': ['DisplayString', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['PortList', 'VlanId'], 'DLINK-ID-REC-MIB': ['dlinkCommon'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'POWER-ETHERNET-MIB': ['pethMainPseGroupIndex', 'pethPsePortIndex', 'pethPsePortShortCounter', 'pethPsePortOverLoadCounter', 'pethPsePortPowerDeniedCounter']}
```
· Download DLINKES-POE-MIB.my
Related source files and packages:
Show all 11 related files and packages
Same file in DGS3130_RUN_2.04.001_mibs.tar.bz2.
Same file in DGS3130_RUN_2.00.011_mibs.tar.bz2.
Same file in DGS3130_RUN_2.04.001_mibs.tar.bz2.
Same file in 2.00.011_MIB.7z.
D-Link official switch MIBs · Publisher's source file: Source package: DMS3130_RUN_1.00.015_mibs.tar.bz2
Module: DLINKES-POE-MIB

Same published definition
Module imports
```
{'SNMPv2-TC': ['DisplayString', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Integer32', 'Unsigned32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP'], 'Q-BRIDGE-MIB': ['PortList', 'VlanId'], 'DLINK-ID-REC-MIB': ['dlinkCommon'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress'], 'POWER-ETHERNET-MIB': ['pethMainPseGroupIndex', 'pethPsePortIndex', 'pethPsePortShortCounter', 'pethPsePortOverLoadCounter', 'pethPsePortPowerDeniedCounter']}
```
· Download DLINKES-POE-MIB.my
Related source files and packages:
Show all 9 related files and packages
Same file in DMS_DXS3130_RUN_1.30.006_mibs.tar.bz2.
Same file in DMS_DXS3130_RUN_1.20.003_mibs.tar.bz2.
Same file in DMS_DXS3130_RUN_1.30.006_mibs.tar.bz2.
Same file in DMS_DXS3130_RUN_1.30.006_mibs.tar.bz2.

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.171)

Henry P. Nagai

Direct children (1)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.171.17.24.1.3.3.1	esPoeIfPdAliveCfgEntry	8	8

Siblings (2)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.171.17.24.1.3.1	esPoeIfCfgTable	1	5
1.3.6.1.4.1.171.17.24.1.3.2	esPoeIfInfoObjects	3	21