drakkar-lig / drakkar-lig/walt-python-packages
PoE not powering on
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Use case:
- A released PoE-powered node is connected to a network port. It has been powered off after being idle for several hours.
- The node is replaced with a new node that is powered externally. The server detects the new node on the network port, and it boots successfully.
- The original PoE-powered node is connected back to the same network port.
Expected behavior:
The original PoE-powered node should power on automatically, and the server should detect that it has reconnected to the network port.
Actual behavior:
The original PoE-powered node remains powered off instead of booting. As a result, the server does not detect that it has been reconnected to the Ethernet port.
Workaround:
Run walt node reboot on the replacement node (the one powered externally). This causes PoE to be re-enabled on the port, allowing the original PoE-powered node to boot.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the walt node reboot entry point and reproduce the described replacement-node sequence to trace where PoE is re-enabled. Identify the PoE port-handling path involved; done means reconnecting the original idle PoE-powered node causes it to boot and become visible to the server without the workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100