5
Configuring Net8

• Supplementary Documentation

• Core Net8 Products and Features

• Net8 Protocol Support

• The BEQ Protocol

• The IPC Protocol

• The RAW Protocol

• The TCP/IP Protocol

• The SPX/IPX Protocol

• The APPC/LU6.2 Protocol

• Net8 Naming Support

• Oracle Enterprise Manager (OEM)

• Configuring Oracle Intelligent Agent for Oracle SNMP

• Oracle Advanced Security Option

Supplementary Documentation

The following documents provide a full discussion of Net8 features:

• Oracle Net8 Administrator's Guide

• Oracle Networking Quick Reference Card for Net8

• Oracle Advanced Security Option Administrator's Guide

• Oracle Cryptographic Toolkit Programmer's Guide

Supplementary Information in README Files

Table 5-1 shows the location of README files for various bundled products. The README files describe changes since the last release.

Table 5-1 Location of README Files for Oracle Products

Core Net8 Products and Features

Net8 Files and Utilities

Location of Net8 Configuration Files

The default directory for global Net8 and Connection Manager files is /var/opt/oracle on Solaris.

Net8 and Connection Manager search for global files in the following order:

1. The directory specified by the environment variable, TNS_ADMIN, if set.

2. The /var/opt/oracle directory.

3. $ORACLE_HOME/network/admin.

If your files are not in the default directory, use the TNS_ADMIN environment variable in the startup files of all network users to specify a different location:

For the C shell, enter:

% setenv TNS_ADMIN directory_name

For each system level configuration file, users may have a corresponding local private configuration file (stored in the user's home directory). The settings in the private file override the settings in the system level file. The private configuration file for sqlnet.ora is $HOME/.sqlnet.ora. The private configuration file for tnsnames.ora is $HOME/.tnsnames.ora. Syntax for these files is identical to that of the corresponding system files.

Sample Configuration Files

Examples of the cman.ora, listner.ora, names.ora, sqlnet.ora, and tnsnames.ora configuration files are located in
$ORACLE_HOME/network/admin/samples.

The adapters Utility

Net8 provides support for various network protocols and naming methods. They are linked into particular executables and provide the interface between network protocols and Net8. To display installed Net8 protocols, enter:

% adapters

To display adapters linked with a specific executable, enter:

% adapters executable

For example, the following command displays the Net8 protocols linked with the oracle executable:

% adapters oracle
Net8 Protocol Adapters linked with oracle are:

BEQ Protocol Adapter
IPC Protocol Adapter
TCP/IP Protocol Adapter
RAW Protocol Adapter

Net8 Naming Adapters linked with oracle are:

Oracle TNS Naming Adapter
Oracle Naming Adapter

Advanced Networking Option/Networking Security products linked with oracle 
are:

Oracle Connection Manager

See Also:

For information on the Oracle Connection Manager, see the Oracle Net8 Administrator's Guide.

Multi-Threaded Server

See Also:

For information on the Multi-Threaded Server, see the Oracle8i Server Concepts and Oracle8i Administrator's Guide.

Oracle Names

See Also:

For information on Oracle Names, see the Oracle Net8 Administrator's Reference.

Net8 Assistant

Oracle Java Runtime Environment is installed with Net8 Assistant
($ORACLE_HOME/bin/net8asst). When the Net8 Assistant command script is executed, the java command script supplied with JRE 1.1.6.2 is called explicitly, regardless of other Java installations on the system.

Net8 Protocol Support

The supported protocols for Net8 version 8.1.5 on Solaris are BEQ protocol, IPC protocol, RAW protocol, TCP/IP protocol, SPX/IPX protocol, APPC/LU6.2 protocol.

Before installing the TCP/IP, APPC/LU6.2, or SPX/IPX Net8 protocol, the appropriate operating system software must be installed and configured. Refer to Oracle8i Installation Guide for Sun SPARC Solaris for requirements details. The BEQ and IPC Net8 protocols do not have any specific operating system requirements.

ADDRESS Specification

The IPC, TCP/IP, APPC/LU6.2, and SPX/IPX Net8 protocols each have a protocol-specific ADDRESS specification that is used for Net8 configuration files and for the MTS_LISTENER_ADDRESS database initialization parameter in the initsid.ora file. See the ADDRESS specification heading under each protocol section in this chapter for details.

Table 5-2 shows a summary of ADDRESS specifications for each protocol.

Table 5-2 ADDRESS Specification Summary

(PROTOCOL = BEQ)
(PROGRAM = ORACLE_HOME/bin/oracle)
(ARGV0 = oracleORACLE_SID)
(ARGS = '(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
(ENVS = 'ORACLE_HOME=ORACLE_HOME,ORACLE_SID=ORACLE_SID')

(PROTOCOL=IPC)
(KEY=key)

(PROTOCOL=TCP) 
(HOST=hostname) 
(PORT=port_id)

(PROTOCOL=SPX)
(SERVICE=servicename)

(PROTOCOL=LU62) 
(TP_NAME=transaction_program_name) 
(LU_NAME=logical_unit_name) 
(MODE=mode_name) 
(PLU=partner_lu_name)

The BEQ Protocol

The BEQ protocol is both a communications mechanism and a process-spawning mechanism. If a service name is not specified, either directly by the user on the command line or the Login screen or indirectly through an environment variable such as TWO_TASK, then the BEQ protocol is used. In which case, a dedicated server will always be used, and the multi-threaded server is never used. This dedicated server is started automatically by the BEQ protocol, which waits for the server process to start and attach to an existing SGA. If the startup of the server process is successful, the BEQ protocol then provides inter-process communication via UNIX pipes.

An important feature of the BEQ protocol is that no network listener is required for its operation, since the protocol is linked into the client tools and directly starts its own server process with no outside interaction. However, the BEQ protocol can only be used when the client program and Oracle8i reside on the same machine. The BEQ protocol is always installed and always linked to all client tools and to the Oracle8i server.

Specifying a BEQ ADDRESS

The BEQ protocol connection parameters are part of the ADDRESS keyword-value pair. You can enter the parameters in any order.

(ADDRESS =

(PROTOCOL = BEQ)
(PROGRAM = ORACLE_HOME/bin/oracle)
(ARGV0 = oracleORACLE_SID)
(ARGS = '(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
(ENVS = 'ORACLE_HOME=ORACLE_HOME,ORACLE_SID=ORACLE_SID')

)

Syntax for BEQ protocol connection parameters is described in Table 5-3.

Table 5-3 Syntax for BEQ Protocol Connection Parameters

Example 5-1 BEQ ADDRESS Specifying a Client

The following is an example of a BEQ ADDRESS:

(ADDRESS =

(PROTOCOL = BEQ)
(PROGRAM = /u01/app/oracle/product/8.1.5/bin/oracle)
(ARGV0 = oracleV815)
(ARGS = '(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
(ENVS = 'ORACLE_HOME=/u01/app/oracle/product/8.1.5,ORACLE_SID=V815')

)

The ADDRESS is commonly part of a larger construct such as a connect descriptor or configuration file.

The IPC Protocol

The IPC protocol is similar to the BEQ protocol in that it can only be used when the client program and the Oracle8i server reside on the same machine. The IPC protocol differs from the BEQ protocol in that it can be used with dedicated server and multi-threaded server configurations. The IPC protocol requires a network listener for its operation. The IPC protocol is always installed and always linked to all client tools and to Oracle8i.

For the IPC protocol, the location of the UNIX Domain Socket (IPC) file on UNIX systems changed after Oracle7 r7.1. Thus, if you have Oracle7 r7.1 installed on the same machine as Oracle8i and you attempt to make an IPC connection between the two instances, the connection may fail. The solution to this problem is to make a symbolic link between the directory where the IPC file used to be (/var/tmp/o) and where it now resides (/var/tmp/.oracle).

Specifying an IPC ADDRESS

The IPC protocol connection parameters are part of the ADDRESS keyword-value pair. You can enter the parameters in any order.

(ADDRESS=

(PROTOCOL=IPC)
(KEY=key)

)

Syntax for IPC protocol connection parameters is described in Table 5-4.

Table 5-4 Syntax for IPC Protocol Connection Parameters

Example 5-2 IPC ADDRESS Specifying a Client

The following is an example of an IPC ADDRESS:

(ADDRESS=

(PROTOCOL=IPC)
(KEY=PROD)

)

The ADDRESS is commonly part of a larger construct such as a connect descriptor or configuration file.

The RAW Protocol

When data is transferred between a client and a server, Net8 adds its own header information to every packet (a block of information sent over the network). Through the Raw Transport feature, Net8 can now minimize header information on each packet going over the network.

After the connection is established, two types of information flow over the network: data and break handling. The connection packets need the Net8 header information to establish the connection correctly. However, after the connection is established, all data packets are stripped of their Net8 header information and passed directly to the operating system, bypassing Net8's network and protocol layers. The performance of the connection is increased because of fewer protocol stack layers for the data to flow through and fewer bytes that are transmitted over the network.

This feature is transparently turned on whenever it is appropriate. That is, if no existing features require that header information be transmitted, the headers are stripped off. For example, encryption and authentication require certain information to be sent along with each packet of information; so Raw Transport would not be enabled.

This feature requires no configuration. Net8 determines if the conditions are met and then transparently switches to Raw Transport mode.

The TCP/IP Protocol

Oracle Corporation recommends that you reserve a port for your Net8 listener in the /etc/services file of each node on the network that defines the Net8 listener port. The port is commonly 1521. The entry list and the listener name and the port number; for example:

listener     1521/tcp

where listener is the name of the listener, as defined in listener.ora.

Reserve more than one port to start more than one listener.

Specifying a TCP/IP ADDRESS

The TCP/IP protocol connection parameters are part of the ADDRESS keyword-value pair. You can enter the three parameters in any order.

(ADDRESS=

(PROTOCOL=TCP)
(HOST=hostname)
(PORT=port_id)

)

Syntax for TCP/IP protocol connection parameters is described in Table 5-5.

Table 5-5 Syntax for TCP/IP Protocol Connection Parameters

Example 5-3 TCP/IP ADDRESS Specifying a Client

Following is an example of the TCP/IP ADDRESS specifying a client on the MADRID host:

(ADDRESS=

(PROTOCOL=TCP)
(HOST=MADRID)
(PORT=1521)

)

The last field could be specified by name, for example, (PORT=listener). The ADDRESS is commonly part of a larger construct such as a connect descriptor or configuration file.

The SPX/IPX Protocol

Oracle SPX/IPX protocol support provides a transparent, two-task communications interface between Oracle8i and client applications running on DOS, UNIX, OS/2, or Netware OS.

The ntisbsdm Broadcast Daemon

A client uses a name and translates the name into an SPX address to identify a server and communicate with it. The netware bindery is a directory service that provides the translation mechanism. When a server is registered with the bindery, it periodically notifies the bindery of its address. This is done using the Server Advertising Protocol (SAP).

The server broadcasts a SAP packet in an IPX datagram every 60 seconds. This SAP packet contains all relevant addressing information. Any client can then query its nearest server for the address of the required server.

The Oracle SPX/IPX protocol broadcasts using the ntisbsdm broadcast daemon in $ORACLE_HOME/bin. The ntspxctl utility starts and stops ntisbsdm.

The ntspxctl Utility

The ntspxctl utility contains functions to register and remove names, and to query a bindery. It can also be used to stop and start the broadcast daemon. (The listener automatically uses the daemon to register service names in use.)

Example 5-4 demonstrates several uses of the ntspxctl utility.

Example 5-4 Using the ntspxctl Utility

The ntspxctl utility reads commands from the command line. If parameters are missing, it prompts for them.

To start ntspxctl, enter:

$ ntspxctl

Output similar to the following is displayed:

ntspxctl: Version 2.0.12.1 - on
Fri Jul 3 11:43:50 1998

To start the broadcast daemon, enter:

ntspxctl> startup

Output similar to the following is displayed:

ntisbsdm started at Fri Jul 3 11:43:47 1998

A system message is displayed if the daemon has already been started.

Startup of the broadcast daemon should be automated, so it is always started when the machine is started. Automate daemon startup by adding an entry to the /etc/inittab file. For example, to start the ntisbsdm on system startup add the following line to /etc/inittab:

ntspxctl:2:once:/u/oracle/bin/ntisbsdm &

where /u/oracle is the full path to $ORACLE_HOME.

To register a name for testing, enter register and the server name. For example:

ntspxctl> register YYY

This creates a socket owned by ntisbsdm, and registers it.

A message similar to the following is displayed:

Name YYY successfully registered
YYY address 00eee045:000000000001:4454

To check the status of ntisbsdm, enter:

ntspxctl> status

or

ntspxctl> summary

A message similar to the following is displayed:

ntisbsdm started at Fri Jul 3 11:43:47 1998
Tracing is off
Pid: 14784 YYY

SPX/IPX Protocol Command Summary

Table 5-6 shows the help command summary for the SPX/IPX protocol.

Table 5-6 help Command Summary

The getname Command

The getname command asks the Novell system for names. It does not involve the broadcast daemon.

Enter:

getname name servicetype

A message similar to the following is displayed:

getname name servicetype (address number_of_hops)

The syntax for the getname command is explained in Table 5-7.

Table 5-7 Syntax for the getname Command

To see all possible names, enter:

getname * *

Example 5-5 shows names obtained using the getname command.

Example 5-5 Using the getname Command

ntspxctl> getname YYY *
YYY  servertype x0103 address 00eee045:000000000001:
    4465 hops 0000
ntspxctl> getname * 103
LSNR servertype x0103 address 00eee053:000000000001:
    502c hops 0000
IBM6 servertype x0103 address 00eee058:000000000001:
    507f hops 0000
DESK servertype x0004 address 00eee055:000000000001:
    5451 hops 0000
DESK servertype x0107 address 00eee055:000000000001:
    5104 hops 0000
CXY4 servertype x009e address 00eee055:000000000001:
    5063 hops 0000
IBM2 servertype x0004 address 00eee057:000000000001:
    5451 hops 0000

To stop ntisbsdm, enter:

ntspxctl> shutdown

The daemon will not be stopped if names are still registered. A message similar to the following is displayed:

1 names are registered
ntisbsdm not stopped

To remove a name, enter remove and the name. Following is an example for the name YYY:

ntspxctl> remove YYY

A message similar to the following is displayed:

Name xxx removed.
ntspxctl> shutdown
ntisbsdm stopped

To force a stop, enter:

ntspxctl> shutdown force

A message similar to the following is displayed:

ntisbsdm stopped

Specifying the SPX/IPX ADDRESS

After the SPX/IPX protocol and Oracle SPX/IPX protocol are installed on your system, you can use the SPX/IPX parameters with the TNS connect descriptors to identify SPX/IPX community nodes.

The SPX/IPX protocol parameters are part of the ADDRESS keyword-value pairs.

(ADDRESS=

(PROTOCOL=SPX)
(SERVICE=servicename)

)

Table 5-8 explains the syntax for the SPX/IPX protocol connection.

Table 5-8 Syntax for SPX/IPX Protocol Connection

Example 5-6 shows an SPX/IPX ADDRESS specifying service MAILDB1 on a remote server.

Example 5-6 SPX/IPX Protocol Connection

(ADDRESS=

(PROTOCOL=SPX)
(SERVICE=MAILDB1)

)

This ADDRESS is commonly part of a larger construct such as a connect descriptor or configuration file.

The APPC/LU6.2 Protocol

The Oracle APPC/LU6.2 protocol is available on networks that use LU6.2 services for communication between Oracle programs. For example, APPC/LU6.2 allows TNS applications to use API as a standard interface.

Figure 5-1 shows the communication layers between Oracle programs using the LU6.2 communications services and the Oracle APPC/LU6.2 protocol:

Figure 5-1 Communication Layers between Oracle programs and LU6.2

Solaris 2.x-Specific Listener

Solaris 2.x does not support the generic listener. To bring up the listener on the server side, run the ntllsnr command.

ntllsnr start|stop -l luname -t tpname -m modename

Syntax for the ntllsnr command is explained in Table 5-9

Table 5-9 Syntax for the ntllsnr Command

Specifying an APPC/LU6.2 ADDRESS

The APPC/LU6.2 protocol parameters are defined in a connect descriptor for each node. Each connect descriptor contains several keyword=value pairs. The APPC/LU6.2-specific keywords can be entered in any order within the connect descriptor.

(ADDRESS=

(PROTOCOL=LU62)
(TP_NAME=tpname)
(LU_NAME=luname)
(MODE=modename)
(PLU=partner_lu_name)

)

The syntax for the APPC/LU6.2 protocol connection is described in Table 5-10.

Table 5-10 Syntax for the APPC/LU6.2 Protocol

Net8 Naming Support

For details on configuring the NIS Naming Support, see the Net8 Administrator's Guide.

Oracle Enterprise Manager (OEM)

Agent Service Discovery and Auto-Configuration

The Oracle Intelligent Agent requires no configuration, unless you want to integrate it with an SNMP system (see "Configuring Oracle Intelligent Agent for Oracle SNMP".)

Debugging Tcl Scripts

The executable oratclsh is provided for debugging your Tcl scripts. Before executing oratclsh, set the environment variable TCL_LIBRARY to point to $ORACLE_HOME/network/agent/tcl.

Configuring Oracle Intelligent Agent for Oracle SNMP

Although Oracle Intelligent Agent does not require Simple Network Management Protocol (SNMP) in order to work, Oracle SNMP support can be configured before starting the Intelligent Agent. Note that all the configuration files for the following steps are located in the $ORACLE_HOME/network/snmp/peer directory.

Configure Master Agent

In the CONFIG.master file, make the following change:

1. Search for the line beginning with MANAGER.

2. Change the ipaddr field, coded as 130.35.10.210, to the IP address or hostname of the machine where you want SNMP trap messages sent.

You can also make other changes to the CONFIG.master file as documented within the file.

Configure the Encapsulator

1. Add the following line to the snmpd.conf file:

where hostname_or_IP_address represents the local machine's IP address.

• In the CONFIG.encap file, you can optionally modify the port number, which is set to 1161 in the default file. If you modify the port number, you must also modify the port number for NEW_SNMPD_PORT in the start_peer script.

  NEW_SNMPD_PORT is the port on which the snmpd agent (the native Sun SPARC Solaris SNMP agent) listens. Make sure this is the same port as specified in the CONFIG.encap file. NEW_TRAPD_PORT is the PEER encapsulator port to which the snmpd agent sends traps.

  NEW_SNMPD_PORT and NEW_TRAPD_PORT in the start_peer script must have different port numbers. You may also modify the NEW_TRAPD_PORT port number.

Verify start_peer Script

The start_peer script contains a line like the following:

SNMPD = snmpd_executable_path

If the snmpd executable on your system is not in the location indicated by the start_peer script, edit snmpd_executable_path to the correct location of the snmpd executable.

Start the SNMP Components

Perform the following steps to start the SNMP components:

1. Verify that the SNMP components, master_peer, encap_peer, and snmpd, are not running:

   $ ps -aef | grep peer
   

If any of the components are running, log in as the root user and use the kill command to terminate the processes before proceeding.

• As the root user, run the start_peer script to start the PEER master agent, PEER encapsulator, and native Sun SPARC Solaris SNMP agent:

3. Verify that the SNMP components are running:

Configure and Start the Database Subagent

Configuration and startup of the database subagent (the Oracle Intelligent Agent) is described in the Oracle Enterprise Manager Configuration Guide.

Oracle Advanced Security Option

.bak Files

During Oracle Advanced Security Option installation, three.bak files are created: naeet.o.bak, naect.o.bak, and naedhs.o.bak. They are located in $ORACLE_HOME/lib. These files are required for relinking during Oracle Advanced Security Option de-install and should not be deleted.

Security and Single Sign-On

For more information about details on configuring Security and Single Sign-On, see the Oracle Advanced Security Option Administrator's Guide.

DCE Integration

See Also:

For details on configuring DCE Integration, see the Oracle Advanced Security Option Administrator's Guide.