Direct Discovery using Discovery Patterns
Summarize
Summary of Direct Discovery using Discovery Patterns
The Telecommunications Discovery Patterns plugin enhances ServiceNow's Telecom Discovery capabilities by enabling direct discovery of standalone network elements—such as routers and switches—without depending on traditional network management systems (EMS/NMS). This pattern-based approach uses protocols like SNMP, CLI, and NETCONF to discover multivendor xNFs, improving visibility and data accuracy in telecom infrastructures. The discovered data is integrated into the Configuration Management Database (CMDB) and Telecom Network Inventory (TNI), following the Telecom Network Inventory data model for consistent telecom asset representation.
Show less
This functionality is part of the TSOM Visibility subscription and is available as a customer-visible plugin from the ServiceNow Store.
Key Features
- Direct Network Element Discovery: Communicate directly with physical network elements using SNMP, CLI, and NETCONF to discover detailed physical inventory including interface cards, slots, and ports without EMS/NMS mediation.
- Automated CI Mapping and CMDB Integration: Discovered data is automatically mapped to telecom-aligned Configuration Item (CI) classes and integrated with the Identification and Reconciliation Engine (IRE) to ensure accurate, non-duplicate records in the CMDB and TNI.
- CMDB Accuracy and Conformance: Patterns trigger CMDB Conformance Certification Audits to identify discrepancies or outdated records, supporting data integrity and remediation.
- Low-Code Pattern Customization: Use low-code pattern designers to extend or customize discovery patterns to fit specific network architectures and business requirements.
How It Works
Telecommunications Discovery Patterns operate within the Horizontal Discovery framework using Nebula Discovery Language (NDL). Each pattern runs a sequence of steps that establish device connections, execute SNMP and/or CLI commands, extract CI attributes and relationships, and send data to IRE for reconciliation and insertion into the CMDB and TNI.
The discovery logic conforms to the TNI data model, which restructures complex relationships—such as nested cards—into valid telecom configurations, ensuring data accuracy and consistency.
Supported Discovery Patterns and Architecture
ServiceNow provides a set of preconfigured discovery patterns targeting common telecom devices, including generic routers and switches as well as vendor-specific models like Cisco 7613 and Juniper MX routers. These patterns support standalone SNMP and CLI-enabled xNFs and operate within a scalable Horizontal Discovery architecture that collects comprehensive infrastructure data.
Integration with Telecom Network Inventory (TNI)
With the TNI plugin installed, every discovered CI automatically results in a corresponding TNI entity record, ensuring synchronized alignment between operational and inventory systems. This integration supports critical telecom functions such as order fulfillment, assurance, and network planning.
Supporting Components
- MID Server: A local Java application that facilitates secure communication between the ServiceNow instance and external network devices.
- Identification & Reconciliation Engine (IRE): Centralizes identification and reconciliation of CI data from multiple sources, maintaining CMDB integrity by preventing duplicates and ensuring accurate data updates.
Next Steps
To leverage this functionality, install the Horizontal Discovery application and configure the Discovery Patterns plugin. This setup enables direct discovery of telecom network elements for enhanced visibility and data management in your ServiceNow environment.
The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.
Telecommunications Discovery Patterns provide a powerful, pattern-based approach to discover and manage telecom network resources directly from network elements. These patterns are especially valuable for discovering standalone xNFs (such as routers and switches) that are not managed through traditional EMS/NMS systems.
Key capabilities
- Direct Network Element Discovery
- Use SNMP, CLI, and NETCONF to communicate directly with physical network elements.
- Discover physical network inventory such as interface cards, slots, ports, and devices without relying on EMS/NMS mediation.
- Automated CI Mapping and CMDB Integration
- Discovered data is automatically mapped to telecom-aligned Configuration item (CI) classes.
- Integrates directly with the Identification and Reconciliation Engine (IRE) to promote accurate, non-duplicate CI records in the CMDB and Telecom Network Inventory (TNI).
- CMDB Accuracy and Conformance
- Patterns trigger CMDB Conformance Certification Audits to detect mismatches or outdated records.
- Supports discrepancy identification and remediation, helping maintain data integrity.
- Low-Code Pattern Customization: Extend or customize discovery patterns using low-code pattern designers to meet your specific network architecture and business needs.
How it works
Telecommunications Discovery Patterns are executed through Horizontal Discovery using the Nebula Discovery Language (NDL). A pattern is a sequence of steps that:
- Establishes a connection to a target device.
- Executes commands using SNMP, CLI, or both.
- Extracts CI attributes and relationships.
- Sends results to IRE for reconciliation and insertion into the CMDB and TNI.
The discovery logic follows the TNI data model, which restructures complex CI relationships (e.g., card-on-card scenarios) to align with telecom modeling best practices. For example, If a child card is discovered inside a parent card, Telecom Discovery synthesizes a subslot to insert the child, avoiding an invalid card-on-card configuration.
Architecture using Horizontal Discovery and Telecommunications Discovery Patterns
The following infographic is an example of the implementation for standalone SNMP or/and CLI xNFs.
Horizontal Discovery Application
The Horizontal Discovery application in ServiceNow is a versatile and highly scalable discovery engine to operate effectively across network, IT, and cloud environments, collecting data across multiple layers to provide a holistic view of the infrastructure.
For more information, see Horizontal discovery process flow with patterns.
Supported discovery patterns
A pattern is a sequence of commands to detect attributes of a configuration item (CI) and its outbound connections. Telecom Discovery provides a set of preconfigured Patterns that cover a wide range of network elements. ServiceNow offers several base system (BASE SYSTEM) TSOM patterns, including:
- Telecom Router Pattern – Generic SNMP-based router discovery.
- Telecom Cisco 7613 Router Pattern – For Cisco 7613 routers using SNMP.
- Telecom Juniper MX SSH Router Pattern – SNMP + CLI discovery of Juniper MX routers.
- Telecom Cisco Switch Pattern – SNMP-based Cisco switch discovery.
- Telecom Switch Pattern – SNMP-based generic switch discovery.
TNI entity creation
If your instance has the Telecom Network Inventory (TNI) plugin installed:
- Every discovered CI automatically results in a TNI entity record.
- The IRE payload includes mapping to both
cmdb_ciandtni_entitytables.
This ensures seamless alignment between operational and inventory systems, which is essential for order fulfillment, assurance, and network planning.
MID Server
MID Server is a Java application that runs as a Windows service or UNIX daemon on a server within your local network. The ServiceNow® MID Server facilitates communication and data transfer between a ServiceNow instance and external applications, data sources, and services.
For more information, see MID Server.
Identification & Reconciliation Engine (IRE)
IRE offers a centralized framework for identifying and reconciling data from multiple sources. It verifies the integrity of the CMDB and some non-CMDB tables when various data sources are used to create or update CI records.