> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/admin/pending-snmp/create-watch-snmp.md). # Create Watch SNMP ## Overview This page explains how to add individual watches into Highlight. For service providers with a requirement to add multiple watches (10 or more) there is an alternative process which is explained on the [bulkloading watches page](/functionality/bulkloading.md). Find out more about [pending watches](/admin/pending-snmp.md). ## Create a watch *Network Explorer showing a folder with locations* Select the point in the Network Explorer tree (or using Admin Browse) where the new watch will be created. This must be a location or a folder which contains one or more locations. To create a new watch from Admin Pending, click **Create Watch** The Edit Pending Watch dialog is used to edit a watch before it is made live. The path to the folder is shown along with the group (if applicable). There are 5 areas: *Admin Pending Watch 5 steps* 1. Main 2. Technical 3. Test Results (visible immediately after a test only) 4. Watch Status (visible after a test and the watch has been saved and reopened) 5. Progress Log (visible after a test and the watch has been saved and reopened) **Save** — It's possible to save the details at any point. You can return to this dialog at any time to complete the process. ## 1. Main *Create Watch Main* * **Watch Name** — this is a required field which uniquely identifies the watch; it must not exceed 100 characters in length. Valid characters are `A-z 0-9 . - _ + ! $ # @ =` * **Location** — select the required location from the drop-down list if not already displayed * **Description** — this is optional and is displayed in Highlight in place of the watch name * **Watch Type** — bandwidth options available will change based on the type selected, see the table below * **Product Type** — this is an optional text field which is limited to 20 characters and enables service providers to display the service name for a watch rather than the Highlight default name, for example FTTC instead of ADSL. * **Bandwidth** — see the table below * **Reference** — Reference is optional and may be useful for customer specific information, for example Purchase Order ### Allow any bandwidth *Choose bandwidth from drop-down list or enter any value* Both bandwidth fields are required. Start typing and select a bandwidth from the displayed list. Alternatively enter any whole number with one of the following units: * **b/B**: bits per second * **k/K**: kilobits per second * **m/M**: megabits per second * **g/G**: gigabits per second * **t/T**: terabits per second
Watch TypeBandwidth 1Bandwidth 2
Leased Line (Dedicated Access, Ethernet)BandwidthOn bearer of
Leased Line + Class of Service (MPLS)BandwidthOn bearer of
Multilink/BondedBandwidthOn bearer of
Asymmetric LineDownstreamUpstream
ADSL MaxDownstreamUpstream
SDSLDownstreamUpstream
Broadband ClarityDownstreamUpstream
## 2. Technical The options available in this section will change based on which protocol (SNMPv2 or SNMPv3) is selected. It's possible to save the watch without completing this section but it will not be possible to test nor activate it. These fields are common between all protocols: * **Device IP** — the device IP address * **Selected Interface** — if an interface has previously been selected, it will be shown ### SNMP v1 If your device only supports SNMPv1, select SNMPv2 and Highlight will fall back to using the older protocol when it finds that SNMPv2 doesn't work. ### SNMP v2 *Create Watch Technical SNMPv2c* * **Community String** — can contain any characters except spaces ### SNMP v3 *Create Watch Technical SNMPv3* * **Username** — must be between 8 and 32 characters and may not contain `,` `'` or `"` * **Auth protocol** — MD5 (default) or SHA1 * **Auth key** — must be between 8 and 32 characters and may not contain `,` `'` or `"` * **Priv protocol** — DES (default) or AES 128 * **Priv key** — must be between 8 and 32 characters and may not contain `,` `'` or `"` **Test** — After all options are completed, the watch can be tested. ## 3. Test Results After clicking **Test** you may briefly see the message *Testing...* *Create Watch Choose Interface* After a successful test, you will be prompted to choose an interface (it's also possible to save the watch without choosing an interface). Immediately after interface selection, you will see *Test successful*. *Create Watch Test Successful* Clicking on **Details** will show additional details related to the test. *Create Watch Test Successful Details* After clicking **Save**, if you then edit the watch, Watch Status and Progress Log will now be visible. *Pending Edit Watch* {% hint style="info" %} The interface list for Draytek devices may contain duplicate names. The interface number will be displayed as a suffix to distinguish between them, for example: WAN2 \[5]. Select the lowest interface number. {% endhint %} *Create Watch Draytek choose interface* ## 4. Watch Status *Pending Watch Status* **Order Management** has two possible states which can be changed by those who have the security privilege Approve New Watches checked in the Add/Edit User dialog: * Approved * Not Approved **Technical Test** has three possible states in this dialog: * Test successful * Test failed * Interface not selected — meaning no interface was selected following a successful test or no interfaces were listed for selection Test in progress, meaning the test has started but not yet completed, is only seen when testing more than one watch so will not appear in this dialog. ## 5. Progress Log *Pending Watch Progress Log* This is a list of automatically added events such as: * Circuit added * Circuit details changed * Approved by order management * Technical test succeeded/failed * Interface selected **Add Entry** — Use to add your own comment. Times are in UTC. --- # 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.highlight.net/admin/pending-snmp/create-watch-snmp.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.