> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/verkada-cameras/es/configuracion/camera-network-settings/use-lldp-with-cameras.md). # Usar LLDP con cámaras Usa LLDP para descubrir información sobre tus cámaras Verkada Las cámaras Verkada admiten el Protocolo de descubrimiento de capa de enlace (LLDP). LLDP es un protocolo estándar de capa de enlace utilizado en diversos dispositivos de red para anunciar su identidad, capacidades y vecinos en una red de área local (LAN). El valor principal de usar LLDP es gestionar las integraciones de red y la solución de problemas. Por ejemplo, un administrador de red puede identificar rápidamente qué dispositivo Verkada está conectado a un puerto de switch en particular o configurar una política para reconfigurar automáticamente el puerto en función de información específica de LLDP. Las cámaras Verkada anuncian la siguiente información cada 30 segundos: * ID del dispositivo * Revisión del firmware * Número de serie * Nombre del fabricante (Verkada) * Nombre del modelo * TLV de Extreme Fabric Connect * Capacidades de autonegociación --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.verkada.com/verkada-cameras/es/configuracion/camera-network-settings/use-lldp-with-cameras.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.