Documentation Index

Fetch the complete documentation index at: https://docs.crossworkassurance.cisco.com/llms.txt

Use this file to discover all available pages before exploring further.

  • Skylight Documentation
  • Latest Documentation
  • 25.7

✨ New: Try our AI‑powered Search (Ctrl + K) — Read more

Setting Up a Discovery Configuration Job

  • Updated on Apr 21, 2026
  • Published on Mar 20, 2026
  • 4 minute(s) read
Prev Next

A Cisco® Crosswork Assurance Sensor Control can be connected to a number of Cisco Assurance Module and Cisco Assurance SFP devices that serve as remote ports for the Sensor Control.

You can use a configuration job to allow the Sensor Control to discover Cisco Assurance Module and Cisco Assurance SFP devices on the network. This section explains how to do that.

You can also use configuration jobs to do other tasks related to Cisco Assurance Module and Cisco Assurance SFP devices associated with a Sensor Control. For more information, see these sections:

  • "Setting Up an Cisco Assurance Module Configuration Job"
  • "Setting Up a DMM Reflector Configuration Job"
  • "Setting Up a Firmware Upgrade Configuration Job"
  • "Setting Up a Loopback Configuration Job"
  • "Setting Up a TWAMP Reflector Configuration Job"
  • "Setting Up a Virtual Connection (VCE) Configuration Job".

To set up a Discovery configuration job

  1. Access the page Commission â–¶ Jobs.

  2. Set all common configuration job settings, as described in "Creating Configuration Jobs in GUI Mode" and in "Creating Configuration Jobs Using Data Sets".

  3. Select the Discovery configuration step in the left pane.The Discovery configuration tab is displayed.
    Setting Up a Discovery Configuration Job.png

  4. Complete all fields of the Discovery configuration tab as required. For more information on specific parameters, see the table below.

  5. Use the Add Button_New_Generic.png button or Duplicate Button_Duplicate.png button to add Discovery settings as required.
    Note: When duplicating a row, always select the row to duplicate before clicking the Duplicate  Button_Duplicate.png button.

  6. Click Apply, then Close.

  7. Click the Refresh Button_Refresh_Generic.png button to refresh the user interface.

Discovery configuration tab (Commission â–¶ Jobs)

General

Parameter Description
State Use this checkbox to set the Administrative State of the discovered Cisco Assurance Module.

Possible values:

  • Checked (In Service).
  • Unchecked (Out of Service).
Interface The logical (i.e., network) interface to use when discovering remote devices, such as LOCAL-2.The logical interface is bound to the server’s local ports, meaning that the logical interfaces defined in Port ▶ Configuration are the same ones bound to the local ports.

Note: Applies to ACP Layer-2 discovery instances only.
Name Name to assign to the discovered Cisco Assurance Module.
Discovery method Select a method to use to discover Cisco Assurance Modules on the network.

Possible values:

  • acp-l2 (ACP Layer-2): Select this method to discover Cisco Assurance Modules in Layer-2.
  • ipad (IP Agnostic Discovery protocol ): Suitable for both Layer-2 and Layer-3 networks. You will need to supply an IP address for a specific module or for a subnet to be scanned.
Discovery mode This parameter is only required if ipad is selected as the Discovery method.

Select a mode to use when discovering Cisco Assurance Modules on the network. The mode determines the delivery method and scope of Layer-3 discovery messages.

Possible values:

  • unicast-directed: Expects a destination IP address assigned to a specific Assurance Sensor SFP or Cisco Assurance Module. This type of discovery message is typically used to ensure that a specific remote device is reachable.
  • unicast: Expects a host destination IP address assigned to a network device other than a Cisco Assurance Module or Assurance Sensor SFP module.
  • subnet: Expects a destination IP address for a subnet. The Sensor Control will send multiple unicast discovery messages to ensure that the entire subnet is covered.

Note: Subnet discovery mode does not support Layer-3 multicast messages. It requires a message rate of at least 60 seconds (one message per minute). A rate of five minutes is recommended.
Rate Set the rate at which discovery messages will be sent.

Possible values:

  • one-shot: A one-time, single-use message.
  • 3sec: Messages sent automatically every three seconds.
  • 60sec: Messages sent automatically every 60 seconds.
  • 5min: Messages sent automatically every five minutes. This is the recommended setting. Sending messages more often than this creates excess traffic.
  • 10min: Messages sent automatically every 10 minutes.
  • 60min: Messages sent automatically every 60 minutes.
Timeout (s) This parameter is only used if ipad is selected as the Discovery method.

Set the period of time (in seconds) after which discovery messages (sent by the Sensor Control) expire. After this amount of time, the Sensor Control will stop listening for reply messages (advertisements) from Cisco Assurance Modules.
Hop limit This parameter is only used if ipad is selected as the Discovery method.

Set the maximum number of hops that the discovery messages can go through in order to discover Cisco Assurance Modules.
Serial number This parameter is only used if:
  • ipad is selected as the Discovery method and
  • unicast-directed is selected as the Discovery mode.

Enter the serial number of a performance if you want to discover a specific device.
Destination IP This parameter is only used if ipad is selected as the Discovery method.

Set the IP address of a specific Assurance Sensor SFP or Cisco Assurance Module or another network device. You can also indicate a subnet that will be scanned to discover all reachable Assurance Sensor Modules.
Netmask This parameter is only used if:
  • ipad is selected as the Discovery method
  • subnet is selected as the Discovery mode.

Set the subnet mask to be used with the Destination IP address.

Maximum subnet size is 23 bits (255.255.254.0), which provides a total of 512 addresses.

© 2026 Cisco and/or its affiliates. All rights reserved.

For more information about trademarks, please visit: Cisco trademarks 
For more information about legal terms, please visit: Cisco legal terms


© 2026 Cisco Privacy Statement Cookies Legal