Banner
HomeTOCPrevNextGlossSearchHelp

PDF

Table of Contents

Starting and Stopping the CiscoWorks NetView Interface

Starting and Stopping the CiscoWorks NetView Interface

Starting and Stopping the CiscoWorks NetView Interface

This chapter contains information on starting and stopping the following processes:

The CiscoWorks NetView Interface must have all of the following processes running in order to perform properly.

If you experience problems starting, stopping, or running any of these processes, refer to Appendix C, "Troubleshooting."


SNA Peer-to-Peer Gateway

The SNA Peer-to-Peer gateway must be started in order for the CiscoWorks NetView Interface to transfer converted events and traps from SNMP alarms into SNA alerts and send them to the IBM host. If you do not wish to receive event or trap information from the network, you can stop the SNA Peer-to-Peer gateway.

The following sections describe the process of starting and stopping each function responsible for task completion.


Starting the SNA Peer-to-Peer Gateway

There are two ways you can start the SNA Peer-to-Peer gateway: running the Peer-to-Peer file, p2pconf, manually or using the startp2p script. This manual describes the use of the startp2p script. If you choose not to run the startp2p script, refer to Chapter 5 in the
7.0 SunLink SNA Peer-to-Peer Administrator's Guide for alternative instructions.

The startp2p script performs the following tasks:

Executes the Peer-to-Peer gateway process.

Configures the gateway.

Activates the link between the SNA and UNIX network.

Time Saver: The startp2p script runs the executable for the gateway process, appc, and the configuration of the gateway, your p2pconf input file. If you choose to run startp2p, you do not have to run the appc or the p2pconf programs.

fig_1.gif

To start the SNA Peer-to-Peer gateway, perform the following steps:

Step 1: Log in as the superuser by entering su and the root password.

Step 2: Change to the directory where the Peer-to-Peer programs reside: 

hostname# cd /usr/sunlink/snap2p/p2p_etc

Step 3: Enter the following command syntax to start the SNA Peer-to-Peer gateway for a Token Ring environment:


hostname# startp2p gatewy01 p2pconf1 snacm0 llc0

If you have an SDLC connection, enter the following command syntax instead:

hostname# startp2p gatewy01 p2pconf1 psdlc0 zsi0

The script checks for the mapper or appcs process to ensure it is running.

If you do not correctly enter the command, the system responds with the following syntax usage string:

startp2p <gateway> <p2pconf file> <snacm# | psdlc#> \ <llc# | zsi# | mcps# his#>

Refer to Chapter 5 in your 7.0 SunLink SNA Peer-to-Peer Administrator's Guide for definitions on the command syntax of the startp2p command.


Stopping the SNA Peer-to-Peer Gateway

To close the link between the SNA and UNIX network, use the stopp2p command.

To invoke the stopp2p command, perform the following steps:

Step 1: Log in as the superuser by entering su and the root password.

Step 2: Change to the directory where the Peer-to-Peer programs reside: 

hostname# cd /usr/sunlink/snap2p/p2p_etc

Step 3: Enter the following command syntax to stop the gateway or gateways:


hostname# stopp2p gatewy01

The name of the specific gateway that you want to stop is gatewy01. When the appc process terminates, the corresponding SDLC or LLC device driver is closed as well.

Refer to Chapter 5 in your 7.0 SunLink SNA Peer-to-Peer Administrator's Guide for information on the command syntax of the stopp2p command.


Protocol Conversion Application (PCA)

The PCA converts events and traps so they can be forwarded to the SNA host. If you do not wish to receive event or trap information from the network, you can stop the SNA Peer-to-Peer gateway.

The following sections describe the process of starting and stopping each function responsible for task completion.


Starting the PCA

To start the PCA, perform the following steps:

Step 1: If the SNA Peer-to-Peer gateway is not already running, start it.

In order to start the PCA, the gateway must already be running. Refer to the previous section, "SNA Peer-to-Peer Gateway" for instructions on starting the gateway.

Step 1: On the SNM Console, move your cursor over the PCA glyph on your network map.

Step 2: Pull over to Tools and select PCA Start.

This starts the PCA application and enables event conversion.

Note: If the PCA Start command does not appear under the Glyph menu, return to Chapter 4 and perform the instructions in the section on "Configuring the Protocol Conversion Application (PCA)."


Stopping the PCA

To stop the conversion of events and traps from the PCA to the SNA host, perform the following steps:

Step 1: On the SNM Console, move your cursor over the PCA glyph on your network map.

Step 2: Pull over to Tools and select PCA Terminate.

This stops the PCA application and disables event conversion.


RUNCMD Server

The RUNCMD Server processes RUNCMD requests from the IBM NCCF facility. The RUNCMD Server must be running in order for requests to receive a response. If you choose to disable RUNCMD queries, stop the RUNCMD Server.

The following sections describe the process of starting and stopping each function responsible for task completion.


Starting the RUNCMD Server

To start the RUNCMD Server, perform the following steps:

Step 1: If the SNA Peer-to-Peer gateway is not already running, start it.

In order to start the RUNCMD Server, the gateway must already be running. Refer to the section "SNA Peer-to-Peer Gateway" earlier in this chapter for instructions on starting the gateway.

Step 2: Enter the following command at the UNIX prompt:


hostname% /usr/sunlink/snap2p/runcmd gateway_name &

This enables the NetView operator to perform RUNCMD requests. The ampersand (&) enables this process to work in the background of the current shell.

If you have added the previous directory string to the PATH statement, then all you need to enter is the runcmd gateway_name command.

If you do not start the RUNCMD Server before you issue a request, you will receive error messages on the NetView console.

You can leave the RUNCMD Server running once you start it.


Stopping the RUNCMD Server

If you do not want to receive RUNCMD requests, stop the RUNCMD Server.

Time Saver: From your local workstation, enter the ps command at the UNIX prompt. Then, use the kill command to remove the RUNCMD Server from the active processes list.

fig_2.gif

To stop the RUNCMD Server from the NetView console, perform the following steps:

Step 1: From the NetView console, type the following command at the system prompt:


RUNCMD SP=P05SA56,APPL=SH,PS -VAX | GREP runcmd

This command provides the status of all running processes.

127 ? R 2578:40 0 99 163668823344 xx 31.3 37.5 snmpd
2511 ? R 1242:08 1 99 231 6976 7112 xx 8.2 11.4 runcmd
2487 ? S 0:54 2 99 53 176 380 xx 0.0 0.6 nmlogd
3182 ? IW 0:09 99 99 13 428 0 xx 0.0 0.0 na.snmp-trap
2477 ? IW 0:00 99 99 25 548 0 xx 0.0 0.0 nmpolld
2496 ? IW 0:17 99 99 36 528 0 xx 0.0 0.0 nmeventd
178 ? IW 0:03 99 99 10 404 0 xx 0.0 0.0 na.snmp-trap

Step 2: Identify the RUNCMD Server process ID (pid) number.

The pid of the RUNCMD Server in this example is 2511. This pid closes all open processes, including CiscoWorks processes.

Step 3: Type the following command to stop the RUNCMD Server:


RUNCMD SP=P05SA56,APPL=SH,KILL -9 2511

The RUNCMD Server process stops.

Note: In general, if the UNIX commands have an UPPERCASE CHAR in the command that command does not work.

HomeTOCPrevNextGlossSearchHelp
-

Copyright 1988-1996 © Cisco Systems Inc.