--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Network router # Network router discovery using patterns {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Network router discovery using patterns The Discovery and Service Mapping Patterns application in ServiceNow utilizes the Network Router pattern to identify and document network routers within your IT environment. To discover certain routers effectively, ensure you have the latest version of the Discovery and Service Mapping Patterns app installed from the ServiceNow Store. This discovery process enriches the CMDB by populating detailed router-related configuration items (CIs) and their relationships. Show full answer Show less ## Prerequisites * Keep Discovery and Service Mapping Patterns and Visibility content up to date. * Ensure routers have valid IP address information for successful discovery. * Verify routers have exit interface routing rules configured and that these routers are reachable. * Create appropriate SNMP Community or SNMPv3 credentials to enable SNMP-based discovery. * Set the **glide.discovery.L3mapping** system property to **true** to enable router discovery. * For Cisco Nexus VRF discovery, use version 1.35.1 or later and create SSH credentials with required command read permissions. ## Configurable Properties Several system properties help tailor the discovery process: * **glide.discovery.maxconcurrentinvocationsperschedule**: Limits concurrent discovery runs per schedule to prevent backlog, defaulting to 3. * **glide.discovery.bgprouterdisable**: By default, disables SNMP routing pattern on BGP routers to avoid performance issues; set to false if Device Neighbors data is needed. * **glide.discovery.disablenexthopdata**: When set true (and BGP router discovery enabled), skips collecting next-hop routing rules to reduce MID Server load. ## Data Collected and CMDB Impact The discovery populates several key CI classes and fields into the CMDB, including: * **IP Router \[cmdbciiprouter\]**: Captures router name, model, manufacturer, serial number, IP addresses, capabilities (routing, VLAN partitioning, switching), physical interfaces, and discovery protocols. * **IP Address \[cmdbciipaddress\]**: Stores IP addresses, netmasks, and associations to network adapters and VRFs (for Cisco Nexus VRF discovery). * **Network Adapter \[cmdbcinetworkadapter\]**: Details about network adapters including IP, MAC, alias, and relationship to routers. * **DNS Name, VRF CIs**: Includes DNS names and VRF details linked to routers, specifically for Cisco Nexus VRF discovery. ## CI Relationships and References The pattern creates and maintains numerous relationships between routers and associated components such as IP addresses, network adapters, routing rules, interfaces, and VLAN partitions. These relationships enable a comprehensive and accurate network topology representation within the CMDB. ## Performance and Optimization To optimize discovery performance and MID Server resource usage, especially when discovering BGP-enabled routers, you can disable certain data collections (e.g., next-hop routing rules) using provided system properties. This helps prevent issues such as MID Server out-of-memory errors during horizontal layer 2 discovery. ## What This Enables for ServiceNow Customers By leveraging this discovery pattern, customers can automatically and accurately map network routers and their configurations into the CMDB. This supports enhanced network visibility, impact analysis, and service mapping. Understanding and configuring required credentials, system properties, and prerequisites ensures a smooth discovery experience and reliable network data for operational decision-making. The Discovery and Service Mapping Patterns application uses the Network Router pattern to find network routers in your environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. ## Request apps on the Store {#network-router-patterns__id_z4l_ysx_rcc} Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#network-router-patterns__inline-send-to-store} To learn about network routers and their versions that you can discover, refer to [Detailed information on products discovered by ITOM Visibility](https://www.servicenow.com/docs/mNB7NqS~kRULRDp~CJup5g "Discovery and Service Mapping can discover a wide range of operating systems and applications."). For information on probe-based network switch and router discovery, see [Network switch and router discovery](https://www.servicenow.com/docs/cJ68d2j8JPtoBYLE7uV21A "Discovery identifies and classifies information about network switches and routers."). ## Cisco Nexus Virtual Routing and Forwarding (VRF) data model {#network-router-patterns__id_nkl_gcx_xjc} The pattern introduces the following CI class starting with Discovery and Service Mapping Patterns version 1.35.1.{#network-router-patterns__table_ibs_21x_xjc__entry__2} | CI class | Extends from | |-|-| | Virtual Routing and Forwarding (VRF) \[cmdb_ci_virtual_routing_forwarding\] | Configuration Item \[cmdb_ci\] | [Table 1. CI class hierarchy] {#network-router-patterns__table_ibs_21x_xjc} ## Prerequisites {#network-router-patterns__section_mlg_mcm_zfc} Verify that the applications are up to date : * Discovery and Service Mapping Patterns * Visibility Content {#network-router-patterns__ul_a1l_d5x_rcc} Verify IP address information : The router must contain IP address information for successful discovery. Verify that exit interface routing rules are configured and reachable : The router that provides the IP address must have exit interface routing rules configured and be reachable for successful discovery. Create SNMP credentials : Create SNMP Community Credentials or SNMPv3 credentials. For more information, see [SNMP credentials](https://www.servicenow.com/docs/access?context=c_SNMPCredentials&version=yokohama). Configure properties for router discovery : Navigate to sys_properties.list and verify that the glide.discovery.L3_mapping system property is set to true. : You can configure these additional properties for network router discovery. {#network-router-patterns__table_ljq_hnr_hkc__entry__2} | System property | Description | |-|-| | glide.discovery.max_concurrent_invocations_per_schedule | Sets a maximum number of scheduled invocations for the same Discovery schedule. It prevents a backlog of scheduled runs if Discovery does not finish before the next one starts. The value is an integer that represents the max number of automated invocations that can run concurrently for the same schedule. If the limit is reached, subsequent scheduled invocations are canceled. A value of 0 or any negative number disables this property. * Type: integer * Default value: 3 {#network-router-patterns__ul_s15_gqw_qbb} Note: This property does not apply to schedules that have a 'Run after' configuration set to 'Even if canceled'. | | glide.discovery.bgp_router_disable | Disables running the SNMP -- Routing pattern when discovering a router running the BGP protocol. If you must populate the Device Neighbors \[discovery_device_neighbors\] table during horizontal layer 2 discovery of the BGP-enabled devices, set the glide.discovery.bgp_router_disable property to false. Notice that enabling this property can cause performance issues including out-of-memory issues on the MID Server. * Type: Boolean * Default value: true {#network-router-patterns__ul_iwf_cg1_1gc} | | glide.discovery.disable_next_hop_data | Skips populating the Next Hop Routing Rule table for BGP-enabled routers during horizontal discovery. The device, its physical interfaces, and its neighbors are still discovered. This property takes effect only when theglide.discovery.bgp_router_disable property is set to false. * Type: Boolean * Default value: false For more information, see [Turn off next-hop route data collection for BGP routers](https://www.servicenow.com/docs/Gha5EfBChN3AsqwJPvFMYg "You can turn off Next Hop Routing Rule [dscy_route_next_hop] table collection for BGP-enabled routers to reduce MID Server memory load during router discovery."). | [Table 2. Optional network router discovery properties] {#network-router-patterns__table_ljq_hnr_hkc} For Cisco Nexus VRF discovery : Verify the following requirements: * Discovery and Service Mapping Patterns starting from version 1.35.1. * Read permissions for the following commands on the Cisco Nexus device: * `sh vrf` * `sh hsrp br` * `sh ip interface vrf all` * `sh ipv6 interface vrf all` {#network-router-patterns__ul_lvs_yww_xjc} * Create SSH credentials for the Cisco Nexus user. For more information, see [SSH credentials](https://www.servicenow.com/docs/access?context=r_SSHCredentialsForm&version=australia&pubname=australia-platform-security&ft:locale=en-US). {#network-router-patterns__ul_yrk_jww_xjc} ## Data collected by Discovery during horizontal discovery {#network-router-patterns__section_qyd_hgn_zfc} Discovery populates the data in the CMDB when running the Network Router pattern. {#network-router-patterns__table_fyh_ngn_zfc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the router. | | Model ID \[model_id\] | Hardware model ID of the router. | | Manufacturer \[manufacturer\] | Router manufacturer. | | Serial number \[serial_number\] | Unique hardware serial number of the router. | | IP Address \[ip_address\] | IP addresses assigned to interfaces. | | Description \[short_description\] | Device description. | | Can route IP \[can_route\] | Indicates whether the IP pockets can be routed between networks. Possible values are true or false. | | Can partition VLANs \[can_partitionvlans\] | Indicates whether the local area network (LAN) can be partitioned. Possible values are true or false. | | Can switch IP \[can_switch\] | Indicates whether a network device has Layer 2 switching capabilities. Possible values are true or false. | | Physical interface count \[physical_interface_count\] | Number of physical interfaces. | | Ports \[ports\] | Individual network interface (physical or logical) used to connect devices such as computers, servers, access points, or uplinks to switches or routers. | | Discovery Protocol ID \[discovery_proto_id\] | Unique identifier of the device participating in the Cisco Discovery Protocol (CDP) or Link Layer Discovery Protocol (LLDP) protocol. | | Discovery Protocol Type \[discovery_proto_type\] | Protocol type. Possible values are CDP or LLDP. | [Table 3. IP Router \[cmdb_ci_ip_router\]] {#network-router-patterns__table_fyh_ngn_zfc} {#network-router-patterns__table_lgw_ghn_zfc__entry__2} | Field | Description | |-|-| | IP Address \[ip_address\] | IP address of the router. | | Netmask \[netmask\] | Netmask of the router. | | Nic \[nic\] | References the Network Adapter \[cmdb_ci_network_adapter\] table. | | Owned By Configuration Item \[owned_by_cmdb_ci\]\* | References the Virtual Routing and Forwarding (VRF) \[cmdb_ci_virtual_routing_forwarding\] table | [Table 4. IP Address \[cmdb_ci_ip_address\]] {#network-router-patterns__table_lgw_ghn_zfc}\* Populated for Cisco Nexus VRF discovery only. {#network-router-patterns__table_vt2_khn_zfc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the network adapter. | | IP Address \[ip_address\] | IP address of the network adapter. | | Netmask \[netmask\] | Netmask of the network adapter. | | MAC Address \[mac_address\] | MAC address of the network adapter. | | Alias \[alias\] | User-assigned name for the network adapter. | | Configuration Item \[cmdb_ci\] | References the IP Router \[cmdb_ci_ip_router\] table. | [Table 5. Network Adapter \[cmdb_ci_network_adapter\]] {#network-router-patterns__table_vt2_khn_zfc} {#network-router-patterns__table_v3l_nhn_zfc__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the Domain Name System (DNS). | | IP Address \[ip_address\] | IP address of the DNS. | [Table 6. DNS Name \[cmdb_ci_dns_name\]] {#network-router-patterns__table_v3l_nhn_zfc} {#network-router-patterns__table_yls_1mr_yjc__entry__2} | Field | Description | |-|-| | Name \[name\] | VRF name as configured on the network device. | | VRF ID \[vrf_id\] | VRF identifier assigned by the network device operating system (OS). | | Display Name \[display_name\] | Display name composed of the VRF name and the associated network device name. | | Configuration Item \[configuration_item\] | References the IP Router \[cmdb_ci_ip_router\] table. | [Table 7. Virtual Routing and Forwarding (VRF) \[cmdb_ci_virtual_routing_forwarding\]\*] {#network-router-patterns__table_yls_1mr_yjc}\* Populated for Cisco Nexus VRF discovery only. ## CI relationships {#network-router-patterns__section_m1t_shn_zfc} Discovery creates these relationships and references to support the network router discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table. {#network-router-patterns__table_iw3_vhn_zfc__entry__3} | CI | Relationship | CI | |-|-|-| | IP Router \[cmdb_ci_ip_router\] | Contains::Contained by | Switch Forwarding Rule \[dscy_swtch_fwd_rule\] | | IP Router \[cmdb_ci_ip_router\] | Contains::Contained by | Switch Partition \[dscy_swtch_partition\] | | IP Router \[cmdb_ci_ip_router\] | Contains::Contained by | Switchport \[dscy_switchport\] | | IP Router \[cmdb_ci_ip_router\] | Owns::Owned by | IP Address \[cmdb_ci_ip_address\] | | IP Router \[cmdb_ci_ip_router\] | Owns::Owned by | Network Adapter \[cmdb_ci_network_adapter\] | | IP Router \[cmdb_ci_ip_router\] | Uses::Used by | Exit Interface Routing Rule \[dscy_route_interface\] | | IP Router \[cmdb_ci_ip_router\] | Uses::Used by | Next Hop Routing Rule \[dscy_route_next_hop\] | | IP Router \[cmdb_ci_ip_router\] | Uses::Used by | Router Interface \[dscy_router_interface\] | | Network Adapter \[cmdb_ci_network_adapter\] | Owns::Owned by | IP Address \[cmdb_ci_ip_address\] | | IP Router \[cmdb_ci_ip_router\] | Owns::Owned by | Virtual Routing and Forwarding (VRF) \[cmdb_ci_virtual_routing_forwarding\]\* | | Virtual Routing and Forwarding (VRF) \[cmdb_ci_virtual_routing_forwarding\] | Contains::Contained by | IP Address \[cmdb_ci_ip_address\]\* | [Table 8. CI relationships] {#network-router-patterns__table_iw3_vhn_zfc}\* Created for Cisco Nexus VRF discovery only. {#network-router-patterns__table_vcn_sgx_xjc__entry__3} | CI/Table | Field | Referenced CI | |-|-|-| | Network Adapter \[cmdb_ci_network_adapter\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Network ARP Table \[discovery_net_arp_table\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Next Hop Routing Rule \[dscy_route_next_hop\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Router Interface \[dscy_router_interface\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Serial Number \[cmdb_serial_number\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Switch Bridge Port Table \[discovery_switch_bridge_port_table\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Switch Forwarding Rule \[dscy_swtch_fwd_rule\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Switch Forwarding Table \[discovery_switch_fwd_table\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Switch Partition \[sdcy_swtch_partition\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Switch Spanning Tree Table \[discovery_switch_spanning_tree_table\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Switchport \[dscy_switchport\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | Exit Interface Routing Rule \[dscy_route_interface\] | Configuration Item \[cmdb_ci\] | IP Router \[cmdb_ci_ip_router\] | | IP Address \[cmdb_ci_ip_address\] | Nic \[nic\] | Network Adapter \[cmdb_ci_network_adapter\] | | IP Address \[cmdb_ci_ip_address\] | Owned By Configuration Item \[owned_by_cmdb_ci\] | Virtual Routing and Forwarding (VRF) \[cmdb_ci_virtual_routing_forwarding\]\* | | Virtual Routing and Forwarding (VRF) \[cmdb_ci_virtual_routing_forwarding\] | Configuration Item \[configuration_item\] | IP Router \[cmdb_ci_ip_router\]\* | [Table 9. CI references] {#network-router-patterns__table_vcn_sgx_xjc}\* Populated for Cisco Nexus VRF discovery only. * **[Turn off next-hop route data collection for BGP routers](https://www.servicenow.com/docs/Gha5EfBChN3AsqwJPvFMYg)** You can turn off Next Hop Routing Rule \[dscy_route_next_hop\] table collection for BGP-enabled routers to reduce MID Server memory load during router discovery.