AS4630 series - How to troubleshoot the Power Devices not powered by the switch's PoE function? Follow

Purpose : 
This article shows troubleshooting the Power Devices not powered by the switch's PoE function.

Model : 

• AS4630-54PE
• AS4630-54NPE

Introduction to PoE : 

• The power sourcing equipment(PSE) mentioned in this article are the switches AS4630-54PE and AS4630-54NPE. The power devices(PD) are IP phones, network security cameras, APs, PDAs, mobile phones, etc.
• For AS4630-54PE and AS4630-54NPE: All the 48 RJ-45 ports fully support IEEE 802.3af/at/bt, Type 3/4 Power-over-Ethernet.

PoE stands for "Power over Ethernet". In IEEE standards, the PSE provides power through 3 ways:

1. mode A - Provide power through the same 2 twisted-pairs as the data (pair 1-2, 3-6)
2. mode B - Provide power through the spare 2 twisted-pairs that the data is not using (pair 4-5, 7-8)
3. 4PPoE - Provide power using all 4 twisted-pairs.

Note: If the PD supports only one of the modes (A or B), or if it supports passive PoE, it is a non-standard PD. Please contact Edgecore Support for detailed debugging.

Here is a diagram of the levels of power each standard provides.

Procedure : 

Step-0 Check the IEEE standard of the PD

Please first check the datasheet of your PD. Find the standard it supports.

CAUTION: If you test with non-supported types, this may cause permanent damage to your PD. Edgecore will not take responsibility if you damaged your PD in this way. Carefully check it before testing.

For example, here's the data sheet for Edgecore Access Point OAP101.

It is compliant to the IEEE PoE standard 802.3at.

Step-1 Please power cycle the switch and boot into the ACCTON-DIAG

Use the following command for testing the POE function.

Note:

• The PoE configuration will only be reloaded when the switch is power cycled. 

First check the current MCU firmware. For example:

root@(none):/# export DEBUG=1
root@(none):/# i2c-dev POE_MCU open
root@(none):/# poe_cmd status system
Request:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x20 0x00 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x17
Response:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x20 0x00 0x02 0x30 0x00 0xE1 0x31 0x13 0x00 0x09 0x07 0x87

Mode  Max_ports Port_map DeviceID SW_Verion MCU_type System_status Ext_SW_ver
=============================================================================
 0x2       0x30        0   0xe131      0x13        0           0x9       0x7
return=BCMPoE_Success(0)

Please see the last part of last line:

SW_Verion MCU_type System_status Ext_SW_ver
===========================================
     0x13        0           0x9       0x7

The firmware version is v1.3.0.7.

Step-2 Configure the PSE according to your PD

Execute these commands first:

root@(none):/# export DEBUG=1 
root@(none):/# i2c-dev POE_MCU open

For the following commands, we will set the PSE port to the designated type, bypass classification for the PD, and manually set the power limit.

You need to specify the testing port number in hexadecimal. For example, port 10 is 0x0a. The port number will be marked in red. The port range is 0~47. Please revise this value to fit your case.

Step-2.1 For IEEE 802.3af PDs

If your PD supports IEEE 802.3af, execute the command:

root@(none):/# poe_cmd raw 0x1c 0x0 0x0a 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x11 0x0 0x0a 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x15 0x0 0x0a 0x02 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x16 0x0 0x0a 0x4d 0xff 0xff 0xff 0xff 0xff 0xff 0xff

Wait for about 20 seconds and connect your PD to the switch port. Does it power up?

Step-2.2 For IEEE 802.3at PDs

If your PD supports IEEE 802.3at, execute the command:

root@(none):/# poe_cmd raw 0x1c 0x0 0x0a 0x03 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x11 0x0 0x0a 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x15 0x0 0x0a 0x02 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x16 0x0 0x0a 0x96 0xff 0xff 0xff 0xff 0xff 0xff 0xff

Wait for about 20 seconds and connect your PD to the switch port. Does it power up?

Step-2.3 For IEEE 802.3bt, Type 3 PDs

If your PD supports IEEE 802.3bt, Type 3, execute the command:

root@(none):/# poe_cmd raw 0x1c 0x0 0x0a 0x05 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x11 0x0 0x0a 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x15 0x0 0x0a 0x02 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x16 0x0 0x0a 0x96 0xff 0xff 0xff 0xff 0xff 0xff 0xff

Wait for about 20 seconds and connect your PD to the switch port. Does it power up?

Step-2.4 For IEEE 802.3bt, Type 4 PDs

If your PD supports IEEE 802.3bt, Type 4, execute the command:

root@(none):/# poe_cmd raw 0x1c 0x0 0x0a 0x06 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x11 0x0 0x0a 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x15 0x0 0x0a 0x02 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x16 0x0 0x0a 0xe1 0xff 0xff 0xff 0xff 0xff 0xff 0xff

Wait for about 20 seconds and connect your PD to the switch port. Does it power up?

With the above settings, if you still find that the PD is not powered, or PD status does not match with the PSE power supplying status, please go to the Step-3 for further test.

Step-3 Check with other test items

You can first check the following points:

1. Power cycle switch and test again
2. Test with another PD device
3. Test with another Ethernet cable
4. Test with another PSE port

Step-4 Check port status

If the above steps do not work, check further with the following commands to find the actual type/class/power delivered status with the PD from the PSE. We will use raw commands for checking. Please see what the command bytes mean at the bottom of this page.

Execute the following commands for further checking:

root@(none):/# export DEBUG=1
root@(none):/# i2c-dev POE_MCU open
root@(none):/# poe_cmd raw 0x21 0x0 0x0a 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x26 0x0 0x0a 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x25 0x0 0x0a 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# poe_cmd raw 0x30 0x0 0x0a 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
root@(none):/# unset DEBUG

**Note that the 0x0a in command should be your testing port number in hexadecimal. Here we are using port 10 as an example. Please revise this value to fit your case.

Please collect the above logs and submit a ticket to Edgecore Support.

Appendix - The explanation of raw command bytes

Example case for Command 0x21:

root@(none):/# poe_cmd raw 0x21 0x0 0x2c 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
Request:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x21 0x00 0x2C 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x45
Response:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x21 0x00 0x2C 0x01 0x01 0x0E 0x01 0xFF 0x00 0x00 0x01 0x5E
return=BCMPoE_Success(0)

• This is port 44. The PSE is still looking for the PD, which did not power up. It detects a class mismatch. This could be the reason why it fails to provide power to PD.

Example case for Command 0x25:

root@(none):/# poe_cmd raw 0x25 0x0 0x2d 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
Request:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x25 0x00 0x2D 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x4A
Response:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x25 0x00 0x2D 0x01 0x00 0x02 0x01 0x02 0x00 0xFF 0xFF 0x56
return=BCMPoE_Success(0)

The Response bytes:

• This is port 45. The PSE is enabled. This port uses 802.3af 4-point detection to detect the PD.
• This port enables classification. This port uses Alternative A pair to supply power.

Example case for Command 0x26:

root@(none):/# poe_cmd raw 0x26 0x0 0x2c 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
Request:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x26 0x00 0x2C 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x4A
Response:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x26 0x00 0x2C 0x06 0x01 0xF9 0x00 0xA9 0xD3 0x00 0xFF 0xCD
return=BCMPoE_Success(0)

• This is port 44. It provides power with 802.3bt Type-4 mode. The power limit is class-based.
• The maximum power threshold is 99.8W. However, since Byte 4 is "Class based", this value does not apply. Byte 5 only works when Byte 4 is "User defined" and when the port is up.

Example case for Command 0x30:

root@(none):/# poe_cmd raw 0x30 0x0 0x0a 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
Request:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x30 0x00 0x0A 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x32
Response:
    0    1    2    3    4    5    6    7    8    9   10   11
============================================================
 0x30 0x00 0x0A 0x03 0x49 0x03 0xA3 0x00 0xC7 0x01 0xF8 0xEC
return=BCMPoE_Success(0)

The Response bytes:

• This is port 10. The PSE is providing power,
• Voltage: 0x0349 (hex) = 841 (dec). 841 x 64.45 / 1000 = 54.202 (V)
• Current: 0x03a3 (hex) = 931 (dec). 931 x 1 / 1000 = 0.931 (A)
• Power: 0x01f8 (hex) = 504 (dec). 504 x 0.1 = 50.4 (W)

--