---
sourceDocument: Yokohama Telecommunications Service Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/telecom-service-ops

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Telecom Juniper MX SSH Router Pattern

# Telecom Juniper MX SSH Router Pattern {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

The ServiceNow® Telecom Discovery application uses the Telecom Juniper MX SSHRouter discovery pattern to find SNMP and CLI -based Juniper MX Series routers in the network. Discovering some of these resources requires
updating the Telecommunications Discovery Patterns (TSOM Patterns) from the ServiceNow® store.

Telecom Discovery uses the Telecommunications Discovery Patterns to run Horizontal Discovery. This Telecommunications Discovery Pattern uses a set of SNMP requests to find and classify CLI over SSH to discover network elements.

Telecom Juniper MX SSH Router pattern is part of the Telecommunications Discovery Patterns application (sn_tsom_patterns), which is part of TSOM Visibility.

## Request apps on the Store {#telecom-juniper-mx-ssh-router-pattern__section_irz_2lk_zdc}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website 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).{#telecom-juniper-mx-ssh-router-pattern__inline-send-to-store}

## Prerequisites {#telecom-juniper-mx-ssh-router-pattern__section_mbp_2xn_zdc}

* Subscription to TSOM.
* Verify that your network router devices have SNMP access.
* On the ServiceNow instance, configure SNMP credentials. For more information, see [SNMP support for Discovery](https://www.servicenow.com/docs/access?context=c_SNMPSupportForDiscovery&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US).
* For setting up TSOM Patterns, see [Configure Telecommunications Discovery (TSOM) Patterns](https://servicenow-prod.fluidtopics.net/nco9q0vAZvRynA_Z0~wUfA#configuring-telecommunications-discovery-patterns "This document outlines the dependencies, requirements, and installation steps necessary for setting up Telecommunications Discovery Patterns (also known as TSOM Patterns) in TSOM Visibility in ServiceNow.").
{#telecom-juniper-mx-ssh-router-pattern__ul_hbf_fxn_zdc}

## Impacted CMDB CIs and CI Relationships (Physical Layer) {#telecom-juniper-mx-ssh-router-pattern__section_hrv_3xn_zdc}

{#telecom-juniper-mx-ssh-router-pattern__table_bhm_kxn_zdc__entry__2}

| CIs | CI Relationships |
|-|-|
| IP Router CI | IP Router Device is represented by the IP Router CI. Table name: **cmdb_ci_ip_router** IP Router CI contains Slots or Network Interfaces. |
| Slot CI | Slots are represented by the Slot CI. Table name: **cmdb_ci_container_slot** Slot is contained by the IP Router. Slot CI contains the Interface Card. |
| Subslot CI | Subslots are represented by the Subslot CI. Table name: **cmdb_ci_container_subslot** Subslot is contained by Interface Card CI. Subslot CI contains the Interface Card CI. |
| Interface Card CI | Different types of cards are represented by the Interface Card CI. Fan and Power Supply Units are also represented by the Card CI. Table name: **cmdb_ci_interface_card** Interface Cards are contained by Slots or Subslots. Interface Cards can contain Network Interface or Subslots. |
| Network Interface CI | Any type of Network Interface is represented by the Network Interface CI. Table name: **cmdb_ci_ni_interface** Network Interface is contained by Interface Card, IP Router. |
[ ]

{#telecom-juniper-mx-ssh-router-pattern__table_bhm_kxn_zdc}

## Classifying xNFs for this Pattern {#ariaid-title2}

To access a full list of OIDs that will be classified.

### Before you begin

Role required: admin

Classifier name: Standard Network Router.

### Procedure

1. Navigate to AllDiscovery DefinitionCI ClassificationSNMP.
2. From the list, select Standard Network Router.
3. Open the tab SNMP OID Classifications and see the list of OIDs.  
   Note:  
   For more information on how to add additional OIDs to the classifier, see [Telecom Discovery using Telecommunications Discovery Patterns](https://servicenow-prod.fluidtopics.net/FrwTTYiFXdQLq6ZdWRf_4Q "The new Telecommunication Discovery Patterns (also known as TSOM Patterns) include patterns for discovering standalone xNFs. These patterns enable the discovery of standalone network elements without a management system, using SNMP, CLI, and NETCONF (roadmap) protocols.").  
   The List of Specific OIDs to call this Pattern:

   |-|-|-|-|
   | **Vendor** | **Model** | **OID** | **Pattern** |
   | Juniper | MX80 | 1.3.6.1.4.1.2636.1.1.1.2.57 | Telecom Juniper MX SSH Router |
   | Juniper | MX104 | 1.3.6.1.4.1.2636.1.1.1.2.97 | Telecom Juniper MX SSH Router |
   | Juniper | MX240 | 1.3.6.1.4.1.2636.1.1.1.2.29 | Telecom Juniper MX SSH Router |
   | Juniper | MX480 | 1.3.6.1.4.1.2636.1.1.1.2.25 | Telecom Juniper MX SSH Router |
   [ ]

   {#classifying-xnfs-juniper-router-pattern__table_cfq_qmf_b2c}

   MiB Tables Used on an xNF: SystemMIB.  
   CLI Commands Used.
   * show chassis hardware \| no-more \| display xml
   * show interface media \| no-more \| display xml
   {#classifying-xnfs-juniper-router-pattern__ul_wl3_5mf_b2c}

*[\>]: and then