The PSM client makes use of external executables for the following utilities:
The PSM client is preconfigured to provide these utilities using specific executables on your computer. You can customize where the PSM client looks for these executables. If the network element being managed requires a specific node controller executable, you can also specify where that node controller executable can be found.
Setting Utility Executables
Use this procedure to configure the CLI, Ping, SNMP Ping, and Traceroute utility executables and parameters.
To use SNMP Ping on Windows, net-snmp or a similar application must be installed. See Installing Net-SNMP.
- Select Tools >Options.
The Options window is displayed.
- Click the Utilities tab.
The Utilities panel is displayed.
- For each tab in the Utilities panel,
specify the desired executables and parameters.
Select the utility that you want to configure (CLI, Ping, SNMP Ping, Traceroute).
Select the Network Element Type from the drop-down menu.
If you want to apply your changes to all network element types, then leave the Type at Default. If you want to tailor the executable to a particular type of network element, then select the specific type from the drop-down menu.
Once you make a change to the parameters of a specific type of network element, the Default parameters no longer apply for that type of network element.
Select the Network Element Version from the drop-down menu.
If you want to apply your changes to all versions of the selected network element type, then leave the Version at Default. If you want to tailor the executable to a particular version of the selected network element type, then select the specific version from the drop-down menu.
Once you make a change to the parameters of a specific version, the Default parameters no longer apply for that version of network element.
Specify the command syntax for the selected utility.
You can specify the name and path to the executable and the parameters to use.
For example, the command to launch the CLI (
C:\Users\user\Desktop\putty.exe -ssh -P 22 <login_username>@<IP_address_of_selected_NE>) is represented by this configuration:
<username>construct is a variable that represents the username of the current PSM user (that is, the username you used to log in to the current PSM client session). The
<address>construct is a variable that represents the IP address of the selected NE. The above configuration launches the putty.exe executable from the specified path and sets up an SSH connection to the selected NE using the username of the current PSM user.
If you are running putty.exe on Windows and you want to explicitly specify the username when launching the CLI, then remove the
<username>construct. For example:
This forces putty.exe to prompt you for the username to use when you launch the CLI.
The above are examples of applications and parameters to use. The validity of the parameters depends on the application chosen.
- When you are done, click OK.
This procedure is complete.
To connect to the CLI, see Connecting to the CLI on a Network Element. To launch the Node Controller on the BTI7000, see Launching the proNX 900 Node Controller. To launch the other utilities, see Performing Diagnostics.
Configuring the proNX 900 Node Controller
Use this procedure to configure how to launch the proNX 900 Node Controller.
The proNX 900 Node Controller is the nodal manager for the BTI7000 Series network elements.
The proNX 900 Node Controller might not be supported on all PSM client platforms. See the BTI7000 Series Common Equipment Installation Guide for a list of platforms that support the proNX 900 Node Controller.
The proNX 900 Node Controller software that is compatible with the network elements in your network must be installed on your local computer.
- From the main menu, choose Tools>Options.
The Options window is displayed.
- Click the Utilities button and then click the Node Controller tab.
- There are several methods by which you can specify the
path to the proNX 900 application software on your local computer:
If all of your versions of proNX 900 are in one directory, you can browse to that directory and select it. Afterwards, when you launch proNX 900, PSM chooses the correct version of the proNX 900 for the selected NE and launches it. If it cannot find an exact match, PSM chooses the best match and prompts you to confirm. Continue at 4.
Manually determine the path to the executable file for each NE type and version, and then copy and paste the path into the proNX 900 Node Controller tab for that version. Continue at 5.
- To browse
to and select the directory that contains the desired proNX 900 version(s),
click the Install tab and perform the following steps.
Click Browse and navigate to the proNX 900 installation directory, for example:
C:\Program Files (x86)\BTI\
If you are running the PSM Client on a 32-bit Windows operating system, you might need to specify a different path for the installation directory, for example:
Select the directory and click Open.
The path to the directory is pasted into the Install Directory field.
This procedure is complete. You can now launch the proNX 900 as instructed in the first step.
- To manually cut and paste the path to the executable file, click
the Command tab and perform the following steps.
Select the NE Type and proNX 900 Version that you want to launch from the drop-down menus.
In your file system, navigate to the proNX 900 executable file, for example
C:\Program Files (x86)\BTI\proNX900_9.3.0_C001\proNX900.exe. Copy the entire path.
In the first line of the Command window, paste the new path to the proNX 900 application executable file over the existing path shown. The first image shows an unaltered command string in the first line, and the second image shows the command string after the path to the executable file has been pasted in.
In the same command window, scroll down and check the user ID (uid) and password (pid) as follows:
if you want to launch the proNX 900 without requiring the user to log in, ensure that the user ID (uid) and password (pid) are the same as the NE user ID and password.
alternatively, you can remove the user ID and password in the command window, forcing the user to log in when the proNX 900 launches.
As desired, repeat these steps for each NE Type and Version of proNX 900. When you are finished click OK.
This procedure is complete.