Your software release
may not support all the features documented in this module. For the latest
caveats and feature information, see Bug Search Tool and the release notes for
your platform and software release. To find information about the features
documented in this module, and to see a list of the releases in which each
feature is supported, see the feature information table at the end of this
Use Cisco Feature
Navigator to find information about platform support and Cisco software image
support. To access Cisco Feature Navigator, go to
An account on Cisco.com is not required.
This section list
some frequently asked questions about Network Powered Lighting.
What does "New
Endpoint" in the "show coap stats" output mean? When does "New Endpoint"
migrate to "Endpoint"?
New endpoint means that an endpoint has been seen (Discovery packets received) but not yet registered by the CoAP proxy. The CoAP proxy will periodically look at the new endpoint and then send them a GET on “./well-known/core” to get more details, and once RSP is received, it is moved to “Endpoint".
Why can I not do a "CoAP start” unless there is a security configuration?
We need to ensure that all configurations related to CoAP are done and then it can be explicitly enabled. This avoids any intermittent unstable states across configurations.
Why do we need to enforce drop into the “coap proxy” configuration mode “coap proxy <cr>”? When I have completed the configuration, I have to exit twice to get back to the switch prompt. I do not find this very user friendly.
We would alternatively have to type “coap proxy” as prefix for each configuration that we do. It is a better option to get into a sub-mode, as all the configurations under the sub-mode relating to coap-proxy can be done.
Why am I not able to unconfigure security or other parameters without first stopping the coap process?
We need to ensure that all configurations related to CoAP are done and then it can be explicitly enabled. This also avoids and controls the complexity where the user might configure settings on the fly, when CoAP is enabled.
When I stop coap, all configurations associated with the CoAP process are not removed automatically (or return to defaults). Why does the CoAP remember previous configuration? This seems very hard for users to start fresh.
The system has been intentionally designed this way and this is expected behavior. Sometimes we just want to make minor changes, like change max-endpoints and re-start the proxy. It is a better option to hold all other configurations in place, else the user has to configure everything all over again.
How can I see what the security configurations have been set?
The command “show run” shows all the configurations.
How can I tune the timer values?
wtsao-3850#sho coap glo
Coap System Timer Values:
Discovery : 120 sec
Cache Exp : 5 sec
Keep Alive : 120 sec
Client DB : 5 sec
Query Queue : 500 ms
Ack delay : 500 ms
Timeout : 5 sec
Max Endpoints : 500
Resource Disc Mode : POST
values are fixed and are not tunable at the moment. The reason for this is to
avoid inconsistency across systems.
What are the commands “list” and “endpoint” used for?
The “list” command is to make it easier to configure multiple ip-addresses and give a name to it. Then you can assign the name instead of a single ip, to represent multiple ip’s. The "endpoint" command is used to configure a static end point, in cases where the endpoints do not advertise themselves.
How can I find the endpoint-to-port mapping by using the “show” command?
We do not support that of now. However, other commands can be run to fetch this data. Currently, we can still get all the details mentioned using individual commands like “lldp neighbours”, “ip dhcp”, “power inlines” and so on.