Diagnostics Configuration Settings
Default settings for Diagnostics can be customized by adjusting the Diagnostic Configuration Settings via the IP/MPLSView Web interface. In the IP/MPLSView Web interface, log in as “admin” and go to Admin > Change Diag Settings. To adjust any of the settings, simply edit the corresponding textfield in the New Value column. Then, scroll down to the bottom of the page and press the “Submit” button. These parameters are described further below.
Only the IP/MPLSView Web administrator (login = “admin”) is allowed to make these adjustments.
Diagnostics Using SSH
By default, diagnostics are performed using telnet. To change the default, Go to Admin > Diagnostics Settings and you should see the screen as shown in Figure 135.
Under the section called Diagnostic Configuration Parameters, there is a Use SSH (instead of telnet) parameter. Set this value to “yes”. Then, press the “Submit” button at the bottom of the page. Now, SSH will be used to access all devices during the various diagnostics tests.
In order for SSH diagnostics to work, you must make sure that the SSH keys have already been accepted. If not, you should log into the device(s) using SSH and accept the keys when prompted.
Table 1: Diagnostic Configuration Ping Parameters
Ping Parameter | Description |
|---|---|
Ping Path | Location on the server of the ping utility to use during any ping operation |
Ping Count | Number of actual pings to issue during a ping operation |
Ping Type of Service (TOS) | Sets the ToS value in the ICMP packet for routers that are set up to treat packets with certain types of service differently than others. Note that ToS is not used very often and most routers ignore it. |
Ping Packet Size (bytes) | Size of the ping packet |
Ping Hex Fill Pattern | A hexadecimal fill pattern to include in the ping packet |
Ping Threshold 1 and 2 (milliseconds) | A ping value that is less than Ping Threshold 1 is “acceptable”. A value greater than or equal to Ping Threshold 1 and less than Ping Threshold 2 will be flagged as “problematic”. A value that is greater than or equal to Ping Threshold 2 will be flagged as “unacceptable”. |
Ping Threshold Colors | Hexadecimal color code indicates the color to display for acceptable, problematic, and unacceptable ping values. |
Table 2: Diagnostic Configuration Trace Parameters
Trace Route Parameter | Description |
|---|---|
Traceroute Timeout (seconds) | Number of seconds to allow the traceroute to run for. |
Traceroute Resolve IP Address | Indicates whether or not to resolve hostnames associated with the IP addresses. 0 = Don’t Resolve; 1 = Resolve. |
Traceroute Type of Service (Juniper only) | Value to include in the IP Type of Service (ToS) field. The range of values is 0 through 255. |
Traceroute Time To Live (TTL) in hops | Maximum TTL value to include in the traceroute request. The range of values is 0 through 128. |
Traceroute Wait Time (for response) in seconds | Maximum time to wait for a response to the traceroute request |
Table 3: Diagnostic Configuration Additional Parameters
Other Parameter | Description |
|---|---|
Show Command Execution Timeout | Number of seconds to allow “show” commands to run for. |
Debug Level | This toggles debuging messages on and off. Users should leave this setting at 0 unless instructed otherwise by Juniper support. |
Table 4: Diagnostic Configuration Device Parameters
Diagnostic Configuration Parameter | Description |
|---|---|
OS Type | This allows the user to select the type of OS on which the server is running. Options include Linux and Solaris. The correct setting is required in some cases for ping and traceroute diagnostics to function properly. |
Diagnostic Login TypeDiagnostic Login Type | This parameter applies to users who have TACACS. For TACACS users, Cisco “show” commands are executed differently, requiring a different login sequence. |
Use SSH (instead of telnet) | Some operations such as “show” commands require the system to log into a device. Use this field to specify whether to use secure shell (SSH) or telnet when logging in. See Diagnostics Using SSH. |
Use Enable Mode | Sets the enable mode when executing “show” commands via the IP/MPLSView Web interface and in the client graphical interface. Default value is “No”. |
Router Profile File | The default router profile file is located in: |
Diag Working Directory | A directory in which the IP/MPLSView system stores temporary results while processing diagnostics data. |
Node Parameter File | The IP/MPLSView node parameter (nodeparam) file. This file is used to correlate IP addresses with device hostnames. |
Hardware Mapping File | The hardwaretypemapping.csv file contains a mapping of recognized device models with their vendors. |
Vendor Configuration File | The vendortemplatefile.csv file contains a mapping of vendor, command template, and icon used. |
Command Template Directory | The command template directory contains templates for each vendor to specify which commands are issued on the devices immediately after logging in. |
General Show Command File | The location of the file containing general “show” commands. The default location is in $INSTALLDIR/db/config/shownodecmds. Whatever commands are listed in this file will appear in the drop-down selection box when user issues a “show” command to a device from either the IP/MPLSView Web interface or IP/MPLSView client. |
VPN Show Command File | Similar to the General Show Command File, this parameter specifies the location of the file in which vpn-related “show” commands are saved. The default location is: $INSTALLDIR/db/config/showvpncmds. |