Switch Details Test

The Routing Engine runs the Junos OS. Software processes that run on the Routing Engine maintain the routing tables, manage the routing protocols used on the router, control the router interfaces, control some chassis components, and provide the interface for system management and user access to the router.

You can install one or two Routing Engines in the router. Each Routing Engine must be installed directly into an SCB. A USB port on the Routing Engine accepts a USB memory device that allows you to load Junos OS. The Routing Engines install into the front of the chassis in vertical slots directly into the SCBs labeled 0 and 1. If two Routing Engines are installed, one functions as the master and the other acts as the backup. If the master Routing Engine fails or is removed and the backup is configured appropriately, the backup takes over as the master.

This test reports the mode of each routing engine available in the Juniper EX Switch.

Target of the test : A Juniper EX Switch

Agent deploying the test : An external agent

Outputs of the test : One set of results for each hardware component of the Junpier EX Switch that is to be monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


The IP address of the host for which this test is to be configured.


The port at which the monitored target exposes its SNMP MIB; The default value is 161.


By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPVersion list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list.


The SNMP community name that the test uses to communicate with the firewall. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVersion chosen is v3, then this parameter will not appear.


This parameter appears only when v3 is selected as the SNMPVersion. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against this parameter. 


This parameter appears only when v3 is selected as the SNMPVersion. An SNMP context is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context and an SNMP entity potentially has access to many contexts. A context is identified by the SNMPEngineID value of the entity hosting the management information (also called a contextEngineID) and a context name that identifies the specific context (also called a contextName). If the Username provided is associated with a context name, then the eG agent will be able to poll the MIB and collect metrics only if it is configured with the context name as well. In such cases therefore, specify the context name of the Username in the Context text box.  By default, this parameter is set to none.


Specify the password that corresponds to the above-mentioned Username. This parameter once again appears only if the SNMPVersion selected is v3.

Confirm Password

Confirm the AuthPass by retyping it here.


This parameter too appears only if v3 is selected as the SNMPversion. From the Authtype list box, choose the authentication algorithm using which SNMP v3 converts the specified username and password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:

  • MD5 – Message Digest Algorithm
  • SHA – Secure Hash Algorithm


This flag appears only when v3 is selected as the SNMPversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the this flag is set to No by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the Yes option. 


If this EncryptFlag is set to Yes, then you will have to mention the encryption type by selecting an option from the EncryptType list. SNMP v3 supports the following encryption types:

  • DES – Data Encryption Standard
  • AES – Advanced Encryption Standard


Specify the encryption password here.

Confirm Password

Confirm the encryption password by retyping it here.


Specify the duration (in seconds) within which the SNMP query executed by this test should time out in this text box. The default is 10 seconds.

Data Over TCP

By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic – for instance, certain types of data traffic or traffic pertaining to specific components – to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the monitored target over TCP (and not UDP). For this, set this flag to Yes. By default, this flag is set to No.

Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates the mode of this routing engine.


The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value Numeric Value
Unknown 1
Master 2
Backup 3
Disabled 4


This measure reports the Measure Values listed in the table above to indicate the mode of this routing engine. However, in the graph of this measure, the mode of the routing engine is indicated using only the Numeric Values listed in the above table.